On Wed, 06.05.15 15:50, Harald Hoyer ([email protected]) wrote: > Works for me... booted with "ro" on the kernel cmdline: > > $ systemctl status systemd-fsck-root.service > ● systemd-fsck-root.service - File System Check on Root Device > Loaded: loaded (/usr/lib/systemd/system/systemd-fsck-root.service; static; > vendor preset: disabled) > Active: inactive (dead) since Mi 2015-05-06 15:37:58 CEST; 1min 44s ago > Docs: man:systemd-fsck-root.service(8) > Main PID: 144 (code=exited, status=0/SUCCESS) > CGroup: /system.slice/systemd-fsck-root.service
I think tis is really confusing for the admin. he now thinks that this is actually the exit status of the root fsck, but it's atcually just /bin/true. I am pretty sure it's best if we say that systemd-fsck-root.service really always is the fsck of the root fs, regardless if booted with an initrd or not, even if this might mean slightly suboptimal deps within the initrd if you have multiple file systems to mount that early. This would certainly be the friendliest, most discoverable option for admins. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
