<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://gentoo-zh.org/extern.php?action=feed&amp;tid=15&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Gentoo中文社区 / File systems]]></title>
		<link>http://www.gentoo-zh.org/viewtopic.php?id=15</link>
		<description><![CDATA[File systems 最近发表的帖子。]]></description>
		<lastBuildDate>Wed, 03 Aug 2022 14:36:10 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[File systems]]></title>
			<link>http://www.gentoo-zh.org/viewtopic.php?pid=15#p15</link>
			<description><![CDATA[<p>File systems<br />文件系统</p><p>Second extended fs support<br />CONFIG_EXT2_FS<br />&#160; &#160; Ext2文件系统,无日志.详见&quot;Documentation/filesystems/ext2.txt&quot;文档.</p><p>&#160; &#160; Ext2 extended attributes<br />&#160; &#160; CONFIG_EXT2_FS_XATTR<br />&#160; &#160; &#160; &#160; Ext2文件系统扩展属性(与inode关联的name:value对)支持.详见attr手册.不确定的选&quot;N&quot;.</p><p>&#160; &#160; &#160; &#160; Ext2 POSIX Access Control Lists<br />&#160; &#160; &#160; &#160; CONFIG_EXT2_FS_POSIX_ACL<br />&#160; &#160; &#160; &#160; &#160; &#160; POSIX ACL(访问控制列表)支持,这是一种超越&quot;owner/group/world&quot;的权限管理方式,<br />&#160; &#160; &#160; &#160; &#160; &#160; 可以更精细的针对每个用户进行访问控制.详见acl手册.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; Ext2 Security Labels<br />&#160; &#160; &#160; &#160; CONFIG_EXT2_FS_SECURITY<br />&#160; &#160; &#160; &#160; &#160; &#160; &quot;安全标签&quot;允许选择使用不同安全模块(如SELinux)实现的访问控制模型,<br />&#160; &#160; &#160; &#160; &#160; &#160; 如果你没有使用需要扩展属性的安全模块,可以选&quot;N&quot;.</p><p>&#160; &#160; Ext2 execute in place support<br />&#160; &#160; CONFIG_EXT2_FS_XIP<br />&#160; &#160; &#160; &#160; 芯片内执行(execute in place)的意思是程序在写入存储介质时就已经分配好运行时的地址,<br />&#160; &#160; &#160; &#160; 因此不需要载入内存即可在芯片内执行,一般仅在嵌入式系统上才使用这种技术.</p><p>Ext3 journalling file system support<br />CONFIG_EXT3_FS<br />&#160; &#160; Ext3日志型文件系统.详见&quot;Documentation/filesystems/ext3.txt&quot;文档.</p><p>&#160; &#160; Default to &#039;data=ordered&#039; in ext3<br />&#160; &#160; CONFIG_EXT3_DEFAULTS_TO_ORDERED<br />&#160; &#160; &#160; &#160; 选&quot;Y&quot;表示将默认的日志模式设为&quot;data=ordered&quot;(更安全),<br />&#160; &#160; &#160; &#160; 选&quot;N&quot;表示将默认的日志模式设为&quot;data=writeback&quot;(更危险).<br />&#160; &#160; &#160; &#160; 选&quot;Y&quot;,仅在你确实明白&quot;data=writeback&quot;的风险,以及确实有充足的理由的时候,才能选&quot;N&quot;.<br />&#160; &#160; Ext3 extended attributes<br />&#160; &#160; CONFIG_EXT3_FS_XATTR<br />&#160; &#160; &#160; &#160; Ext3文件系统扩展属性(与inode关联的name:value对)支持.详见attr手册.不确定的选&quot;N&quot;.</p><p>&#160; &#160; &#160; &#160; Ext3 POSIX Access Control Lists<br />&#160; &#160; &#160; &#160; CONFIG_EXT3_FS_POSIX_ACL<br />&#160; &#160; &#160; &#160; &#160; &#160; POSIX ACL(访问控制列表)支持,这是一种超越&quot;owner/group/world&quot;的权限管理方式,<br />&#160; &#160; &#160; &#160; &#160; &#160; 可以更精细的针对每个用户进行访问控制.详见acl手册.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; Ext3 Security Labels<br />&#160; &#160; &#160; &#160; CONFIG_EXT3_FS_SECURITY<br />&#160; &#160; &#160; &#160; &#160; &#160; &quot;安全标签&quot;允许选择使用不同安全模块(如SELinux)实现的访问控制模型,<br />&#160; &#160; &#160; &#160; &#160; &#160; 如果你没有使用需要扩展属性的安全模块,可以选&quot;N&quot;.</p><p>The Extended 4 (ext4) filesystem<br />CONFIG_EXT4_FS<br />&#160; &#160; Ext4日志型文件系统.详见&quot;Documentation/filesystems/ext4.txt&quot;文档.</p><p>&#160; &#160; Use ext4 for ext2/ext3 file systems<br />&#160; &#160; CONFIG_EXT4_USE_FOR_EXT23<br />&#160; &#160; &#160; &#160; 在ext2/ext3文件系统上使用ext4驱动.这样可以对ext2/ext3/ext4三种文件系统只使用同一个驱动.<br />&#160; &#160; &#160; &#160; 主要目的是减少内核尺寸.<br />&#160; &#160; Ext4 POSIX Access Control Lists<br />&#160; &#160; CONFIG_EXT4_FS_POSIX_ACL<br />&#160; &#160; &#160; &#160; POSIX ACL(访问控制列表)支持,这是一种超越&quot;owner/group/world&quot;的权限管理方式,<br />&#160; &#160; &#160; &#160; 可以更精细的针对每个用户进行访问控制.详见acl手册.不确定的选&quot;N&quot;.<br />&#160; &#160; Ext4 Security Labels<br />&#160; &#160; CONFIG_EXT4_FS_SECURITY<br />&#160; &#160; &#160; &#160; &quot;安全标签&quot;允许选择使用不同安全模块(如SELinux)实现的访问控制模型,<br />&#160; &#160; &#160; &#160; 如果你没有使用需要扩展属性的安全模块,可以选&quot;N&quot;.<br />&#160; &#160; EXT4 debugging support<br />&#160; &#160; CONFIG_EXT4_DEBUG<br />&#160; &#160; &#160; &#160; 仅供调试使用</p><p>JBD (ext3) debugging support<br />CONFIG_JBD_DEBUG<br />&#160; &#160; 仅供调试使用<br />JBD2 (ext4) debugging support<br />CONFIG_JBD2_DEBUG<br />&#160; &#160; 仅供调试使用<br />Reiserfs support<br />CONFIG_REISERFS_FS<br />&#160; &#160; 曾经的明星文件系统,特别擅长处理大量小文件的场合,由于其创始人入狱,前景不明.</p><p>&#160; &#160; Enable reiserfs debug mode<br />&#160; &#160; CONFIG_REISERFS_CHECK<br />&#160; &#160; &#160; &#160; 仅供调试使用<br />&#160; &#160; Stats in /proc/fs/reiserfs<br />&#160; &#160; CONFIG_REISERFS_PROC_INFO<br />&#160; &#160; &#160; &#160; 在/proc/fs/reiserfs文件中显示Reiserfs文件系统的状态,仅供调试使用<br />&#160; &#160; ReiserFS extended attributes<br />&#160; &#160; CONFIG_REISERFS_FS_XATTR<br />&#160; &#160; &#160; &#160; ReiserFS文件系统扩展属性(与inode关联的name:value对)支持.详见attr手册.不确定的选&quot;N&quot;.</p><p>&#160; &#160; &#160; &#160; ReiserFS POSIX Access Control Lists<br />&#160; &#160; &#160; &#160; CONFIG_REISERFS_FS_POSIX_ACL<br />&#160; &#160; &#160; &#160; &#160; &#160; POSIX ACL(访问控制列表)支持,这是一种超越&quot;owner/group/world&quot;的权限管理方式,<br />&#160; &#160; &#160; &#160; &#160; &#160; 可以更精细的针对每个用户进行访问控制.详见acl手册.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; ReiserFS Security Labels<br />&#160; &#160; &#160; &#160; CONFIG_REISERFS_FS_SECURITY<br />&#160; &#160; &#160; &#160; &#160; &#160; &quot;安全标签&quot;允许选择使用不同安全模块(如SELinux)实现的访问控制模型,<br />&#160; &#160; &#160; &#160; &#160; &#160; 如果你没有使用需要扩展属性的安全模块,可以选&quot;N&quot;.</p><p>JFS filesystem support<br />CONFIG_JFS_FS<br />&#160; &#160; JFS日志型文件系统.详见&quot;Documentation/filesystems/jfs.txt&quot;文档.</p><p>&#160; &#160; JFS POSIX Access Control Lists<br />&#160; &#160; CONFIG_JFS_POSIX_ACL<br />&#160; &#160; &#160; &#160; POSIX ACL(访问控制列表)支持,这是一种超越&quot;owner/group/world&quot;的权限管理方式,<br />&#160; &#160; &#160; &#160; 可以更精细的针对每个用户进行访问控制.详见acl手册.不确定的选&quot;N&quot;.<br />&#160; &#160; JFS Security Labels<br />&#160; &#160; CONFIG_JFS_SECURITY<br />&#160; &#160; &#160; &#160; &quot;安全标签&quot;允许选择使用不同安全模块(如SELinux)实现的访问控制模型,<br />&#160; &#160; &#160; &#160; 如果你没有使用需要扩展属性的安全模块,可以选&quot;N&quot;.<br />&#160; &#160; JFS debugging<br />&#160; &#160; CONFIG_JFS_DEBUG<br />&#160; &#160; &#160; &#160; 仅供调试使用<br />&#160; &#160; JFS statistics<br />&#160; &#160; CONFIG_JFS_STATISTICS<br />&#160; &#160; &#160; &#160; 在/proc/fs/jfs/目录中显示JFS文件系统的统计信息</p><p>XFS filesystem support<br />CONFIG_XFS_FS<br />&#160; &#160; XFS日志型文件系统是一个高性能的文件系统(笔者的最爱),擅长大文件和多线程.<br />&#160; &#160; 详见&quot;Documentation/filesystems/&quot;目录中&quot;xfs*.txt&quot;系列文档.</p><p>&#160; &#160; XFS Quota support<br />&#160; &#160; CONFIG_XFS_QUOTA<br />&#160; &#160; &#160; &#160; XFS磁盘配额(使用专用的xfs_quota工具)比通用磁盘配额模块(CONFIG_QUOTA)拥有更高级的特性,<br />&#160; &#160; &#160; &#160; 它不但能够控制用户或组的磁盘用量,还能控制项目(文件夹)的磁盘用量<br />&#160; &#160; &#160; &#160; (无论哪个用户在项目的文件夹中创建文件),但是不能同时使用组配额和项目配额.<br />&#160; &#160; &#160; &#160; 此外,对XFS来说,配额数据记录在文件系统元数据中,而不是像CONFIG_QUOTA那样记录<br />&#160; &#160; &#160; &#160; 在aquota.user和aquota.group文件中.最后,XFS配额和通用磁盘配额是两个相互独立的系统,可以同时并存.<br />&#160; &#160; XFS POSIX ACL support<br />&#160; &#160; CONFIG_XFS_POSIX_ACL<br />&#160; &#160; &#160; &#160; POSIX ACL(访问控制列表)支持,这是一种超越&quot;owner/group/world&quot;的权限管理方式,<br />&#160; &#160; &#160; &#160; 可以更精细的针对每个用户进行访问控制.详见acl手册.不确定的选&quot;N&quot;.<br />&#160; &#160; XFS Realtime subvolume support<br />&#160; &#160; CONFIG_XFS_RT<br />&#160; &#160; &#160; &#160; &quot;实时子卷&quot;是专门存储文件数据的卷,可以允许将日志与数据分开在不同的磁盘上,<br />&#160; &#160; &#160; &#160; 例如将大块头的流媒体文件存储在高速磁盘组成的实时子卷上.详见xfs手册页.<br />&#160; &#160; XFS Verbose Warnings<br />&#160; &#160; CONFIG_XFS_WARN<br />&#160; &#160; &#160; &#160; 仅供调试使用<br />&#160; &#160; XFS Debugging support<br />&#160; &#160; CONFIG_XFS_DEBUG<br />&#160; &#160; &#160; &#160; 仅供调试使用</p><p>GFS2 file system support<br />CONFIG_GFS2_FS<br />&#160; &#160; GFS2可用于搭建高可用集群文件系统,由红帽公司开发,允许所有集群节点并行访问,<br />&#160; &#160; 同时又能够完美的保持文件系统的一致性:一个节点对文件系统的任何修改都立即对所有其他节点可见.<br />&#160; &#160; 详见&quot;Documentation/filesystems/&quot;目录中&quot;gfs*.txt&quot;系列文档.</p><p>&#160; &#160; GFS2 DLM locking<br />&#160; &#160; CONFIG_GFS2_FS_LOCKING_DLM<br />&#160; &#160; &#160; &#160; GFS2分布式锁管理器(DLM).务必选&quot;Y&quot;,除非你知道自己在做什么.</p><p>OCFS2 file system support<br />CONFIG_OCFS2_FS<br />&#160; &#160; OCFS2(Oracle集群文件系统)的目标是成为一种通用文件系统.<br />&#160; &#160; OCFS2能使集群中的所有节点并发的通过标准文件系统接口来访问存储备.<br />&#160; &#160; 要使用OCFS2还需要ocfs2-tools的帮助.详见&quot;Documentation/filesystems/ocfs2.txt&quot;文档.</p><p>&#160; &#160; O2CB Kernelspace Clustering<br />&#160; &#160; CONFIG_OCFS2_FS_O2CB<br />&#160; &#160; &#160; &#160; O2CB(OCFS2 Cluster Base)是位于内核空间的集群服务结构.具体包括:NM(节点管理器,监控所有节点),HB(心跳服务),TCP(控制节点间的通讯),DLM(分布式锁管理器),CONFIGFS(用户配置文件系统驱动,挂载点是/config),DLMFS(用户空间和内核空间DLM的接口).开启此项后,将只需要很少量的用户空间组件(也就是ocfs2-tools),OCFS2就可以转起来了.但它只能玩转OCFS2自身,玩不了其他集群.<br />&#160; &#160; OCFS2 Userspace Clustering<br />&#160; &#160; CONFIG_OCFS2_FS_USERSPACE_CLUSTER<br />&#160; &#160; &#160; &#160; 为用户空间的集群服务提供支持.目的是为了配合CONFIG_DLM模块一起使用.<br />&#160; &#160; OCFS2 statistics<br />&#160; &#160; CONFIG_OCFS2_FS_STATS<br />&#160; &#160; &#160; &#160; 允许对OCFS2的使用状况进行一些统计.开启后会增加内存占用.<br />&#160; &#160; OCFS2 logging support<br />&#160; &#160; CONFIG_OCFS2_DEBUG_MASKLOG<br />&#160; &#160; &#160; &#160; 仅供调试使用<br />&#160; &#160; OCFS2 expensive checks<br />&#160; &#160; CONFIG_OCFS2_DEBUG_FS<br />&#160; &#160; &#160; &#160; 仅供调试使用</p><p>Btrfs filesystem support<br />CONFIG_BTRFS_FS<br />&#160; &#160; Btrfs是由Oracle于2007年宣布的支持写时复制(COW)的文件系统.<br />&#160; &#160; 拥有众多抢眼球的特性:软RAID管理,卷管理,克隆/快照,压缩功能,<br />&#160; &#160; 支持跨多块磁盘动态增大或收缩卷.其目标是成为下一代Linux标准文件系统.<br />&#160; &#160; 详见&quot;Documentation/filesystems/btrfs.txt&quot;文档.</p><p>&#160; &#160; Btrfs POSIX Access Control Lists<br />&#160; &#160; CONFIG_BTRFS_FS_POSIX_ACL<br />&#160; &#160; &#160; &#160; POSIX ACL(访问控制列表)支持,这是一种超越&quot;owner/group/world&quot;的权限管理方式,<br />&#160; &#160; &#160; &#160; 可以更精细的针对每个用户进行访问控制.详见acl手册.不确定的选&quot;N&quot;.<br />&#160; &#160; Btrfs with integrity check tool compiled in (DANGEROUS)<br />&#160; &#160; CONFIG_BTRFS_FS_CHECK_INTEGRITY<br />&#160; &#160; &#160; &#160; 仅供调试使用<br />&#160; &#160; Btrfs will run sanity tests upon loading<br />&#160; &#160; CONFIG_BTRFS_FS_RUN_SANITY_TESTS<br />&#160; &#160; &#160; &#160; 仅供调试使用<br />&#160; &#160; Btrfs debugging support<br />&#160; &#160; &#160; &#160; 仅供调试使用</p><p>NILFS2 file system support<br />CONFIG_NILFS2_FS<br />&#160; &#160; NILFS2是一种非常前卫的&quot;log-structured&quot;文件系统,是Linux下一代文件系统的有力竞争者.<br />&#160; &#160; NILFS2将底层设备当作一种只能追加写(append)的设备,文件系统的任何修改都只以<br />&#160; &#160; 顺序追加的方式写入磁盘(而是不覆盖旧数据),从而避免耗时的寻道(seek)操作,<br />&#160; &#160; 从而大幅提升写入性能(因为文件系统的整体效率主要由写操作的效率决定).<br />&#160; &#160; 此种思路带来了一系列靓瞎眼的特性:自动不间断快照(可以迅速恢复被删除的文件<br />&#160; &#160; 或者回到先前某个特定的时间点),快速崩溃恢复(比大多数日志型文件系统还要快),<br />&#160; &#160; 高性能(在SSD上更有绝对优势).但也带来了一个新问题:需要垃圾收集机制以清理旧数据,<br />&#160; &#160; 造成垃圾收集时的性能降低(可以通过合理安排垃圾收集时间来避免).<br />&#160; &#160; NILFS2目前不支持如下功能:atime(访问时间),POSIX ACL,扩展属性.<br />&#160; &#160; 不过考虑到SSD(固态硬盘)即将成为主流,假以时日,前途大大的啊!.<br />&#160; &#160; 详见&quot;Documentation/filesystems/nilfs2.txt&quot;文档.<br />F2FS filesystem support<br />Direct Access (DAX) support<br />Enable filesystem export operations for block IO</p><p>Enable POSIX file locking API<br />CONFIG_FILE_LOCKING<br />&#160; &#160; POSIX标准文件锁定API支持.NFS之类的网络文件系统和给文件加锁与解锁的flock()系统调用需要它.<br />&#160; &#160; 不确定的选&quot;Y&quot;.<br />FS Encryption (Per-file encryption)<br />&#160; &#160;<br />Dnotify support<br />CONFIG_DNOTIFY<br />&#160; &#160; 旧式的基于目录的文件变化的通知机制(已被Inotify取代),目前仅有少量古董程序依赖它.建议选&quot;N&quot;.<br />Inotify support for userspace<br />CONFIG_INOTIFY_USER<br />&#160; &#160; 用户空间的Inotify支持.Inotify是替代Dnotify的文件系统变化通知机制.建议选&quot;Y&quot;.<br />&#160; &#160; [提示]如果你使用了systemd作为init,那就必须选&quot;Y&quot;.<br />Filesystem wide access notification<br />CONFIG_FANOTIFY<br />&#160; &#160; fanotify是一种打算取代Inotify的文件系统变化通知机制,不过,<br />&#160; &#160; 由于目前Fanotify比inotify支持的文件系统事件类型少很多,完全取代Inotify还不现实.<br />&#160; &#160; 建议选&quot;Y&quot;.[提示]如果你使用了systemd作为init,那就必须选&quot;Y&quot;.</p><p>&#160; &#160; fanotify permissions checking<br />&#160; &#160; CONFIG_FANOTIFY_ACCESS_PERMISSIONS<br />&#160; &#160; &#160; &#160; 允许fanotify的监听器(listener)对文件系统事件进行权限检查.<br />&#160; &#160; &#160; &#160; 这样,监听器就可以在系统访问某个文件之前,首先扫描此文件.<br />&#160; &#160; &#160; &#160; 某些防病毒程序以及分级存储管理系统可能需要此特性.不确定的选&quot;N&quot;.</p><p>Quota support<br />CONFIG_QUOTA<br />&#160; &#160; 通用的磁盘配额支持(限制某个用户或者某组用户的磁盘占用空间).<br />&#160; &#160; 需要配合quota-tools工具使用.<br />Report quota messages through netlink interface<br />CONFIG_QUOTA_NETLINK_INTERFACE<br />&#160; &#160; 通过netlink接口报告QUOTA的警告信息(例如&quot;到达限额&quot;).不确定的选&quot;Y&quot;.<br />Print quota warnings to console (OBSOLETE)<br />CONFIG_PRINT_QUOTA_WARNING<br />&#160; &#160; 将QUOTA的警告信息直接显示在控制台上.反对使用,未来会移除此项.选&quot;N&quot;.<br />Additional quota sanity checks<br />CONFIG_QUOTA_DEBUG<br />&#160; &#160; 对quota内部结构进行额外的完整性检查.主要用于调试目的.不确定的选&quot;N&quot;.<br />Old quota format support<br />CONFIG_QFMT_V1<br />&#160; &#160; 老旧的v1版配额格式(linux-2.4.22之前使用的格式)支持.选&quot;N&quot;.<br />Quota format vfsv0 and vfsv1 support<br />CONFIG_QFMT_V2<br />&#160; &#160; vfsv0/vfsv1配额格式支持.两者都支持32位的UID/GID,<br />&#160; &#160; 而vfsv1还支持64位的inode/block配额.建议开启.<br />Kernel automounter version 4 support (also supports v3)<br />CONFIG_AUTOFS4_FS<br />&#160; &#160; 新的内核按需自动加载远程文件系统的支持(也支持v3).<br />&#160; &#160; 此特性需要配合用户空间工具(autofs)使用,并且需要开启NFS文件系统支持.<br />&#160; &#160; 如果你的计算机不是大型分布式网络的一部分,你应该不会需要此功能.<br />FUSE (Filesystem in Userspace) support<br />CONFIG_FUSE_FS<br />&#160; &#160; FUSE允许在用户空间实现一个全功能的文件系统,<br />&#160; &#160; 还有一个与之对应的libfuse2库和相关工具.<br />&#160; &#160; 详见&quot;Documentation/filesystems/fuse.txt&quot;文档.<br />&#160; &#160; 如果你打算开发一个自己的文件系统或者使用一个基于<br />&#160; &#160; FUSE的文件系统(例如NTFS-3G或ZFS-FUSE),可以选&quot;Y&quot;.</p><p>&#160; &#160; Character device in Userspace support<br />&#160; &#160; CONFIG_CUSE<br />&#160; &#160; &#160; &#160; 这是一个FUSE扩展,用于在用户空间实现字符设备支持.</p><p>Caches<br />&#160; &#160; 文件系统缓存</p><p>&#160; &#160; General filesystem local caching manager<br />&#160; &#160; CONFIG_FSCACHE<br />&#160; &#160; &#160; &#160; 通用文件系统本地缓存管理器.它为各种不同的文件系统(例如网络文件系统)提供了统一的本地缓存框架.<br />&#160; &#160; &#160; &#160; 这样各种缓存实现可以作为插件添加进来.详见&quot;Documentation/filesystems/caching/fscache.txt&quot;文档.</p><p>&#160; &#160; &#160; &#160; Gather statistical information on local caching<br />&#160; &#160; &#160; &#160; CONFIG_FSCACHE_STATS<br />&#160; &#160; &#160; &#160; &#160; &#160; 收集本地缓存的统计信息(这会增加系统运行负载),并通过/proc/fs/fscache/stats文件导出到用户空间.<br />&#160; &#160; &#160; &#160; &#160; &#160; 主要用于调试目的.<br />&#160; &#160; &#160; &#160; Gather latency information on local caching<br />&#160; &#160; &#160; &#160; CONFIG_FSCACHE_HISTOGRAM<br />&#160; &#160; &#160; &#160; &#160; &#160; 收集本地缓存的延迟信息(这会增加系统运行负载),并通过/proc/fs/fscache/histogram文件导出到用户空间.<br />&#160; &#160; &#160; &#160; &#160; &#160; 主要用于调试目的.<br />&#160; &#160; &#160; &#160; Debug FS-Cache<br />&#160; &#160; &#160; &#160; CONFIG_FSCACHE_DEBUG<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅供调试使用<br />&#160; &#160; &#160; &#160; Maintain global object list for debugging purposes<br />&#160; &#160; &#160; &#160; CONFIG_FSCACHE_OBJECT_LIST<br />&#160; &#160; &#160; &#160; &#160; &#160; 在/proc/fs/fscache/objects文件中维护一个活动缓存对象的全局列表.仅用于调试目的.<br />&#160; &#160; &#160; &#160; Filesystem caching on files<br />&#160; &#160; &#160; &#160; CONFIG_CACHEFILES<br />&#160; &#160; &#160; &#160; &#160; &#160; 将一个已挂载的文件系统用作另一个文件系统的缓存.<br />&#160; &#160; &#160; &#160; &#160; &#160; 例如将一个本地磁盘分区挂载为一个远程网络文件系统的缓存,<br />&#160; &#160; &#160; &#160; &#160; &#160; 或者将一个高速设备(例如SSD)用作一个低速设备(例如普通硬盘)的缓存.</p><p>&#160; &#160; &#160; &#160; &#160; &#160; Debug CacheFiles<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_CACHEFILES_DEBUG<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 仅供调试使用<br />&#160; &#160; &#160; &#160; &#160; &#160; Gather latency information on CacheFiles<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_CACHEFILES_HISTOGRAM<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 收集本地缓存的延迟信息(这会增加系统运行负载),<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 并通过/proc/fs/cachefiles/histogram文件导出到用户空间.主要用于调试目的.</p><p>CD-ROM/DVD Filesystems<br />&#160; &#160; CD-ROM/DVD光盘文件系统</p><p>&#160; &#160; ISO 9660 CDROM file system support<br />&#160; &#160; CONFIG_ISO9660_FS<br />&#160; &#160; &#160; &#160; ISO9660是所有CD/DVD光盘通用的标准文件系统.建议选&quot;Y&quot;.详见&quot;Documentation/filesystems/isofs.txt&quot;文档.</p><p>&#160; &#160; &#160; &#160; Microsoft Joliet CDROM extensions<br />&#160; &#160; &#160; &#160; CONFIG_JOLIET<br />&#160; &#160; &#160; &#160; &#160; &#160; Microsoft对ISO9660文件系统的Joliet扩展,允许在文件名中使用Unicode字符,也允许长文件名.建议选&quot;Y&quot;.<br />&#160; &#160; &#160; &#160; Transparent decompression extension<br />&#160; &#160; &#160; &#160; CONFIG_ZISOFS<br />&#160; &#160; &#160; &#160; &#160; &#160; Linux对ISO9660文件系统的扩展,允许将数据透明的压缩存储在CD上.使用并不广泛,不确定的可以选&quot;N&quot;.</p><p>&#160; &#160; UDF file system support<br />&#160; &#160; CONFIG_UDF_FS<br />&#160; &#160; &#160; &#160; UDF的目标是取代ISO9660,现已经广泛地用于大容量DVD光盘上(特别是刻录盘).<br />&#160; &#160; &#160; &#160; 建议选&quot;Y&quot;.详见&quot;Documentation/filesystems/udf.txt&quot;文档.</p><p>DOS/FAT/NT Filesystems<br />&#160; &#160; DOS/FAT/NTFS文件系统</p><p>&#160; &#160; MSDOS fs support<br />&#160; &#160; CONFIG_MSDOS_FS<br />&#160; &#160; &#160; &#160; 古老的MSDOS文件系统(FAT16),基本绝种了<br />&#160; &#160; VFAT (Windows-95) fs support<br />&#160; &#160; CONFIG_VFAT_FS<br />&#160; &#160; &#160; &#160; 从Win95开始使用的VFAT文件系统(FAT32).如果你要使用基于UEFI平台的电脑,<br />&#160; &#160; &#160; &#160; 并且使用GPT磁盘分区,则必须选&quot;Y&quot;.详见&quot;Documentation/filesystems/vfat.txt&quot;文档.</p><p>&#160; &#160; &#160; &#160; Default codepage for FAT<br />&#160; &#160; &#160; &#160; CONFIG_FAT_DEFAULT_CODEPAGE<br />&#160; &#160; &#160; &#160; &#160; &#160; 在FAT系列文件系统上,&quot;8.3&quot;格式的短文件名以特定的代码页进行存储(可以通过chcp命令查看),<br />&#160; &#160; &#160; &#160; &#160; &#160; 但长文件名却以Unicode进行存储.此选项的作用就是指定将长文件名转换为短文件名时使用的默认代码页.<br />&#160; &#160; &#160; &#160; &#160; &#160; 可以通过&quot;codepage&quot;挂载选项进行修改.简体中文通常使用&quot;936&quot;,繁体中文通常使用&quot;950&quot;.<br />&#160; &#160; &#160; &#160; Default iocharset for FAT<br />&#160; &#160; &#160; &#160; CONFIG_FAT_DEFAULT_IOCHARSET<br />&#160; &#160; &#160; &#160; &#160; &#160; 指定默认以什么字符集显示文件名,<br />&#160; &#160; &#160; &#160; &#160; &#160; 这个值可以通过&quot;iocharset&quot;挂载选项修改.但必须与系统的locale设置保持一致.<br />&#160; &#160; &#160; &#160; &#160; &#160; 例如在&quot;zh_CN.UTF-8&quot;或&quot;en_US.UTF-8&quot;的情况下应该使用&quot;utf8&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; [注意]应谨慎使用&quot;iocharset=utf8&quot;，因为它会导致FAT文件系统上的文件名变得大小写敏感。</p><p>&#160; &#160; NTFS file system support<br />&#160; &#160; CONFIG_NTFS_FS<br />&#160; &#160; &#160; &#160; NTFS文件系统.仅选中此项表示仅支持只读(不支持NTFS压缩或加密文件),不支持写入.<br />&#160; &#160; &#160; &#160; 详见&quot;Documentation/filesystems/ntfs.txt&quot;文档.</p><p>&#160; &#160; &#160; &#160; NTFS debugging support<br />&#160; &#160; &#160; &#160; CONFIG_NTFS_DEBUG<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅供调试使用<br />&#160; &#160; &#160; &#160; NTFS write support<br />&#160; &#160; &#160; &#160; CONFIG_NTFS_RW<br />&#160; &#160; &#160; &#160; &#160; &#160; 由于微软没有公开NTFS的技术标准,所以内核只能支持非常残缺的写入功能:<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅能覆盖已存在的文件但不能改变其长度,不能创建文件或目录.建议选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; [提示]在Linux环境下写入NTFS始终是一件危险的事情,即使对于NTFS-3G也是如此,<br />&#160; &#160; &#160; &#160; &#160; &#160; 除了不支持压缩或加密文件之外,网上还有不少血的教训,有兴趣可以搜搜.</p><p>Pseudo filesystems<br />&#160; &#160; 伪文件系统</p><p>&#160; &#160; /proc file system support<br />&#160; &#160; CONFIG_PROC_FS<br />&#160; &#160; &#160; &#160; 显示系统状态的虚拟文件系统(进程信息,irq设置,内存使用,设备驱动,网络状态等),通常挂载到&quot;/proc&quot;目录.<br />&#160; &#160; &#160; &#160; 许多程序依赖于它.选&quot;Y&quot;,除非你知道自己在做什么.详见&quot;Documentation/filesystems/proc.txt&quot;文档.</p><p>&#160; &#160; &#160; &#160; /proc/kcore support<br />&#160; &#160; &#160; &#160; CONFIG_PROC_KCORE<br />&#160; &#160; &#160; &#160; &#160; &#160; 系统物理内存的映象.建议选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; /proc/vmcore support<br />&#160; &#160; &#160; &#160; CONFIG_PROC_VMCORE<br />&#160; &#160; &#160; &#160; &#160; &#160; 以ELF格式转储的已崩溃内核镜像,仅供调试使用<br />&#160; &#160; &#160; &#160; Sysctl support (/proc/sys)<br />&#160; &#160; &#160; &#160; CONFIG_PROC_SYSCTL<br />&#160; &#160; &#160; &#160; &#160; &#160; 显示各种不同的内核调节参数,并让root用户能通过/proc/sys/目录交互地更改其中的某些内容.<br />&#160; &#160; &#160; &#160; &#160; &#160; 必选&quot;Y&quot;,除非你是嵌入式系统并且知道自己在做什么.详见&quot;Documentation/sysctl/&quot;目录中的文档.<br />&#160; &#160; &#160; &#160; Enable /proc page monitoring<br />&#160; &#160; &#160; &#160; CONFIG_PROC_PAGE_MONITOR<br />&#160; &#160; &#160; &#160; &#160; &#160; 用于监视进程内存占用的接口<br />&#160; &#160; &#160; &#160; &#160; &#160; (/proc/&lt;pid&gt;/{smaps,clear_refs,pagemap}和/proc/{kpagecount,kpageflags}).<br />&#160; &#160; &#160; &#160; &#160; &#160; 建议选&quot;Y&quot;.</p><p>&#160; &#160; sysfs file system support<br />&#160; &#160; CONFIG_SYSFS<br />&#160; &#160; &#160; &#160; 导出内核内部对象及其属性和对象之间的相互关系的文件系统,通常挂载到&quot;/sys&quot;目录,sysfs把连接在系统上的设备和总线以及驱动程序等组织成为一个分级的文件,并允许通过该文件系统调整某些内核子系统以及设备的参数.内核启动时依靠它挂载类似&quot;/dev/sda1&quot;这样形式的根分区,禁用sysfs后必须在内核引导参数中使用设备号指定根分区(类似&quot;root=03:01&quot;这样).选&quot;Y&quot;,除非你知道自己在做什么.详见&quot;Documentation/filesystems/&quot;目录中&quot;sysfs*.txt&quot;系列文档.<br />&#160; &#160; Tmpfs virtual memory file system support (former shm fs)<br />&#160; &#160; CONFIG_TMPFS<br />&#160; &#160; &#160; &#160; tmpfs文件系统(以前叫shm[共享内存]文件系统),大多数系统的正常运行都依赖于它<br />&#160; &#160; &#160; &#160; (例如Udev使用的&quot;/dev/&quot;目录通常挂载为tmpfs).选&quot;Y&quot;,除非你知道自己在做什么.<br />&#160; &#160; &#160; &#160; 详见&quot;Documentation/filesystems/tmpfs.txt&quot;文档.</p><p>&#160; &#160; &#160; &#160; Tmpfs POSIX Access Control Lists<br />&#160; &#160; &#160; &#160; CONFIG_TMPFS_POSIX_ACL<br />&#160; &#160; &#160; &#160; &#160; &#160; POSIX ACL(访问控制列表)支持,这是一种超越&quot;owner/group/world&quot;的权限管理方式,<br />&#160; &#160; &#160; &#160; &#160; &#160; 可以更精细的针对每个用户进行访问控制.<br />&#160; &#160; &#160; &#160; &#160; &#160; 详见acl手册.许多发行版都要求/dev/目录支持ACL(例如让ALSA相关的文件可以正常工作).不确定的选&quot;Y&quot;.<br />&#160; &#160; &#160; &#160; Tmpfs extended attributes<br />&#160; &#160; &#160; &#160; CONFIG_TMPFS_XATTR<br />&#160; &#160; &#160; &#160; &#160; &#160; TMPFS文件系统扩展属性(与inode关联的name:value对)支持(仅支持trusted.*和security.*命名空间).<br />&#160; &#160; &#160; &#160; &#160; &#160; 详见attr手册.由于它被CONFIG_TMPFS_POSIX_ACL依赖,所以选&quot;Y&quot;.</p><p>&#160; &#160; HugeTLB file system support<br />&#160; &#160; CONFIG_HUGETLBFS<br />&#160; &#160; &#160; &#160; 这是使用大内存页的传统方式,需要专门进行配置以及应用程序的特别支持.<br />&#160; &#160; &#160; &#160; 推荐使用较新的透明大内存页(CONFIG_TRANSPARENT_HUGEPAGE).选&quot;N&quot;.<br />&#160; &#160; Userspace-driven configuration filesystem<br />&#160; &#160; CONFIG_CONFIGFS_FS<br />&#160; &#160; &#160; &#160; configfs是一个基于内存的虚拟文件系统,与sysfs类似但又有不同:configfs用于<br />&#160; &#160; &#160; &#160; 从用户空间查看/修改/创建/删除内核对象,而sysfs仅能查看/修改由内核负责创建和删除的对象.<br />&#160; &#160; &#160; &#160; 通常挂载到&quot;/config&quot;目录.详见&quot;Documentation/configfs/&quot;目录中的文档.不确定的选&quot;N&quot;.</p><p>Miscellaneous filesystems<br />CONFIG_MISC_FILESYSTEMS<br />&#160; &#160; 各种非主流的杂项文件系统,有些是专用于嵌入式系统,有些是来自于其他操作系统,还有些专用于某些特定场合.<br />&#160; &#160; {此处省略哪些非常非主流的文件系统}<br />&#160; &#160; eCrypt filesystem layer support<br />&#160; &#160; CONFIG_ECRYPT_FS<br />&#160; &#160; &#160; &#160; eCryptfs是一个符合POSIX标准的企业级文件系统加密栈(加密/解密转换层),工作在VFS(虚拟文件系统)层,<br />&#160; &#160; &#160; &#160; 可以在各种普通文件系统上使用(需要ecryptfs-utils工具).eCryptfs将加密元数据保存在每个文件的首部,<br />&#160; &#160; &#160; &#160; 从而允许文件在不同主机之间任意移动,同时又能确保仅在内核密钥环中拥有正确密钥的时候才能解密文件<br />&#160; &#160; &#160; &#160; 的内容.此外,eCryptfs还支持高级密匙管理和配置策略.[提示]使用eCryptfs之后,读操作性能最大可<br />&#160; &#160; &#160; &#160; 下降1/3左右,写操作性能则普遍下降一个数量级.</p><p>&#160; &#160; &#160; &#160; Enable notifications for userspace key wrap/unwrap<br />&#160; &#160; &#160; &#160; CONFIG_ECRYPT_FS_MESSAGING<br />&#160; &#160; &#160; &#160; &#160; &#160; 允许ecryptfsd守护进程操作/dev/ecryptfs设备.<br />&#160; &#160; &#160; &#160; &#160; &#160; 这将允许用户空间使用其他后端(例如OpenSSL)加密/解密FEK(file encryption key).不确定的选&quot;N&quot;.</p><p>&#160; &#160; SquashFS 4.0 - Squashed file system support<br />&#160; &#160; CONFIG_SQUASHFS<br />&#160; &#160; &#160; &#160; SquashFS是一种高压缩率的只读文件系统,可以使用多种压缩算法(例如zlib,xz,lzo).<br />&#160; &#160; &#160; &#160; SquashFS常用于嵌入式设备和LiveCD系统.</p><p>&#160; &#160; &#160; &#160; Squashfs XATTR support<br />&#160; &#160; &#160; &#160; CONFIG_SQUASHFS_XATTR<br />&#160; &#160; &#160; &#160; &#160; &#160; Squashfs文件系统扩展属性(与inode关联的name:value对)支持.详见attr手册.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; Include support for ZLIB compressed file systems<br />&#160; &#160; &#160; &#160; CONFIG_SQUASHFS_ZLIB<br />&#160; &#160; &#160; &#160; &#160; &#160; ZLIB是Squashfs默认的标准压缩算法.在压缩率和性能之间达到了最佳的平衡.<br />&#160; &#160; &#160; &#160; Include support for LZO compressed file systems<br />&#160; &#160; &#160; &#160; CONFIG_SQUASHFS_LZO<br />&#160; &#160; &#160; &#160; &#160; &#160; LZO是性能最佳的压缩算法(CPU和内存占用都很低),但是压缩率确是最差的.常用于资源有限的嵌入式系统.<br />&#160; &#160; &#160; &#160; Include support for XZ compressed file systems<br />&#160; &#160; &#160; &#160; CONFIG_SQUASHFS_XZ<br />&#160; &#160; &#160; &#160; &#160; &#160; XZ是压缩率最佳的压缩算法,但其CPU和内存占用都最高.可用于PC环境.<br />&#160; &#160; &#160; &#160; Use 4K device block size?<br />&#160; &#160; &#160; &#160; CONFIG_SQUASHFS_4K_DEVBLK_SIZE<br />&#160; &#160; &#160; &#160; &#160; &#160; 出于降低潜伏时间的考虑,Squashfs默认使用1K大小的块.但是在MTD NAND设备上,<br />&#160; &#160; &#160; &#160; &#160; &#160; 使用4K大小的块才可以获得最佳性能.此外,在大多数设备上,<br />&#160; &#160; &#160; &#160; &#160; &#160; 使用4K大小的块才能获得最佳连续读取性能.如果你的Squashfs位于闪存设备上,建议选&quot;Y&quot;.否则建议选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; Additional option for memory-constrained systems<br />&#160; &#160; &#160; &#160; CONFIG_SQUASHFS_EMBEDDED<br />&#160; &#160; &#160; &#160; &#160; &#160; 允许强制指定缓存大小.不确定的选&quot;N&quot;.</p><p>&#160; &#160; &#160; &#160; &#160; &#160; Number of fragments cached<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; SquashFS默认缓存最后3个从文件系统上读取的片段.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 降低此值(最小值是&quot;1&quot;,不能设为&quot;0&quot;)可以降低内存的占用,但是会增加底层物理设备的读取次数.<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; 增加此值则正好相反.[提示]按一般经验,大于&quot;3&quot;的值并不能带来显著的性能提升.</p><p>&#160; &#160; EFI Variable filesystem<br />&#160; &#160; CONFIG_EFIVAR_FS<br />&#160; &#160; &#160; &#160; efivarfs可以取代通过sysfs(CONFIG_EFI_VARS)展示的&quot;EFI变量&quot;,<br />&#160; &#160; &#160; &#160; 其主要目的是可以突破sysfs中变量值不能超出1024字节的限制.不确定的选&quot;N&quot;.</p><p>Network File Systems<br />CONFIG_NETWORK_FILESYSTEMS<br />&#160; &#160; 网络文件系统</p><p>&#160; &#160; NFS client support<br />&#160; &#160; CONFIG_NFS_FS<br />&#160; &#160; &#160; &#160; NFS(Network File System)客户端支持,<br />&#160; &#160; &#160; &#160; 这样就可以使用nfs-utils包中的mount.nfs工具挂载远程服务器提供的NFS文件系统.详见nfs手册页.</p><p>&#160; &#160; &#160; &#160; NFS client support for NFS version 2<br />&#160; &#160; &#160; &#160; CONFIG_NFS_V2<br />&#160; &#160; &#160; &#160; &#160; &#160; NFSv2(RFC 1094)版本协议支持<br />&#160; &#160; &#160; &#160; NFS client support for NFS version 3<br />&#160; &#160; &#160; &#160; CONFIG_NFS_V3<br />&#160; &#160; &#160; &#160; &#160; &#160; NFSv3(RFC 1813)版本协议支持</p><p>&#160; &#160; &#160; &#160; &#160; &#160; NFS client support for the NFSv3 ACL protocol extension<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NFS_V3_ACL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 为NFSv3添加POSIX ACL支持(Solaris NFSv3 ACL).大多数NFS服务器都不支持这个扩展.不确定的选&quot;N&quot;.</p><p>&#160; &#160; &#160; &#160; NFS client support for NFS version 4<br />&#160; &#160; &#160; &#160; CONFIG_NFS_V4<br />&#160; &#160; &#160; &#160; &#160; &#160; NFSv4(RFC 3530)版本协议支持<br />&#160; &#160; &#160; &#160; Provide swap over NFS support<br />&#160; &#160; &#160; &#160; CONFIG_NFS_SWAP<br />&#160; &#160; &#160; &#160; &#160; &#160; 允许将NFS文件系统用做swap分区.</p><p>&#160; &#160; NFS client support for NFSv4.1<br />&#160; &#160; CONFIG_NFS_V4_1<br />&#160; &#160; &#160; &#160; NFSv4.1(RFC 5661)版本协议客户端支持,<br />&#160; &#160; &#160; &#160; 这样就可以使用nfs-utils包中的mount.nfs工具挂载远程服务器提供的NFS文件系统.<br />&#160; &#160; &#160; &#160; 详见nfs手册页以及NFS各个版本之间的比较.</p><p>&#160; &#160; &#160; &#160; NFSv4.1 Implementation ID Domain<br />&#160; &#160; &#160; &#160; CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN<br />&#160; &#160; &#160; &#160; &#160; &#160; NFSv4.1规范新引入了会话机制,该选项定义在建立会话过程中使用在EXCHANGE_ID指令中的&quot;domain&quot;部分的值.<br />&#160; &#160; &#160; &#160; &#160; &#160; 这个值必须是个标准的DNS域名格式.如果你没有修改内核的NFS客户端代码,那么请保持默认值&quot;kernel.org&quot;.</p><p>&#160; &#160; Root file system on NFS<br />&#160; &#160; CONFIG_ROOT_NFS<br />&#160; &#160; &#160; &#160; 允许将NFS挂载为根文件系统(root=/dev/nfs),<br />&#160; &#160; &#160; &#160; 通常用于没有本地存储设备的无盘工作站(还必须开启CONFIG_IP_PNP以及至少一个子项).<br />&#160; &#160; &#160; &#160; 详见&quot;Documentation/filesystems/nfs/nfsroot.txt&quot;文档.<br />&#160; &#160; Provide NFS client caching support<br />&#160; &#160; CONFIG_NFS_FSCACHE<br />&#160; &#160; &#160; &#160; 为NFS提供本地缓存支持,也就是利用CONFIG_FSCACHE选项的功能.<br />&#160; &#160; Use the legacy NFS DNS resolver<br />&#160; &#160; CONFIG_NFS_USE_LEGACY_DNS<br />&#160; &#160; &#160; &#160; 内核现在有自己的DNS解析实现,如果你依然想使用老式的DNS解析脚本,可以选&quot;Y&quot;.不确定的选&quot;N&quot;.<br />&#160; &#160; NFS server support<br />&#160; &#160; CONFIG_NFSD<br />&#160; &#160; &#160; &#160; NFS服务器端支持.要实现此功能,还需要nfs-utils软件包的支持.<br />&#160; &#160; &#160; &#160; 详见nfs手册页.这里也有一个NFS文章系列可以看看.此选项内嵌了NFSv2协议支持.</p><p>&#160; &#160; &#160; &#160; NFS server support for NFS version 3<br />&#160; &#160; &#160; &#160; CONFIG_NFSD_V3<br />&#160; &#160; &#160; &#160; &#160; &#160; NFSv3(RFC 1813)版本协议支持</p><p>&#160; &#160; &#160; &#160; &#160; &#160; NFS server support for the NFSv3 ACL protocol extension<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NFSD_V3_ACL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 为NFSv3添加POSIX ACL支持(Solaris NFSv3 ACL).此扩展并不属于NFSv3协议的官方内容.</p><p>&#160; &#160; &#160; &#160; NFS server support for NFS version 4<br />&#160; &#160; &#160; &#160; CONFIG_NFSD_V4<br />&#160; &#160; &#160; &#160; &#160; &#160; NFSv4(RFC 3530)版本协议支持</p><p>&#160; &#160; &#160; &#160; &#160; &#160; NFS server manual fault injection<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_NFSD_FAULT_INJECTION<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 仅供调试使用</p><p>&#160; &#160; Secure RPC: Kerberos V mechanism<br />&#160; &#160; CONFIG_RPCSEC_GSS_KRB5<br />&#160; &#160; &#160; &#160; 为使用Kerberos V5 GSS-API身份验证机制(RFC1964)的安全RPC提供支持.<br />&#160; &#160; &#160; &#160; 要实现此功能,还需要nfs-utils软件包以及用户空间的Kerberos支持.<br />&#160; &#160; RPC: Enable dprintk debugging<br />&#160; &#160; CONFIG_SUNRPC_DEBUG<br />&#160; &#160; &#160; &#160; 允许使用rpcdebug工具调试RPC故障,如果选&quot;N&quot;会让故障调试特别困难.<br />&#160; &#160; Ceph distributed file system<br />&#160; &#160; CONFIG_CEPH_FS<br />&#160; &#160; &#160; &#160; 允许挂载Ceph分布式文件系统.不确定的选&quot;N&quot;.详见&quot;Documentation/filesystems/ceph.txt&quot;文档.<br />&#160; &#160; CIFS support (advanced network filesystem, SMBFS successor)<br />&#160; &#160; CONFIG_CIFS<br />&#160; &#160; &#160; &#160; CIFS(Common Internet File System)协议客户端支持.CIFS主要用于Linux与Windows之间共享文件系统.<br />&#160; &#160; &#160; &#160; 如果你打算挂载Windows的共享文件夹,或者由Samba提供的文件系统,就选&quot;Y&quot;.<br />&#160; &#160; &#160; &#160; 详见&quot;Documentation/filesystems/cifs.txt&quot;文档.</p><p>&#160; &#160; &#160; &#160; CIFS statistics<br />&#160; &#160; &#160; &#160; CONFIG_CIFS_STATS<br />&#160; &#160; &#160; &#160; &#160; &#160; 在/proc/fs/cifs/Stats文件中显示每个被挂载的CIFS文件系统的统计信息</p><p>&#160; &#160; &#160; &#160; &#160; &#160; Extended statistics<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_CIFS_STATS2<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 在/proc/fs/cifs/目录下显示更详细的统计信息.对运行性能和内存占用都有些影响.不确定的选&quot;N&quot;.</p><p>&#160; &#160; &#160; &#160; Support legacy servers which use weaker LANMAN security<br />&#160; &#160; &#160; &#160; CONFIG_CIFS_WEAK_PW_HASH<br />&#160; &#160; &#160; &#160; &#160; &#160; 选&quot;N&quot;,除非你确实知道自己在干什么.<br />&#160; &#160; &#160; &#160; Kerberos/SPNEGO advanced session setup<br />&#160; &#160; &#160; &#160; CONFIG_CIFS_UPCALL<br />&#160; &#160; &#160; &#160; &#160; &#160; Kerberos/SPNEGO高级会话支持.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; CIFS extended attributes<br />&#160; &#160; &#160; &#160; CONFIG_CIFS_XATTR<br />&#160; &#160; &#160; &#160; &#160; &#160; CIFS文件系统扩展属性(与inode关联的name:value对)支持.不确定的选&quot;N&quot;.</p><p>&#160; &#160; &#160; &#160; &#160; &#160; CIFS POSIX Extensions<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_CIFS_POSIX<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; CIFS POSIX扩展.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; &#160; &#160; Provide CIFS ACL support<br />&#160; &#160; &#160; &#160; &#160; &#160; CONFIG_CIFS_ACL<br />&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 允许从服务器抓取CIFS/NTFS ACL.不确定的选&quot;N&quot;.</p><p>&#160; &#160; &#160; &#160; Enable CIFS debugging routines<br />&#160; &#160; &#160; &#160; CONFIG_CIFS_DEBUG<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅供调试使用<br />&#160; &#160; &#160; &#160; DFS feature support<br />&#160; &#160; &#160; &#160; CONFIG_CIFS_DFS_UPCALL<br />&#160; &#160; &#160; &#160; &#160; &#160; DFS(Distributed File System)支持.不确定的选&quot;N&quot;.<br />&#160; &#160; &#160; &#160; SMB2 network file system support<br />&#160; &#160; &#160; &#160; CONFIG_CIFS_SMB2<br />&#160; &#160; &#160; &#160; &#160; &#160; 仅供开发与调试使用</p><p>&#160; &#160; Provide CIFS client caching support<br />&#160; &#160; CONFIG_CIFS_FSCACHE<br />&#160; &#160; &#160; &#160; 为CIFS提供本地缓存支持,也就是利用CONFIG_FSCACHE选项的功能.<br />&#160; &#160; NCP file system support (to mount NetWare volumes)<br />&#160; &#160; CONFIG_NCP_FS<br />&#160; &#160; &#160; &#160; NCP(NetWare Core Protocol)协议支持.这东西早就销声匿迹了,选&quot;N&quot;.<br />&#160; &#160; Coda file system support (advanced network fs)<br />&#160; &#160; CONFIG_CODA_FS<br />&#160; &#160; &#160; &#160; Coda是一种比NFS更先进的分布式集群文件系统.LVS(Linux Virtual Server)就采用了Coda分布式文件系统.详见&quot;Documentation/filesystems/coda.txt&quot;文档.<br />&#160; &#160; Andrew File System support<br />&#160; &#160; CONFIG_AFS_FS<br />&#160; &#160; &#160; &#160; AFS(Andrew File System)文件系统的实验性支持,目前仅支持只读访问.详见&quot;Documentation/filesystems/afs.txt&quot;文档.<br />&#160; &#160; Provide AFS client caching support<br />&#160; &#160; CONFIG_AFS_FSCACHE<br />&#160; &#160; &#160; &#160; 为AFS提供本地缓存支持,也就是利用CONFIG_FSCACHE选项的功能.<br />&#160; &#160; Plan 9 Resource Sharing Support (9P2000)<br />&#160; &#160; CONFIG_9P_FS<br />&#160; &#160; &#160; &#160; 9P2000协议是Plan 9概念网络操作系统上使用的资源共享协议.不确定的选&quot;N&quot;.</p><p>Native language support<br />CONFIG_NLS<br />&#160; &#160; 本地语言支持.仅在你使用FAT/NTFS/JOLIET文件系统的情况下才需要这个东西.</p><p>&#160; &#160; Default NLS Option<br />&#160; &#160; CONFIG_NLS_DEFAULT<br />&#160; &#160; &#160; &#160; 挂载文件系统时,控制台的默认本地语言(不是文件系统用于存储文件名的语言),建议设为&quot;utf8&quot;<br />&#160; &#160; &#160; &#160; (因为控制台的默认编码是&quot;utf8&quot;:vt.default_utf8=1).<br />&#160; &#160; {此处省略的各种字符集请按需选择}</p><p>Distributed Lock Manager (DLM)<br />CONFIG_DLM<br />&#160; &#160; 通用的分布式锁管理器(DLM).用于为各种分布式文件系统提供通用的锁定支持.</p><p>&#160; &#160; DLM debugging<br />&#160; &#160; CONFIG_DLM_DEBUG<br />&#160; &#160; &#160; &#160; 仅供开发与调试使用</p>]]></description>
			<author><![CDATA[dummy@example.com (batsom)]]></author>
			<pubDate>Wed, 03 Aug 2022 14:36:10 +0000</pubDate>
			<guid>http://www.gentoo-zh.org/viewtopic.php?pid=15#p15</guid>
		</item>
	</channel>
</rss>
