RESOLVED!!!
The error was that I wrote the new menuentries in grub.cfg under the
voice ###BEGIN /usr/etc/grub.d/40_custom, while it was necessary to
write them under the voice ###BEGIN /usr/etc/grub.d/10_linux.
This recognized it was very easy to get a multiboot "LFS | ArchLinux |
Ubuntu-Plus-7 | Windows 7" choice.
I understand that under LFS no role must be given to grub-mkconfig and
/usr/etc/grub.d files: it's better to forget their existence and
manually editing grub.cfg (saving it with wq!).
I'm very happy and now I can begin BLFS.
Again many thanks to all you.

Giorgio Cittadini, aka giocitta


2011/8/17 Giorgio Cittadini <gioci...@gmail.com>:
> To the attention of Andy and Mac (with many thanks for having
> considered my problem).
>
> This is how the things go.
> I installed LFS-6.8 on a notebook HP Pavilion dv6215ea with i386 dual
> core CPU. My situation at the moment is the following:
>
> (1) 500 GB HD partitioned so to have Windows 7 (reserved) in the first
> partition, Windows 7 (OS) in the second, LFS in the third, Ubuntu 11.4
> in the fifth, ArchLinux in the sixth, and one 2 GB swap in the
> seventh;
> (2) ArchLinux and Ubuntu do have grub2 perfectly recognizing every OS
> I put in the HD, so that I can easily use the grub2 that, at the
> moment, is installed on the MBR, to boot also LFS;
> (3) On the contrary, LFS doesn't succeed to read any OS but itself;
> (4) According to your suggestions I added to /usr/etc/grub.d/40_custom
> the menuentry for "Windows 7", but it is not recognized because I
> haven't any /usr/etc/default/grub file that grub-mkconfig requests to
> act on /usr/etc/grub.d/ files to generate /boot/grub/grub.cfg. This is
> the problem!
> (5) But also if I manually modify grub.cfg introducing the new
> menuentry (and, obviously, I don't use grub-mkconfig), nothing
> changes.
>
> Could there be a bug in the tarball of grub? I don't think it
> possible, since the other OSs do use grub2 successfully (one in the
> 1.98, the other in the 1.99 version).
> So I think I have mistaken some passage during LFS building.
> That is all.
> Again many thanks for your courtesy, kindness and tolerance towards a
> newbie. I do appreciate very much.
>
> giocitta
>
> 2011/8/17 Andrew Benton <b3n...@gmail.com>:
>> On Tue, 16 Aug 2011 12:46:46 -0500
>> Mike McCarty <mike.mcca...@sbcglobal.net> wrote:
>>> Andrew Benton wrote:
>>> > You don't need to reinstall grub. If it's working Ok and you can boot
>>> > into LFS then just edit grub.cfg to make an entry for windows,
>>> > something like this:
>>> >
>>> > menuentry "Windows" {
>>> >    set root=(hd0,1)
>>> >    chainloader +1
>>> > }
>>>
>>> Back when I was making a dual boot system, this didn't work
>>> for me. I had a machine which "wanted" the Windows Boot Manager
>>> to be in control of boot. Fortunately, the Windows Boot Manager
>>> is actually a reasonable piece of software, and I was able to
>>> configure it to load GRUB for me.
>>>
>>> What you suggest may work in most circumstances, and it's the
>>> solution I usually see, but it is not a universal solution.
>>
>> I didn't suggest it was a universal solution. Windows XP likes to be on
>> the first partition of the first disk. On this computer I've set the
>> BIOS with my linux disk as the first disk and Windows XP on the second
>> disk. So to make windows think it's on the first disk I have to make
>> grub lie to it ans tell windows that it's on the first disk so the
>> windows entry in my grub.cfg looks like this:
>>
>> menuentry "Windows XP" {
>>   set root=(hd1,1)
>>   drivemap -s (hd0) ${root}
>>   chainloader +1
>> }
>>
>> However the original poster said he was using windows 7 which can be
>> installed on any partition which is why I didn't put this in my
>> original reply.
>>
>> Andy
>> --
>> http://linuxfromscratch.org/mailman/listinfo/lfs-support
>> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
>> Unsubscribe: See the above information page
>>
>
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to