Debian claims to have fixed it. Please note the following, which
suggests otherwise:
r...@noel-intrepid:~# /etc/init.d/nfs-common restart
* Stopping NFS common utilities [ OK ]
* Starting NFS common utilities [
This problem is present in Hardy, Intrepid and Jaunty. I've just gone
and checked them all, along with Fedora 10. Ernst is correct about the
differential behavior between mounting nfs and nfs4.
The upstream debian bug is #451782.
** Bug watch added: Debian Bug tracker #451782
the same problem the original reporter had is still present in hardy.
(the nfs module is automatically loaded only with nfsv3 mounts, not with nfsv4
mounts)
--
(gutsy)Need to modprobe nfs module before mounting nfs4 export
https://bugs.launchpad.net/bugs/117957
You received this bug
Also true for me.
I added nfs to /etc/modules as a workaround
--
(gutsy)Need to modprobe nfs module before mounting nfs4 export
https://bugs.launchpad.net/bugs/117957
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I don't have this problem anymore
--
(gutsy)Need to modprobe nfs module before mounting nfs4 export
https://bugs.launchpad.net/bugs/117957
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I'll confirm that this problem still exists in Gutsy as of this date.
** Changed in: util-linux (Ubuntu)
Status: New = Confirmed
--
(gutsy)Need to modprobe nfs module before mounting nfs4 export
https://bugs.launchpad.net/bugs/117957
You received this bug notification because you are a
** Changed in: util-linux (Ubuntu)
Sourcepackagename: None = util-linux
--
(gutsy)Need to modprobe nfs module before mounting nfs4 export
https://bugs.launchpad.net/bugs/117957
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
