1ae811ee27
Some systems have a modprobe.d/nfs.conf file that sets an nfs4 alias pointing to nfs.ko, rather than nfs4.ko. This can prevent the v4 module from loading on mount, since the kernel sees that something named "nfs4" has already been loaded. To work around this, I've renamed the modules to "nfsv2.ko" "nfsv3.ko" and "nfsv4.ko". I also had to move the nfs4_fs_type back to nfs.ko to ensure that `mount -t nfs4` still works. Signed-off-by: Bryan Schumaker <bjschuma@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
34 lines
1.1 KiB
Makefile
34 lines
1.1 KiB
Makefile
#
|
|
# Makefile for the Linux nfs filesystem routines.
|
|
#
|
|
|
|
obj-$(CONFIG_NFS_FS) += nfs.o
|
|
|
|
nfs-y := client.o dir.o file.o getroot.o inode.o super.o \
|
|
direct.o pagelist.o read.o symlink.o unlink.o \
|
|
write.o namespace.o mount_clnt.o \
|
|
dns_resolve.o cache_lib.o
|
|
nfs-$(CONFIG_ROOT_NFS) += nfsroot.o
|
|
nfs-$(CONFIG_SYSCTL) += sysctl.o
|
|
nfs-$(CONFIG_NFS_FSCACHE) += fscache.o fscache-index.o
|
|
|
|
obj-$(CONFIG_NFS_V2) += nfsv2.o
|
|
nfsv2-y := nfs2super.o proc.o nfs2xdr.o
|
|
|
|
obj-$(CONFIG_NFS_V3) += nfsv3.o
|
|
nfsv3-y := nfs3super.o nfs3client.o nfs3proc.o nfs3xdr.o
|
|
nfsv3-$(CONFIG_NFS_V3_ACL) += nfs3acl.o
|
|
|
|
obj-$(CONFIG_NFS_V4) += nfsv4.o
|
|
nfsv4-y := nfs4proc.o nfs4xdr.o nfs4state.o nfs4renewd.o nfs4super.o nfs4file.o \
|
|
delegation.o idmap.o callback.o callback_xdr.o callback_proc.o \
|
|
nfs4namespace.o nfs4getroot.o nfs4client.o
|
|
nfsv4-$(CONFIG_SYSCTL) += nfs4sysctl.o
|
|
nfsv4-$(CONFIG_NFS_V4_1) += pnfs.o pnfs_dev.o
|
|
|
|
obj-$(CONFIG_PNFS_FILE_LAYOUT) += nfs_layout_nfsv41_files.o
|
|
nfs_layout_nfsv41_files-y := nfs4filelayout.o nfs4filelayoutdev.o
|
|
|
|
obj-$(CONFIG_PNFS_OBJLAYOUT) += objlayout/
|
|
obj-$(CONFIG_PNFS_BLOCK) += blocklayout/
|