@mitsunee @CauseOfBSOD @LivingCooki some of them yes, most of them no -- iirc systemd-{boot,sysusers,tmpfiles,udev,ukify} and kernel-install can

[navi@social.vlhl.dev]

@mitsunee @CauseOfBSOD @LivingCooki

some of them yes, most of them no -- iirc systemd-{boot,sysusers,tmpfiles,udev,ukify} and kernel-install can?

but the more important bits (like logind) nope, and require a fork that is basically systemd as a whole except with 90% of it disabled with `#if 0`

[daemonspudguy@app.wafrn.net]

@LivingCooki@void.lgbt @navi@social.vlhl.dev @mitsunee@mk.absturztau.be @CauseOfBSOD@wetdry.world

I'm not even entirely sure why systemd-boot is even considered part of systemd when it's just the continuation of Gummiboot and is a bootloader as a result, and thus literally cannot be running at the same time as systemd because it's a bootloader.

[livingcooki@void.lgbt]

@daemonspudguy @mitsunee @navi @CauseOfBSOD I assume because systemd wants to be a more complete software suite that handles most stuff related to booting into a user, so it does make sense to also provide a bootloader (when they for some reason aren't satisfied with just recommending software they don't make themselves)