That's what I have done. I now auto-correct it if it needs to be corrected.Well you could put back the symlink...
A decade of editing '/boot/config.txt' is a habit which is too hard to break, and having that open a 'DO NOT EDIT' file on Bookworm is just too annoying.
If anything is written to '/boot/config.txt' so that becomes a file it's not going to have any effect on configuration so might as well throw it away, make it a symlink again.
I can't see any downside -
- Scripts, which use 'sudo sed' incorrectly, will fail, but they fail as it is.
- Scripts, which access or edit '/boot/config.txt' correctly, will work as they always have, won't fail as they do now.
- I can edit '/boot/config.txt' as I always have and have it work.
- I don't have to edit any code which accesses '/boot/config.txt'.
Reverting to a symlink is a clear win to me.
- Bookworm behaves the same as previous versions did, even if thing are different under the hood. It's back to being as transparent as it was before the recent change.
You missed a case where it won't work: restoring config.txt/cmdline.txt from backup.
Code:
sudo cp /boot/config.bak /boot/config.txt
Statistics: Posted by thagrol — Thu Feb 01, 2024 1:43 pm