8cf1fb2163
Just like files-layout, blocks & objects layouts are part of the NFS 4.1 protocol and should be automatically selected if NFS_4_1 is selected. The small problem is that these depend on other Kernel support being present, while files only depends on NFS itself. This patch removes from the user choice the presence of objects and blocks layout. But makes sure these are selected only if the depended subsystems are present in the Kernel. Signed-off-by: Boaz Harrosh <bharrosh@panasas.com> Acked-by: Peng Tao <peng_tao@emc.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
146 lines
4.6 KiB
Plaintext
146 lines
4.6 KiB
Plaintext
config NFS_FS
|
|
tristate "NFS client support"
|
|
depends on INET && FILE_LOCKING
|
|
select LOCKD
|
|
select SUNRPC
|
|
select NFS_ACL_SUPPORT if NFS_V3_ACL
|
|
help
|
|
Choose Y here if you want to access files residing on other
|
|
computers using Sun's Network File System protocol. To compile
|
|
this file system support as a module, choose M here: the module
|
|
will be called nfs.
|
|
|
|
To mount file systems exported by NFS servers, you also need to
|
|
install the user space mount.nfs command which can be found in
|
|
the Linux nfs-utils package, available from http://linux-nfs.org/.
|
|
Information about using the mount command is available in the
|
|
mount(8) man page. More detail about the Linux NFS client
|
|
implementation is available via the nfs(5) man page.
|
|
|
|
Below you can choose which versions of the NFS protocol are
|
|
available in the kernel to mount NFS servers. Support for NFS
|
|
version 2 (RFC 1094) is always available when NFS_FS is selected.
|
|
|
|
To configure a system which mounts its root file system via NFS
|
|
at boot time, say Y here, select "Kernel level IP
|
|
autoconfiguration" in the NETWORK menu, and select "Root file
|
|
system on NFS" below. You cannot compile this file system as a
|
|
module in this case.
|
|
|
|
If unsure, say N.
|
|
|
|
config NFS_V3
|
|
bool "NFS client support for NFS version 3"
|
|
depends on NFS_FS
|
|
help
|
|
This option enables support for version 3 of the NFS protocol
|
|
(RFC 1813) in the kernel's NFS client.
|
|
|
|
If unsure, say Y.
|
|
|
|
config NFS_V3_ACL
|
|
bool "NFS client support for the NFSv3 ACL protocol extension"
|
|
depends on NFS_V3
|
|
help
|
|
Some NFS servers support an auxiliary NFSv3 ACL protocol that
|
|
Sun added to Solaris but never became an official part of the
|
|
NFS version 3 protocol. This protocol extension allows
|
|
applications on NFS clients to manipulate POSIX Access Control
|
|
Lists on files residing on NFS servers. NFS servers enforce
|
|
ACLs on local files whether this protocol is available or not.
|
|
|
|
Choose Y here if your NFS server supports the Solaris NFSv3 ACL
|
|
protocol extension and you want your NFS client to allow
|
|
applications to access and modify ACLs on files on the server.
|
|
|
|
Most NFS servers don't support the Solaris NFSv3 ACL protocol
|
|
extension. You can choose N here or specify the "noacl" mount
|
|
option to prevent your NFS client from trying to use the NFSv3
|
|
ACL protocol.
|
|
|
|
If unsure, say N.
|
|
|
|
config NFS_V4
|
|
bool "NFS client support for NFS version 4"
|
|
depends on NFS_FS
|
|
select SUNRPC_GSS
|
|
help
|
|
This option enables support for version 4 of the NFS protocol
|
|
(RFC 3530) in the kernel's NFS client.
|
|
|
|
To mount NFS servers using NFSv4, you also need to install user
|
|
space programs which can be found in the Linux nfs-utils package,
|
|
available from http://linux-nfs.org/.
|
|
|
|
If unsure, say Y.
|
|
|
|
config NFS_V4_1
|
|
bool "NFS client support for NFSv4.1 (EXPERIMENTAL)"
|
|
depends on NFS_FS && NFS_V4 && EXPERIMENTAL
|
|
select SUNRPC_BACKCHANNEL
|
|
select PNFS_FILE_LAYOUT
|
|
help
|
|
This option enables support for minor version 1 of the NFSv4 protocol
|
|
(RFC 5661) in the kernel's NFS client.
|
|
|
|
If unsure, say N.
|
|
|
|
config PNFS_FILE_LAYOUT
|
|
tristate
|
|
|
|
config PNFS_BLOCK
|
|
tristate
|
|
depends on NFS_FS && NFS_V4_1 && BLK_DEV_DM
|
|
default m
|
|
|
|
config PNFS_OBJLAYOUT
|
|
tristate
|
|
depends on NFS_FS && NFS_V4_1 && SCSI_OSD_ULD
|
|
default m
|
|
|
|
config ROOT_NFS
|
|
bool "Root file system on NFS"
|
|
depends on NFS_FS=y && IP_PNP
|
|
help
|
|
If you want your system to mount its root file system via NFS,
|
|
choose Y here. This is common practice for managing systems
|
|
without local permanent storage. For details, read
|
|
<file:Documentation/filesystems/nfs/nfsroot.txt>.
|
|
|
|
Most people say N here.
|
|
|
|
config NFS_FSCACHE
|
|
bool "Provide NFS client caching support"
|
|
depends on NFS_FS=m && FSCACHE || NFS_FS=y && FSCACHE=y
|
|
help
|
|
Say Y here if you want NFS data to be cached locally on disc through
|
|
the general filesystem cache manager
|
|
|
|
config NFS_USE_LEGACY_DNS
|
|
bool "Use the legacy NFS DNS resolver"
|
|
depends on NFS_V4
|
|
help
|
|
The kernel now provides a method for translating a host name into an
|
|
IP address. Select Y here if you would rather use your own DNS
|
|
resolver script.
|
|
|
|
If unsure, say N
|
|
|
|
config NFS_USE_KERNEL_DNS
|
|
bool
|
|
depends on NFS_V4 && !NFS_USE_LEGACY_DNS
|
|
select DNS_RESOLVER
|
|
select KEYS
|
|
default y
|
|
|
|
config NFS_USE_NEW_IDMAPPER
|
|
bool "Use the new idmapper upcall routine"
|
|
depends on NFS_V4 && KEYS
|
|
help
|
|
Say Y here if you want NFS to use the new idmapper upcall functions.
|
|
You will need /sbin/request-key (usually provided by the keyutils
|
|
package). For details, read
|
|
<file:Documentation/filesystems/nfs/idmapper.txt>.
|
|
|
|
If you are unsure, say N.
|