I mailed the list some months ago about this, but still havent
managed to crack it. I wonder if anyone can shed some light.
I'm trying to boot a number of diskless Linux boxes using
an Alpha (5.0A PK 3) as a boot node, and dhcp (not joind)
as the initial parameter source.
Everything proceeds OK until the client attempts to nfs-mount
its root filesystem. It then gets an error code which it interprets
as 'server requires stronger authentication'.
Console output on the booting client shows that its got all
the correct parameters for ip address, name, netmask etc
and that it is indeed trying to NFS-mount the correct directory
as its root filesystem.
I've got that directory exported -root=0 on the server
=======
/tftpboot/ProX/prox-2
-root=0
=======
and mountd on the server is running with no checks and
non-root mounts permitted: '/usr/sbin/mountd -n'
The same scheme succeeds if I use a Linux box as the boot-host,
and when the client has booted, it can then successfully mount
(on /mnt, say) the above directory.
I'm now ploughing through Linux's nfsroot.c and tcpdumps of the
various mount attempts, but if anyone can suggest what the message
'server requires stronger authentication' might mean, I'd be
very grateful.
Cheers,
Terry.
Received on Wed Nov 07 2001 - 09:50:01 NZDT