diff options
Diffstat (limited to 'fs/Kconfig')
| -rw-r--r-- | fs/Kconfig | 65 |
1 files changed, 9 insertions, 56 deletions
diff --git a/fs/Kconfig b/fs/Kconfig index e786b380e5aa..74cc991e6c03 100644 --- a/fs/Kconfig +++ b/fs/Kconfig @@ -251,7 +251,7 @@ config JBD2 config JBD2_DEBUG bool "JBD2 (ext4dev/ext4) debugging support" - depends on JBD2 + depends on JBD2 && DEBUG_FS help If you are using the ext4dev/ext4 journaled file system (or potentially any other filesystem/device using JBD2), this option @@ -260,10 +260,10 @@ config JBD2_DEBUG By default, the debugging output will be turned off. If you select Y here, then you will be able to turn on debugging - with "echo N > /proc/sys/fs/jbd2-debug", where N is a number between - 1 and 5. The higher the number, the more debugging output is - generated. To turn debugging off again, do - "echo 0 > /proc/sys/fs/jbd2-debug". + with "echo N > /sys/kernel/debug/jbd2/jbd2-debug", where N is a + number between 1 and 5. The higher the number, the more debugging + output is generated. To turn debugging off again, do + "echo 0 > /sys/kernel/debug/jbd2/jbd2-debug". config FS_MBCACHE # Meta block cache for Extended Attributes (ext2/ext3/ext4) @@ -441,9 +441,6 @@ config OCFS2_FS Note: Features which OCFS2 does not support yet: - extended attributes - - shared writeable mmap - - loopback is supported, but data written will not - be cluster coherent. - quotas - cluster aware flock - Directory change notification (F_NOTIFY) @@ -991,7 +988,7 @@ config TMPFS_POSIX_ACL config HUGETLBFS bool "HugeTLB file system support" - depends on X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN + depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || BROKEN help hugetlbfs is a filesystem backing for HugeTLB pages, based on ramfs. For architectures that support it, say Y here and read @@ -1371,51 +1368,6 @@ config CRAMFS If unsure, say N. -config CRAMFS_LINEAR - bool "Use linear addressing for CramFs" - depends on CRAMFS - help - This option tells the CramFs driver to load data directly from - a linear adressed memory range (usually non volatile memory - like flash) instead of going through the block device layer. - This saves some memory since no intermediate buffering is - necessary. - - This is also a prerequisite for XIP of binaries stored on the - filesystem. - - The location of the CramFs image in memory is board - dependent. Therefore, if you say Y, you must know the proper - physical address where to store the CramFs image and specify - it using the physaddr=0x******** mount option (for example: - "mount -t cramfs -o physaddr=0x100000 none /mnt"). - - If unsure, say N. - -config CRAMFS_LINEAR_XIP - bool "Support XIP on linear CramFs" - depends on CRAMFS_LINEAR - help - You must say Y to this option if you want to be able to run - applications directly from non-volatile memory. XIP - applications are marked by setting the sticky bit (ie, "chmod - +t <app name>"). A cramfs file system then needs to be - created using mkcramfs (with XIP cramfs support in - it). Applications marked for XIP execution will not be - compressed since they have to run directly from flash. - -config ROOT_CRAMFS_LINEAR - bool "Root file system on linear CramFs" - depends on CRAMFS_LINEAR - help - Say Y if you have enabled linear CramFs, and you want to be - able to use the linear CramFs image as a root file system. To - actually have the kernel mount this CramFs image as a root - file system, you must also pass the command line parameter - "root=/dev/null rootflags=physaddr=0x********" to the kernel - (replace 0x******** with the physical address location of the - linear CramFs image to boot with). - config VXFS_FS tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)" depends on BLOCK @@ -1723,7 +1675,8 @@ config NFSD_V3_ACL config NFSD_V4 bool "Provide NFSv4 server support (EXPERIMENTAL)" - depends on NFSD_V3 && EXPERIMENTAL + depends on NFSD && NFSD_V3 && EXPERIMENTAL + select RPCSEC_GSS_KRB5 help If you would like to include the NFSv4 server as well as the NFSv2 and NFSv3 servers, say Y here. This feature is experimental, and @@ -2097,7 +2050,7 @@ config AFS_DEBUG config 9P_FS tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)" - depends on INET && EXPERIMENTAL + depends on INET && NET_9P && EXPERIMENTAL help If you say Y here, you will get experimental support for Plan 9 resource sharing via the 9P2000 protocol. |