Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # File system configuration |
| 3 | # |
| 4 | |
| 5 | menu "File systems" |
| 6 | |
| 7 | config EXT2_FS |
| 8 | tristate "Second extended fs support" |
| 9 | help |
| 10 | Ext2 is a standard Linux file system for hard disks. |
| 11 | |
| 12 | To compile this file system support as a module, choose M here: the |
| 13 | module will be called ext2. Be aware however that the file system |
| 14 | of your root partition (the one containing the directory /) cannot |
| 15 | be compiled as a module, and so this could be dangerous. |
| 16 | |
| 17 | If unsure, say Y. |
| 18 | |
| 19 | config EXT2_FS_XATTR |
| 20 | bool "Ext2 extended attributes" |
| 21 | depends on EXT2_FS |
| 22 | help |
| 23 | Extended attributes are name:value pairs associated with inodes by |
| 24 | the kernel or by users (see the attr(5) manual page, or visit |
| 25 | <http://acl.bestbits.at/> for details). |
| 26 | |
| 27 | If unsure, say N. |
| 28 | |
| 29 | config EXT2_FS_POSIX_ACL |
| 30 | bool "Ext2 POSIX Access Control Lists" |
| 31 | depends on EXT2_FS_XATTR |
Andreas Gruenbacher | b84c215 | 2005-07-07 17:56:57 -0700 | [diff] [blame] | 32 | select FS_POSIX_ACL |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 33 | help |
| 34 | Posix Access Control Lists (ACLs) support permissions for users and |
| 35 | groups beyond the owner/group/world scheme. |
| 36 | |
| 37 | To learn more about Access Control Lists, visit the Posix ACLs for |
| 38 | Linux website <http://acl.bestbits.at/>. |
| 39 | |
| 40 | If you don't know what Access Control Lists are, say N |
| 41 | |
| 42 | config EXT2_FS_SECURITY |
| 43 | bool "Ext2 Security Labels" |
| 44 | depends on EXT2_FS_XATTR |
| 45 | help |
| 46 | Security labels support alternative access control models |
| 47 | implemented by security modules like SELinux. This option |
| 48 | enables an extended attribute handler for file security |
| 49 | labels in the ext2 filesystem. |
| 50 | |
| 51 | If you are not using a security module that requires using |
| 52 | extended attributes for file security labels, say N. |
| 53 | |
Carsten Otte | 6d79125 | 2005-06-23 22:05:26 -0700 | [diff] [blame] | 54 | config EXT2_FS_XIP |
| 55 | bool "Ext2 execute in place support" |
| 56 | depends on EXT2_FS |
| 57 | help |
| 58 | Execute in place can be used on memory-backed block devices. If you |
| 59 | enable this option, you can select to mount block devices which are |
| 60 | capable of this feature without using the page cache. |
| 61 | |
| 62 | If you do not use a block device that is capable of using this, |
| 63 | or if unsure, say N. |
| 64 | |
| 65 | config FS_XIP |
| 66 | # execute in place |
| 67 | bool |
| 68 | depends on EXT2_FS_XIP |
| 69 | default y |
| 70 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 71 | config EXT3_FS |
| 72 | tristate "Ext3 journalling file system support" |
Mark Fasheh | b4e40a5 | 2005-12-15 14:31:24 -0800 | [diff] [blame] | 73 | select JBD |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 74 | help |
| 75 | This is the journaling version of the Second extended file system |
| 76 | (often called ext3), the de facto standard Linux file system |
| 77 | (method to organize files on a storage device) for hard disks. |
| 78 | |
| 79 | The journaling code included in this driver means you do not have |
| 80 | to run e2fsck (file system checker) on your file systems after a |
| 81 | crash. The journal keeps track of any changes that were being made |
| 82 | at the time the system crashed, and can ensure that your file system |
| 83 | is consistent without the need for a lengthy check. |
| 84 | |
| 85 | Other than adding the journal to the file system, the on-disk format |
| 86 | of ext3 is identical to ext2. It is possible to freely switch |
| 87 | between using the ext3 driver and the ext2 driver, as long as the |
| 88 | file system has been cleanly unmounted, or e2fsck is run on the file |
| 89 | system. |
| 90 | |
| 91 | To add a journal on an existing ext2 file system or change the |
| 92 | behavior of ext3 file systems, you can use the tune2fs utility ("man |
| 93 | tune2fs"). To modify attributes of files and directories on ext3 |
| 94 | file systems, use chattr ("man chattr"). You need to be using |
| 95 | e2fsprogs version 1.20 or later in order to create ext3 journals |
| 96 | (available at <http://sourceforge.net/projects/e2fsprogs/>). |
| 97 | |
| 98 | To compile this file system support as a module, choose M here: the |
| 99 | module will be called ext3. Be aware however that the file system |
| 100 | of your root partition (the one containing the directory /) cannot |
| 101 | be compiled as a module, and so this may be dangerous. |
| 102 | |
| 103 | config EXT3_FS_XATTR |
| 104 | bool "Ext3 extended attributes" |
| 105 | depends on EXT3_FS |
| 106 | default y |
| 107 | help |
| 108 | Extended attributes are name:value pairs associated with inodes by |
| 109 | the kernel or by users (see the attr(5) manual page, or visit |
| 110 | <http://acl.bestbits.at/> for details). |
| 111 | |
| 112 | If unsure, say N. |
| 113 | |
| 114 | You need this for POSIX ACL support on ext3. |
| 115 | |
| 116 | config EXT3_FS_POSIX_ACL |
| 117 | bool "Ext3 POSIX Access Control Lists" |
| 118 | depends on EXT3_FS_XATTR |
Andreas Gruenbacher | b84c215 | 2005-07-07 17:56:57 -0700 | [diff] [blame] | 119 | select FS_POSIX_ACL |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 120 | help |
| 121 | Posix Access Control Lists (ACLs) support permissions for users and |
| 122 | groups beyond the owner/group/world scheme. |
| 123 | |
| 124 | To learn more about Access Control Lists, visit the Posix ACLs for |
| 125 | Linux website <http://acl.bestbits.at/>. |
| 126 | |
| 127 | If you don't know what Access Control Lists are, say N |
| 128 | |
| 129 | config EXT3_FS_SECURITY |
| 130 | bool "Ext3 Security Labels" |
| 131 | depends on EXT3_FS_XATTR |
| 132 | help |
| 133 | Security labels support alternative access control models |
| 134 | implemented by security modules like SELinux. This option |
| 135 | enables an extended attribute handler for file security |
| 136 | labels in the ext3 filesystem. |
| 137 | |
| 138 | If you are not using a security module that requires using |
| 139 | extended attributes for file security labels, say N. |
| 140 | |
| 141 | config JBD |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 142 | tristate |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 143 | help |
| 144 | This is a generic journaling layer for block devices. It is |
Mark Fasheh | b4e40a5 | 2005-12-15 14:31:24 -0800 | [diff] [blame] | 145 | currently used by the ext3 and OCFS2 file systems, but it could |
| 146 | also be used to add journal support to other file systems or block |
| 147 | devices such as RAID or LVM. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 148 | |
Mark Fasheh | b4e40a5 | 2005-12-15 14:31:24 -0800 | [diff] [blame] | 149 | If you are using the ext3 or OCFS2 file systems, you need to |
| 150 | say Y here. If you are not using ext3 OCFS2 then you will probably |
| 151 | want to say N. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 152 | |
| 153 | To compile this device as a module, choose M here: the module will be |
Mark Fasheh | b4e40a5 | 2005-12-15 14:31:24 -0800 | [diff] [blame] | 154 | called jbd. If you are compiling ext3 or OCFS2 into the kernel, |
| 155 | you cannot compile this code as a module. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 156 | |
| 157 | config JBD_DEBUG |
| 158 | bool "JBD (ext3) debugging support" |
| 159 | depends on JBD |
| 160 | help |
| 161 | If you are using the ext3 journaled file system (or potentially any |
| 162 | other file system/device using JBD), this option allows you to |
| 163 | enable debugging output while the system is running, in order to |
| 164 | help track down any problems you are having. By default the |
| 165 | debugging output will be turned off. |
| 166 | |
| 167 | If you select Y here, then you will be able to turn on debugging |
| 168 | with "echo N > /proc/sys/fs/jbd-debug", where N is a number between |
| 169 | 1 and 5, the higher the number, the more debugging output is |
| 170 | generated. To turn debugging off again, do |
| 171 | "echo 0 > /proc/sys/fs/jbd-debug". |
| 172 | |
| 173 | config FS_MBCACHE |
| 174 | # Meta block cache for Extended Attributes (ext2/ext3) |
| 175 | tristate |
| 176 | depends on EXT2_FS_XATTR || EXT3_FS_XATTR |
| 177 | default y if EXT2_FS=y || EXT3_FS=y |
| 178 | default m if EXT2_FS=m || EXT3_FS=m |
| 179 | |
| 180 | config REISERFS_FS |
| 181 | tristate "Reiserfs support" |
| 182 | help |
| 183 | Stores not just filenames but the files themselves in a balanced |
| 184 | tree. Uses journaling. |
| 185 | |
| 186 | Balanced trees are more efficient than traditional file system |
| 187 | architectural foundations. |
| 188 | |
| 189 | In general, ReiserFS is as fast as ext2, but is very efficient with |
| 190 | large directories and small files. Additional patches are needed |
| 191 | for NFS and quotas, please see <http://www.namesys.com/> for links. |
| 192 | |
| 193 | It is more easily extended to have features currently found in |
| 194 | database and keyword search systems than block allocation based file |
| 195 | systems are. The next version will be so extended, and will support |
| 196 | plugins consistent with our motto ``It takes more than a license to |
| 197 | make source code open.'' |
| 198 | |
| 199 | Read <http://www.namesys.com/> to learn more about reiserfs. |
| 200 | |
| 201 | Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com. |
| 202 | |
| 203 | If you like it, you can pay us to add new features to it that you |
| 204 | need, buy a support contract, or pay us to port it to another OS. |
| 205 | |
| 206 | config REISERFS_CHECK |
| 207 | bool "Enable reiserfs debug mode" |
| 208 | depends on REISERFS_FS |
| 209 | help |
| 210 | If you set this to Y, then ReiserFS will perform every check it can |
| 211 | possibly imagine of its internal consistency throughout its |
| 212 | operation. It will also go substantially slower. More than once we |
| 213 | have forgotten that this was on, and then gone despondent over the |
| 214 | latest benchmarks.:-) Use of this option allows our team to go all |
| 215 | out in checking for consistency when debugging without fear of its |
| 216 | effect on end users. If you are on the verge of sending in a bug |
| 217 | report, say Y and you might get a useful error message. Almost |
| 218 | everyone should say N. |
| 219 | |
| 220 | config REISERFS_PROC_INFO |
| 221 | bool "Stats in /proc/fs/reiserfs" |
| 222 | depends on REISERFS_FS |
| 223 | help |
| 224 | Create under /proc/fs/reiserfs a hierarchy of files, displaying |
| 225 | various ReiserFS statistics and internal data at the expense of |
| 226 | making your kernel or module slightly larger (+8 KB). This also |
| 227 | increases the amount of kernel memory required for each mount. |
| 228 | Almost everyone but ReiserFS developers and people fine-tuning |
| 229 | reiserfs or tracing problems should say N. |
| 230 | |
| 231 | config REISERFS_FS_XATTR |
| 232 | bool "ReiserFS extended attributes" |
| 233 | depends on REISERFS_FS |
| 234 | help |
| 235 | Extended attributes are name:value pairs associated with inodes by |
| 236 | the kernel or by users (see the attr(5) manual page, or visit |
| 237 | <http://acl.bestbits.at/> for details). |
| 238 | |
| 239 | If unsure, say N. |
| 240 | |
| 241 | config REISERFS_FS_POSIX_ACL |
| 242 | bool "ReiserFS POSIX Access Control Lists" |
| 243 | depends on REISERFS_FS_XATTR |
Andreas Gruenbacher | b84c215 | 2005-07-07 17:56:57 -0700 | [diff] [blame] | 244 | select FS_POSIX_ACL |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 245 | help |
| 246 | Posix Access Control Lists (ACLs) support permissions for users and |
| 247 | groups beyond the owner/group/world scheme. |
| 248 | |
| 249 | To learn more about Access Control Lists, visit the Posix ACLs for |
| 250 | Linux website <http://acl.bestbits.at/>. |
| 251 | |
| 252 | If you don't know what Access Control Lists are, say N |
| 253 | |
| 254 | config REISERFS_FS_SECURITY |
| 255 | bool "ReiserFS Security Labels" |
| 256 | depends on REISERFS_FS_XATTR |
| 257 | help |
| 258 | Security labels support alternative access control models |
| 259 | implemented by security modules like SELinux. This option |
| 260 | enables an extended attribute handler for file security |
| 261 | labels in the ReiserFS filesystem. |
| 262 | |
| 263 | If you are not using a security module that requires using |
| 264 | extended attributes for file security labels, say N. |
| 265 | |
| 266 | config JFS_FS |
| 267 | tristate "JFS filesystem support" |
| 268 | select NLS |
| 269 | help |
| 270 | This is a port of IBM's Journaled Filesystem . More information is |
| 271 | available in the file <file:Documentation/filesystems/jfs.txt>. |
| 272 | |
| 273 | If you do not intend to use the JFS filesystem, say N. |
| 274 | |
| 275 | config JFS_POSIX_ACL |
| 276 | bool "JFS POSIX Access Control Lists" |
| 277 | depends on JFS_FS |
Andreas Gruenbacher | b84c215 | 2005-07-07 17:56:57 -0700 | [diff] [blame] | 278 | select FS_POSIX_ACL |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 279 | help |
| 280 | Posix Access Control Lists (ACLs) support permissions for users and |
| 281 | groups beyond the owner/group/world scheme. |
| 282 | |
| 283 | To learn more about Access Control Lists, visit the Posix ACLs for |
| 284 | Linux website <http://acl.bestbits.at/>. |
| 285 | |
| 286 | If you don't know what Access Control Lists are, say N |
| 287 | |
| 288 | config JFS_SECURITY |
| 289 | bool "JFS Security Labels" |
| 290 | depends on JFS_FS |
| 291 | help |
| 292 | Security labels support alternative access control models |
| 293 | implemented by security modules like SELinux. This option |
| 294 | enables an extended attribute handler for file security |
| 295 | labels in the jfs filesystem. |
| 296 | |
| 297 | If you are not using a security module that requires using |
| 298 | extended attributes for file security labels, say N. |
| 299 | |
| 300 | config JFS_DEBUG |
| 301 | bool "JFS debugging" |
| 302 | depends on JFS_FS |
| 303 | help |
| 304 | If you are experiencing any problems with the JFS filesystem, say |
| 305 | Y here. This will result in additional debugging messages to be |
| 306 | written to the system log. Under normal circumstances, this |
| 307 | results in very little overhead. |
| 308 | |
| 309 | config JFS_STATISTICS |
| 310 | bool "JFS statistics" |
| 311 | depends on JFS_FS |
| 312 | help |
| 313 | Enabling this option will cause statistics from the JFS file system |
| 314 | to be made available to the user in the /proc/fs/jfs/ directory. |
| 315 | |
| 316 | config FS_POSIX_ACL |
| 317 | # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs) |
| 318 | # |
| 319 | # NOTE: you can implement Posix ACLs without these helpers (XFS does). |
| 320 | # Never use this symbol for ifdefs. |
| 321 | # |
| 322 | bool |
Andreas Gruenbacher | b84c215 | 2005-07-07 17:56:57 -0700 | [diff] [blame] | 323 | default n |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 324 | |
| 325 | source "fs/xfs/Kconfig" |
| 326 | |
Mark Fasheh | b4e40a5 | 2005-12-15 14:31:24 -0800 | [diff] [blame] | 327 | config OCFS2_FS |
| 328 | tristate "OCFS2 file system support (EXPERIMENTAL)" |
| 329 | depends on NET && EXPERIMENTAL |
| 330 | select CONFIGFS_FS |
| 331 | select JBD |
| 332 | select CRC32 |
| 333 | select INET |
| 334 | help |
| 335 | OCFS2 is a general purpose extent based shared disk cluster file |
| 336 | system with many similarities to ext3. It supports 64 bit inode |
| 337 | numbers, and has automatically extending metadata groups which may |
| 338 | also make it attractive for non-clustered use. |
| 339 | |
| 340 | You'll want to install the ocfs2-tools package in order to at least |
| 341 | get "mount.ocfs2". |
| 342 | |
| 343 | Project web page: http://oss.oracle.com/projects/ocfs2 |
| 344 | Tools web page: http://oss.oracle.com/projects/ocfs2-tools |
| 345 | OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/ |
| 346 | |
| 347 | Note: Features which OCFS2 does not support yet: |
| 348 | - extended attributes |
Mark Fasheh | b4e40a5 | 2005-12-15 14:31:24 -0800 | [diff] [blame] | 349 | - shared writeable mmap |
| 350 | - loopback is supported, but data written will not |
| 351 | be cluster coherent. |
| 352 | - quotas |
| 353 | - cluster aware flock |
| 354 | - Directory change notification (F_NOTIFY) |
| 355 | - Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease) |
| 356 | - POSIX ACLs |
| 357 | - readpages / writepages (not user visible) |
| 358 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 359 | config MINIX_FS |
| 360 | tristate "Minix fs support" |
| 361 | help |
| 362 | Minix is a simple operating system used in many classes about OS's. |
| 363 | The minix file system (method to organize files on a hard disk |
| 364 | partition or a floppy disk) was the original file system for Linux, |
| 365 | but has been superseded by the second extended file system ext2fs. |
| 366 | You don't want to use the minix file system on your hard disk |
| 367 | because of certain built-in restrictions, but it is sometimes found |
| 368 | on older Linux floppy disks. This option will enlarge your kernel |
| 369 | by about 28 KB. If unsure, say N. |
| 370 | |
| 371 | To compile this file system support as a module, choose M here: the |
| 372 | module will be called minix. Note that the file system of your root |
| 373 | partition (the one containing the directory /) cannot be compiled as |
| 374 | a module. |
| 375 | |
| 376 | config ROMFS_FS |
| 377 | tristate "ROM file system support" |
| 378 | ---help--- |
| 379 | This is a very small read-only file system mainly intended for |
| 380 | initial ram disks of installation disks, but it could be used for |
| 381 | other read-only media as well. Read |
| 382 | <file:Documentation/filesystems/romfs.txt> for details. |
| 383 | |
| 384 | To compile this file system support as a module, choose M here: the |
| 385 | module will be called romfs. Note that the file system of your |
| 386 | root partition (the one containing the directory /) cannot be a |
| 387 | module. |
| 388 | |
| 389 | If you don't know whether you need it, then you don't need it: |
| 390 | answer N. |
| 391 | |
Robert Love | 0eeca28 | 2005-07-12 17:06:03 -0400 | [diff] [blame] | 392 | config INOTIFY |
| 393 | bool "Inotify file change notification support" |
| 394 | default y |
| 395 | ---help--- |
Robert Love | 3de1174 | 2005-08-04 13:07:08 -0700 | [diff] [blame] | 396 | Say Y here to enable inotify support and the associated system |
| 397 | calls. Inotify is a file change notification system and a |
Robert Love | 0eeca28 | 2005-07-12 17:06:03 -0400 | [diff] [blame] | 398 | replacement for dnotify. Inotify fixes numerous shortcomings in |
| 399 | dnotify and introduces several new features. It allows monitoring |
Robert Love | 3de1174 | 2005-08-04 13:07:08 -0700 | [diff] [blame] | 400 | of both files and directories via a single open fd. Other features |
| 401 | include multiple file events, one-shot support, and unmount |
| 402 | notification. |
| 403 | |
| 404 | For more information, see Documentation/filesystems/inotify.txt |
Robert Love | 0eeca28 | 2005-07-12 17:06:03 -0400 | [diff] [blame] | 405 | |
| 406 | If unsure, say Y. |
| 407 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 408 | config QUOTA |
| 409 | bool "Quota support" |
| 410 | help |
| 411 | If you say Y here, you will be able to set per user limits for disk |
| 412 | usage (also called disk quotas). Currently, it works for the |
| 413 | ext2, ext3, and reiserfs file system. ext3 also supports journalled |
| 414 | quotas for which you don't need to run quotacheck(8) after an unclean |
Adrian Bunk | 919532a | 2005-09-06 15:17:22 -0700 | [diff] [blame] | 415 | shutdown. |
| 416 | For further details, read the Quota mini-HOWTO, available from |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 417 | <http://www.tldp.org/docs.html#howto>, or the documentation provided |
| 418 | with the quota tools. Probably the quota support is only useful for |
| 419 | multi user systems. If unsure, say N. |
| 420 | |
| 421 | config QFMT_V1 |
| 422 | tristate "Old quota format support" |
| 423 | depends on QUOTA |
| 424 | help |
| 425 | This quota format was (is) used by kernels earlier than 2.4.22. If |
| 426 | you have quota working and you don't want to convert to new quota |
| 427 | format say Y here. |
| 428 | |
| 429 | config QFMT_V2 |
| 430 | tristate "Quota format v2 support" |
| 431 | depends on QUOTA |
| 432 | help |
| 433 | This quota format allows using quotas with 32-bit UIDs/GIDs. If you |
Adrian Bunk | 919532a | 2005-09-06 15:17:22 -0700 | [diff] [blame] | 434 | need this functionality say Y here. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 435 | |
| 436 | config QUOTACTL |
| 437 | bool |
| 438 | depends on XFS_QUOTA || QUOTA |
| 439 | default y |
| 440 | |
| 441 | config DNOTIFY |
| 442 | bool "Dnotify support" if EMBEDDED |
| 443 | default y |
| 444 | help |
| 445 | Dnotify is a directory-based per-fd file change notification system |
| 446 | that uses signals to communicate events to user-space. There exist |
| 447 | superior alternatives, but some applications may still rely on |
| 448 | dnotify. |
| 449 | |
| 450 | Because of this, if unsure, say Y. |
| 451 | |
| 452 | config AUTOFS_FS |
| 453 | tristate "Kernel automounter support" |
| 454 | help |
| 455 | The automounter is a tool to automatically mount remote file systems |
| 456 | on demand. This implementation is partially kernel-based to reduce |
| 457 | overhead in the already-mounted case; this is unlike the BSD |
| 458 | automounter (amd), which is a pure user space daemon. |
| 459 | |
| 460 | To use the automounter you need the user-space tools from the autofs |
| 461 | package; you can find the location in <file:Documentation/Changes>. |
| 462 | You also want to answer Y to "NFS file system support", below. |
| 463 | |
| 464 | If you want to use the newer version of the automounter with more |
| 465 | features, say N here and say Y to "Kernel automounter v4 support", |
| 466 | below. |
| 467 | |
| 468 | To compile this support as a module, choose M here: the module will be |
| 469 | called autofs. |
| 470 | |
| 471 | If you are not a part of a fairly large, distributed network, you |
| 472 | probably do not need an automounter, and can say N here. |
| 473 | |
| 474 | config AUTOFS4_FS |
| 475 | tristate "Kernel automounter version 4 support (also supports v3)" |
| 476 | help |
| 477 | The automounter is a tool to automatically mount remote file systems |
| 478 | on demand. This implementation is partially kernel-based to reduce |
| 479 | overhead in the already-mounted case; this is unlike the BSD |
| 480 | automounter (amd), which is a pure user space daemon. |
| 481 | |
| 482 | To use the automounter you need the user-space tools from |
| 483 | <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also |
| 484 | want to answer Y to "NFS file system support", below. |
| 485 | |
| 486 | To compile this support as a module, choose M here: the module will be |
| 487 | called autofs4. You will need to add "alias autofs autofs4" to your |
| 488 | modules configuration file. |
| 489 | |
| 490 | If you are not a part of a fairly large, distributed network or |
| 491 | don't have a laptop which needs to dynamically reconfigure to the |
| 492 | local network, you probably do not need an automounter, and can say |
| 493 | N here. |
| 494 | |
Miklos Szeredi | 04578f1 | 2005-09-09 13:10:22 -0700 | [diff] [blame] | 495 | config FUSE_FS |
| 496 | tristate "Filesystem in Userspace support" |
| 497 | help |
| 498 | With FUSE it is possible to implement a fully functional filesystem |
| 499 | in a userspace program. |
| 500 | |
| 501 | There's also companion library: libfuse. This library along with |
| 502 | utilities is available from the FUSE homepage: |
| 503 | <http://fuse.sourceforge.net/> |
| 504 | |
Miklos Szeredi | 909021e | 2005-09-27 21:45:20 -0700 | [diff] [blame] | 505 | See <file:Documentation/filesystems/fuse.txt> for more information. |
| 506 | See <file:Documentation/Changes> for needed library/utility version. |
| 507 | |
Miklos Szeredi | 04578f1 | 2005-09-09 13:10:22 -0700 | [diff] [blame] | 508 | If you want to develop a userspace FS, or if you want to use |
| 509 | a filesystem based on FUSE, answer Y or M. |
| 510 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 511 | menu "CD-ROM/DVD Filesystems" |
| 512 | |
| 513 | config ISO9660_FS |
| 514 | tristate "ISO 9660 CDROM file system support" |
| 515 | help |
| 516 | This is the standard file system used on CD-ROMs. It was previously |
| 517 | known as "High Sierra File System" and is called "hsfs" on other |
| 518 | Unix systems. The so-called Rock-Ridge extensions which allow for |
| 519 | long Unix filenames and symbolic links are also supported by this |
| 520 | driver. If you have a CD-ROM drive and want to do more with it than |
| 521 | just listen to audio CDs and watch its LEDs, say Y (and read |
| 522 | <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO, |
| 523 | available from <http://www.tldp.org/docs.html#howto>), thereby |
| 524 | enlarging your kernel by about 27 KB; otherwise say N. |
| 525 | |
| 526 | To compile this file system support as a module, choose M here: the |
| 527 | module will be called isofs. |
| 528 | |
| 529 | config JOLIET |
| 530 | bool "Microsoft Joliet CDROM extensions" |
| 531 | depends on ISO9660_FS |
| 532 | select NLS |
| 533 | help |
| 534 | Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system |
| 535 | which allows for long filenames in unicode format (unicode is the |
| 536 | new 16 bit character code, successor to ASCII, which encodes the |
| 537 | characters of almost all languages of the world; see |
| 538 | <http://www.unicode.org/> for more information). Say Y here if you |
| 539 | want to be able to read Joliet CD-ROMs under Linux. |
| 540 | |
| 541 | config ZISOFS |
| 542 | bool "Transparent decompression extension" |
| 543 | depends on ISO9660_FS |
| 544 | select ZLIB_INFLATE |
| 545 | help |
| 546 | This is a Linux-specific extension to RockRidge which lets you store |
| 547 | data in compressed form on a CD-ROM and have it transparently |
| 548 | decompressed when the CD-ROM is accessed. See |
| 549 | <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools |
| 550 | necessary to create such a filesystem. Say Y here if you want to be |
| 551 | able to read such compressed CD-ROMs. |
| 552 | |
| 553 | config ZISOFS_FS |
| 554 | # for fs/nls/Config.in |
| 555 | tristate |
| 556 | depends on ZISOFS |
| 557 | default ISO9660_FS |
| 558 | |
| 559 | config UDF_FS |
| 560 | tristate "UDF file system support" |
| 561 | help |
| 562 | This is the new file system used on some CD-ROMs and DVDs. Say Y if |
| 563 | you intend to mount DVD discs or CDRW's written in packet mode, or |
| 564 | if written to by other UDF utilities, such as DirectCD. |
| 565 | Please read <file:Documentation/filesystems/udf.txt>. |
| 566 | |
| 567 | To compile this file system support as a module, choose M here: the |
| 568 | module will be called udf. |
| 569 | |
| 570 | If unsure, say N. |
| 571 | |
| 572 | config UDF_NLS |
| 573 | bool |
| 574 | default y |
| 575 | depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y) |
| 576 | |
| 577 | endmenu |
| 578 | |
| 579 | menu "DOS/FAT/NT Filesystems" |
| 580 | |
| 581 | config FAT_FS |
| 582 | tristate |
| 583 | select NLS |
| 584 | help |
| 585 | If you want to use one of the FAT-based file systems (the MS-DOS and |
| 586 | VFAT (Windows 95) file systems), then you must say Y or M here |
| 587 | to include FAT support. You will then be able to mount partitions or |
| 588 | diskettes with FAT-based file systems and transparently access the |
| 589 | files on them, i.e. MSDOS files will look and behave just like all |
| 590 | other Unix files. |
| 591 | |
| 592 | This FAT support is not a file system in itself, it only provides |
| 593 | the foundation for the other file systems. You will have to say Y or |
| 594 | M to at least one of "MSDOS fs support" or "VFAT fs support" in |
| 595 | order to make use of it. |
| 596 | |
| 597 | Another way to read and write MSDOS floppies and hard drive |
| 598 | partitions from within Linux (but not transparently) is with the |
| 599 | mtools ("man mtools") program suite. You don't need to say Y here in |
| 600 | order to do that. |
| 601 | |
| 602 | If you need to move large files on floppies between a DOS and a |
| 603 | Linux box, say Y here, mount the floppy under Linux with an MSDOS |
| 604 | file system and use GNU tar's M option. GNU tar is a program |
| 605 | available for Unix and DOS ("man tar" or "info tar"). |
| 606 | |
| 607 | It is now also becoming possible to read and write compressed FAT |
| 608 | file systems; read <file:Documentation/filesystems/fat_cvf.txt> for |
| 609 | details. |
| 610 | |
| 611 | The FAT support will enlarge your kernel by about 37 KB. If unsure, |
| 612 | say Y. |
| 613 | |
| 614 | To compile this as a module, choose M here: the module will be called |
| 615 | fat. Note that if you compile the FAT support as a module, you |
| 616 | cannot compile any of the FAT-based file systems into the kernel |
| 617 | -- they will have to be modules as well. |
| 618 | |
| 619 | config MSDOS_FS |
| 620 | tristate "MSDOS fs support" |
| 621 | select FAT_FS |
| 622 | help |
| 623 | This allows you to mount MSDOS partitions of your hard drive (unless |
| 624 | they are compressed; to access compressed MSDOS partitions under |
| 625 | Linux, you can either use the DOS emulator DOSEMU, described in the |
| 626 | DOSEMU-HOWTO, available from |
| 627 | <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in |
| 628 | <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you |
| 629 | intend to use dosemu with a non-compressed MSDOS partition, say Y |
| 630 | here) and MSDOS floppies. This means that file access becomes |
| 631 | transparent, i.e. the MSDOS files look and behave just like all |
| 632 | other Unix files. |
| 633 | |
| 634 | If you have Windows 95 or Windows NT installed on your MSDOS |
| 635 | partitions, you should use the VFAT file system (say Y to "VFAT fs |
| 636 | support" below), or you will not be able to see the long filenames |
| 637 | generated by Windows 95 / Windows NT. |
| 638 | |
| 639 | This option will enlarge your kernel by about 7 KB. If unsure, |
| 640 | answer Y. This will only work if you said Y to "DOS FAT fs support" |
| 641 | as well. To compile this as a module, choose M here: the module will |
| 642 | be called msdos. |
| 643 | |
| 644 | config VFAT_FS |
| 645 | tristate "VFAT (Windows-95) fs support" |
| 646 | select FAT_FS |
| 647 | help |
| 648 | This option provides support for normal Windows file systems with |
| 649 | long filenames. That includes non-compressed FAT-based file systems |
| 650 | used by Windows 95, Windows 98, Windows NT 4.0, and the Unix |
| 651 | programs from the mtools package. |
| 652 | |
| 653 | The VFAT support enlarges your kernel by about 10 KB and it only |
| 654 | works if you said Y to the "DOS FAT fs support" above. Please read |
| 655 | the file <file:Documentation/filesystems/vfat.txt> for details. If |
| 656 | unsure, say Y. |
| 657 | |
| 658 | To compile this as a module, choose M here: the module will be called |
| 659 | vfat. |
| 660 | |
| 661 | config FAT_DEFAULT_CODEPAGE |
| 662 | int "Default codepage for FAT" |
| 663 | depends on MSDOS_FS || VFAT_FS |
| 664 | default 437 |
| 665 | help |
| 666 | This option should be set to the codepage of your FAT filesystems. |
| 667 | It can be overridden with the "codepage" mount option. |
| 668 | See <file:Documentation/filesystems/vfat.txt> for more information. |
| 669 | |
| 670 | config FAT_DEFAULT_IOCHARSET |
| 671 | string "Default iocharset for FAT" |
| 672 | depends on VFAT_FS |
| 673 | default "iso8859-1" |
| 674 | help |
| 675 | Set this to the default input/output character set you'd |
| 676 | like FAT to use. It should probably match the character set |
| 677 | that most of your FAT filesystems use, and can be overridden |
| 678 | with the "iocharset" mount option for FAT filesystems. |
| 679 | Note that "utf8" is not recommended for FAT filesystems. |
| 680 | If unsure, you shouldn't set "utf8" here. |
| 681 | See <file:Documentation/filesystems/vfat.txt> for more information. |
| 682 | |
| 683 | config NTFS_FS |
| 684 | tristate "NTFS file system support" |
| 685 | select NLS |
| 686 | help |
| 687 | NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003. |
| 688 | |
| 689 | Saying Y or M here enables read support. There is partial, but |
| 690 | safe, write support available. For write support you must also |
| 691 | say Y to "NTFS write support" below. |
| 692 | |
| 693 | There are also a number of user-space tools available, called |
| 694 | ntfsprogs. These include ntfsundelete and ntfsresize, that work |
| 695 | without NTFS support enabled in the kernel. |
| 696 | |
| 697 | This is a rewrite from scratch of Linux NTFS support and replaced |
| 698 | the old NTFS code starting with Linux 2.5.11. A backport to |
| 699 | the Linux 2.4 kernel series is separately available as a patch |
| 700 | from the project web site. |
| 701 | |
| 702 | For more information see <file:Documentation/filesystems/ntfs.txt> |
| 703 | and <http://linux-ntfs.sourceforge.net/>. |
| 704 | |
| 705 | To compile this file system support as a module, choose M here: the |
| 706 | module will be called ntfs. |
| 707 | |
| 708 | If you are not using Windows NT, 2000, XP or 2003 in addition to |
| 709 | Linux on your computer it is safe to say N. |
| 710 | |
| 711 | config NTFS_DEBUG |
| 712 | bool "NTFS debugging support" |
| 713 | depends on NTFS_FS |
| 714 | help |
| 715 | If you are experiencing any problems with the NTFS file system, say |
| 716 | Y here. This will result in additional consistency checks to be |
| 717 | performed by the driver as well as additional debugging messages to |
| 718 | be written to the system log. Note that debugging messages are |
| 719 | disabled by default. To enable them, supply the option debug_msgs=1 |
| 720 | at the kernel command line when booting the kernel or as an option |
| 721 | to insmod when loading the ntfs module. Once the driver is active, |
| 722 | you can enable debugging messages by doing (as root): |
| 723 | echo 1 > /proc/sys/fs/ntfs-debug |
| 724 | Replacing the "1" with "0" would disable debug messages. |
| 725 | |
| 726 | If you leave debugging messages disabled, this results in little |
| 727 | overhead, but enabling debug messages results in very significant |
| 728 | slowdown of the system. |
| 729 | |
| 730 | When reporting bugs, please try to have available a full dump of |
| 731 | debugging messages while the misbehaviour was occurring. |
| 732 | |
| 733 | config NTFS_RW |
| 734 | bool "NTFS write support" |
| 735 | depends on NTFS_FS |
| 736 | help |
| 737 | This enables the partial, but safe, write support in the NTFS driver. |
| 738 | |
| 739 | The only supported operation is overwriting existing files, without |
| 740 | changing the file length. No file or directory creation, deletion or |
| 741 | renaming is possible. Note only non-resident files can be written to |
| 742 | so you may find that some very small files (<500 bytes or so) cannot |
| 743 | be written to. |
| 744 | |
| 745 | While we cannot guarantee that it will not damage any data, we have |
| 746 | so far not received a single report where the driver would have |
| 747 | damaged someones data so we assume it is perfectly safe to use. |
| 748 | |
| 749 | Note: While write support is safe in this version (a rewrite from |
| 750 | scratch of the NTFS support), it should be noted that the old NTFS |
| 751 | write support, included in Linux 2.5.10 and before (since 1997), |
| 752 | is not safe. |
| 753 | |
| 754 | This is currently useful with TopologiLinux. TopologiLinux is run |
| 755 | on top of any DOS/Microsoft Windows system without partitioning your |
| 756 | hard disk. Unlike other Linux distributions TopologiLinux does not |
| 757 | need its own partition. For more information see |
| 758 | <http://topologi-linux.sourceforge.net/> |
| 759 | |
| 760 | It is perfectly safe to say N here. |
| 761 | |
| 762 | endmenu |
| 763 | |
| 764 | menu "Pseudo filesystems" |
| 765 | |
| 766 | config PROC_FS |
| 767 | bool "/proc file system support" |
| 768 | help |
| 769 | This is a virtual file system providing information about the status |
| 770 | of the system. "Virtual" means that it doesn't take up any space on |
| 771 | your hard disk: the files are created on the fly by the kernel when |
| 772 | you try to access them. Also, you cannot read the files with older |
| 773 | version of the program less: you need to use more or cat. |
| 774 | |
| 775 | It's totally cool; for example, "cat /proc/interrupts" gives |
| 776 | information about what the different IRQs are used for at the moment |
| 777 | (there is a small number of Interrupt ReQuest lines in your computer |
| 778 | that are used by the attached devices to gain the CPU's attention -- |
| 779 | often a source of trouble if two devices are mistakenly configured |
| 780 | to use the same IRQ). The program procinfo to display some |
| 781 | information about your system gathered from the /proc file system. |
| 782 | |
| 783 | Before you can use the /proc file system, it has to be mounted, |
| 784 | meaning it has to be given a location in the directory hierarchy. |
| 785 | That location should be /proc. A command such as "mount -t proc proc |
| 786 | /proc" or the equivalent line in /etc/fstab does the job. |
| 787 | |
| 788 | The /proc file system is explained in the file |
| 789 | <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage |
| 790 | ("man 5 proc"). |
| 791 | |
| 792 | This option will enlarge your kernel by about 67 KB. Several |
| 793 | programs depend on this, so everyone should say Y here. |
| 794 | |
| 795 | config PROC_KCORE |
| 796 | bool "/proc/kcore support" if !ARM |
| 797 | depends on PROC_FS && MMU |
| 798 | |
Vivek Goyal | 666bfdd | 2005-06-25 14:58:21 -0700 | [diff] [blame] | 799 | config PROC_VMCORE |
| 800 | bool "/proc/vmcore support (EXPERIMENTAL)" |
Maneesh Soni | 05970d4 | 2006-01-09 20:51:52 -0800 | [diff] [blame] | 801 | depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP |
Vivek Goyal | 68250ba | 2006-04-10 22:54:30 -0700 | [diff] [blame] | 802 | default y |
Vivek Goyal | 666bfdd | 2005-06-25 14:58:21 -0700 | [diff] [blame] | 803 | help |
| 804 | Exports the dump image of crashed kernel in ELF format. |
| 805 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 806 | config SYSFS |
| 807 | bool "sysfs file system support" if EMBEDDED |
| 808 | default y |
| 809 | help |
| 810 | The sysfs filesystem is a virtual filesystem that the kernel uses to |
| 811 | export internal kernel objects, their attributes, and their |
| 812 | relationships to one another. |
| 813 | |
| 814 | Users can use sysfs to ascertain useful information about the running |
| 815 | kernel, such as the devices the kernel has discovered on each bus and |
| 816 | which driver each is bound to. sysfs can also be used to tune devices |
| 817 | and other kernel subsystems. |
| 818 | |
| 819 | Some system agents rely on the information in sysfs to operate. |
| 820 | /sbin/hotplug uses device and object attributes in sysfs to assist in |
| 821 | delegating policy decisions, like persistantly naming devices. |
| 822 | |
| 823 | sysfs is currently used by the block subsystem to mount the root |
| 824 | partition. If sysfs is disabled you must specify the boot device on |
| 825 | the kernel boot command line via its major and minor numbers. For |
| 826 | example, "root=03:01" for /dev/hda1. |
| 827 | |
| 828 | Designers of embedded systems may wish to say N here to conserve space. |
| 829 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 830 | config TMPFS |
| 831 | bool "Virtual memory file system support (former shm fs)" |
| 832 | help |
| 833 | Tmpfs is a file system which keeps all files in virtual memory. |
| 834 | |
| 835 | Everything in tmpfs is temporary in the sense that no files will be |
| 836 | created on your hard drive. The files live in memory and swap |
| 837 | space. If you unmount a tmpfs instance, everything stored therein is |
| 838 | lost. |
| 839 | |
| 840 | See <file:Documentation/filesystems/tmpfs.txt> for details. |
| 841 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 842 | config HUGETLBFS |
| 843 | bool "HugeTLB file system support" |
Brian Gerst | 0d078f6 | 2005-10-30 14:59:20 -0800 | [diff] [blame] | 844 | depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN |
Arthur Othieno | dda27d1 | 2006-04-18 22:20:57 -0700 | [diff] [blame] | 845 | help |
| 846 | hugetlbfs is a filesystem backing for HugeTLB pages, based on |
| 847 | ramfs. For architectures that support it, say Y here and read |
| 848 | <file:Documentation/vm/hugetlbpage.txt> for details. |
| 849 | |
| 850 | If unsure, say N. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 851 | |
| 852 | config HUGETLB_PAGE |
| 853 | def_bool HUGETLBFS |
| 854 | |
| 855 | config RAMFS |
| 856 | bool |
| 857 | default y |
| 858 | ---help--- |
| 859 | Ramfs is a file system which keeps all files in RAM. It allows |
| 860 | read and write access. |
| 861 | |
| 862 | It is more of an programming example than a useable file system. If |
| 863 | you need a file system which lives in RAM with limit checking use |
| 864 | tmpfs. |
| 865 | |
| 866 | To compile this as a module, choose M here: the module will be called |
| 867 | ramfs. |
| 868 | |
Joel Becker | 7063fbf | 2005-12-15 14:29:43 -0800 | [diff] [blame] | 869 | config CONFIGFS_FS |
| 870 | tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)" |
Adrian Bunk | 65714b9 | 2006-03-26 14:25:52 +0200 | [diff] [blame] | 871 | depends on SYSFS && EXPERIMENTAL |
Joel Becker | 7063fbf | 2005-12-15 14:29:43 -0800 | [diff] [blame] | 872 | help |
| 873 | configfs is a ram-based filesystem that provides the converse |
| 874 | of sysfs's functionality. Where sysfs is a filesystem-based |
| 875 | view of kernel objects, configfs is a filesystem-based manager |
| 876 | of kernel objects, or config_items. |
| 877 | |
| 878 | Both sysfs and configfs can and should exist together on the |
| 879 | same system. One is not a replacement for the other. |
| 880 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 881 | endmenu |
| 882 | |
| 883 | menu "Miscellaneous filesystems" |
| 884 | |
| 885 | config ADFS_FS |
| 886 | tristate "ADFS file system support (EXPERIMENTAL)" |
| 887 | depends on EXPERIMENTAL |
| 888 | help |
| 889 | The Acorn Disc Filing System is the standard file system of the |
| 890 | RiscOS operating system which runs on Acorn's ARM-based Risc PC |
| 891 | systems and the Acorn Archimedes range of machines. If you say Y |
| 892 | here, Linux will be able to read from ADFS partitions on hard drives |
| 893 | and from ADFS-formatted floppy discs. If you also want to be able to |
| 894 | write to those devices, say Y to "ADFS write support" below. |
| 895 | |
| 896 | The ADFS partition should be the first partition (i.e., |
| 897 | /dev/[hs]d?1) on each of your drives. Please read the file |
| 898 | <file:Documentation/filesystems/adfs.txt> for further details. |
| 899 | |
| 900 | To compile this code as a module, choose M here: the module will be |
| 901 | called adfs. |
| 902 | |
| 903 | If unsure, say N. |
| 904 | |
| 905 | config ADFS_FS_RW |
| 906 | bool "ADFS write support (DANGEROUS)" |
| 907 | depends on ADFS_FS |
| 908 | help |
| 909 | If you say Y here, you will be able to write to ADFS partitions on |
| 910 | hard drives and ADFS-formatted floppy disks. This is experimental |
| 911 | codes, so if you're unsure, say N. |
| 912 | |
| 913 | config AFFS_FS |
| 914 | tristate "Amiga FFS file system support (EXPERIMENTAL)" |
| 915 | depends on EXPERIMENTAL |
| 916 | help |
| 917 | The Fast File System (FFS) is the common file system used on hard |
| 918 | disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y |
| 919 | if you want to be able to read and write files from and to an Amiga |
| 920 | FFS partition on your hard drive. Amiga floppies however cannot be |
| 921 | read with this driver due to an incompatibility of the floppy |
| 922 | controller used in an Amiga and the standard floppy controller in |
| 923 | PCs and workstations. Read <file:Documentation/filesystems/affs.txt> |
| 924 | and <file:fs/affs/Changes>. |
| 925 | |
| 926 | With this driver you can also mount disk files used by Bernd |
| 927 | Schmidt's Un*X Amiga Emulator |
| 928 | (<http://www.freiburg.linux.de/~uae/>). |
| 929 | If you want to do this, you will also need to say Y or M to "Loop |
| 930 | device support", above. |
| 931 | |
| 932 | To compile this file system support as a module, choose M here: the |
| 933 | module will be called affs. If unsure, say N. |
| 934 | |
| 935 | config HFS_FS |
| 936 | tristate "Apple Macintosh file system support (EXPERIMENTAL)" |
| 937 | depends on EXPERIMENTAL |
Lennert Buytenhek | 878129a | 2005-11-07 00:59:18 -0800 | [diff] [blame] | 938 | select NLS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 939 | help |
| 940 | If you say Y here, you will be able to mount Macintosh-formatted |
| 941 | floppy disks and hard drive partitions with full read-write access. |
| 942 | Please read <file:fs/hfs/HFS.txt> to learn about the available mount |
| 943 | options. |
| 944 | |
| 945 | To compile this file system support as a module, choose M here: the |
| 946 | module will be called hfs. |
| 947 | |
| 948 | config HFSPLUS_FS |
| 949 | tristate "Apple Extended HFS file system support" |
| 950 | select NLS |
| 951 | select NLS_UTF8 |
| 952 | help |
| 953 | If you say Y here, you will be able to mount extended format |
| 954 | Macintosh-formatted hard drive partitions with full read-write access. |
| 955 | |
| 956 | This file system is often called HFS+ and was introduced with |
| 957 | MacOS 8. It includes all Mac specific filesystem data such as |
| 958 | data forks and creator codes, but it also has several UNIX |
| 959 | style features such as file ownership and permissions. |
| 960 | |
| 961 | config BEFS_FS |
| 962 | tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)" |
| 963 | depends on EXPERIMENTAL |
| 964 | select NLS |
| 965 | help |
| 966 | The BeOS File System (BeFS) is the native file system of Be, Inc's |
| 967 | BeOS. Notable features include support for arbitrary attributes |
| 968 | on files and directories, and database-like indeces on selected |
| 969 | attributes. (Also note that this driver doesn't make those features |
| 970 | available at this time). It is a 64 bit filesystem, so it supports |
| 971 | extremly 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. |
| 1007 | |
| 1008 | |
| 1009 | |
| 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. |
| 1040 | |
| 1041 | config JFFS_PROC_FS |
| 1042 | bool "JFFS stats available in /proc filesystem" |
| 1043 | depends on JFFS_FS && PROC_FS |
| 1044 | help |
| 1045 | Enabling this option will cause statistics from mounted JFFS file systems |
| 1046 | to be made available to the user in the /proc/fs/jffs/ directory. |
| 1047 | |
| 1048 | config JFFS2_FS |
| 1049 | tristate "Journalling Flash File System v2 (JFFS2) support" |
| 1050 | select CRC32 |
| 1051 | depends on MTD |
| 1052 | help |
| 1053 | JFFS2 is the second generation of the Journalling Flash File System |
| 1054 | for use on diskless embedded devices. It provides improved wear |
| 1055 | levelling, compression and support for hard links. You cannot use |
| 1056 | this on normal block devices, only on 'MTD' devices. |
| 1057 | |
| 1058 | Further information on the design and implementation of JFFS2 is |
| 1059 | available at <http://sources.redhat.com/jffs2/>. |
| 1060 | |
| 1061 | config JFFS2_FS_DEBUG |
| 1062 | int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)" |
| 1063 | depends on JFFS2_FS |
| 1064 | default "0" |
| 1065 | help |
| 1066 | This controls the amount of debugging messages produced by the JFFS2 |
| 1067 | code. Set it to zero for use in production systems. For evaluation, |
| 1068 | testing and debugging, it's advisable to set it to one. This will |
| 1069 | enable a few assertions and will print debugging messages at the |
| 1070 | KERN_DEBUG loglevel, where they won't normally be visible. Level 2 |
| 1071 | is unlikely to be useful - it enables extra debugging in certain |
| 1072 | areas which at one point needed debugging, but when the bugs were |
| 1073 | located and fixed, the detailed messages were relegated to level 2. |
| 1074 | |
| 1075 | If reporting bugs, please try to have available a full dump of the |
| 1076 | messages at debug level 1 while the misbehaviour was occurring. |
| 1077 | |
KaiGai Kohei | aa98d7c | 2006-05-13 15:09:47 +0900 | [diff] [blame] | 1078 | config JFFS2_FS_XATTR |
| 1079 | bool "JFFS2 XATTR support" |
| 1080 | depends on JFFS2_FS |
| 1081 | default n |
| 1082 | help |
| 1083 | Extended attributes are name:value pairs associated with inodes by |
| 1084 | the kernel or by users (see the attr(5) manual page, or visit |
| 1085 | <http://acl.bestbits.at/> for details). |
| 1086 | |
| 1087 | If unsure, say N. |
| 1088 | |
| 1089 | config JFFS2_FS_POSIX_ACL |
| 1090 | bool "JFFS2 POSIX Access Control Lists" |
| 1091 | depends on JFFS2_FS_XATTR |
| 1092 | default y |
| 1093 | select FS_POSIX_ACL |
| 1094 | help |
| 1095 | Posix Access Control Lists (ACLs) support permissions for users and |
| 1096 | groups beyond the owner/group/world scheme. |
| 1097 | |
| 1098 | To learn more about Access Control Lists, visit the Posix ACLs for |
| 1099 | Linux website <http://acl.bestbits.at/>. |
| 1100 | |
| 1101 | If you don't know what Access Control Lists are, say N |
| 1102 | |
| 1103 | config JFFS2_FS_SECURITY |
| 1104 | bool "JFFS2 Security Labels" |
| 1105 | depends on JFFS2_FS_XATTR |
| 1106 | default y |
| 1107 | help |
| 1108 | Security labels support alternative access control models |
| 1109 | implemented by security modules like SELinux. This option |
| 1110 | enables an extended attribute handler for file security |
| 1111 | labels in the jffs2 filesystem. |
| 1112 | |
| 1113 | If you are not using a security module that requires using |
| 1114 | extended attributes for file security labels, say N. |
| 1115 | |
Andrew Victor | 2f82ce1 | 2005-02-09 09:24:26 +0000 | [diff] [blame] | 1116 | config JFFS2_FS_WRITEBUFFER |
| 1117 | bool "JFFS2 write-buffering support" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1118 | depends on JFFS2_FS |
Andrew Victor | 2f82ce1 | 2005-02-09 09:24:26 +0000 | [diff] [blame] | 1119 | default y |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1120 | help |
Andrew Victor | 2f82ce1 | 2005-02-09 09:24:26 +0000 | [diff] [blame] | 1121 | This enables the write-buffering support in JFFS2. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1122 | |
Andrew Victor | 2f82ce1 | 2005-02-09 09:24:26 +0000 | [diff] [blame] | 1123 | This functionality is required to support JFFS2 on the following |
| 1124 | types of flash devices: |
| 1125 | - NAND flash |
| 1126 | - NOR flash with transparent ECC |
| 1127 | - DataFlash |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1128 | |
Ferenc Havasi | e631ddb | 2005-09-07 09:35:26 +0100 | [diff] [blame] | 1129 | config JFFS2_SUMMARY |
| 1130 | bool "JFFS2 summary support (EXPERIMENTAL)" |
| 1131 | depends on JFFS2_FS && EXPERIMENTAL |
| 1132 | default n |
| 1133 | help |
| 1134 | This feature makes it possible to use summary information |
| 1135 | for faster filesystem mount. |
| 1136 | |
| 1137 | The summary information can be inserted into a filesystem image |
| 1138 | by the utility 'sumtool'. |
| 1139 | |
| 1140 | If unsure, say 'N'. |
| 1141 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1142 | config JFFS2_COMPRESSION_OPTIONS |
| 1143 | bool "Advanced compression options for JFFS2" |
| 1144 | depends on JFFS2_FS |
| 1145 | default n |
| 1146 | help |
| 1147 | Enabling this option allows you to explicitly choose which |
| 1148 | compression modules, if any, are enabled in JFFS2. Removing |
| 1149 | compressors and mean you cannot read existing file systems, |
| 1150 | and enabling experimental compressors can mean that you |
| 1151 | write a file system which cannot be read by a standard kernel. |
| 1152 | |
| 1153 | If unsure, you should _definitely_ say 'N'. |
| 1154 | |
| 1155 | config JFFS2_ZLIB |
| 1156 | bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS |
| 1157 | select ZLIB_INFLATE |
| 1158 | select ZLIB_DEFLATE |
| 1159 | depends on JFFS2_FS |
| 1160 | default y |
| 1161 | help |
| 1162 | Zlib is designed to be a free, general-purpose, legally unencumbered, |
Thomas Gleixner | 182ec4e | 2005-11-07 11:16:07 +0000 | [diff] [blame] | 1163 | lossless data-compression library for use on virtually any computer |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1164 | hardware and operating system. See <http://www.gzip.org/zlib/> for |
| 1165 | further information. |
Thomas Gleixner | 182ec4e | 2005-11-07 11:16:07 +0000 | [diff] [blame] | 1166 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1167 | Say 'Y' if unsure. |
| 1168 | |
| 1169 | config JFFS2_RTIME |
| 1170 | bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS |
| 1171 | depends on JFFS2_FS |
| 1172 | default y |
| 1173 | help |
| 1174 | Rtime does manage to recompress already-compressed data. Say 'Y' if unsure. |
| 1175 | |
| 1176 | config JFFS2_RUBIN |
| 1177 | bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS |
| 1178 | depends on JFFS2_FS |
| 1179 | default n |
| 1180 | help |
| 1181 | RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure. |
| 1182 | |
| 1183 | choice |
| 1184 | prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS |
| 1185 | default JFFS2_CMODE_PRIORITY |
| 1186 | depends on JFFS2_FS |
| 1187 | help |
Thomas Gleixner | 182ec4e | 2005-11-07 11:16:07 +0000 | [diff] [blame] | 1188 | You can set here the default compression mode of JFFS2 from |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1189 | the available compression modes. Don't touch if unsure. |
| 1190 | |
| 1191 | config JFFS2_CMODE_NONE |
| 1192 | bool "no compression" |
| 1193 | help |
| 1194 | Uses no compression. |
| 1195 | |
| 1196 | config JFFS2_CMODE_PRIORITY |
| 1197 | bool "priority" |
| 1198 | help |
Thomas Gleixner | 182ec4e | 2005-11-07 11:16:07 +0000 | [diff] [blame] | 1199 | Tries the compressors in a predefinied order and chooses the first |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1200 | successful one. |
| 1201 | |
| 1202 | config JFFS2_CMODE_SIZE |
| 1203 | bool "size (EXPERIMENTAL)" |
| 1204 | help |
Thomas Gleixner | 182ec4e | 2005-11-07 11:16:07 +0000 | [diff] [blame] | 1205 | Tries all compressors and chooses the one which has the smallest |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1206 | result. |
| 1207 | |
| 1208 | endchoice |
| 1209 | |
| 1210 | config CRAMFS |
| 1211 | tristate "Compressed ROM file system support (cramfs)" |
| 1212 | select ZLIB_INFLATE |
| 1213 | help |
| 1214 | Saying Y here includes support for CramFs (Compressed ROM File |
| 1215 | System). CramFs is designed to be a simple, small, and compressed |
| 1216 | file system for ROM based embedded systems. CramFs is read-only, |
| 1217 | limited to 256MB file systems (with 16MB files), and doesn't support |
| 1218 | 16/32 bits uid/gid, hard links and timestamps. |
| 1219 | |
| 1220 | See <file:Documentation/filesystems/cramfs.txt> and |
| 1221 | <file:fs/cramfs/README> for further information. |
| 1222 | |
| 1223 | To compile this as a module, choose M here: the module will be called |
| 1224 | cramfs. Note that the root file system (the one containing the |
| 1225 | directory /) cannot be compiled as a module. |
| 1226 | |
| 1227 | If unsure, say N. |
| 1228 | |
| 1229 | config VXFS_FS |
| 1230 | tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)" |
| 1231 | help |
| 1232 | FreeVxFS is a file system driver that support the VERITAS VxFS(TM) |
| 1233 | file system format. VERITAS VxFS(TM) is the standard file system |
| 1234 | of SCO UnixWare (and possibly others) and optionally available |
| 1235 | for Sunsoft Solaris, HP-UX and many other operating systems. |
| 1236 | Currently only readonly access is supported. |
| 1237 | |
| 1238 | NOTE: the file system type as used by mount(1), mount(2) and |
| 1239 | fstab(5) is 'vxfs' as it describes the file system format, not |
| 1240 | the actual driver. |
| 1241 | |
| 1242 | To compile this as a module, choose M here: the module will be |
| 1243 | called freevxfs. If unsure, say N. |
| 1244 | |
| 1245 | |
| 1246 | config HPFS_FS |
| 1247 | tristate "OS/2 HPFS file system support" |
| 1248 | help |
| 1249 | OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS |
| 1250 | is the file system used for organizing files on OS/2 hard disk |
| 1251 | partitions. Say Y if you want to be able to read files from and |
| 1252 | write files to an OS/2 HPFS partition on your hard drive. OS/2 |
| 1253 | floppies however are in regular MSDOS format, so you don't need this |
| 1254 | option in order to be able to read them. Read |
| 1255 | <file:Documentation/filesystems/hpfs.txt>. |
| 1256 | |
| 1257 | To compile this file system support as a module, choose M here: the |
| 1258 | module will be called hpfs. If unsure, say N. |
| 1259 | |
| 1260 | |
| 1261 | |
| 1262 | config QNX4FS_FS |
| 1263 | tristate "QNX4 file system support (read only)" |
| 1264 | help |
| 1265 | This is the file system used by the real-time operating systems |
| 1266 | QNX 4 and QNX 6 (the latter is also called QNX RTP). |
| 1267 | Further information is available at <http://www.qnx.com/>. |
| 1268 | Say Y if you intend to mount QNX hard disks or floppies. |
| 1269 | Unless you say Y to "QNX4FS read-write support" below, you will |
| 1270 | only be able to read these file systems. |
| 1271 | |
| 1272 | To compile this file system support as a module, choose M here: the |
| 1273 | module will be called qnx4. |
| 1274 | |
| 1275 | If you don't know whether you need it, then you don't need it: |
| 1276 | answer N. |
| 1277 | |
| 1278 | config QNX4FS_RW |
| 1279 | bool "QNX4FS write support (DANGEROUS)" |
| 1280 | depends on QNX4FS_FS && EXPERIMENTAL && BROKEN |
| 1281 | help |
| 1282 | Say Y if you want to test write support for QNX4 file systems. |
| 1283 | |
| 1284 | It's currently broken, so for now: |
| 1285 | answer N. |
| 1286 | |
| 1287 | |
| 1288 | |
| 1289 | config SYSV_FS |
| 1290 | tristate "System V/Xenix/V7/Coherent file system support" |
| 1291 | help |
| 1292 | SCO, Xenix and Coherent are commercial Unix systems for Intel |
| 1293 | machines, and Version 7 was used on the DEC PDP-11. Saying Y |
| 1294 | here would allow you to read from their floppies and hard disk |
| 1295 | partitions. |
| 1296 | |
| 1297 | If you have floppies or hard disk partitions like that, it is likely |
| 1298 | that they contain binaries from those other Unix systems; in order |
| 1299 | to run these binaries, you will want to install linux-abi which is a |
| 1300 | a set of kernel modules that lets you run SCO, Xenix, Wyse, |
| 1301 | UnixWare, Dell Unix and System V programs under Linux. It is |
| 1302 | available via FTP (user: ftp) from |
| 1303 | <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>). |
| 1304 | NOTE: that will work only for binaries from Intel-based systems; |
| 1305 | PDP ones will have to wait until somebody ports Linux to -11 ;-) |
| 1306 | |
| 1307 | If you only intend to mount files from some other Unix over the |
| 1308 | network using NFS, you don't need the System V file system support |
| 1309 | (but you need NFS file system support obviously). |
| 1310 | |
| 1311 | Note that this option is generally not needed for floppies, since a |
| 1312 | good portable way to transport files and directories between unixes |
| 1313 | (and even other operating systems) is given by the tar program ("man |
| 1314 | tar" or preferably "info tar"). Note also that this option has |
| 1315 | nothing whatsoever to do with the option "System V IPC". Read about |
| 1316 | the System V file system in |
| 1317 | <file:Documentation/filesystems/sysv-fs.txt>. |
| 1318 | Saying Y here will enlarge your kernel by about 27 KB. |
| 1319 | |
| 1320 | To compile this as a module, choose M here: the module will be called |
| 1321 | sysv. |
| 1322 | |
| 1323 | If you haven't heard about all of this before, it's safe to say N. |
| 1324 | |
| 1325 | |
| 1326 | |
| 1327 | config UFS_FS |
| 1328 | tristate "UFS file system support (read only)" |
| 1329 | help |
| 1330 | BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD, |
| 1331 | OpenBSD and NeXTstep) use a file system called UFS. Some System V |
| 1332 | Unixes can create and mount hard disk partitions and diskettes using |
| 1333 | this file system as well. Saying Y here will allow you to read from |
| 1334 | these partitions; if you also want to write to them, say Y to the |
| 1335 | experimental "UFS file system write support", below. Please read the |
| 1336 | file <file:Documentation/filesystems/ufs.txt> for more information. |
| 1337 | |
| 1338 | The recently released UFS2 variant (used in FreeBSD 5.x) is |
| 1339 | READ-ONLY supported. |
| 1340 | |
| 1341 | If you only intend to mount files from some other Unix over the |
| 1342 | network using NFS, you don't need the UFS file system support (but |
| 1343 | you need NFS file system support obviously). |
| 1344 | |
| 1345 | Note that this option is generally not needed for floppies, since a |
| 1346 | good portable way to transport files and directories between unixes |
| 1347 | (and even other operating systems) is given by the tar program ("man |
| 1348 | tar" or preferably "info tar"). |
| 1349 | |
| 1350 | When accessing NeXTstep files, you may need to convert them from the |
| 1351 | NeXT character set to the Latin1 character set; use the program |
| 1352 | recode ("info recode") for this purpose. |
| 1353 | |
| 1354 | To compile the UFS file system support as a module, choose M here: the |
| 1355 | module will be called ufs. |
| 1356 | |
| 1357 | If you haven't heard about all of this before, it's safe to say N. |
| 1358 | |
| 1359 | config UFS_FS_WRITE |
| 1360 | bool "UFS file system write support (DANGEROUS)" |
Alexey Dobriyan | 537421b | 2006-02-01 03:05:24 -0800 | [diff] [blame] | 1361 | depends on UFS_FS && EXPERIMENTAL && BROKEN |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1362 | help |
| 1363 | Say Y here if you want to try writing to UFS partitions. This is |
| 1364 | experimental, so you should back up your UFS partitions beforehand. |
| 1365 | |
| 1366 | endmenu |
| 1367 | |
| 1368 | menu "Network File Systems" |
| 1369 | depends on NET |
| 1370 | |
| 1371 | config NFS_FS |
| 1372 | tristate "NFS file system support" |
| 1373 | depends on INET |
| 1374 | select LOCKD |
| 1375 | select SUNRPC |
Andreas Gruenbacher | b7fa055 | 2005-06-22 17:16:27 +0000 | [diff] [blame] | 1376 | select NFS_ACL_SUPPORT if NFS_V3_ACL |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1377 | help |
| 1378 | If you are connected to some other (usually local) Unix computer |
| 1379 | (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing |
| 1380 | on that computer (the NFS server) using the Network File Sharing |
| 1381 | protocol, say Y. "Mounting files" means that the client can access |
| 1382 | the files with usual UNIX commands as if they were sitting on the |
| 1383 | client's hard disk. For this to work, the server must run the |
| 1384 | programs nfsd and mountd (but does not need to have NFS file system |
| 1385 | support enabled in its kernel). NFS is explained in the Network |
| 1386 | Administrator's Guide, available from |
| 1387 | <http://www.tldp.org/docs.html#guide>, on its man page: "man |
| 1388 | nfs", and in the NFS-HOWTO. |
| 1389 | |
| 1390 | A superior but less widely used alternative to NFS is provided by |
| 1391 | the Coda file system; see "Coda file system support" below. |
| 1392 | |
| 1393 | If you say Y here, you should have said Y to TCP/IP networking also. |
| 1394 | This option would enlarge your kernel by about 27 KB. |
| 1395 | |
| 1396 | To compile this file system support as a module, choose M here: the |
| 1397 | module will be called nfs. |
| 1398 | |
| 1399 | If you are configuring a diskless machine which will mount its root |
| 1400 | file system over NFS at boot time, say Y here and to "Kernel |
| 1401 | level IP autoconfiguration" above and to "Root file system on NFS" |
| 1402 | below. You cannot compile this driver as a module in this case. |
| 1403 | There are two packages designed for booting diskless machines over |
| 1404 | the net: netboot, available from |
| 1405 | <http://ftp1.sourceforge.net/netboot/>, and Etherboot, |
| 1406 | available from <http://ftp1.sourceforge.net/etherboot/>. |
| 1407 | |
| 1408 | If you don't know what all this is about, say N. |
| 1409 | |
| 1410 | config NFS_V3 |
| 1411 | bool "Provide NFSv3 client support" |
| 1412 | depends on NFS_FS |
| 1413 | help |
| 1414 | Say Y here if you want your NFS client to be able to speak version |
| 1415 | 3 of the NFS protocol. |
| 1416 | |
| 1417 | If unsure, say Y. |
| 1418 | |
Andreas Gruenbacher | b7fa055 | 2005-06-22 17:16:27 +0000 | [diff] [blame] | 1419 | config NFS_V3_ACL |
| 1420 | bool "Provide client support for the NFSv3 ACL protocol extension" |
| 1421 | depends on NFS_V3 |
| 1422 | help |
| 1423 | Implement the NFSv3 ACL protocol extension for manipulating POSIX |
| 1424 | Access Control Lists. The server should also be compiled with |
| 1425 | the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option. |
| 1426 | |
| 1427 | If unsure, say N. |
| 1428 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1429 | config NFS_V4 |
| 1430 | bool "Provide NFSv4 client support (EXPERIMENTAL)" |
| 1431 | depends on NFS_FS && EXPERIMENTAL |
| 1432 | select RPCSEC_GSS_KRB5 |
| 1433 | help |
| 1434 | Say Y here if you want your NFS client to be able to speak the newer |
| 1435 | version 4 of the NFS protocol. |
| 1436 | |
| 1437 | Note: Requires auxiliary userspace daemons which may be found on |
| 1438 | http://www.citi.umich.edu/projects/nfsv4/ |
| 1439 | |
| 1440 | If unsure, say N. |
| 1441 | |
| 1442 | config NFS_DIRECTIO |
| 1443 | bool "Allow direct I/O on NFS files (EXPERIMENTAL)" |
| 1444 | depends on NFS_FS && EXPERIMENTAL |
| 1445 | help |
| 1446 | This option enables applications to perform uncached I/O on files |
| 1447 | in NFS file systems using the O_DIRECT open() flag. When O_DIRECT |
| 1448 | is set for a file, its data is not cached in the system's page |
| 1449 | cache. Data is moved to and from user-level application buffers |
| 1450 | directly. Unlike local disk-based file systems, NFS O_DIRECT has |
| 1451 | no alignment restrictions. |
| 1452 | |
| 1453 | Unless your program is designed to use O_DIRECT properly, you are |
| 1454 | much better off allowing the NFS client to manage data caching for |
| 1455 | you. Misusing O_DIRECT can cause poor server performance or network |
| 1456 | storms. This kernel build option defaults OFF to avoid exposing |
| 1457 | system administrators unwittingly to a potentially hazardous |
| 1458 | feature. |
| 1459 | |
| 1460 | For more details on NFS O_DIRECT, see fs/nfs/direct.c. |
| 1461 | |
| 1462 | If unsure, say N. This reduces the size of the NFS client, and |
| 1463 | causes open() to return EINVAL if a file residing in NFS is |
| 1464 | opened with the O_DIRECT flag. |
| 1465 | |
| 1466 | config NFSD |
| 1467 | tristate "NFS server support" |
| 1468 | depends on INET |
| 1469 | select LOCKD |
| 1470 | select SUNRPC |
| 1471 | select EXPORTFS |
Andreas Gruenbacher | a257cdd | 2005-06-22 17:16:26 +0000 | [diff] [blame] | 1472 | select NFS_ACL_SUPPORT if NFSD_V3_ACL || NFSD_V2_ACL |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1473 | help |
| 1474 | If you want your Linux box to act as an NFS *server*, so that other |
| 1475 | computers on your local network which support NFS can access certain |
| 1476 | directories on your box transparently, you have two options: you can |
| 1477 | use the self-contained user space program nfsd, in which case you |
| 1478 | should say N here, or you can say Y and use the kernel based NFS |
| 1479 | server. The advantage of the kernel based solution is that it is |
| 1480 | faster. |
| 1481 | |
| 1482 | In either case, you will need support software; the respective |
| 1483 | locations are given in the file <file:Documentation/Changes> in the |
| 1484 | NFS section. |
| 1485 | |
| 1486 | If you say Y here, you will get support for version 2 of the NFS |
| 1487 | protocol (NFSv2). If you also want NFSv3, say Y to the next question |
| 1488 | as well. |
| 1489 | |
| 1490 | Please read the NFS-HOWTO, available from |
| 1491 | <http://www.tldp.org/docs.html#howto>. |
| 1492 | |
| 1493 | To compile the NFS server support as a module, choose M here: the |
| 1494 | module will be called nfsd. If unsure, say N. |
| 1495 | |
Andreas Gruenbacher | a257cdd | 2005-06-22 17:16:26 +0000 | [diff] [blame] | 1496 | config NFSD_V2_ACL |
| 1497 | bool |
| 1498 | depends on NFSD |
| 1499 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1500 | config NFSD_V3 |
| 1501 | bool "Provide NFSv3 server support" |
| 1502 | depends on NFSD |
| 1503 | help |
| 1504 | If you would like to include the NFSv3 server as well as the NFSv2 |
| 1505 | server, say Y here. If unsure, say Y. |
| 1506 | |
Andreas Gruenbacher | a257cdd | 2005-06-22 17:16:26 +0000 | [diff] [blame] | 1507 | config NFSD_V3_ACL |
| 1508 | bool "Provide server support for the NFSv3 ACL protocol extension" |
| 1509 | depends on NFSD_V3 |
| 1510 | select NFSD_V2_ACL |
| 1511 | help |
| 1512 | Implement the NFSv3 ACL protocol extension for manipulating POSIX |
| 1513 | Access Control Lists on exported file systems. NFS clients should |
| 1514 | be compiled with the NFSv3 ACL protocol extension; see the |
| 1515 | CONFIG_NFS_V3_ACL option. If unsure, say N. |
| 1516 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1517 | config NFSD_V4 |
| 1518 | bool "Provide NFSv4 server support (EXPERIMENTAL)" |
| 1519 | depends on NFSD_V3 && EXPERIMENTAL |
| 1520 | select NFSD_TCP |
NeilBrown | a55370a | 2005-06-23 22:03:52 -0700 | [diff] [blame] | 1521 | select CRYPTO_MD5 |
| 1522 | select CRYPTO |
Andreas Gruenbacher | b84c215 | 2005-07-07 17:56:57 -0700 | [diff] [blame] | 1523 | select FS_POSIX_ACL |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1524 | help |
| 1525 | If you would like to include the NFSv4 server as well as the NFSv2 |
| 1526 | and NFSv3 servers, say Y here. This feature is experimental, and |
| 1527 | should only be used if you are interested in helping to test NFSv4. |
| 1528 | If unsure, say N. |
| 1529 | |
| 1530 | config NFSD_TCP |
| 1531 | bool "Provide NFS server over TCP support" |
| 1532 | depends on NFSD |
| 1533 | default y |
| 1534 | help |
| 1535 | If you want your NFS server to support TCP connections, say Y here. |
| 1536 | TCP connections usually perform better than the default UDP when |
| 1537 | the network is lossy or congested. If unsure, say Y. |
| 1538 | |
| 1539 | config ROOT_NFS |
| 1540 | bool "Root file system on NFS" |
| 1541 | depends on NFS_FS=y && IP_PNP |
| 1542 | help |
| 1543 | If you want your Linux box to mount its whole root file system (the |
| 1544 | one containing the directory /) from some other computer over the |
| 1545 | net via NFS (presumably because your box doesn't have a hard disk), |
| 1546 | say Y. Read <file:Documentation/nfsroot.txt> for details. It is |
| 1547 | likely that in this case, you also want to say Y to "Kernel level IP |
| 1548 | autoconfiguration" so that your box can discover its network address |
| 1549 | at boot time. |
| 1550 | |
| 1551 | Most people say N here. |
| 1552 | |
| 1553 | config LOCKD |
| 1554 | tristate |
| 1555 | |
| 1556 | config LOCKD_V4 |
| 1557 | bool |
| 1558 | depends on NFSD_V3 || NFS_V3 |
| 1559 | default y |
| 1560 | |
| 1561 | config EXPORTFS |
| 1562 | tristate |
| 1563 | |
Andreas Gruenbacher | a257cdd | 2005-06-22 17:16:26 +0000 | [diff] [blame] | 1564 | config NFS_ACL_SUPPORT |
| 1565 | tristate |
| 1566 | select FS_POSIX_ACL |
| 1567 | |
| 1568 | config NFS_COMMON |
| 1569 | bool |
| 1570 | depends on NFSD || NFS_FS |
| 1571 | default y |
| 1572 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1573 | config SUNRPC |
| 1574 | tristate |
| 1575 | |
| 1576 | config SUNRPC_GSS |
| 1577 | tristate |
| 1578 | |
| 1579 | config RPCSEC_GSS_KRB5 |
| 1580 | tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)" |
| 1581 | depends on SUNRPC && EXPERIMENTAL |
| 1582 | select SUNRPC_GSS |
| 1583 | select CRYPTO |
| 1584 | select CRYPTO_MD5 |
| 1585 | select CRYPTO_DES |
| 1586 | help |
| 1587 | Provides for secure RPC calls by means of a gss-api |
| 1588 | mechanism based on Kerberos V5. This is required for |
| 1589 | NFSv4. |
| 1590 | |
| 1591 | Note: Requires an auxiliary userspace daemon which may be found on |
| 1592 | http://www.citi.umich.edu/projects/nfsv4/ |
| 1593 | |
| 1594 | If unsure, say N. |
| 1595 | |
| 1596 | config RPCSEC_GSS_SPKM3 |
| 1597 | tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)" |
| 1598 | depends on SUNRPC && EXPERIMENTAL |
| 1599 | select SUNRPC_GSS |
| 1600 | select CRYPTO |
| 1601 | select CRYPTO_MD5 |
| 1602 | select CRYPTO_DES |
J. Bruce Fields | df6db30 | 2006-03-20 23:25:10 -0500 | [diff] [blame] | 1603 | select CRYPTO_CAST5 |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1604 | help |
| 1605 | Provides for secure RPC calls by means of a gss-api |
| 1606 | mechanism based on the SPKM3 public-key mechanism. |
| 1607 | |
| 1608 | Note: Requires an auxiliary userspace daemon which may be found on |
| 1609 | http://www.citi.umich.edu/projects/nfsv4/ |
| 1610 | |
| 1611 | If unsure, say N. |
| 1612 | |
| 1613 | config SMB_FS |
| 1614 | tristate "SMB file system support (to mount Windows shares etc.)" |
| 1615 | depends on INET |
| 1616 | select NLS |
| 1617 | help |
| 1618 | SMB (Server Message Block) is the protocol Windows for Workgroups |
| 1619 | (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share |
| 1620 | files and printers over local networks. Saying Y here allows you to |
| 1621 | mount their file systems (often called "shares" in this context) and |
| 1622 | access them just like any other Unix directory. Currently, this |
| 1623 | works only if the Windows machines use TCP/IP as the underlying |
| 1624 | transport protocol, and not NetBEUI. For details, read |
| 1625 | <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO, |
| 1626 | available from <http://www.tldp.org/docs.html#howto>. |
| 1627 | |
| 1628 | Note: if you just want your box to act as an SMB *server* and make |
| 1629 | files and printing services available to Windows clients (which need |
| 1630 | to have a TCP/IP stack), you don't need to say Y here; you can use |
| 1631 | the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>) |
| 1632 | for that. |
| 1633 | |
| 1634 | General information about how to connect Linux, Windows machines and |
| 1635 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. |
| 1636 | |
| 1637 | To compile the SMB support as a module, choose M here: the module will |
| 1638 | be called smbfs. Most people say N, however. |
| 1639 | |
| 1640 | config SMB_NLS_DEFAULT |
| 1641 | bool "Use a default NLS" |
| 1642 | depends on SMB_FS |
| 1643 | help |
| 1644 | Enabling this will make smbfs use nls translations by default. You |
| 1645 | need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls |
| 1646 | settings and you need to give the default nls for the SMB server as |
| 1647 | CONFIG_SMB_NLS_REMOTE. |
| 1648 | |
| 1649 | The nls settings can be changed at mount time, if your smbmount |
| 1650 | supports that, using the codepage and iocharset parameters. |
| 1651 | |
| 1652 | smbmount from samba 2.2.0 or later supports this. |
| 1653 | |
| 1654 | config SMB_NLS_REMOTE |
| 1655 | string "Default Remote NLS Option" |
| 1656 | depends on SMB_NLS_DEFAULT |
| 1657 | default "cp437" |
| 1658 | help |
| 1659 | This setting allows you to specify a default value for which |
| 1660 | codepage the server uses. If this field is left blank no |
| 1661 | translations will be done by default. The local codepage/charset |
| 1662 | default to CONFIG_NLS_DEFAULT. |
| 1663 | |
| 1664 | The nls settings can be changed at mount time, if your smbmount |
| 1665 | supports that, using the codepage and iocharset parameters. |
| 1666 | |
| 1667 | smbmount from samba 2.2.0 or later supports this. |
| 1668 | |
| 1669 | config CIFS |
| 1670 | tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)" |
| 1671 | depends on INET |
| 1672 | select NLS |
| 1673 | help |
| 1674 | This is the client VFS module for the Common Internet File System |
| 1675 | (CIFS) protocol which is the successor to the Server Message Block |
| 1676 | (SMB) protocol, the native file sharing mechanism for most early |
| 1677 | PC operating systems. The CIFS protocol is fully supported by |
| 1678 | file servers such as Windows 2000 (including Windows 2003, NT 4 |
| 1679 | and Windows XP) as well by Samba (which provides excellent CIFS |
Steve French | ec58ef0 | 2005-11-04 09:44:33 -0800 | [diff] [blame] | 1680 | server support for Linux and many other operating systems). Limited |
| 1681 | support for Windows ME and similar servers is provided as well. |
| 1682 | You must use the smbfs client filesystem to access older SMB servers |
| 1683 | such as OS/2 and DOS. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1684 | |
| 1685 | The intent of the cifs module is to provide an advanced |
| 1686 | network file system client for mounting to CIFS compliant servers, |
| 1687 | including support for dfs (hierarchical name space), secure per-user |
| 1688 | session establishment, safe distributed caching (oplock), optional |
| 1689 | packet signing, Unicode and other internationalization improvements, |
| 1690 | and optional Winbind (nsswitch) integration. You do not need to enable |
| 1691 | cifs if running only a (Samba) server. It is possible to enable both |
| 1692 | smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003 |
| 1693 | and Samba 3 servers, and smbfs for accessing old servers). If you need |
Steve French | ec58ef0 | 2005-11-04 09:44:33 -0800 | [diff] [blame] | 1694 | to mount to Samba or Windows from this machine, say Y. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1695 | |
| 1696 | config CIFS_STATS |
| 1697 | bool "CIFS statistics" |
| 1698 | depends on CIFS |
| 1699 | help |
| 1700 | Enabling this option will cause statistics for each server share |
| 1701 | mounted by the cifs client to be displayed in /proc/fs/cifs/Stats |
| 1702 | |
Steve French | ec58ef0 | 2005-11-04 09:44:33 -0800 | [diff] [blame] | 1703 | config CIFS_STATS2 |
| 1704 | bool "CIFS extended statistics" |
| 1705 | depends on CIFS_STATS |
| 1706 | help |
| 1707 | Enabling this option will allow more detailed statistics on SMB |
| 1708 | request timing to be displayed in /proc/fs/cifs/DebugData and also |
| 1709 | allow optional logging of slow responses to dmesg (depending on the |
| 1710 | value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details). |
| 1711 | These additional statistics may have a minor effect on performance |
| 1712 | and memory utilization. |
| 1713 | |
| 1714 | Unless you are a developer or are doing network performance analysis |
| 1715 | or tuning, say N. |
| 1716 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1717 | config CIFS_XATTR |
Steve French | ec58ef0 | 2005-11-04 09:44:33 -0800 | [diff] [blame] | 1718 | bool "CIFS extended attributes" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1719 | depends on CIFS |
| 1720 | help |
| 1721 | Extended attributes are name:value pairs associated with inodes by |
| 1722 | the kernel or by users (see the attr(5) manual page, or visit |
| 1723 | <http://acl.bestbits.at/> for details). CIFS maps the name of |
| 1724 | extended attributes beginning with the user namespace prefix |
| 1725 | to SMB/CIFS EAs. EAs are stored on Windows servers without the |
| 1726 | user namespace prefix, but their names are seen by Linux cifs clients |
| 1727 | prefaced by the user namespace prefix. The system namespace |
| 1728 | (used by some filesystems to store ACLs) is not supported at |
| 1729 | this time. |
Steve French | ec58ef0 | 2005-11-04 09:44:33 -0800 | [diff] [blame] | 1730 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1731 | If unsure, say N. |
| 1732 | |
| 1733 | config CIFS_POSIX |
Steve French | ec58ef0 | 2005-11-04 09:44:33 -0800 | [diff] [blame] | 1734 | bool "CIFS POSIX Extensions" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1735 | depends on CIFS_XATTR |
| 1736 | help |
| 1737 | Enabling this option will cause the cifs client to attempt to |
| 1738 | negotiate a newer dialect with servers, such as Samba 3.0.5 |
| 1739 | or later, that optionally can handle more POSIX like (rather |
| 1740 | than Windows like) file behavior. It also enables |
| 1741 | support for POSIX ACLs (getfacl and setfacl) to servers |
| 1742 | (such as Samba 3.10 and later) which can negotiate |
| 1743 | CIFS POSIX ACL support. If unsure, say N. |
| 1744 | |
| 1745 | config CIFS_EXPERIMENTAL |
| 1746 | bool "CIFS Experimental Features (EXPERIMENTAL)" |
Steve French | cb9dbff | 2005-11-02 11:37:15 -0800 | [diff] [blame] | 1747 | depends on CIFS && EXPERIMENTAL |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1748 | help |
Steve French | ec58ef0 | 2005-11-04 09:44:33 -0800 | [diff] [blame] | 1749 | Enables cifs features under testing. These features are |
| 1750 | experimental and currently include support for writepages |
| 1751 | (multipage writebehind performance improvements) and directory |
| 1752 | change notification ie fcntl(F_DNOTIFY) as well as some security |
| 1753 | improvements. Some also depend on setting at runtime the |
| 1754 | pseudo-file /proc/fs/cifs/Experimental (which is disabled by |
| 1755 | default). See the file fs/cifs/README for more details. |
| 1756 | |
| 1757 | If unsure, say N. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1758 | |
Steve French | a2653eb | 2005-11-10 15:33:38 -0800 | [diff] [blame] | 1759 | config CIFS_UPCALL |
| 1760 | bool "CIFS Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)" |
| 1761 | depends on CIFS_EXPERIMENTAL |
| 1762 | select CONNECTOR |
| 1763 | help |
| 1764 | Enables an upcall mechanism for CIFS which will be used to contact |
| 1765 | userspace helper utilities to provide SPNEGO packaged Kerberos |
| 1766 | tickets which are needed to mount to certain secure servers |
Steve French | 1b397f4 | 2005-11-10 19:36:39 -0800 | [diff] [blame] | 1767 | (for which more secure Kerberos authentication is required). If |
| 1768 | unsure, say N. |
Steve French | a2653eb | 2005-11-10 15:33:38 -0800 | [diff] [blame] | 1769 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1770 | config NCP_FS |
| 1771 | tristate "NCP file system support (to mount NetWare volumes)" |
| 1772 | depends on IPX!=n || INET |
| 1773 | help |
| 1774 | NCP (NetWare Core Protocol) is a protocol that runs over IPX and is |
| 1775 | used by Novell NetWare clients to talk to file servers. It is to |
| 1776 | IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you |
| 1777 | to mount NetWare file server volumes and to access them just like |
| 1778 | any other Unix directory. For details, please read the file |
| 1779 | <file:Documentation/filesystems/ncpfs.txt> in the kernel source and |
| 1780 | the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>. |
| 1781 | |
| 1782 | You do not have to say Y here if you want your Linux box to act as a |
| 1783 | file *server* for Novell NetWare clients. |
| 1784 | |
| 1785 | General information about how to connect Linux, Windows machines and |
| 1786 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. |
| 1787 | |
| 1788 | To compile this as a module, choose M here: the module will be called |
| 1789 | ncpfs. Say N unless you are connected to a Novell network. |
| 1790 | |
| 1791 | source "fs/ncpfs/Kconfig" |
| 1792 | |
| 1793 | config CODA_FS |
| 1794 | tristate "Coda file system support (advanced network fs)" |
| 1795 | depends on INET |
| 1796 | help |
| 1797 | Coda is an advanced network file system, similar to NFS in that it |
| 1798 | enables you to mount file systems of a remote server and access them |
| 1799 | with regular Unix commands as if they were sitting on your hard |
| 1800 | disk. Coda has several advantages over NFS: support for |
| 1801 | disconnected operation (e.g. for laptops), read/write server |
| 1802 | replication, security model for authentication and encryption, |
| 1803 | persistent client caches and write back caching. |
| 1804 | |
| 1805 | If you say Y here, your Linux box will be able to act as a Coda |
| 1806 | *client*. You will need user level code as well, both for the |
| 1807 | client and server. Servers are currently user level, i.e. they need |
| 1808 | no kernel support. Please read |
| 1809 | <file:Documentation/filesystems/coda.txt> and check out the Coda |
| 1810 | home page <http://www.coda.cs.cmu.edu/>. |
| 1811 | |
| 1812 | To compile the coda client support as a module, choose M here: the |
| 1813 | module will be called coda. |
| 1814 | |
| 1815 | config CODA_FS_OLD_API |
| 1816 | bool "Use 96-bit Coda file identifiers" |
| 1817 | depends on CODA_FS |
| 1818 | help |
| 1819 | A new kernel-userspace API had to be introduced for Coda v6.0 |
| 1820 | to support larger 128-bit file identifiers as needed by the |
| 1821 | new realms implementation. |
| 1822 | |
| 1823 | However this new API is not backward compatible with older |
| 1824 | clients. If you really need to run the old Coda userspace |
| 1825 | cache manager then say Y. |
| 1826 | |
| 1827 | For most cases you probably want to say N. |
| 1828 | |
| 1829 | config AFS_FS |
| 1830 | # for fs/nls/Config.in |
| 1831 | tristate "Andrew File System support (AFS) (Experimental)" |
| 1832 | depends on INET && EXPERIMENTAL |
| 1833 | select RXRPC |
| 1834 | help |
| 1835 | If you say Y here, you will get an experimental Andrew File System |
| 1836 | driver. It currently only supports unsecured read-only AFS access. |
| 1837 | |
| 1838 | See <file:Documentation/filesystems/afs.txt> for more intormation. |
| 1839 | |
| 1840 | If unsure, say N. |
| 1841 | |
| 1842 | config RXRPC |
| 1843 | tristate |
| 1844 | |
Eric Van Hensbergen | 93fa58c | 2005-09-09 13:04:18 -0700 | [diff] [blame] | 1845 | config 9P_FS |
| 1846 | tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)" |
| 1847 | depends on INET && EXPERIMENTAL |
| 1848 | help |
| 1849 | If you say Y here, you will get experimental support for |
| 1850 | Plan 9 resource sharing via the 9P2000 protocol. |
| 1851 | |
| 1852 | See <http://v9fs.sf.net> for more information. |
| 1853 | |
| 1854 | If unsure, say N. |
| 1855 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1856 | endmenu |
| 1857 | |
| 1858 | menu "Partition Types" |
| 1859 | |
| 1860 | source "fs/partitions/Kconfig" |
| 1861 | |
| 1862 | endmenu |
| 1863 | |
| 1864 | source "fs/nls/Kconfig" |
| 1865 | |
| 1866 | endmenu |
| 1867 | |