3 ms·

systemd broke UNIX. Everything that worked before, now is a mine field. Last week I had a SLES virtual machine refusing to boot, no network, just emergency shel

by pgtan 8y ago

systemd broke UNIX. Everything that worked before, now is a mine field. Last week I had a SLES virtual machine refusing to boot, no network, just emergency shell. The reason was a forgotten line in fstab (without nofail option of course), so systemd couldn't mount some file system. Coming from Gentoo, this is just unbelievable.

the_why_of_y 8y ago
Systemd correctly implements the "noauto" and "nofail" keywords in fstab(5) that were added in 2008 in the way they have been documented since 2010: if neither of these is specified for a filesystem, then that file system will be mounted at boot time and a failed attempt to mount that filesystem implies a boot failure. Util-linux-ng 2.14 Release Notes (09-Jun-2008) ============================================== mount(8) supports new "nofail" mount option. https://github.com/karelzak/util-linux/commit/abe3d704b6aeb6b82ff32e8599edb56525cdfd72 https://github.com/karelzak/util-linux/commit/abe3d704b6aeb6... The fact that previous init scripts gladly ignored these failures does not reflect negatively on systemd but on those init scripts. Since 2011, FreeBSD has the same options with the same behavior, except that "nofail" is called "failok". https://svnweb.freebsd.org/base?view=revision&revision=222832 https://svnweb.freebsd.org/base?view=revision&revision=22283... Add a special mount option "failok" to indicate that the administrator wants the system to proceed to boot without bailing out into single user mode, even when the file system can not be successfully mounted. By your argument, FreeBSD broke UNIX.
zlynx 8y ago
systemd refusing to boot without required drives is actually a favorite feature of mine. Ever since I had an RH AS server boot without /var mounted. It was truly lovely with a gigabyte of trash filling up / then trying to decide if it was worth merging data or just throwing it out.

by pgtan 8y ago

the_why_of_y 8y ago

Systemd correctly implements the "noauto" and "nofail" keywords in fstab(5) that were added in 2008 in the way they have been documented since 2010: if neither of these is specified for a filesystem, then that file system will be mounted at boot time and a failed attempt to mount that filesystem implies a boot failure. Util-linux-ng 2.14 Release Notes (09-Jun-2008) ============================================== mount(8) supports new "nofail" mount option. https://github.com/karelzak/util-linux/commit/abe3d704b6aeb6b82ff32e8599edb56525cdfd72 https://github.com/karelzak/util-linux/commit/abe3d704b6aeb6... The fact that previous init scripts gladly ignored these failures does not reflect negatively on systemd but on those init scripts. Since 2011, FreeBSD has the same options with the same behavior, except that "nofail" is called "failok". https://svnweb.freebsd.org/base?view=revision&revision=222832 https://svnweb.freebsd.org/base?view=revision&revision=22283... Add a special mount option "failok" to indicate that the administrator wants the system to proceed to boot without bailing out into single user mode, even when the file system can not be successfully mounted. By your argument, FreeBSD broke UNIX.

zlynx 8y ago

systemd refusing to boot without required drives is actually a favorite feature of mine. Ever since I had an RH AS server boot without /var mounted. It was truly lovely with a gigabyte of trash filling up / then trying to decide if it was worth merging data or just throwing it out.