Thanks for the followup. Closing the debian-installer part now. The work
on the Debian side wrt. multiplexing the installer UI to mutiple
consoles sounds interesting, but I don't think we should houd our breath
for it -- I think this is going to be tricky given how different the
capabilities of VT
This bug was fixed in the package systemd - 229-4ubuntu8
---
systemd (229-4ubuntu8) xenial-proposed; urgency=medium
* Queue loading transient units after setting their properties. Fixes
starting VMs with libvirt. (LP: #1529079)
* Connect pid1's stdin/out/err fds to /dev/null
This bug was fixed in the package systemd - 231-5
---
systemd (231-5) unstable; urgency=medium
[ Iain Lane ]
* Let graphical-session-pre.target be manually started (LP: #1615341)
[ Felipe Sateler ]
* Add basic version of git-cherry-pick
* Replace
This bug was fixed in the package busybox - 1:1.22.0-19ubuntu2
---
busybox (1:1.22.0-19ubuntu2) yakkety; urgency=medium
* debian/patches/readlink-in-slash-bin.patch: put readlink in /bin/
like coreutils. Closes LP: #1615021.
-- Steve Langasek
I've thought about this some more, and while the /bin/readlink
/usr/bin/readlink in busybox is a bug, fixing this is definitely not
going to fix the problem in the installer. In the installer,
/etc/udev/rules.d/80-net-setup-link.rules will never exist since this is
an admin override; so the
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1615021
Title:
Unable to network boot Ubuntu 16.04
Examining the initrd shows that readlink is provided as
/usr/bin/readlink -> /bin/busybox, not as /bin/readlink where systemd
expects it (and where it's shipped on an installed system). This is a
bug in debian-installer's construction of that image - though gee it
would be nice if systemd didn't