On fresh Utopic host (VM, server install):
$ sudo apt-get update; sudo apt-get install ubuntu-dev-tools systemd haveged $ mk-sbuild utopic relogin $ mk-sbuild utopic $ sbuild-update --keygen $ pull-lp-source hello $ sbuild -Ad utopic *.dsc
# boot with init=/lib/systmed/systemd
$ sbuild -Ad utopic *.dsc
Fails with "E: 10mount: E: Failed to resolve path "...../dev/shm": Not a directory"
/run/shm does not exsit.
This is a bug in systmed, until we support booting with either upstart or systemd "/run/shm" should continue to be present.
Specifically, systemd, unlike mountall does not appear to support and match Ubuntu default mount points as specified in /lib/init/fstab.
On fresh Utopic host (VM, server install):
$ sudo apt-get update; sudo apt-get install ubuntu-dev-tools systemd haveged
$ mk-sbuild utopic
relogin
$ mk-sbuild utopic
$ sbuild-update --keygen
$ pull-lp-source hello
$ sbuild -Ad utopic *.dsc
# boot with init=/lib/ systmed/ systemd
$ sbuild -Ad utopic *.dsc
Fails with
"E: 10mount: E: Failed to resolve path "...../dev/shm": Not a directory"
/run/shm does not exsit.
This is a bug in systmed, until we support booting with either upstart or systemd "/run/shm" should continue to be present.
Specifically, systemd, unlike mountall does not appear to support and match Ubuntu default mount points as specified in /lib/init/fstab.