Consider using a migration script to simplify the migration process #31
Conversation
| VAR=$VARIANT | ||
| fi | ||
|
|
||
| # Only run if on Kinoite or Silverblue |
There was a problem hiding this comment.
I believe we can generalize this a bit because more flavors will eventually be added. More importantly, we want to check that there's a booted rpm-ostree system that's capable of rebasing:
$ rpm-ostree status --booted --json | jq .deployments[].booted
|
|
||
| echo "Migrating to \"${IMG_NAME}\". Running rpm-ostree rebase & setting the kernel arguments." | ||
|
|
||
| RUNSCRIPT="RET=1; until [ \${RET} -eq 0 ]; do rpm-ostree rebase --experimental ${IMG}; RET=\$?; if [[ ! \$RET = 0 ]]; then read -r -p 'Rebasing failed. Do you want to try again? [y/N]: ' retryresponse; if [[ ! \$retryresponse =~ ^[Yy]$ ]]; then exit 1; fi; fi; done; rpm-ostree kargs --append=rd.driver.blacklist=nouveau --append=modprobe.blacklist=nouveau --append=nvidia-drm.modeset=1" |
There was a problem hiding this comment.
Can we try to enroll the secure boot key as well?
|
This is a great idea ... if it's generic enough we can just put it on the image and avoid the curling to bash altogether. Something like |
|
I've created / am working on a tool that may satisfy this PR: https://github.com/bhh32/ublue-it-cli |
Hello,
Consider adding a script like the one in this pull request to make it easier to switch to the desired image (kargs etc are set by the script)
All that would be needed is to run the following in the terminal and to answer the prompts.