See also bug
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/377432
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/276365
Title:
/var/run/network is not created
--
ubuntu-bugs mailing list
FYI
another fix is proposed is this bug,
https://bugs.launchpad.net/ubuntu/+bug/367171
it seems this is a bug in ifupdown or netbase?
HTH
--
/var/run/network is not created
https://bugs.launchpad.net/bugs/276365
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: vmbuilder
Status: Fix Committed => Fix Released
--
/var/run/network is not created
https://bugs.launchpad.net/bugs/276365
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
This bug was fixed in the package vm-builder - 0.9-0ubuntu3
---
vm-builder (0.9-0ubuntu3) intrepid; urgency=low
[ Johan Euphrosine ]
* Fix exception when suite provided does not exist (LP: #281801)
and provide unit test for it.
[ Chuck Short ]
* Added parameters required
Better fix committed by Soren at rev 258:
Create /var/{run,lock} on root filesystem, so that the appropriate tmpfs's
will be mountable before /var is mounted in the running system. This matches
d-i behaviour.
Don't create /var/run/network anymore.
** Changed in: vm-builder (Ubun
