The article you reference is ONLY based on history, not on further usfull user cases for file systems and directories.
Like you want to have /usr mounted as only read only. Which will protect your computer from some hackes changing the system. Then you might want to differ /usr/* from /usr/local/*
@AppA Why /etc? Why not, it has to have some name. It is where you store configuration files that change your system behavior for all users at your system. In each users home directory you place the part of configuration files that only apply on that user, not the orthers.
/bin and /sbin is for programs needed in singel user and booting time.
/usr/bin /usr/sbin is programs delivered by your distribution.
/usr/local/bin /usr/local/sbin is programs you (your admin) has installed for all users.
[lists(dot)busybox(dot)net] is the adress to the resource and you can compare this to the / of the site
[/pipermail/busybox/2010-December/074114.html] is the absolute path to an HTML stored at the adress. One is to find the site the other is to find a file on the site.
Not sure if this really explains the design choices them selves but it makes sense to differantiate the two.
@StupidIdiot12345 It is hard to say. As "Unix System Resource" is technically correct and logical like /dev /etc etc.
But if/when /usr were originally to include a user files (there where no /home), it would be correct that /usr stands for "user".But same is with /tmp. So is it just broken e letter? :D Or that all root dirs were with tree letters? Like "ls /?sr" same way as 14 letters for filenames and 3 letter postfix. It is hard to find out those Unix dev ideas to name things
Very well explained, 100% marks for a tutorial well done.
2010superfunny 2 weeks ago
m'kay... :)
Zahrec 1 month ago
@AppA
The article you reference is ONLY based on history, not on further usfull user cases for file systems and directories.
Like you want to have /usr mounted as only read only. Which will protect your computer from some hackes changing the system. Then you might want to differ /usr/* from /usr/local/*
andjack 1 month ago
@AppA Why /etc? Why not, it has to have some name. It is where you store configuration files that change your system behavior for all users at your system. In each users home directory you place the part of configuration files that only apply on that user, not the orthers.
/bin and /sbin is for programs needed in singel user and booting time.
/usr/bin /usr/sbin is programs delivered by your distribution.
/usr/local/bin /usr/local/sbin is programs you (your admin) has installed for all users.
andjack 1 month ago
@theseriousaccount Yeah the difference between absolute and relative paths is clear to me, it's that I don't understand why everything is where it is.
For example, why are the settings (usually) in /etc and why are binaries in /bin and/or /usr/bin...
For this I think I have to dig deeper inside the history of UNIX and Linux to find out.
AppA 1 month ago
@AppA
Very simplified explanation:
[lists(dot)busybox(dot)net] is the adress to the resource and you can compare this to the / of the site
[/pipermail/busybox/2010-December/074114.html] is the absolute path to an HTML stored at the adress. One is to find the site the other is to find a file on the site.
Not sure if this really explains the design choices them selves but it makes sense to differantiate the two.
theseriousaccount 1 month ago
@andjack I found this resource, but I still have trouble getting to understand these design choices:
lists(dot)busybox(dot)net/pipermail/busybox/2010-December/074114.html
AppA 1 month ago
very nice! easy to understand.
alankhoa 1 month ago
@TheFri13 Yes, you are right.
But it is so symetrical to say that with all the other sbin:s so I usually say that anyway before I take a second thought about it. :-)
andjack 1 month ago
@StupidIdiot12345 It is hard to say. As "Unix System Resource" is technically correct and logical like /dev /etc etc.
But if/when /usr were originally to include a user files (there where no /home), it would be correct that /usr stands for "user".But same is with /tmp. So is it just broken e letter? :D Or that all root dirs were with tree letters? Like "ls /?sr" same way as 14 letters for filenames and 3 letter postfix. It is hard to find out those Unix dev ideas to name things
TheFri13 1 month ago