http://qa.mandrakesoft.com/show_bug.cgi?id=4852
------- Additional Comments From [EMAIL PROTECTED] 2003-29-08 03:37 -------
in 9.2rc1 there's some improvement, unfortunately it does not work correctly.
First : there's is really an enhancement necessary not to look only in /boot but
in /mnt/linuxMdK9.1/boot as well
Second : there a major bug as initrd is not correctly initialized (it takes the
file there is in /boot, not the one in /mnt/linuxMdK9.1 and when those are not
the same kernel versions... well it breaks again MdK9.1 !! (ggrrrr Kernel Panic)
This is worse for me as nvidia driver does not tolerate the mismatch (it makes X
crash) and has to be reinstalled to get X back.
Nevertheless, I appreciated the Add buttons : Other (Win...) / Linux. There's
still integration with lilo to do !
Furthermore, it would be kind to get the options from previous lilo rather than
emptying the field (another enhancement).
Here's the lilo.conf that works (commented are lines generated by drakboot)
boot=/dev/hda
map=/boot/map
vga=normal
default="linux_MdK9.2rc1"
keytable=/boot/fr-latin1.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label="linux_MdK9.2rc1"
root=/dev/hda5
initrd=/boot/initrd.img
append="devfs=mount hdc=ide-scsi acpi=off resume=/dev/hda7 splash=silent"
vga=788
read-only
image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/hda5
initrd=/boot/initrd.img
append="devfs=mount hdc=ide-scsi acpi=off resume=/dev/hda7"
read-only
image=/boot/vmlinuz
label="failsafe"
root=/dev/hda5
initrd=/boot/initrd.img
append="failsafe devfs=nomount hdc=ide-scsi acpi=off resume=/dev/hda7"
read-only
other=/dev/hda1
label="windows"
table=/dev/hda
image=/boot/vmlinuz-2.4.21-0.13mdk
label="linuxMdK9.1"
root=/dev/hda8
initrd=/boot/initrd-2.4.21-0.13mdk.img
#initrd=/boot/initrd-2.4.22-1mdk.img
append="quiet devfs=mount hdc=ide-scsi acpi=off"
read-only
As you can see, once again I had to copy files manually, this is not for the noobie.
--
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:
Facts :
- drakboot is Windoze friendly and configures correctly lilo to take into
account previous windoze installation
- with an existing Linux partition (with MdK9.1), drakboot is not friendly and
obliges to edit lilo.conf manually in the end (or at least do manual operations)
What I wanted to do :
- for installation of Mandrake 9.2 beta 2 I did not want to mess my MdK9.1
stable installation
- hence I've dedicated a partition for fresh install of Mandrake 9.2 so that MdK
9.1 is preserved (if data is partitionned, my assumption is it's separated and
hence safe !). That's what I did when some time ago I switched from Windoze and
still gave a chance to revert easily, and it worked flawlessly being very
Windoze friendly (I did not revert though, I've kept moving forward).
- So I expected Mandrake 9.2 to cohabit with Mandrake 9.1 and easily revert,
which proved more difficult than expected but worked in the end.
My diagnosis is that drakboot makes the assumption that another Linux is in
/boot and that taking into account another partition is not well managed hence
this is more a request for enhancement than bug report). It could simplify life
for the noobie (avoiding manual steps ).
At first I pointed at lilo (see previous bug report
http://qa.mandrakesoft.com/show_bug.cgi?id=4829), now I think it's more an
enhancement of drakboot to exploit lilo features to the best : provide a simple
strategy to detect previous versions of Linux, in the same way it detects windoze.
Enhancement Proposal :
- detection of another partition with Linux
- configure lilo correctly, either way :
. identify the mount point (e.g. /mnt/linux-0) and configure lilo to take
it into account (may require to copy files - as I had to do - to local partition
/boot...)
. obtain previous configuration and adapt/check it (as partition naming
may have changed in between, as was the case for me)
The point is to use the latest install to take into account previous ones (of
course there are other possibilities), as I tend to expect the latest release
not to break anything (it lowers immediately my confidence in it).
What do you think of it ?
