Support for rc.local AND dietpi/postboot.d hooks for expansion, generic support for mmcblkX where X is determined at runtime #163
Conversation
This file contains 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
added 3 commits
September 18, 2020 14:58
…tPi (should still work with rc-local stuff)
belveder79
changed the title
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.
This fix enables expansion of dietPi images at next boot (tested with RockPro64 and Dietpi 6.32) through the use of postboot hooks instead of rc.local (however, the original one should stay intact).
Furthermore it moves to a runtime check for the correct /dev/mmcblkXpY numbers which should ideally work with different configurations (even if root is /dev/mmcblk2p1 as in the case of RockPro64 for example)