http://qa.mandrakesoft.com/show_bug.cgi?id=4852

           Product: drakxtools
         Component: drakboot
           Summary: drakboot dual boot Linux Mandrake is not Linux friendly
           Product: drakxtools
           Version: 9.2-0.32mdk
          Platform: PC
        OS/Version: All
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: drakboot
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


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 ?

-- 
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.

Reply via email to