9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: Plan9ish virtual consoles, etc. (was Re: [9fans] First-timer help)
Date: Sat, 30 Jul 2005 10:02:04 -0500	[thread overview]
Message-ID: <a4e6962a0507300802337450dc@mail.gmail.com> (raw)
In-Reply-To: <20050730112540.5de8ae86@localhost.localdomain>

On 7/30/05, Martin C. Atkins <martin_ml@parvat.com> wrote:
> 
> Following our recent discussions about various ways of sharing the
> display amongst logins, I thought Jim Getty's talk at OLS was
> interesting.
> 
> He goes a lot further than I was suggesting, but I couldn't help but
> think how much easier the things he was proposing would be, if he
> could think outside the "X box" (and no, I don't mean the games
> machine :-), and base the infrastructure on Plan 9!
> 
> Perhaps if Plan 9 were shown to trivially do these things (without,
> for example, having to put user identities and SELiniux-like
> facilities into the X server! Yes, really! Yuk!), it would be
> (another) example of Plan 9's superiority.
> 

I talked to Jim directly about this.  He's very pro-plan 9 and talked
about Rob's influence on the Xrender extensions.  He also spoke in
vocal support of unlocking Linux's private namespaces as a key
component of this stuff.  I pointed him at the v9fs stuff and also
told him about Plan9ports, which he was pretty excited about --
particularly when he heard venti was now part of it.

      -eric


  reply	other threads:[~2005-07-30 15:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-30  5:55 Martin C. Atkins
2005-07-30 15:02 ` Eric Van Hensbergen [this message]
2005-07-30 16:19   ` Martin C. Atkins
2005-07-30 18:48     ` Eric Van Hensbergen

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=a4e6962a0507300802337450dc@mail.gmail.com \
    --to=ericvh@gmail.com \
    --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).