From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pc boot and ether drivers
Date: Wed, 17 Nov 2004 23:53:23 -0500 [thread overview]
Message-ID: <90434074e615c95c1ad55afb9f6687eb@plan9.bell-labs.com> (raw)
In-Reply-To: <ee9e417a041117200113ea6134@mail.gmail.com>
On Tue, 16 Nov 2004 21:11:42 -0500, jmk@plan9.bell-labs.com
<jmk@plan9.bell-labs.com> wrote:
> It's mostly historic and most of the reasons have gone away.
> Sharing code with the current 9load code would be more trouble
> than it's worth. There are ideas for doing a better job by
> rewriting the bootstrap altogether, but who knows if/when it
> will ever be done.
By 'rewriting the bootstrap altogether' I would make it go away
altogether and use the kernel to boot another kernel. We can do this
already but some of the details are a bit messy and a tidy up and
re-organisation would be a good idea; this is likely to fall out
of something else I hope to be doing soon. How you get the first
(bootstrap) kernel into memory could be the same as now, using
whatever methods you like - Plan 9 MBR/PBS, Grub, LILO, LinuxBIOS,
PXE, whatever.
On Wed Nov 17 20:29:00 EST 2004, ericvh@gmail.com wrote:
> ...
> We have enough to do without having to worry about
> writing boot loaders.
>
> -eric
Agreed.
On Wed Nov 17 23:01:38 EST 2004, russcox@gmail.com wrote:
> the boot process is crappy enough.
> let's not make it crappier.
Agreed.
--jim
next prev parent reply other threads:[~2004-11-18 4:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 1:55 Tim Newsham
2004-11-17 2:09 ` geoff
2004-11-17 2:11 ` jmk
2004-11-18 0:54 ` Vester Thacker
2004-11-18 1:28 ` Eric Van Hensbergen
2004-11-18 2:32 ` Karl Magdsick
2004-11-18 2:43 ` geoff
2004-11-18 3:09 ` Tim Newsham
2004-11-18 3:16 ` geoff
2004-11-18 3:54 ` Tim Newsham
2004-11-18 4:01 ` Russ Cox
2004-11-18 4:53 ` jmk [this message]
2004-11-18 6:04 ` Vester Thacker
2004-11-18 10:39 ` C H Forsyth
2004-11-18 11:45 ` Vester Thacker
2004-11-18 7:10 ` geoff
2004-11-18 4:16 ` bs
2004-11-18 3:40 ` Russ Cox
2004-11-18 4:26 ` Vester Thacker
2004-11-18 4:34 ` Vester Thacker
2004-11-18 16:23 ` Ronald G. Minnich
2004-11-18 15:08 ` Ronald G. Minnich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=90434074e615c95c1ad55afb9f6687eb@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).