Xref: utzoo comp.protocols.nfs:2221 comp.unix.questions:30785
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!uhccux!uhunix1.uhcc.Hawaii.Edu!pilger
From: pilger@uhunix1.uhcc.Hawaii.Edu (Eric Pilger)
Newsgroups: comp.protocols.nfs,comp.unix.questions
Subject: Re: Personal NFS?
Message-ID: <12681@uhccux.uhcc.Hawaii.Edu>
Date: 27 Apr 91 00:27:27 GMT
References: <1991Apr24.000005.7810@bradley.bradley.edu> <4034@inews.intel.com>
Sender: news@uhccux.uhcc.Hawaii.Edu
Followup-To: comp.protocols.nfs
Organization: University of Hawaii
Lines: 39

In article <4034@inews.intel.com> bhoughto@pima.intel.com (Blair P. Houghton) writes:
>
>	cd $HOME
>	mkdir foo
>	mount -t nfs /bar/bletch@uunet foo
Actually, SunOS insists on:
	mount -t nfs uunet:/bar/bletch $HOME/foo

>	cd $HOME
>	umount -f foo
Once again, SunOS insists on:
	umount $HOME/foo

>	rmdir foo
>
>Basically, RTFM mount(8) and umount(8).  If your sysadmin has
>turned off your permission to invoke mount or umount, scream

SunOS does not let anyone but root issue the mount or umount command.
I suppose you could change these commands to be SUID, but I would only
want to do this on my own personal machine.  IT WOULD NOT be a wise
thing to do generally.  The safest path is to create a small program
that is hardwired to do specific mounts, and make it SUID.  This
provides a little more control.

>loudly.  The only thing you need to do either is write permission
>in the directory, and the right sort of connectivity to the

AND make sure the file system you're trying to mount from the remote machine
is exported to you.  Check the /etc/exports file.

>remote system (most routers and gateways prevent nfs activity


Eric Pilger
Systems Programmer 
NASA Infrared Telescope Facility
2680 Woodlawn Drive
Honolulu, HI 96822