-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 21 Sep 2009 15:27:09 +0200 "thveillon.debian" <thveillon.deb...@googlemail.com> wrote:
> > I still fail to understand what went wrong. After the installation and > > reboot which went OK, I picked the chain option and that's when it all > > went downhill. > > The chaining from grub-legacy menu to grub2 is just supposed to enable > testing of the grub2 install, it doesn't install anything. One has to > run "upgrade-from-grub-legacy" as root to finish the process, or simply > properly install grub2 in the mbr, and create the config. Sorry, but I did run "upgrade-from-grub-legacy" after the chaining boot went well. > If the boot process failed with the chainloading from grub-legacy, it > means that it would not have been a good idea to finish the process > anyway... The process didn't fail...which is why I ran the upgrade script. > > Obviously grub-pc is not ready for primetime yet. On the update it > > did on my machine, it failed to pick up the Ubuntu installation on another > > partition. How did it get migrated to Squeeze ? > > > > The package "os-prober" is taking care of other OS detection, it's > "recommended" but not automatically installed. Does that mean maintainers assume you only have one installation ? >I am using grub2 since > Lenny was testing, now on three squeeze, and three Ubuntu, no problem > here. Just got lucky maybe. Lucky is right - google problems with Grub2. Don't get me wrong - it **seems** Grub2 will be an improvement over its predecessor but, at least in my case and it seems many others it's not quite ready. - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkq3koMACgkQIyN89Z1rCtFFWgCfTdwFTRXZMCIA4+aaGLlFIYFZ s6wAoLH8ST1TitJSYrFnHMzsFhK3otYF =/xMs -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org