9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jacob Todd <jaketodd422@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] So, why Plan 9?
Date: Tue, 12 Oct 2010 08:24:27 -0400	[thread overview]
Message-ID: <AANLkTind1z61QduMPewKOtoimv99=nwDXswro-1Sv8GK@mail.gmail.com> (raw)
In-Reply-To: <i9025v$n7d$1@news2.carnet.hr>

[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]

There's APE, the Ansi Posix Environment.
On Oct 12, 2010 4:40 AM, "Aleksandar Kuktin" <akuktin@gmail.com> wrote:
> On Mon, 11 Oct 2010 13:45:02 +0000, Bruce Ellis wrote:
>
>> Very succinct, and better than I could do 'til the coffee kicks in.
>>
>> You could have pointed out that the entire source tree is smaller than
>> the gcc manual.
>
> WAT!?!
>
> Ahem.. pardon my manners please, but this caught me completely of guard.
>
> I learned of Plan 9's existence a few years back, when I was finishing my
> Linux from scratch and was out looking if there is a way to get something
> even better than a Linux. I've been lurking in this group for quite a
> while now, hoping to maybe find some easy way to merry the two systems.
>
> Speaking of which, is there a way to do the opposite of "Plan 9 in
> userspace"? That is, a way to use Unix-specific programs and libraries on
> Plan 9?
>
> Basically, this is what has been holding me back. I would like to switch
> to Plan 9, but still have all of my Linux programs and libraries
> available. I also dread using any virtualizators, QEMUs, Xens and other
> stuff; not because I find them hard to use, but because I don't want to
> waste CPU cycles on compatibility layers.
>
> Is there already an implemented.. POSIX compatibility layer, library, or
> something? Hopefully, something that is very, very thin??
> Maybe?
>

[-- Attachment #2: Type: text/html, Size: 1739 bytes --]

  parent reply	other threads:[~2010-10-12 12:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11  9:05 Mark Carter
2010-10-11 10:23 ` Sergey Zhilkin
2010-10-11 11:07 ` Robert Raschke
2010-10-11 11:17   ` Robert Raschke
2010-10-11 11:53     ` Nick LaForge
2010-10-11 13:39       ` Bruce Ellis
2010-10-11 14:45         ` ron minnich
2010-10-11 15:01         ` Karljurgen Feuerherm
2010-10-12  8:33       ` Aleksandar Kuktin
2010-10-12  8:51         ` Max E
2010-10-12 14:47           ` David Leimbach
2010-10-12 11:25         ` Steve Simon
2010-10-12 12:24         ` Jacob Todd [this message]
2010-10-12 16:04         ` Aleksandar Kuktin
2010-10-11 18:43     ` Brian L. Stuart
2010-10-12  8:17       ` Anssi Porttikivi
2010-10-12 14:09         ` Mark Carter
2010-10-12 14:53           ` Steve Simon
2010-10-12 14:59             ` David Leimbach
2010-10-12  9:06 ` Max E
2010-10-12  9:29   ` yy

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='AANLkTind1z61QduMPewKOtoimv99=nwDXswro-1Sv8GK@mail.gmail.com' \
    --to=jaketodd422@gmail.com \
    --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).