From: harker@harker.com (Robert Harker)
Subject: [TUHS] historical users and groups
Date: Tue, 13 Jan 2009 23:28:02 -0800 [thread overview]
Message-ID: <496D9402.3060607@harker.com> (raw)
In-Reply-To: <mailman.1.1231898401.13466.tuhs@minnie.tuhs.org>
My knowledge comes from my early days at Sun in 84-85 as a rock-n-roll roadie
turned into a UNIX sysadmin. It was passed to me as I was learning how to
take care of trade show Sun Workstations. So take it with a grain of salt.
> daemon user
daemon was for daemon processes that ran in the background but did not want to
run as root. I believe it was used by inetd when it spawned a process but an
not sure. It was also used by sendmail when it gave up its SUID root privileges.
> operator user
operator was a normal user that had privilege to read the raw file systems
through group membership. Sysadmins who did backups would also be a member of
this group. The group I recall in the early days was "kmem" although now
there is a separate group "disk".
> bin user
A user to go with group bin. Typically would be the "proper" owner of all the
binaries and libraries on a system. It has lingered on for far to long
because, IMHO, the vendors had no clue as to why everything was owned by bin
and just kept it that way since "thats the way it's always been".
> bin group
I was told that group bin came from UCB to allow semi-trusted staff to replace
binaries in the file system without giving them the root password.
> staff group
My recollection is that staff was for group read/write permissions for home
directories, separate from group wheel which granted extra privileges
> nobody group versus nogroup group
The nobody group was a group to go with the nobody user introduced with NFS.
nogroup may have been someone's attempt to make the name more obvious, or it
may have been for non-privileged account. But the second case weakens the
protection of a non-privileged account
next parent reply other threads:[~2009-01-14 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1231898401.13466.tuhs@minnie.tuhs.org>
2009-01-14 7:28 ` Robert Harker [this message]
2009-01-14 0:59 Jeremy C. Reed
2009-01-14 13:00 ` Jose R. Valverde
2009-01-15 17:15 ` Jason Stevens
2009-01-16 5:52 ` Angus Robinson
2009-01-14 13:33 ` Jose R. Valverde
2009-01-14 17:15 ` Tim Bradshaw
2009-01-14 17:36 ` John Cowan
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=496D9402.3060607@harker.com \
--to=harker@harker.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).