[comp.sys.next] Restricting access on external disk

ram@cpsacs.cps.msu.edu (Ram Raghavan) (06/22/91)

Hi, we have a NeXT Station 68040 with 200M int drive. We bought
a Maxtor LXT340 (340MB) and connected it to the external SCSI
port. The disk was recognized and initialized (using the popup
window) fine. We labeled the drive "ext" and disk was mounted
as /ext.

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

When we reboot the NeXT however it doesn't mount /ext at all. We even
added an entry in the netinfo database using niload. Still the same
problem.

Could you please let me know what I'm doing wrong?
Thanks.

-Ram Raghavan
ram@cpsacs.cps.msu.edu

wb1j+@andrew.cmu.edu (William M. Bumgarner) (06/24/91)

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. <Thpppt!>
"I ride tandem with the random/Things don't run the way I planned them.."