On Sun, Mar 20, 2011 at 12:09 AM, Dom <to...@rpdom.net> wrote: > On 19/03/11 13:29, Joel Rees wrote: >> >> I really didn't have much problem with grub 1, just edit menu.lst . >> >> I'm having the devil of a time trying to figure out how to set the >> default boot and how to chain in grub 2 in squeeze. >> >> I found something about using update grub and setting the default boot >> in a fle in /usr/share/grub, followed by doing an update-grub, but >> that doesn't change the default boot, > > You can change the default in file /etc/default/grub. Edit the > GRUB_DEFAULT= line to the entry number you want (starting with 0 for the > first entry in the grub menu. > > Then run update-grub.
I think I got stuck for a while on update-grub being in /usr/sbin . Or was it grub-update ? Anyway, I finally tried that today, and the update found my new install of Fedora 15. But selecting that sends my system off to the ether. It sits there with the deban grub splash screen forever. Might be problems with F15, which is still alpha. Fedora 13 is still bootable, has been since I installed Debian in the default partition of the first (and only) bootable drive (over the Fedora 10 that had been there). > I don't use chain loading, so am not sure how to do that. I think grub2 > should automatically detect other OSen, is os-prober is installed, when > update-grub is run. I'm sure someone else here can advise you. Well, apparently, it doesn't find the other OSses until you do the /usr/sbin/grub-update . That's one problem. The other problem is that I don't want Debian to be the default right now. Maybe later. Another problem is the fragile linkage. If Debian ends up with more than two entries there, or if, for some reason I delete the rescue mode entry, having the third entry as the default suddenly is not what I want. Maybe that won't happen with Fedora 13's most recent kernel as the default, but it definitely is more than possible if I try to default to the Fedora 15 install. With chainloading each system can maintain its own grub, and Debian's kernel install scripts don't need to know for Fedora's kernels. That doesn't completely solve things. That is, if Debian ever thinks it has to make a third entry, and the third entry was the default, what was default is no longer. Am I making sense? It's late at night here. Joel Rees There are two problems with -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktik-lbagepyk6drubzt-wpec7vm...@mail.gmail.com
