1 # SPDX-License-Identifier: GPL-2.0-only <<
2 # 1 #
3 # File system configuration 2 # File system configuration
4 # 3 #
5 4
6 menu "File systems" 5 menu "File systems"
7 6
8 # Use unaligned word dcache accesses !! 7 config EXT2_FS
9 config DCACHE_WORD_ACCESS !! 8 tristate "Second extended fs support"
10 bool !! 9 help
>> 10 This is the de facto standard Linux file system (method to organize
>> 11 files on a storage device) for hard disks.
11 12
12 config VALIDATE_FS_PARSER !! 13 You want to say Y here, unless you intend to use Linux exclusively
13 bool "Validate filesystem parameter de !! 14 from inside a DOS partition using the UMSDOS file system. The
>> 15 advantage of the latter is that you can get away without
>> 16 repartitioning your hard drive (which often implies backing
>> 17 everything up and restoring afterwards); the disadvantage is that
>> 18 Linux becomes susceptible to DOS viruses and that UMSDOS is somewhat
>> 19 slower than ext2fs. Even if you want to run Linux in this fashion,
>> 20 it might be a good idea to have ext2fs around: it enables you to
>> 21 read more floppy disks and facilitates the transition to a *real*
>> 22 Linux partition later. Another (rare) case which doesn't require
>> 23 ext2fs is a diskless Linux box which mounts all files over the
>> 24 network using NFS (in this case it's sufficient to say Y to "NFS
>> 25 file system support" below). Saying Y here will enlarge your kernel
>> 26 by about 44 KB.
>> 27
>> 28 The Ext2fs-Undeletion mini-HOWTO, available from
>> 29 <http://www.tldp.org/docs.html#howto>, gives information about
>> 30 how to retrieve deleted files on ext2fs file systems.
>> 31
>> 32 To change the behavior of ext2 file systems, you can use the tune2fs
>> 33 utility ("man tune2fs"). To modify attributes of files and
>> 34 directories on ext2 file systems, use chattr ("man chattr").
>> 35
>> 36 Ext2fs partitions can be read from within DOS using the ext2tool
>> 37 command line tool package (available from
>> 38 <ftp://ibiblio.org/pub/Linux/system/filesystems/ext2/>) and from
>> 39 within Windows NT using the ext2nt command line tool package from
>> 40 <ftp://ibiblio.org/pub/Linux/utils/dos/>. Explore2fs is a
>> 41 graphical explorer for ext2fs partitions which runs on Windows 95
>> 42 and Windows NT and includes experimental write support; it is
>> 43 available from
>> 44 <http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm>.
>> 45
>> 46 To compile this file system support as a module, choose M here: the
>> 47 module will be called ext2. Be aware however that the file system
>> 48 of your root partition (the one containing the directory /) cannot
>> 49 be compiled as a module, and so this could be dangerous. Most
>> 50 everyone wants to say Y here.
>> 51
>> 52 config EXT2_FS_XATTR
>> 53 bool "Ext2 extended attributes"
>> 54 depends on EXT2_FS
14 help 55 help
15 Enable this to perform validation of !! 56 Extended attributes are name:value pairs associated with inodes by
16 filesystem when it is registered. !! 57 the kernel or by users (see the attr(5) manual page, or visit
>> 58 <http://acl.bestbits.at/> for details).
17 59
18 config FS_IOMAP !! 60 If unsure, say N.
19 bool <<
20 61
21 # Stackable filesystems !! 62 config EXT2_FS_POSIX_ACL
22 config FS_STACK !! 63 bool "Ext2 POSIX Access Control Lists"
23 bool !! 64 depends on EXT2_FS_XATTR
>> 65 help
>> 66 Posix Access Control Lists (ACLs) support permissions for users and
>> 67 groups beyond the owner/group/world scheme.
24 68
25 config BUFFER_HEAD !! 69 To learn more about Access Control Lists, visit the Posix ACLs for
26 bool !! 70 Linux website <http://acl.bestbits.at/>.
27 71
28 # old blockdev_direct_IO implementation. Use !! 72 If you don't know what Access Control Lists are, say N
29 config LEGACY_DIRECT_IO !! 73
30 depends on BUFFER_HEAD !! 74 config EXT2_FS_SECURITY
31 bool !! 75 bool "Ext2 Security Labels"
>> 76 depends on EXT2_FS_XATTR
>> 77 help
>> 78 Security labels support alternative access control models
>> 79 implemented by security modules like SELinux. This option
>> 80 enables an extended attribute handler for file security
>> 81 labels in the ext2 filesystem.
>> 82
>> 83 If you are not using a security module that requires using
>> 84 extended attributes for file security labels, say N.
>> 85
>> 86 config EXT3_FS
>> 87 tristate "Ext3 journalling file system support"
>> 88 help
>> 89 This is the journaling version of the Second extended file system
>> 90 (often called ext3), the de facto standard Linux file system
>> 91 (method to organize files on a storage device) for hard disks.
>> 92
>> 93 The journaling code included in this driver means you do not have
>> 94 to run e2fsck (file system checker) on your file systems after a
>> 95 crash. The journal keeps track of any changes that were being made
>> 96 at the time the system crashed, and can ensure that your file system
>> 97 is consistent without the need for a lengthy check.
>> 98
>> 99 Other than adding the journal to the file system, the on-disk format
>> 100 of ext3 is identical to ext2. It is possible to freely switch
>> 101 between using the ext3 driver and the ext2 driver, as long as the
>> 102 file system has been cleanly unmounted, or e2fsck is run on the file
>> 103 system.
>> 104
>> 105 To add a journal on an existing ext2 file system or change the
>> 106 behavior of ext3 file systems, you can use the tune2fs utility ("man
>> 107 tune2fs"). To modify attributes of files and directories on ext3
>> 108 file systems, use chattr ("man chattr"). You need to be using
>> 109 e2fsprogs version 1.20 or later in order to create ext3 journals
>> 110 (available at <http://sourceforge.net/projects/e2fsprogs/>).
>> 111
>> 112 To compile this file system support as a module, choose M here: the
>> 113 module will be called ext3. Be aware however that the file system
>> 114 of your root partition (the one containing the directory /) cannot
>> 115 be compiled as a module, and so this may be dangerous.
>> 116
>> 117 config EXT3_FS_XATTR
>> 118 bool "Ext3 extended attributes"
>> 119 depends on EXT3_FS
>> 120 default y
>> 121 help
>> 122 Extended attributes are name:value pairs associated with inodes by
>> 123 the kernel or by users (see the attr(5) manual page, or visit
>> 124 <http://acl.bestbits.at/> for details).
>> 125
>> 126 If unsure, say N.
>> 127
>> 128 You need this for POSIX ACL support on ext3.
>> 129
>> 130 config EXT3_FS_POSIX_ACL
>> 131 bool "Ext3 POSIX Access Control Lists"
>> 132 depends on EXT3_FS_XATTR
>> 133 help
>> 134 Posix Access Control Lists (ACLs) support permissions for users and
>> 135 groups beyond the owner/group/world scheme.
32 136
33 if BLOCK !! 137 To learn more about Access Control Lists, visit the Posix ACLs for
>> 138 Linux website <http://acl.bestbits.at/>.
34 139
35 source "fs/ext2/Kconfig" !! 140 If you don't know what Access Control Lists are, say N
36 source "fs/ext4/Kconfig" !! 141
37 source "fs/jbd2/Kconfig" !! 142 config EXT3_FS_SECURITY
>> 143 bool "Ext3 Security Labels"
>> 144 depends on EXT3_FS_XATTR
>> 145 help
>> 146 Security labels support alternative access control models
>> 147 implemented by security modules like SELinux. This option
>> 148 enables an extended attribute handler for file security
>> 149 labels in the ext3 filesystem.
>> 150
>> 151 If you are not using a security module that requires using
>> 152 extended attributes for file security labels, say N.
>> 153
>> 154 config JBD
>> 155 # CONFIG_JBD could be its own option (even modular), but until there are
>> 156 # other users than ext3, we will simply make it be the same as CONFIG_EXT3_FS
>> 157 # dep_tristate ' Journal Block Device support (JBD for ext3)' CONFIG_JBD $CONFIG_EXT3_FS
>> 158 tristate
>> 159 default EXT3_FS
>> 160 help
>> 161 This is a generic journaling layer for block devices. It is
>> 162 currently used by the ext3 file system, but it could also be used to
>> 163 add journal support to other file systems or block devices such as
>> 164 RAID or LVM.
>> 165
>> 166 If you are using the ext3 file system, you need to say Y here. If
>> 167 you are not using ext3 then you will probably want to say N.
>> 168
>> 169 To compile this device as a module, choose M here: the module will be
>> 170 called jbd. If you are compiling ext3 into the kernel, you cannot
>> 171 compile this code as a module.
>> 172
>> 173 config JBD_DEBUG
>> 174 bool "JBD (ext3) debugging support"
>> 175 depends on JBD
>> 176 help
>> 177 If you are using the ext3 journaled file system (or potentially any
>> 178 other file system/device using JBD), this option allows you to
>> 179 enable debugging output while the system is running, in order to
>> 180 help track down any problems you are having. By default the
>> 181 debugging output will be turned off.
>> 182
>> 183 If you select Y here, then you will be able to turn on debugging
>> 184 with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
>> 185 1 and 5, the higher the number, the more debugging output is
>> 186 generated. To turn debugging off again, do
>> 187 "echo 0 > /proc/sys/fs/jbd-debug".
38 188
39 config FS_MBCACHE 189 config FS_MBCACHE
40 # Meta block cache for Extended Attributes (ex !! 190 # Meta block cache for Extended Attributes (ext2/ext3)
41 tristate 191 tristate
42 default y if EXT2_FS=y && EXT2_FS_XATT !! 192 depends on EXT2_FS_XATTR || EXT3_FS_XATTR
43 default y if EXT4_FS=y !! 193 default y if EXT2_FS=y || EXT3_FS=y
44 default m if EXT2_FS_XATTR || EXT4_FS !! 194 default m if EXT2_FS=m || EXT3_FS=m
45 <<
46 source "fs/reiserfs/Kconfig" <<
47 source "fs/jfs/Kconfig" <<
48 <<
49 source "fs/xfs/Kconfig" <<
50 source "fs/gfs2/Kconfig" <<
51 source "fs/ocfs2/Kconfig" <<
52 source "fs/btrfs/Kconfig" <<
53 source "fs/nilfs2/Kconfig" <<
54 source "fs/f2fs/Kconfig" <<
55 source "fs/bcachefs/Kconfig" <<
56 source "fs/zonefs/Kconfig" <<
57 <<
58 endif # BLOCK <<
59 <<
60 config FS_DAX <<
61 bool "File system based Direct Access <<
62 depends on MMU <<
63 depends on ZONE_DEVICE || FS_DAX_LIMIT <<
64 select FS_IOMAP <<
65 select DAX <<
66 help <<
67 Direct Access (DAX) can be used on m <<
68 If the block device supports DAX and <<
69 then you can avoid using the pagecac <<
70 on this option will compile in suppo <<
71 <<
72 For a DAX device to support file sys <<
73 struct pages. For the nfit based NV <<
74 using the ndctl utility: <<
75 <<
76 # ndctl create-namespace --for <<
77 --mode=fsdax --map=mem <<
78 <<
79 See the 'create-namespace' man page <<
80 --map=mem: <<
81 https://docs.pmem.io/ndctl-user-guid <<
82 <<
83 For ndctl to work CONFIG_DEV_DAX nee <<
84 file systems DAX support needs to be <<
85 per-inode using a mount option as we <<
86 Documentation/filesystems/dax.rst fo <<
87 <<
88 If you do not have a block device th <<
89 or if unsure, say N. Saying Y will <<
90 by about 5kB. <<
91 195
92 config FS_DAX_PMD !! 196 config REISERFS_FS
93 bool !! 197 tristate "Reiserfs support"
94 default FS_DAX !! 198 help
95 depends on FS_DAX !! 199 Stores not just filenames but the files themselves in a balanced
96 depends on ZONE_DEVICE !! 200 tree. Uses journaling.
97 depends on TRANSPARENT_HUGEPAGE !! 201
98 !! 202 Balanced trees are more efficient than traditional file system
99 # Selected by DAX drivers that do not expect f !! 203 architectural foundations.
100 # get_user_pages() of DAX mappings. I.e. "limi !! 204
101 # for fork() of processes with MAP_SHARED mapp !! 205 In general, ReiserFS is as fast as ext2, but is very efficient with
102 # direct-I/O to a DAX mapping. !! 206 large directories and small files. Additional patches are needed
103 config FS_DAX_LIMITED !! 207 for NFS and quotas, please see <http://www.namesys.com/> for links.
104 bool !! 208
>> 209 It is more easily extended to have features currently found in
>> 210 database and keyword search systems than block allocation based file
>> 211 systems are. The next version will be so extended, and will support
>> 212 plugins consistent with our motto ``It takes more than a license to
>> 213 make source code open.''
>> 214
>> 215 Read <http://www.namesys.com/> to learn more about reiserfs.
>> 216
>> 217 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
>> 218
>> 219 If you like it, you can pay us to add new features to it that you
>> 220 need, buy a support contract, or pay us to port it to another OS.
105 221
106 # Posix ACL utility routines !! 222 config REISERFS_CHECK
>> 223 bool "Enable reiserfs debug mode"
>> 224 depends on REISERFS_FS
>> 225 help
>> 226 If you set this to Y, then ReiserFS will perform every check it can
>> 227 possibly imagine of its internal consistency throughout its
>> 228 operation. It will also go substantially slower. More than once we
>> 229 have forgotten that this was on, and then gone despondent over the
>> 230 latest benchmarks.:-) Use of this option allows our team to go all
>> 231 out in checking for consistency when debugging without fear of its
>> 232 effect on end users. If you are on the verge of sending in a bug
>> 233 report, say Y and you might get a useful error message. Almost
>> 234 everyone should say N.
>> 235
>> 236 config REISERFS_PROC_INFO
>> 237 bool "Stats in /proc/fs/reiserfs"
>> 238 depends on REISERFS_FS
>> 239 help
>> 240 Create under /proc/fs/reiserfs a hierarchy of files, displaying
>> 241 various ReiserFS statistics and internal data at the expense of
>> 242 making your kernel or module slightly larger (+8 KB). This also
>> 243 increases the amount of kernel memory required for each mount.
>> 244 Almost everyone but ReiserFS developers and people fine-tuning
>> 245 reiserfs or tracing problems should say N.
>> 246
>> 247 config JFS_FS
>> 248 tristate "JFS filesystem support"
>> 249 help
>> 250 This is a port of IBM's Journaled Filesystem . More information is
>> 251 available in the file Documentation/filesystems/jfs.txt.
>> 252
>> 253 If you do not intend to use the JFS filesystem, say N.
>> 254
>> 255 config JFS_POSIX_ACL
>> 256 bool "JFS POSIX Access Control Lists"
>> 257 depends on JFS_FS
>> 258 help
>> 259 Posix Access Control Lists (ACLs) support permissions for users and
>> 260 groups beyond the owner/group/world scheme.
>> 261
>> 262 To learn more about Access Control Lists, visit the Posix ACLs for
>> 263 Linux website <http://acl.bestbits.at/>.
>> 264
>> 265 If you don't know what Access Control Lists are, say N
>> 266
>> 267 config JFS_DEBUG
>> 268 bool "JFS debugging"
>> 269 depends on JFS_FS
>> 270 help
>> 271 If you are experiencing any problems with the JFS filesystem, say
>> 272 Y here. This will result in additional debugging messages to be
>> 273 written to the system log. Under normal circumstances, this
>> 274 results in very little overhead.
>> 275
>> 276 config JFS_STATISTICS
>> 277 bool "JFS statistics"
>> 278 depends on JFS_FS
>> 279 help
>> 280 Enabling this option will cause statistics from the JFS file system
>> 281 to be made available to the user in the /proc/fs/jfs/ directory.
>> 282
>> 283 config FS_POSIX_ACL
>> 284 # Posix ACL utility routines (for now, only ext2/ext3/jfs)
107 # 285 #
108 # Note: Posix ACLs can be implemented without !! 286 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
109 # this symbol for ifdefs in core code. !! 287 # Never use this symbol for ifdefs.
110 # 288 #
111 config FS_POSIX_ACL !! 289 bool
112 def_bool n !! 290 depends on EXT2_FS_POSIX_ACL || EXT3_FS_POSIX_ACL || JFS_POSIX_ACL
>> 291 default y
113 292
114 config EXPORTFS !! 293 config XFS_FS
115 tristate !! 294 tristate "XFS filesystem support"
>> 295 help
>> 296 XFS is a high performance journaling filesystem which originated
>> 297 on the SGI IRIX platform. It is completely multi-threaded, can
>> 298 support large files and large filesystems, extended attributes,
>> 299 variable block sizes, is extent based, and makes extensive use of
>> 300 Btrees (directories, extents, free space) to aid both performance
>> 301 and scalability.
>> 302
>> 303 Refer to the documentation at <http://oss.sgi.com/projects/xfs/>
>> 304 for complete details. This implementation is on-disk compatible
>> 305 with the IRIX version of XFS.
>> 306
>> 307 To compile this file system support as a module, choose M here: the
>> 308 module will be called xfs. Be aware, however, that if the file
>> 309 system of your root partition is compiled as a module, you'll need
>> 310 to use an initial ramdisk (initrd) to boot.
>> 311
>> 312 config XFS_RT
>> 313 bool "Realtime support (EXPERIMENTAL)"
>> 314 depends on XFS_FS && EXPERIMENTAL
>> 315 help
>> 316 If you say Y here you will be able to mount and use XFS filesystems
>> 317 which contain a realtime subvolume. The realtime subvolume is a
>> 318 separate area of disk space where only file data is stored. The
>> 319 realtime subvolume is designed to provide very deterministic
>> 320 data rates suitable for media streaming applications.
>> 321
>> 322 See the xfs man page in section 5 for a bit more information.
>> 323
>> 324 This feature is unsupported at this time, is not yet fully
>> 325 functional, and may cause serious problems.
>> 326
>> 327 If unsure, say N.
>> 328
>> 329 config XFS_QUOTA
>> 330 bool "Quota support"
>> 331 depends on XFS_FS
>> 332 help
>> 333 If you say Y here, you will be able to set limits for disk usage on
>> 334 a per user and/or a per group basis under XFS. XFS considers quota
>> 335 information as filesystem metadata and uses journaling to provide a
>> 336 higher level guarantee of consistency. The on-disk data format for
>> 337 quota is also compatible with the IRIX version of XFS, allowing a
>> 338 filesystem to be migrated between Linux and IRIX without any need
>> 339 for conversion.
>> 340
>> 341 If unsure, say N. More comprehensive documentation can be found in
>> 342 README.quota in the xfsprogs package. XFS quota can be used either
>> 343 with or without the generic quota support enabled (CONFIG_QUOTA) -
>> 344 they are completely independent subsystems.
>> 345
>> 346 config XFS_POSIX_ACL
>> 347 bool "ACL support"
>> 348 depends on XFS_FS
>> 349 help
>> 350 Posix Access Control Lists (ACLs) support permissions for users and
>> 351 groups beyond the owner/group/world scheme.
>> 352
>> 353 To learn more about Access Control Lists, visit the Posix ACLs for
>> 354 Linux website <http://acl.bestbits.at/>.
116 355
117 config EXPORTFS_BLOCK_OPS !! 356 If you don't know what Access Control Lists are, say N
118 bool "Enable filesystem export operati !! 357
>> 358 config MINIX_FS
>> 359 tristate "Minix fs support"
>> 360 help
>> 361 Minix is a simple operating system used in many classes about OS's.
>> 362 The minix file system (method to organize files on a hard disk
>> 363 partition or a floppy disk) was the original file system for Linux,
>> 364 but has been superseded by the second extended file system ext2fs.
>> 365 You don't want to use the minix file system on your hard disk
>> 366 because of certain built-in restrictions, but it is sometimes found
>> 367 on older Linux floppy disks. This option will enlarge your kernel
>> 368 by about 28 KB. If unsure, say N.
>> 369
>> 370 To compile this file system support as a module, choose M here: the
>> 371 module will be called minix. Note that the file system of your root
>> 372 partition (the one containing the directory /) cannot be compiled as
>> 373 a module.
>> 374
>> 375 config ROMFS_FS
>> 376 tristate "ROM file system support"
>> 377 ---help---
>> 378 This is a very small read-only file system mainly intended for
>> 379 initial ram disks of installation disks, but it could be used for
>> 380 other read-only media as well. Read
>> 381 <file:Documentation/filesystems/romfs.txt> for details.
>> 382
>> 383 To compile this file system support as a module, choose M here: the
>> 384 module will be called romfs. Note that the file system of your
>> 385 root partition (the one containing the directory /) cannot be a
>> 386 module.
>> 387
>> 388 If you don't know whether you need it, then you don't need it:
>> 389 answer N.
>> 390
>> 391 config QUOTA
>> 392 bool "Quota support"
>> 393 help
>> 394 If you say Y here, you will be able to set per user limits for disk
>> 395 usage (also called disk quotas). Currently, it works for the
>> 396 ext2, ext3, and reiserfs file system. You need additional software
>> 397 in order to use quota support (you can download sources from
>> 398 <http://www.sf.net/projects/linuxquota/>). For further details, read
>> 399 the Quota mini-HOWTO, available from
>> 400 <http://www.tldp.org/docs.html#howto>. Probably the quota
>> 401 support is only useful for multi user systems. If unsure, say N.
>> 402
>> 403 config QFMT_V1
>> 404 tristate "Old quota format support"
>> 405 depends on QUOTA
119 help 406 help
120 This option enables the export opera !! 407 This quota format was (is) used by kernels earlier than 2.4.??. If
121 external block IO. !! 408 you have quota working and you don't want to convert to new quota
>> 409 format say Y here.
>> 410
>> 411 config QFMT_V2
>> 412 tristate "Quota format v2 support"
>> 413 depends on QUOTA
>> 414 help
>> 415 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
>> 416 need this functionality say Y here. Note that you will need latest
>> 417 quota utilities for new quota format with this kernel.
122 418
123 config FILE_LOCKING !! 419 config QUOTACTL
124 bool "Enable POSIX file locking API" i !! 420 bool
>> 421 depends on XFS_QUOTA || QUOTA
125 default y 422 default y
>> 423
>> 424 config AUTOFS_FS
>> 425 tristate "Kernel automounter support"
126 help 426 help
127 This option enables standard file lo !! 427 The automounter is a tool to automatically mount remote file systems
128 for filesystems like NFS and for the !! 428 on demand. This implementation is partially kernel-based to reduce
129 call. Disabling this option saves ab !! 429 overhead in the already-mounted case; this is unlike the BSD
>> 430 automounter (amd), which is a pure user space daemon.
>> 431
>> 432 To use the automounter you need the user-space tools from the autofs
>> 433 package; you can find the location in <file:Documentation/Changes>.
>> 434 You also want to answer Y to "NFS file system support", below.
>> 435
>> 436 If you want to use the newer version of the automounter with more
>> 437 features, say N here and say Y to "Kernel automounter v4 support",
>> 438 below.
>> 439
>> 440 To compile this support as a module, choose M here: the module will be
>> 441 called autofs.
130 442
131 source "fs/crypto/Kconfig" !! 443 If you are not a part of a fairly large, distributed network, you
>> 444 probably do not need an automounter, and can say N here.
132 445
133 source "fs/verity/Kconfig" !! 446 config AUTOFS4_FS
>> 447 tristate "Kernel automounter version 4 support (also supports v3)"
>> 448 help
>> 449 The automounter is a tool to automatically mount remote file systems
>> 450 on demand. This implementation is partially kernel-based to reduce
>> 451 overhead in the already-mounted case; this is unlike the BSD
>> 452 automounter (amd), which is a pure user space daemon.
>> 453
>> 454 To use the automounter you need the user-space tools from
>> 455 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4/>; you also
>> 456 want to answer Y to "NFS file system support", below.
>> 457
>> 458 To compile this support as a module, choose M here: the module will be
>> 459 called autofs4. You will need to add "alias autofs autofs4" to your
>> 460 modules configuration file.
>> 461
>> 462 If you are not a part of a fairly large, distributed network or
>> 463 don't have a laptop which needs to dynamically reconfigure to the
>> 464 local network, you probably do not need an automounter, and can say
>> 465 N here.
>> 466
>> 467 menu "CD-ROM/DVD Filesystems"
134 468
135 source "fs/notify/Kconfig" !! 469 config ISO9660_FS
>> 470 tristate "ISO 9660 CDROM file system support"
>> 471 help
>> 472 This is the standard file system used on CD-ROMs. It was previously
>> 473 known as "High Sierra File System" and is called "hsfs" on other
>> 474 Unix systems. The so-called Rock-Ridge extensions which allow for
>> 475 long Unix filenames and symbolic links are also supported by this
>> 476 driver. If you have a CD-ROM drive and want to do more with it than
>> 477 just listen to audio CDs and watch its LEDs, say Y (and read
>> 478 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
>> 479 available from <http://www.tldp.org/docs.html#howto>), thereby
>> 480 enlarging your kernel by about 27 KB; otherwise say N.
>> 481
>> 482 To compile this file system support as a module, choose M here: the
>> 483 module will be called isofs.
>> 484
>> 485 config JOLIET
>> 486 bool "Microsoft Joliet CDROM extensions"
>> 487 depends on ISO9660_FS
>> 488 help
>> 489 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
>> 490 which allows for long filenames in unicode format (unicode is the
>> 491 new 16 bit character code, successor to ASCII, which encodes the
>> 492 characters of almost all languages of the world; see
>> 493 <http://www.unicode.org/> for more information). Say Y here if you
>> 494 want to be able to read Joliet CD-ROMs under Linux.
>> 495
>> 496 config ZISOFS
>> 497 bool "Transparent decompression extension"
>> 498 depends on ISO9660_FS
>> 499 select ZLIB_INFLATE
>> 500 help
>> 501 This is a Linux-specific extension to RockRidge which lets you store
>> 502 data in compressed form on a CD-ROM and have it transparently
>> 503 decompressed when the CD-ROM is accessed. See
>> 504 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
>> 505 necessary to create such a filesystem. Say Y here if you want to be
>> 506 able to read such compressed CD-ROMs.
136 507
137 source "fs/quota/Kconfig" !! 508 config ZISOFS_FS
>> 509 # for fs/nls/Config.in
>> 510 tristate
>> 511 depends on ZISOFS
>> 512 default ISO9660_FS
138 513
139 source "fs/autofs/Kconfig" !! 514 config UDF_FS
140 source "fs/fuse/Kconfig" !! 515 tristate "UDF file system support"
141 source "fs/overlayfs/Kconfig" !! 516 help
>> 517 This is the new file system used on some CD-ROMs and DVDs. Say Y if
>> 518 you intend to mount DVD discs or CDRW's written in packet mode, or
>> 519 if written to by other UDF utilities, such as DirectCD.
>> 520 Please read <file:Documentation/filesystems/udf.txt>.
142 521
143 menu "Caches" !! 522 To compile this file system support as a module, choose M here: the
>> 523 module will be called udf.
144 524
145 source "fs/netfs/Kconfig" !! 525 If unsure, say N.
146 source "fs/cachefiles/Kconfig" <<
147 526
148 endmenu 527 endmenu
149 528
150 if BLOCK !! 529 menu "DOS/FAT/NT Filesystems"
151 menu "CD-ROM/DVD Filesystems" <<
152 530
153 source "fs/isofs/Kconfig" !! 531 config FAT_FS
154 source "fs/udf/Kconfig" !! 532 tristate "DOS FAT fs support"
>> 533 help
>> 534 If you want to use one of the FAT-based file systems (the MS-DOS,
>> 535 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
>> 536 ordinary DOS partition) file systems), then you must say Y or M here
>> 537 to include FAT support. You will then be able to mount partitions or
>> 538 diskettes with FAT-based file systems and transparently access the
>> 539 files on them, i.e. MSDOS files will look and behave just like all
>> 540 other Unix files.
>> 541
>> 542 This FAT support is not a file system in itself, it only provides
>> 543 the foundation for the other file systems. You will have to say Y or
>> 544 M to at least one of "MSDOS fs support" or "VFAT fs support" in
>> 545 order to make use of it.
>> 546
>> 547 Another way to read and write MSDOS floppies and hard drive
>> 548 partitions from within Linux (but not transparently) is with the
>> 549 mtools ("man mtools") program suite. You don't need to say Y here in
>> 550 order to do that.
>> 551
>> 552 If you need to move large files on floppies between a DOS and a
>> 553 Linux box, say Y here, mount the floppy under Linux with an MSDOS
>> 554 file system and use GNU tar's M option. GNU tar is a program
>> 555 available for Unix and DOS ("man tar" or "info tar").
>> 556
>> 557 It is now also becoming possible to read and write compressed FAT
>> 558 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
>> 559 details.
155 560
156 endmenu !! 561 The FAT support will enlarge your kernel by about 37 KB. If unsure,
157 endif # BLOCK !! 562 say Y.
>> 563
>> 564 To compile this as a module, choose M here: the module will be called
>> 565 fat. Note that if you compile the FAT support as a module, you
>> 566 cannot compile any of the FAT-based file systems into the kernel
>> 567 -- they will have to be modules as well.
>> 568 The file system of your root partition (the one containing the
>> 569 directory /) cannot be a module, so don't say M here if you intend
>> 570 to use UMSDOS as your root file system.
>> 571
>> 572 config MSDOS_FS
>> 573 tristate "MSDOS fs support"
>> 574 depends on FAT_FS
>> 575 help
>> 576 This allows you to mount MSDOS partitions of your hard drive (unless
>> 577 they are compressed; to access compressed MSDOS partitions under
>> 578 Linux, you can either use the DOS emulator DOSEMU, described in the
>> 579 DOSEMU-HOWTO, available from
>> 580 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
>> 581 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
>> 582 intend to use dosemu with a non-compressed MSDOS partition, say Y
>> 583 here) and MSDOS floppies. This means that file access becomes
>> 584 transparent, i.e. the MSDOS files look and behave just like all
>> 585 other Unix files.
>> 586
>> 587 If you want to use UMSDOS, the Unix-like file system on top of a
>> 588 DOS file system, which allows you to run Linux from within a DOS
>> 589 partition without repartitioning, you'll have to say Y or M here.
>> 590
>> 591 If you have Windows 95 or Windows NT installed on your MSDOS
>> 592 partitions, you should use the VFAT file system (say Y to "VFAT fs
>> 593 support" below), or you will not be able to see the long filenames
>> 594 generated by Windows 95 / Windows NT.
>> 595
>> 596 This option will enlarge your kernel by about 7 KB. If unsure,
>> 597 answer Y. This will only work if you said Y to "DOS FAT fs support"
>> 598 as well. To compile this as a module, choose M here: the module will
>> 599 be called msdos.
>> 600
>> 601 config VFAT_FS
>> 602 tristate "VFAT (Windows-95) fs support"
>> 603 depends on FAT_FS
>> 604 help
>> 605 This option provides support for normal Windows file systems with
>> 606 long filenames. That includes non-compressed FAT-based file systems
>> 607 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
>> 608 programs from the mtools package.
>> 609
>> 610 You cannot use the VFAT file system for your Linux root partition
>> 611 (the one containing the directory /); use UMSDOS instead if you
>> 612 want to run Linux from within a DOS partition (i.e. say Y to
>> 613 "Unix like fs on top of std MSDOS fs", below).
>> 614
>> 615 The VFAT support enlarges your kernel by about 10 KB and it only
>> 616 works if you said Y to the "DOS FAT fs support" above. Please read
>> 617 the file <file:Documentation/filesystems/vfat.txt> for details. If
>> 618 unsure, say Y.
>> 619
>> 620 To compile this as a module, choose M here: the module will be called
>> 621 vfat.
>> 622
>> 623 config UMSDOS_FS
>> 624 #dep_tristate ' UMSDOS: Unix-like file system on top of standard MSDOS fs' CONFIG_UMSDOS_FS $CONFIG_MSDOS_FS
>> 625 # UMSDOS is temprory broken
>> 626 bool
>> 627 help
>> 628 Say Y here if you want to run Linux from within an existing DOS
>> 629 partition of your hard drive. The advantage of this is that you can
>> 630 get away without repartitioning your hard drive (which often implies
>> 631 backing everything up and restoring afterwards) and hence you're
>> 632 able to quickly try out Linux or show it to your friends; the
>> 633 disadvantage is that Linux becomes susceptible to DOS viruses and
>> 634 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
>> 635 is to write files with long unix filenames to MSDOS floppies; it
>> 636 also allows Unix-style soft-links and owner/permissions of files on
>> 637 MSDOS floppies. You will need a program called umssync in order to
>> 638 make use of UMSDOS; read
>> 639 <file:Documentation/filesystems/umsdos.txt>.
>> 640
>> 641 To get utilities for initializing/checking UMSDOS file system, or
>> 642 latest patches and/or information, visit the UMSDOS home page at
>> 643 <http://www.voyager.hr/~mnalis/umsdos/>.
>> 644
>> 645 This option enlarges your kernel by about 28 KB and it only works if
>> 646 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
>> 647 above. To compile this as a module, choose M here: the module will be
>> 648 called umsdos. Note that the file system of your root partition
>> 649 (the one containing the directory /) cannot be a module, so saying M
>> 650 could be dangerous. If unsure, say N.
>> 651
>> 652 config NTFS_FS
>> 653 tristate "NTFS file system support"
>> 654 help
>> 655 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
>> 656
>> 657 Saying Y or M here enables read support. There is partial, but
>> 658 safe, write support available. For write support you must also
>> 659 say Y to "NTFS write support" below.
>> 660
>> 661 There are also a number of user-space tools available, called
>> 662 ntfsprogs. These include ntfsundelete and ntfsresize, that work
>> 663 without NTFS support enabled in the kernel.
>> 664
>> 665 This is a rewrite from scratch of Linux NTFS support and replaced
>> 666 the old NTFS code starting with Linux 2.5.11. A backport to
>> 667 the Linux 2.4 kernel series is separately available as a patch
>> 668 from the project web site.
>> 669
>> 670 For more information see <file:Documentation/filesystems/ntfs.txt>
>> 671 and <http://linux-ntfs.sourceforge.net/>.
158 672
159 if BLOCK !! 673 To compile this file system support as a module, choose M here: the
160 menu "DOS/FAT/EXFAT/NT Filesystems" !! 674 module will be called ntfs.
161 675
162 source "fs/fat/Kconfig" !! 676 If you are not using Windows NT, 2000, XP or 2003 in addition to
163 source "fs/exfat/Kconfig" !! 677 Linux on your computer it is safe to say N.
164 source "fs/ntfs3/Kconfig" !! 678
>> 679 config NTFS_DEBUG
>> 680 bool "NTFS debugging support"
>> 681 depends on NTFS_FS
>> 682 help
>> 683 If you are experiencing any problems with the NTFS file system, say
>> 684 Y here. This will result in additional consistency checks to be
>> 685 performed by the driver as well as additional debugging messages to
>> 686 be written to the system log. Note that debugging messages are
>> 687 disabled by default. To enable them, supply the option debug_msgs=1
>> 688 at the kernel command line when booting the kernel or as an option
>> 689 to insmod when loading the ntfs module. Once the driver is active,
>> 690 you can enable debugging messages by doing (as root):
>> 691 echo 1 > /proc/sys/fs/ntfs-debug
>> 692 Replacing the "1" with "0" would disable debug messages.
>> 693
>> 694 If you leave debugging messages disabled, this results in little
>> 695 overhead, but enabling debug messages results in very significant
>> 696 slowdown of the system.
>> 697
>> 698 When reporting bugs, please try to have available a full dump of
>> 699 debugging messages while the misbehaviour was occurring.
>> 700
>> 701 config NTFS_RW
>> 702 bool "NTFS write support"
>> 703 depends on NTFS_FS
>> 704 help
>> 705 This enables the partial, but safe, write support in the NTFS driver.
>> 706
>> 707 The only supported operation is overwriting existing files, without
>> 708 changing the file length. No file or directory creation, deletion or
>> 709 renaming is possible. Note only non-resident files can be written to
>> 710 so you may find that some very small files (<500 bytes or so) cannot
>> 711 be written to.
>> 712
>> 713 While we cannot guarantee that it will not damage any data, we have
>> 714 so far not received a single report where the driver would have
>> 715 damaged someones data so we assume it is perfectly safe to use.
>> 716
>> 717 Note: While write support is safe in this version (a rewrite from
>> 718 scratch of the NTFS support), it should be noted that the old NTFS
>> 719 write support, included in Linux 2.5.10 and before (since 1997),
>> 720 is not safe.
>> 721
>> 722 This is currently useful with TopologiLinux. TopologiLinux is run
>> 723 on top of any DOS/Microsoft Windows system without partitioning your
>> 724 hard disk. Unlike other Linux distributions TopologiLinux does not
>> 725 need its own partition. For more information see
>> 726 <http://topologi-linux.sourceforge.net/>
>> 727
>> 728 It is perfectly safe to say N here.
165 729
166 endmenu 730 endmenu
167 endif # BLOCK <<
168 731
169 menu "Pseudo filesystems" 732 menu "Pseudo filesystems"
170 733
171 source "fs/proc/Kconfig" !! 734 config PROC_FS
172 source "fs/kernfs/Kconfig" !! 735 bool "/proc file system support"
173 source "fs/sysfs/Kconfig" !! 736 help
>> 737 This is a virtual file system providing information about the status
>> 738 of the system. "Virtual" means that it doesn't take up any space on
>> 739 your hard disk: the files are created on the fly by the kernel when
>> 740 you try to access them. Also, you cannot read the files with older
>> 741 version of the program less: you need to use more or cat.
>> 742
>> 743 It's totally cool; for example, "cat /proc/interrupts" gives
>> 744 information about what the different IRQs are used for at the moment
>> 745 (there is a small number of Interrupt ReQuest lines in your computer
>> 746 that are used by the attached devices to gain the CPU's attention --
>> 747 often a source of trouble if two devices are mistakenly configured
>> 748 to use the same IRQ). The program procinfo to display some
>> 749 information about your system gathered from the /proc file system.
>> 750
>> 751 Before you can use the /proc file system, it has to be mounted,
>> 752 meaning it has to be given a location in the directory hierarchy.
>> 753 That location should be /proc. A command such as "mount -t proc proc
>> 754 /proc" or the equivalent line in /etc/fstab does the job.
>> 755
>> 756 The /proc file system is explained in the file
>> 757 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
>> 758 ("man 5 proc").
>> 759
>> 760 This option will enlarge your kernel by about 67 KB. Several
>> 761 programs depend on this, so everyone should say Y here.
>> 762
>> 763 config PROC_KCORE
>> 764 bool
>> 765 default y if !ARM
>> 766
>> 767 config DEVFS_FS
>> 768 bool "/dev file system support (OBSOLETE)"
>> 769 depends on EXPERIMENTAL
>> 770 help
>> 771 This is support for devfs, a virtual file system (like /proc) which
>> 772 provides the file system interface to device drivers, normally found
>> 773 in /dev. Devfs does not depend on major and minor number
>> 774 allocations. Device drivers register entries in /dev which then
>> 775 appear automatically, which means that the system administrator does
>> 776 not have to create character and block special device files in the
>> 777 /dev directory using the mknod command (or MAKEDEV script) anymore.
>> 778
>> 779 This is work in progress. If you want to use this, you *must* read
>> 780 the material in <file:Documentation/filesystems/devfs/>, especially
>> 781 the file README there.
>> 782
>> 783 Note that devfs no longer manages /dev/pts! If you are using UNIX98
>> 784 ptys, you will also need to enable (and mount) the /dev/pts
>> 785 filesystem (CONFIG_DEVPTS_FS).
>> 786
>> 787 Note that devfs has been obsoleted by udev,
>> 788 <http://www.kernel.org/pub/linux/utils/kernel/hotplug/>.
>> 789 It has been stripped down to a bare minimum and is only provided for
>> 790 legacy installations that use its naming scheme which is
>> 791 unfortunately different from the names normal Linux installations
>> 792 use.
>> 793
>> 794 If unsure, say N.
>> 795
>> 796 config DEVFS_MOUNT
>> 797 bool "Automatically mount at boot"
>> 798 depends on DEVFS_FS
>> 799 help
>> 800 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
>> 801 this to 'Y' will make the kernel automatically mount devfs onto /dev
>> 802 when the system is booted, before the init thread is started.
>> 803 You can override this with the "devfs=nomount" boot option.
>> 804
>> 805 If unsure, say N.
>> 806
>> 807 config DEVFS_DEBUG
>> 808 bool "Debug devfs"
>> 809 depends on DEVFS_FS
>> 810 help
>> 811 If you say Y here, then the /dev file system code will generate
>> 812 debugging messages. See the file
>> 813 <file:Documentation/filesystems/devfs/boot-options> for more
>> 814 details.
>> 815
>> 816 If unsure, say N.
>> 817
>> 818 config DEVPTS_FS
>> 819 # It compiles as a module for testing only. It should not be used
>> 820 # as a module in general. If we make this "tristate", a bunch of people
>> 821 # who don't know what they are doing turn it on and complain when it
>> 822 # breaks.
>> 823 bool "/dev/pts file system for Unix98 PTYs"
>> 824 depends on UNIX98_PTYS
>> 825 ---help---
>> 826 You should say Y here if you said Y to "Unix98 PTY support" above.
>> 827 You'll then get a virtual file system which can be mounted on
>> 828 /dev/pts with "mount -t devpts". This, together with the pseudo
>> 829 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
>> 830 support as described in The Open Group's Unix98 standard: in order
>> 831 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
>> 832 of the pseudo terminal is then made available to the process and the
>> 833 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
>> 834 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
>> 835
>> 836 The GNU C library glibc 2.1 contains the requisite support for this
>> 837 mode of operation; you also need client programs that use the Unix98
>> 838 API. Please read <file:Documentation/Changes> for more information
>> 839 about the Unix98 pty devices.
>> 840
>> 841 config DEVPTS_FS_XATTR
>> 842 bool "/dev/pts Extended Attributes"
>> 843 depends on DEVPTS_FS
>> 844 help
>> 845 Extended attributes are name:value pairs associated with inodes by
>> 846 the kernel or by users (see the attr(5) manual page, or visit
>> 847 <http://acl.bestbits.at/> for details).
>> 848
>> 849 If unsure, say N.
>> 850
>> 851 config DEVPTS_FS_SECURITY
>> 852 bool "/dev/pts Security Labels"
>> 853 depends on DEVPTS_FS_XATTR
>> 854 help
>> 855 Security labels support alternative access control models
>> 856 implemented by security modules like SELinux. This option
>> 857 enables an extended attribute handler for file security
>> 858 labels in the /dev/pts filesystem.
>> 859
>> 860 If you are not using a security module that requires using
>> 861 extended attributes for file security labels, say N.
174 862
175 config TMPFS 863 config TMPFS
176 bool "Tmpfs virtual memory file system !! 864 bool "Virtual memory file system support (former shm fs)"
177 depends on SHMEM <<
178 select MEMFD_CREATE <<
179 help 865 help
180 Tmpfs is a file system which keeps a 866 Tmpfs is a file system which keeps all files in virtual memory.
181 867
182 Everything in tmpfs is temporary in 868 Everything in tmpfs is temporary in the sense that no files will be
183 created on your hard drive. The file 869 created on your hard drive. The files live in memory and swap
184 space. If you unmount a tmpfs instan 870 space. If you unmount a tmpfs instance, everything stored therein is
185 lost. 871 lost.
186 872
187 See <file:Documentation/filesystems/ !! 873 See <file:Documentation/filesystems/tmpfs.txt> for details.
188 874
189 config TMPFS_POSIX_ACL !! 875 config HUGETLBFS
190 bool "Tmpfs POSIX Access Control Lists !! 876 bool "HugeTLB file system support"
191 depends on TMPFS !! 877 depends X86 || IA64 || PPC64 || SPARC64 || X86_64 || BROKEN
192 select TMPFS_XATTR <<
193 select FS_POSIX_ACL <<
194 help <<
195 POSIX Access Control Lists (ACLs) su <<
196 for users and groups beyond the stan <<
197 and this option selects support for <<
198 filesystems. <<
199 <<
200 If you've selected TMPFS, it's possi <<
201 this option as there are a number of <<
202 POSIX ACL support under /dev for cer <<
203 For example, some distros need this <<
204 files for sound to work properly. I <<
205 say Y. <<
206 878
207 config TMPFS_XATTR !! 879 config HUGETLB_PAGE
208 bool "Tmpfs extended attributes" !! 880 def_bool HUGETLBFS
209 depends on TMPFS <<
210 default n <<
211 help <<
212 Extended attributes are name:value p <<
213 the kernel or by users (see the attr <<
214 881
215 This enables support for the trusted !! 882 config RAMFS
216 namespaces. !! 883 bool
>> 884 default y
>> 885 ---help---
>> 886 Ramfs is a file system which keeps all files in RAM. It allows
>> 887 read and write access.
>> 888
>> 889 It is more of an programming example than a useable file system. If
>> 890 you need a file system which lives in RAM with limit checking use
>> 891 tmpfs.
>> 892
>> 893 To compile this as a module, choose M here: the module will be called
>> 894 ramfs.
>> 895
>> 896 endmenu
217 897
218 You need this for POSIX ACL support !! 898 menu "Miscellaneous filesystems"
>> 899
>> 900 config ADFS_FS
>> 901 tristate "ADFS file system support (EXPERIMENTAL)"
>> 902 depends on EXPERIMENTAL
>> 903 help
>> 904 The Acorn Disc Filing System is the standard file system of the
>> 905 RiscOS operating system which runs on Acorn's ARM-based Risc PC
>> 906 systems and the Acorn Archimedes range of machines. If you say Y
>> 907 here, Linux will be able to read from ADFS partitions on hard drives
>> 908 and from ADFS-formatted floppy discs. If you also want to be able to
>> 909 write to those devices, say Y to "ADFS write support" below.
>> 910
>> 911 The ADFS partition should be the first partition (i.e.,
>> 912 /dev/[hs]d?1) on each of your drives. Please read the file
>> 913 <file:Documentation/filesystems/adfs.txt> for further details.
>> 914
>> 915 To compile this code as a module, choose M here: the module will be
>> 916 called adfs.
219 917
220 If unsure, say N. 918 If unsure, say N.
221 919
222 config TMPFS_INODE64 !! 920 config ADFS_FS_RW
223 bool "Use 64-bit ino_t by default in t !! 921 bool "ADFS write support (DANGEROUS)"
224 depends on TMPFS && 64BIT !! 922 depends on ADFS_FS
225 default n !! 923 help
>> 924 If you say Y here, you will be able to write to ADFS partitions on
>> 925 hard drives and ADFS-formatted floppy disks. This is experimental
>> 926 codes, so if you're unsure, say N.
>> 927
>> 928 config AFFS_FS
>> 929 tristate "Amiga FFS file system support (EXPERIMENTAL)"
>> 930 depends on EXPERIMENTAL
>> 931 help
>> 932 The Fast File System (FFS) is the common file system used on hard
>> 933 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
>> 934 if you want to be able to read and write files from and to an Amiga
>> 935 FFS partition on your hard drive. Amiga floppies however cannot be
>> 936 read with this driver due to an incompatibility of the floppy
>> 937 controller used in an Amiga and the standard floppy controller in
>> 938 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
>> 939 and <file:fs/affs/Changes>.
>> 940
>> 941 With this driver you can also mount disk files used by Bernd
>> 942 Schmidt's Un*X Amiga Emulator
>> 943 (<http://www.freiburg.linux.de/~uae/>).
>> 944 If you want to do this, you will also need to say Y or M to "Loop
>> 945 device support", above.
>> 946
>> 947 To compile this file system support as a module, choose M here: the
>> 948 module will be called affs. If unsure, say N.
>> 949
>> 950 config HFS_FS
>> 951 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
>> 952 depends on EXPERIMENTAL
>> 953 help
>> 954 If you say Y here, you will be able to mount Macintosh-formatted
>> 955 floppy disks and hard drive partitions with full read-write access.
>> 956 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
>> 957 options.
>> 958
>> 959 To compile this file system support as a module, choose M here: the
>> 960 module will be called hfs.
>> 961
>> 962 config BEFS_FS
>> 963 tristate "BeOS file systemv(BeFS) support (read only) (EXPERIMENTAL)"
>> 964 depends on EXPERIMENTAL
226 help 965 help
227 tmpfs has historically used only ino !! 966 The BeOS File System (BeFS) is the native file system of Be, Inc's
228 int. In some cases this can cause wr !! 967 BeOS. Notable features include support for arbitrary attributes
229 in multiple files with the same inod !! 968 on files and directories, and database-like indices on selected
230 option makes tmpfs use the full widt !! 969 attributes. (Also note that this driver doesn't make those features
231 needing to specify the inode64 optio !! 970 available at this time). It is a 64 bit filesystem, so it supports
>> 971 extreemly large volumes and files.
>> 972
>> 973 If you use this filesystem, you should also say Y to at least one
>> 974 of the NLS (native language support) options below.
>> 975
>> 976 If you don't know what this is about, say N.
>> 977
>> 978 To compile this as a module, choose M here: the module will be
>> 979 called befs.
>> 980
>> 981 config BEFS_DEBUG
>> 982 bool "Debug BeFS"
>> 983 depends on BEFS_FS
>> 984 help
>> 985 If you say Y here, you can use the 'debug' mount option to enable
>> 986 debugging output from the driver.
>> 987
>> 988 config BFS_FS
>> 989 tristate "BFS file system support (EXPERIMENTAL)"
>> 990 depends on EXPERIMENTAL
>> 991 help
>> 992 Boot File System (BFS) is a file system used under SCO UnixWare to
>> 993 allow the bootloader access to the kernel image and other important
>> 994 files during the boot process. It is usually mounted under /stand
>> 995 and corresponds to the slice marked as "STAND" in the UnixWare
>> 996 partition. You should say Y if you want to read or write the files
>> 997 on your /stand slice from within Linux. You then also need to say Y
>> 998 to "UnixWare slices support", below. More information about the BFS
>> 999 file system is contained in the file
>> 1000 <file:Documentation/filesystems/bfs.txt>.
>> 1001
>> 1002 If you don't know what this is about, say N.
>> 1003
>> 1004 To compile this as a module, choose M here: the module will be called
>> 1005 bfs. Note that the file system of your root partition (the one
>> 1006 containing the directory /) cannot be compiled as a module.
232 1007
233 But if a long-lived tmpfs is to be a <<
234 ancient that opening a file larger t <<
235 the INODE64 config option and inode6 <<
236 failing with EOVERFLOW once 33-bit i <<
237 1008
238 To override this configured default, <<
239 option when mounting. <<
240 1009
241 If unsure, say N. !! 1010 config EFS_FS
>> 1011 tristate "EFS file system support (read only) (EXPERIMENTAL)"
>> 1012 depends on EXPERIMENTAL
>> 1013 help
>> 1014 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
>> 1015 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
>> 1016 uses the XFS file system for hard disk partitions however).
>> 1017
>> 1018 This implementation only offers read-only access. If you don't know
>> 1019 what all this is about, it's safe to say N. For more information
>> 1020 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
>> 1021
>> 1022 To compile the EFS file system support as a module, choose M here: the
>> 1023 module will be called efs.
>> 1024
>> 1025 config JFFS_FS
>> 1026 tristate "Journalling Flash File System (JFFS) support"
>> 1027 depends on MTD
>> 1028 help
>> 1029 JFFS is the Journaling Flash File System developed by Axis
>> 1030 Communications in Sweden, aimed at providing a crash/powerdown-safe
>> 1031 file system for disk-less embedded devices. Further information is
>> 1032 available at (<http://developer.axis.com/software/jffs/>).
>> 1033
>> 1034 config JFFS_FS_VERBOSE
>> 1035 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
>> 1036 depends on JFFS_FS
>> 1037 default "0"
>> 1038 help
>> 1039 Determines the verbosity level of the JFFS debugging messages.
242 1040
243 config TMPFS_QUOTA !! 1041 config JFFS_PROC_FS
244 bool "Tmpfs quota support" !! 1042 bool "JFFS stats available in /proc filesystem"
245 depends on TMPFS !! 1043 depends on JFFS_FS && PROC
246 select QUOTA <<
247 help 1044 help
248 Quota support allows to set per user !! 1045 Enabling this option will cause statistics from mounted JFFS file systems
249 usage. Say Y to enable quota suppor !! 1046 to be made available to the user in the /proc/fs/jffs/ directory.
250 user and group quota enforcement wit !! 1047
251 mount options. !! 1048 config JFFS2_FS
>> 1049 tristate "Journalling Flash File System v2 (JFFS2) support"
>> 1050 depends on MTD
>> 1051 select CRC32
>> 1052 select ZLIB_INFLATE
>> 1053 select ZLIB_DEFLATE
>> 1054 help
>> 1055 JFFS2 is the second generation of the Journalling Flash File System
>> 1056 for use on diskless embedded devices. It provides improved wear
>> 1057 levelling, compression and support for hard links. You cannot use
>> 1058 this on normal block devices, only on 'MTD' devices.
>> 1059
>> 1060 Further information on the design and implementation of JFFS2 is
>> 1061 available at <http://sources.redhat.com/jffs2/>.
>> 1062
>> 1063 config JFFS2_FS_DEBUG
>> 1064 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
>> 1065 depends on JFFS2_FS
>> 1066 default "0"
>> 1067 help
>> 1068 This controls the amount of debugging messages produced by the JFFS2
>> 1069 code. Set it to zero for use in production systems. For evaluation,
>> 1070 testing and debugging, it's advisable to set it to one. This will
>> 1071 enable a few assertions and will print debugging messages at the
>> 1072 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
>> 1073 is unlikely to be useful - it enables extra debugging in certain
>> 1074 areas which at one point needed debugging, but when the bugs were
>> 1075 located and fixed, the detailed messages were relegated to level 2.
>> 1076
>> 1077 If reporting bugs, please try to have available a full dump of the
>> 1078 messages at debug level 1 while the misbehaviour was occurring.
>> 1079
>> 1080 config JFFS2_FS_NAND
>> 1081 bool "JFFS2 support for NAND flash (EXPERIMENTAL)"
>> 1082 depends on JFFS2_FS && EXPERIMENTAL
>> 1083 default n
>> 1084 help
>> 1085 This enables the experimental support for NAND flash in JFFS2. NAND
>> 1086 is a newer type of flash chip design than the traditional NOR flash,
>> 1087 with higher density but a handful of characteristics which make it
>> 1088 more interesting for the file system to use. Support for NAND flash
>> 1089 is not yet complete and may corrupt data. For further information,
>> 1090 including a link to the mailing list where details of the remaining
>> 1091 work to be completed for NAND flash support can be found, see the
>> 1092 JFFS2 web site at <http://sources.redhat.com/jffs2>.
>> 1093
>> 1094 Say 'N' unless you have NAND flash and you are willing to test and
>> 1095 develop JFFS2 support for it.
>> 1096
>> 1097 config CRAMFS
>> 1098 tristate "Compressed ROM file system support"
>> 1099 select ZLIB_INFLATE
>> 1100 help
>> 1101 Saying Y here includes support for CramFs (Compressed ROM File
>> 1102 System). CramFs is designed to be a simple, small, and compressed
>> 1103 file system for ROM based embedded systems. CramFs is read-only,
>> 1104 limited to 256MB file systems (with 16MB files), and doesn't support
>> 1105 16/32 bits uid/gid, hard links and timestamps.
>> 1106
>> 1107 See <file:Documentation/filesystems/cramfs.txt> and
>> 1108 <file:fs/cramfs/README> for further information.
>> 1109
>> 1110 To compile this as a module, choose M here: the module will be called
>> 1111 cramfs. Note that the root file system (the one containing the
>> 1112 directory /) cannot be compiled as a module.
252 1113
253 If unsure, say N. 1114 If unsure, say N.
254 1115
255 config ARCH_SUPPORTS_HUGETLBFS !! 1116 config VXFS_FS
256 def_bool n !! 1117 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
>> 1118 help
>> 1119 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
>> 1120 file system format. VERITAS VxFS(TM) is the standard file system
>> 1121 of SCO UnixWare (and possibly others) and optionally available
>> 1122 for Sunsoft Solaris, HP-UX and many other operating systems.
>> 1123 Currently only readonly access is supported.
>> 1124
>> 1125 NOTE: the file system type as used by mount(1), mount(2) and
>> 1126 fstab(5) is 'vxfs' as it describes the file system format, not
>> 1127 the actual driver.
257 1128
258 menuconfig HUGETLBFS !! 1129 To compile this as a module, choose M here: the module will be
259 bool "HugeTLB file system support" !! 1130 called freevxfs. If unsure, say N.
260 depends on X86 || SPARC64 || ARCH_SUPP !! 1131
261 depends on (SYSFS || SYSCTL) !! 1132
262 select MEMFD_CREATE !! 1133 config HPFS_FS
263 select PADATA if SMP !! 1134 tristate "OS/2 HPFS file system support"
264 help 1135 help
265 hugetlbfs is a filesystem backing fo !! 1136 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
266 ramfs. For architectures that suppor !! 1137 is the file system used for organizing files on OS/2 hard disk
267 <file:Documentation/admin-guide/mm/h !! 1138 partitions. Say Y if you want to be able to read files from and
>> 1139 write files to an OS/2 HPFS partition on your hard drive. OS/2
>> 1140 floppies however are in regular MSDOS format, so you don't need this
>> 1141 option in order to be able to read them. Read
>> 1142 <file:Documentation/filesystems/hpfs.txt>.
268 1143
269 If unsure, say N. !! 1144 To compile this file system support as a module, choose M here: the
>> 1145 module will be called hpfs. If unsure, say N.
270 1146
271 if HUGETLBFS !! 1147
272 config HUGETLB_PAGE_OPTIMIZE_VMEMMAP_DEFAULT_O !! 1148
273 bool "HugeTLB Vmemmap Optimization (HV !! 1149 config QNX4FS_FS
274 default n !! 1150 tristate "QNX4 file system support (read only)"
275 depends on HUGETLB_PAGE_OPTIMIZE_VMEMM !! 1151 help
>> 1152 This is the file system used by the real-time operating systems
>> 1153 QNX 4 and QNX 6 (the latter is also called QNX RTP).
>> 1154 Further information is available at <http://www.qnx.com/>.
>> 1155 Say Y if you intend to mount QNX hard disks or floppies.
>> 1156 Unless you say Y to "QNX4FS read-write support" below, you will
>> 1157 only be able to read these file systems.
>> 1158
>> 1159 To compile this file system support as a module, choose M here: the
>> 1160 module will be called qnx4.
>> 1161
>> 1162 If you don't know whether you need it, then you don't need it:
>> 1163 answer N.
>> 1164
>> 1165 config QNX4FS_RW
>> 1166 bool "QNX4FS write support (DANGEROUS)"
>> 1167 depends on QNX4FS_FS && EXPERIMENTAL
276 help 1168 help
277 The HugeTLB Vmemmap Optimization (HV !! 1169 Say Y if you want to test write support for QNX4 file systems.
278 enable HVO by default. It can be dis <<
279 (boot command line) or hugetlb_optim <<
280 endif # HUGETLBFS <<
281 1170
282 config HUGETLB_PAGE !! 1171 It's currently broken, so for now:
283 def_bool HUGETLBFS !! 1172 answer N.
284 select XARRAY_MULTI <<
285 1173
286 config HUGETLB_PAGE_OPTIMIZE_VMEMMAP <<
287 def_bool HUGETLB_PAGE <<
288 depends on ARCH_WANT_OPTIMIZE_HUGETLB_ <<
289 depends on SPARSEMEM_VMEMMAP <<
290 <<
291 config HUGETLB_PMD_PAGE_TABLE_SHARING <<
292 def_bool HUGETLB_PAGE <<
293 depends on ARCH_WANT_HUGE_PMD_SHARE && <<
294 1174
295 config ARCH_HAS_GIGANTIC_PAGE <<
296 bool <<
297 1175
298 source "fs/configfs/Kconfig" !! 1176 config SYSV_FS
299 source "fs/efivarfs/Kconfig" !! 1177 tristate "System V/Xenix/V7/Coherent file system support"
>> 1178 help
>> 1179 SCO, Xenix and Coherent are commercial Unix systems for Intel
>> 1180 machines, and Version 7 was used on the DEC PDP-11. Saying Y
>> 1181 here would allow you to read from their floppies and hard disk
>> 1182 partitions.
>> 1183
>> 1184 If you have floppies or hard disk partitions like that, it is likely
>> 1185 that they contain binaries from those other Unix systems; in order
>> 1186 to run these binaries, you will want to install linux-abi which is a
>> 1187 a set of kernel modules that lets you run SCO, Xenix, Wyse,
>> 1188 UnixWare, Dell Unix and System V programs under Linux. It is
>> 1189 available via FTP (user: ftp) from
>> 1190 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
>> 1191 NOTE: that will work only for binaries from Intel-based systems;
>> 1192 PDP ones will have to wait until somebody ports Linux to -11 ;-)
>> 1193
>> 1194 If you only intend to mount files from some other Unix over the
>> 1195 network using NFS, you don't need the System V file system support
>> 1196 (but you need NFS file system support obviously).
>> 1197
>> 1198 Note that this option is generally not needed for floppies, since a
>> 1199 good portable way to transport files and directories between unixes
>> 1200 (and even other operating systems) is given by the tar program ("man
>> 1201 tar" or preferably "info tar"). Note also that this option has
>> 1202 nothing whatsoever to do with the option "System V IPC". Read about
>> 1203 the System V file system in
>> 1204 <file:Documentation/filesystems/sysv-fs.txt>.
>> 1205 Saying Y here will enlarge your kernel by about 27 KB.
>> 1206
>> 1207 To compile this as a module, choose M here: the module will be called
>> 1208 sysv.
300 1209
301 endmenu !! 1210 If you haven't heard about all of this before, it's safe to say N.
302 1211
303 menuconfig MISC_FILESYSTEMS !! 1212
304 bool "Miscellaneous filesystems" !! 1213
305 default y !! 1214 config UFS_FS
>> 1215 tristate "UFS file system support (read only)"
>> 1216 help
>> 1217 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
>> 1218 OpenBSD and NeXTstep) use a file system called UFS. Some System V
>> 1219 Unixes can create and mount hard disk partitions and diskettes using
>> 1220 this file system as well. Saying Y here will allow you to read from
>> 1221 these partitions; if you also want to write to them, say Y to the
>> 1222 experimental "UFS file system write support", below. Please read the
>> 1223 file <file:Documentation/filesystems/ufs.txt> for more information.
>> 1224
>> 1225 If you only intend to mount files from some other Unix over the
>> 1226 network using NFS, you don't need the UFS file system support (but
>> 1227 you need NFS file system support obviously).
>> 1228
>> 1229 Note that this option is generally not needed for floppies, since a
>> 1230 good portable way to transport files and directories between unixes
>> 1231 (and even other operating systems) is given by the tar program ("man
>> 1232 tar" or preferably "info tar").
>> 1233
>> 1234 When accessing NeXTstep files, you may need to convert them from the
>> 1235 NeXT character set to the Latin1 character set; use the program
>> 1236 recode ("info recode") for this purpose.
>> 1237
>> 1238 To compile the UFS file system support as a module, choose M here: the
>> 1239 module will be called ufs.
>> 1240
>> 1241 If you haven't heard about all of this before, it's safe to say N.
>> 1242
>> 1243 config UFS_FS_WRITE
>> 1244 bool "UFS file system write support (DANGEROUS)"
>> 1245 depends on UFS_FS && EXPERIMENTAL
306 help 1246 help
307 Say Y here to get to see options for !! 1247 Say Y here if you want to try writing to UFS partitions. This is
308 filesystems, such as filesystems tha !! 1248 experimental, so you should back up your UFS partitions beforehand.
309 operating systems. <<
310 <<
311 This option alone does not add any k <<
312 <<
313 If you say N, all options in this su <<
314 disabled; if unsure, say Y here. <<
315 <<
316 if MISC_FILESYSTEMS <<
317 <<
318 source "fs/orangefs/Kconfig" <<
319 source "fs/adfs/Kconfig" <<
320 source "fs/affs/Kconfig" <<
321 source "fs/ecryptfs/Kconfig" <<
322 source "fs/hfs/Kconfig" <<
323 source "fs/hfsplus/Kconfig" <<
324 source "fs/befs/Kconfig" <<
325 source "fs/bfs/Kconfig" <<
326 source "fs/efs/Kconfig" <<
327 source "fs/jffs2/Kconfig" <<
328 # UBIFS File system configuration <<
329 source "fs/ubifs/Kconfig" <<
330 source "fs/cramfs/Kconfig" <<
331 source "fs/squashfs/Kconfig" <<
332 source "fs/freevxfs/Kconfig" <<
333 source "fs/minix/Kconfig" <<
334 source "fs/omfs/Kconfig" <<
335 source "fs/hpfs/Kconfig" <<
336 source "fs/qnx4/Kconfig" <<
337 source "fs/qnx6/Kconfig" <<
338 source "fs/romfs/Kconfig" <<
339 source "fs/pstore/Kconfig" <<
340 source "fs/sysv/Kconfig" <<
341 source "fs/ufs/Kconfig" <<
342 source "fs/erofs/Kconfig" <<
343 source "fs/vboxsf/Kconfig" <<
344 1249
345 endif # MISC_FILESYSTEMS !! 1250 endmenu
346 1251
347 menuconfig NETWORK_FILESYSTEMS !! 1252 menu "Network File Systems"
348 bool "Network File Systems" <<
349 default y <<
350 depends on NET 1253 depends on NET
>> 1254
>> 1255 config NFS_FS
>> 1256 tristate "NFS file system support"
>> 1257 depends on INET
>> 1258 select LOCKD
>> 1259 select SUNRPC
>> 1260 help
>> 1261 If you are connected to some other (usually local) Unix computer
>> 1262 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
>> 1263 on that computer (the NFS server) using the Network File Sharing
>> 1264 protocol, say Y. "Mounting files" means that the client can access
>> 1265 the files with usual UNIX commands as if they were sitting on the
>> 1266 client's hard disk. For this to work, the server must run the
>> 1267 programs nfsd and mountd (but does not need to have NFS file system
>> 1268 support enabled in its kernel). NFS is explained in the Network
>> 1269 Administrator's Guide, available from
>> 1270 <http://www.tldp.org/docs.html#guide>, on its man page: "man
>> 1271 nfs", and in the NFS-HOWTO.
>> 1272
>> 1273 A superior but less widely used alternative to NFS is provided by
>> 1274 the Coda file system; see "Coda file system support" below.
>> 1275
>> 1276 If you say Y here, you should have said Y to TCP/IP networking also.
>> 1277 This option would enlarge your kernel by about 27 KB.
>> 1278
>> 1279 To compile this file system support as a module, choose M here: the
>> 1280 module will be called nfs.
>> 1281
>> 1282 If you are configuring a diskless machine which will mount its root
>> 1283 file system over NFS at boot time, say Y here and to "Kernel
>> 1284 level IP autoconfiguration" above and to "Root file system on NFS"
>> 1285 below. You cannot compile this driver as a module in this case.
>> 1286 There are two packages designed for booting diskless machines over
>> 1287 the net: netboot, available from
>> 1288 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
>> 1289 available from <http://ftp1.sourceforge.net/etherboot/>.
>> 1290
>> 1291 If you don't know what all this is about, say N.
>> 1292
>> 1293 config NFS_V3
>> 1294 bool "Provide NFSv3 client support"
>> 1295 depends on NFS_FS
351 help 1296 help
352 Say Y here to get to see options for !! 1297 Say Y here if you want your NFS client to be able to speak the newer
353 filesystem-related networking code, !! 1298 version 3 of the NFS protocol.
354 RPCSEC security modules. <<
355 1299
356 This option alone does not add any k !! 1300 If unsure, say N.
357 1301
358 If you say N, all options in this su !! 1302 config NFS_V4
359 disabled; if unsure, say Y here. !! 1303 bool "Provide NFSv4 client support (EXPERIMENTAL)"
>> 1304 depends on NFS_FS && EXPERIMENTAL
>> 1305 help
>> 1306 Say Y here if you want your NFS client to be able to speak the newer
>> 1307 version 4 of the NFS protocol. This feature is experimental, and
>> 1308 should only be used if you are interested in helping to test NFSv4.
360 1309
361 if NETWORK_FILESYSTEMS !! 1310 If unsure, say N.
>> 1311
>> 1312 config NFS_DIRECTIO
>> 1313 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
>> 1314 depends on NFS_FS && EXPERIMENTAL
>> 1315 help
>> 1316 This option enables applications to perform uncached I/O on files
>> 1317 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
>> 1318 is set for a file, its data is not cached in the system's page
>> 1319 cache. Data is moved to and from user-level application buffers
>> 1320 directly. Unlike local disk-based file systems, NFS O_DIRECT has
>> 1321 no alignment restrictions.
>> 1322
>> 1323 Unless your program is designed to use O_DIRECT properly, you are
>> 1324 much better off allowing the NFS client to manage data caching for
>> 1325 you. Misusing O_DIRECT can cause poor server performance or network
>> 1326 storms. This kernel build option defaults OFF to avoid exposing
>> 1327 system administrators unwittingly to a potentially hazardous
>> 1328 feature.
>> 1329
>> 1330 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
>> 1331
>> 1332 If unsure, say N. This reduces the size of the NFS client, and
>> 1333 causes open() to return EINVAL if a file residing in NFS is
>> 1334 opened with the O_DIRECT flag.
>> 1335
>> 1336 config NFSD
>> 1337 tristate "NFS server support"
>> 1338 depends on INET
>> 1339 select LOCKD
>> 1340 select SUNRPC
>> 1341 help
>> 1342 If you want your Linux box to act as an NFS *server*, so that other
>> 1343 computers on your local network which support NFS can access certain
>> 1344 directories on your box transparently, you have two options: you can
>> 1345 use the self-contained user space program nfsd, in which case you
>> 1346 should say N here, or you can say Y and use the kernel based NFS
>> 1347 server. The advantage of the kernel based solution is that it is
>> 1348 faster.
>> 1349
>> 1350 In either case, you will need support software; the respective
>> 1351 locations are given in the file <file:Documentation/Changes> in the
>> 1352 NFS section.
>> 1353
>> 1354 If you say Y here, you will get support for version 2 of the NFS
>> 1355 protocol (NFSv2). If you also want NFSv3, say Y to the next question
>> 1356 as well.
>> 1357
>> 1358 Please read the NFS-HOWTO, available from
>> 1359 <http://www.tldp.org/docs.html#howto>.
>> 1360
>> 1361 To compile the NFS server support as a module, choose M here: the
>> 1362 module will be called nfsd. If unsure, say N.
>> 1363
>> 1364 config NFSD_V3
>> 1365 bool "Provide NFSv3 server support"
>> 1366 depends on NFSD
>> 1367 help
>> 1368 If you would like to include the NFSv3 server as well as the NFSv2
>> 1369 server, say Y here. If unsure, say Y.
362 1370
363 source "fs/nfs/Kconfig" !! 1371 config NFSD_V4
364 source "fs/nfsd/Kconfig" !! 1372 bool "Provide NFSv4 server support (EXPERIMENTAL)"
>> 1373 depends on NFSD_V3 && EXPERIMENTAL
>> 1374 help
>> 1375 If you would like to include the NFSv4 server as well as the NFSv2
>> 1376 and NFSv3 servers, say Y here. This feature is experimental, and
>> 1377 should only be used if you are interested in helping to test NFSv4.
>> 1378 If unsure, say N.
365 1379
366 config GRACE_PERIOD !! 1380 config NFSD_TCP
367 tristate !! 1381 bool "Provide NFS server over TCP support (EXPERIMENTAL)"
>> 1382 depends on NFSD && EXPERIMENTAL
>> 1383 help
>> 1384 Enable NFS service over TCP connections. This the officially
>> 1385 still experimental, but seems to work well.
>> 1386
>> 1387 config ROOT_NFS
>> 1388 bool "Root file system on NFS"
>> 1389 depends on NFS_FS=y && IP_PNP
>> 1390 help
>> 1391 If you want your Linux box to mount its whole root file system (the
>> 1392 one containing the directory /) from some other computer over the
>> 1393 net via NFS (presumably because your box doesn't have a hard disk),
>> 1394 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
>> 1395 likely that in this case, you also want to say Y to "Kernel level IP
>> 1396 autoconfiguration" so that your box can discover its network address
>> 1397 at boot time.
>> 1398
>> 1399 Most people say N here.
368 1400
369 config LOCKD 1401 config LOCKD
370 tristate 1402 tristate
371 depends on FILE_LOCKING <<
372 select GRACE_PERIOD <<
373 1403
374 config LOCKD_V4 1404 config LOCKD_V4
375 bool 1405 bool
376 depends on NFSD || NFS_V3 !! 1406 depends on NFSD_V3 || NFS_V3
377 depends on FILE_LOCKING <<
378 default y 1407 default y
379 1408
380 config NFS_ACL_SUPPORT !! 1409 config EXPORTFS
381 tristate 1410 tristate
382 select FS_POSIX_ACL !! 1411 default NFSD
383 <<
384 config NFS_COMMON <<
385 bool <<
386 depends on NFSD || NFS_FS || LOCKD <<
387 default y <<
388 1412
389 config NFS_COMMON_LOCALIO_SUPPORT !! 1413 config SUNRPC
390 tristate 1414 tristate
391 depends on NFS_LOCALIO <<
392 default y if NFSD=y || NFS_FS=y <<
393 default m if NFSD=m && NFS_FS=m <<
394 select SUNRPC <<
395 1415
396 config NFS_LOCALIO !! 1416 config SUNRPC_GSS
397 bool "NFS client and server support fo !! 1417 tristate "Provide RPCSEC_GSS authentication (EXPERIMENTAL)"
398 depends on NFSD && NFS_FS !! 1418 depends on SUNRPC && EXPERIMENTAL
399 select NFS_COMMON_LOCALIO_SUPPORT !! 1419 default SUNRPC if NFS_V4=y
400 default n !! 1420 help
>> 1421 Provides cryptographic authentication for NFS rpc requests. To
>> 1422 make this useful, you must also select at least one rpcsec_gss
>> 1423 mechanism.
>> 1424 Note: You should always select this option if you wish to use
>> 1425 NFSv4.
>> 1426
>> 1427 config RPCSEC_GSS_KRB5
>> 1428 tristate "Kerberos V mechanism for RPCSEC_GSS (EXPERIMENTAL)"
>> 1429 depends on SUNRPC_GSS && CRYPTO_DES && CRYPTO_MD5
>> 1430 default SUNRPC_GSS if NFS_V4=y
>> 1431 help
>> 1432 Provides a gss-api mechanism based on Kerberos V5 (this is
>> 1433 mandatory for RFC3010-compliant NFSv4 implementations).
>> 1434 Requires a userspace daemon;
>> 1435 see http://www.citi.umich.edu/projects/nfsv4/.
>> 1436
>> 1437 Note: If you select this option, please ensure that you also
>> 1438 enable the MD5 and DES crypto ciphers.
>> 1439
>> 1440 config SMB_FS
>> 1441 tristate "SMB file system support (to mount Windows shares etc.)"
>> 1442 depends on INET
>> 1443 help
>> 1444 SMB (Server Message Block) is the protocol Windows for Workgroups
>> 1445 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
>> 1446 files and printers over local networks. Saying Y here allows you to
>> 1447 mount their file systems (often called "shares" in this context) and
>> 1448 access them just like any other Unix directory. Currently, this
>> 1449 works only if the Windows machines use TCP/IP as the underlying
>> 1450 transport protocol, and not NetBEUI. For details, read
>> 1451 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
>> 1452 available from <http://www.tldp.org/docs.html#howto>.
>> 1453
>> 1454 Note: if you just want your box to act as an SMB *server* and make
>> 1455 files and printing services available to Windows clients (which need
>> 1456 to have a TCP/IP stack), you don't need to say Y here; you can use
>> 1457 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
>> 1458 for that.
>> 1459
>> 1460 General information about how to connect Linux, Windows machines and
>> 1461 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
>> 1462
>> 1463 To compile the SMB support as a module, choose M here: the module will
>> 1464 be called smbfs. Most people say N, however.
>> 1465
>> 1466 config SMB_NLS_DEFAULT
>> 1467 bool "Use a default NLS"
>> 1468 depends on SMB_FS
>> 1469 help
>> 1470 Enabling this will make smbfs use nls translations by default. You
>> 1471 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
>> 1472 settings and you need to give the default nls for the SMB server as
>> 1473 CONFIG_SMB_NLS_REMOTE.
>> 1474
>> 1475 The nls settings can be changed at mount time, if your smbmount
>> 1476 supports that, using the codepage and iocharset parameters.
>> 1477
>> 1478 smbmount from samba 2.2.0 or later supports this.
>> 1479
>> 1480 config SMB_NLS_REMOTE
>> 1481 string "Default Remote NLS Option"
>> 1482 depends on SMB_NLS_DEFAULT
>> 1483 default "cp437"
>> 1484 help
>> 1485 This setting allows you to specify a default value for which
>> 1486 codepage the server uses. If this field is left blank no
>> 1487 translations will be done by default. The local codepage/charset
>> 1488 default to CONFIG_NLS_DEFAULT.
>> 1489
>> 1490 The nls settings can be changed at mount time, if your smbmount
>> 1491 supports that, using the codepage and iocharset parameters.
>> 1492
>> 1493 smbmount from samba 2.2.0 or later supports this.
>> 1494
>> 1495 config CIFS
>> 1496 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)(EXPERIMENTAL)"
>> 1497 depends on INET
401 help 1498 help
402 Some NFS servers support an auxiliar !! 1499 This is the client VFS module for the Common Internet File System
403 that is not an official part of the !! 1500 (CIFS) protocol which is the successor to the Server Message Block
>> 1501 (SMB) protocol, the native file sharing mechanism for most early
>> 1502 PC operating systems. CIFS is fully supported by current network
>> 1503 file servers such as Windows 2000 (including Windows NT version 4
>> 1504 and Windows XP) as well by Samba (which provides excellent CIFS
>> 1505 server support for Linux and many other operating systems). For
>> 1506 production systems the smbfs module may be used instead of this
>> 1507 cifs module since smbfs is currently more stable and provides
>> 1508 support for older servers. The intent of this module is to provide the
>> 1509 most advanced network file system function for CIFS compliant servers,
>> 1510 including support for dfs (hierarchical name space), secure per-user
>> 1511 session establishment, safe distributed caching (oplock), optional
>> 1512 packet signing, Unicode and other internationalization improvements, and
>> 1513 optional Winbind (nsswitch) integration. This module is in an early
>> 1514 development stage, so unless you are specifically interested in this
>> 1515 filesystem, just say N.
>> 1516
>> 1517 config NCP_FS
>> 1518 tristate "NCP file system support (to mount NetWare volumes)"
>> 1519 depends on IPX!=n || INET
>> 1520 help
>> 1521 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
>> 1522 used by Novell NetWare clients to talk to file servers. It is to
>> 1523 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
>> 1524 to mount NetWare file server volumes and to access them just like
>> 1525 any other Unix directory. For details, please read the file
>> 1526 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
>> 1527 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
>> 1528
>> 1529 You do not have to say Y here if you want your Linux box to act as a
>> 1530 file *server* for Novell NetWare clients.
>> 1531
>> 1532 General information about how to connect Linux, Windows machines and
>> 1533 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
>> 1534
>> 1535 To compile this as a module, choose M here: the module will be called
>> 1536 ncpfs. Say N unless you are connected to a Novell network.
>> 1537
>> 1538 source "fs/ncpfs/Kconfig"
>> 1539
>> 1540 config CODA_FS
>> 1541 tristate "Coda file system support (advanced network fs)"
>> 1542 depends on INET
>> 1543 help
>> 1544 Coda is an advanced network file system, similar to NFS in that it
>> 1545 enables you to mount file systems of a remote server and access them
>> 1546 with regular Unix commands as if they were sitting on your hard
>> 1547 disk. Coda has several advantages over NFS: support for
>> 1548 disconnected operation (e.g. for laptops), read/write server
>> 1549 replication, security model for authentication and encryption,
>> 1550 persistent client caches and write back caching.
>> 1551
>> 1552 If you say Y here, your Linux box will be able to act as a Coda
>> 1553 *client*. You will need user level code as well, both for the
>> 1554 client and server. Servers are currently user level, i.e. they need
>> 1555 no kernel support. Please read
>> 1556 <file:Documentation/filesystems/coda.txt> and check out the Coda
>> 1557 home page <http://www.coda.cs.cmu.edu/>.
>> 1558
>> 1559 To compile the coda client support as a module, choose M here: the
>> 1560 module will be called coda.
>> 1561
>> 1562 config CODA_FS_OLD_API
>> 1563 bool "Use 96-bit Coda file identifiers"
>> 1564 depends on CODA_FS
>> 1565 help
>> 1566 A new kernel-userspace API had to be introduced for Coda v6.0
>> 1567 to support larger 128-bit file identifiers as needed by the
>> 1568 new realms implementation.
>> 1569
>> 1570 However this new API is not backward compatible with older
>> 1571 clients. If you really need to run the old Coda userspace
>> 1572 cache manager then say Y.
>> 1573
>> 1574 For most cases you probably want to say N.
>> 1575
>> 1576 config INTERMEZZO_FS
>> 1577 tristate "InterMezzo file system support (replicating fs) (EXPERIMENTAL)"
>> 1578 depends on INET && EXPERIMENTAL
>> 1579 help
>> 1580 InterMezzo is a networked file system with disconnected operation
>> 1581 and kernel level write back caching. It is most often used for
>> 1582 replicating potentially large trees or keeping laptop/desktop copies
>> 1583 in sync.
>> 1584
>> 1585 If you say Y or M your kernel or module will provide InterMezzo
>> 1586 support. You will also need a file server daemon, which you can get
>> 1587 from <http://www.inter-mezzo.org/>.
>> 1588
>> 1589 config AFS_FS
>> 1590 # for fs/nls/Config.in
>> 1591 tristate "Andrew File System support (AFS) (Experimental)"
>> 1592 depends on INET && EXPERIMENTAL
>> 1593 select RXRPC
>> 1594 help
>> 1595 If you say Y here, you will get an experimental Andrew File System
>> 1596 driver. It currently only supports unsecured read-only AFS access.
404 1597
405 This option enables support for the !! 1598 See Documentation/filesystems/afs.txt for more intormation.
406 kernel's NFS server and client. Enab <<
407 NFS clients to bypass the network wh <<
408 writes to the local NFS server. <<
409 1599
410 If unsure, say N. 1600 If unsure, say N.
411 1601
412 config NFS_V4_2_SSC_HELPER !! 1602 config RXRPC
413 bool !! 1603 tristate
414 default y if NFS_V4_2 <<
415 1604
416 source "net/sunrpc/Kconfig" !! 1605 endmenu
417 source "fs/ceph/Kconfig" <<
418 1606
419 source "fs/smb/Kconfig" !! 1607 menu "Partition Types"
420 source "fs/coda/Kconfig" <<
421 source "fs/afs/Kconfig" <<
422 source "fs/9p/Kconfig" <<
423 1608
424 endif # NETWORK_FILESYSTEMS !! 1609 source "fs/partitions/Kconfig"
425 1610
426 source "fs/nls/Kconfig" !! 1611 endmenu
427 source "fs/dlm/Kconfig" <<
428 source "fs/unicode/Kconfig" <<
429 1612
430 config IO_WQ !! 1613 source "fs/nls/Kconfig"
431 bool <<
432 1614
433 endmenu 1615 endmenu
>> 1616
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.