9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] So What is P9 good for.....
Date: Fri, 14 Feb 2003 19:27:32 -0800	[thread overview]
Message-ID: <449b922076a2122f384b55b3e3f1aead@collyer.net> (raw)
In-Reply-To: <98b94a6949552dc3aa03d60ef4d245ef@plan9.bell-labs.com>

Yes, one can cite individual complaints about 6th edition, but my
point was that in 1975 or 1976, compared to the other systems of the
day, Unix *seemed* *to me*, as a user, virtually free of arbitrary
limits.

I could create directories beneath my home directory to a depth
greater than 6 (unlike, say, TOPS-10 and perhaps, later, VMS), indeed
to arbitrary depth (yes, I'd run the file system out of blocks or
i-nodes eventually, but at least the system didn't pick a
pseudo-random constant like `6').  I could create files with names
that weren't 6+3 upper-case alphanumerics, unlike most, if not all,
DEC operating systems and others influenced by them.  14 (ASCII)
characters per component seemed most generous and I can't recall
needing more.  The exec argument limit was an implementation artifact
of a small machine, and has been increased repeatedly over the years,
unlike the limits mentioned above, which couldn't be changed without
harming binary compatibility with existing programs.  8-bit userids
were a result of parsimonious choice of the `char' data type on a
small machine, not somebody saying `Let's limit the number of users to
169 just to be arbitrary and a pain', and the size of userids has been
increased over the years.

Reading through section II of the 6th edition manual (the system call
interface), about the only arbitrary limits (perhaps I should say
capricious; those that are not just a consequence of the size of some
data type) that I can see are the maximum number of open files per
process and, arguably, various output delays in STTY(II).  This was
not true of the system call interfaces of most other systems of the
day (not to mention programming language implementations), where it
was normal to find a general mechanism described, followed by a
limitation to some capricious number, usually small enough to
seriously limit the utility of the mechanism, and often further
reducible by the system administrator during system configuration, so
you couldn't even count on the miserly nominal limit in the
documentation.  Quoting Armando Stettner of DEC (from memory), ``Unix
isn't a police-state operating system.''.

And (returning to the question of why I use Plan 9) the feeling I got
reading the CACM Unix paper appeared again when reading about Plan 9
circa 1991.



  parent reply	other threads:[~2003-02-15  3:27 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 15:21 John Stalker
2003-02-13 15:38 ` Ronald G. Minnich
2003-02-13 15:43   ` Boyd Roberts
2003-02-13 15:53     ` Phil White
2003-02-13 23:25       ` Jim Choate
2003-02-14 19:45         ` Dan Cross
2003-02-14 21:04           ` Phil White
2003-02-13 16:51   ` matt
2003-02-14  9:31   ` Douglas A. Gwyn
2003-02-14 15:11     ` Ronald G. Minnich
2003-02-17  9:53       ` Douglas A. Gwyn
2003-02-17 11:32         ` Geoff Collyer
2003-02-17 12:06           ` Lucio De Re
2003-02-17 13:36             ` Russ Cox
2003-02-17 13:41               ` Lucio De Re
2003-02-17 21:37           ` Andrew
2003-02-17 22:03             ` Geoff Collyer
2003-02-17 22:07               ` Russ Cox
2003-02-17 22:07               ` rob pike, esq.
2003-02-17 22:59                 ` northern snowfall
2003-02-17 23:10                 ` Russ Cox
2003-02-17 23:23                   ` George Michaelson
2003-02-18  0:53                     ` Skip Tavakkolian
2003-02-18  0:51                       ` Mike Haertel
2003-02-18  9:33                       ` Douglas A. Gwyn
2003-02-18  9:49                         ` [9fans] Re: acd compile problem Conor Williams
2003-02-18 10:01                           ` nigel
2003-02-18 17:30                         ` [9fans] So What is P9 good for Skip Tavakkolian
2003-02-18 17:25                           ` nigel
2003-02-18  4:13                     ` Jack Johnson
2003-02-18  9:10                       ` M Heath
2003-02-20  2:52                     ` Martin C.Atkins
2003-02-17 23:35                   ` matt
2003-02-17 23:45                     ` George Michaelson
2003-02-18  1:53                 ` Geoff Collyer
2003-02-17 23:32             ` Dan Cross
2003-02-14  2:06 ` Geoff Collyer
2003-02-14  9:31   ` Richard Miller
2003-02-14  9:34     ` Geoff Collyer
2003-02-14 15:12       ` Ronald G. Minnich
2003-02-14 13:40     ` David Presotto
2003-02-14 16:44       ` rob pike, esq.
2003-02-14 16:47         ` Ronald G. Minnich
2003-02-15  3:27       ` Geoff Collyer [this message]
2003-02-15  6:29         ` Ronald G. Minnich
2003-02-15  9:39         ` Digby Tarvin
2003-02-17  9:53       ` Douglas A. Gwyn
2003-02-17  9:53     ` Douglas A. Gwyn
  -- strict thread matches above, loose matches on Subject: below --
2003-02-18 15:34 Tom Glinos
2003-02-18 15:39 ` Ronald G. Minnich
2003-02-18  3:06 okamoto
2003-02-18  1:34 okamoto
2003-02-15  6:47 Andrew Simmons
2003-02-14 21:55 Skip Tavakkolian
2003-02-14 21:58 ` Doc Shipley
2003-02-15  0:20 ` Dan Cross
2003-02-13 14:20 peter a. cejchan
2003-02-13  9:37 Jeffrey Haun
2003-02-13 10:04 ` Stephen Wynne
2003-02-13 17:52   ` maynard
2003-02-13 18:12     ` Scott Schwartz
2003-02-13 20:00       ` Jack Johnson
2003-02-13 10:11 ` Phil White
2003-02-13 10:22 ` Lucio De Re
2003-02-13 10:33 ` Skip Tavakkolian
2003-02-13 13:54 ` Russ Cox
2003-02-13 14:00   ` Lucio De Re
2003-02-13 16:26   ` rob pike, esq.
2003-02-13 16:31     ` northern snowfall
2003-02-13 23:28     ` Jim Choate
2003-02-14 19:50       ` mike
2003-02-14 20:05         ` Doc Shipley
2003-02-14 19:51       ` Dan Cross
2003-02-13 14:00 ` northern snowfall
2003-02-13 18:02 ` Jack Johnson

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=449b922076a2122f384b55b3e3f1aead@collyer.net \
    --to=geoff@collyer.net \
    --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).