On Thu, 26 Dec 2024 23:54:47 +0600 Roman Valov <[email protected]>
wrote:
> - In Debian: dracut invokes kernel-install (via a post-update hook)
Only if systemd-boot is used.
> - In non-Debian: kernel-install invokes dracut
Oh, really? Interesting. Could you please expand a bit on this?
Aligning with other distros might make sense.
> 2) Invocation of post update hooks is opt-out. Personally, I have
> bumped into unexpectedly updated boot images several times when
> switching between distros while testing dracut workflows.
Please note that you're currently doing something that's a bit "weird",
that's arguably outside Debian's scope. I agree that it should
eventually be fixed, but having a working setup for "regular" Debian
users should in my opinion be the priority.
> 3) Setting environment variable on the command line is clunky and
> shell completion does not help with it.
man is always your friend.
> Hence it is proposed to introduce a wrapper intended to invoke hooks
> and possibly deal with Debian workflows integration in general. The
> wrapper could then be considered a subject to adhering policies. And
> original dracut executable should remain "lower-level" tool. Which
> usage experience does not differ from non-Debian world.
Dracut is a tool originating from other distros. According to what
you're saying, other distros consider dracut to be "low level". So,
arguably, dracut shouldn't be running bootloader hooks from
/etc/initramfs/post-update.d, since, if I understand correctly, dracut
isn't the initramfs builder, but kernel-install is. Am I correct?
This honestly doesn't sound correct to me, since as far as I know
kernel-install is fairly new and Dracut can be used standalone.
But if things have changed, and Dracut isn't to be used "standalone"
anymore, then maybe kernel-install instead should be patched to run
bootloader hooks?
