Hi Rich
I am posting things about this script test here at your request
I disagree with your assessment as I think both of us have been tricked with what is loading. I now believe that somehow the booting process....is reading elements from more that one boot list
Here is my alleged proof that you are mislead. That is...mylocale is still loading when I told it not to. Image expires in one month
https://i.postimg.cc/B6wNTV6L/gremlin2.png1) onboot.lst has no mention of mylocale*
2) bootloader string has no mention of UTF setting nor timezone setting
3) but apps onboot maintenance tells a different story
4) ls installed command confirms that mylocale has loaded.....and that means we are tricked by the bash script
ie I have yet to confirm that script fails
FWIW here is my new bootloader.....and I am booting 17b
menuentry "17a" {
linux /boot/vmlinuz17 home=LABEL=tc1 tce=/mnt/sdb1/17/tce waitusb=10 quiet lang=en_AU.UTF-8 tz=Australia/Perth blacklist=snd-hda-intel nozswap
initrd /boot/amd-ucode.img /boot/rootfs17.gz /boot/modules17.gz
}
menuentry "17b" {
linux /boot/vmlinuz17 home=LABEL=tc1 tce=/mnt/sdb1/17/tce waitusb=10 quiet blacklist=snd-hda-intel nozswap
initrd /boot/amd-ucode.img /boot/rootfs17.gz /boot/modules17.gz
}
and I have only just discovered that I can no longer use a boot code for lst=name.lst