Everybody who noticed the change in Bookworm /boot/cmdline.txt to /boot/firmware/cmdline.txt and relied on the link now is pi**ed and has to update the code againWell you could put back the symlink... but once you know about the change, it is easier to just edit files in the new location. Plus if you revert the system to using the symlink, you have to keep checking to see if an update quietly stepped on it again.I don't know how many users already updated their tools with the fixed code which now has to be updated again
That's for me a very unprofessional way to migrate some code change.
I don't know how many users already updated their tools with the fixed code which now has to be updated again I disagree.
If they were relying on the symlink, they were doing it wrong. And if they were relying on the link most of their code likely wouldn't have needed to be updated anyway.
The proper fix is to identify which directory is correct (/boot or /boot/firmware) on the OS you are running on and access the files in that directory. Something that's likely trivial in most languages - it certainly is in bash and python.
That said, could the latest change have been handled and notified to us in a better way? Yes, of course it could have.
Statistics: Posted by thagrol — Thu Feb 01, 2024 2:14 am