9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Georg Lehner <jorge-plan9@magma.com.ni>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9pm/Plan 9 kernel in user space
Date: Thu, 19 Oct 2006 01:05:48 +0200	[thread overview]
Message-ID: <87wt6x9qcz.fsf@jorgito.magma.com.ni> (raw)
In-Reply-To: <ee9e417a0610171724u1ca1d1d2u6ecaf2d5d7a31f6a@mail.gmail.com> (Russ Cox's message of "Tue, 17 Oct 2006 20:24:39 -0400")

"Russ Cox" <rsc@swtch.com> writes:
...
> You'd be better off just porting fossil (venti is ported)
> to the current Plan 9 from User Space, which does
> not depend on a central user-space kernel.
...

Running fossil+venti on a Linux Kernel surely is an interresting
alternative: more efficient then my first idea, plus the same benefit:
lots of hardware drivers not supported in Plan 9.

The idea of Plan 9 in userspace still attracts me for several reasons:
- running Plan 9 alongside my Linux Desktop with reasonable speed
- running CPU and Auth servers on Linux Servers with otherwise small
  workload=20
- doing same thing under Windows, eventually starting under Cygwin

 I'll look into drawterm.


Charles Forsyth <forsyth@terzarima.net> writes:

>>"cl"? (Under Windows, you might expect your compiler to be called "cl.exe")
>
> plain cl is fine: it's just  not in his search path
> or perhaps not even on his machine

cl is not on my machine, where may I be able to get it from?

Thanks and

Regards,

        Jorge-León


  reply	other threads:[~2006-10-18 23:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 23:31 jorge-plan9
2006-10-18  0:08 ` Andrew Simmons
2006-10-18  7:34   ` Charles Forsyth
2006-10-18  0:24 ` Russ Cox
2006-10-18 23:05   ` Georg Lehner [this message]
2006-10-18 23:13     ` Russ Cox
2006-10-19  9:06     ` Richard Miller
2006-10-19  9:50     ` C H Forsyth
2006-10-19 20:13 ` Sascha Retzki
2006-10-19 20:39   ` Richard Bilson
2006-10-19 22:21   ` Charles Forsyth
2006-10-19 16:06 Richard Miller

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=87wt6x9qcz.fsf@jorgito.magma.com.ni \
    --to=jorge-plan9@magma.com.ni \
    --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).