I think it's about tracking and profiling? Not wanting to be part of that is a valid choice and shouldn't be punished in any way.
Forcing a certain behavior or else you're considered suspicious is pretty twisted and dystopian. Not my problem whoever is doing this can't find a better way of separating threats from certain privacy conscious mental profiles.
In a world where code is written more and more by LLMs, these random human generated comments might hold anthropological value in some future.
Think of it akin to us studying cave paintings, wondering what whoever left their handprint on the cave wall was thinking when they did it. So these ancient lines of code might be studied in some future by our descendants, or whatever form we'll take. Interesting to perceive the author's frustration with said bit of code.
By comparison LLM generated code is neat and tidy with clean and clear comments. Plenty of that to go around for the future. No need to suck the soul out of every bit of code we currently have.
The arsons are a small blip in a country of 300 million+ people, not a national threat. This presidential concentration-camp tweet is an unhinged response no matter how you slice it.
Punishment's main goal is to discourage the behavior. If old one doesn't cut it anymore they usually make it worse, no matter the times we live in, or subject. That's how it goes, anything to stop bad behavior.
Saying this as an outsider, not even from the US.
>I need the flexibity to boot different OS kernels. AFAIK, UEFI offers no such flexibility.
Yes it does, I use it with two kernels, just have different entry for each stub in UEFI. Whenever I want to boot the non-default kernel I just hit F11 (for BIOS boot menu, on my motherboard) and choose the boot option. You just need to add the boot options in UEFI, pointing to the corresponding EFI files. They also have the kernel command line parameters baked into them and you can set your desired ones (silent boot whatever).
You can also craft a text file named startup.nsh, and if present in the root (or ~nearby) of the FAT32 EFI partition, on bootup its UEFI commands will be executed rather than the default firmware selection.
If a motherboard doesn't have enough UEFI commands in its built-in Shell (or has no built-in Shell at all), you'll want to include your own Shell.efi file right there along with any startup.nsh you might decide to deploy.
This can also be good for USB booting where the removable USB device is in regular MBR layout rather than GPT-style-partitioning.
Whether or not the whole USB drive is FAT32 or not, as long as there is a proper EFI folder in a UEFI-recognizable filesystem, you can boot to any other OS on any other filesystem, depending only on the contents of the EFI folder. Unless there is a startup.nsh for the UEFI to follow instead, then you might not even need an EFI folder. As intended. Boot floppies still work as designed too. Startup.nsh is more commonly expected to contain reference to an EFI folder that is present on some recognizable filesystem, rather than work as a lone soldier though. GPT-layout partitions are not supposed to be necessary either, it's only needed when you want more partitions than legacy BIOS will handle, or partitions that are too huge for MBR representation.
Now any alternative to GRUB would by necessity have to perform more pleasingly on legacy-compatible systems where UEFI is not enabled also, or it will remain a less-effective alternative.
Once a geek is smart enough to handle both BIOS & UEFI, the more I would be able to trust their UEFI solution.
I just have two kernels with two boot options in BIOS. I just hit F11 at boot time and choose a BIOS boot option for either kernel. Of-course, you need to add the entries in UEFI, either from UEFI shell either with some tool (efibootmgr).
This scheme also supports secure booting and silent booting. The stubs are signed after being generated.
You can have command line parameters baked into the EFISTUB.
I also have two kernels, so there's two UKIs on /efi, and I have both added as separate boot options in BIOS.
