Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!mips!apple!agate!agate!adrianho From: adrianho@barkley.berkeley.edu (Adrian J Ho) Newsgroups: comp.protocols.nfs Subject: Re: Personal NFS? Message-ID: Date: 27 Apr 91 06:34:18 GMT References: <1991Apr24.000005.7810@bradley.bradley.edu> <4034@inews.intel.com> <12681@uhccux.uhcc.Hawaii.Edu> Sender: root@agate.berkeley.edu (Charlie Root) Followup-To: comp.protocols.nfs Organization: University of California, Berkeley Lines: 21 In-Reply-To: pilger@uhunix1.uhcc.Hawaii.Edu's message of 27 Apr 91 00: 27:27 GMT In article <12681@uhccux.uhcc.Hawaii.Edu> pilger@uhunix1.uhcc.Hawaii.Edu (Eric Pilger) writes: >>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. Or, if you don't have access to the remote machine: showmount -e Personally, I'd trust showmount more than /etc/exports. Some systems (eg. SunOS) require you to run exportfs(8) after you update /etc/exports to get the desired effect, while others (eg. Ultrix) don't. If (like me) you have to deal with a mix of the two, it's all too easy to forget that second step. -- ----------------------------------------------------------------------------- Adrian Ho, EECS (pronounced "eeks!") Dept. Phone: (415) 642-5563 UC Berkeley adrianho@barkley.berkeley.edu