From: Joel Salomon <salomo3@cooper.edu>
To: 9fans@cse.psu.edu
Cc: "Eric S. Raymond" <esr@thyrsus.com>
Subject: Re: [9fans] book chapters
Date: Fri, 27 Jun 2003 18:08:13 -0400 [thread overview]
Message-ID: <Pine.SUN.3.90.1030627173421.29163A-100000@magnum.cooper.edu> (raw)
In-Reply-To: <001601c33c91$249f4cd0$2a8be793@gli.cas.cz>
On Fri, 27 Jun 2003, pac wrote:
> folks!
> i'd like to hear your comments on these:
>
> http://catb.org/~esr/writings/taoup/html/plan9.html
like matt said.
> http://catb.org/~esr/writings/taoup/html/ch20s03.html
>
> regards,
> ++pac.
I may not be the best person to do this but...
* A Unix File is Just a Big Bag of Bytes
Plan 9 keeps this model, but avoids *some* of the problems esr points out
- I'll mention these is turn
* Unix Support For GUIs Is Weak.
Rio. Acme. It's not the "point and drool" of the macintosh, but is
internally consistent, convenient once you get used to it, and *very
well* integrated into the resr of the system, especially since many
"interesting" services (tcp/ip, mail, ftp, cd writing, etc.) implement
the file system interface
* File Deletion Is Forever
File Creation Is Forever :-)
* Unix Assumes a Static File System
I'm out of my depths here - anyone able to answer this?
* The Design of Job Control was Badly Botched
Rio. 'nuff said.
* The Unix API Doesn't Use Exceptions
http://groups.google.com/groups?dq=&hl=en&lr=&ie=UTF-8&frame=right&th=7d07c12c4a19c45e&seekm=bf8367f8234d6dcb8847b6fd73d7f020%40plan9.escet.urjc.es
or search for "exception" on comp.os.plan9 where this subject has been
discused ad nauseum
* ioctl(2) and fcntl(2) are an embarrassment
That's why Plan9 doesn't have them!
* The Unix Security Model May Be Too Primitive
Plan 9 dosn't have a superuser account, but has anyone found the lack of
ACLs limiting?
* Unix has Too Many Different Kinds of Names
And he gives plan9 credit for unifying them. (but he mentions per-user
dynamically adjustable namespaces - I'm sure he was in error here, but
*is* there a way to simultaneously adjust the namespace of *all* my
processes? Perhaps with nemo's redirfs & badsrv underneath everything...)
* File Systems Might Be Considered Harmful
Then he goes on to say that "no major production operating system has
yet followed EROS's lead".
* Towards A Global Internet Address Space
Yup, we've got that too. In fact the model esr proposes is... Plan 9!
Did I leave anything out?
--Joel
next prev parent reply other threads:[~2003-06-27 22:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 9:47 pac
2003-06-27 10:22 ` matt
2003-06-27 22:08 ` Joel Salomon [this message]
2003-06-27 22:12 ` Geoff Collyer, geoff
2003-06-27 23:39 ` boyd, rounin
2003-06-28 1:03 ` Scott Schwartz
2003-06-28 2:10 ` Dan Cross
2003-06-28 2:27 ` Dan Cross
2003-06-29 17:55 ` Jack Johnson
2003-06-30 11:17 ` matt
2003-06-30 13:43 ` ron minnich
2003-06-30 14:02 ` matt
2003-06-30 16:56 ` Jack Johnson
2003-06-30 17:16 ` boyd, rounin
2003-06-30 17:19 ` ron minnich
2003-06-30 17:24 ` ron minnich
2003-06-30 17:29 ` boyd, rounin
2003-06-30 18:40 ` rog
2003-06-30 23:16 ` Kenji Arisawa
2003-06-30 23:24 ` boyd, rounin
2003-07-01 1:44 ` David Presotto
2003-07-01 11:27 ` Kenji Arisawa
2003-07-01 11:32 ` David Presotto
2003-07-01 9:51 ` matt
2003-06-27 22:36 ` William Ahern
2003-06-27 22:28 Joel Salomon
2003-06-27 22:26 ` Geoff Collyer, geoff
2003-06-27 23:43 ` boyd, rounin
2003-06-27 23:46 ` Geoff Collyer, geoff
2003-06-28 0:53 ` Dennis Ritchie
2003-06-28 17:44 A. Baker
2003-06-29 4:38 ` Dennis Ritchie
2003-06-30 18:17 Richard C Bilson
2003-07-01 17:48 A. Baker
2003-07-02 0:27 ` Dennis Ritchie
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=Pine.SUN.3.90.1030627173421.29163A-100000@magnum.cooper.edu \
--to=salomo3@cooper.edu \
--cc=9fans@cse.psu.edu \
--cc=esr@thyrsus.com \
/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).