sdubby does not exist

"grub2" ?

Strictly speaking, sd-boot has a 32-bit variant. I think it isn't tested much, and it's fine not to even try it from Anaconda, but it exists.

> `env_prune=['MALLOC_PERTURB_']` Why is this needed?

`updateloaderentries` is from https://bugzilla.redhat.com/show_bug.cgi?id=2134972. As I wrote the ticket, please let's not do this at all. `updateloaderentries` is modifying some existing on-disk files. It would be nicer to just write the with the right contents from the start. But if we can't do that, then a bit of python should good enough: ```py def clean_up_loader_entry(filename, args): with open(filename, 'r+') as f: lines = [] for line in f: if line.startswith('options'): filtered = (opt for opt in line.split()[1:] if not opt.startswith('inst.') and not opt.startswith('BOOT_IMAGE')) lines += [' '.join((f'options {args}', *filtered)) + '\n'] else: lines += [line] f.seek(0) f.write(''.join(lines)) f.truncate() ```

"for now we assume" — the installer is in full control, so there is no need hedge like this. Instead: "When the Linux installer is creating the partitions, it can create the ESP as large as needed."

"its" Hmm, so this description doesn't sound right. "second boot menu": I guess you're thinking about the firmware menu, but generally it wouldn't be shown, so for normal use it's just "boot menu". Also, the kerel doesn't load the initrd, it happens earlier. Kernels with an efi stub also usually contain their own commandline, so injection of the parameters is an optional step… So this text would require some editing. But the bigger issue is that a description of systemd-boot features shouldn't be done here. Please instead refer to some docs (https://www.freedesktop.org/software/systemd/man/systemd-stub.html, https://www.freedesktop.org/software/systemd/man/systemd-boot.html ?). The feature set and details of operation of sd-stub/boot can change over time. I think a one-sentence description of systemd-boot would be enough.

ditto

I see that the `ZIPL` class has an ` update_bls_args()` function that does something similar. Maybe there could be a common helper instead of having a separate script?