From: "Rodrigo G. López" <rodrigosloop@gmail.com>
To: "Stephan Han." <xenonelive@gmail.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Who's behind the UNIX filesystem permission implementation
Date: Wed, 31 Jul 2019 18:49:29 +0200 [thread overview]
Message-ID: <CA+cCjXrWok5DR61hA0xKEodMfVyCUgNmsksTCjS6u6Aikf-0pw@mail.gmail.com> (raw)
In-Reply-To: <CAJV3Z_-JVU2Nn1nhrXOKHWQOni3ZWhRsPiAn_mQ7oH5hMnWumA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
Multics had modes per file (https://multicians.org/fjcc4.html) but i don't
know about the origins. the simpler approach of owner/group/other is a
purely Unix creation and i would bet Ken Thompson is behind it all.
i would love to know more.
-rodri
On Wed, Jul 31, 2019, 12:00 PM Stephan Han. <xenonelive@gmail.com> wrote:
> Hello Unix enthusiasts.
>
> I'd like to know who or the group of people behind implementing this
> filesystem permission system.
> Since we are using this system for nearly 40 years and it addresses all
> the aspects of the permission matter without any hustle.
> I'm inspired to know who/how came up with this theory?
> Also if it derived from somewhere else or If there's an origin story about
> this, it would be worth to share.
>
> Cheers.
> Stephan
>
> --
> No When
>
[-- Attachment #2: Type: text/html, Size: 1463 bytes --]
next prev parent reply other threads:[~2019-07-31 16:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 9:59 Stephan Han.
2019-07-31 16:49 ` Rodrigo G. López [this message]
2019-07-31 17:29 ` Arthur Krewat
2019-07-31 17:58 ` Clem Cole
2019-07-31 18:03 ` Christopher Browne
2019-07-31 20:16 ` Arthur Krewat
2019-07-31 17:00 ` Toby Thain
2019-07-31 17:18 ` Warner Losh
2019-07-31 22:24 ` William Corcoran
2019-07-31 22:49 ` George Michaelson
2019-07-31 18:46 ` Grant Taylor via TUHS
2019-07-31 19:01 ` Clem Cole
2019-07-31 19:34 ` Ben Greenfield via TUHS
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=CA+cCjXrWok5DR61hA0xKEodMfVyCUgNmsksTCjS6u6Aikf-0pw@mail.gmail.com \
--to=rodrigosloop@gmail.com \
--cc=tuhs@minnie.tuhs.org \
--cc=xenonelive@gmail.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).