On Sat, 2002-09-21 at 13:37, Jim Wildman wrote: > You can also use > rpm -Va > to verify the integrity of all the rpms that have been installed.
-Remember that once the system has been broken into, you can't trust the executables and libraries on it to give accurate results. Keep static versions of handy tools like ls, rpm, fsck, your RPM database, and so on on a CD or diskette. -Consider putting /usr on a separate hard drive and setting the jumpers on the drive to read-only (some drives have this, on others you will have to cut the 'write' lead on the cable, or rig a jumper yourself). -Create and follow a written change-control policy (when do you install new software, how do you test it first, who does it, where do you document the change). Don't go overboard on thi, it doesn't need to be too complex. Just make sure that if you aren't sure about a change you can find out QUICKLY if it's legit. Remember that it's easy to forget some minor change you made six months ago. This should include config changes. -David ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
