9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] [9fans ] What's the best access method to Plan9 from Linux
Date: Fri,  8 Feb 2008 15:33:04 +0000	[thread overview]
Message-ID: <020820081533.28502.47AC763000019F5600006F5622230703629B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net> (raw)

> That makes me think that if there was a C to dis compiler, a full
> plan9 fs (with its /dis/bin, /dis/lib) could be used from inferno.
> Probably, as usual, many people know the reasons of not having such a
> compiler. I don't. :)

That's really two questions:
1) Why no C to dis?  There are a lot of reasons why C is
not a good fit to dis or to Inferno, for that matter,
not the least of which is C's ability to take the address
of an arbitrary object (not in the OO sense, but saying
thing all the time gets old).  Between that and the ability
to cast between integers and pointers, it's pretty much
impossible to do all your memory management with reference
counts and garbage collection, and Inferno doesn't have
a system call for arbitrary memory allocation.  There is,
however, a C to Limbo translator.  It doesn't do a complete
translation, but it takes care of a fair amount of the
tedious stuff and leaves you with some Limbo you can then
clean up.

2) I'm not quite sure what you mean by a full plan9 fs.
Do you mean like kfs or fossil/venti?  If so, then Inferno
does have its own version of kfs.  It can exist in another
file or on a disk partition quite happily.  It doesn't
do write buffering at the moment, so it can be a little
slow, especially during an install, but it does seem to
work pretty well.  In fact, if you're sufficiently bored
and a danger seeker, you can try my ISO image for a native
install.  It's a bootable CD image that will do an install
onto a disk and leave you with a system that will boot
straight into Inferno.  Be forewarned, there are a number
of limitations to the installation scripts that I haven't
had time to work on.  But if you want to give it a try,
check out http://umdrive.memphis.edu/blstuart/htdocs/inf_nat_inst.html

BLS


             reply	other threads:[~2008-02-08 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 15:33 Brian L. Stuart [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-08  9:13 Hongzheng Wang
2008-02-08  9:28 ` Uriel
2008-02-08  9:43   ` Lluís Batlle
2008-02-08 10:14 ` Gorka Guardiola
2008-02-08 10:35   ` Hongzheng Wang

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=020820081533.28502.47AC763000019F5600006F5622230703629B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net \
    --to=blstuart@bellsouth.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).