On Wed, 26 Sep 2001, Hubert Feyrer wrote:

> On Tue, 25 Sep 2001, Rafal Boni wrote:
> > I *think* you may be able to work around this if you wire down the root &
> > dump paritions in your config, but my sinuses are blocking the flow of oxygen
> > to my brain, so I may be wrong here.
> 
> No, you are right. I use this for a netbooting kernel:
> 
> 	config              netbsd          root on sq0 type nfs
> 
> and this now that I found time to prepare my disk:
> 
> 	config          netbsd          root on sd1 type ffs
> 
> Of course I'm still tftp'ing the kernel in the latter case.

  I stole the device_register() stuff from the pmax port, and modified it
to work on my Challenge S.  It uses the OSLoadPartition passed as one of
the arguments to determine the root filesystem.  I think this environment
variable is used to specify where the kernel is located for the auto and
single commands, and the boot command if no explicit path is specified.
For netbooting with the root on NFS, I set it to "bootp()", and the kernel
mounts the root from the NFS server.  By setting it to
"scsi(0)disk(2)rdisk(0)partition(0)", I could netboot with 'boot -f
bootp()netbsd' and have it mount the root from the second disk.  [This
would preclude having an automatic boot from the network though, but that
was OK for me at the time.  Hmm, I wonder if you could set SystemPartition
to "bootp()" and OSLoader to "netbsd".  then the PROM would boot netbsd
from the network, and the kernel could use OSLoadPartition to get the root
device?]

--
Michael L. Hitch			mhitch@montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA