Re: Tracking changes made by installation of software

1999-02-07 Thread John Hasler
MallarJ writes: > dpkg works fine, except in two cases. > 1) if you don't use dpkg (some things still come in gzipped packages) Use alien (or debhelper, if you prefer "real" packages). > 2) If installation scripts run after dpkg completes do more changes. File bug reports. No package should ev

Re: Tracking changes made by installation of software

1999-02-07 Thread Jiri Baum
[EMAIL PROTECTED]: > > > allows admins to prevent users from making incorrect modifications > > > where they shouldn't be. Jiri: > > Why aren't you setting permissions appropriately? ... > This doesn't have anything to with my system, I'm just repoting on what > tripwire does. I don't have permi

Re: Tracking changes made by installation of software

1999-02-07 Thread MallarJ
In a message dated 2/6/99 1:52:00 PM Central Standard Time, [EMAIL PROTECTED] writes: > What problem are you trying to solve here? You do realize that dpkg saves > a md5sum of every conffile it installs, don't you? And that when you > upgrade the package that dpkg will check the md5sum and, if

Re: Tracking changes made by installation of software

1999-02-06 Thread John Hasler
jiri writes: > Actually, a simple version shouldn't be difficult at all - if you start > with the `find and diff' idea, but put a checksum next to each of the > files, then you'll have a list of files added, files removed and files > changed. For the changed files, you compare them with an archive

Re: Tracking changes made by installation of software

1999-02-06 Thread MallarJ
In a message dated 2/6/99 2:51:14 AM Central Standard Time, [EMAIL PROTECTED] writes: > > allows admins to prevent users from making incorrect modifications where > > they shouldn't be. > > Why aren't you setting permissions appropriately? > > Unlike MS DOS / Win, in Linux you can set files

Re: Tracking changes made by installation of software

1999-02-06 Thread Jiri Baum
[EMAIL PROTECTED]: ... > allows admins to prevent users from making incorrect modifications where > they shouldn't be. Why aren't you setting permissions appropriately? Unlike MS DOS / Win, in Linux you can set files to be read-only to ordinary users, or invisible altogether (inaccessible directo