Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!jarthur!nntp-server.caltech.edu!jjfeiler
From: jjfeiler@nntp-server.caltech.edu (John Jay Feiler)
Newsgroups: comp.sys.next
Subject: external hard disks and automounter
Keywords: automounter hard disk fstab
Message-ID: <1991Mar27.212410.8118@nntp-server.caltech.edu>
Date: 27 Mar 91 21:24:10 GMT
Organization: California Institute of Technology, Pasadena
Lines: 26

I discovered an interesting problem last night, and I haven't seen it
mentioned anywhere (though my search hasn't been exhaustive), so I thought I'd
mention it here:

The situation:  New external Fujitsu M2263S, named ExternalDisk, internal
105MB Quantum.
Internal drive is mounted as /, because I could not find anyone with 2.1 to
do a builddisk on the Fujitsu, Fujitsu mounted as /ExternalDisk.

If I let automounter do the mounting, and log in as root, everything is
hunky-dory.  I have the Users directory on the Fujitsu, and a sym-link from
/Users to /ExternalDisk/Users.  When I log in as som normal user, everything is 
ok until I try and
ok until I try and log out, at which point I get a "can't eject some disk"
message.  I click ok, and it logs me out.  Now, when another user logs in,
every file on the external disk is listed as having the first user as owner,
so the second user can't write in any of her own directories.

However, if I put the appropriate entry in fstab, so the automounter doesn't
get a chance to mess me up, everything works as expected.  Has anyone else 
encountered this?  Does it sey somewhere in the docs that I should have been
doing this all along?

	Just thought I'd mention it...

		John Feiler