Chapter 3. The Root Filesystem
3.1. Purpose
The contents of the root filesystem must be adequate to boot, restore, recover, and/or repair the system.
• To boot a system, enough must be present on the root partition to mount other filesystems. This includes
utilities, configuration, boot loader information, and other essential start-up data. /usr, /opt, and /var are
designed such that they may be located on other partitions or filesystems.
• To enable recovery and/or repair of a system, those utilities needed by an experienced maintainer to diagnose
and reconstruct a damaged system must be present on the root filesystem.
• To restore a system, those utilities needed to restore from system backups (on floppy, tape, etc.) must be
present on the root filesystem.
Rationale
The primary concern used to balance these considerations, which favor placing many things on the root
filesystem, is the goal of keeping root as small as reasonably possible. For several reasons, it is desirable to
keep the root filesystem small:
• It is occasionally mounted from very small media.
• The root filesystem contains many system-specific configuration files. Possible examples include a kernel
that is specific to the system, a specific hostname, etc. This means that the root filesystem isn’t always
shareable between networked systems. Keeping it small on servers in networked systems minimizes the
amount of lost space for areas of unshareable files. It also allows workstations with smaller local hard
drives.
• While you may have the root filesystem on a large partition, and may be able to fill it to your heart’s
content, there will be people with smaller partitions. If you have more files installed, you may find
incompatibilities with other systems using root filesystems on smaller partitions. If you are a developer
then you may be turning your assumption into a problem for a large number of users.
• Disk errors that corrupt data on the root filesystem are a greater problem than errors on any other
partition. A small root filesystem is less prone to corruption as the result of a system crash.
Applications must never create or require special files or subdirectories in the root directory. Other locations in
the FHS hierarchy provide more than enough flexibility for any package.
Rationale
There are several reasons why creating a new subdirectory of the root filesystem is prohibited:
• It demands space on a root partition which the system administrator may want kept small and simple for
either performance or security reasons.
• It evades whatever discipline the system administrator may have set up for distributing standard file
hierarchies across mountable volumes.
Distributions should not create new directories in the root hierarchy without extremely careful consideration
of the consequences including for application portability.
3
剩余51页未读，继续阅读
jichunlai
- 粉丝: 38
- 资源: 48
我的内容管理
展开
最新资源
- 构建Cadence PSpice仿真模型库教程
- VMware 10.0安装指南：步骤详解与网络、文件共享解决方案
- 中国互联网20周年必读：影响行业的100本经典书籍
- SQL Server 2000 Analysis Services的经典MDX查询示例
- VC6.0 MFC操作Excel教程：亲测Win7下的应用与保存技巧
- 使用Python NetworkX处理网络图
- 科技驱动：计算机控制技术的革新与应用
- MF-1型机器人硬件与robobasic编程详解
- ADC性能指标解析：超越位数、SNR和谐波
- 通用示波器改造为逻辑分析仪：0-1字符显示与电路设计
- C++实现TCP控制台客户端
- SOA架构下ESB在卷烟厂的信息整合与决策支持
- 三维人脸识别：技术进展与应用解析
- 单张人脸图像的眼镜边框自动去除方法
- C语言绘制图形：余弦曲线与正弦函数示例
- Matlab 文件操作入门：fopen、fclose、fprintf、fscanf 等函数使用详解
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
