[opensuse-factory] Where do you expect documentation for bootloader update after kernel upgrade?
Hi, I have question for middle experienced user of opensuse. Often is quite useful for users to have documentation when kernel upgrade fail because bootloader update failed to different reasons. Or also what they need manually edit if something goes bad as in https://bugzilla.novell.com/show_bug.cgi?id=224476. So my question where you expect documentation about this (some howto or FAQ and also describe process what happen during it)? Manpage for update-kernel script? Or some comments in some config file? Please expect that bootloader is not only grub, but also for other architectures (powerLilo etc.). Josef Reidinger, perl-Bootloader maintainer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Josef Reidinger wrote:
Hi, I have question for middle experienced user of opensuse. Often is quite useful for users to have documentation when kernel upgrade fail because bootloader update failed to different reasons. Or also what they need manually edit if something goes bad as in https://bugzilla.novell.com/show_bug.cgi?id=224476. So my question where you expect documentation about this (some howto or FAQ and also describe process what happen during it)? Manpage for update-kernel script? Or some comments in some config file? Please expect that bootloader is not only grub, but also for other architectures (powerLilo etc.). Josef Reidinger, perl-Bootloader maintainer
Comments in the config files would be helpful as rescue disks have no man pages or other help and that would normally be where you will be trying to fix the problem from. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dave Plater wrote:
Josef Reidinger wrote:
Hi, I have question for middle experienced user of opensuse. Often is quite useful for users to have documentation when kernel upgrade fail because bootloader update failed to different reasons. Or also what they need manually edit if something goes bad as in https://bugzilla.novell.com/show_bug.cgi?id=224476. So my question where you expect documentation about this (some howto or FAQ and also describe process what happen during it)? Manpage for update-kernel script? Or some comments in some config file? Please expect that bootloader is not only grub, but also for other architectures (powerLilo etc.). Josef Reidinger, perl-Bootloader maintainer
Comments in the config files would be helpful as rescue disks have no man pages or other help and that would normally be where you will be trying to fix the problem from. Regards Dave P
Comments in configfile have disadvantage, that it messed that configfile and cannot be so long. I think e.g. debian menu.lst is good example how unreadable it can be. But maybe good idea is add to configfile See section where you specify some plain text file about it. example debian configfile menu.lst: # menu.lst - See: grub(Valím oči! Super!, info grub, update-grub(Valím oči! Super! # grub-install(Valím oči! Super!, grub-floppy(Valím oči! Super!, # grub-md5-crypt, /usr/share/doc/grub # and /usr/share/doc/grub-doc/. ## default num # Set the default entry to the entry number NUM. Numbering starts from 0, and # the entry number 0 is the default if the command is not used. # # You can specify 'saved' instead of a number. In this case, the default entry # is the entry saved with the command 'savedefault'. # WARNING: If you are using dmraid do not use 'savedefault' or your # array will desync and will not let you boot your system. default 0 ## timeout sec # Set a timeout, in SEC seconds, before automatically booting the default entry # (normally the first entry defined). timeout 3 ## hiddenmenu # Hides the menu by default (press ESC to see the menu) hiddenmenu # Pretty colours #color cyan/blue white/blue ## password ['--md5'] passwd # If used in the first section of a menu file, disable all interactive editing # control (menu entry editor and command-line) and entries protected by the # command 'lock' # e.g. password topsecret # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/ # password topsecret # # examples # # title Windows 95/98/NT/2000 # root (hd0,0) # makeactive # chainloader +1 # # title Linux # root (hd0,1) # kernel /vmlinuz root=/dev/hda2 ro # # # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST ### BEGIN AUTOMAGIC KERNELS LIST ## lines between the AUTOMAGIC KERNELS LIST markers will be modified ## by the debian update-grub script except for the default options below ## DO NOT UNCOMMENT THEM, Just edit them to your needs ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=UUID=4b5235e0-8b0f-4baf-a0a3-d2c55c055f3f ro ## Setup crashdump menu entries ## e.g. crashdump=1 # crashdump=0 ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,2) ## should update-grub create alternative automagic boot options ## e.g. alternative=true ## alternative=false # alternative=true ## should update-grub lock alternative automagic boot options ## e.g. lockalternative=true ## lockalternative=false # lockalternative=false ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=791 resume=/dev/hda5 # defoptions=quiet splash ## should update-grub lock old automagic boot options ## e.g. lockold=false ## lockold=true # lockold=false ## Xen hypervisor options to use with the default Xen boot option # xenhopt= ## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 ## altoption boot targets option ## multiple altoptions lines are allowed ## e.g. altoptions=(extra menu suffix) extra boot options ## altoptions=(recovery) single # altoptions=(recovery mode) single ## controls how many kernels should be put into the menu.lst ## only counts the first occurence of a kernel, not the ## alternative kernel options ## e.g. howmany=all ## howmany=7 # howmany=all ## should update-grub create memtest86 boot option ## e.g. memtest86=true ## memtest86=false # memtest86=true ## should update-grub adjust the value of the default booted system ## can be true or false # updatedefaultentry=false ## should update-grub add savedefault to the default options ## can be true or false # savedefault=false ## ## End Default Options ## title Ubuntu 7.10, kernel 2.6.22-15-generic root (hd0,2) kernel /boot/vmlinuz-2.6.22-15-generic root=UUID=4b5235e0-8b0f-4baf-a0a3-d2c55c055f3f ro quiet splash initrd /boot/initrd.img-2.6.22-15-generic quiet title Ubuntu 7.10, kernel 2.6.22-15-generic (recovery mode) root (hd0,2) kernel /boot/vmlinuz-2.6.22-15-generic root=UUID=4b5235e0-8b0f-4baf-a0a3-d2c55c055f3f ro single initrd /boot/initrd.img-2.6.22-15-generic title Ubuntu 7.10, kernel 2.6.22-14-generic root (hd0,2) kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=4b5235e0-8b0f-4baf-a0a3-d2c55c055f3f ro quiet splash initrd /boot/initrd.img-2.6.22-14-generic quiet title Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode) root (hd0,2) kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=4b5235e0-8b0f-4baf-a0a3-d2c55c055f3f ro single initrd /boot/initrd.img-2.6.22-14-generic title Ubuntu 7.10, memtest86+ root (hd0,2) kernel /boot/memtest86+.bin quiet ### END DEBIAN AUTOMAGIC KERNELS LIST # This is a divider, added to separate the menu items below from the Debian # ones. title Other operating systems: root # This entry automatically added by the Debian installer for a non-linux OS # on /dev/sda1 title Windows Vista/Longhorn (loader) root (hd0,0) savedefault makeactive chainloader +1 # This entry automatically added by the Debian installer for a non-linux OS # on /dev/sda2 title Windows Vista/Longhorn (loader) root (hd0,1) savedefault makeactive chainloader +1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2008-11-06 at 17:41 +0100, Josef Reidinger wrote:
and cannot be so long. I think e.g. debian menu.lst is good example how unreadable it can be. But maybe good idea is add to configfile See section where you specify some plain text file about it.
Exactly. You could also add a very small file to /boot, like readme.suse, saying where the various docs can be found: grub, bootloader, whatever, and very briefly the rescue options: there is a rescue option in the dvd documented [where], etc. All in 1 or 2 kilobytes of text: remember that some of us use a separate and small boot partition. Symlinks might not be useful, if the user is reading using a rescue system. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkULLwACgkQtTMYHG2NR9WyYgCfR3srNdMvZZtJJInU1c0BBxd9 SXIAnjz7wSDv4gfacNIDW3foHPWq087A =JzJY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
This is a great point. I had booloader and kernel update issues in the past and despite my knowledge of linux, this was tough to fix. - How to and FAQ +1 - manpage -1 because I wouldn't even know what to look for - comments in the config file: same, One wouldn't necessarily know where to look for All one would have in the best case is a bootable cd or dvd of opensuse + access to the web. Once the bootloader or kernel update is screwed up, you are far from manpages or even looking at config files. Erik.
-----Original Message----- From: Josef Reidinger [mailto:jreidinger@suse.cz] Sent: November 6, 2008 9:15 AM To: opensuse-factory Subject: [opensuse-factory] Where do you expect documentation for bootloader update after kernel upgrade?
Hi, I have question for middle experienced user of opensuse. Often is quite useful for users to have documentation when kernel upgrade fail because bootloader update failed to different reasons. Or also what they need manually edit if something goes bad as in https://bugzilla.novell.com/show_bug.cgi?id=224476. So my question where you expect documentation about this (some howto or FAQ and also describe process what happen during it)? Manpage for update-kernel script? Or some comments in some config file? Please expect that bootloader is not only grub, but also for other architectures (powerLilo etc.). Josef Reidinger, perl-Bootloader maintainer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Josef Reidinger wrote:
Hi, I have question for middle experienced user of opensuse. Often is quite useful for users to have documentation when kernel upgrade fail because bootloader update failed to different reasons. Or also what they need manually edit if something goes bad as in https://bugzilla.novell.com/show_bug.cgi?id=224476. So my question where you expect documentation about this (some howto or FAQ and also describe process what happen during it)? Manpage for update-kernel script? Or some comments in some config file? Please expect that bootloader is not only grub, but also for other architectures (powerLilo etc.). Josef Reidinger, perl-Bootloader maintainer
I think from reading the only other reply and looking at the debian config, the conclusion could be drawn that a text grub howto in the boot directory would be in order, lilo.conf is easy to edit but I find grub very complicated. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dave Plater schreef:
Josef Reidinger wrote:
Hi, I have question for middle experienced user of opensuse. Often is quite useful for users to have documentation when kernel upgrade fail because bootloader update failed to different reasons. Or also what they need manually edit if something goes bad as in https://bugzilla.novell.com/show_bug.cgi?id=224476. So my question where you expect documentation about this (some howto or FAQ and also describe process what happen during it)? Manpage for update-kernel script? Or some comments in some config file? Please expect that bootloader is not only grub, but also for other architectures (powerLilo etc.). Josef Reidinger, perl-Bootloader maintainer
I think from reading the only other reply and looking at the debian config, the conclusion could be drawn that a text grub howto in the boot directory would be in order, lilo.conf is easy to edit but I find grub very complicated. Regards Dave P
+1, add it to /boot -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dave Plater wrote:
Josef Reidinger wrote:
Hi, I have question for middle experienced user of opensuse. Often is quite useful for users to have documentation when kernel upgrade fail because bootloader update failed to different reasons. Or also what they need manually edit if something goes bad as in https://bugzilla.novell.com/show_bug.cgi?id=224476. So my question where you expect documentation about this (some howto or FAQ and also describe process what happen during it)? Manpage for update-kernel script? Or some comments in some config file? Please expect that bootloader is not only grub, but also for other architectures (powerLilo etc.). Josef Reidinger, perl-Bootloader maintainer
I think from reading the only other reply and looking at the debian config, the conclusion could be drawn that a text grub howto in the boot directory would be in order, lilo.conf is easy to edit but I find grub very complicated. Regards Dave P
Good idea, thanks. I try first version of this file, but now it is after deadline for beta 5, so is some time to improve it before i add to first time. So I attach it and welcome any suggestion or improvements. JR This file is for first help if you occur some problems during booting. FAQ Q: Kernel upgrade break my tuned bootloader settings, I want edit it manually. A: set LOADER_TYPE="none" in /etc/sysconfig/bootloader. Hint is used /boot/vmlinuz and /boot/initrd symlinks as files which is already point to actual kernel. WARNING after kernel upgrade you must update also configuration manually, otherwise you cannot boot. Configuration files for bootloader (if you want manually edit it) /etc/sysconfig/bootloader - contain various settings for bootloader and is used by perl-Bootloader for grub (x86*) or trustedgrub - /boot/grub/menu.lst - main configuration for sections /boot/grub/device.map - mapping of real device to grub device /etc/grub.conf - batch file for grub if you need update your bootloader location for lilo ( x86* or ppc) - /etc/lilo.conf - main configuration file for elilo ( x86_64 or ia) - /etc/elilo.conf - main configuration file efibootmgr - utility for efi labels /boot/efi/efi/SuSE/elilo.conf - configuration after elilo preprocess, use only if elilo break original configuration, in other case edit directly elilo.conf in /etc for zipl (s390)- /etc/zipl.conf - main configuration file
participants (5)
-
Carlos E. R. -
Dave Plater -
Josef Reidinger -
Oddball -
Putrycz, Erik