Description of the structure and application of the folders under "Go" Linux

Description of the structure and application of the folders under Linux:

/bin: Binary executable command.

/dev: Device special files.

/etc: System administration and configuration files.

/ETC/RC.D: Startup configuration files and scripts.

/home: The base point of the household directory, such as the user's main directory is/home/user, can be expressed in ~user.

/LIB: Standard programming library, also called dynamic Link shared library, acts like a. dll file in Windows.

/sbin: System administration commands, which are stored in the hypervisor used by the system administrator.

/tmp: A common temporary file storage point.

/root: The system administrator's home directory.

/MNT: This directory is provided by the system to allow users to temporarily mount other file systems.

/lost+found: This directory is usually empty, the system is not properly shut down and leave the "homeless" file is here.

/proc: A virtual directory, which is a mapping of system memory. This directory can be accessed directly to obtain system information.

/var: overflow area for some large files, such as log files for various services.

/usr: The most extensive directory, the applications and files to be used almost all in this directory. These include:

/USR/X11R6: The directory where x window is stored.

/usr/bin: A multitude of applications.

/usr/sbin: Some management programs for super users.

/usr/doc:linux documentation.

The header files required to develop and compile the application under/usr/include:linux.

/usr/lib: Common dynamic Link libraries and package configuration files.

/usr/man: Help documentation.

/USR/SRC: Source code, the Linux kernel code is placed in the/usr/src/linux.

/usr/local/bin: Locally added command.

/usr/local/lib: Locally added Coogan file system.

Typically, the root filesystem occupies a smaller space because most of the files do not need to be changed frequently, and include strict files and a small, infrequently changed file system that cannot be easily damaged. In addition to a possible system boot image called the/vmlinuz standard, the root directory generally does not contain any files. All other files are in subdirectories of the root file system.

1./bin Directory

The/bin directory contains commands that are required for boot startup or commands that may be used by ordinary users (possibly after boot boot). These commands are binary executable programs (the bin is the binary abbreviation), most of the system is important system files.

2./sbin Directory

The/sbin directory is similar to/bin and is also used to store binary files. Since most of these files are the basic system programs used by the system administrator, they are generally not used by ordinary users, although they can be used when necessary and permissible.

3./etc Directory

The/etc directory holds various system configuration files, including user information file/etc/passwd, System initialization file/ETC/RC and so on. Linux relies on these files to run normally.

4./root Directory

The/root directory is the Super User directory.

5./lib Directory

The/lib directory is the shared library required by the program on the root file system, which holds the shared files required for the root file system program to run. These files contain code that can be shared by many programs to prevent each program from having a copy of the same subroutine, making the executable smaller and space-saving.

6./lib/modules Directory

The/lib/modules directory contains system cores that can load various modules, especially those needed to reboot the system when recovering a damaged system (for example, network and file system drivers).

7./dev Directory

The/dev directory holds device files, which are device drivers, through which users access external devices. For example, the user can access the/dev/mouse to access the mouse input, just like accessing other files.

8./tmp Directory

The/tmp directory stores the information and data generated by the program at run time. However, after booting the boot, it is best to use/var/tmp instead of/tmp, because the former may have a larger disk space.

9./Boot Directory

The/boot directory holds the files used by the boot loader (bootstrap loader), such as Lilo, and the core image is often placed here, rather than in the root directory. But if there are many core images, this directory can become very large, and it would be better to use a separate file system. It is also important to note that the core image must be within the first 1024 cylinders of the IDE's hard disk.

/mnt Directory

The/MNT directory is the installation point of the system Administrator temporary installation (mount) file system. The program does not automatically support installation to/mnt. /mnt The following can be divided into many subdirectories, such as/mnt/dosa may be using the Msdos file system floppy drive, and/mnt/exta may be the use of ext2 file system floppy drive,/mnt/cdrom optical drive and so on.

/proc,/usr,/var,/home Directory

Installation point for other file systems.

The directory tree can be divided into small sections, each of which can be on its own disk or partition. The main sections are the root,/usr,/var, and/home file systems. Each part has a different purpose.

