9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nemo@gsyc.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Crazy idea... or a new project?
Date: Fri, 24 Nov 2000 08:37:45 +0000	[thread overview]
Message-ID: <20001124073543.EDFA1199E9@mail.cse.psu.edu> (raw)

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

Another way could be to be able to link the kernel
with device drivers before loading it, and keep
the kernel just with devices used. I think that
could be done by making each driver provide a
(user) program to check if the device is there,
and linking a second kernel depending on what's
there. 



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

[-- Attachment #2.1.1: Type: text/plain, Size: 580 bytes --]

That's a little simplistic.  The x86 is a lousy architecture,
and you're right about the compilers etc.  But all those
lousy drivers, VGAs, USB floppies, it goes on and on.
Are any two the same?  I doubt it.  That's the horror of
PCs, yet is a perhaps unavoidable consequence of the
history that made the PC dominant (c.f. the Mac).

The PC kernel for Plan 9 is huge because of all the drivers
it must have to run on all devices.  Sure we could have
(and perhaps should have) loadable device drivers,
but that is a solution to a problem that shouldn't exist.

-rob


[-- Attachment #2.1.2: Type: message/rfc822, Size: 1463 bytes --]

From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Crazy idea... or a new project?
Date: Thu, 23 Nov 2000 19:05:08 -0500
Message-ID: <20001124000509.EF643199EE@mail.cse.psu.edu>

I don't agree about the x86.
Sure it's an ugly chip.
Sure it and its PC hosts are complicated.
But the bootstrap code and the compiler
are written.  In Plan 9, it's no different
to write applications for the x86 than it
is to write them for any other architecture.

Russ

             reply	other threads:[~2000-11-24  8:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-24  8:37 nemo [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:40 presotto
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
     [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=20001124073543.EDFA1199E9@mail.cse.psu.edu \
    --to=nemo@gsyc.escet.urjc.es \
    --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).