From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 != Inferno... right?
Date: Thu, 20 Nov 2008 17:55:28 +0000 [thread overview]
Message-ID: <112020081755.2769.4925A49000066BD800000AD122230682229B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net> (raw)
In-Reply-To: <fc1f12e60811200945j621b8003m9365eb9fab33fba7@mail.gmail.com>
> I'm just about ready to take the plunge (again) into Plan 9 for file
Welcome to the pool. The water's great.
> started to get the impression that Inferno is perhaps a better way to
> go for a newbie like me to the whole rio/acme/fossil Way. Is this
> mistaken?
For rio/acme/fossil, you do want to go Plan 9 and not
Inferno. Inferno's windowing system isn't rio, but acme
is there. Unless I'm out of the loop on something,
there isn't a fossil port to Inferno, though I think
there's a venti port.
> They don't appear to be the same thing, and searching the
> last six months of archives show that there isn't a lot of Inferno
> talk here.
That's partly because there's a separate Inferno list. And
you're right that they're not the same, but are closely
related. The original Inferno kernel was based on (and
used code from, I think) the Plan 9 kernel that was current
at the time. So as you might guess there are a lot of
design elements that are common. But at the same time,
there are a lot of pretty major differences. I'd say
they're both worth diving into.
BLS
next prev parent reply other threads:[~2008-11-20 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 17:45 Tod Beardsley
2008-11-20 17:55 ` Brian L. Stuart [this message]
2008-11-20 18:47 ` Roman V. Shaposhnik
2008-11-20 19:23 ` Brian L. Stuart
2008-11-20 20:28 ` a
2008-11-20 21:05 ` Brian L. Stuart
2008-11-20 22:54 ` Tod Beardsley
2008-11-21 0:07 ` David Leimbach
2008-11-20 18:02 ` a
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=112020081755.2769.4925A49000066BD800000AD122230682229B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net \
--to=blstuart@bellsouth.net \
--cc=9fans@9fans.net \
/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).