ben@epmooch.UUCP (Rev. Ben A. Mesander) (12/13/90)
>In article <27687f3f.2675@uop.uop.edu> nishan@uop.edu (Nishan Sandhar) writes: >Is it advisable to set the various bits to make a file non-readable, non- >deleteable, etc? Especially on the sys:c directory, some of the devs >directory's files, fonts, etc. > >This would most likely protect against viruses, but do programs generally >require a certain status for some of these files? > >Please reply via e-mail, and I'll post a summary if there is interest. > > >-- >-------------------------------------------------- >| Nishan Sandhar | University of the Pacific | >| nishan@uop.edu | Stockton, CA 95211 | >-------------------------------------------------- I've done this, after I accidentally overwrote a library via a typo. I've had no problems. -- | ben@epmooch.UUCP (Ben Mesander) | "Cash is more important than | | ben%servalan.UUCP@uokmax.ecn.uoknor.edu | your mother." - Al Shugart, | | !chinet!uokmax!servalan!epmooch!ben | CEO, Seagate Technologies |
nishan@uop.edu (Nishan Sandhar) (12/14/90)
Is it advisable to set the various bits to make a file non-readable, non- deleteable, etc? Especially on the sys:c directory, some of the devs directory's files, fonts, etc. This would most likely protect against viruses, but do programs generally require a certain status for some of these files? Please reply via e-mail, and I'll post a summary if there is interest. -- -------------------------------------------------- | Nishan Sandhar | University of the Pacific | | nishan@uop.edu | Stockton, CA 95211 | --------------------------------------------------