Each machine has a root file system that contains the files necessary to boot the system and enable other file systems to mount, and the root filesystem should have enough content for a single-user state. It should also include tools to repair damaged systems, restore backups, and so on.

The/usr file system contains all the commands, libraries, man pages, and other non-changing files that are required in general operations.

/usr should not have a file to be modified in general use. This allows the files in this file system to be shared over the network, which can be more efficient because it saves disk space (/usr is easily hundreds of trillion) and is easy to manage (when upgrading an application, only the primary/USR needs to be changed without changing each machine) even if the file system is on a local disk, You can also read mount only to reduce file system corruption when the system crashes.

The/var file system contains files that change, such as the spool directory (for Mail, news, printers, and so on), log files, formatted manual pages, and staging files. Traditionally,/var has been somewhere in/usr, but it is not possible for/USR to be read-only installed.

The/home file system contains all of the actual data on the system, including the user House directory. A large home/home may be divided into a number of file systems, you need to add a class name under/home, such as/home/students,/home/staff and so on.

Here is a detailed description:

/etc File System

The/etc directory contains a variety of system configuration files, some of which are described below. Other you should know which program they belong to and read the man page of the program. Many network configuration files are also in/etc.

1./ETC/RC or/etc/rc.d or/ETC/RC? D: A directory that starts, or alters, a script or script that runs at run-time.

2./ETC/PASSWD: User database, where the domain gives the user name, real name, user start directory, encrypted password, and other information of the user.

3./ETC/FDPRM: Floppy parameter table to illustrate different floppy disk formats. Can be set with SETFDPRM. See the SETFDPRM help page for more information.

4./etc/fstab: Specifies the list of file systems that need to be installed automatically at startup. Also includes information about the swap area enabled with SWAPON-A.

5./etc/group: Similar to/etc/passwd, but not the user information but the group information. Includes various data for the group.

6./etc/inittab:init configuration file.

7./etc/issue: Includes the user's output information before the logon prompt. Usually includes a short description of the system or a welcome message. Specific content is determined by the system administrator.

8./etc/magic: Config file for "file". Contains a description of the different file formats, and "file" guesses the file type based on it.

9./ETC/MOTD:MOTD is the message of the day, which is automatically exported after the user has successfully logged in. The content is determined by the system administrator.

Often used to advertise information, such as warnings for scheduled shutdown times.

/etc/mtab: List of currently installed file systems. Initialized by the script (SCRITP) and updated automatically by the Mount command. Used when a list of currently installed file systems is required (for example, the DF command).

/etc/shadow: Shadow password file on a system with Shadow (shadow) password software installed. The shadow password file moves the encrypted password in the/etc/passwd file to/etc/shadow, which is readable only by the superuser (root). This makes it more difficult to decipher the password, which increases the security of the system.

configuration file for the./etc/login.defs:login command.

/etc/printcap: Similar to/etc/termcap, but for printers. syntax is different.

/etc/profile,/etc/csh.login,/ETC/CSH.CSHRC: Files that are executed Bourne or cshells at logon or startup. This allows the system administrator to establish a global default environment for all users.

/etc/securetty: Confirm the security terminal, that is, which terminal allows superuser (root) to log in. Only virtual consoles are generally listed, which makes it impossible (at least difficult) to break into the system via a modem or network and gain superuser privileges.

/etc/shells: Lists the shells you can use. The CHSH command allows the user to change the login shell within the scope specified in this file. A service process that provides a machine FTP service FTPD checks whether the user shell is listed in the/etc/shells file, and if not, the user will not be allowed to log on.

/ETC/TERMCAP: Terminal performance database. Describes what "escape sequence" controls are used by different terminals. Instead of outputting the escape sequence directly (so that it works only with a particular brand of terminal), the program looks for the correct sequence of work to be done from/etc/termcap. In this way, most programs can run on most terminals.

/dev File system

