Hi, the init-scripts that are installed by the upcoming still unstable ebuilds aren't prepared for systems, where nfsd is compiled as a kernel-module. All init-scripts check /proc/filesystems if it contains nfsd, but it won't until the module nfsd is loaded. The scripts need to be modified. They could either check for the kernel-version, or silently load the nfsd-module before checking /proc/filesystems Reproducible: Always Steps to Reproduce:
what init-scripts ? what ebuilds ? why cant you just put your nfs modules into the modules.autoload files ?
/etc/init.d/nfs installed by net-fs/nfs-utils-1.0.6-r4. Sure i could write "nfsd" into my modules.autoload.d/kernel-2.*, but that's not the way it's ment to be: the module would be loaded automatically, if you mount the nfsd-filesystem to /proc/..., but since your "nfsd-fs" detecting code doesn't work if the nfsd-module isn't loaded, you should load the module prior to testing for nfsd in /proc/filesystems.
Just to have a better wording: most application of the nfs-utils package load the nfsd-module automatically, perhaps due to the automatic-module-loading-swicth in the kernel. Now your kernel-2.6 detection-code that uses /proc/filesystems does not and will fail since the module isn't loaded - oh well, it won't fail is /etc/init.d/nfs is restarted, since the module is loaded then. You could either load the module simply by doing "modprobe nfsd >/dev/null 2>&1" or simply by checking that the kernel-version is greater than 2.5. Due to that, most poeple running kernel-2.6 and having compiled nfsd as a module will run nsfd in compatibility-mode without knowing that. Since compatibility-mode is broken, this has to be fixed/improved. Loading the nfsd-module is also recommed with regard to Bug http://bugs.gentoo.org/show_bug.cgi?id=66575
added to cvs
