Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!sei.cmu.edu!fs7.ece.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!wb1j+ From: wb1j+@andrew.cmu.edu (William M. Bumgarner) Newsgroups: comp.sys.next Subject: Re: Restricting access on external disk Message-ID: Date: 23 Jun 91 18:38:59 GMT References: <1991Jun21.222350.20974@msuinfo.cl.msu.edu> Organization: Carnegie Mellon, Pittsburgh, PA Lines: 26 In-Reply-To: <1991Jun21.222350.20974@msuinfo.cl.msu.edu> Excerpts From Captions of netnews.comp.sys.next: 21-Jun-91 Restricting access on exter.. Ram Raghavan@cpsacs.cps. (831) >PROBLEM: Now whoever logs in becomes the "owner" of /ext. We created >an /etc/fstab entry for the external disk to restrict the file access. >(Refer p.169 in Network and System Administration manual.) >The /etc/fstab looked as follows: > > /dev/sd0a / 4.3 rw,noquota,noauto 0 1 > /dev/sd1a /ext 4.3 rw,noquota,noauto 0 1 > I would make fun of you about this.... but I can't because I just did the same thing less than two days ago. :-) Remove the 'noauto' from the /ext mount line-- this will allow it to automatically mount at boot time. b.bum b.bumgarner | Disclaimer: All opinions expressed are my own. wb1j+@andrew.cmu.edu | I officially don't represent anyone unless I NeXT Campus Consultant | explicity say I am doing so. So there. "I ride tandem with the random/Things don't run the way I planned them.."