The/dev directory includes device files for all devices. The device file is named with a specific convention, which is described in the device list. Device files are generated by the system during installation and can be described later with/dev/makedev. /dev/makedev.local is a descriptive document written by the system administrator for local device files (or connections) (such as some non-standard device drivers that are not part of the standard Makedev). Below is a brief introduction to some of the commonly used files in/dev.

1./dev/console: System console, which is a direct and system connected monitor.

2./dev/hd:ide the hard drive driver interface. such as:/dev/hda refers to the first hard disk, had1 refers to the first partition of/dev/hda. If there are other hard disks in the system, then/dev/hdb,/dev/hdc 、...... If more than one partition is hda1, hda2 ...

3./DEV/SD:SCSI disk driver interface. If the system has a SCSI hard disk, it will not access the/dev/had, but will access the/DEV/SDA.

4./DEV/FD: Floppy drive device driver. such as:/dev/fd0 refers to the system's first floppy disk, which is commonly referred to as a disk,/dev/fd1 refers to a second floppy disk, ... The/dev/fd1 h1440, however, represents access to 4.5 high-density disks in drive 1.

5./DEV/ST:SCSI tape drive driver.

6./dev/tty: Provides Virtual Console support. such as:/dev/tty1 refers to the system's first Virtual Console,/dev/tty2 is the system's second Virtual Console.

7./dev/pty: Provide remote login pseudo terminal support. The/dev/pty device is used for Telnet login.

8./dev/ttys: Computer serial interface, for DOS is "COM1" port.

9./DEV/CUA: The computer serial interface, the device used with the modem.

/dev/null: "Black hole", all information written to the device will disappear. For example: When you want to hide the output information on the screen, simply enter the output information into/dev/null.

/usr file system

/usr is a very important directory, usually this file system is very large, because all programs are installed here. All files in/usr typically come from Linux distributions, locally installed programs, and other things under/usr/local, as this will not require reinstalling all programs when upgrading a new system or release. Many of the content in the/usr directory is optional, but these features make it more efficient for users to use the system. /usr can accommodate many large packages and their configuration files. Some important directories are listed below (some of the less important directories have been omitted).

1./USR/X11R6: Contains all executable programs, configuration files, and supporting files for the X Window System. To simplify the development and installation of x, files for x are not integrated into the system. The X Window System is a powerful graphical environment that provides a large number of graphical tool programs. Users who are familiar with Microsoft Windows will not be overwhelmed by the X Window System.

2./usr/x386: Similar to/USR/X11R6, but is dedicated to x one release 5.

3./usr/bin: Centralized almost all user commands, is the system's software library. Some other commands are in/bin or/usr/local/bin.

4./usr/sbin: Includes unnecessary system administration commands for the root file system, such as most service programs.

5./usr/man,/usr/info,/usr/doc: These directories contain all manual pages, GNU information documents, and various other documentation files. Each online manual has two subdirectories for the section. For example:/usr/man/man1 contains the source code for the first section of the online manual (no formatted original file),/USR/MAN/CAT1 contains the first section of the formatted content. The online manual is divided into the following nine sections: internal commands, system calls, library functions, devices, file formats, games, macro packages, system administration, and core programs.

6./usr/include: Contains header files for the C language, which are used to describe the data structure, sub-procedures, and constants in the C language program, which end with. H. In order to maintain consistency, this should actually be placed under the/usr/lib, but it is customary to use the name.

7./usr/lib: Contains the immutable data files of the program or subsystem, including some site–wide profiles. The name Lib originates from the library; The original library of programming also exists in/usr/lib. When the program is compiled, the program connects to the library. There are also a number of programs that store configuration files.

8./usr/local: Locally installed software and other files are placed here. This is similar to/usr. Users may find some of the larger packages, such as Tex, Emacs, and more.

/var file system

/var contains data to be changed when the system is generally running. Usually the size of the directory in which the data resides is constantly changing or expanding. In the original/var directory, some of the content is in/usr, but in order to maintain the relative stability of the/USR directory, the directories that need to change frequently are placed in/var. Each system is specific, i.e. it is not shared with other computers over the network. Some important directories are listed below (some of the less important directories are omitted).

