From: reed@reedmedia.net (Jeremy C. Reed)
Subject: [TUHS] history of sbin?
Date: Thu, 31 Jan 2013 18:06:15 -0600 (CST) [thread overview]
Message-ID: <alpine.NEB.2.02.1301311747070.26654@t1.m.reedmedia.net> (raw)
I have heard the story a few times about sbin split is due to disk
space, such as told at
http://www.osnews.com/story/25556/Understanding_the_bin_sbin_usr_bin_usr_sbin_Split/
http://lists.busybox.net/pipermail/busybox/2010-December/074114.html
But I don't see any mention of it in 32V and not in BSD until around
Net2 (like in 1991 src.README said ``... there has been a major
reorganization of the file system. (You may have seen similar
reorganizations on systems shipped by Sun Microsytems [sic] and Digital
Equipment Corporation, among others.) ... /sbin same as /bin, but
binaries for the root user''. The slides from Feb. 1988 for a BSD BOF at
USENIX mentioned this sbin reorganization.
Looking at "Unix Text Processing" (1987) and "Life with Unix" (1989) I
didn't see any use of sbin/. (I didn't look at my other old books.)
From searching old 1980 usenet archives I only saw a few mentions (like
/usr/brl/sbin/...).
When did some (non-BSD) systems ship and document /sbin, /usr/sbin?
Is the common story (liked linked above) the right story?
Jeremy C. Reed
echo uggc://errqzrqvn.arg/obbxf/ofq-uvfgbel/ | \
tr "noqruvxzabcefgl" "abdehikmnoprsty"
next reply other threads:[~2013-02-01 0:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 0:06 Jeremy C. Reed [this message]
2013-02-01 1:28 ` Random832
2013-02-01 1:37 ` Warner Losh
2013-02-01 1:41 ` Warren Toomey
2013-02-01 1:53 ` ramble1035 @dslextreme.com
2013-02-01 2:01 ` Larry McVoy
2013-02-01 2:02 ` Armando Stettner
2013-02-01 3:09 ` Larry McVoy
2013-02-01 3:24 ` Armando Stettner
2013-02-01 2:03 ` [TUHS] 1974 CACM Paper, was " Warren Toomey
2013-02-01 2:14 ` Warren Toomey
2013-02-01 2:34 ` [TUHS] 1974 CACM Paper Warren Toomey
2013-02-01 2:54 ` [TUHS] history of sbin? Warren Toomey
2013-02-01 4:58 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=alpine.NEB.2.02.1301311747070.26654@t1.m.reedmedia.net \
--to=reed@reedmedia.net \
/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).