From mboxrd@z Thu Jan 1 00:00:00 1970 From: imp@bsdimp.com (Warner Losh) Date: Thu, 2 Feb 2012 10:40:01 -0700 Subject: [TUHS] Understanding the /bin, /sbin, /usr/bin, /usr/sbin Split In-Reply-To: <89159FF1-5521-4890-A5F0-30DC9E5B7EC9@bsdimp.com> References: <20120201121214.55c73577@cnb.csic.es> <4F2A907D.9000000@fastmail.us> <89159FF1-5521-4890-A5F0-30DC9E5B7EC9@bsdimp.com> Message-ID: <78400D2A-74E6-434D-B168-4D1C1EDB8326@bsdimp.com> On Feb 2, 2012, at 10:24 AM, Warner Losh wrote: > > 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. That should read 'all non-binary executables and non-config files' Warner