On Wed January 31 2007 17:09, Darryl Gregorash wrote: > This entire thread has been very confusing and puzzling. I have never > seen any reports of this kind of behaviour in the grub install routines, > nor have I ever encountered a problem with those routines myself.
I ran into a similar problem when I first installed 10.1 to test drive it. 10.0 was my daily desktop and I'd kept 9.3 as a backup on an adjacent partition. Moreover, I'd just added a much larger third disk and a combined six or seven additional partitions. /home and /swap were designated to be shared across all three Linux installations, plus slices for the XP side and backups. This obviously confused the installer. I didn't check what the bootloader configuration module was going to write. I just accepted it... trusting soul :-) ... because I'd never had a problem with it before. But the system stumbled and locked up at next boot. I booted into 9.3 normally (no changes) and inspected the situation. Sure enough, the default and 10.1 portions of menu.lst were incorrectly written... specifically, wrong partition numbers. The paths were correct, but it had misinterpreted which slice was 10.1 '/'. The system was fine after I cleaned it up manually. Now I purposely take the time to visually confirm what it wants to do before committing. No more problems. Carl -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
