On Thu 22 Nov 2012 at 01:37:02 -0500, Lou Poppler wrote: > Thanks for your reply -- for some reason it didn't arrive here as email, > but I found it tonight while looking in the debian-boot list archives.
Strange. mail.msen.com accepted the mail from my server. > On Mon, 19 Nov 2012 11:00:49 +0000, Brian Potkin wrote: > > : : Did you get that advice from section 6.3.6.1? I'd agree it is > less > : helpful than intended. > > Yes, exactly. The mention of black arts also makes me hesitant to interfere > when the automatic process gets it wrong. The GRUB ecosystem seems more > complicated, the more I try to understand it, with the various scripts > which probe and update and install, but aren't really discussed in the > mainline grub documentation sources, such as they are. Perhaps in section > 6.3.6.2 where it says "See the grub manual for complete information." > there could be some hyperlink[s]. I am not sure that would really help in general. In this case it would not have because the bug lay with d-i and not any of the GRUB scripts. > : : It's a pity you declined to install GRUB. At least you should > have got a > : bootable system from which to attempt to get the missing entry into the > : GRUB menu. > > It's too bad the ISO doesn't provide a way to boot into the completed > installation, without overwriting the disk's MBR. I would be more > confident to experiment with GRUB configurations and probing if I could > see what it was trying to install before I commit to it. I don't want > to lose the ability to boot the existing Win7 system on my wife's computer. It does. You decline the offer to install GRUB to /dev/sda by answering 'No' and specifying where GRUB should go. > I see that the beta-4 version is available today. I'll grab that, and try > it out to see if it will work automatically. It works for me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
