Date: Sat, 16 Oct 1999 16:45:13 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: Alexey Zelkin <phantom@cris.net> Cc: Bill Swingle <unfurl@dub.net>, current@FreeBSD.ORG Subject: Re: boot2 problem Message-ID: <38082D09.93BC86A6@newsguy.com> References: <19991014171747.A11382@scorpion.crimea.ua> <199910150757.AAA00979@dingo.cdrom.com> <19991015114556.A7776@scorpion.crimea.ua> <19991015030944.A93974@dub.net> <19991015132017.A19180@scorpion.crimea.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexey Zelkin wrote: > > > It's pretty consistant with other OS's boot prompt. > Ok, I see that I'll not get answer to my question except "do it otherwise". Actually, you got an answer, though you might have missed it. Boot2 does not have "/kernel" as default, but "/boot/loader". Thus, even if we did identify -v as a "parameter" and passed it to what is being loaded, it would be the loader that receives it. Alas, we just don't have a lot of space for boot2, and we'd rather not spend it on things like that. Rather, we decided to keep boot2 simple, and transfer all niceties to a new stage, the loader. Loader is fully featured, has an extended help, and includes a complete structured programming language. We can't fit all of this into boot2, obviously. And if we decided to add "just this feature" to boot2, where would we draw the line? As the requirements for the boot stage increase, so will boot2. It happened before, and that's why we now have a three stage loader. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" 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?38082D09.93BC86A6>