From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Understanding the /bin, /sbin, /usr/bin, /usr/sbin Split
Date: Thu, 2 Feb 2012 14:49:44 -0700 [thread overview]
Message-ID: <52BD3851-95AF-4DFC-8728-9F2DB1E1614C@bsdimp.com> (raw)
In-Reply-To: <alpine.BSF.2.00.1202030759350.66525@aneurin.horsfall.org>
On Feb 2, 2012, at 2:14 PM, Dave Horsfall wrote:
> On Thu, 2 Feb 2012, John Cowan wrote:
>
>> Does anyone know what the "s" in sbin stands for? "Superuser"? I would
>> have put these files in /root/bin, but perhaps /root did not yet exist.
>
> I seem to recall that they were statically linked i.e. not using those
> new-fangled shared library thingies. And if you've ever tried to admin a
> system with a trashed shared library, you'll understand; it usually
> involves looking for the installation media.
/bin is also statically linked, at least on those distributions that support split / and /usr. SunOS 4.x and 4.4BSD did this. Except for the ones that have gone to a dynamic root moving the shared libraries from /usr/lib to /lib. Prior to the /etc -> /sbin moves, all binaries were statically linked. Even after the move /bin and /sbin remained static, while /usr/bin and /usr/sbin were dynamic. The needs of reliability vs space savings pushed all the binaries in /sbin and /bin to be static.
Even after the split in more modern systems, init and sh tend to be the only binaries that are statically linked anymore. Thankfully, most binaries are dynamic these days, which saves a ton of space on / (as a percentage of what's used).
Warner
>> Not everything in /usr/share comes from /etc; in particular,
>> /usr/share/dict was formerly /usr/dict.
>
> As I dimly recall, /usr/share was exported, hence the name.
>
> -- Dave
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
>
next prev parent reply other threads:[~2012-02-02 21:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 19:16 A. P. Garcia
2012-01-31 19:27 ` Warner Losh
2012-02-01 11:12 ` Jose R. Valverde
2012-02-01 17:35 ` Warner Losh
2012-02-02 13:32 ` Random832
2012-02-02 17:24 ` Warner Losh
2012-02-02 17:36 ` John Cowan
2012-02-02 18:10 ` Warner Losh
2012-02-02 21:14 ` Dave Horsfall
2012-02-02 21:49 ` Warner Losh [this message]
2012-02-02 22:29 ` Tim Newsham
2012-02-02 22:47 ` Warner Losh
2012-02-02 22:59 ` Lyndon Nerenberg
2012-02-02 23:33 ` Warner Losh
2012-03-13 16:09 ` [TUHS] ASR 37 teletype desired by LCM / Vulcan.com John Foust
2012-02-02 22:53 ` [TUHS] Understanding the /bin, /sbin, /usr/bin, /usr/sbin Split Lyndon Nerenberg
2012-02-02 23:35 ` Warner Losh
2012-02-03 11:10 ` Tim Bradshaw
2012-02-03 15:22 ` Jose R. Valverde
2012-02-03 16:06 ` Ronald Natalie
2012-02-03 16:09 ` Steve Nickolas
2012-02-02 17:40 ` Warner Losh
2012-02-02 18:02 ` Tim Newsham
2012-02-02 13:45 ` Tim Bradshaw
2012-02-01 9:26 arnold
2012-02-02 13:35 ` Tim Bradshaw
2012-02-02 13:49 ` Larry McVoy
2012-02-02 23:16 Norman Wilson
2012-02-02 23:37 ` Carl Lowenstein
2012-02-02 23:58 ` John Cowan
2012-02-04 19:34 Pepe
2012-02-04 21:05 ` Lyndon Nerenberg
2012-02-05 8:38 Hendrik Jan Thomassen
2012-02-05 10:13 ` Jaap Akkerhuis
2012-02-05 17:15 ` Warner Losh
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=52BD3851-95AF-4DFC-8728-9F2DB1E1614C@bsdimp.com \
--to=imp@bsdimp.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).