The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cowan@ccil.org (John Cowan)
Subject: [TUHS] Early UNIX file permission oddity
Date: Wed, 21 May 2008 07:08:51 -0400	[thread overview]
Message-ID: <20080521110851.GG14184@mercury.ccil.org> (raw)
In-Reply-To: <20080521043224.GA32712@minnie.tuhs.org>

Warren Toomey scripsit:

> The only possibility that I can see is, as 3rd Edition was being rewritten
> from assembly into C, the filesystem went through a stage where there
> "rwx" execute bits for user, and "rxw" execute bits for other as the CACM
> paper described, but groups had not been introduced yet. Then, the idea of
> groups was added [...]. 

I think you're probably right, but with an important caveat:

It's important to remember that 1st, 2nd, 3rd, ... represent editions of
the *manual*, and that there is no guarantee that any particular
snapshot of the system corresponds exactly to what was in any particular
manual edition.  Research Unix (as it was later called retrospectively)
was right up to the end a continuously evolving system, and the whole
concept of releases simply did not exist for it.

So when the CACM article was written, it probably specified what the
kernel was doing that particular day, without reference to any edition.

-- 
John Cowan        http://www.ccil.org/~cowan          cowan at ccil.org
Please leave your values                Check your assumptions.  In fact,
   at the front desk.                      check your assumptions at the door.
     --sign in Paris hotel                   --Cordelia Vorkosigan



  parent reply	other threads:[~2008-05-21 11:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21  4:32 Warren Toomey
2008-05-21  6:15 ` Wilko Bulte
2008-05-21 11:08 ` John Cowan [this message]
2008-05-21 11:20   ` Warren Toomey
2008-05-21 11:50     ` John Cowan
2008-05-21 21:39   ` Tim Newsham

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=20080521110851.GG14184@mercury.ccil.org \
    --to=cowan@ccil.org \
    /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).