[systemd-devel] Second (erroneous) check of rootfs?
Harald Hoyer
harald.hoyer at gmail.com
Thu Jan 8 08:12:25 PST 2015
On 08.01.2015 16:55, Lennart Poettering wrote:
> On Thu, 08.01.15 16:34, Harald Hoyer (harald.hoyer at gmail.com) wrote:
>
>> IMHO
>>
>> systemd-fsck-root.service should be removed entirely and generated by the
>> fstab-generator in the real root like all the other mount points.
>
> Well, this service *is* special, it needs to run before the other
> fsck, and it needs different code to find the device to operate on,
> since udev isn't up yet. It will have to stay I figure...
>
>> fstab-generator should create systemd-fsck-root.service for the /sysroot
>> mountpoint in the initrd, which then will be serialized.
>
> Not a fan of overriding things like that... I would prefer to run the
> same unit files in the initrd and on the host...
>
> What about this: we add some code to systemd-fsck that when run
> without parameters, and within an initrd, it will check the host root?
not sure, if I can follow. When run without parameters and within the initrd,
it should do nothing. Anything can be root. Maybe it's NFS... and it is not
mounted yet.
A fake unit could do the same job.
More information about the systemd-devel
mailing list