Booster and encrypt vs. sd-encrypt hook

[rieje]

I've been reading about kernel parameters from the Arch Wiki.

Booster supports e.g. rd.luks.uuid=, does it mean it supports sd-crypt hooks only and not not encrypt hooks (e.g. for me, cryptdevice= that I had previous for mkinitcpio didn't work)? Or is encrypt vs. sd-encrypt hook only a mkinitcpio distinction and booster (and perhaps other initramfs generators) may support one, style, both, or maybe even their own?

Would it be accurate to say booster only supports kernel parameters read by systemd-cryptsetup-generator? I'm not sure how much of an assumption the Arch Wiki makes regarding mkinitcpio being the initramfs generator it talks about kernel parameters. I realize mkinitcpio is the default but it also seems kernel parameters is a standard that should be followed by initramfs generators.

[c3Ls1US]

@rieje Currently, booster does not implement hooks as a feature and it's not clear whether it will be. Also, because booster supports some boot time kernel parameters from mkinitcpio or systemd-cryptsetup this does not imply hooks like sd-crypt will be supported