raspberrypi: use /boot/firmware path throughout our scripts#7944
Merged
raspberrypi: use /boot/firmware path throughout our scripts#7944
Conversation
Since we dropped Debian Bullseye support, including the legacy RPi kernel/firmware stack with /boot isntead of /boot/firmware FAT partition, we do not need to rely on the symlinks for backwards compatibility anymore. Use new paths, and do not create symlinks on fresh images and kernel migration anymore. Exclude only CHANGELOG.txt and (pre-)patches: The latter run on older systems as well, and the kernel migration is enforced only at the end of DietPi v10.0 patches. Signed-off-by: MichaIng <micha@dietpi.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since we dropped Debian Bullseye support, including the legacy RPi kernel/firmware stack with /boot isntead of /boot/firmware FAT partition, we do not need to rely on the symlinks for backwards compatibility anymore.
Use new paths, and do not create symlinks on fresh images and kernel migration anymore. Exclude only CHANGELOG.txt and (pre-)patches: The latter run on older systems as well, and the kernel migration is enforced only at the end of DietPi v10.0 patches.