From: splite-gentoo@sigint.cs.purdue.edu
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: adding sbin directories to PATH for all users
Date: Wed, 25 Nov 2015 15:12:32 -0500 [thread overview]
Message-ID: <20151125201232.GO20646@sigint.cs.purdue.edu> (raw)
In-Reply-To: <22102.843.697962.119455@a1i15.kph.uni-mainz.de>
On Wed, Nov 25, 2015 at 07:51:55PM +0100, Ulrich Mueller wrote:
> >>>>> On Wed, 25 Nov 2015, William Hubbs wrote:
>> From what I've read, the traditional difference between bin and sbin
>> was that sbin means static-bin and everything stored in there was to
>> be able to come up without libraries.
>
> Source/reference for this?
Some of us are old enough to remember when it happened, sonny. It was
Sun's idea. Disks were expensive, so they wanted as much of the OS to be
mountable read-only via NFS as possible (remember diskless workstations?
no, you probably don't), so they moved /bin and /lib to /usr and replaced
them with symlinks. /sbin was created to hold the necessary binaries
to get /usr mounted via NFS at boot. They had to be statically-linked
because all the shared libraries were in /usr-- hence the "s" in "sbin".
If you really want a reference, here you go (page 7):
http://chiclassiccomp.org/docs/content/computing/Sun/800-1731-10_SunOS4.0ChangeNotes9May88.pdf
>> As mgorny was talking about earlier, a good chunk of what is in sbin
>> *can* be run by normal users.
>
> Then it shouldn't be in sbin, in the first place. That's a separate
> discussion though.
Bollocks. The whole "/sbin is for admins" meme is an after-the-fact
fabrication by those too young to remember the original purpose for it.
(Unfortunately, that included people at Sun.)
Now, get off my lawn.
next prev parent reply other threads:[~2015-11-25 20:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 17:10 [gentoo-dev] rfc: adding sbin directories to PATH for all users William Hubbs
2015-11-25 17:24 ` Michael Orlitzky
2015-11-25 17:36 ` Kristian Fiskerstrand
2015-11-25 18:05 ` Ulrich Mueller
2015-11-25 18:17 ` Michał Górny
2015-11-25 19:18 ` Daniel Campbell
2015-11-25 19:23 ` Michał Górny
2015-11-25 20:16 ` Mike Gilbert
2015-11-25 20:15 ` Kristian Fiskerstrand
2015-11-26 15:03 ` [gentoo-dev] " Duncan
2015-11-26 15:10 ` Alan McKinnon
2015-11-25 18:14 ` [gentoo-dev] " William Hubbs
2015-11-25 18:31 ` Ulrich Mueller
2015-11-25 18:38 ` William Hubbs
2015-11-25 18:51 ` Ulrich Mueller
2015-11-25 19:47 ` William Hubbs
2015-11-25 20:53 ` Ulrich Mueller
2015-11-25 21:39 ` William Hubbs
2015-11-25 20:12 ` splite-gentoo [this message]
2015-11-25 18:58 ` Mike Gilbert
2015-11-25 20:42 ` Anthony G. Basile
2015-11-26 16:37 ` Peter Stuge
2015-11-25 19:17 ` Nicolas Sebrecht
2015-11-25 21:39 ` Andrew Savchenko
2015-11-26 3:58 ` Mike Gilbert
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=20151125201232.GO20646@sigint.cs.purdue.edu \
--to=splite-gentoo@sigint.cs.purdue.edu \
--cc=gentoo-dev@lists.gentoo.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