Hi I think we should rename our hook from “raspi3-firmware” to > “50raspi3-firmware”. update-initramfs uses run-parts(8) to invoke hooks, so > you could then ship a hook with a higher number which would be guaranteed > to run after the raspi3-firmware hook. > > Let me know if that sounds good, and I’ll prepare a package upload. >
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 and 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. An advanced user can then customize the templates in the /etc folder and since those are config files the modified templates will not get overwritten during a package update. Upon the next generation of the config files the new templates will get applied. 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. Best regards Matthias
