-
Notifications
You must be signed in to change notification settings - Fork 88
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This is in general for us right now a no-op, but is closer to technically correct. In ostree the "merge deployment" concept started out as "deployment we use for the original /etc" which *may be different* from the booted deployment. For example, when one wants to do a "factory reset", we want to start from a fresh /etc. The other important case here is when we're doing a fresh install (or into a new stateroot) there may be no merge deployment at all! It wouldn't be correct to look at `/`. We only sidestep this issue right now because the install logic bypasses this to directly gather kargs...and doesn't use the same `deploy` API as inplace updates. But we want to get closer to doing things that way. Signed-off-by: Colin Walters <[email protected]>
- Loading branch information
Showing
3 changed files
with
31 additions
and
13 deletions.
There are no files selected for viewing
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
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
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