zlacker

[return to "Understanding the bin, sbin, usr/bin, usr/sbin split (2010)"]
1. baby+rq[view] [source] 2022-05-11 10:35:57
>>taubek+(OP)
Tangent, but that's what made getting into Linux/Unix really hard. You have all these folders and files and no README.md to explain what is what. And there seemed to be no logic at all with how things were organized or named (and names often were shortened to abbreviations that I couldn't comprehend). I'm wondering what a modern system made to be readable and understandable would look like.

The other thing, coming from windows, was not understanding where to install things. In windows there's like a single place where you install all your stuff.

◧◩
2. trasz+Qq[view] [source] 2022-05-11 10:38:57
>>baby+rq
Take a look at "man hier": https://www.freebsd.org/cgi/man.cgi?hier
◧◩◪
3. moffka+Gv[view] [source] 2022-05-11 11:28:57
>>trasz+Qq
"Link a man to man and you solve his problem for a day, teach a man to man and you've enlightened him for life."

Side note, calling the file system layout "hier" has got to be the stupidest naming choice. Did they want this to be lost forever so that nobody ever finds it?

◧◩◪◨
4. indror+WD[view] [source] 2022-05-11 12:22:56
>>moffka+Gv
Once upon a time, the manpages were a printed object. This, coupled with some of Bell and later BSD's quirks about naming things, led to some historic naming conventions. See also: this entire damn conversation on naming directories.

One wasn't intended to call man directly, instead calling apropos first, finding the appropriate page to open.

◧◩◪◨⬒
5. colejo+zM[view] [source] 2022-05-11 13:09:42
>>indror+WD
But what if I need to read on how to use apropos? Then I need to do `man apropos` and I'm stuck in a cycle! /s

https://www.man7.org/linux/man-pages/man1/apropos.1.html

[go to top]