9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] What makes Plan 9 unique?
Date: Thu, 25 Oct 2001 11:36:36 +0200	[thread overview]
Message-ID: <20011025113635.V2648@cackle.proxima.alt.za> (raw)
In-Reply-To: <9r783d$s5l$1@newpoisson.nosc.mil>; from Matt Senecal on Thu, Oct 25, 2001 at 09:00:24AM +0000

On Thu, Oct 25, 2001 at 09:00:24AM +0000, Matt Senecal wrote:
> 
> What makes Plan 9 truly unique? What about it makes it better than Solaris,
> or other UNIX systems?
> 
I've been toying with lib9p over the past week and a lot of what
seemed an extremely handy but very remote paradigm (from the
developer's perspective, as a user I accepted it as a given) suddenly
took on a very concrete mantle.

If that doesn't do it, I also tried remote debugging of a Limbo
program on Inferno with mixed results (not being much of a debugger
freak).  The equivalent operation with acid over a network ought to
impress developers.  Even if done in two distinct rio windows.

> Imagine you're going to be giving the presentation to a bunch of long-time
> computer users whose main attitude going into the meeting is going to be:
> "Nice lines, but so what? Why should I consider Plan 9?"
> 
I wouldn't try that approach.  Perhaps "what can I learn from Plan 9?"
I was thrilled when I read the very old papers, without a clue about
the system itself.

> I understand that I'm going to be learning a lot of this on my own in the
> coming weeks, but I wanted to make sure that there wasn't some cool feature
> that I missed. There's only so much you can learn on a standalone system
> (although I may be networking with an old donated '486 if I can find some
> NICs).

Most of my Plan 9 network is '486s with NE2000s.  Not great, but
workable.  And very stable.  I was getting fileserver freezes which
were resolved (I don't know why) when I took the SCSI disk out and
reconnected all its cabling.  In all other respects, it seems totally
maintenance free.  Note that this is a hybrid of Second and Third
edition Plan 9, not yet up to date as regards releases.

++L


  reply	other threads:[~2001-10-25  9:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25  9:00 Matt Senecal
2001-10-25  9:36 ` Lucio De Re [this message]
2001-10-26  9:25   ` Douglas A. Gwyn
2001-10-26 14:03     ` Matt Senecal
2001-10-26 15:36 ` Borja Marcos
2001-10-25 11:56 Russ Cox
2001-10-26  9:25 ` Douglas A. Gwyn
2001-10-26 15:01 Russ Cox
2001-10-26 16:48 ` Thomas Bushnell, BSG
2001-10-29  9:04 ` pac
2001-10-26 16:58 presotto
2001-10-29 10:16 ` Ozan Yigit
2001-10-29 20:54   ` Skip Tavakkolian
2001-10-30 16:50   ` Dan Cross
2001-10-26 17:09 forsyth
2001-10-29  1:56 okamoto
2001-10-29 13:07 bwc
2001-10-29 18:54 presotto
2001-10-29 20:54 David Gordon Hogan
2001-10-29 21:28 David Gordon Hogan
2001-11-05 14:59 ` Jonadab the Unsightly One
2001-11-06 10:22   ` Jonadab the Unsightly One
2001-11-05 22:14 David Gordon Hogan
2001-11-06 10:22 ` Jonadab the Unsightly One
2001-11-06 11:01 geoff
2001-11-06 16:45 Russ Cox
2001-11-06 17:53 ` Thomas Bushnell, BSG
2001-11-06 18:28   ` William Josephson
2001-11-07  2:46 ` Boyd Roberts
2001-11-06 17:08 anothy
2001-11-07  1:02 David Gordon Hogan
2001-11-07  6:34 Russ Cox

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=20011025113635.V2648@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).