[Sussex] Re: Setting up a simple home network

Steve Dobson steve at dobson.org
Sat Apr 30 13:25:39 UTC 2005


Alan

On Sat, 2005-04-30 at 14:09 +0100, John Crowhurst wrote:
> On Sat, April 30, 2005 13:21, Captain Redbeard said:
> > I then added the following line to /etc/fstab on the client:
> >
> >
> > templeofthebeard.homenet:/home/public /home/public nfs
> > defaults 0 0
> 
> Make sure the mount point exists on the client, its just a directory.
> 
> > And for good measure ran "/etc/rc.d/rd.inet2" on both
> > machines.  It ran OK on the server but the client warned me
> > that rc.portmap was not executable!  I had to make this file
> > executable and re-ran "/etc/rc.d/rd.inet2" but now it's
> > telling me:
> 
> ok chmod 755 /etc/rc.d/rc.portmap should fix that.
> 
> > mount: templeofthebeard.homenet:/home/public failed, reason
> > given by server: Permission denied
> 
> The NFSd on the sharing machine doesn't allow you to perform the
> operation, perhaps you've not restarted the service after making a change
> to the /etc/exports, or the setting is too restrictive.
> 
> Look at the /etc/exports file on the sharing machine, I see you have:
> /home/public 192.168.0.1/255/255/255.0(sync)
> *(sync,no_subtree_check,rw)

Dumb question to check you have thinks right.

192.168.0.2 templeofthebeard is the NDS server here, isn't it?  The
machine running nfsd!  If shrineofthebeard is the server then you are
only allowing it to share the directory to itself.

As you have names for the machines I suggest that you use them!
Try changing the /etc/exports (assuming shrineofthebeard) to:

/home/public templeofthebeard(sync,no_subtree_check,rw)

BTW: What do the options sync & no_subtree_check do?  I don't have them
on my Debian system.

> It looks like the setting you have doesn't allow the connecting machine to
> even have readonly access. You could try changing it to:
> 
> /home/public (sync,no_subtree_check,rw,no_root_squash)

I agree, and has he as a simple network this is okay, but bad practice
in general as it allows anyone to mount the /home/public directory and
that then gives them access to the files.

> So that all machines gain read/write access, and that the root's files
> keep their root ownership across machines.
> 
> > i.e. all that work for nothing.  Now what?
> 
> Well, you are getting somewhere, albeit slowly.

I tend to agree, he is making progress very slowly.

Steve





More information about the Sussex mailing list