Open
Conversation
jdoubleu
force-pushed
the
persistent-store
branch
from
1830251 to
c391359
Compare
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.
This small change introduces an option to mount a persistent drive, i.e. one that is not always created from scratch in a temporary location. This drive can be used to store persistent data across multiple boots (or tool invocations).
For example, the OVMF stores its non-volatile variables in a binary file called
NvVarson the first mounted disk.I've picked
.uefi-run.persistent.fatto be stored in the user$HOME. Not sure whether that's the best location, but at least it should always be available. Hopefully,4 MiBare enough.