From: "Corey" <corey_s@qwest.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] this is not an advocacy question
Date: Fri, 26 May 2006 01:48:22 -0700 [thread overview]
Message-ID: <200605260148.22511.corey_s@qwest.net> (raw)
In-Reply-To: <ba8bf2d7794053b740e56f5b72f10898@collyer.net>
On Friday 26 May 2006 00:16, geoff@collyer.net wrote:
> Inferno and Plan 9 kernels are similar, having common
> ancestry.
>
So Inferno and Plan 9 kernels are both forks from a common source?
How far have the two divurged? Do/can they share device drivers?
( Also, are there any design white-papers/documents that explain or
discuss the kernel implementations/concepts? ( similar to what is
available for the, say, L4 kernels ) )
> Both systems use essentially 9P2000 as their
> network filesystem protocol.
>
Is it accurate to say that "Styx" is a conformant implementation
of 9fs2000 that is written in Limbo rather than C? ( similar to v9fs
under linux? )
> If you want to write in Limbo, you have to run Inferno, but you can
> run Inferno on (l)unix, Windows or Plan 9. If you want to write
> applications in C, you can't use Inferno.
>
Aside from the considerable portability provided by Inferno via the
Dis virtual-machine, are there any other obvious/compelling
reasons for choosing to develop in Limbo?
After doing quite a bit of reading, I get the general notion that the
primary functional difference between plan9 and inferno consists in a
choice/requirement of portability vs. language.( ie Inferno/Limbo vs.
Plan9/C )
I'm wondering whether Inferno's current requirement of a new/"obscure"
language (limbo) as its sole development platform hindered wider usage.
i.e., I'm curious as to how many deployments resulted in Plan 9 over
Inferno specifically due to language ( C vs Limbo )
considerations/requirements/preference.
The point of all this, is that - aside from sheer interest in the nuances of
these two operating environments - I've hit a point in my own independent
evaluations of Plan 9 and Inferno, that I'm unable to decide where best to
focus my future learning/experimentation - Plan 9 or Inferno.
Since I lack any practical experience under either OS -- it's not a matter
of "install them both and see which you like better", such as the case would
be with, say, two Linux distributions -- I'm hoping to get some further info
from an experienced/knowledgable forum.
Thanks for your time!
next prev parent reply other threads:[~2006-05-26 8:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 7:10 Corey
2006-05-26 7:16 ` geoff
2006-05-26 8:48 ` Corey [this message]
2006-05-26 9:17 ` geoff
2006-05-26 14:29 ` rog
2006-05-26 17:39 ` David Leimbach
2006-05-30 11:02 ` rog
2006-05-30 15:06 ` David Leimbach
2006-05-30 15:14 ` rog
2006-05-30 16:26 ` David Leimbach
2006-05-30 16:36 ` Gabriel Diaz
2006-05-30 17:08 ` David Leimbach
2006-05-30 17:19 ` rog
2006-05-30 23:37 ` LiteStar numnums
2006-06-01 16:32 ` rog
2006-06-01 16:50 ` David Leimbach
2006-05-27 20:08 ` Corey
2006-05-26 9:51 Fco. J. Ballesteros
2006-05-26 15:16 ` Latchesar Ionkov
2006-05-26 15:53 ` Skip Tavakkolian
2006-05-26 17:03 ` Latchesar Ionkov
2006-05-26 18:23 ` Roman Shaposhnick
2006-05-26 18:48 ` Francisco J Ballesteros
2006-05-26 19:00 ` Skip Tavakkolian
2006-05-31 3:19 ` Roman Shaposhnik
2006-05-26 17:32 erik quanstrom
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=200605260148.22511.corey_s@qwest.net \
--to=corey_s@qwest.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).