Hi guys!
Just came here to tell you that I got a Triple boot working - but after some minor grub(2?) pain...
I installed Karmic in a spare (ext4) partition, and Jaunty is installed in an ext3 partition. Everything went great. But... after rebooting, grub only showed me Karmic: Jaunty and Vista were gone.
After looking for the /boot/grub/menu.lst file (heh) and realizing it's not there anymore, i reached /boot/grub/grub.cfg, where sure enough, I only had the Karmic partition listed.
Then, I tried grub's suggestion:
It spilled a bunch of stuff into the screen, including all the partitions that it had found and the entries to the other OS's... However, my /boot/grub/grub.cfg file still showed only the Karmic entry!
I then did instead
and sure enough this file had all the entries I needed!
So... taking my chances I decided to edit /boot/grub/grub.cfg even though it explicitly tells me not to, and added all the entries as shown in the attached file, and it worked.
Now, the questions:
- why doesn't sudo grub-mkconfig write the correct entries into the grub.cfg file?
- could I have done something else (e.g. another grub command that would have fixed it?)
Thanks!
Just came here to tell you that I got a Triple boot working - but after some minor grub(2?) pain...
I installed Karmic in a spare (ext4) partition, and Jaunty is installed in an ext3 partition. Everything went great. But... after rebooting, grub only showed me Karmic: Jaunty and Vista were gone.
After looking for the /boot/grub/menu.lst file (heh) and realizing it's not there anymore, i reached /boot/grub/grub.cfg, where sure enough, I only had the Karmic partition listed.
Then, I tried grub's suggestion:
Code:
sudo grub-mkconfig
I then did instead
Code:
sudo grub-mkconfig > grub.log
So... taking my chances I decided to edit /boot/grub/grub.cfg even though it explicitly tells me not to, and added all the entries as shown in the attached file, and it worked.
Now, the questions:
- why doesn't sudo grub-mkconfig write the correct entries into the grub.cfg file?
- could I have done something else (e.g. another grub command that would have fixed it?)
Thanks!
Comment