2005-04-17 06:20:36 +08:00
|
|
|
#
|
|
|
|
|
# File system configuration
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
menu "File systems"
|
|
|
|
|
|
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2006-10-01 02:45:40 +08:00
|
|
|
if BLOCK
|
|
|
|
|
|
2008-10-21 02:28:45 +08:00
|
|
|
source "fs/ext2/Kconfig"
|
|
|
|
|
source "fs/ext3/Kconfig"
|
|
|
|
|
source "fs/ext4/Kconfig"
|
2005-06-24 13:05:26 +08:00
|
|
|
|
|
|
|
|
config FS_XIP
|
|
|
|
|
# execute in place
|
|
|
|
|
bool
|
|
|
|
|
depends on EXT2_FS_XIP
|
|
|
|
|
default y
|
|
|
|
|
|
2008-10-21 02:28:45 +08:00
|
|
|
source "fs/jbd/Kconfig"
|
|
|
|
|
source "fs/jbd2/Kconfig"
|
2006-10-11 16:21:01 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config FS_MBCACHE
|
2006-10-11 16:20:56 +08:00
|
|
|
# Meta block cache for Extended Attributes (ext2/ext3/ext4)
|
2005-04-17 06:20:36 +08:00
|
|
|
tristate
|
2008-08-21 07:56:22 +08:00
|
|
|
default y if EXT2_FS=y && EXT2_FS_XATTR
|
|
|
|
|
default y if EXT3_FS=y && EXT3_FS_XATTR
|
|
|
|
|
default y if EXT4_FS=y && EXT4_FS_XATTR
|
|
|
|
|
default m if EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-01-22 15:22:31 +08:00
|
|
|
source "fs/reiserfs/Kconfig"
|
2009-01-22 15:24:27 +08:00
|
|
|
source "fs/jfs/Kconfig"
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config FS_POSIX_ACL
|
2008-02-12 06:12:24 +08:00
|
|
|
# Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
|
2005-04-17 06:20:36 +08:00
|
|
|
#
|
|
|
|
|
# NOTE: you can implement Posix ACLs without these helpers (XFS does).
|
|
|
|
|
# Never use this symbol for ifdefs.
|
|
|
|
|
#
|
|
|
|
|
bool
|
2005-07-08 08:56:57 +08:00
|
|
|
default n
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-08-06 21:12:22 +08:00
|
|
|
config FILE_LOCKING
|
|
|
|
|
bool "Enable POSIX file locking API" if EMBEDDED
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This option enables standard file locking support, required
|
|
|
|
|
for filesystems like NFS and for the flock() system
|
|
|
|
|
call. Disabling this option saves about 11k.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
source "fs/xfs/Kconfig"
|
2006-01-17 00:43:37 +08:00
|
|
|
source "fs/gfs2/Kconfig"
|
2009-01-22 15:26:11 +08:00
|
|
|
source "fs/ocfs2/Kconfig"
|
2009-01-22 15:27:30 +08:00
|
|
|
source "fs/btrfs/Kconfig"
|
2008-09-26 00:25:16 +08:00
|
|
|
|
2008-02-07 16:15:16 +08:00
|
|
|
endif # BLOCK
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-12-18 02:59:41 +08:00
|
|
|
source "fs/notify/Kconfig"
|
[PATCH] inotify
inotify is intended to correct the deficiencies of dnotify, particularly
its inability to scale and its terrible user interface:
* dnotify requires the opening of one fd per each directory
that you intend to watch. This quickly results in too many
open files and pins removable media, preventing unmount.
* dnotify is directory-based. You only learn about changes to
directories. Sure, a change to a file in a directory affects
the directory, but you are then forced to keep a cache of
stat structures.
* dnotify's interface to user-space is awful. Signals?
inotify provides a more usable, simple, powerful solution to file change
notification:
* inotify's interface is a system call that returns a fd, not SIGIO.
You get a single fd, which is select()-able.
* inotify has an event that says "the filesystem that the item
you were watching is on was unmounted."
* inotify can watch directories or files.
Inotify is currently used by Beagle (a desktop search infrastructure),
Gamin (a FAM replacement), and other projects.
See Documentation/filesystems/inotify.txt.
Signed-off-by: Robert Love <rml@novell.com>
Cc: John McCutchan <ttb@tentacle.dhs.org>
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-07-13 05:06:03 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config QUOTA
|
|
|
|
|
bool "Quota support"
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, you will be able to set per user limits for disk
|
|
|
|
|
usage (also called disk quotas). Currently, it works for the
|
|
|
|
|
ext2, ext3, and reiserfs file system. ext3 also supports journalled
|
|
|
|
|
quotas for which you don't need to run quotacheck(8) after an unclean
|
2005-09-07 06:17:22 +08:00
|
|
|
shutdown.
|
|
|
|
|
For further details, read the Quota mini-HOWTO, available from
|
2005-04-17 06:20:36 +08:00
|
|
|
<http://www.tldp.org/docs.html#howto>, or the documentation provided
|
|
|
|
|
with the quota tools. Probably the quota support is only useful for
|
|
|
|
|
multi user systems. If unsure, say N.
|
|
|
|
|
|
2007-10-17 14:29:31 +08:00
|
|
|
config QUOTA_NETLINK_INTERFACE
|
|
|
|
|
bool "Report quota messages through netlink interface"
|
|
|
|
|
depends on QUOTA && NET
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, quota warnings (about exceeding softlimit, reaching
|
|
|
|
|
hardlimit, etc.) will be reported through netlink interface. If unsure,
|
|
|
|
|
say Y.
|
|
|
|
|
|
|
|
|
|
config PRINT_QUOTA_WARNING
|
|
|
|
|
bool "Print quota warnings to console (OBSOLETE)"
|
|
|
|
|
depends on QUOTA
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, quota warnings (about exceeding softlimit, reaching
|
|
|
|
|
hardlimit, etc.) will be printed to the process' controlling terminal.
|
|
|
|
|
Note that this behavior is currently deprecated and may go away in
|
|
|
|
|
future. Please use notification via netlink socket instead.
|
|
|
|
|
|
2008-09-22 11:54:49 +08:00
|
|
|
# Generic support for tree structured quota files. Seleted when needed.
|
|
|
|
|
config QUOTA_TREE
|
|
|
|
|
tristate
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config QFMT_V1
|
|
|
|
|
tristate "Old quota format support"
|
|
|
|
|
depends on QUOTA
|
|
|
|
|
help
|
|
|
|
|
This quota format was (is) used by kernels earlier than 2.4.22. If
|
|
|
|
|
you have quota working and you don't want to convert to new quota
|
|
|
|
|
format say Y here.
|
|
|
|
|
|
|
|
|
|
config QFMT_V2
|
|
|
|
|
tristate "Quota format v2 support"
|
|
|
|
|
depends on QUOTA
|
2008-09-22 11:54:49 +08:00
|
|
|
select QUOTA_TREE
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
This quota format allows using quotas with 32-bit UIDs/GIDs. If you
|
2005-09-07 06:17:22 +08:00
|
|
|
need this functionality say Y here.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config QUOTACTL
|
|
|
|
|
bool
|
|
|
|
|
depends on XFS_QUOTA || QUOTA
|
|
|
|
|
default y
|
|
|
|
|
|
2009-01-22 15:31:56 +08:00
|
|
|
source "fs/autofs/Kconfig"
|
|
|
|
|
source "fs/autofs4/Kconfig"
|
2009-01-22 15:33:25 +08:00
|
|
|
source "fs/fuse/Kconfig"
|
2005-09-10 04:10:22 +08:00
|
|
|
|
2006-10-20 14:28:35 +08:00
|
|
|
config GENERIC_ACL
|
|
|
|
|
bool
|
|
|
|
|
select FS_POSIX_ACL
|
|
|
|
|
|
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2006-10-01 02:45:40 +08:00
|
|
|
if BLOCK
|
2005-04-17 06:20:36 +08:00
|
|
|
menu "CD-ROM/DVD Filesystems"
|
|
|
|
|
|
2009-01-22 15:35:21 +08:00
|
|
|
source "fs/isofs/Kconfig"
|
|
|
|
|
source "fs/udf/Kconfig"
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
endmenu
|
2008-02-07 16:15:16 +08:00
|
|
|
endif # BLOCK
|
2005-04-17 06:20:36 +08:00
|
|
|
|
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2006-10-01 02:45:40 +08:00
|
|
|
if BLOCK
|
2005-04-17 06:20:36 +08:00
|
|
|
menu "DOS/FAT/NT Filesystems"
|
|
|
|
|
|
2009-01-22 15:37:59 +08:00
|
|
|
source "fs/fat/Kconfig"
|
2009-01-22 15:39:20 +08:00
|
|
|
source "fs/ntfs/Kconfig"
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
endmenu
|
2008-02-07 16:15:16 +08:00
|
|
|
endif # BLOCK
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
menu "Pseudo filesystems"
|
|
|
|
|
|
2008-07-25 16:48:30 +08:00
|
|
|
source "fs/proc/Kconfig"
|
2009-01-22 15:40:58 +08:00
|
|
|
source "fs/sysfs/Kconfig"
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config TMPFS
|
|
|
|
|
bool "Virtual memory file system support (former shm fs)"
|
|
|
|
|
help
|
|
|
|
|
Tmpfs is a file system which keeps all files in virtual memory.
|
|
|
|
|
|
|
|
|
|
Everything in tmpfs is temporary in the sense that no files will be
|
|
|
|
|
created on your hard drive. The files live in memory and swap
|
|
|
|
|
space. If you unmount a tmpfs instance, everything stored therein is
|
|
|
|
|
lost.
|
|
|
|
|
|
|
|
|
|
See <file:Documentation/filesystems/tmpfs.txt> for details.
|
|
|
|
|
|
2006-09-29 17:01:35 +08:00
|
|
|
config TMPFS_POSIX_ACL
|
|
|
|
|
bool "Tmpfs POSIX Access Control Lists"
|
|
|
|
|
depends on TMPFS
|
|
|
|
|
select GENERIC_ACL
|
|
|
|
|
help
|
|
|
|
|
POSIX Access Control Lists (ACLs) support permissions for users and
|
|
|
|
|
groups beyond the owner/group/world scheme.
|
|
|
|
|
|
|
|
|
|
To learn more about Access Control Lists, visit the POSIX ACLs for
|
|
|
|
|
Linux website <http://acl.bestbits.at/>.
|
|
|
|
|
|
|
|
|
|
If you don't know what Access Control Lists are, say N.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config HUGETLBFS
|
|
|
|
|
bool "HugeTLB file system support"
|
2008-04-30 19:38:46 +08:00
|
|
|
depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
|
|
|
|
|
(S390 && 64BIT) || BROKEN
|
2006-04-19 13:20:57 +08:00
|
|
|
help
|
|
|
|
|
hugetlbfs is a filesystem backing for HugeTLB pages, based on
|
|
|
|
|
ramfs. For architectures that support it, say Y here and read
|
|
|
|
|
<file:Documentation/vm/hugetlbpage.txt> for details.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config HUGETLB_PAGE
|
|
|
|
|
def_bool HUGETLBFS
|
|
|
|
|
|
2009-01-22 15:42:52 +08:00
|
|
|
source "fs/configfs/Kconfig"
|
2005-12-16 06:29:43 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
endmenu
|
|
|
|
|
|
2009-01-07 06:40:57 +08:00
|
|
|
menuconfig MISC_FILESYSTEMS
|
|
|
|
|
bool "Miscellaneous filesystems"
|
|
|
|
|
default y
|
|
|
|
|
---help---
|
|
|
|
|
Say Y here to get to see options for various miscellaneous
|
|
|
|
|
filesystems, such as filesystems that came from other
|
|
|
|
|
operating systems.
|
|
|
|
|
|
|
|
|
|
This option alone does not add any kernel code.
|
|
|
|
|
|
|
|
|
|
If you say N, all options in this submenu will be skipped and
|
|
|
|
|
disabled; if unsure, say Y here.
|
|
|
|
|
|
|
|
|
|
if MISC_FILESYSTEMS
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-01-22 15:48:46 +08:00
|
|
|
source "fs/adfs/Kconfig"
|
2009-01-22 15:49:44 +08:00
|
|
|
source "fs/affs/Kconfig"
|
2009-01-22 15:50:50 +08:00
|
|
|
source "fs/ecryptfs/Kconfig"
|
2009-01-22 15:53:24 +08:00
|
|
|
source "fs/hfs/Kconfig"
|
|
|
|
|
source "fs/hfsplus/Kconfig"
|
2009-01-22 15:54:16 +08:00
|
|
|
source "fs/befs/Kconfig"
|
2009-01-22 15:55:13 +08:00
|
|
|
source "fs/bfs/Kconfig"
|
2009-01-22 15:56:07 +08:00
|
|
|
source "fs/efs/Kconfig"
|
2008-08-29 11:19:50 +08:00
|
|
|
source "fs/jffs2/Kconfig"
|
2008-07-15 00:08:38 +08:00
|
|
|
# UBIFS File system configuration
|
|
|
|
|
source "fs/ubifs/Kconfig"
|
2009-01-22 15:56:54 +08:00
|
|
|
source "fs/cramfs/Kconfig"
|
2009-01-22 15:57:46 +08:00
|
|
|
source "fs/squashfs/Kconfig"
|
2009-01-22 15:58:51 +08:00
|
|
|
source "fs/freevxfs/Kconfig"
|
2009-01-22 15:59:49 +08:00
|
|
|
source "fs/minix/Kconfig"
|
2009-01-22 16:00:41 +08:00
|
|
|
source "fs/omfs/Kconfig"
|
2009-01-22 16:01:26 +08:00
|
|
|
source "fs/hpfs/Kconfig"
|
2009-01-22 16:02:21 +08:00
|
|
|
source "fs/qnx4/Kconfig"
|
2009-01-22 16:03:34 +08:00
|
|
|
source "fs/romfs/Kconfig"
|
2009-01-22 16:04:23 +08:00
|
|
|
source "fs/sysv/Kconfig"
|
2009-01-22 16:05:02 +08:00
|
|
|
source "fs/ufs/Kconfig"
|
2006-06-25 20:47:24 +08:00
|
|
|
|
2009-01-07 06:40:57 +08:00
|
|
|
endif # MISC_FILESYSTEMS
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-10-17 14:30:16 +08:00
|
|
|
menuconfig NETWORK_FILESYSTEMS
|
|
|
|
|
bool "Network File Systems"
|
|
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
depends on NET
|
2007-10-17 14:30:16 +08:00
|
|
|
---help---
|
|
|
|
|
Say Y here to get to see options for network filesystems and
|
|
|
|
|
filesystem-related networking code, such as NFS daemon and
|
|
|
|
|
RPCSEC security modules.
|
2008-05-22 05:09:04 +08:00
|
|
|
|
2007-10-17 14:30:16 +08:00
|
|
|
This option alone does not add any kernel code.
|
|
|
|
|
|
|
|
|
|
If you say N, all options in this submenu will be skipped and
|
|
|
|
|
disabled; if unsure, say Y here.
|
|
|
|
|
|
|
|
|
|
if NETWORK_FILESYSTEMS
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-01-22 16:07:41 +08:00
|
|
|
source "fs/nfs/Kconfig"
|
2009-01-22 16:08:58 +08:00
|
|
|
source "fs/nfsd/Kconfig"
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config LOCKD
|
|
|
|
|
tristate
|
|
|
|
|
|
|
|
|
|
config LOCKD_V4
|
|
|
|
|
bool
|
|
|
|
|
depends on NFSD_V3 || NFS_V3
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config EXPORTFS
|
|
|
|
|
tristate
|
|
|
|
|
|
2005-06-23 01:16:26 +08:00
|
|
|
config NFS_ACL_SUPPORT
|
|
|
|
|
tristate
|
|
|
|
|
select FS_POSIX_ACL
|
|
|
|
|
|
|
|
|
|
config NFS_COMMON
|
|
|
|
|
bool
|
|
|
|
|
depends on NFSD || NFS_FS
|
|
|
|
|
default y
|
|
|
|
|
|
2009-01-22 16:11:56 +08:00
|
|
|
source "net/sunrpc/Kconfig"
|
2009-01-22 16:13:16 +08:00
|
|
|
source "fs/smbfs/Kconfig"
|
2008-10-19 11:28:49 +08:00
|
|
|
source "fs/cifs/Kconfig"
|
2005-04-17 06:20:36 +08:00
|
|
|
source "fs/ncpfs/Kconfig"
|
|
|
|
|
|
|
|
|
|
config CODA_FS
|
|
|
|
|
tristate "Coda file system support (advanced network fs)"
|
|
|
|
|
depends on INET
|
|
|
|
|
help
|
|
|
|
|
Coda is an advanced network file system, similar to NFS in that it
|
|
|
|
|
enables you to mount file systems of a remote server and access them
|
|
|
|
|
with regular Unix commands as if they were sitting on your hard
|
|
|
|
|
disk. Coda has several advantages over NFS: support for
|
|
|
|
|
disconnected operation (e.g. for laptops), read/write server
|
|
|
|
|
replication, security model for authentication and encryption,
|
|
|
|
|
persistent client caches and write back caching.
|
|
|
|
|
|
|
|
|
|
If you say Y here, your Linux box will be able to act as a Coda
|
|
|
|
|
*client*. You will need user level code as well, both for the
|
|
|
|
|
client and server. Servers are currently user level, i.e. they need
|
|
|
|
|
no kernel support. Please read
|
|
|
|
|
<file:Documentation/filesystems/coda.txt> and check out the Coda
|
|
|
|
|
home page <http://www.coda.cs.cmu.edu/>.
|
|
|
|
|
|
|
|
|
|
To compile the coda client support as a module, choose M here: the
|
|
|
|
|
module will be called coda.
|
|
|
|
|
|
|
|
|
|
config AFS_FS
|
2006-11-16 17:19:27 +08:00
|
|
|
tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
|
2005-04-17 06:20:36 +08:00
|
|
|
depends on INET && EXPERIMENTAL
|
2007-04-27 06:55:03 +08:00
|
|
|
select AF_RXRPC
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here, you will get an experimental Andrew File System
|
|
|
|
|
driver. It currently only supports unsecured read-only AFS access.
|
|
|
|
|
|
2006-10-04 04:22:29 +08:00
|
|
|
See <file:Documentation/filesystems/afs.txt> for more information.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-04-27 06:55:03 +08:00
|
|
|
config AFS_DEBUG
|
|
|
|
|
bool "AFS dynamic debugging"
|
|
|
|
|
depends on AFS_FS
|
|
|
|
|
help
|
|
|
|
|
Say Y here to make runtime controllable debugging messages appear.
|
|
|
|
|
|
|
|
|
|
See <file:Documentation/filesystems/afs.txt> for more information.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
[PATCH] v9fs: Documentation, Makefiles, Configuration
OVERVIEW
V9FS is a distributed file system for Linux which provides an
implementation of the Plan 9 resource sharing protocol 9P. It can be
used to share all sorts of resources: static files, synthetic file servers
(such as /proc or /sys), devices, and application file servers (such as
FUSE).
BACKGROUND
Plan 9 (http://plan9.bell-labs.com/plan9) is a research operating
system and associated applications suite developed by the Computing
Science Research Center of AT&T Bell Laboratories (now a part of
Lucent Technologies), the same group that developed UNIX , C, and C++.
Plan 9 was initially released in 1993 to universities, and then made
generally available in 1995. Its core operating systems code laid the
foundation for the Inferno Operating System released as a product by
Lucent Bell-Labs in 1997. The Inferno venture was the only commercial
embodiment of Plan 9 and is currently maintained as a product by Vita
Nuova (http://www.vitanuova.com). After updated releases in 2000 and
2002, Plan 9 was open-sourced under the OSI approved Lucent Public
License in 2003.
The Plan 9 project was started by Ken Thompson and Rob Pike in 1985.
Their intent was to explore potential solutions to some of the
shortcomings of UNIX in the face of the widespread use of high-speed
networks to connect machines. In UNIX, networking was an afterthought
and UNIX clusters became little more than a network of stand-alone
systems. Plan 9 was designed from first principles as a seamless
distributed system with integrated secure network resource sharing.
Applications and services were architected in such a way as to allow
for implicit distribution across a cluster of systems. Configuring an
environment to use remote application components or services in place
of their local equivalent could be achieved with a few simple command
line instructions. For the most part, application implementations
operated independent of the location of their actual resources.
Commercial operating systems haven't changed much in the 20 years
since Plan 9 was conceived. Network and distributed systems support is
provided by a patchwork of middle-ware, with an endless number of
packages supplying pieces of the puzzle. Matters are complicated by
the use of different complicated protocols for individual services,
and separate implementations for kernel and application resources.
The V9FS project (http://v9fs.sourceforge.net) is an attempt to bring
Plan 9's unified approach to resource sharing to Linux and other
operating systems via support for the 9P2000 resource sharing
protocol.
V9FS HISTORY
V9FS was originally developed by Ron Minnich and Maya Gokhale at Los
Alamos National Labs (LANL) in 1997. In November of 2001, Greg Watson
setup a SourceForge project as a public repository for the code which
supported the Linux 2.4 kernel.
About a year ago, I picked up the initial attempt Ron Minnich had
made to provide 2.6 support and got the code integrated into a 2.6.5
kernel. I then went through a line-for-line re-write attempting to
clean-up the code while more closely following the Linux Kernel style
guidelines. I co-authored a paper with Ron Minnich on the V9FS Linux
support including performance comparisons to NFSv3 using Bonnie and
PostMark - this paper appeared at the USENIX/FREENIX 2005
conference in April 2005:
( http://www.usenix.org/events/usenix05/tech/freenix/hensbergen.html ).
CALL FOR PARTICIPATION/REQUEST FOR COMMENTS
Our 2.6 kernel support is stabilizing and we'd like to begin pursuing
its integration into the official kernel tree. We would appreciate any
review, comments, critiques, and additions from this community and are
actively seeking people to join our project and help us produce
something that would be acceptable and useful to the Linux community.
STATUS
The code is reasonably stable, although there are no doubt corner cases
our regression tests haven't discovered yet. It is in regular use by several
of the developers and has been tested on x86 and PowerPC
(32-bit and 64-bit) in both small and large (LANL cluster) deployments.
Our current regression tests include fsx, bonnie, and postmark.
It was our intention to keep things as simple as possible for this
release -- trying to focus on correctness within the core of the
protocol support versus a rich set of features. For example: a more
complete security model and cache layer are in the road map, but
excluded from this release. Additionally, we have removed support for
mmap operations at Al Viro's request.
PERFORMANCE
Detailed performance numbers and analysis are included in the FREENIX
paper, but we show comparable performance to NFSv3 for large file
operations based on the Bonnie benchmark, and superior performance for
many small file operations based on the PostMark benchmark. Somewhat
preliminary graphs (from the FREENIX paper) are available
(http://v9fs.sourceforge.net/perf/index.html).
RESOURCES
The source code is available in a few different forms:
tarballs: http://v9fs.sf.net
CVSweb: http://cvs.sourceforge.net/viewcvs.py/v9fs/linux-9p/
CVS: :pserver:anonymous@cvs.sourceforge.net:/cvsroot/v9fs/linux-9p
Git: rsync://v9fs.graverobber.org/v9fs (webgit: http://v9fs.graverobber.org)
9P: tcp!v9fs.graverobber.org!6564
The user-level server is available from either the Plan 9 distribution
or from http://v9fs.sf.net
Other support applications are still being developed, but preliminary
version can be downloaded from sourceforge.
Documentation on the protocol has historically been the Plan 9 Man
pages (http://plan9.bell-labs.com/sys/man/5/INDEX.html), but there is
an effort under way to write a more complete Internet-Draft style
specification (http://v9fs.sf.net/rfc).
There are a couple of mailing lists supporting v9fs, but the most used
is v9fs-developer@lists.sourceforge.net -- please direct/cc your
comments there so the other v9fs contibutors can participate in the
conversation. There is also an IRC channel: irc://freenode.net/#v9fs
This part of the patch contains Documentation, Makefiles, and configuration
file changes.
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-10 04:04:18 +08:00
|
|
|
config 9P_FS
|
|
|
|
|
tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
|
2007-07-11 06:57:28 +08:00
|
|
|
depends on INET && NET_9P && EXPERIMENTAL
|
[PATCH] v9fs: Documentation, Makefiles, Configuration
OVERVIEW
V9FS is a distributed file system for Linux which provides an
implementation of the Plan 9 resource sharing protocol 9P. It can be
used to share all sorts of resources: static files, synthetic file servers
(such as /proc or /sys), devices, and application file servers (such as
FUSE).
BACKGROUND
Plan 9 (http://plan9.bell-labs.com/plan9) is a research operating
system and associated applications suite developed by the Computing
Science Research Center of AT&T Bell Laboratories (now a part of
Lucent Technologies), the same group that developed UNIX , C, and C++.
Plan 9 was initially released in 1993 to universities, and then made
generally available in 1995. Its core operating systems code laid the
foundation for the Inferno Operating System released as a product by
Lucent Bell-Labs in 1997. The Inferno venture was the only commercial
embodiment of Plan 9 and is currently maintained as a product by Vita
Nuova (http://www.vitanuova.com). After updated releases in 2000 and
2002, Plan 9 was open-sourced under the OSI approved Lucent Public
License in 2003.
The Plan 9 project was started by Ken Thompson and Rob Pike in 1985.
Their intent was to explore potential solutions to some of the
shortcomings of UNIX in the face of the widespread use of high-speed
networks to connect machines. In UNIX, networking was an afterthought
and UNIX clusters became little more than a network of stand-alone
systems. Plan 9 was designed from first principles as a seamless
distributed system with integrated secure network resource sharing.
Applications and services were architected in such a way as to allow
for implicit distribution across a cluster of systems. Configuring an
environment to use remote application components or services in place
of their local equivalent could be achieved with a few simple command
line instructions. For the most part, application implementations
operated independent of the location of their actual resources.
Commercial operating systems haven't changed much in the 20 years
since Plan 9 was conceived. Network and distributed systems support is
provided by a patchwork of middle-ware, with an endless number of
packages supplying pieces of the puzzle. Matters are complicated by
the use of different complicated protocols for individual services,
and separate implementations for kernel and application resources.
The V9FS project (http://v9fs.sourceforge.net) is an attempt to bring
Plan 9's unified approach to resource sharing to Linux and other
operating systems via support for the 9P2000 resource sharing
protocol.
V9FS HISTORY
V9FS was originally developed by Ron Minnich and Maya Gokhale at Los
Alamos National Labs (LANL) in 1997. In November of 2001, Greg Watson
setup a SourceForge project as a public repository for the code which
supported the Linux 2.4 kernel.
About a year ago, I picked up the initial attempt Ron Minnich had
made to provide 2.6 support and got the code integrated into a 2.6.5
kernel. I then went through a line-for-line re-write attempting to
clean-up the code while more closely following the Linux Kernel style
guidelines. I co-authored a paper with Ron Minnich on the V9FS Linux
support including performance comparisons to NFSv3 using Bonnie and
PostMark - this paper appeared at the USENIX/FREENIX 2005
conference in April 2005:
( http://www.usenix.org/events/usenix05/tech/freenix/hensbergen.html ).
CALL FOR PARTICIPATION/REQUEST FOR COMMENTS
Our 2.6 kernel support is stabilizing and we'd like to begin pursuing
its integration into the official kernel tree. We would appreciate any
review, comments, critiques, and additions from this community and are
actively seeking people to join our project and help us produce
something that would be acceptable and useful to the Linux community.
STATUS
The code is reasonably stable, although there are no doubt corner cases
our regression tests haven't discovered yet. It is in regular use by several
of the developers and has been tested on x86 and PowerPC
(32-bit and 64-bit) in both small and large (LANL cluster) deployments.
Our current regression tests include fsx, bonnie, and postmark.
It was our intention to keep things as simple as possible for this
release -- trying to focus on correctness within the core of the
protocol support versus a rich set of features. For example: a more
complete security model and cache layer are in the road map, but
excluded from this release. Additionally, we have removed support for
mmap operations at Al Viro's request.
PERFORMANCE
Detailed performance numbers and analysis are included in the FREENIX
paper, but we show comparable performance to NFSv3 for large file
operations based on the Bonnie benchmark, and superior performance for
many small file operations based on the PostMark benchmark. Somewhat
preliminary graphs (from the FREENIX paper) are available
(http://v9fs.sourceforge.net/perf/index.html).
RESOURCES
The source code is available in a few different forms:
tarballs: http://v9fs.sf.net
CVSweb: http://cvs.sourceforge.net/viewcvs.py/v9fs/linux-9p/
CVS: :pserver:anonymous@cvs.sourceforge.net:/cvsroot/v9fs/linux-9p
Git: rsync://v9fs.graverobber.org/v9fs (webgit: http://v9fs.graverobber.org)
9P: tcp!v9fs.graverobber.org!6564
The user-level server is available from either the Plan 9 distribution
or from http://v9fs.sf.net
Other support applications are still being developed, but preliminary
version can be downloaded from sourceforge.
Documentation on the protocol has historically been the Plan 9 Man
pages (http://plan9.bell-labs.com/sys/man/5/INDEX.html), but there is
an effort under way to write a more complete Internet-Draft style
specification (http://v9fs.sf.net/rfc).
There are a couple of mailing lists supporting v9fs, but the most used
is v9fs-developer@lists.sourceforge.net -- please direct/cc your
comments there so the other v9fs contibutors can participate in the
conversation. There is also an IRC channel: irc://freenode.net/#v9fs
This part of the patch contains Documentation, Makefiles, and configuration
file changes.
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-10 04:04:18 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here, you will get experimental support for
|
|
|
|
|
Plan 9 resource sharing via the 9P2000 protocol.
|
|
|
|
|
|
|
|
|
|
See <http://v9fs.sf.net> for more information.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-10-17 14:30:16 +08:00
|
|
|
endif # NETWORK_FILESYSTEMS
|
2005-04-17 06:20:36 +08:00
|
|
|
|
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2006-10-01 02:45:40 +08:00
|
|
|
if BLOCK
|
2005-04-17 06:20:36 +08:00
|
|
|
menu "Partition Types"
|
|
|
|
|
|
|
|
|
|
source "fs/partitions/Kconfig"
|
|
|
|
|
|
|
|
|
|
endmenu
|
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2006-10-01 02:45:40 +08:00
|
|
|
endif
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
source "fs/nls/Kconfig"
|
2006-01-18 17:30:29 +08:00
|
|
|
source "fs/dlm/Kconfig"
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
endmenu
|