It seems that the link to systemd at /sbin/init must be re-written, or the
boot will hang when init is suppose to start.
sudo ln -sf /usr/lib/systemd/systemd /sbin/init
Perhaps this has to do with the otherwise chain-of-links, from /lib/systemd to
/usr/lib/systemd? To get by the boot-hang, "init=/usr/lib/systemd/systemd"
can be added to the kernel command line, and then change the link in /sbin/.
Other errors that have shown-up, reading from "journalctl",
systemd[242]: Failed at step EXEC spawning
/lib/systemd/systemd-remount-api-vfs: No such file or directory
systemd-udevd[273]: Error running install command for snd_pcm
systemd-tmpfiles[1747]: [/usr/lib/tmpfiles.d/legacy.conf:22] Unknown group
'lock'.
systemd[1]: Failed to start Recreate Volatile Files and Directories.
jasper minissdpd[561]: /lib/init/vars.sh: line 49: cat: command not found
jasper minissdpd[561]: /etc/init.d/minissdpd: line 55: start-stop-daemon:
command not found
gpm[629]: Starting mouse interface server: gpm/etc/init.d/gpm: 69:
/etc/init.d/gpm: start-stop-daemon: not found
smokeping[792]: Starting latency logger daemon:
smokeping/etc/init.d/smokeping: 108: /etc/init.d/smokeping: mkdir: not found
sysfsutils[957]: Setting sysfs variables.../etc/init.d/sysfsutils: 30:
/etc/init.d/sysfsutils: sed: not found
systemd[1]: Failed to start LSB: exim Mail Transport Agent.
systemd[1]: Failed to start Cleanup of Temporary Directories.
"systemd/system/systemd-remount-api-vfs.service" makes reference to the
nonexistent
"systemd/systemd-remount-api-vfs", so I assume that that is obsolete, and the
link also, "system/local-fs.target.wants/systemd-remount-api-vfs.service".
There is a reference in "/usr/lib/tmpfiles.d/legacy.conf" to a group "lock", a
group which does not exist on a non-legacy system. It appears that this is
enough for "Recreate Volatile..." to fail. Is that not a systemd bug? I
commented-out the line referencing group "lock".
If there are real files in /tmp/, over which the tmpfs gets mounted, these
should be removed, or there will be a warning message.
Many systemd services will fail because systemd will now re-set the PATH
variable
to "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin" - which conspicuously
leaves off "/bin" and "/sbin" - UNLESS the "--enable-split-usr" is explicitly
selected when running "configure".
./configure --enable-split-usr --bindir=/bin --sysconfdir=/etc
--with-distro=debian
This is in systemd-196/src/core/main.c
#ifdef HAVE_SPLIT_USR
"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
#else
"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin",
#endif
It seems kind of silly, to me, and it causes problems, but there it is. After
a recompile and re-install - remembering to modify
"/usr/lib/tmpfiles.d/legacy.conf" again - these other problems all go away.
Then, there are many files in /sbin, such as "shutdown" and "halt", which are
linked to "/bin/systemctl". But now, "systemctl" is only in /usr/bin. So,
sudo ln -s /usr/bin/systemctl /bin/systemctl
These will all have to be re-linked eventually.
Other problems - it seems that, for instance, "named" tries to access the
internet before the network interface has come up, and just throws a lot of
error messages until that happens. There is no native bind9.service file, and
the process is configured from /etc/init.d/bind9 for now.
systemd-196 seems to be running cleanly now, with no errors or warnings in the
logs.
James
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
