From: Vester Thacker <vester.thacker@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] pc boot and ether drivers
Date: Thu, 18 Nov 2004 13:26:38 +0900 [thread overview]
Message-ID: <32a656c204111720266056314c@mail.gmail.com> (raw)
In-Reply-To: <1285048a44ca7a9d3c339d95924f2745@collyer.net>
On Wed, 17 Nov 2004 18:43:22 -0800, geoff@collyer.net <geoff@collyer.net> wrote:
> The main complication is that the Plan 9 bootstraps also read and
> parse plan9.ini and leave the results in a known place for the loaded
> kernel. I suppose that code could be moved into the kernels.
Couldn't we have a single large kernel with all the
drivers for installation purposes? Could we have
the user build and/or a kernel during the install
process for the type of Plan 9 computer that is
desired rather than the current scheme? Would
this lessen the need for a plan9.ini during the
initial installation bootstrap?
I don't advocate plan9.ini being depreciated, only
that it should not be required initially. IMHO this
might be advantagous considering floppy drives
are obsolete. Sorry if this obfuscates the matter
a bit.
-vester
next prev parent reply other threads:[~2004-11-18 4:26 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
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 [this message]
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=32a656c204111720266056314c@mail.gmail.com \
--to=vester.thacker@gmail.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).