This sounds like a good option. I was also thinking of solutions and
my idea was the following:
Put a template for cmdline.txt and config.txt (e.g cmdline.txt.in
<http://cmdline.txt.in> and config.txt.in <http://config.txt.in>)
somewhere in the /etc folder (e.g. /etc/raspi3-firmware). Within the
template there are keywords that the raspi3-firmware hook (or better
50-raspi3-firmware) will replace (sed) when it generates the files for
/boot/firmware.
I agree that this is the most user-friendly solution.
This is still a bit cumbersome compared to the offerings of e.g.
grub2. But I guess it is a (too) big effort to reach the level of grub2.
Yes, I've been experimenting with grub2 on the RPi but had to abandon
the idea after quete some very frustrating experiences.
Regards,
Arjen Balfoort
