The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Groups origins
Date: Sun, 3 Oct 2021 17:22:48 -0600	[thread overview]
Message-ID: <CANCZdfoHjGanx5W0hBnvZitNAtmQU5nxnJP0GconNxC5qT1hCw@mail.gmail.com> (raw)
In-Reply-To: <DC7CDF60-D803-471B-B921-D97A5FA1B096@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]

On Sun, Oct 3, 2021 at 3:55 PM Will Senn <will.senn@gmail.com> wrote:

> Hi all,
>
> I was reading a recent thread, over on the FreeBSD forums about groups
> that quickly devolved into a discussion on the origin of the operator group:
> https://forums.freebsd.org/threads/groups-overview.82303/
>
> I thought y’all would be the best place to ask the questions that arose in
> me during my read of the thread.
>
> Here they are in no special order:
>
> 1. Where did operator come from and what was it intended to solve?
>

Operator was for people that 'operated' the computers. The name came from a
group on TOPS-20. The operator could do things normal users couldn't, like
restart stalled print jobs, run backups to mag tape and a few other normal
'house keeping' duties that these old machines needed.

In BSD, it serves much the same purpose. It's a way to grant a little bit
of privilege to an otherwise normal account that falls short of root.

This grew out of the days before the personal computer revolution where the
machine was massive (in terms of size), served a lot of people (via dumb
terminals), and needed constant care and feeding that you'd delegate to
undergrad technitians who needed work study money...


> 2. How has it evolved.
>

In general, using groups to control permissions has fallen out of style.
There's a few around still like operator and wheel that control some
things, or have elevated privs due to being able to open files others can't.


> 3. What’s a good place to look/ref to read about groups, generally?
>

At one point, it was well documented in the FreeBSD handbook, but I'm not
seeing it right away in a quick search.


> I liked one respondent’s answer about using find, heir, and the files
> themselves to learn about groups being used in a running system, paying
> attention to the owner, Audi, etc along the way and this is how I do it
> now, but this approach doesn’t account for the history and evolution.
>
> Thanks!
>
> Willu
>
>
>
> Sent from my iPhone
>

[-- Attachment #2: Type: text/html, Size: 3459 bytes --]

  reply	other threads:[~2021-10-03 23:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03 21:54 Will Senn
2021-10-03 23:22 ` Warner Losh [this message]
2021-10-03 22:10 Norman Wilson
2021-10-04 13:39 ` John P. Linderman
2021-10-04  1:22 Norman Wilson

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=CANCZdfoHjGanx5W0hBnvZitNAtmQU5nxnJP0GconNxC5qT1hCw@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=tuhs@minnie.tuhs.org \
    --cc=will.senn@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).