usr STANDS FOR USER. If you think it is an acronym YOU ARE WRONG. None of the original root level directories' names are acronyms. They are all shortened forms of the words they represent (etc for et cetera, dev for device, bin for binary, and so on). If you think the Unix creators would break consistency for just one directory, you're an idiot.
tldp.org says "some people may now refer to this directory as meaning 'User System Resources' and not 'user' as was originally intended"
@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
What about /dev and /proc?! They are definitely NOT dependent on the distribution you are using. And /srv?! WTF?! And "usr" does not come from "user". You should stop teaching! NOW!
There has been some effort to standardise the GNU/Linux file system (in the same that BSD has a strict file system hierarchy). There are general commonalities between different systems. It just takes a bit of study and use to get used to it, it's quite logical. When you see how much more efficient and powerful it is you really begin to appreciate free software.
For me, as a Linux beginner the LFS is confusing as hell. Programs can reside in /bin, /sbin or /usr/bin and /usr/sbin. But then again, they could reside anywhere the developer wants to place it.
Similarly, the program settings are not located within the same folders, but usually in /etc or your home dir. Settings are almost always configuration files which don't always state all of the options available (sometimes you have to add a setting yourself).
@AppA I must agree. It's certainly not very intuitive and I'll be it puts a lot of people off. One does tend to get better at "predicting" where a file may go over time, but I've already been using linux for years and only now starting to know where to go to find certain files when I need them with a measure of accuracy.
[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.
@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.
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/*
@tuxxerrr Cd is actually a command of shell. But all what are in /bin/ are system programs.
Commands and programs are two different things. Like ls, cp, mv, rm and so on are system programs and not commands. But then pipe, alias, cd and so on are shell commands.
User types to used command interpreter (like bash, sh or zsh) a program name, options and then other programs, files and/or mix them with commands.
small correction to myself that not all /bin/ are system programs, but all are programs. Some of them are system programs and some programs belongs to applications and so on. But point is, program and command are two different things.
@andjack I know those.... but /sbin/ is only for administrative purposes to fix the system. Not for any server software. Idea with /sbin/ is that if system goes gaga, root can fix the system with such tools.
'cd' is not an external command i.e. it does not reside on the filesystem as a file. It's a function of the shell (an internal command) that changes its notion of the current working directory.
In otherwords, on the unixes, child processes (external commands) cannot change the environment of a parent process (the shell in this case).
@dapodix Yes you are correct. 'cd' is an internal command. grep, sed, gawk, cp etc are commands that are found within /bin. Other than that, this is pretty quick and easy demo of Unix type file system. I'll still give it a thumbs up. :)
Very well explained, 100% marks for a tutorial well done.
2010superfunny 2 weeks ago
m'kay... :)
Zahrec 1 month ago
Comment removed
Zahrec 1 month ago
very nice! easy to understand.
alankhoa 1 month ago
usr STANDS FOR USER. If you think it is an acronym YOU ARE WRONG. None of the original root level directories' names are acronyms. They are all shortened forms of the words they represent (etc for et cetera, dev for device, bin for binary, and so on). If you think the Unix creators would break consistency for just one directory, you're an idiot.
tldp.org says "some people may now refer to this directory as meaning 'User System Resources' and not 'user' as was originally intended"
StupidIdiot12345 1 month ago 2
@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
What about /dev and /proc?! They are definitely NOT dependent on the distribution you are using. And /srv?! WTF?! And "usr" does not come from "user". You should stop teaching! NOW!
prestigen19 1 month ago
Why no /dev?
noobyfromhell 1 month ago
Comment removed
eebeni 2 months ago 12
@eebeni sorry but it has been user all time I used unix systems, since back in the end of -80:th.
andjack 1 month ago
@andjack Oops you're right.
eebeni 1 month ago
@eebeni no problem. I am impressed by anyone that say what you said. Thanks!
andjack 1 month ago
There has been some effort to standardise the GNU/Linux file system (in the same that BSD has a strict file system hierarchy). There are general commonalities between different systems. It just takes a bit of study and use to get used to it, it's quite logical. When you see how much more efficient and powerful it is you really begin to appreciate free software.
va7mn 2 months ago
For me, as a Linux beginner the LFS is confusing as hell. Programs can reside in /bin, /sbin or /usr/bin and /usr/sbin. But then again, they could reside anywhere the developer wants to place it.
Similarly, the program settings are not located within the same folders, but usually in /etc or your home dir. Settings are almost always configuration files which don't always state all of the options available (sometimes you have to add a setting yourself).
Have fun searching! :(
AppA 2 months ago 2
@AppA I must agree. It's certainly not very intuitive and I'll be it puts a lot of people off. One does tend to get better at "predicting" where a file may go over time, but I've already been using linux for years and only now starting to know where to go to find certain files when I need them with a measure of accuracy.
2000jago 2 months ago
@AppA no there is simple.
/bin are for user programs and /sbin for system program and servers.
They are dist. programs that is used and needed to boot the system before all file systems are mounted.
(history: / was the smal and fast disk).
/usr/bin are for user progs and /usr/sbin for system progs.
/usr is for more common progs that isn't neaded until the system is up running.
(history: /usr was larger but slower than the disk used for /)
/usr/local/bin and sbin are local installed by admin.
andjack 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
@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
@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 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
@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
Netscape ?! Wow !! Now I feel old !
ElectronikHeart 4 months ago
@ElectronikHeart I love that Netscape's code (Mozilla code) ate Microsoft's interwebs by turning open source. Checkmate.
IamDUFF 3 months ago
Why does this vid makes me want to watch southpark?
No but seriously, thanks.
jeroeniskoning 4 months ago
this is _NOT_ a good video at all.. cd is not a command which is found in bin.. its a meta-command provided by the shell...
tuxxerrr 4 months ago
@tuxxerrr $ whereis cd
/usr/bin/cd
$ #Nice going there, bro
macheads101 3 months ago 2
@macheads101 - Heh. Get a real OS already??
$ whereis cd
cd:
$ which cd
$ type -a cd
cd is a shell builtin
dapodix 3 months ago
@tuxxerrr Cd is actually a command of shell. But all what are in /bin/ are system programs.
Commands and programs are two different things. Like ls, cp, mv, rm and so on are system programs and not commands. But then pipe, alias, cd and so on are shell commands.
User types to used command interpreter (like bash, sh or zsh) a program name, options and then other programs, files and/or mix them with commands.
ls | grep foobar > result.txt
program, command, program, syntax, command, file.
TheFri13 2 months ago 2
small correction to myself that not all /bin/ are system programs, but all are programs. Some of them are system programs and some programs belongs to applications and so on. But point is, program and command are two different things.
TheFri13 2 months ago
@TheFri13 /bin and /sbin are programs that are needed when you boot the system, before /usr is mounted.
/usr/bin and /usr/sbin are all programs which are available after /usr is mounted.
/usr/local/bin and /usr/local/sbin is for local installation from source by sysadmin.
bin is user programs and sbin is for root and servers.
andjack 1 month ago
@andjack I know those.... but /sbin/ is only for administrative purposes to fix the system. Not for any server software. Idea with /sbin/ is that if system goes gaga, root can fix the system with such tools.
TheFri13 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
Good video. Thank you. Look forward to more.
Regards,
TheKC1ML 5 months ago
Thanks for sharing your knowledge.Please post some more videos.Thanks !!
sifarin 6 months ago
nice video, please more like this. ;)
hakermik 6 months ago
Excellent vid. Thanks for sharing.
krazyfua 6 months ago
Thank you!,great video!
Videoorchard 6 months ago
just wow.. thanks friend this video class really appreciated keep loading more videos... SHAIK
eknaamzeeshan 7 months ago
this is the best explanation I have ever heard, thanks so much for making this.
scarfprickles 8 months ago
simplified and easy to understand, thank you.
4UCESO 9 months ago
thank you man very good, the way how you explained
bara242 10 months ago
Mmmkay?
Craf7y 1 year ago
'cd' is not an external command i.e. it does not reside on the filesystem as a file. It's a function of the shell (an internal command) that changes its notion of the current working directory.
In otherwords, on the unixes, child processes (external commands) cannot change the environment of a parent process (the shell in this case).
dapodix 1 year ago
@dapodix Yes you are correct. 'cd' is an internal command. grep, sed, gawk, cp etc are commands that are found within /bin. Other than that, this is pretty quick and easy demo of Unix type file system. I'll still give it a thumbs up. :)
fidjetelectronics 10 months ago
very very clear explaination. This is what unix beginner need to understand. Thanks.
quanvu07 1 year ago
Thanks, very useful.
frog252 1 year ago