Subject: Re: net boot problems
From: David Laight <email@example.com>
Date: 02/01/2003 20:35:06
On Sat, Feb 01, 2003 at 12:20:50PM -0800, Andrey Petrov wrote:
> Sounds as nfs server isn't actually started, make sure you
> have rpcbind, mountd and nfsd running.
> > After the 'Using BOOTPARMS protocol' message, there is a bit of nfs traffic,
> > lookup fh 2048,1/2 "netbsd" this is GENERIC
> > read fh 2048,1/3 1024 bytes @ 0
> > read fh 2048,1/3 1024 bytes @ 1024
> > read fh 2048,1/3 1024 bytes @ 2048
> > read fh 2048,1/3 1024 bytes @ 3072
> > read fh 2048,1/3 64 bytes @ 52
> > read fh 2048,1/3 440 bytes @ 3071820
> > All the responses are 'ok'.
NFS reads of the kernel...
I've since made more/less (maybe different) progress.
The timeout of the bootp requests can be removed by running a dhcp server
(I should know that, but 'man bootp' really ought to link a dhcp page).
However the netbsd dhcp server seems unwilling to report the 'server path'
option - which I think needs setting to the base of the exported filesystem.
(I don't fancy running nfsd chrooted....)
I've searched the source (parts are trully horrid) but the only reference
to the server path option is in a header file. Maybe it can be specified
The INSTALL kernel actually loads - but can't find a root filesystem.
Is there a problem with the kernel size?
David Laight: firstname.lastname@example.org