It was <2025-05-05 pon 10:39>, when Kaizaad Bilimorya wrote:
> On Mon, May 5, 2025 at 10:03 AM Andrei Borzenkov <arvidj...@gmail.com>
> wrote:
>
>> On Mon, May 5, 2025 at 4:58 PM Kaizaad Bilimorya <kaiz...@sharcnet.ca>
>> wrote:
>> >
>> > Hello Silvio,
>> > Thank you for your response.
>> > We're using Ansible to automate some tasks so it is easier (and more
>> reliable) to add/remove mount unit files than having to parse the fstab for
>> our specific mount options.
>> > And as the Systemd documentation says "For tooling, writing mount units
>> should be preferred over editing /etc/fstab" which is something I agree
>> with. I need the
>> > "x-initrd.mount" option since we are setting up some custom Dracut hooks
>> early in the boot process for the local disk and want this disk mounted
>> before switch-root.
>> >
>>
>> You do not need "x-initrd.mount".
>
> Isn't the purpose of the "x-initrd.mount" option to have a filesystem
> mounted in the initrd? Which is what I need.

Yes - it tells fstab-generator running in initrd to generate a unit for
the entry.

Not exactly - this option tells systemd running on the rootfs as the
system manager (see call to fstab_is_extrinsic in mount.c) to ignore a
mount created in initrd regardless of what tools were uesd to mount it.

-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

Attachment: signature.asc
Description: PGP signature

Reply via email to