Hello,
Now that Secure Boot is supported, is there any documentation that describes the specific steps required to convert a CentOS 8 system with Secure Boot to Rocky? Is this even supported?
The scenario I'm looking at is a machine running CentOS 8 that uses both SB and NBDE.
The naive approach, and I haven't tested this yet, would be to disable SB, do the conversion, then re-enable it.
Thanks for any insights.
Converting from a CentOS 8 system with secure boot to Rocky Linux 8 should "just work" while leaving secure boot enabled. I would recommend using the script that is provided here:
https://github.com/rocky-linux/rocky-tools/tree/main/migrate2rocky
-L
On Mon, 21 Mar 2022 at 14:40, ckeader via rocky rocky@lists.resf.org wrote:
Hello,
Now that Secure Boot is supported, is there any documentation that describes the specific steps required to convert a CentOS 8 system with Secure Boot to Rocky? Is this even supported?
The scenario I'm looking at is a machine running CentOS 8 that uses both SB and NBDE.
The naive approach, and I haven't tested this yet, would be to disable SB, do the conversion, then re-enable it.
Thanks for any insights.
rocky mailing list -- rocky@lists.resf.org To unsubscribe send an email to rocky-leave@lists.resf.org
Louis Abel via rocky writes:
Converting from a CentOS 8 system with secure boot to Rocky Linux 8 should "just work" while leaving secure boot enabled. I would recommend using the script that is provided here:
https://github.com/rocky-linux/rocky-tools/tree/main/migrate2rocky
I have tried the migration, and it failed completely, but it's unrelated to secure boot.
The process failed at the point where it tries to install the large bulk of packages downloaded. The reason was: a lot of packages are installed in both i686 and x86_64 form, e.g. -devel rpms. dnf then complained about a file (IIRC, a man page) that is owned by two packages. It was either libgpg-error or libgcrypt -devel, I don't remember which, and I'm nearly sure it doesn't matter which.
After that, the package list on the system was inconsistent as some rocky rpms were already installed. The migration script refused to do anything meaningful afterwards and I had to reinstall from scratch and restore the data backup.
Secure boot was not a problem, I had to disable it for PXE and re-enabled it after installation.
-
ckeader -
Louis Abel