You can also easily customize tripwire to ignore files you KNOW are going to change. Simplifies the process of weeding through the list.
Also catches those cases where "make install" fiddles with config files. > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > David Boyes > Sent: Friday, February 27, 2004 11:37 AM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] RPM question > > > > I also use find and grep a lot for this kind of thing. > > Assuming you know your software is going into /usr, you could > > do something like this: > > > > find /usr > before > > ./configure ; make ; make install > > find /usr > after > > > > for i in `cat before`; do > > grep -v $i after > zzz > > mv zzz after > > done > > > > The remaining "after" file will only have those files which > > were not in "before." > > That's one of the nice things about using tripwire for this > -- you don't > have to know in advance what got changed. tripwire does a > snapshot of the > whole system, so when you get some lame package that dumps > files in /lib or > other unexpected places, or you need to edit a file in /etc > or something, > you don't have to track down everything. > > -- db > ============================================================================== If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. <http://www.ml.com/email_terms/> ==============================================================================
