From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs kernel: eagle
Date: Thu, 9 Nov 2000 02:05:25 -0500 [thread overview]
Message-ID: <20001109070527.BFA6A199E3@mail.cse.psu.edu> (raw)
(I also believe that there could be a slight distinction between kernels intended
for CPU servers and kernels meant for terminals. While enterprise CPU servers
are probably not going to need devices like VGA and sound, they should
be given the opportunity to be free of them, terminals, on the other hand,
might need some of the multimedia drivers.
Although, as Jim points out, you are quite right overall,
this part we already do: see the differences between
/sys/src/9/pc/pcdisk and /sys/src/9/pc/pccpu.
Russ
next reply other threads:[~2000-11-09 7:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 7:05 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 14:24 presotto
2000-11-09 7:00 jmk
2000-11-09 8:17 ` Christopher Nielsen
2000-11-09 8:21 ` Christopher Nielsen
2000-11-07 15:31 jmk
2000-11-08 9:22 ` Jakub Jermar
2000-11-08 12:54 ` Boyd Roberts
2000-11-07 9:28 Jakub Jermar
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=20001109070527.BFA6A199E3@mail.cse.psu.edu \
--to=rsc@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).