<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
</head><body>
<p style="margin: 0;"><span> </span></p>
<p style="margin: 0;"><span>Use rsync.  Before the install, rsync the file system to a backup directory.  Then after the install use rsync to compare.  Example command lines for the backup:</span></p>
<p style="margin: 0;"> </p>
<p style="margin: 0;"><span>rsync -rvax / /backup_mounted_fs/</span></p>
<p style="margin: 0;"><span> </span></p>
<p style="margin: 0;"><span>OR</span></p>
<p style="margin: 0;"><span> </span></p>
<p style="margin: 0;"><span>rsync -rvax / joe@othermachine:/pre_install_backup/</span></p>
<p style="margin: 0;"><span><span></span></span></p>
<p style="margin: 0;"><span><span><br/></span></span></p>
<p style="margin: 0;"><span><span>Example command lines for the compare:</span></span></p>
<p style="margin: 0;"><span><span><br/></span></span></p>
<p style="margin: 0;"><span><span>rsync -rvaxcn / /backup_mounted_fs/</span></span></p>
<p style="margin: 0;"><span><span>rsync -rvaxcn / joe@othermachine:/pre_install_backup/</span></span></p>
<p style="margin: 0;"><span><span><br/></span></span></p>
<p style="margin: 0;"><span><span>Note the trailing slashes, they are needed.  Also note the addition of 'c' and 'n' options on the compare.  They cause rsync to compare using checksums instead of file metadata and to perform a test run without actually changing data respectively - with the 'v' flag outputting what it would have synced.  'x' instructs rsync to not descend into other file systems (eg. /proc, etc).</span></span></p>
<p style="margin: 0;"> </p>
<p style="margin: 0;">It's a very useful tool for things like this.</p>
<p style="margin: 0;"> </p>
<p style="margin: 0;">-Alan</p>
<p style="margin: 0px; "></p>
<div style="margin: 5px 0px 5px 0px;">
<br/>On March 23, 2012 at 9:10 AM James Sumners <james.sumners@gmail.com> wrote:
<br/>
<br/>> I have a situation where I'm being forced to allow a remote installer
<br/>> to have root level sudo access to install their company's product
<br/>> (don't like it, but it's out of my hands). Technically, I have the
<br/>> system setup such that they should not need such access, but I can't
<br/>> change the monkey's script. Anyway, I'd like to be able to sort of
<br/>> "snapshot" my file system before I let them in so that I can go back
<br/>> and look at a before and after difference. Do any of you know of such
<br/>> a tool? Could this be done with rsync?
<br/>>
<br/>> I've read that LVM supports snapshots at the block level. Seeing as
<br/>> they are block level snapshots I don't see how that will help me
<br/>> figure out what the installer changed. I'd be able to revert the
<br/>> changes, but not study them.
<br/>>
<br/>> --
<br/>> James Sumners
<br/>> http://james.roomfullofmirrors.com/
<br/>>
<br/>> "All governments suffer a recurring problem: Power attracts
<br/>> pathological personalities. It is not that power corrupts but that it
<br/>> is magnetic to the corruptible. Such people have a tendency to become
<br/>> drunk on violence, a condition to which they are quickly addicted."
<br/>>
<br/>> Missionaria Protectiva, Text QIV (decto)
<br/>> CH:D 59
<br/>> _______________________________________________
<br/>> Ale mailing list
<br/>> Ale@ale.org
<br/>> http://mail.ale.org/mailman/listinfo/ale
<br/>> See JOBS, ANNOUNCE and SCHOOLS lists at
<br/>> http://mail.ale.org/mailman/listinfo
</div>
</body></html>