[systemd-devel] Questions about initrd environment services and IgnoreOnIsolate

[Carolina Jubran]

Hello!
Following up on my previous message about ensuring my drivers are loaded in initrd. It was suggested to add Before=initrd-switch-root.target and consider my systemd service started only when the drivers are fully loaded.
What is the correct way to ensure my service is not considered started until the drivers are loaded?
Any guidance would be greatly appreciated.
Thank you, Carolina Jubran

________________________________
From: Carolina Jubran <cjubran at nvidia.com>
Sent: Thursday, May 16, 2024 9:16 AM
To: killermoehre at gmx.net <killermoehre at gmx.net>; systemd-devel at lists.freedesktop.org <systemd-devel at lists.freedesktop.org>
Subject: Re: [systemd-devel] Questions about initrd environment services and IgnoreOnIsolate

Hi

The modules need to be loaded using the services because there are several things that still do not autoload their modules.
For instance, attempting an NFS mount over RDMA will fail unless the RDMA NFS module is pre-loaded.

Thank you,
Carolina Jubran
________________________________
From: systemd-devel <systemd-devel-bounces at lists.freedesktop.org> on behalf of killermoehre at gmx.net <killermoehre at gmx.net>
Sent: Monday, May 13, 2024 11:33 PM
To: systemd-devel at lists.freedesktop.org <systemd-devel at lists.freedesktop.org>
Subject: Re: [systemd-devel] Questions about initrd environment services and IgnoreOnIsolate

External email: Use caution opening links or attachments

Hi,

may I ask why you need your own .service to load the module instead of using modules-load.d and modprobe.d? Just to understand your problem better.

BR
Silvio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20240522/8053701c/attachment-0001.htm>