Xref: utzoo comp.protocols.nfs:2216 comp.unix.questions:30766
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!reed!intelhf!ichips!iwarp.intel.com!inews!pima!bhoughto
From: bhoughto@pima.intel.com (Blair P. Houghton)
Newsgroups: comp.protocols.nfs,comp.unix.questions
Subject: Re: Personal NFS?
Message-ID: <4034@inews.intel.com>
Date: 26 Apr 91 03:04:35 GMT
References: <1991Apr24.000005.7810@bradley.bradley.edu>
Sender: news@inews.intel.com
Organization: Intel Corp, Chandler, AZ
Lines: 33

In article <1991Apr24.000005.7810@bradley.bradley.edu> guru@buhub.bradley.edu (Jerry Whelan) writes:
>	Once upon a time, a friend of mine mentioned in passing a package
>that would allow a normal user to mount remote filesystems in said user's
>home directory.

This sounds oddly undescriptive, but the obvious answer is to

	cd $HOME
	mkdir foo
	mount -t nfs /bar/bletch@uunet foo

and wait (usually milliseconds) for nfs to find and mount the fs.

To get to the file /bar/bletch/bazz on uunet, the path is
$HOME/foo/bazz, or ~/foo/bazz, or /usr/noodles/nudelman/bazz,
if you're Nudelman.

When you're done, do

	cd $HOME
	umount -f foo
	rmdir foo

Basically, RTFM mount(8) and umount(8).  If your sysadmin has
turned off your permission to invoke mount or umount, scream
loudly.  The only thing you need to do either is write permission
in the directory, and the right sort of connectivity to the
remote system (most routers and gateways prevent nfs activity
through them, but the workstation in the next cubicle is a
short hop).

				--Blair
				  "I scratch my head."