<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> du -sh /usr/lib/systemd/ 13M /usr/lib/systemd/ du -sh /usr/lib64/systemd 6.4M /usr/lib64/systemd i.e. about 20M with most stuffs of systemd package installed. Is it too large for initrd? Idk about your setup, might be embedded flash.. <div class="moz-cite-prefix">On 9/23/24 12:03, <a class="moz-txt-link-abbreviated" href="mailto:Dharma.B@microchip.com">Dharma.B@microchip.com</a> wrote: </div> <blockquote type="cite" cite="mid:54d87455-777c-4d3a-a785-1e1cfb79aff3@microchip.com"> <pre class="moz-quote-pre" wrap="">Hi Team, I'm exploring the possibility of splitting the systemd binary to optimize boot time before and after switching to the root filesystem. I’m aware that the systemd binary is quite large and may not fit in the initramfs, but is it feasible to have a minimal version of systemd that can invoke essential services and continue tracking them after transitioning to the main root filesystem? This approach is aimed at speeding up the boot process. I’m unsure if this is possible, which is why I’m seeking guidance from the systemd mailing list. </pre> </blockquote> </body> </html>