Public bug reported:

network-interface.conf handles new network interfaces. Unfortunately, at boot 
it is called while the root system is still read-only.
Not to mention the command "mkdir -p /run/network" that is not going to work 
with ro root, dhcpclient cannot write leases and fails. Static address is still 
somehow succeeding. wpasupplicant does not work either.
Not understanding upstart structure well enough (are there dependency graph 
visualisation tools?), I have just added
"mount -orw,remount /" before the "mkdir" command. This fixed the network 
interface configuration at boot.
I know this will interfere with fsck.
Surely there are better ways to fix it...please? I see a lot of dumbfounded 
folk scratching their heads why simple /etc/network/interfaces configuration 
does not work.

** Affects: ifupdown (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1102182

Title:
  netscript-2.4-upstart runs with read-only root: dhcp and wpa broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1102182/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to