Questão de Linux Administration #019e3987
What is the purpose of the Filesystem Hierarchy Standard?
It is a security model used to ensure files are organized according to their permissions and accessibility.
It provides unified tools to create, maintain and manage multiple filesystems in a common way.
It defines a common internal structure of inodes for all compliant filesystems.
It is a distribution neutral description of locations of files and directories.
Explicação Oficial / Explicações da Comunidade
The Filesystem Hierarchy Standard (FHS) defines the directory structure and directory contents in Linux and other Unix-like operating systems. It is a distribution-neutral description of where files and directories should be located, ensuring consistency across different Linux distributions.
How it Works
The FHS specifies the purpose of each major directory (e.g., /bin, /etc, /usr, /var) and the types of files they should contain. For example, /bin holds essential user command binaries, /etc contains configuration files, and /var stores variable data like logs and spools. This standardization allows users and administrators to predict file locations regardless of the distribution.
Why the Correct Answer is Right
The correct answer states that the FHS is a distribution-neutral description of locations of files and directories. This is accurate because the FHS is a consensus-based standard adopted by major Linux distributions to maintain compatibility and ease of administration.
Why the Incorrect Answers are Wrong
- The description of a security model for organizing files according to permissions and accessibility is incorrect. The FHS does not define security models; it defines directory structure. Security models like DAC (Discretionary Access Control) or MAC (Mandatory Access Control) are separate concepts.
- The claim that the FHS provides unified tools to create, maintain, and manage multiple filesystems is false. Tools for filesystem management (e.g.,
mkfs,mount,fsck) are part of the operating system utilities, not the FHS. - The statement that the FHS defines a common internal structure of inodes for all compliant filesystems is incorrect. Inode structure is filesystem-specific (e.g., ext4, XFS, Btrfs) and is not defined by the FHS. The FHS deals with the directory hierarchy, not low-level filesystem metadata.