1 |
On 10/02/18 20:06, Rich Freeman wrote: |
2 |
> On Sat, Feb 10, 2018 at 2:52 PM, Kai Krakow <hurikhan77@×××××.com> wrote: |
3 |
>> Am Sat, 10 Feb 2018 19:38:56 +0000 schrieb Wols Lists: |
4 |
>> |
5 |
>>> On 10/02/18 18:56, Kai Krakow wrote: |
6 |
>>>> role and /usr takes the role of /, and /home already took the role of |
7 |
>>>> /usr (that's why it's called /usr, it was user data in early unix). The |
8 |
>>> |
9 |
>>> Actually no, not at all. /usr is not short for USeR, it's an acronym for |
10 |
>>> User System Resources, which is why it contains OS stuff, not user |
11 |
>>> stuff. Very confusing, I know. |
12 |
>> |
13 |
>> From https://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/usr.html: |
14 |
>> |
15 |
>>> In the original Unix implementations, /usr was where the home |
16 |
>>> directories of the users were placed (that is to say, /usr/someone was |
17 |
>>> then the directory now known as /home/someone). In current Unices, /usr |
18 |
>>> is where user-land programs and data (as opposed to 'system land' |
19 |
>>> programs and data) are. The name hasn't changed, but it's meaning has |
20 |
>>> narrowed and lengthened from "everything user related" to "user usable |
21 |
>>> programs and data". As such, some people may now refer to this |
22 |
>>> directory as meaning 'User System Resources' and not 'user' as was |
23 |
>>> originally intended. |
24 |
>> |
25 |
>> So, actually the acronym was only invented later to represent the new |
26 |
>> role of the directory. ;-) |
27 |
>> |
28 |
> |
29 |
> A bit more of history here: |
30 |
> |
31 |
> http://www.osnews.com/story/25556/Understanding_the_bin_sbin_usr_bin_usr_sbin_Split |
32 |
> |
33 |
Fascinating. And I made a typo, which is interesting too - I always knew |
34 |
it as Unix System Resources - typing "user" was a mistake ... I wonder |
35 |
how much weird info is down to mistakes like that :-) |
36 |
|
37 |
Cheers, |
38 |
Wol |