You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
systemd 227[0] enforces that /etc/mtab isn't a regular file and freezes the system during boot if it is. This is only a temporary issue as the behavior is patched[1] away in the next version of systemd.
A temporary workaround is to create a symlink instead in init.drbl:
diff --git a/setup/files/misc/init.drbl b/setup/files/misc/init.drbl
index 73ea98a..f8e5e8d 100755
--- a/setup/files/misc/init.drbl+++ b/setup/files/misc/init.drbl@@ -352,11 +352,7 @@ maybe_break drbl_postnfs
rm -f /etc/mtab /etc/mtab~ /etc/mtab~~ /etc/nologin
# if, for any reason, mtab was not synced with what it should be, Sync it.
-while read ilist; do- # skip the "rootfs / rootfs rw 0 0" - [ -n "$(echo $ilist | grep -E "^rootfs \/ rootfs .*")" ] && continue- echo $ilist >> /etc/mtab-done < /proc/mounts+ln -sf /proc/mounts /etc/mtab
# umount the useless /initrd/proc and /initrd if they exist.
for i in /initrd/proc /initrd; do
I'm not familiar enough with the internals to know if this creates any issues (due to rootfs not being removed), but it works in our current setup.
systemd 227 is currently used in Debian Stretch and Sid.
systemd 227[0] enforces that /etc/mtab isn't a regular file and freezes the system during boot if it is. This is only a temporary issue as the behavior is patched[1] away in the next version of systemd.
A temporary workaround is to create a symlink instead in init.drbl:
I'm not familiar enough with the internals to know if this creates any issues (due to rootfs not being removed), but it works in our current setup.
systemd 227 is currently used in Debian Stretch and Sid.
[0] http://lists.freedesktop.org/archives/systemd-devel/2015-October/034509.html
[1] systemd/systemd@5dea1c1
The text was updated successfully, but these errors were encountered: