9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Crazy idea... or a new project?
Date: Fri, 24 Nov 2000 17:40:17 -0500	[thread overview]
Message-ID: <20001124224019.301B219A18@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

I seem to be missing messages from this stream so
excuse me if this has already been suggested:

I guess it depends on what problem you are trying to
solve.  We have lots (> 100) of systems that boot off
of LAN's.  We end up with kernels stuffed full of
drivers because otherwise, we'ld have to keep a database
lying around somewhere for each system and spend time
making lots of kernels each time we change something.
Granted we could write enough software to make this
painless, but it's one more thing to screw up.

I was actually fond of an idea I've heard from Rob or
Ken, can't remember which.  To address the problem, he
suggested the dhcp daemon link the kernel on the fly.
It could use a hardware vector passed in the dhcp request
(generated from plan9.ini perhaps) and return the file
name of the result so that the system could tftp it over.

Unfortunately, I find this all a lot less of a problem than
figuring out what IRQ's and IO ports to assign devices or that
of getting a new VGA board working.

[-- Attachment #2: Type: message/rfc822, Size: 2314 bytes --]

From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Crazy idea... or a new project?
Date: Fri, 24 Nov 2000 23:24:09 +0100
Message-ID: <01e701c05665$44417500$0ab9c6d4@cybercable.fr>

From: Scott Schwartz <schwartz@bio.cse.psu.edu>

> Just to digress for a moment, I've never liked the idea of loadable
> device drivers, because they seeem like such a stopgap measure.

maybe you could 'plumb' them.  after boot the kernel gets
handed up a file with rules/whatever to load device drivers
based on interrupts or other device ready 'events'.

i was thinking about digital uda-50 interfaces.  you could
just plug 'em in and ultrix would autoconf them at run
(ie. any) time.  of course, the driver was already loaded.

probably hard to generalise, but it might work out.


             reply	other threads:[~2000-11-24 22:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-24 22:40 presotto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-27  2:36 okamoto
2000-11-27  6:16 ` Boyd Roberts
2000-11-27  8:21   ` Andy Newman
2000-11-24 23:47 rob pike
2000-11-24 23:52 ` Boyd Roberts
2000-11-25 18:52 ` Fariborz 'Skip' Tavakkolian
2000-11-24 22:16 rob pike
2000-11-24 19:05 rob pike
2000-11-24 21:06 ` Francisco J Ballesteros
2000-11-24 21:28   ` Boyd Roberts
2000-11-24 23:37     ` Francisco J Ballesteros
2000-11-24 23:40       ` Boyd Roberts
2000-11-25  1:57         ` Francisco J Ballesteros
2000-11-24  8:37 nemo
     [not found] <rob@plan9.bell-labs.com>
2000-11-24  0:41 ` rob pike
2000-11-24  0:48   ` Boyd Roberts
2000-11-24 22:13   ` Scott Schwartz
2000-11-24 22:24     ` Boyd Roberts
2000-11-24  0:05 Russ Cox
2000-11-24  0:08 ` Boyd Roberts
2000-11-23 13:25 Andrew Zubinski
2000-11-23 22:51 ` Richard
2000-11-23 22:55 ` Boyd Roberts

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=20001124224019.301B219A18@mail.cse.psu.edu \
    --to=presotto@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).