docs: No need to manually delete bootengine.cpio any more #420
Conversation
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
Dracut is no longer run in a chroot, so bootengine.cpio is created alongside the other build files rather than in the board root and is therefore no longer persisted. To be honest, there was probably no need to delete it anyway, as it would have been overwritten. It seems like this was just a precaution. Signed-off-by: James Le Cuirot <[email protected]>
2 tasks
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://lemon-wave-085522403-420.westeurope.1.azurestaticapps.net |
ader1990
reviewed
May 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No need to manually delete bootengine.cpio any more
Dracut is no longer run in a chroot, so bootengine.cpio is created alongside the other build files rather than in the board root and is therefore no longer persisted.
To be honest, there was probably no need to delete it anyway, as it would have been overwritten. It seems like this was just a precaution.
sys-kernel/bootengine may end up being installed to the SDK rather than the board root, but that hasn't happened yet.