http://qa.mandrakesoft.com/show_bug.cgi?id=5377
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED]
Component|Installation |program
Product|Installation |bootloader-utils
Version|1.830 |1.6-3mdk
------- Additional Comments From [EMAIL PROTECTED] 2003-18-09 12:51 -------
we really should consolidate code between drakboot/drakx & installkernel
--
Configure bugmail: http://qa.mandrakesoft.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.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEW
creation_date:
description:
When installing standard kernel-2.4.22.5mdk-1-1mdk from main and
kernel-2.6.0-0.test4.3mdk-1-1mdk from contribs during install
the initrd.img and vmlinuz symlinks in /boot points to the 2.6 kernel:
lrwxrwxrwx 1 root root 29 syys 8 2003 initrd.img
->initrd-2.6.0-0.test4.3mdk.img
lrwxrwxrwx 1 root root 26 syys 8 2003 vmlinuz
->vmlinuz-2.6.0-0.test4.3mdk
This is _bad_ since the lilo options linux, linux-nonfb and failsafe all use:
image=/boot/vmlinuz
initrd=/boot/initrd.img
as their kernel choice...
This will lead to users trying to fix their broken systems most likely
ending up with more problems, since without they knowing it, they will
be booting into an 2.6 test-kernel :-(
And this is definately an installer bug since all contrib kernels
are using -L parameter with /sbin/installkernel, and installing
a 2.6 kernel _after_ a newly installed system has been rebooted into,
won't trigger this behaviour....
Regards
Thomas
