9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Chris Hollis-Locke" <chris@cjl1.demon.co.uk>
To: <9fans@cse.psu.edu>
Subject: [9fans] Startup kernel thoughts
Date: Tue, 13 Nov 2001 23:19:53 +0000	[thread overview]
Message-ID: <004201c16c99$c3504ba0$2248dec2@falken> (raw)
In-Reply-To: <20011113195826.27824199BB@mail.cse.psu.edu>

----- Original Message -----
From: <presotto@closedmind.org>
To: <9fans@cse.psu.edu>
Sent: Tuesday, November 13, 2001 7:58 PM
Subject: Re: [9fans] one reason ideas from Plan 9 didn't catch on


>
> The startup kernel for next release isn't going to fit on a floppy if we
> don't change things.  We're (jmk and I mostly) considering suggestions
> for what to do.

Given load-time driver linkage (I'm not sure of the value of completely
'dynamic' loading) a first step could be a probe that details a manifest
of files to download and put on the install floppy.

In true Plan 9 style, the manifest could be a list of rc commands for
constructing the floppy
(not sure how you'd get them from the target h/w to a p9 box though -
probably write them back to the floppy you ran the probe from)
The probe could be kept up-to-date with the available kernels/drivers, so could
also be used as a "can this hardware run Plan 9?" test program.

The obvious downsides are
* it adds several steps to the install procedure
* individual drivers are fatter, though only the required drivers
  are on the floppy.
* god-knows who would have the time to implement/maintain it!




      parent reply	other threads:[~2001-11-13 23:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 19:58 [9fans] one reason ideas from Plan 9 didn't catch on presotto
2001-11-13 20:14 ` William Josephson
2001-11-13 21:39 ` Mike Haertel
2001-11-13 22:42   ` [9fans] Installation mechanism Jim Choate
2001-11-13 22:54     ` Mike Fletcher
2001-11-13 22:54 ` [9fans] one reason ideas from Plan 9 didn't catch on George Michaelson
2001-11-14  0:19   ` William Josephson
2001-11-13 23:19 ` Chris Hollis-Locke [this message]

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='004201c16c99$c3504ba0$2248dec2@falken' \
    --to=chris@cjl1.demon.co.uk \
    --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).