[ On Friday, May 28, 1999 at 14:37:06 (+1000), Simon Burge wrote: ]
> Subject: Re: bin/7656: run kvm_mkdb at boot to fix dmesg error 
>
> Given that it's a "machdep", should this "restriction" on what
> the contents of 'booted_kernel' are?  If so, then I can change
> 'booted_kernel' to something like 'kernel_location' and make
> 'booted_kernel' the basename of that, but then that may not make sense
> for diskless boots...

It the base filename of the 'booted_kernel' doesn't make sense from
diskless client's perspective then that's the fault of the the person
who configured the file server's image of the root filesystem.  It
should be trivial to ensure that the kernel on the TFTP or MOP server
and the kernel in the client's root directory are identical.

-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>      <robohack!woods>
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>