> Please show the contents of /etc/network/interfaces. This is quite straight forward (I've attached the file).
> Which of the bridges is the one that gets started? vm0 only > The bridges are assumed to be up at system startup. vm0 vm1 vm2 vm8 > What do you mean here? Do you mean that other parts of > your configuration assume they're available? That's entirely > reasonable. >> Maybe this is again related to parts of the networking setup using >> /var/run/network, while others use /run/network. > Not unless something broke on your upgrade and prevented > /var/run from being migrated to a symlink to /run. If so, you > probably have a broken shutdown sequence as described > in bug #858122. /run and /var/run where both directories. None of them was symlinked to the other. > I don't think this is likely to be the cause in any case, since > ifupdown doesn't use /run to share data with other packages. ifup was the command exausting the error message about /run not holding directory /run/network. Which was correct: ifup mentions /run/network checking if it is there, breaking if not. Since there where various other issues, I decided to reinstall. This solved some errors, but gave some new ones, while some old remained. Badly enough most related to networking ... :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876449 Title: plymouth hanging after printing "Booting system without full network configuration" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/876449/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
