replacing boot loader -- how?, and to what?
I need to replace my boot loader, as one of the upgrades performed by to upgrade my libraries removed the 32bit libs that lilo upon which lilo required to install a new OS was removed as not being necessary. Unfortunately, it was needed to install a new kernel, so while my system can continue to run I can't upgrade to a new kernel. I think Grub is the current (?) recommended boot loader (?) but I really don't know. How can I install a loader lthat can let me boot as well as select what kernel image at boot time as well as add parameters to the boot line (like adding kenel flags and/or whether or not to start in a rescue mode, etc. Of course once I try, any major mistake might prohibit a retry...but maybe there are suggestions on how to prepare for that possibility? thanks!
On Sunday, 3 April 2022 11:14:37 AM ACST L A Walsh wrote:
I need to replace my boot loader, as one of the upgrades performed by to upgrade my libraries removed the 32bit libs that lilo upon which lilo required to install a new OS was removed as not being necessary. Unfortunately, it was needed to install a new kernel, so while my system can continue to run I can't upgrade to a new kernel.
I think Grub is the current (?) recommended boot loader (?) but I really don't know. How can I install a loader lthat can let me boot as well as select what kernel image at boot time as well as add parameters to the boot line (like adding kenel flags and/or whether or not to start in a rescue mode, etc. Of course once I try, any major mistake might prohibit a retry...but maybe there are suggestions on how to prepare for that possibility?
thanks!
Hi Linda. 'zypper in grub2' as root should do the trick. It will search for and automatically setup booting based on the partitions found and the images located. You can adjust boot options (kernel/display params etc) by editing /etc/ default/grub and running (as root) update-bootloader (check man update- bootloader for options after installing), or you can do it the "easy" way via YaST Grub2 also has options for UEFI and TPM support if you need them (as far as I know, lilo has neither). Regards, Rodney. -- ================================================================================================================== Rodney Baker rodney.baker@iinet.net.au ==================================================================================================================
On 2022-04-03 03:44, L A Walsh wrote:
I need to replace my boot loader, as one of the upgrades performed by to upgrade my libraries removed the 32bit libs that lilo upon which lilo required to install a new OS was removed as not being necessary. Unfortunately, it was needed to install a new kernel, so while my system can continue to run I can't upgrade to a new kernel.
I think Grub is the current (?) recommended boot loader (?) but I really don't know. How can I install a loader lthat can let me boot as well as select what kernel image at boot time as well as add parameters to the boot line (like adding kenel flags and/or whether or not to start in a rescue mode, etc. Of course once I try, any major mistake might prohibit a retry...but maybe there are suggestions on how to prepare for that possibility?
Yes, grub-2 is the default boot loader, at can do what you ask for. You can use YaST, module "Boot Loader" to adjusts its settings. Yast trick: to force yast into writing/updating all boot files, just change the timeout (tab "Bootloader Options") just one second up or down, then accept to exit. I can never be sure i have done everything right, so better be prepared. Download the rescue image now: http://download.opensuse.org/distribution/leap/15.3/live/openSUSE-Leap-15.3-... and put it on an USB stick (a 4GB stick is fine if you can find it). If the stick is seen as /dev/sdX, then a plain: cp openSUSE-Leap-15.3-Rescue-CD-x86_64-Media.iso /dev/sdX will do. To perform a rescue, you boot that USB stick, open a terminal, and then "su -" to root. You mount the partition to be rescued. Suppose it is mounted in /rescued, then do: mount --bind /proc /rescued/proc mount --bind /sys /rescued/sys mount --bind /dev /rescued/dev chroot /rescued Then you can work on that terminal as it were the operating system of the partition to be rescued. You can run "yast", but in text mode, not graphics (because it fails and I have not figured it out). -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
participants (3)
-
Carlos E. R.
-
L A Walsh
-
Rodney Baker