Have a look at this discussion:
http://markmail.org/message/kbdcma2vixgfdz4x
In short, Tim Gardner has written:
"We typically don't enable options that are marked experimental.
fs/nfs/Kconfig:depends on EXPERIMENTAL"
However, this explanation isn't entirely satisfactory, as William van de
Velde has pointed out:
"But why is cachefs core module enabled when that one also is experimental
/lib/modules/2.6.31-10-generic/kernel/fs/fscache/fscache.ko
fs/fscache/Kconfig: depends on EXPERIMENTAL
boot/config-2.6.31-10-generic: CONFIG_CACHEFILES=m
also is the userspace daemon cachefilesd for nfs and afs already in the
repository.
I think it would be generally a good idea to not enable experimental
things but we already have the cachefilesd userspace daemon and the kernel
stuff can be build as modules so can this functionality be enabled as a
module?"
This has remained unanswered.
To put my 2 cents in, I've noticed that the NFS_V4 option itself is also
experimental, from looking at fs/nfs/Kconfig:
config NFS_V4
bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
depends on NFS_FS && EXPERIMENTAL
In general, I think that the EXPERIMENTAL state of stuff related to NFS
4 isn't entirely deserved anymore since it has been around and people
have been using it for a while .
--
nfs + fs-cache
https://bugs.launchpad.net/bugs/190472
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
