]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # File system configuration | |
3 | # | |
4 | ||
5 | menu "File systems" | |
6 | ||
9361401e DH |
7 | if BLOCK |
8 | ||
1da177e4 LT |
9 | config EXT2_FS |
10 | tristate "Second extended fs support" | |
11 | help | |
12 | Ext2 is a standard Linux file system for hard disks. | |
13 | ||
14 | To compile this file system support as a module, choose M here: the | |
d23edbd3 | 15 | module will be called ext2. |
1da177e4 LT |
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 | |
b84c2157 | 32 | select FS_POSIX_ACL |
1da177e4 LT |
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 | ||
6d79125b CO |
54 | config EXT2_FS_XIP |
55 | bool "Ext2 execute in place support" | |
0c426f26 | 56 | depends on EXT2_FS && MMU |
6d79125b CO |
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 | ||
1da177e4 LT |
71 | config EXT3_FS |
72 | tristate "Ext3 journalling file system support" | |
b4e40a51 | 73 | select JBD |
1da177e4 | 74 | help |
cc2e2767 | 75 | This is the journalling version of the Second extended file system |
1da177e4 LT |
76 | (often called ext3), the de facto standard Linux file system |
77 | (method to organize files on a storage device) for hard disks. | |
78 | ||
cc2e2767 | 79 | The journalling code included in this driver means you do not have |
1da177e4 LT |
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 | |
d23edbd3 | 99 | module will be called ext3. |
1da177e4 LT |
100 | |
101 | config EXT3_FS_XATTR | |
102 | bool "Ext3 extended attributes" | |
103 | depends on EXT3_FS | |
104 | default y | |
105 | help | |
106 | Extended attributes are name:value pairs associated with inodes by | |
107 | the kernel or by users (see the attr(5) manual page, or visit | |
108 | <http://acl.bestbits.at/> for details). | |
109 | ||
110 | If unsure, say N. | |
111 | ||
112 | You need this for POSIX ACL support on ext3. | |
113 | ||
114 | config EXT3_FS_POSIX_ACL | |
115 | bool "Ext3 POSIX Access Control Lists" | |
116 | depends on EXT3_FS_XATTR | |
b84c2157 | 117 | select FS_POSIX_ACL |
1da177e4 LT |
118 | help |
119 | Posix Access Control Lists (ACLs) support permissions for users and | |
120 | groups beyond the owner/group/world scheme. | |
121 | ||
122 | To learn more about Access Control Lists, visit the Posix ACLs for | |
123 | Linux website <http://acl.bestbits.at/>. | |
124 | ||
125 | If you don't know what Access Control Lists are, say N | |
126 | ||
127 | config EXT3_FS_SECURITY | |
128 | bool "Ext3 Security Labels" | |
129 | depends on EXT3_FS_XATTR | |
130 | help | |
131 | Security labels support alternative access control models | |
132 | implemented by security modules like SELinux. This option | |
133 | enables an extended attribute handler for file security | |
134 | labels in the ext3 filesystem. | |
135 | ||
136 | If you are not using a security module that requires using | |
137 | extended attributes for file security labels, say N. | |
138 | ||
03010a33 TT |
139 | config EXT4_FS |
140 | tristate "The Extended 4 (ext4) filesystem" | |
dab291af | 141 | select JBD2 |
717d50e4 | 142 | select CRC16 |
dab291af | 143 | help |
03010a33 | 144 | This is the next generation of the ext3 filesystem. |
02ea2104 | 145 | |
dab291af | 146 | Unlike the change from ext2 filesystem to ext3 filesystem, |
03010a33 TT |
147 | the on-disk format of ext4 is not forwards compatible with |
148 | ext3; it is based on extent maps and it supports 48-bit | |
149 | physical block numbers. The ext4 filesystem also supports delayed | |
150 | allocation, persistent preallocation, high resolution time stamps, | |
151 | and a number of other features to improve performance and speed | |
152 | up fsck time. For more information, please see the web pages at | |
153 | http://ext4.wiki.kernel.org. | |
154 | ||
155 | The ext4 filesystem will support mounting an ext3 | |
156 | filesystem; while there will be some performance gains from | |
157 | the delayed allocation and inode table readahead, the best | |
158 | performance gains will require enabling ext4 features in the | |
159 | filesystem, or formating a new filesystem as an ext4 | |
160 | filesystem initially. | |
02ea2104 MC |
161 | |
162 | To compile this file system support as a module, choose M here. The | |
473dc8ed | 163 | module will be called ext4. |
02ea2104 MC |
164 | |
165 | If unsure, say N. | |
166 | ||
03010a33 TT |
167 | config EXT4DEV_COMPAT |
168 | bool "Enable ext4dev compatibility" | |
169 | depends on EXT4_FS | |
170 | help | |
171 | Starting with 2.6.28, the name of the ext4 filesystem was | |
172 | renamed from ext4dev to ext4. Unfortunately there are some | |
f319fb8b JE |
173 | legacy userspace programs (such as klibc's fstype) have |
174 | "ext4dev" hardcoded. | |
03010a33 TT |
175 | |
176 | To enable backwards compatibility so that systems that are | |
177 | still expecting to mount ext4 filesystems using ext4dev, | |
178 | chose Y here. This feature will go away by 2.6.31, so | |
179 | please arrange to get your userspace programs fixed! | |
180 | ||
181 | config EXT4_FS_XATTR | |
182 | bool "Ext4 extended attributes" | |
183 | depends on EXT4_FS | |
02ea2104 MC |
184 | default y |
185 | help | |
186 | Extended attributes are name:value pairs associated with inodes by | |
187 | the kernel or by users (see the attr(5) manual page, or visit | |
188 | <http://acl.bestbits.at/> for details). | |
189 | ||
190 | If unsure, say N. | |
191 | ||
03010a33 | 192 | You need this for POSIX ACL support on ext4. |
02ea2104 | 193 | |
03010a33 TT |
194 | config EXT4_FS_POSIX_ACL |
195 | bool "Ext4 POSIX Access Control Lists" | |
196 | depends on EXT4_FS_XATTR | |
02ea2104 MC |
197 | select FS_POSIX_ACL |
198 | help | |
199 | POSIX Access Control Lists (ACLs) support permissions for users and | |
200 | groups beyond the owner/group/world scheme. | |
201 | ||
202 | To learn more about Access Control Lists, visit the POSIX ACLs for | |
203 | Linux website <http://acl.bestbits.at/>. | |
204 | ||
205 | If you don't know what Access Control Lists are, say N | |
206 | ||
03010a33 TT |
207 | config EXT4_FS_SECURITY |
208 | bool "Ext4 Security Labels" | |
209 | depends on EXT4_FS_XATTR | |
02ea2104 MC |
210 | help |
211 | Security labels support alternative access control models | |
212 | implemented by security modules like SELinux. This option | |
213 | enables an extended attribute handler for file security | |
03010a33 | 214 | labels in the ext4 filesystem. |
02ea2104 MC |
215 | |
216 | If you are not using a security module that requires using | |
217 | extended attributes for file security labels, say N. | |
218 | ||
1da177e4 | 219 | config JBD |
1da177e4 | 220 | tristate |
1da177e4 | 221 | help |
cc2e2767 | 222 | This is a generic journalling layer for block devices. It is |
2b4e30fb JB |
223 | currently used by the ext3 file system, but it could also be |
224 | used to add journal support to other file systems or block | |
b4e40a51 | 225 | devices such as RAID or LVM. |
1da177e4 | 226 | |
2b4e30fb JB |
227 | If you are using the ext3 file system, you need to say Y here. |
228 | If you are not using ext3 then you will probably want to say N. | |
1da177e4 LT |
229 | |
230 | To compile this device as a module, choose M here: the module will be | |
2b4e30fb JB |
231 | called jbd. If you are compiling ext3 into the kernel, you |
232 | cannot compile this code as a module. | |
1da177e4 LT |
233 | |
234 | config JBD_DEBUG | |
235 | bool "JBD (ext3) debugging support" | |
c2a9159c | 236 | depends on JBD && DEBUG_FS |
1da177e4 LT |
237 | help |
238 | If you are using the ext3 journaled file system (or potentially any | |
239 | other file system/device using JBD), this option allows you to | |
240 | enable debugging output while the system is running, in order to | |
241 | help track down any problems you are having. By default the | |
242 | debugging output will be turned off. | |
243 | ||
244 | If you select Y here, then you will be able to turn on debugging | |
c2a9159c JS |
245 | with "echo N > /sys/kernel/debug/jbd/jbd-debug", where N is a |
246 | number between 1 and 5, the higher the number, the more debugging | |
247 | output is generated. To turn debugging off again, do | |
248 | "echo 0 > /sys/kernel/debug/jbd/jbd-debug". | |
1da177e4 | 249 | |
dab291af MC |
250 | config JBD2 |
251 | tristate | |
818d276c | 252 | select CRC32 |
dab291af MC |
253 | help |
254 | This is a generic journaling layer for block devices that support | |
255 | both 32-bit and 64-bit block numbers. It is currently used by | |
2b4e30fb | 256 | the ext4 and OCFS2 filesystems, but it could also be used to add |
dab291af MC |
257 | journal support to other file systems or block devices such |
258 | as RAID or LVM. | |
259 | ||
2b4e30fb JB |
260 | If you are using ext4 or OCFS2, you need to say Y here. |
261 | If you are not using ext4 or OCFS2 then you will | |
262 | probably want to say N. | |
dab291af MC |
263 | |
264 | To compile this device as a module, choose M here. The module will be | |
2b4e30fb | 265 | called jbd2. If you are compiling ext4 or OCFS2 into the kernel, |
dab291af MC |
266 | you cannot compile this code as a module. |
267 | ||
268 | config JBD2_DEBUG | |
03010a33 | 269 | bool "JBD2 (ext4) debugging support" |
0f49d5d0 | 270 | depends on JBD2 && DEBUG_FS |
dab291af | 271 | help |
03010a33 | 272 | If you are using the ext4 journaled file system (or |
dab291af MC |
273 | potentially any other filesystem/device using JBD2), this option |
274 | allows you to enable debugging output while the system is running, | |
275 | in order to help track down any problems you are having. | |
276 | By default, the debugging output will be turned off. | |
277 | ||
278 | If you select Y here, then you will be able to turn on debugging | |
0f49d5d0 JS |
279 | with "echo N > /sys/kernel/debug/jbd2/jbd2-debug", where N is a |
280 | number between 1 and 5. The higher the number, the more debugging | |
281 | output is generated. To turn debugging off again, do | |
282 | "echo 0 > /sys/kernel/debug/jbd2/jbd2-debug". | |
dab291af | 283 | |
1da177e4 | 284 | config FS_MBCACHE |
02ea2104 | 285 | # Meta block cache for Extended Attributes (ext2/ext3/ext4) |
1da177e4 | 286 | tristate |
03010a33 TT |
287 | depends on EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR |
288 | default y if EXT2_FS=y || EXT3_FS=y || EXT4_FS=y | |
289 | default m if EXT2_FS=m || EXT3_FS=m || EXT4_FS=m | |
1da177e4 LT |
290 | |
291 | config REISERFS_FS | |
292 | tristate "Reiserfs support" | |
293 | help | |
294 | Stores not just filenames but the files themselves in a balanced | |
cc2e2767 | 295 | tree. Uses journalling. |
1da177e4 LT |
296 | |
297 | Balanced trees are more efficient than traditional file system | |
298 | architectural foundations. | |
299 | ||
300 | In general, ReiserFS is as fast as ext2, but is very efficient with | |
301 | large directories and small files. Additional patches are needed | |
302 | for NFS and quotas, please see <http://www.namesys.com/> for links. | |
303 | ||
304 | It is more easily extended to have features currently found in | |
305 | database and keyword search systems than block allocation based file | |
306 | systems are. The next version will be so extended, and will support | |
307 | plugins consistent with our motto ``It takes more than a license to | |
308 | make source code open.'' | |
309 | ||
310 | Read <http://www.namesys.com/> to learn more about reiserfs. | |
311 | ||
312 | Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com. | |
313 | ||
314 | If you like it, you can pay us to add new features to it that you | |
315 | need, buy a support contract, or pay us to port it to another OS. | |
316 | ||
317 | config REISERFS_CHECK | |
318 | bool "Enable reiserfs debug mode" | |
319 | depends on REISERFS_FS | |
320 | help | |
321 | If you set this to Y, then ReiserFS will perform every check it can | |
322 | possibly imagine of its internal consistency throughout its | |
323 | operation. It will also go substantially slower. More than once we | |
324 | have forgotten that this was on, and then gone despondent over the | |
325 | latest benchmarks.:-) Use of this option allows our team to go all | |
326 | out in checking for consistency when debugging without fear of its | |
327 | effect on end users. If you are on the verge of sending in a bug | |
328 | report, say Y and you might get a useful error message. Almost | |
329 | everyone should say N. | |
330 | ||
331 | config REISERFS_PROC_INFO | |
332 | bool "Stats in /proc/fs/reiserfs" | |
880ebdc5 | 333 | depends on REISERFS_FS && PROC_FS |
1da177e4 LT |
334 | help |
335 | Create under /proc/fs/reiserfs a hierarchy of files, displaying | |
336 | various ReiserFS statistics and internal data at the expense of | |
337 | making your kernel or module slightly larger (+8 KB). This also | |
338 | increases the amount of kernel memory required for each mount. | |
339 | Almost everyone but ReiserFS developers and people fine-tuning | |
340 | reiserfs or tracing problems should say N. | |
341 | ||
342 | config REISERFS_FS_XATTR | |
343 | bool "ReiserFS extended attributes" | |
344 | depends on REISERFS_FS | |
345 | help | |
346 | Extended attributes are name:value pairs associated with inodes by | |
347 | the kernel or by users (see the attr(5) manual page, or visit | |
348 | <http://acl.bestbits.at/> for details). | |
349 | ||
350 | If unsure, say N. | |
351 | ||
352 | config REISERFS_FS_POSIX_ACL | |
353 | bool "ReiserFS POSIX Access Control Lists" | |
354 | depends on REISERFS_FS_XATTR | |
b84c2157 | 355 | select FS_POSIX_ACL |
1da177e4 LT |
356 | help |
357 | Posix Access Control Lists (ACLs) support permissions for users and | |
358 | groups beyond the owner/group/world scheme. | |
359 | ||
360 | To learn more about Access Control Lists, visit the Posix ACLs for | |
361 | Linux website <http://acl.bestbits.at/>. | |
362 | ||
363 | If you don't know what Access Control Lists are, say N | |
364 | ||
365 | config REISERFS_FS_SECURITY | |
366 | bool "ReiserFS Security Labels" | |
367 | depends on REISERFS_FS_XATTR | |
368 | help | |
369 | Security labels support alternative access control models | |
370 | implemented by security modules like SELinux. This option | |
371 | enables an extended attribute handler for file security | |
372 | labels in the ReiserFS filesystem. | |
373 | ||
374 | If you are not using a security module that requires using | |
375 | extended attributes for file security labels, say N. | |
376 | ||
377 | config JFS_FS | |
378 | tristate "JFS filesystem support" | |
379 | select NLS | |
380 | help | |
381 | This is a port of IBM's Journaled Filesystem . More information is | |
382 | available in the file <file:Documentation/filesystems/jfs.txt>. | |
383 | ||
384 | If you do not intend to use the JFS filesystem, say N. | |
385 | ||
386 | config JFS_POSIX_ACL | |
387 | bool "JFS POSIX Access Control Lists" | |
388 | depends on JFS_FS | |
b84c2157 | 389 | select FS_POSIX_ACL |
1da177e4 LT |
390 | help |
391 | Posix Access Control Lists (ACLs) support permissions for users and | |
392 | groups beyond the owner/group/world scheme. | |
393 | ||
394 | To learn more about Access Control Lists, visit the Posix ACLs for | |
395 | Linux website <http://acl.bestbits.at/>. | |
396 | ||
397 | If you don't know what Access Control Lists are, say N | |
398 | ||
399 | config JFS_SECURITY | |
400 | bool "JFS Security Labels" | |
401 | depends on JFS_FS | |
402 | help | |
403 | Security labels support alternative access control models | |
404 | implemented by security modules like SELinux. This option | |
405 | enables an extended attribute handler for file security | |
406 | labels in the jfs filesystem. | |
407 | ||
408 | If you are not using a security module that requires using | |
409 | extended attributes for file security labels, say N. | |
410 | ||
411 | config JFS_DEBUG | |
412 | bool "JFS debugging" | |
413 | depends on JFS_FS | |
414 | help | |
415 | If you are experiencing any problems with the JFS filesystem, say | |
416 | Y here. This will result in additional debugging messages to be | |
417 | written to the system log. Under normal circumstances, this | |
418 | results in very little overhead. | |
419 | ||
420 | config JFS_STATISTICS | |
421 | bool "JFS statistics" | |
422 | depends on JFS_FS | |
423 | help | |
424 | Enabling this option will cause statistics from the JFS file system | |
425 | to be made available to the user in the /proc/fs/jfs/ directory. | |
426 | ||
427 | config FS_POSIX_ACL | |
89206955 | 428 | # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4) |
1da177e4 LT |
429 | # |
430 | # NOTE: you can implement Posix ACLs without these helpers (XFS does). | |
431 | # Never use this symbol for ifdefs. | |
432 | # | |
433 | bool | |
b84c2157 | 434 | default n |
1da177e4 | 435 | |
bfcd17a6 TP |
436 | config FILE_LOCKING |
437 | bool "Enable POSIX file locking API" if EMBEDDED | |
438 | default y | |
439 | help | |
440 | This option enables standard file locking support, required | |
441 | for filesystems like NFS and for the flock() system | |
442 | call. Disabling this option saves about 11k. | |
443 | ||
1da177e4 | 444 | source "fs/xfs/Kconfig" |
f7825dcf | 445 | source "fs/gfs2/Kconfig" |
1da177e4 | 446 | |
b4e40a51 | 447 | config OCFS2_FS |
02ed8416 MF |
448 | tristate "OCFS2 file system support" |
449 | depends on NET && SYSFS | |
b4e40a51 | 450 | select CONFIGFS_FS |
2b4e30fb | 451 | select JBD2 |
b4e40a51 | 452 | select CRC32 |
b4e40a51 MF |
453 | help |
454 | OCFS2 is a general purpose extent based shared disk cluster file | |
455 | system with many similarities to ext3. It supports 64 bit inode | |
456 | numbers, and has automatically extending metadata groups which may | |
457 | also make it attractive for non-clustered use. | |
458 | ||
459 | You'll want to install the ocfs2-tools package in order to at least | |
460 | get "mount.ocfs2". | |
461 | ||
462 | Project web page: http://oss.oracle.com/projects/ocfs2 | |
463 | Tools web page: http://oss.oracle.com/projects/ocfs2-tools | |
464 | OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/ | |
465 | ||
1252c434 MF |
466 | For more information on OCFS2, see the file |
467 | <file:Documentation/filesystems/ocfs2.txt>. | |
b4e40a51 | 468 | |
9341d229 JB |
469 | config OCFS2_FS_O2CB |
470 | tristate "O2CB Kernelspace Clustering" | |
471 | depends on OCFS2_FS | |
472 | default y | |
473 | help | |
474 | OCFS2 includes a simple kernelspace clustering package, the OCFS2 | |
475 | Cluster Base. It only requires a very small userspace component | |
476 | to configure it. This comes with the standard ocfs2-tools package. | |
477 | O2CB is limited to maintaining a cluster for OCFS2 file systems. | |
478 | It cannot manage any other cluster applications. | |
479 | ||
480 | It is always safe to say Y here, as the clustering method is | |
481 | run-time selectable. | |
482 | ||
483 | config OCFS2_FS_USERSPACE_CLUSTER | |
484 | tristate "OCFS2 Userspace Clustering" | |
485 | depends on OCFS2_FS && DLM | |
486 | default y | |
487 | help | |
488 | This option will allow OCFS2 to use userspace clustering services | |
489 | in conjunction with the DLM in fs/dlm. If you are using a | |
490 | userspace cluster manager, say Y here. | |
491 | ||
492 | It is safe to say Y, as the clustering method is run-time | |
493 | selectable. | |
494 | ||
ce7231e9 SM |
495 | config OCFS2_FS_STATS |
496 | bool "OCFS2 statistics" | |
497 | depends on OCFS2_FS | |
498 | default y | |
499 | help | |
500 | This option allows some fs statistics to be captured. Enabling | |
501 | this option may increase the memory consumption. | |
502 | ||
2b388c67 JB |
503 | config OCFS2_DEBUG_MASKLOG |
504 | bool "OCFS2 logging support" | |
505 | depends on OCFS2_FS | |
506 | default y | |
507 | help | |
508 | The ocfs2 filesystem has an extensive logging system. The system | |
509 | allows selection of events to log via files in /sys/o2cb/logmask/. | |
510 | This option will enlarge your kernel, but it allows debugging of | |
511 | ocfs2 filesystem issues. | |
512 | ||
5a58c3ef JK |
513 | config OCFS2_DEBUG_FS |
514 | bool "OCFS2 expensive checks" | |
515 | depends on OCFS2_FS | |
516 | default n | |
517 | help | |
518 | This option will enable expensive consistency checks. Enable | |
519 | this option for debugging only as it is likely to decrease | |
520 | performance of the filesystem. | |
521 | ||
2b4e30fb JB |
522 | config OCFS2_COMPAT_JBD |
523 | bool "Use JBD for compatibility" | |
524 | depends on OCFS2_FS | |
525 | default n | |
526 | select JBD | |
527 | help | |
528 | The ocfs2 filesystem now uses JBD2 for its journalling. JBD2 | |
529 | is backwards compatible with JBD. It is safe to say N here. | |
530 | However, if you really want to use the original JBD, say Y here. | |
531 | ||
25fad945 | 532 | endif # BLOCK |
1da177e4 | 533 | |
25fad945 RD |
534 | config DNOTIFY |
535 | bool "Dnotify support" | |
536 | default y | |
537 | help | |
538 | Dnotify is a directory-based per-fd file change notification system | |
539 | that uses signals to communicate events to user-space. There exist | |
540 | superior alternatives, but some applications may still rely on | |
541 | dnotify. | |
1da177e4 | 542 | |
25fad945 | 543 | If unsure, say Y. |
9361401e | 544 | |
0eeca283 RL |
545 | config INOTIFY |
546 | bool "Inotify file change notification support" | |
547 | default y | |
548 | ---help--- | |
2d9048e2 AG |
549 | Say Y here to enable inotify support. Inotify is a file change |
550 | notification system and a replacement for dnotify. Inotify fixes | |
551 | numerous shortcomings in dnotify and introduces several new features | |
552 | including multiple file events, one-shot support, and unmount | |
3de11748 RL |
553 | notification. |
554 | ||
e403149c | 555 | For more information, see <file:Documentation/filesystems/inotify.txt> |
0eeca283 RL |
556 | |
557 | If unsure, say Y. | |
558 | ||
2d9048e2 AG |
559 | config INOTIFY_USER |
560 | bool "Inotify support for userspace" | |
561 | depends on INOTIFY | |
562 | default y | |
563 | ---help--- | |
564 | Say Y here to enable inotify support for userspace, including the | |
565 | associated system calls. Inotify allows monitoring of both files and | |
566 | directories via a single open fd. Events are read from the file | |
567 | descriptor, which is also select()- and poll()-able. | |
568 | ||
e403149c | 569 | For more information, see <file:Documentation/filesystems/inotify.txt> |
2d9048e2 | 570 | |
0eeca283 RL |
571 | If unsure, say Y. |
572 | ||
1da177e4 LT |
573 | config QUOTA |
574 | bool "Quota support" | |
575 | help | |
576 | If you say Y here, you will be able to set per user limits for disk | |
577 | usage (also called disk quotas). Currently, it works for the | |
578 | ext2, ext3, and reiserfs file system. ext3 also supports journalled | |
579 | quotas for which you don't need to run quotacheck(8) after an unclean | |
919532a5 AB |
580 | shutdown. |
581 | For further details, read the Quota mini-HOWTO, available from | |
1da177e4 LT |
582 | <http://www.tldp.org/docs.html#howto>, or the documentation provided |
583 | with the quota tools. Probably the quota support is only useful for | |
584 | multi user systems. If unsure, say N. | |
585 | ||
8e893469 JK |
586 | config QUOTA_NETLINK_INTERFACE |
587 | bool "Report quota messages through netlink interface" | |
588 | depends on QUOTA && NET | |
589 | help | |
590 | If you say Y here, quota warnings (about exceeding softlimit, reaching | |
591 | hardlimit, etc.) will be reported through netlink interface. If unsure, | |
592 | say Y. | |
593 | ||
594 | config PRINT_QUOTA_WARNING | |
595 | bool "Print quota warnings to console (OBSOLETE)" | |
596 | depends on QUOTA | |
597 | default y | |
598 | help | |
599 | If you say Y here, quota warnings (about exceeding softlimit, reaching | |
600 | hardlimit, etc.) will be printed to the process' controlling terminal. | |
601 | Note that this behavior is currently deprecated and may go away in | |
602 | future. Please use notification via netlink socket instead. | |
603 | ||
1da177e4 LT |
604 | config QFMT_V1 |
605 | tristate "Old quota format support" | |
606 | depends on QUOTA | |
607 | help | |
608 | This quota format was (is) used by kernels earlier than 2.4.22. If | |
609 | you have quota working and you don't want to convert to new quota | |
610 | format say Y here. | |
611 | ||
612 | config QFMT_V2 | |
613 | tristate "Quota format v2 support" | |
614 | depends on QUOTA | |
615 | help | |
616 | This quota format allows using quotas with 32-bit UIDs/GIDs. If you | |
919532a5 | 617 | need this functionality say Y here. |
1da177e4 LT |
618 | |
619 | config QUOTACTL | |
620 | bool | |
621 | depends on XFS_QUOTA || QUOTA | |
622 | default y | |
623 | ||
1da177e4 LT |
624 | config AUTOFS_FS |
625 | tristate "Kernel automounter support" | |
626 | help | |
627 | The automounter is a tool to automatically mount remote file systems | |
628 | on demand. This implementation is partially kernel-based to reduce | |
629 | overhead in the already-mounted case; this is unlike the BSD | |
630 | automounter (amd), which is a pure user space daemon. | |
631 | ||
632 | To use the automounter you need the user-space tools from the autofs | |
633 | package; you can find the location in <file:Documentation/Changes>. | |
634 | You also want to answer Y to "NFS file system support", below. | |
635 | ||
636 | If you want to use the newer version of the automounter with more | |
637 | features, say N here and say Y to "Kernel automounter v4 support", | |
638 | below. | |
639 | ||
640 | To compile this support as a module, choose M here: the module will be | |
641 | called autofs. | |
642 | ||
643 | If you are not a part of a fairly large, distributed network, you | |
644 | probably do not need an automounter, and can say N here. | |
645 | ||
646 | config AUTOFS4_FS | |
647 | tristate "Kernel automounter version 4 support (also supports v3)" | |
648 | help | |
649 | The automounter is a tool to automatically mount remote file systems | |
650 | on demand. This implementation is partially kernel-based to reduce | |
651 | overhead in the already-mounted case; this is unlike the BSD | |
652 | automounter (amd), which is a pure user space daemon. | |
653 | ||
654 | To use the automounter you need the user-space tools from | |
655 | <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also | |
656 | want to answer Y to "NFS file system support", below. | |
657 | ||
658 | To compile this support as a module, choose M here: the module will be | |
659 | called autofs4. You will need to add "alias autofs autofs4" to your | |
660 | modules configuration file. | |
661 | ||
662 | If you are not a part of a fairly large, distributed network or | |
663 | don't have a laptop which needs to dynamically reconfigure to the | |
664 | local network, you probably do not need an automounter, and can say | |
665 | N here. | |
666 | ||
04578f17 MS |
667 | config FUSE_FS |
668 | tristate "Filesystem in Userspace support" | |
669 | help | |
670 | With FUSE it is possible to implement a fully functional filesystem | |
671 | in a userspace program. | |
672 | ||
673 | There's also companion library: libfuse. This library along with | |
674 | utilities is available from the FUSE homepage: | |
675 | <http://fuse.sourceforge.net/> | |
676 | ||
909021ea MS |
677 | See <file:Documentation/filesystems/fuse.txt> for more information. |
678 | See <file:Documentation/Changes> for needed library/utility version. | |
679 | ||
04578f17 MS |
680 | If you want to develop a userspace FS, or if you want to use |
681 | a filesystem based on FUSE, answer Y or M. | |
682 | ||
f2fbc6c2 RD |
683 | config GENERIC_ACL |
684 | bool | |
685 | select FS_POSIX_ACL | |
686 | ||
9361401e | 687 | if BLOCK |
1da177e4 LT |
688 | menu "CD-ROM/DVD Filesystems" |
689 | ||
690 | config ISO9660_FS | |
691 | tristate "ISO 9660 CDROM file system support" | |
692 | help | |
693 | This is the standard file system used on CD-ROMs. It was previously | |
694 | known as "High Sierra File System" and is called "hsfs" on other | |
695 | Unix systems. The so-called Rock-Ridge extensions which allow for | |
696 | long Unix filenames and symbolic links are also supported by this | |
697 | driver. If you have a CD-ROM drive and want to do more with it than | |
698 | just listen to audio CDs and watch its LEDs, say Y (and read | |
699 | <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO, | |
700 | available from <http://www.tldp.org/docs.html#howto>), thereby | |
701 | enlarging your kernel by about 27 KB; otherwise say N. | |
702 | ||
703 | To compile this file system support as a module, choose M here: the | |
704 | module will be called isofs. | |
705 | ||
706 | config JOLIET | |
707 | bool "Microsoft Joliet CDROM extensions" | |
708 | depends on ISO9660_FS | |
709 | select NLS | |
710 | help | |
711 | Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system | |
712 | which allows for long filenames in unicode format (unicode is the | |
713 | new 16 bit character code, successor to ASCII, which encodes the | |
714 | characters of almost all languages of the world; see | |
715 | <http://www.unicode.org/> for more information). Say Y here if you | |
716 | want to be able to read Joliet CD-ROMs under Linux. | |
717 | ||
718 | config ZISOFS | |
719 | bool "Transparent decompression extension" | |
720 | depends on ISO9660_FS | |
721 | select ZLIB_INFLATE | |
722 | help | |
723 | This is a Linux-specific extension to RockRidge which lets you store | |
724 | data in compressed form on a CD-ROM and have it transparently | |
725 | decompressed when the CD-ROM is accessed. See | |
726 | <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools | |
727 | necessary to create such a filesystem. Say Y here if you want to be | |
728 | able to read such compressed CD-ROMs. | |
729 | ||
1da177e4 LT |
730 | config UDF_FS |
731 | tristate "UDF file system support" | |
f845fced | 732 | select CRC_ITU_T |
1da177e4 LT |
733 | help |
734 | This is the new file system used on some CD-ROMs and DVDs. Say Y if | |
735 | you intend to mount DVD discs or CDRW's written in packet mode, or | |
736 | if written to by other UDF utilities, such as DirectCD. | |
737 | Please read <file:Documentation/filesystems/udf.txt>. | |
738 | ||
739 | To compile this file system support as a module, choose M here: the | |
740 | module will be called udf. | |
741 | ||
742 | If unsure, say N. | |
743 | ||
744 | config UDF_NLS | |
745 | bool | |
746 | default y | |
747 | depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y) | |
748 | ||
749 | endmenu | |
25fad945 | 750 | endif # BLOCK |
1da177e4 | 751 | |
9361401e | 752 | if BLOCK |
1da177e4 LT |
753 | menu "DOS/FAT/NT Filesystems" |
754 | ||
755 | config FAT_FS | |
756 | tristate | |
757 | select NLS | |
758 | help | |
759 | If you want to use one of the FAT-based file systems (the MS-DOS and | |
760 | VFAT (Windows 95) file systems), then you must say Y or M here | |
761 | to include FAT support. You will then be able to mount partitions or | |
762 | diskettes with FAT-based file systems and transparently access the | |
763 | files on them, i.e. MSDOS files will look and behave just like all | |
764 | other Unix files. | |
765 | ||
766 | This FAT support is not a file system in itself, it only provides | |
767 | the foundation for the other file systems. You will have to say Y or | |
768 | M to at least one of "MSDOS fs support" or "VFAT fs support" in | |
769 | order to make use of it. | |
770 | ||
771 | Another way to read and write MSDOS floppies and hard drive | |
772 | partitions from within Linux (but not transparently) is with the | |
773 | mtools ("man mtools") program suite. You don't need to say Y here in | |
774 | order to do that. | |
775 | ||
776 | If you need to move large files on floppies between a DOS and a | |
777 | Linux box, say Y here, mount the floppy under Linux with an MSDOS | |
778 | file system and use GNU tar's M option. GNU tar is a program | |
779 | available for Unix and DOS ("man tar" or "info tar"). | |
780 | ||
1da177e4 LT |
781 | The FAT support will enlarge your kernel by about 37 KB. If unsure, |
782 | say Y. | |
783 | ||
784 | To compile this as a module, choose M here: the module will be called | |
785 | fat. Note that if you compile the FAT support as a module, you | |
786 | cannot compile any of the FAT-based file systems into the kernel | |
787 | -- they will have to be modules as well. | |
788 | ||
789 | config MSDOS_FS | |
790 | tristate "MSDOS fs support" | |
791 | select FAT_FS | |
792 | help | |
793 | This allows you to mount MSDOS partitions of your hard drive (unless | |
794 | they are compressed; to access compressed MSDOS partitions under | |
795 | Linux, you can either use the DOS emulator DOSEMU, described in the | |
796 | DOSEMU-HOWTO, available from | |
797 | <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in | |
798 | <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you | |
799 | intend to use dosemu with a non-compressed MSDOS partition, say Y | |
800 | here) and MSDOS floppies. This means that file access becomes | |
801 | transparent, i.e. the MSDOS files look and behave just like all | |
802 | other Unix files. | |
803 | ||
804 | If you have Windows 95 or Windows NT installed on your MSDOS | |
805 | partitions, you should use the VFAT file system (say Y to "VFAT fs | |
806 | support" below), or you will not be able to see the long filenames | |
807 | generated by Windows 95 / Windows NT. | |
808 | ||
809 | This option will enlarge your kernel by about 7 KB. If unsure, | |
810 | answer Y. This will only work if you said Y to "DOS FAT fs support" | |
811 | as well. To compile this as a module, choose M here: the module will | |
812 | be called msdos. | |
813 | ||
814 | config VFAT_FS | |
815 | tristate "VFAT (Windows-95) fs support" | |
816 | select FAT_FS | |
817 | help | |
818 | This option provides support for normal Windows file systems with | |
819 | long filenames. That includes non-compressed FAT-based file systems | |
820 | used by Windows 95, Windows 98, Windows NT 4.0, and the Unix | |
821 | programs from the mtools package. | |
822 | ||
823 | The VFAT support enlarges your kernel by about 10 KB and it only | |
824 | works if you said Y to the "DOS FAT fs support" above. Please read | |
825 | the file <file:Documentation/filesystems/vfat.txt> for details. If | |
826 | unsure, say Y. | |
827 | ||
828 | To compile this as a module, choose M here: the module will be called | |
829 | vfat. | |
830 | ||
831 | config FAT_DEFAULT_CODEPAGE | |
832 | int "Default codepage for FAT" | |
833 | depends on MSDOS_FS || VFAT_FS | |
834 | default 437 | |
835 | help | |
836 | This option should be set to the codepage of your FAT filesystems. | |
837 | It can be overridden with the "codepage" mount option. | |
838 | See <file:Documentation/filesystems/vfat.txt> for more information. | |
839 | ||
840 | config FAT_DEFAULT_IOCHARSET | |
841 | string "Default iocharset for FAT" | |
842 | depends on VFAT_FS | |
843 | default "iso8859-1" | |
844 | help | |
845 | Set this to the default input/output character set you'd | |
846 | like FAT to use. It should probably match the character set | |
847 | that most of your FAT filesystems use, and can be overridden | |
848 | with the "iocharset" mount option for FAT filesystems. | |
849 | Note that "utf8" is not recommended for FAT filesystems. | |
850 | If unsure, you shouldn't set "utf8" here. | |
851 | See <file:Documentation/filesystems/vfat.txt> for more information. | |
852 | ||
853 | config NTFS_FS | |
854 | tristate "NTFS file system support" | |
855 | select NLS | |
856 | help | |
857 | NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003. | |
858 | ||
859 | Saying Y or M here enables read support. There is partial, but | |
860 | safe, write support available. For write support you must also | |
861 | say Y to "NTFS write support" below. | |
862 | ||
863 | There are also a number of user-space tools available, called | |
864 | ntfsprogs. These include ntfsundelete and ntfsresize, that work | |
865 | without NTFS support enabled in the kernel. | |
866 | ||
867 | This is a rewrite from scratch of Linux NTFS support and replaced | |
868 | the old NTFS code starting with Linux 2.5.11. A backport to | |
869 | the Linux 2.4 kernel series is separately available as a patch | |
870 | from the project web site. | |
871 | ||
872 | For more information see <file:Documentation/filesystems/ntfs.txt> | |
337e2ab5 | 873 | and <http://www.linux-ntfs.org/>. |
1da177e4 LT |
874 | |
875 | To compile this file system support as a module, choose M here: the | |
876 | module will be called ntfs. | |
877 | ||
878 | If you are not using Windows NT, 2000, XP or 2003 in addition to | |
879 | Linux on your computer it is safe to say N. | |
880 | ||
881 | config NTFS_DEBUG | |
882 | bool "NTFS debugging support" | |
883 | depends on NTFS_FS | |
884 | help | |
885 | If you are experiencing any problems with the NTFS file system, say | |
886 | Y here. This will result in additional consistency checks to be | |
887 | performed by the driver as well as additional debugging messages to | |
888 | be written to the system log. Note that debugging messages are | |
889 | disabled by default. To enable them, supply the option debug_msgs=1 | |
890 | at the kernel command line when booting the kernel or as an option | |
891 | to insmod when loading the ntfs module. Once the driver is active, | |
892 | you can enable debugging messages by doing (as root): | |
893 | echo 1 > /proc/sys/fs/ntfs-debug | |
894 | Replacing the "1" with "0" would disable debug messages. | |
895 | ||
896 | If you leave debugging messages disabled, this results in little | |
897 | overhead, but enabling debug messages results in very significant | |
898 | slowdown of the system. | |
899 | ||
900 | When reporting bugs, please try to have available a full dump of | |
901 | debugging messages while the misbehaviour was occurring. | |
902 | ||
903 | config NTFS_RW | |
904 | bool "NTFS write support" | |
905 | depends on NTFS_FS | |
906 | help | |
907 | This enables the partial, but safe, write support in the NTFS driver. | |
908 | ||
909 | The only supported operation is overwriting existing files, without | |
910 | changing the file length. No file or directory creation, deletion or | |
911 | renaming is possible. Note only non-resident files can be written to | |
912 | so you may find that some very small files (<500 bytes or so) cannot | |
913 | be written to. | |
914 | ||
915 | While we cannot guarantee that it will not damage any data, we have | |
916 | so far not received a single report where the driver would have | |
917 | damaged someones data so we assume it is perfectly safe to use. | |
918 | ||
919 | Note: While write support is safe in this version (a rewrite from | |
920 | scratch of the NTFS support), it should be noted that the old NTFS | |
921 | write support, included in Linux 2.5.10 and before (since 1997), | |
922 | is not safe. | |
923 | ||
924 | This is currently useful with TopologiLinux. TopologiLinux is run | |
925 | on top of any DOS/Microsoft Windows system without partitioning your | |
926 | hard disk. Unlike other Linux distributions TopologiLinux does not | |
927 | need its own partition. For more information see | |
928 | <http://topologi-linux.sourceforge.net/> | |
929 | ||
930 | It is perfectly safe to say N here. | |
931 | ||
932 | endmenu | |
25fad945 | 933 | endif # BLOCK |
1da177e4 LT |
934 | |
935 | menu "Pseudo filesystems" | |
936 | ||
6eedf8d3 | 937 | source "fs/proc/Kconfig" |
b89a8171 | 938 | |
1da177e4 LT |
939 | config SYSFS |
940 | bool "sysfs file system support" if EMBEDDED | |
941 | default y | |
942 | help | |
943 | The sysfs filesystem is a virtual filesystem that the kernel uses to | |
944 | export internal kernel objects, their attributes, and their | |
945 | relationships to one another. | |
946 | ||
947 | Users can use sysfs to ascertain useful information about the running | |
948 | kernel, such as the devices the kernel has discovered on each bus and | |
949 | which driver each is bound to. sysfs can also be used to tune devices | |
950 | and other kernel subsystems. | |
951 | ||
952 | Some system agents rely on the information in sysfs to operate. | |
953 | /sbin/hotplug uses device and object attributes in sysfs to assist in | |
03a67a46 | 954 | delegating policy decisions, like persistently naming devices. |
1da177e4 LT |
955 | |
956 | sysfs is currently used by the block subsystem to mount the root | |
957 | partition. If sysfs is disabled you must specify the boot device on | |
958 | the kernel boot command line via its major and minor numbers. For | |
959 | example, "root=03:01" for /dev/hda1. | |
960 | ||
961 | Designers of embedded systems may wish to say N here to conserve space. | |
962 | ||
1da177e4 LT |
963 | config TMPFS |
964 | bool "Virtual memory file system support (former shm fs)" | |
965 | help | |
966 | Tmpfs is a file system which keeps all files in virtual memory. | |
967 | ||
968 | Everything in tmpfs is temporary in the sense that no files will be | |
969 | created on your hard drive. The files live in memory and swap | |
970 | space. If you unmount a tmpfs instance, everything stored therein is | |
971 | lost. | |
972 | ||
973 | See <file:Documentation/filesystems/tmpfs.txt> for details. | |
974 | ||
39f0247d AG |
975 | config TMPFS_POSIX_ACL |
976 | bool "Tmpfs POSIX Access Control Lists" | |
977 | depends on TMPFS | |
978 | select GENERIC_ACL | |
979 | help | |
980 | POSIX Access Control Lists (ACLs) support permissions for users and | |
981 | groups beyond the owner/group/world scheme. | |
982 | ||
983 | To learn more about Access Control Lists, visit the POSIX ACLs for | |
984 | Linux website <http://acl.bestbits.at/>. | |
985 | ||
986 | If you don't know what Access Control Lists are, say N. | |
987 | ||
1da177e4 LT |
988 | config HUGETLBFS |
989 | bool "HugeTLB file system support" | |
53492b1d GS |
990 | depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \ |
991 | (S390 && 64BIT) || BROKEN | |
dda27d1a AO |
992 | help |
993 | hugetlbfs is a filesystem backing for HugeTLB pages, based on | |
994 | ramfs. For architectures that support it, say Y here and read | |
995 | <file:Documentation/vm/hugetlbpage.txt> for details. | |
996 | ||
997 | If unsure, say N. | |
1da177e4 LT |
998 | |
999 | config HUGETLB_PAGE | |
1000 | def_bool HUGETLBFS | |
1001 | ||
7063fbf2 | 1002 | config CONFIGFS_FS |
02ac0499 JB |
1003 | tristate "Userspace-driven configuration filesystem" |
1004 | depends on SYSFS | |
7063fbf2 JB |
1005 | help |
1006 | configfs is a ram-based filesystem that provides the converse | |
1007 | of sysfs's functionality. Where sysfs is a filesystem-based | |
1008 | view of kernel objects, configfs is a filesystem-based manager | |
1009 | of kernel objects, or config_items. | |
1010 | ||
1011 | Both sysfs and configfs can and should exist together on the | |
1012 | same system. One is not a replacement for the other. | |
1013 | ||
1da177e4 LT |
1014 | endmenu |
1015 | ||
1016 | menu "Miscellaneous filesystems" | |
1017 | ||
1018 | config ADFS_FS | |
1019 | tristate "ADFS file system support (EXPERIMENTAL)" | |
9361401e | 1020 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
1021 | help |
1022 | The Acorn Disc Filing System is the standard file system of the | |
1023 | RiscOS operating system which runs on Acorn's ARM-based Risc PC | |
1024 | systems and the Acorn Archimedes range of machines. If you say Y | |
1025 | here, Linux will be able to read from ADFS partitions on hard drives | |
1026 | and from ADFS-formatted floppy discs. If you also want to be able to | |
1027 | write to those devices, say Y to "ADFS write support" below. | |
1028 | ||
1029 | The ADFS partition should be the first partition (i.e., | |
1030 | /dev/[hs]d?1) on each of your drives. Please read the file | |
1031 | <file:Documentation/filesystems/adfs.txt> for further details. | |
1032 | ||
1033 | To compile this code as a module, choose M here: the module will be | |
1034 | called adfs. | |
1035 | ||
1036 | If unsure, say N. | |
1037 | ||
1038 | config ADFS_FS_RW | |
1039 | bool "ADFS write support (DANGEROUS)" | |
1040 | depends on ADFS_FS | |
1041 | help | |
1042 | If you say Y here, you will be able to write to ADFS partitions on | |
1043 | hard drives and ADFS-formatted floppy disks. This is experimental | |
1044 | codes, so if you're unsure, say N. | |
1045 | ||
1046 | config AFFS_FS | |
1047 | tristate "Amiga FFS file system support (EXPERIMENTAL)" | |
9361401e | 1048 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
1049 | help |
1050 | The Fast File System (FFS) is the common file system used on hard | |
1051 | disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y | |
1052 | if you want to be able to read and write files from and to an Amiga | |
1053 | FFS partition on your hard drive. Amiga floppies however cannot be | |
1054 | read with this driver due to an incompatibility of the floppy | |
1055 | controller used in an Amiga and the standard floppy controller in | |
1056 | PCs and workstations. Read <file:Documentation/filesystems/affs.txt> | |
1057 | and <file:fs/affs/Changes>. | |
1058 | ||
1059 | With this driver you can also mount disk files used by Bernd | |
1060 | Schmidt's Un*X Amiga Emulator | |
1061 | (<http://www.freiburg.linux.de/~uae/>). | |
1062 | If you want to do this, you will also need to say Y or M to "Loop | |
1063 | device support", above. | |
1064 | ||
1065 | To compile this file system support as a module, choose M here: the | |
1066 | module will be called affs. If unsure, say N. | |
1067 | ||
237fead6 MH |
1068 | config ECRYPT_FS |
1069 | tristate "eCrypt filesystem layer support (EXPERIMENTAL)" | |
88b4a07e | 1070 | depends on EXPERIMENTAL && KEYS && CRYPTO && NET |
237fead6 MH |
1071 | help |
1072 | Encrypted filesystem that operates on the VFS layer. See | |
e403149c | 1073 | <file:Documentation/filesystems/ecryptfs.txt> to learn more about |
237fead6 MH |
1074 | eCryptfs. Userspace components are required and can be |
1075 | obtained from <http://ecryptfs.sf.net>. | |
1076 | ||
1077 | To compile this file system support as a module, choose M here: the | |
1078 | module will be called ecryptfs. | |
1079 | ||
1da177e4 LT |
1080 | config HFS_FS |
1081 | tristate "Apple Macintosh file system support (EXPERIMENTAL)" | |
9361401e | 1082 | depends on BLOCK && EXPERIMENTAL |
878129a3 | 1083 | select NLS |
1da177e4 LT |
1084 | help |
1085 | If you say Y here, you will be able to mount Macintosh-formatted | |
1086 | floppy disks and hard drive partitions with full read-write access. | |
889c94a1 JFS |
1087 | Please read <file:Documentation/filesystems/hfs.txt> to learn about |
1088 | the available mount options. | |
1da177e4 LT |
1089 | |
1090 | To compile this file system support as a module, choose M here: the | |
1091 | module will be called hfs. | |
1092 | ||
1093 | config HFSPLUS_FS | |
1094 | tristate "Apple Extended HFS file system support" | |
9361401e | 1095 | depends on BLOCK |
1da177e4 LT |
1096 | select NLS |
1097 | select NLS_UTF8 | |
1098 | help | |
1099 | If you say Y here, you will be able to mount extended format | |
1100 | Macintosh-formatted hard drive partitions with full read-write access. | |
1101 | ||
1102 | This file system is often called HFS+ and was introduced with | |
1103 | MacOS 8. It includes all Mac specific filesystem data such as | |
1104 | data forks and creator codes, but it also has several UNIX | |
1105 | style features such as file ownership and permissions. | |
1106 | ||
1107 | config BEFS_FS | |
1108 | tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)" | |
9361401e | 1109 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
1110 | select NLS |
1111 | help | |
1112 | The BeOS File System (BeFS) is the native file system of Be, Inc's | |
1113 | BeOS. Notable features include support for arbitrary attributes | |
3cb2fccc | 1114 | on files and directories, and database-like indices on selected |
1da177e4 LT |
1115 | attributes. (Also note that this driver doesn't make those features |
1116 | available at this time). It is a 64 bit filesystem, so it supports | |
44c09201 | 1117 | extremely large volumes and files. |
1da177e4 LT |
1118 | |
1119 | If you use this filesystem, you should also say Y to at least one | |
1120 | of the NLS (native language support) options below. | |
1121 | ||
1122 | If you don't know what this is about, say N. | |
1123 | ||
1124 | To compile this as a module, choose M here: the module will be | |
1125 | called befs. | |
1126 | ||
1127 | config BEFS_DEBUG | |
1128 | bool "Debug BeFS" | |
1129 | depends on BEFS_FS | |
1130 | help | |
1131 | If you say Y here, you can use the 'debug' mount option to enable | |
c7736339 | 1132 | debugging output from the driver. |
1da177e4 LT |
1133 | |
1134 | config BFS_FS | |
1135 | tristate "BFS file system support (EXPERIMENTAL)" | |
9361401e | 1136 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
1137 | help |
1138 | Boot File System (BFS) is a file system used under SCO UnixWare to | |
1139 | allow the bootloader access to the kernel image and other important | |
1140 | files during the boot process. It is usually mounted under /stand | |
1141 | and corresponds to the slice marked as "STAND" in the UnixWare | |
1142 | partition. You should say Y if you want to read or write the files | |
1143 | on your /stand slice from within Linux. You then also need to say Y | |
1144 | to "UnixWare slices support", below. More information about the BFS | |
1145 | file system is contained in the file | |
1146 | <file:Documentation/filesystems/bfs.txt>. | |
1147 | ||
1148 | If you don't know what this is about, say N. | |
1149 | ||
1150 | To compile this as a module, choose M here: the module will be called | |
1151 | bfs. Note that the file system of your root partition (the one | |
1152 | containing the directory /) cannot be compiled as a module. | |
1153 | ||
1154 | ||
1155 | ||
1156 | config EFS_FS | |
1157 | tristate "EFS file system support (read only) (EXPERIMENTAL)" | |
9361401e | 1158 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
1159 | help |
1160 | EFS is an older file system used for non-ISO9660 CD-ROMs and hard | |
1161 | disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer | |
1162 | uses the XFS file system for hard disk partitions however). | |
1163 | ||
1164 | This implementation only offers read-only access. If you don't know | |
1165 | what all this is about, it's safe to say N. For more information | |
1166 | about EFS see its home page at <http://aeschi.ch.eu.org/efs/>. | |
1167 | ||
1168 | To compile the EFS file system support as a module, choose M here: the | |
1169 | module will be called efs. | |
1170 | ||
31db6e9e | 1171 | source "fs/jffs2/Kconfig" |
0d7eff87 AB |
1172 | # UBIFS File system configuration |
1173 | source "fs/ubifs/Kconfig" | |
1174 | ||
1da177e4 LT |
1175 | config CRAMFS |
1176 | tristate "Compressed ROM file system support (cramfs)" | |
9361401e | 1177 | depends on BLOCK |
1da177e4 LT |
1178 | select ZLIB_INFLATE |
1179 | help | |
1180 | Saying Y here includes support for CramFs (Compressed ROM File | |
1181 | System). CramFs is designed to be a simple, small, and compressed | |
1182 | file system for ROM based embedded systems. CramFs is read-only, | |
1183 | limited to 256MB file systems (with 16MB files), and doesn't support | |
1184 | 16/32 bits uid/gid, hard links and timestamps. | |
1185 | ||
1186 | See <file:Documentation/filesystems/cramfs.txt> and | |
1187 | <file:fs/cramfs/README> for further information. | |
1188 | ||
1189 | To compile this as a module, choose M here: the module will be called | |
1190 | cramfs. Note that the root file system (the one containing the | |
1191 | directory /) cannot be compiled as a module. | |
1192 | ||
1193 | If unsure, say N. | |
1194 | ||
1195 | config VXFS_FS | |
1196 | tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)" | |
9361401e | 1197 | depends on BLOCK |
1da177e4 LT |
1198 | help |
1199 | FreeVxFS is a file system driver that support the VERITAS VxFS(TM) | |
1200 | file system format. VERITAS VxFS(TM) is the standard file system | |
1201 | of SCO UnixWare (and possibly others) and optionally available | |
1202 | for Sunsoft Solaris, HP-UX and many other operating systems. | |
1203 | Currently only readonly access is supported. | |
1204 | ||
1205 | NOTE: the file system type as used by mount(1), mount(2) and | |
1206 | fstab(5) is 'vxfs' as it describes the file system format, not | |
1207 | the actual driver. | |
1208 | ||
1209 | To compile this as a module, choose M here: the module will be | |
1210 | called freevxfs. If unsure, say N. | |
1211 | ||
25fad945 RD |
1212 | config MINIX_FS |
1213 | tristate "Minix file system support" | |
1214 | depends on BLOCK | |
1215 | help | |
1216 | Minix is a simple operating system used in many classes about OS's. | |
1217 | The minix file system (method to organize files on a hard disk | |
1218 | partition or a floppy disk) was the original file system for Linux, | |
1219 | but has been superseded by the second extended file system ext2fs. | |
1220 | You don't want to use the minix file system on your hard disk | |
1221 | because of certain built-in restrictions, but it is sometimes found | |
1222 | on older Linux floppy disks. This option will enlarge your kernel | |
1223 | by about 28 KB. If unsure, say N. | |
1224 | ||
1225 | To compile this file system support as a module, choose M here: the | |
1226 | module will be called minix. Note that the file system of your root | |
1227 | partition (the one containing the directory /) cannot be compiled as | |
1228 | a module. | |
1229 | ||
63ca8ce2 BC |
1230 | config OMFS_FS |
1231 | tristate "SonicBlue Optimized MPEG File System support" | |
1232 | depends on BLOCK | |
1233 | select CRC_ITU_T | |
1234 | help | |
1235 | This is the proprietary file system used by the Rio Karma music | |
1236 | player and ReplayTV DVR. Despite the name, this filesystem is not | |
1237 | more efficient than a standard FS for MPEG files, in fact likely | |
1238 | the opposite is true. Say Y if you have either of these devices | |
1239 | and wish to mount its disk. | |
1240 | ||
1241 | To compile this file system support as a module, choose M here: the | |
1242 | module will be called omfs. If unsure, say N. | |
1da177e4 LT |
1243 | |
1244 | config HPFS_FS | |
1245 | tristate "OS/2 HPFS file system support" | |
9361401e | 1246 | depends on BLOCK |
1da177e4 LT |
1247 | help |
1248 | OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS | |
1249 | is the file system used for organizing files on OS/2 hard disk | |
1250 | partitions. Say Y if you want to be able to read files from and | |
1251 | write files to an OS/2 HPFS partition on your hard drive. OS/2 | |
1252 | floppies however are in regular MSDOS format, so you don't need this | |
1253 | option in order to be able to read them. Read | |
1254 | <file:Documentation/filesystems/hpfs.txt>. | |
1255 | ||
1256 | To compile this file system support as a module, choose M here: the | |
1257 | module will be called hpfs. If unsure, say N. | |
1258 | ||
1259 | ||
1da177e4 LT |
1260 | config QNX4FS_FS |
1261 | tristate "QNX4 file system support (read only)" | |
9361401e | 1262 | depends on BLOCK |
1da177e4 LT |
1263 | help |
1264 | This is the file system used by the real-time operating systems | |
1265 | QNX 4 and QNX 6 (the latter is also called QNX RTP). | |
1266 | Further information is available at <http://www.qnx.com/>. | |
1267 | Say Y if you intend to mount QNX hard disks or floppies. | |
1268 | Unless you say Y to "QNX4FS read-write support" below, you will | |
1269 | only be able to read these file systems. | |
1270 | ||
1271 | To compile this file system support as a module, choose M here: the | |
1272 | module will be called qnx4. | |
1273 | ||
1274 | If you don't know whether you need it, then you don't need it: | |
1275 | answer N. | |
1276 | ||
1277 | config QNX4FS_RW | |
1278 | bool "QNX4FS write support (DANGEROUS)" | |
1279 | depends on QNX4FS_FS && EXPERIMENTAL && BROKEN | |
1280 | help | |
1281 | Say Y if you want to test write support for QNX4 file systems. | |
1282 | ||
1283 | It's currently broken, so for now: | |
1284 | answer N. | |
1285 | ||
25fad945 RD |
1286 | config ROMFS_FS |
1287 | tristate "ROM file system support" | |
1288 | depends on BLOCK | |
1289 | ---help--- | |
1290 | This is a very small read-only file system mainly intended for | |
1291 | initial ram disks of installation disks, but it could be used for | |
1292 | other read-only media as well. Read | |
1293 | <file:Documentation/filesystems/romfs.txt> for details. | |
1294 | ||
1295 | To compile this file system support as a module, choose M here: the | |
1296 | module will be called romfs. Note that the file system of your | |
1297 | root partition (the one containing the directory /) cannot be a | |
1298 | module. | |
1299 | ||
1300 | If you don't know whether you need it, then you don't need it: | |
1301 | answer N. | |
1da177e4 LT |
1302 | |
1303 | ||
1304 | config SYSV_FS | |
1305 | tristate "System V/Xenix/V7/Coherent file system support" | |
9361401e | 1306 | depends on BLOCK |
1da177e4 LT |
1307 | help |
1308 | SCO, Xenix and Coherent are commercial Unix systems for Intel | |
1309 | machines, and Version 7 was used on the DEC PDP-11. Saying Y | |
1310 | here would allow you to read from their floppies and hard disk | |
1311 | partitions. | |
1312 | ||
1313 | If you have floppies or hard disk partitions like that, it is likely | |
1314 | that they contain binaries from those other Unix systems; in order | |
cab00891 | 1315 | to run these binaries, you will want to install linux-abi which is |
1da177e4 LT |
1316 | a set of kernel modules that lets you run SCO, Xenix, Wyse, |
1317 | UnixWare, Dell Unix and System V programs under Linux. It is | |
1318 | available via FTP (user: ftp) from | |
1319 | <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>). | |
1320 | NOTE: that will work only for binaries from Intel-based systems; | |
1321 | PDP ones will have to wait until somebody ports Linux to -11 ;-) | |
1322 | ||
1323 | If you only intend to mount files from some other Unix over the | |
1324 | network using NFS, you don't need the System V file system support | |
1325 | (but you need NFS file system support obviously). | |
1326 | ||
1327 | Note that this option is generally not needed for floppies, since a | |
1328 | good portable way to transport files and directories between unixes | |
1329 | (and even other operating systems) is given by the tar program ("man | |
1330 | tar" or preferably "info tar"). Note also that this option has | |
1331 | nothing whatsoever to do with the option "System V IPC". Read about | |
1332 | the System V file system in | |
1333 | <file:Documentation/filesystems/sysv-fs.txt>. | |
1334 | Saying Y here will enlarge your kernel by about 27 KB. | |
1335 | ||
1336 | To compile this as a module, choose M here: the module will be called | |
1337 | sysv. | |
1338 | ||
1339 | If you haven't heard about all of this before, it's safe to say N. | |
1340 | ||
1341 | ||
1da177e4 LT |
1342 | config UFS_FS |
1343 | tristate "UFS file system support (read only)" | |
9361401e | 1344 | depends on BLOCK |
1da177e4 LT |
1345 | help |
1346 | BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD, | |
1347 | OpenBSD and NeXTstep) use a file system called UFS. Some System V | |
1348 | Unixes can create and mount hard disk partitions and diskettes using | |
1349 | this file system as well. Saying Y here will allow you to read from | |
1350 | these partitions; if you also want to write to them, say Y to the | |
1351 | experimental "UFS file system write support", below. Please read the | |
1352 | file <file:Documentation/filesystems/ufs.txt> for more information. | |
1353 | ||
1354 | The recently released UFS2 variant (used in FreeBSD 5.x) is | |
1355 | READ-ONLY supported. | |
1356 | ||
1da177e4 LT |
1357 | Note that this option is generally not needed for floppies, since a |
1358 | good portable way to transport files and directories between unixes | |
1359 | (and even other operating systems) is given by the tar program ("man | |
1360 | tar" or preferably "info tar"). | |
1361 | ||
1362 | When accessing NeXTstep files, you may need to convert them from the | |
1363 | NeXT character set to the Latin1 character set; use the program | |
1364 | recode ("info recode") for this purpose. | |
1365 | ||
1366 | To compile the UFS file system support as a module, choose M here: the | |
1367 | module will be called ufs. | |
1368 | ||
1369 | If you haven't heard about all of this before, it's safe to say N. | |
1370 | ||
1371 | config UFS_FS_WRITE | |
1372 | bool "UFS file system write support (DANGEROUS)" | |
5afb3145 | 1373 | depends on UFS_FS && EXPERIMENTAL |
1da177e4 LT |
1374 | help |
1375 | Say Y here if you want to try writing to UFS partitions. This is | |
1376 | experimental, so you should back up your UFS partitions beforehand. | |
1377 | ||
abf5d15f ED |
1378 | config UFS_DEBUG |
1379 | bool "UFS debugging" | |
1380 | depends on UFS_FS | |
1381 | help | |
1382 | If you are experiencing any problems with the UFS filesystem, say | |
1383 | Y here. This will result in _many_ additional debugging messages to be | |
1384 | written to the system log. | |
1385 | ||
1da177e4 LT |
1386 | endmenu |
1387 | ||
ea0985ad JE |
1388 | menuconfig NETWORK_FILESYSTEMS |
1389 | bool "Network File Systems" | |
1390 | default y | |
1da177e4 | 1391 | depends on NET |
ea0985ad JE |
1392 | ---help--- |
1393 | Say Y here to get to see options for network filesystems and | |
1394 | filesystem-related networking code, such as NFS daemon and | |
1395 | RPCSEC security modules. | |
6fb1bc10 | 1396 | |
ea0985ad JE |
1397 | This option alone does not add any kernel code. |
1398 | ||
1399 | If you say N, all options in this submenu will be skipped and | |
1400 | disabled; if unsure, say Y here. | |
1401 | ||
1402 | if NETWORK_FILESYSTEMS | |
1da177e4 LT |
1403 | |
1404 | config NFS_FS | |
6fb1bc10 | 1405 | tristate "NFS client support" |
1da177e4 LT |
1406 | depends on INET |
1407 | select LOCKD | |
1408 | select SUNRPC | |
b7fa0554 | 1409 | select NFS_ACL_SUPPORT if NFS_V3_ACL |
1da177e4 | 1410 | help |
6fb1bc10 CL |
1411 | Choose Y here if you want to access files residing on other |
1412 | computers using Sun's Network File System protocol. To compile | |
1413 | this file system support as a module, choose M here: the module | |
1414 | will be called nfs. | |
1da177e4 | 1415 | |
6fb1bc10 CL |
1416 | To mount file systems exported by NFS servers, you also need to |
1417 | install the user space mount.nfs command which can be found in | |
1418 | the Linux nfs-utils package, available from http://linux-nfs.org/. | |
1419 | Information about using the mount command is available in the | |
1420 | mount(8) man page. More detail about the Linux NFS client | |
1421 | implementation is available via the nfs(5) man page. | |
1da177e4 | 1422 | |
6fb1bc10 CL |
1423 | Below you can choose which versions of the NFS protocol are |
1424 | available in the kernel to mount NFS servers. Support for NFS | |
1425 | version 2 (RFC 1094) is always available when NFS_FS is selected. | |
1da177e4 | 1426 | |
6fb1bc10 CL |
1427 | To configure a system which mounts its root file system via NFS |
1428 | at boot time, say Y here, select "Kernel level IP | |
1429 | autoconfiguration" in the NETWORK menu, and select "Root file | |
1430 | system on NFS" below. You cannot compile this file system as a | |
1431 | module in this case. | |
1da177e4 | 1432 | |
6fb1bc10 | 1433 | If unsure, say N. |
1da177e4 LT |
1434 | |
1435 | config NFS_V3 | |
6fb1bc10 | 1436 | bool "NFS client support for NFS version 3" |
1da177e4 LT |
1437 | depends on NFS_FS |
1438 | help | |
6fb1bc10 CL |
1439 | This option enables support for version 3 of the NFS protocol |
1440 | (RFC 1813) in the kernel's NFS client. | |
1da177e4 LT |
1441 | |
1442 | If unsure, say Y. | |
1443 | ||
b7fa0554 | 1444 | config NFS_V3_ACL |
6fb1bc10 | 1445 | bool "NFS client support for the NFSv3 ACL protocol extension" |
b7fa0554 AG |
1446 | depends on NFS_V3 |
1447 | help | |
6fb1bc10 CL |
1448 | Some NFS servers support an auxiliary NFSv3 ACL protocol that |
1449 | Sun added to Solaris but never became an official part of the | |
1450 | NFS version 3 protocol. This protocol extension allows | |
1451 | applications on NFS clients to manipulate POSIX Access Control | |
1452 | Lists on files residing on NFS servers. NFS servers enforce | |
1453 | ACLs on local files whether this protocol is available or not. | |
1454 | ||
1455 | Choose Y here if your NFS server supports the Solaris NFSv3 ACL | |
1456 | protocol extension and you want your NFS client to allow | |
1457 | applications to access and modify ACLs on files on the server. | |
1458 | ||
1459 | Most NFS servers don't support the Solaris NFSv3 ACL protocol | |
1460 | extension. You can choose N here or specify the "noacl" mount | |
1461 | option to prevent your NFS client from trying to use the NFSv3 | |
1462 | ACL protocol. | |
b7fa0554 AG |
1463 | |
1464 | If unsure, say N. | |
1465 | ||
1da177e4 | 1466 | config NFS_V4 |
6fb1bc10 | 1467 | bool "NFS client support for NFS version 4 (EXPERIMENTAL)" |
1da177e4 LT |
1468 | depends on NFS_FS && EXPERIMENTAL |
1469 | select RPCSEC_GSS_KRB5 | |
1470 | help | |
6fb1bc10 CL |
1471 | This option enables support for version 4 of the NFS protocol |
1472 | (RFC 3530) in the kernel's NFS client. | |
1da177e4 | 1473 | |
6fb1bc10 CL |
1474 | To mount NFS servers using NFSv4, you also need to install user |
1475 | space programs which can be found in the Linux nfs-utils package, | |
1476 | available from http://linux-nfs.org/. | |
1da177e4 LT |
1477 | |
1478 | If unsure, say N. | |
1479 | ||
6fb1bc10 CL |
1480 | config ROOT_NFS |
1481 | bool "Root file system on NFS" | |
1482 | depends on NFS_FS=y && IP_PNP | |
1483 | help | |
1484 | If you want your system to mount its root file system via NFS, | |
1485 | choose Y here. This is common practice for managing systems | |
1486 | without local permanent storage. For details, read | |
1487 | <file:Documentation/filesystems/nfsroot.txt>. | |
1488 | ||
1489 | Most people say N here. | |
1490 | ||
1da177e4 LT |
1491 | config NFSD |
1492 | tristate "NFS server support" | |
1493 | depends on INET | |
1494 | select LOCKD | |
1495 | select SUNRPC | |
1496 | select EXPORTFS | |
f05e15b5 | 1497 | select NFS_ACL_SUPPORT if NFSD_V2_ACL |
1da177e4 | 1498 | help |
d24455b5 CL |
1499 | Choose Y here if you want to allow other computers to access |
1500 | files residing on this system using Sun's Network File System | |
1501 | protocol. To compile the NFS server support as a module, | |
1502 | choose M here: the module will be called nfsd. | |
1da177e4 | 1503 | |
d24455b5 CL |
1504 | You may choose to use a user-space NFS server instead, in which |
1505 | case you can choose N here. | |
1da177e4 | 1506 | |
d24455b5 CL |
1507 | To export local file systems using NFS, you also need to install |
1508 | user space programs which can be found in the Linux nfs-utils | |
1509 | package, available from http://linux-nfs.org/. More detail about | |
1510 | the Linux NFS server implementation is available via the | |
1511 | exports(5) man page. | |
1da177e4 | 1512 | |
d24455b5 CL |
1513 | Below you can choose which versions of the NFS protocol are |
1514 | available to clients mounting the NFS server on this system. | |
1515 | Support for NFS version 2 (RFC 1094) is always available when | |
1516 | CONFIG_NFSD is selected. | |
1da177e4 | 1517 | |
d24455b5 | 1518 | If unsure, say N. |
1da177e4 | 1519 | |
a257cdd0 AG |
1520 | config NFSD_V2_ACL |
1521 | bool | |
1522 | depends on NFSD | |
1523 | ||
1da177e4 | 1524 | config NFSD_V3 |
d24455b5 | 1525 | bool "NFS server support for NFS version 3" |
1da177e4 LT |
1526 | depends on NFSD |
1527 | help | |
d24455b5 CL |
1528 | This option enables support in your system's NFS server for |
1529 | version 3 of the NFS protocol (RFC 1813). | |
1530 | ||
1531 | If unsure, say Y. | |
1da177e4 | 1532 | |
a257cdd0 | 1533 | config NFSD_V3_ACL |
d24455b5 | 1534 | bool "NFS server support for the NFSv3 ACL protocol extension" |
a257cdd0 | 1535 | depends on NFSD_V3 |
78dd0992 | 1536 | select NFSD_V2_ACL |
a257cdd0 | 1537 | help |
d24455b5 CL |
1538 | Solaris NFS servers support an auxiliary NFSv3 ACL protocol that |
1539 | never became an official part of the NFS version 3 protocol. | |
1540 | This protocol extension allows applications on NFS clients to | |
1541 | manipulate POSIX Access Control Lists on files residing on NFS | |
1542 | servers. NFS servers enforce POSIX ACLs on local files whether | |
1543 | this protocol is available or not. | |
1544 | ||
1545 | This option enables support in your system's NFS server for the | |
1546 | NFSv3 ACL protocol extension allowing NFS clients to manipulate | |
1547 | POSIX ACLs on files exported by your system's NFS server. NFS | |
1548 | clients which support the Solaris NFSv3 ACL protocol can then | |
1549 | access and modify ACLs on your NFS server. | |
1550 | ||
1551 | To store ACLs on your NFS server, you also need to enable ACL- | |
1552 | related CONFIG options for your local file systems of choice. | |
1553 | ||
1554 | If unsure, say N. | |
a257cdd0 | 1555 | |
1da177e4 | 1556 | config NFSD_V4 |
d24455b5 | 1557 | bool "NFS server support for NFS version 4 (EXPERIMENTAL)" |
1a448fdb CL |
1558 | depends on NFSD && PROC_FS && EXPERIMENTAL |
1559 | select NFSD_V3 | |
89206955 | 1560 | select FS_POSIX_ACL |
42ed95c4 | 1561 | select RPCSEC_GSS_KRB5 |
1da177e4 | 1562 | help |
d24455b5 CL |
1563 | This option enables support in your system's NFS server for |
1564 | version 4 of the NFS protocol (RFC 3530). | |
1565 | ||
1566 | To export files using NFSv4, you need to install additional user | |
1567 | space programs which can be found in the Linux nfs-utils package, | |
1568 | available from http://linux-nfs.org/. | |
1569 | ||
1da177e4 LT |
1570 | If unsure, say N. |
1571 | ||
1da177e4 LT |
1572 | config LOCKD |
1573 | tristate | |
1574 | ||
1575 | config LOCKD_V4 | |
1576 | bool | |
1577 | depends on NFSD_V3 || NFS_V3 | |
1578 | default y | |
1579 | ||
1580 | config EXPORTFS | |
1581 | tristate | |
1582 | ||
a257cdd0 AG |
1583 | config NFS_ACL_SUPPORT |
1584 | tristate | |
1585 | select FS_POSIX_ACL | |
1586 | ||
1587 | config NFS_COMMON | |
1588 | bool | |
1589 | depends on NFSD || NFS_FS | |
1590 | default y | |
1591 | ||
1da177e4 LT |
1592 | config SUNRPC |
1593 | tristate | |
1594 | ||
1595 | config SUNRPC_GSS | |
1596 | tristate | |
1597 | ||
c3a57ed7 | 1598 | config SUNRPC_XPRT_RDMA |
3211e4eb | 1599 | tristate |
113632d0 | 1600 | depends on SUNRPC && INFINIBAND && EXPERIMENTAL |
3211e4eb | 1601 | default SUNRPC && INFINIBAND |
327a299d CL |
1602 | help |
1603 | This option enables an RPC client transport capability that | |
1604 | allows the NFS client to mount servers via an RDMA-enabled | |
1605 | transport. | |
1606 | ||
1607 | To compile RPC client RDMA transport support as a module, | |
1608 | choose M here: the module will be called xprtrdma. | |
1609 | ||
1610 | If unsure, say N. | |
c3a57ed7 | 1611 | |
a26cfad6 CL |
1612 | config SUNRPC_REGISTER_V4 |
1613 | bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)" | |
1614 | depends on SUNRPC && EXPERIMENTAL | |
1615 | default n | |
1616 | help | |
1617 | Sun added support for registering RPC services at an IPv6 | |
1618 | address by creating two new versions of the rpcbind protocol | |
1619 | (RFC 1833). | |
1620 | ||
1621 | This option enables support in the kernel RPC server for | |
1622 | registering kernel RPC services via version 4 of the rpcbind | |
1623 | protocol. If you enable this option, you must run a portmapper | |
1624 | daemon that supports rpcbind protocol version 4. | |
1625 | ||
1626 | Serving NFS over IPv6 from knfsd (the kernel's NFS server) | |
1627 | requires that you enable this option and use a portmapper that | |
1628 | supports rpcbind version 4. | |
1629 | ||
1630 | If unsure, say N to get traditional behavior (register kernel | |
1631 | RPC services using only rpcbind version 2). Distributions | |
1632 | using the legacy Linux portmapper daemon must say N here. | |
1633 | ||
1da177e4 LT |
1634 | config RPCSEC_GSS_KRB5 |
1635 | tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)" | |
1636 | depends on SUNRPC && EXPERIMENTAL | |
1637 | select SUNRPC_GSS | |
1638 | select CRYPTO | |
1639 | select CRYPTO_MD5 | |
1640 | select CRYPTO_DES | |
bcbaecbb | 1641 | select CRYPTO_CBC |
1da177e4 | 1642 | help |
327a299d CL |
1643 | Choose Y here to enable Secure RPC using the Kerberos version 5 |
1644 | GSS-API mechanism (RFC 1964). | |
1da177e4 | 1645 | |
327a299d CL |
1646 | Secure RPC calls with Kerberos require an auxiliary user-space |
1647 | daemon which may be found in the Linux nfs-utils package | |
1648 | available from http://linux-nfs.org/. In addition, user-space | |
1649 | Kerberos support should be installed. | |
1da177e4 LT |
1650 | |
1651 | If unsure, say N. | |
1652 | ||
1653 | config RPCSEC_GSS_SPKM3 | |
1654 | tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)" | |
1655 | depends on SUNRPC && EXPERIMENTAL | |
1656 | select SUNRPC_GSS | |
1657 | select CRYPTO | |
1658 | select CRYPTO_MD5 | |
1659 | select CRYPTO_DES | |
df6db302 | 1660 | select CRYPTO_CAST5 |
bcbaecbb | 1661 | select CRYPTO_CBC |
1da177e4 | 1662 | help |
327a299d CL |
1663 | Choose Y here to enable Secure RPC using the SPKM3 public key |
1664 | GSS-API mechansim (RFC 2025). | |
1da177e4 | 1665 | |
327a299d CL |
1666 | Secure RPC calls with SPKM3 require an auxiliary userspace |
1667 | daemon which may be found in the Linux nfs-utils package | |
1668 | available from http://linux-nfs.org/. | |
1da177e4 LT |
1669 | |
1670 | If unsure, say N. | |
1671 | ||
1672 | config SMB_FS | |
c7736339 | 1673 | tristate "SMB file system support (OBSOLETE, please use CIFS)" |
1da177e4 LT |
1674 | depends on INET |
1675 | select NLS | |
1676 | help | |
1677 | SMB (Server Message Block) is the protocol Windows for Workgroups | |
1678 | (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share | |
1679 | files and printers over local networks. Saying Y here allows you to | |
1680 | mount their file systems (often called "shares" in this context) and | |
1681 | access them just like any other Unix directory. Currently, this | |
1682 | works only if the Windows machines use TCP/IP as the underlying | |
1683 | transport protocol, and not NetBEUI. For details, read | |
1684 | <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO, | |
1685 | available from <http://www.tldp.org/docs.html#howto>. | |
1686 | ||
1687 | Note: if you just want your box to act as an SMB *server* and make | |
1688 | files and printing services available to Windows clients (which need | |
1689 | to have a TCP/IP stack), you don't need to say Y here; you can use | |
1690 | the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>) | |
1691 | for that. | |
1692 | ||
1693 | General information about how to connect Linux, Windows machines and | |
1694 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1695 | ||
c7736339 AM |
1696 | To compile the SMB support as a module, choose M here: |
1697 | the module will be called smbfs. Most people say N, however. | |
1da177e4 LT |
1698 | |
1699 | config SMB_NLS_DEFAULT | |
1700 | bool "Use a default NLS" | |
1701 | depends on SMB_FS | |
1702 | help | |
1703 | Enabling this will make smbfs use nls translations by default. You | |
1704 | need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls | |
1705 | settings and you need to give the default nls for the SMB server as | |
1706 | CONFIG_SMB_NLS_REMOTE. | |
1707 | ||
1708 | The nls settings can be changed at mount time, if your smbmount | |
1709 | supports that, using the codepage and iocharset parameters. | |
1710 | ||
1711 | smbmount from samba 2.2.0 or later supports this. | |
1712 | ||
1713 | config SMB_NLS_REMOTE | |
1714 | string "Default Remote NLS Option" | |
1715 | depends on SMB_NLS_DEFAULT | |
1716 | default "cp437" | |
1717 | help | |
1718 | This setting allows you to specify a default value for which | |
1719 | codepage the server uses. If this field is left blank no | |
1720 | translations will be done by default. The local codepage/charset | |
1721 | default to CONFIG_NLS_DEFAULT. | |
1722 | ||
1723 | The nls settings can be changed at mount time, if your smbmount | |
1724 | supports that, using the codepage and iocharset parameters. | |
1725 | ||
1726 | smbmount from samba 2.2.0 or later supports this. | |
1727 | ||
bb26b963 | 1728 | source "fs/cifs/Kconfig" |
6103335d | 1729 | |
1da177e4 LT |
1730 | config NCP_FS |
1731 | tristate "NCP file system support (to mount NetWare volumes)" | |
1732 | depends on IPX!=n || INET | |
1733 | help | |
1734 | NCP (NetWare Core Protocol) is a protocol that runs over IPX and is | |
1735 | used by Novell NetWare clients to talk to file servers. It is to | |
1736 | IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you | |
1737 | to mount NetWare file server volumes and to access them just like | |
1738 | any other Unix directory. For details, please read the file | |
1739 | <file:Documentation/filesystems/ncpfs.txt> in the kernel source and | |
1740 | the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>. | |
1741 | ||
1742 | You do not have to say Y here if you want your Linux box to act as a | |
1743 | file *server* for Novell NetWare clients. | |
1744 | ||
1745 | General information about how to connect Linux, Windows machines and | |
1746 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1747 | ||
1748 | To compile this as a module, choose M here: the module will be called | |
1749 | ncpfs. Say N unless you are connected to a Novell network. | |
1750 | ||
1751 | source "fs/ncpfs/Kconfig" | |
1752 | ||
1753 | config CODA_FS | |
1754 | tristate "Coda file system support (advanced network fs)" | |
1755 | depends on INET | |
1756 | help | |
1757 | Coda is an advanced network file system, similar to NFS in that it | |
1758 | enables you to mount file systems of a remote server and access them | |
1759 | with regular Unix commands as if they were sitting on your hard | |
1760 | disk. Coda has several advantages over NFS: support for | |
1761 | disconnected operation (e.g. for laptops), read/write server | |
1762 | replication, security model for authentication and encryption, | |
1763 | persistent client caches and write back caching. | |
1764 | ||
1765 | If you say Y here, your Linux box will be able to act as a Coda | |
1766 | *client*. You will need user level code as well, both for the | |
1767 | client and server. Servers are currently user level, i.e. they need | |
1768 | no kernel support. Please read | |
1769 | <file:Documentation/filesystems/coda.txt> and check out the Coda | |
1770 | home page <http://www.coda.cs.cmu.edu/>. | |
1771 | ||
1772 | To compile the coda client support as a module, choose M here: the | |
1773 | module will be called coda. | |
1774 | ||
1da177e4 | 1775 | config AFS_FS |
64aaa4f8 | 1776 | tristate "Andrew File System support (AFS) (EXPERIMENTAL)" |
1da177e4 | 1777 | depends on INET && EXPERIMENTAL |
08e0e7c8 | 1778 | select AF_RXRPC |
1da177e4 LT |
1779 | help |
1780 | If you say Y here, you will get an experimental Andrew File System | |
1781 | driver. It currently only supports unsecured read-only AFS access. | |
1782 | ||
cc2e2767 | 1783 | See <file:Documentation/filesystems/afs.txt> for more information. |
1da177e4 LT |
1784 | |
1785 | If unsure, say N. | |
1786 | ||
08e0e7c8 DH |
1787 | config AFS_DEBUG |
1788 | bool "AFS dynamic debugging" | |
1789 | depends on AFS_FS | |
1790 | help | |
1791 | Say Y here to make runtime controllable debugging messages appear. | |
1792 | ||
1793 | See <file:Documentation/filesystems/afs.txt> for more information. | |
1794 | ||
1795 | If unsure, say N. | |
1796 | ||
93fa58cb EVH |
1797 | config 9P_FS |
1798 | tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)" | |
bd238fb4 | 1799 | depends on INET && NET_9P && EXPERIMENTAL |
93fa58cb EVH |
1800 | help |
1801 | If you say Y here, you will get experimental support for | |
1802 | Plan 9 resource sharing via the 9P2000 protocol. | |
1803 | ||
1804 | See <http://v9fs.sf.net> for more information. | |
1805 | ||
1806 | If unsure, say N. | |
1807 | ||
ea0985ad | 1808 | endif # NETWORK_FILESYSTEMS |
1da177e4 | 1809 | |
9361401e | 1810 | if BLOCK |
1da177e4 LT |
1811 | menu "Partition Types" |
1812 | ||
1813 | source "fs/partitions/Kconfig" | |
1814 | ||
1815 | endmenu | |
9361401e | 1816 | endif |
1da177e4 LT |
1817 | |
1818 | source "fs/nls/Kconfig" | |
e7fd4179 | 1819 | source "fs/dlm/Kconfig" |
1da177e4 LT |
1820 | |
1821 | endmenu |