From: Will Senn <will.senn@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: [TUHS] Groups origins
Date: Sun, 3 Oct 2021 16:54:01 -0500 [thread overview]
Message-ID: <DC7CDF60-D803-471B-B921-D97A5FA1B096@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
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?
2. How has it evolved.
3. What’s a good place to look/ref to read about groups, generally?
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: 1451 bytes --]
next reply other threads:[~2021-10-03 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 21:54 Will Senn [this message]
2021-10-03 23:22 ` Warner Losh
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=DC7CDF60-D803-471B-B921-D97A5FA1B096@gmail.com \
--to=will.senn@gmail.com \
--cc=tuhs@minnie.tuhs.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).