The newbies to the Linux command-line may wind up asking why there are such a significant number of special directories, what they are there for, and why things are sorted out how they are. If you are not acclimated with how Linux arranges documents, the directories can appear to be absolute self-assertive with odd truncated names and, much of the time, repetitive names. It turns out there’s a strategy to this depends on many years of UNIX convention, and in this section, we will be giving a prologue to the Linux directory structure.
Ex: ([email protected]:~$ cd /root)
Ex: ([email protected]:~$ cd /bin)
Ex: ([email protected]:~$ cd /lib)
Ex: ([email protected]:~$ cd /boot)
Ex: ([email protected]:~$ cd /opt)
Ex: ([email protected]:~$ cd /etc)
Ex: ([email protected]:~$ cd /home)
Ex: ([email protected]:~$ cd /srv)
Ex: ([email protected]:~$ cd /media)
Ex: ([email protected]:~$ cd /usr)
“/usr/bin”: This directory incorporates a lot of commands.
Ex: ([email protected]:/usr$ cd /usr/bin/)
“/usr/lib”: this directory contains libraries that are not legitimately executed by clients or scripts.
Ex: ([email protected]:/usr$ cd /usr/lib)
“/usr/local”: This registry can be utilized by an owner to install software locally.
Ex: ([email protected]:/usr$ cd /usr/local/)
“/usr/share”: This directory contains architecture-independent data.
Ex: ([email protected]:/usr$ cd /usr/share)
“/usr/src”: This directory is for kernel source files.
Ex: ([email protected]:/usr$ cd /usr/src)
Ex: ([email protected]:~$ cd /dev)
Ex: ([email protected]:~$ cd /proc)
Ex: ([email protected]:~$ cd /sys)
Ex: ([email protected]:~$ cd /tmp)