[Bug 214935] New: Entries in menu.lst still use links "vmlinuz" and "initrd" to load the corresponding section
https://bugzilla.novell.com/show_bug.cgi?id=214935 Summary: Entries in menu.lst still use links "vmlinuz" and "initrd" to load the corresponding section Product: openSUSE 10.2 Version: Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: aosthof@novell.com QAContact: jsrain@novell.com When installing a fresh system - thus no update - the symlinks "vmlinuz" and "initrd" still will be used in menu.lst to load the corresponding section. This shouldn't be: If one wants to remove an existing kernel per "rpm -e <kernel-name>", the existing sections, which include those symlinks, won't get removed. Nearly the same problem appears when installing a new kernel besides an existing one. In this case, the new entry in menu.lst uses again symlinks and the entry related to the former kernel uses *.previous symlinks to load these sections. E.g. a wrong entry looks like this: ----------------------------------- title openSUSE 10.2 root (hd0,1) kernel /boot/vmlinuz root=/dev/sda2 vga=0x31a resume=/dev/sda1 splash=silent showopts initrd /boot/initrd But it should look like this: ----------------------------- title openSUSE 10.2 -- Kernel-2.6.18.1-7-default root (hd0,1) kernel /boot/vmlinuz-2.6.18.1-7-default root=/dev/sda2 vga=0x31a resume=/dev/sda1 splash=silent showopts initrd /boot/initrd-2.6.18.1-7-default -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=214935 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kernel-maintainers@forge.provo.novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=214935 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=214935 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |jplack@novell.com |maintainers@forge.provo.nove| |ll.com | Status|ASSIGNED |NEW Component|Installation |Basesystem -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=214935 jplack@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jplack@novell.com |odabrunz@novell.com ------- Comment #1 from jplack@novell.com 2006-11-13 03:29 MST ------- this is still the case in beta2 this can only be solved in yast2-bootloader -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=214935 stefan.fent@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |agruen@novell.com ------- Comment #2 from stefan.fent@novell.com 2006-11-16 01:32 MST ------- Actually, it can't be solved that easily, as we don't have knowledge about the image name, which requires us to do some "guessing" here. We can guess upon the current name scheme quite good, but eventually this is changed, then we'd have to make a new guess, this would be bad and adding (again) version dependencies between kernel and [yast2-b, perl-B]ootloader A solution would be to let the kernel-rpm provide the image name. sth. like 'image = vmlinuz-2.6.18-2.13-git-24' Andreas, do you have any idea wether it's already possible to get this information from the actual provides of the kernel.rpm, that is _stable_? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=214935 stefan.fent@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Blocker ------- Comment #3 from stefan.fent@novell.com 2006-11-16 02:57 MST ------- Marking this blocker, as the original entry is not deleted. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=214935 agruen@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|agruen@novell.com | ------- Comment #4 from agruen@novell.com 2006-11-16 06:16 MST ------- Initial comment: The problem here is that the initial bootloader configuration is created by yast at a time when no packages have been installed yet, and so there is no way to use the actual image and initrd names initially. The kernel's %post script is called with YAST_IS_RUNNING="instsys", when the kernel package is finally installed, meaning that the kernel will not try to create an initrd or another bootloader entry. I discussed this with Stefan some weeks ago, and we agreed on the following approach: let yast create bootloader entries as it does now, and "fix" the entries (by replacing the symlinks with the actual files) after the kernel packages have been installed. I don't know at which point in time yast creates the initrd for the kernel, and whether o rnot it calls the kernel's %post script for that. In any case, the right point in time for fixing the bootloader entry would be after the initrd has been created IMO. The kernel's %post script could be used for that when called with YAST_IS_RUNNING!="instsys". Please be aware that more than one kernel can be selected, and so more than one kernel may get installed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=214935 ------- Comment #5 from agruen@novell.com 2006-11-16 06:18 MST ------- If the kernel's %post script is not called, then the image name can still be guessed from the symlinks in /boot: each kernel will have one image and one initrd symlink. This is just as good as some magic additional Provides tag. Going via the %post script makes more sense IMO though. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=214935 ------- Comment #6 from stefan.fent@novell.com 2006-11-17 11:43 MST ------- This should be fixed with latest yast2-bootloader, final testing on monday -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=214935 odabrunz@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #7 from odabrunz@novell.com 2006-11-21 10:10 MST ------- Fix is in yast2-bootloader-2.14.8.rpm. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com