From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Understanding the /bin, /sbin, /usr/bin, /usr/sbin Split
Date: Thu, 2 Feb 2012 10:24:26 -0700 [thread overview]
Message-ID: <89159FF1-5521-4890-A5F0-30DC9E5B7EC9@bsdimp.com> (raw)
In-Reply-To: <4F2A907D.9000000@fastmail.us>
On Feb 2, 2012, at 6:32 AM, Random832 wrote:
> On 2/1/2012 6:12 AM, Jose R. Valverde wrote:
>> So, beyond the point of filling up a disk (and that's the point for the partition
>> system) there was a need to ensure you could separate user data from system data:
>> adding user programs or data to a separate space (disk, partition, whatever)
>> ensured the system space was not filled and the system would not become unusable.
>
> The thing is, /usr isn't "user data". That's /home. /usr is just "more system space".
/usr was user data, back in the day. /home came about much later.
> And this article never actually explains sbin. Or /usr/share, which is interesting because as I understand it it's designed to be shareable between multiple computers of possibly different architectures
sbin was created in SYS Vr4 to move all the binaries that were in /etc. /usr/share was created to move all the non-binary, non-text files that were in /etc like termcap and timezone info.
Warner
next prev parent reply other threads:[~2012-02-02 17:24 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 [this message]
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
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=89159FF1-5521-4890-A5F0-30DC9E5B7EC9@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).