Subject: Re: bin/7656: run kvm_mkdb at boot to fix dmesg error
To: Gordon W. Ross <>
From: Simon Burge <>
List: tech-kern
Date: 05/29/1999 16:39:20
"Gordon W. Ross" wrote:

> Simon Burge writes:
> [ in regards to what "booted_kernel" should be ]
>  > 
>  > It _is_ trivial to ensure that the kernel on the TFTP or MOP server
>  > and the kernel in the client's root directory are identical, but is it
>  > a requirement to have the file name the same in each case?  I prefer
>  > calling the kernel in the diskless client area "/netbsd", but calling
>  > the kernel by hostname in the TFTP/MOP server directory.  I guess I
>  > could make directories based on the hostname, and put kernels called
>  > "netbsd" in those, but (a) I don't see why this should be dictated by
>  > the OS and (b) some machines have problems with the length of the TFTP
>  > bootfile name.
> The best thing here is a real boot program in the TFTP area,
> i.e. one which can load /netbsd from the actual NFS root.
> You get other nice features too, like choosing which kernel
> to boot.  See the sparc, sun3, or any of several others.

It's on my todo list, but it's not done yet...