Ensure the encrypted swapfile is always created #3895
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
NeilGerring
force-pushed
the
fix-encrypted-swapfile
branch
from
fa051f8
to
bd62266
Compare
…n a reboot Signed-off-by: Neil Gerring <ng@neilgerring.co.uk>
NeilGerring
force-pushed
the
fix-encrypted-swapfile
branch
from
bd62266
to
a745d00
Compare
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.
- What I did
Ensured the encrypted swap file would be created after the initial boot.
- How I did it
Changed the shell script to have a else if that would re-create the swapfile if the provided path existed and the file size didn't need to be changed.
- How to verify it
Reboot a fresh virtual machine and then run
swapon --show.- Description for the changelog
Ensure a encrypted swap file is always created after a reboot.
- A picture of a cute animal (not mandatory but encouraged)