1./var/catman: Includes the formatted Help (man) page. The source file for the help page is generally present in/usr/man/catman, and some man pages may have a pre-formatted version, which exists in/usr/man/cat. While the other man pages need to be formatted for the first time, the formatted version exists in/var/man so that other people can look at the same page without waiting for formatting. (/var/catman are often cleared, just as you would clear a temporary directory.) )

2./var/lib: The file to be changed when the system is in normal operation.

3./var/local: Variable data that holds the programs installed in the/usr/local (that is, programs installed by the system administrator). Note that if necessary, even locally installed programs will use other/var directories, such as/var/lock.

4./var/lock: Lock the file. Many programs follow the convention of creating a locked file in/var/lock to support their use of a particular device or file. Other programs will not use this device or file when they notice the lock file.

5./var/log: Logs (log) files for various programs, especially login (/var/log/wtmplog records all log-in and logoff to system) and Syslog (/var/log/messages Records store all core and System program information). The files in the/var/log often grow in uncertainty and should be cleaned up regularly.

6./var/run: A system-related information file is available before the next system boot. For example,/var/run/utmp contains information about the user who is currently logged on.

7./var/spool: directory where the "spool (spool)" program is placed, such as mail, news, print queues, and other queued work. Each of the different spool has its own subdirectory under/var/spool, for example, the user's mailbox is stored in/var/spool/mail.

8./var/tmp: A temporary file that is larger than/TMP and that requires a longer time to exist. Note system administrators may not allow/var/tmp to have very old files.

/proc File System

The/proc file system is a pseudo file system, which means that it is a directory that does not actually exist, so this is a very special directory. It does not exist on a disk, but is generated in memory by the core. This directory is used to provide information about the system. Here are some of the most important files and directories (the/proc file system is described in more detail in the proc man page).

1./proc/x: The directory of information about process X, which is the identification number for this process. Each process has a directory called its own process number under/proc.

2./proc/cpuinfo: Store processor (CPU) information, such as the type of CPU, manufacturer, model, and performance.

3./proc/devices: A list of device drivers for the currently running core configuration.

4./PROC/DMA: Displays the DMA channel currently in use.

5./proc/filesystems: File system Information for the core configuration.

6./proc/interrupts: Displays information about the interrupt information and occupants that are occupied, and the amount that is occupied.

7./proc/ioports: The I/O port currently in use.

8./proc/kcore: System physical memory image. It is exactly the same size as the physical memory, but it does not actually occupy so much memory; it is only created when the program accesses it. (Note: Unless you copy it somewhere, there's nothing in the/proc that takes up any disk space.) )

9./PROC/KMSG: Message for core output. will also be sent to the syslog.

/PROC/KSYMS: the core symbol table.

/proc/loadavg: System "average load"; 3 meaningless indicators indicate the current workload of the system.

/proc/meminfo: Various memory usage information, including physical memory and swap partition (swap).

/proc/modules: Stores which core module information is currently loaded.

/proc/net: Network protocol status information.

/proc/self: A symbolic connection to the process directory that is stored to view the/PROC program. When 2 processes view/proc, this will be a different connection. This is primarily convenient for the program to get its own process directory.

/proc/stat: The different states of the system, for example, the number of times a page error occurred after the system started.

/proc/uptime: The length of time the system started.

/proc/version: Core version.

/usr/local is usually the directory where you install the software, this directory is equivalent to the Programefiles directory under Windows

/opt This directory is the installation directory of some large software, or the installation directory of some service programs

For example: Just installed the beta version of Firefox, can be installed in the/opt/firefox_beta directory, the/opt/firefox_beta directory contains all the files needed to run Firefox, libraries, data and so on. To remove Firefox, you can simply delete the/opt/firefox_beta directory.

/usr/local

The main store is the software that is installed manually, that is, software that is not installed through "new" or apt-get. It has a similar directory structure to the/usr directory. Let the package Manager manage the/usr directory, and put the custom script (scripts) under the/usr/local directory, I think this should be a good idea.

Source

Description of the structure and application of the folders under "Go" Linux