9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Robert Seaton <seatonr@dupage.edu>
To: 9fans@9fans.net
Subject: [9fans] novel userspace paradigms introduced by plan 9
Date: Sat,  2 Jul 2011 11:15:17 -0500	[thread overview]
Message-ID: <BANLkTin9RO2YeBcNM8gbcNHG7G1xPHH5vA@mail.gmail.com> (raw)

Hello, 9fans!

I'm a GSoC student working on "Plan 9 From Gentoo", a Gentoo project
to create a liveCD that comprises of a Gentoo base-system and a Plan
9-inspired userspace, instead of the typical GNU userspace.

However, I'm new to Plan 9, and I'm wondering if veteran 9'ers have
any suggestions for novel userspace concepts intro'd by Plan 9 that
should be included/documented or that still need to be ported to Linux
from Plan 9. These ideas don't necessarily need to be unique to Plan
9, as long as they are different from the typical GNU/Linux fare.

Some of the things I have discovered so far:
* Drawing windows on the screen via rio and mouse button 2
* Mouse chording
* Sending things via plumber
* Majority of text can be edited (i.e. old commands in the shell, etc)

Thanks,
robb



             reply	other threads:[~2011-07-02 16:15 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02 16:15 Robert Seaton [this message]
2011-07-02 16:23 ` Jacob Todd
2011-07-17 12:37   ` Eugene Gorodinsky
2011-07-17 13:54     ` Charles Forsyth
2011-07-18  8:32       ` Eugene Gorodinsky
2011-07-18 17:14         ` Charles Forsyth
2011-07-19  7:50           ` Eugene Gorodinsky
2011-07-02 16:29 ` dexen deVries
2011-07-02 17:24   ` Jack Johnson
2011-07-02 17:34     ` [9fans] To p9 or not to p9? (was: novel userspace paradigms introduced by plan 9) dexen deVries
2011-07-02 18:23     ` [9fans] novel userspace paradigms introduced by plan 9 Eli Cohen
2011-07-02 18:36       ` dexen deVries
2011-07-02 23:10         ` simon softnet
2011-07-02 23:31           ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-07-03  8:55             ` simon softnet
2011-07-03 11:06         ` Connor Lane Smith
2011-07-03 14:38           ` Iruatã Souza
2011-07-03 22:05             ` Charles Forsyth
2011-07-03 17:57           ` Lyndon Nerenberg
2011-07-03 18:10             ` dexen deVries
2011-07-03 20:44             ` erik quanstrom
2011-07-03 20:53               ` Lyndon Nerenberg
2011-07-03 20:57                 ` erik quanstrom
2011-07-03 21:08                   ` andrey mirtchovski
2011-07-03 21:29                     ` ron minnich
2011-07-03 21:38                       ` andrew zerger
2011-07-03 21:39                         ` andrew zerger
2011-07-03 21:51                       ` andrey mirtchovski
2011-07-17 16:25                     ` Nicolas Bercher
     [not found]         ` <CAMdzYRr4_2JdEXaZ8cg=_9CJYzZr63HtEAtaG6x8WXGrPtp_DQ@mail.gmail.c>
2011-07-03 11:55           ` erik quanstrom
2011-07-03 12:32             ` Connor Lane Smith
     [not found]             ` <CAMdzYRowH+Y3UA4iyPy+4dP-cE064A6XZXvTbB1M-jBypu_ORw@mail.gmail.c>
2011-07-03 12:51               ` erik quanstrom
2011-07-03 13:13                 ` Connor Lane Smith
2011-07-04  6:44 ` Yaroslav
2011-07-04 14:59   ` Robert Seaton
2011-07-16 10:52     ` simon softnet
2011-07-16 19:12       ` David Leimbach
2011-07-16 19:17         ` simon softnet
2011-07-16 19:32           ` Ethan Grammatikidis
2011-07-16 21:10             ` simon softnet
2011-07-17  9:38               ` Ethan Grammatikidis
2011-07-18  9:04       ` Balwinder S Dheeman
2011-07-18  9:30         ` dexen deVries

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=BANLkTin9RO2YeBcNM8gbcNHG7G1xPHH5vA@mail.gmail.com \
    --to=seatonr@dupage.edu \
    --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).