From: arnold@skeeve.com
To: tuhs@minnie.tuhs.org, gtaylor@tnetconsulting.net
Subject: Re: [TUHS] /bin vs /sbin
Date: Tue, 21 Jul 2020 12:22:11 -0600 [thread overview]
Message-ID: <202007211822.06LIMBJ4018831@freefriends.org> (raw)
In-Reply-To: <862d8a34-456d-33c1-7ef0-58c6e8089de9@tnetconsulting.net>
Grant Taylor via TUHS <tuhs@minnie.tuhs.org> wrote:
> To me, this makes it fairly self evident that /sbin was originally for
> statically linked binaries. At least in Linux.
Dunno about that.
> Does anyone have any history of /sbin from other traditional Unixes?
> I'd be quite interested in learning more.
/sbin and /usr/sbin came into being in the late 80s when Berkeley
and USG were standardizing on file system layouts for diskless workstations;
Sun and DEC and others were also in on this.
/sbin specifically was meant to hold the executables meant for use by
root that previously had been in /etc along with config files.
(sbin ==> super-user bin.)
The idea was that /etc held things specific to a box, while /bin, /sbin,
/usr could be remote mounted from a server. This is also when /home
came into practice as the place to hold home directories.
This avoided having umpteen zillion copies of the same files
(executables, man pages, libraries, etc.) since they could be mounted
read-only from one or a few servers. At the time, disk space was not
nearly as cheap as it is now.
This is also when /var came into being for log files and such;
again - it was per machine space, so it lived either on a small disk
in the workstation or on a per-client chunk of space on the server
if the client was totally diskless.
HTH,
Arnold
next prev parent reply other threads:[~2020-07-21 18:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 17:55 Grant Taylor via TUHS
2020-07-21 18:15 ` Warner Losh
2020-07-21 22:42 ` David Arnold
2020-07-22 3:33 ` Warner Losh
2020-07-21 18:22 ` arnold [this message]
2020-07-21 18:33 ` Warner Losh
2020-07-21 18:43 ` Larry McVoy
2020-07-22 1:16 ` tytso
2020-07-22 3:27 ` Grant Taylor via TUHS
2020-07-22 3:35 ` Warner Losh
2021-01-27 5:56 ` Greg A. Woods
2021-01-27 19:06 ` Grant Taylor via TUHS
2021-01-27 22:22 ` Warner Losh
2021-01-27 22:35 ` Greg A. Woods
2021-01-28 5:24 ` Grant Taylor via TUHS
2020-07-22 1:44 ` Dan Cross
2020-07-22 2:17 ` Jon Forrest
2020-07-22 2:20 ` Adam Thornton
2020-07-22 13:30 ` Clem Cole
2020-07-22 13:43 ` Richard Salz
2020-07-22 2:27 ` Kurt H Maier
2020-07-21 19:24 ` Clem Cole
2020-07-22 13:39 ` Clem Cole
2021-01-29 23:50 ` Chris Hanson
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=202007211822.06LIMBJ4018831@freefriends.org \
--to=arnold@skeeve.com \
--cc=gtaylor@tnetconsulting.net \
--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).