From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Glendix?
Date: Tue, 13 Nov 2007 08:00:07 -0500 [thread overview]
Message-ID: <e5f46d62b0e0d33521d64523cb8752c2@quanstro.net> (raw)
In-Reply-To: <473980C6.4040009@kix.in>
> Hi,
>
> > so you might get more hardware support, but you'd lose all the userspace
> > code, so would it really end up that much more capable?
>
> I don't understand what "lose all the userspace code" means. The
> objective of the exercise is to enable Plan 9's userspace to work
> unmodified on Linux.
>
> It boils down to Linux's drivers/schedulers/et.al. but Plan 9's
> programming environment. You'd still use /net to do network programming,
> use libdraw and not X, so to the programmer the fact that the
> distribution is running the Linux kernel is not known.
>
> Performance-wise, I see how it would be a bad idea; since read/write to
> /net will ultimately result in a socket-like call, so there would be a
> overhead.
>
> --
> Anant
what an unholy marrage!
what happens when you're tracking a bug? do you give up when
it enters linux? how do you configure hardware if you're not
going to use the linux machinery?
why are linux schedulers interesting?
i think that rather than the best of both worlds, you'd end up
with the worst of both. all the joys of linux administration and
yet no (insert favorite browser here).
- erik
next prev parent reply other threads:[~2007-11-13 13:00 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 9:28 Anant Narayanan
2007-11-13 10:05 ` Gorka Guardiola
2007-11-13 10:14 ` Uriel
2007-11-13 10:33 ` Gorka Guardiola
2007-11-13 14:25 ` David Leimbach
2007-11-14 0:51 ` Alexander Sychev
2007-11-13 21:37 ` Joel C. Salomon
2007-11-13 10:17 ` Charles Forsyth
2007-11-13 10:39 ` roger peppe
2007-11-13 10:47 ` Anant Narayanan
2007-11-13 12:18 ` Uriel
2007-11-13 13:00 ` erik quanstrom [this message]
2007-11-13 13:31 ` Uriel
2007-11-13 13:47 ` roger peppe
2007-11-13 14:10 ` sqweek
2007-11-13 13:54 ` Charles Forsyth
2007-11-13 15:20 ` Anant Narayanan
2007-11-13 18:23 ` Bakul Shah
2007-11-13 14:26 ` erik quanstrom
2007-11-13 16:49 ` Uriel
2007-11-13 17:19 ` erik quanstrom
2007-11-13 17:24 ` Iruata Souza
2007-11-13 22:01 ` David Leimbach
2007-11-13 15:16 ` Anant Narayanan
2007-11-13 14:29 ` Anant Narayanan
2007-11-13 17:21 ` erik quanstrom
2007-11-13 21:41 ` Joel C. Salomon
2007-11-13 13:30 ` John Stalker
2007-11-13 15:35 ` Harri Haataja
2007-11-13 16:22 ` John Stalker
2007-11-13 16:43 ` Aki Nyrhinen
2007-11-13 16:39 ` Uriel
2007-11-13 16:46 ` Iruata Souza
2007-11-13 18:02 ` Charles Forsyth
2007-11-13 18:12 ` Iruata Souza
2007-11-13 22:04 ` David Leimbach
2007-11-13 22:16 ` David Leimbach
2007-11-13 23:19 ` Iruata Souza
2007-11-14 2:23 ` R
2007-11-14 11:44 ` Iruata Souza
2007-11-14 12:17 ` R
2007-11-14 12:40 ` Christian Kellermann
2007-11-14 13:01 ` R
2007-11-14 13:08 ` Christian Kellermann
2007-11-13 17:48 ` John Stalker
2007-11-13 16:26 ` Russ Cox
2007-11-13 16:42 ` Charles Forsyth
2007-11-13 17:44 ` Latchesar Ionkov
2007-11-14 5:44 ` ron minnich
2007-11-16 8:42 ` [9fans] Nine4Linux [WAS: Glendix?] Enrico Weigelt
2007-11-16 10:20 ` erik quanstrom
[not found] ` <1b69251dfdcb6b8022ff78767f07ce86@quanstro.net>
2007-11-22 18:01 ` Enrico Weigelt
2007-11-22 22:00 ` Paweł Lasek
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=e5f46d62b0e0d33521d64523cb8752c2@quanstro.net \
--to=quanstro@quanstro.net \
--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).