** Tags added: regression-release
--
[regression][intrepid] NFS mounts not attempted with idle network interface
https://bugs.launchpad.net/bugs/327458
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Okay, changing package to udev and setting confirmed - I've verified the
mismatch exists here.
** Changed in: udev (Ubuntu)
Sourcepackagename: sysvinit = udev
Status: Incomplete = Confirmed
--
[regression][intrepid] NFS mounts not attempted with idle network interface
allow-hotplug has never worked or been valid in Ubuntu, it's a Debianism
they introduced later and that we have chosen not to adopt
** Changed in: udev (Ubuntu)
Status: Confirmed = Invalid
--
[regression][intrepid] NFS mounts not attempted with idle network interface
** Changed in: sysvinit (Ubuntu)
Status: New = Incomplete
--
[regression][intrepid] NFS mounts not attempted with idle network interface
https://bugs.launchpad.net/bugs/327458
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Ah-ha - thanks for the pointer :) The problem has probably shifted to
udev rules..
I tried booting without 'auto usb0' and without altering
/etc/default/rcS: the NFS mount now works. Unfortunately this prevents
the usb0 network interface being configured when I plug my USB network
device in, due
I've found an upstream bug reported with a similar issue:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496007
sadly no responses there...
--
[regression][intrepid] NFS mounts not attempted with idle network interface
https://bugs.launchpad.net/bugs/327458
You received this bug notification
I think I see what's up:
From the interfaces(5) manual page:
Lines beginning with the word auto are used to identify the physical
interfaces to be brought up when ifup is run with the -a option. (This
option is used by the system boot scripts.)
And
Lines beginning with allow- are used
