White Hat Institute

White Hat Institute Logo - I
Donate

Linux basics

Command-line interface (part 6)

File hierarchy

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.

  • : The  registry is a unique home index for the root user on the framework. It’s usable and readable only by the root client, and it’s generally structured to work much like a  directory yet for records and settings the root client needs. Nowadays, numerous frameworks impair the root client for utilizing the  command to get super-user benefits, so this registry isn’t used so much.

  • and: These registries store binary executable records, which are fundamental for booting the system. The significant contrast between these directories is that the registry is proposed for system binaries that administrators will use to manage the Linux operating framework.

Linux basics 46
  • : This directory stores the shared libraries for the binaries found in the  and  directories.

Linux basics 47
  • : The purpose of this index is to store all the bootloader documents, kernel records, and  files. It’s frequently treated as a different, small partition so that the bootloader can peruse it more effectively.

Linux basics 48
  • : The idea of the  directory is to store optional software, downloaded from outside the Linux repository. You can find an empty  folder on many Linux-like systems.

  • : The directory stores system setup files. In the event that you have to configure a service on a Linux framework, or change network or other core settings, this is the place to look first.

Linux basics 49
  • : The  directory is the area on Linux frameworks where each user stores his/her records. Every directory under  is named after a specific user name and is owned by that user.

Linux basics 50
  • : The purpose of this directory is to store documents that a server may share remotely.

Linux basics 51
  • and: When you add extra filesystems to your PC, regardless of whether it’s from a USB drive, an NFS mount, or different sources, you need some standard place to mount them. For this reason, we use  and  directories. The  register fills in as a mount point for removable media gadgets, for example, CDROMs, computerized cameras, and different USB-connected devices. Since  is relatively new in the UNIX world, you could experience frameworks running without this registry. The  directory should be empty and only used for temporary mount points.

Linux basics 52
  • : Although  is articulated like a user, we need to know that it represents Unix System Resources. The  directory ought to contain shareable, read-only information.

Linux basics 53

: This directory incorporates a lot of commands.

Linux basics 54

: this directory contains libraries that are not legitimately executed by clients or scripts.

Linux basics 55

: This registry can be utilized by an owner to install software locally.

Linux basics 56

: This directory contains architecture-independent data.

Linux basics 57

: This directory is for kernel source files.

Linux basics 58-1
  • : You will discover device records here. UNIX frameworks have an  rule that implies even your equipment ends up with a file. This catalog contains records for gadgets on your system from disks and partitions to mice and keyboards.

Linux basics 59
  • : The  registry stores records that represent data about pretty much the majority of the running processes on the framework.

Linux basics 60
  • : While some kernel state documents have appeared in  nowadays, they are supposed to be put away in The  registry is intended to contain these documents that let you collaborate with the kernel, and this catalog gets powerfully populated with records that frequently appear as nested series of recursive symlinks.

Linux basics 61
  • : Applications and users should utilize  to store impermanent information when required. Information stored in  may use either disk space or RAM. The two of which are overseen by the operating system. Never use  to store information that is significant or which you wish to archive.

Linux basics 62