[Cooker] [Bug 5200] [Installation] 9.2 RC1 installer messes up windows lilo entries during upgrade
http://qa.mandrakesoft.com/show_bug.cgi?id=5200 --- Additional Comments From [EMAIL PROTECTED] 2003-05-09 14:44 --- Created an attachment (id=753) -- (http://qa.mandrakesoft.com/attachment.cgi?id=753action=view) whole /root/drakx excludin replay_install.img, .tar.bz2 archive -- 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: UNCONFIRMED creation_date: description: I've upgraded from Mandrake 9.1 ro 9.2 RC1 on a Thinkpad A21e laptop. There were 2 windows partitions: hda1 (actual Windows partition) and hda2 (hidden IBM service DOS partition). During upgrade, the installer placed the hda2 secondary servicing partition twice into lilo.conf (labelled windows and windows2), while the hda1 partition was not added. Luckily, it preserved the old entry as windows_old. The resulting lilo.conf looked like this: boot=/dev/hda map=/boot/map vga=791 default=windows keytable=/boot/us.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label=linux root=/dev/hda5 initrd=/boot/initrd.img append=devfs=mount acpi=off read-only other=/dev/hda2 label=windows table=/dev/hda other=/dev/hda2 label=windows2 table=/dev/hda other=/dev/fd0 label=floppy unsafe image=/boot/vmlinuz-2.4.21-0.18mdk label=old_linux root=/dev/hda5 initrd=/boot/initrd-2.4.21-0.18mdk.img append=devfs=mount acpi=off read-only image=/boot/vmlinuz-2.4.21-0.18mdk label=2421-18 root=/dev/hda5 initrd=/boot/initrd-2.4.21-0.18mdk.img append=devfs=mount acpi=off read-only image=/boot/vmlinuz label=failsafe root=/dev/hda5 initrd=/boot/initrd.img append=devfs=nomount acpi=off failsafe read-only other=/dev/hda1 label=dos table=/dev/hda other=/dev/hda1 label=old_windows table=/dev/hda
[Cooker] [Bug 5200] [Installation] 9.2 RC1 installer messes up windows lilo entries during upgrade
http://qa.mandrakesoft.com/show_bug.cgi?id=5200 --- Additional Comments From [EMAIL PROTECTED] 2003-04-09 12:02 --- Ok, as soon as I get access to that machine (can't say when, though :( ). -- 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: UNCONFIRMED creation_date: description: I've upgraded from Mandrake 9.1 ro 9.2 RC1 on a Thinkpad A21e laptop. There were 2 windows partitions: hda1 (actual Windows partition) and hda2 (hidden IBM service DOS partition). During upgrade, the installer placed the hda2 secondary servicing partition twice into lilo.conf (labelled windows and windows2), while the hda1 partition was not added. Luckily, it preserved the old entry as windows_old. The resulting lilo.conf looked like this: boot=/dev/hda map=/boot/map vga=791 default=windows keytable=/boot/us.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label=linux root=/dev/hda5 initrd=/boot/initrd.img append=devfs=mount acpi=off read-only other=/dev/hda2 label=windows table=/dev/hda other=/dev/hda2 label=windows2 table=/dev/hda other=/dev/fd0 label=floppy unsafe image=/boot/vmlinuz-2.4.21-0.18mdk label=old_linux root=/dev/hda5 initrd=/boot/initrd-2.4.21-0.18mdk.img append=devfs=mount acpi=off read-only image=/boot/vmlinuz-2.4.21-0.18mdk label=2421-18 root=/dev/hda5 initrd=/boot/initrd-2.4.21-0.18mdk.img append=devfs=mount acpi=off read-only image=/boot/vmlinuz label=failsafe root=/dev/hda5 initrd=/boot/initrd.img append=devfs=nomount acpi=off failsafe read-only other=/dev/hda1 label=dos table=/dev/hda other=/dev/hda1 label=old_windows table=/dev/hda
