Thanks for the link Brian. Very valuable.
Have you discussed moving
cntvct-log
to systemd-analyze? IMHO, systemd can have better control when the target is
reached to record the wall time.
Umut
From: systemd-devel on behalf of
Brian Masney
Date: Thursday, 26 September 2024 at 03:07
To: dha
On Wed, Sep 25, 2024 at 03:53:36PM +, dharm...@microchip.com wrote:
> yes something similar to this, I will experiment this and get back to you.
>
> and I think since the egt service and its libraries depend on the full
> rootfs, integrating initramfs might not provide significant benefits in
25.09.2024 18:28, aplanas wrote:
Hi!
An user have /home in a different encrypted partition via pcrlock. After
the initrd, during the normal boot process, the systemd-cryptsetup
generator is reading this file to open the devices in /dev/mapper/$name.
But this is happening before /var gets mounted
Hi Serenissi,
Thanks for your valuable comments.
> which means you won't be able to run egt in initfamfs until main rootfs
> is mounted anyways?
Yes, egt depends on libraries and examples under /usr/share in rootfs.
> In theory you can use RootImage to point to /sysroot and start egt after
>
Hi!
An user have /home in a different encrypted partition via pcrlock. After
the initrd, during the normal boot process, the systemd-cryptsetup
generator is reading this file to open the devices in /dev/mapper/$name.
But this is happening before /var gets mounted, and this contains the
pcrloc
If you want to keep the egt service running from early initramfs into
the new roootfs then see https://systemd.io/ROOT_STORAGE_DAEMONS
> Since systemd v255, alternatively the SurviveFinalKillSignal=yes unit
option can be set
If the egt service can work very early in main rootfs then you can a
Biblical Coventant:
God will not Allow "daemon" name in Linux 7.0 as most as possible.
More Anointing in Linux 7.0 at least.
