Rename initoverlayfs-setup to initoverlayfs #70
Merged
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
This binary is going to have two modes: initoverlayfs --systemd which is the recommended one. And: initoverlayfs where we use initoverlayfs's built-in init system, this is for use-cases where we require high levels of optimization, such as in the Automotive use case, this requires storage drivers to be built directly into the kernel so the kernel can do storage initialization, this built-in initoverlayfs init system will not do udev type things, at least initially. Signed-off-by: Eric Curtin <[email protected]>
ericcurtin
requested review from
rhatdan,
dougsland and
masneyb
as code owners
dougsland
approved these changes
Feb 19, 2024
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 binary is going to have two modes:
initoverlayfs --systemd
which is the recommended one. And:
initoverlayfs
where we use initoverlayfs's built-in init system, this is for use-cases where we require high levels of optimization, such as in the Automotive use case, this requires storage drivers to be built directly into the kernel so the kernel can do storage initialization, this built-in initoverlayfs init system will not do udev type things, at least initially.