Re: Root-NFS: Server returned error 13

[Brian Butcher <butcher@yebo.co.za>]

> Ken Yap writes:
>  > >    /tftpboot/192.168.77.194 192.198.77.194(rw, no_root_squash)
>  > >    Root-NFS: Server returned error 13 while mounting
>  >
>  > I find that exports files work better (or even at all) when hostnames
>  > are used.
> 
> If you do that, make sure that you list these hostnames in /etc/hosts,
> rather than relying on DNS to do the right thing. Not only is this a
> security precaution, but I know that the Solaris NFS server won't even
> attempt to resolve these names using anything other than /etc/hosts. I
> don't know whether common NFS servers for Linux exhibit the same
> behavior.

Still not there:- the inconsistent I.P. addresses are an error in
writing E-mail, not the exports file.
I have tried using I.P. addresses, unmodified hostnames and fully
modified hostnames. It appears to make no difference if I call
the client 192.168.77.194, parsimony or parsimony.in.mafikeng.

Does the second line of this extract from the debug file mean that the
export has been correctly processed? or does the '^I' symbol mean it 
was not completed?


Jun 30 11:42:20 mean_machine mountd[72]: clnt parsimony.in.mafikeng
exports: 
Jun 30 11:42:20 mean_machine mountd[72]: ^I/tftboot/192.168.77.194 rw
portck 
Jun 30 11:43:14 mean_machine mountd[72]: flushed host access cache 
Jun 30 11:43:14 mean_machine mountd[72]: mnt [1 99/6/30 13:25:55
192.168.77.194 0.0+0] 
Jun 30 11:43:14 mean_machine mountd[72]: ^I/tftpboot/192.168.77.194 
Jun 30 11:43:14 mean_machine mountd[72]: ^Imount res = 13 
 192.168.77.194 0.0+0]

===========================================================================
This Mail was sent to netboot mailing list by:
Brian Butcher <butcher@yebo.co.za>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.