🚀 go-pugleaf

In article <1992Sep29.005224.25329@lsa.umich.edu> Hal.Varian@umich.edu writes:
> In article <1992Sep29.002311.8323@ni.umd.edu> louie@ni.umd.edu  
> (Louis Mamakos) writes:
> > In article <1992Sep28.214104.25073@lsa.umich.edu>  
> Hal.Varian@umich.edu writes:
> > >In article <28SEP92.15351318@enh.nist.gov> aoml@enh.nist.gov  
> > >writes:
> > >> We just add a new hp drive purchased from TECOR, when ever  
> we  
> > >change the onwership of user's files, the whole disk's  
> ownership  
> > >randemly changed back to one
> > >> of our user after few seconds.
> > >> 
> > >>         The command I use is chown -R directory-name
> > >> 
> > >>         With -R option, chown seem not only going decending  
> > >but also going
> > >> up to the whole disk.
> > >> 
> > >>         has anybody experienced that problem ?
> > >>         We are using 2 NeXT stations trubo clolrs on a  
> small  
> > >network
> > >> 
> > >> aoml,Ying-Yuang Chen
> > >
> > >The same thing happened to me with my Fujitsu drive.  I was  
> > >running 3.0 beta PR2 when it happened, so I decided to wait  
> for  
> > >the official release before I tried to figure out what was  
> going  
> > >on.  
> > 
> > Yes, don't allow the workspace to auto-mount the disk.  When  
> it does,
> > the file system is mounted such the each file appears to be  
> owned by
> > the user that's currently logged in.  If you think about it,  
> that's
> > the correct behaviour for removable media such as a floppy.
> > 
> > The solution is configure an entry in /etc/fstab and wherever  
> the hell
> > it goes in netinfo for that file system.
> > 
> > louie
> 
> Well my fstab entry says
>   /dev/sd0a / 4.3 rw,noquota,noauto 0 1
>   /dev/sd1a /Users 4.3 rw,noquota,noauto 0 2
> 
> As far as I can tell from the documentation, this is what I'm  
> supposed to say. 
> 

You don't want "noauto" except for the boot disc.