The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wb@freebie.xs4all.nl (Wilko Bulte)
Subject: [TUHS] Early UNIX file permission oddity
Date: Wed, 21 May 2008 08:15:15 +0200	[thread overview]
Message-ID: <20080521061515.GA73871@freebie.xs4all.nl> (raw)
In-Reply-To: <20080521043224.GA32712@minnie.tuhs.org>

Quoting Warren Toomey, who wrote on Wed, May 21, 2008 at 02:32:24PM +1000 ..
> I was just browsing through the 1974 UNIX CACM paper, the one that first
> publicly described the design and functionality of UNIX. I came across
> some sentences which describe the file permissions, and they sounded quite odd:
> 
>   When a file is created, it is marked with the user ID of its owner.
>   Also given for new files is a set of seven protection bits.
>   Six of these specify independently read, write, and execute permission
>   for the owner of the file and for all other users. [The seventh bit
>   is the set-user-id bit. ]
> 
> This seems to indicate that there are "rwx" bits for owner, "rwx" bits for other,
> and no "rwx" bits for group. I've never seen a UNIX system with 6 file
> permission bits, so I thought I would poke around to see what I could find. It

Well, I have a UNIX-like system sitting in my basement that has this.  This
is a TSC Uniflex system running on a Motorola MC6809 CPU.  8 bit CPU in
other words.

..

Wilko



  reply	other threads:[~2008-05-21  6:15 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 [this message]
2008-05-21 11:08 ` John Cowan
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=20080521061515.GA73871@freebie.xs4all.nl \
    --to=wb@freebie.xs4all.nl \
    /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).