-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
install: Rename install
-> install to-disk
, peer with to-filesystem
#226
Conversation
252e223
to
850ad43
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Possible (more simple? ) alternative: Keep |
There's a bit more rationale to why to make |
Should we keep If we expect one to happen more often then the other? |
…tem` Take the current `install` verb and change it to be `bootc install to-disk`, and then `install-to-filesystem` becomes `bootc install to-filesystem` - they are obvious peers. The main motivation here is that in the end many use cases will want nontrivial filesystem customization, and while I like having a fully opinionated builtin flow to write to a target disk, we should really think of `to-filesystem` as a fully equal peer of `to-disk`. Signed-off-by: Colin Walters <[email protected]>
I saw someone get confused and think `bootc install` could work on a filesystem. Signed-off-by: Colin Walters <[email protected]>
Similarly to previous patch for `install to-disk`, verify that the target is a directory *and* that it's a mountpoint (we can't sanely support installing to a subdirectory of a filesystem). Signed-off-by: Colin Walters <[email protected]>
850ad43
to
7997f57
Compare
That doesn't feel very different from the status quo though...and more importantly the reason there's a separate verb (i.e. CLI command) today is that the two paths have a few mutually-incompatible extra arguments (e.g. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Required since containers/bootc#226 Signed-off-by: John Eckersberg <[email protected]>
install: Rename
install
->install to-disk
, peer withto-filesystem
Take the current
install
verb and change it to bebootc install to-disk
, and theninstall-to-filesystem
becomesbootc install to-filesystem
- they are obvious peers.The main motivation here is that in the end many use cases will
want nontrivial filesystem customization, and while I like having
a fully opinionated builtin flow to write to a target disk,
we should really think of
to-filesystem
as a fully equal peerof
to-disk
.Signed-off-by: Colin Walters [email protected]
install-to-disk: Verify target is a block device
I saw someone get confused and think
bootc install
could workon a filesystem.
Signed-off-by: Colin Walters [email protected]
install-to-filesystem: Verify target is a dir+mountpoint
Similarly to previous patch for
install to-disk
, verifythat the target is a directory and that it's a mountpoint (we
can't sanely support installing to a subdirectory of a filesystem).
Signed-off-by: Colin Walters [email protected]