From: William Josephson <jkw@eecs.harvard.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] linux and plan 9 ports.
Date: Wed, 19 Jan 2005 20:22:33 -0500 [thread overview]
Message-ID: <20050120012233.GF59585@mero.morphisms.net> (raw)
In-Reply-To: <3122eaf9ac0e6310ce949954e38a2456@terzarima.net>
On Wed, Jan 19, 2005 at 01:47:31AM +0000, Charles Forsyth wrote:
> >>By the way what is the major motivation when you all updated from
> >>2.4.xyz to 2.6.xyz? Sorry, off topic!
>
> oh no! i forgot one of the more compelling ones:
> - a scheduler that might not be completely hopeless
Have they finally fixed it a bit? Last I tried
to run any number of threads on a Linux box it
nearly died on me.
next prev parent reply other threads:[~2005-01-20 1:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 17:07 Noah Evans
2005-01-18 19:11 ` Bruce Ellis
2005-01-18 19:25 ` Ronald G. Minnich
2005-01-19 1:38 ` Kenji Okamoto
2005-01-19 1:37 ` Charles Forsyth
2005-01-19 1:47 ` Charles Forsyth
2005-01-19 4:13 ` Ronald G. Minnich
2005-01-20 1:22 ` William Josephson [this message]
2005-01-19 4:12 ` Ronald G. Minnich
2005-01-20 1:20 ` William Josephson
2005-01-20 1:16 ` William Josephson
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=20050120012233.GF59585@mero.morphisms.net \
--to=jkw@eecs.harvard.edu \
--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).