From owner-freebsd-hackers Sun Jul 2 17:10:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns3.khmere.com (d83b56af.dsl.flashcom.net [216.59.86.175]) by hub.freebsd.org (Postfix) with ESMTP id 17A1A37B7BF; Sun, 2 Jul 2000 17:10:30 -0700 (PDT) (envelope-from nathan@khmere.com) Received: from khmere.com (ns2.khmere.com [216.59.86.176]) by ns3.khmere.com (8.9.3/8.8.7) with ESMTP id RAA35602; Sun, 2 Jul 2000 17:13:31 -0700 (PDT) Message-ID: <395FD9F1.84B67DE9@khmere.com> Date: Sun, 02 Jul 2000 17:10:26 -0700 From: nathan@khmere.com X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.15 i586) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-net@FreeBSD.ORG" , "hackers@FreeBSD.ORG" Subject: Re: loader ??? Awwww... come on someone must know !!! References: <395D7D2B.48B90842@khmere.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nathan@khmere.com wrote: > I have FreeBSD 4.0-RELEASE (on i386) > > What I am trying to do is nfs root boot from the loader (?) > I do: > > ok> unload kernel > ok> load diskless_kernel > ok> set kernel=diskless_kernel > ok> boot -r -h > > Now what I understand is the -r flag will tell the kernel to overide the > rootdev and use the "staticly linked device" from when you made the > kernel ? > > Now my kernel (the diskless_kernel ) is a diskless kernel ( with BOOTP, > NFS_ROOT .... etc.. ) compiled in. > But when I boot like this is just tries to mount /dev/ad0s1a ... (normal > device ) even though it gets the proper reply from the bootp server that > its rootfs= it even prints : > > rootfs is > Mounting root from ufs:/dev/ad0s1a > > but still mounts the ufs ! > > How do if force it to boot root fs on nfs ? > > I have tried to do a boot -a then when I prompts me for root fs I enter > the proper nfs mount and it is cool ...... but I need it to do it with > out promting... > > I have tried to : > > ok> set rootdev=nfs: > ok> boot -h > ok> can't determine root device > > I have also passed it kernel flags ? (mybe wrong ones ... ? ) > > Now I have looked at the /usr/src/sys/boot/i386/libi386/bootinfo.c and > I see where it checks the roodev to see if it is proper ..... > but I cannot determine what type of device I can name so that this will > not die on me ??? > set rootdev=??? > > how do I have the kernel to load the nfs root instead of use the currdev > ? > > What does etherboot do when it loads the kernel ? does it pass it > special parameters ?? > > If you are wondering why I just don't boot from etherboot ....etc...(I > do ) but... I want to be able to boot my remote systems without a > floppie and chose how to boot from loader (via serail console ...I don't > have serial access for the bios but I can get serial console with > FreeBSD !! ). Either default (use local drive) or load the diskless > kernel , then boot diskless. > This way I almost the same options ..... and maybe automate it... > > Any help would be great !! > > thank you kindly.... > > nathan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message