steve,
yes it does exist. i am running karmic upgraded all the way back from hardy
heron and my nfs mounts not longer auto mount. here are my fstab entries
192.168.0.5:/var/lib/mythtv /var/lib/mythtv nfs
rsize=8192,wsize=8192,timeo=14,intr
192.168.0.5:/media/500gb /media/500gb nfs rsize=8192,wsi
With Ubuntu 9.10, this bug does not exist.
** Changed in: nfs-utils (Ubuntu)
Status: Confirmed => Fix Released
--
not automount by fstab in Jaunty
https://bugs.launchpad.net/bugs/367675
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I have the same issue. Added some log messages to /etc/network/if-
up.d/mountnfs script and discovered that the script was exiting in
exit_unless_last_interface. That function reads /etc/network/interfaces
and exits if not all of the "auto" interfaces are currently up.
My /etc/network/interfaces f
i have the same issue on my laptop where Jaunty was update from
intrepid.I am still trying to locate that nfs from the terminal using
the SUDO command.Thus far nothing has worked.The only Thing that seems
to work is the workaround,which is:
sudo modprobe floppy
what I have managed to get was tha
** Description changed:
I have some workstations on ubuntu. On this workstations some network
paths is mounted by NFS. But after upgrade to Jaunty I have one problem:
NFS mounts in fstab not mounted automatically at startup. Strange thing:
NFS paths mounts successfully by command "mount -a
** Description changed:
I have some workstations on ubuntu. On this workstations some network
paths is mounted by NFS. But after upgrade to Jaunty I have one problem:
NFS mounts in fstab not mounted automatically at startup. Strange thing:
NFS paths mounts successfully by command "mount -a
