Date: Fri, 30 Oct 1998 10:34:59 -0800 From: Mike Smith <mike@smith.net.au> To: Mike Smith <mike@smith.net.au> Cc: John Polstra <jdp@polstra.com>, current@FreeBSD.ORG Subject: Re: New boot loader and alternate kernels Message-ID: <199810301834.KAA01153@dingo.cdrom.com> In-Reply-To: Your message of "Fri, 30 Oct 1998 10:29:58 PST." <199810301829.KAA01109@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I have a question about the new boot loader. My /boot/boot.conf > > file looks like this: > > > > load /kernel > > autoboot 10 > > > > Now suppose I want to boot an alternate kernel. To do that, it seems > > I have to interrupt the autoboot sequence by pressing a key, then do > > "unload /kernel", then do "boot /kernel.alt". Is that right? It's > > the unload step that I'm wondering about. Can it be avoided? > > Unloading is an all or nothing proposition; it throws everything away > (it doesn't take any arguments). This avoids having holes in the > loaded region, as well as having to deal with dependancy issues. I also forgot to point out that in the more complex case: load /kernel load /modules/foo.ko ... autoboot 10 you could just add unload to the end of the script. There's probably a call for a 'bootmodules' variable as well; until we get more people using this and asking for features I'm not sure what's worth adding and what's just fluff. How many people would be interested in labels and conditional branches, for example? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810301834.KAA01153>