[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Format option for chainloading GRUB from BOOTMGR
From: |
Andrey Borzenkov |
Subject: |
Re: Format option for chainloading GRUB from BOOTMGR |
Date: |
Wed, 7 Aug 2013 22:52:17 +0400 |
В Wed, 7 Aug 2013 13:23:18 -0400
Alexei Podtelezhnikov <address@hidden> пишет:
> On Wed, Aug 7, 2013 at 12:16 PM, Andrey Borzenkov <address@hidden>wrote:
>
> >
> > Alexei Podtelezhnikov <address@hidden> пишет:
> >
> > > >
> > > > How is location of /boot/grub relevant here? To change it you update
> > > > grub2.img and if I understand you correctly, BCD does not need to be
> > > > updated for it?
> > > >
> > >
> > > Correct. BCD needs to know the location of grub2.img only, not what's
> > > inside.
> > >
> > > It is too bad that UUID cannot be given in --prefix. The search_fs_uuid
> > > stuff is not for the end user.
> >
> > grub-mkimage (or grub-probe for that matter) are not end user tools.
> > End user should use grub-install which does search for UUID and
> > creates image that looks for it.
> >
> > > How about making this a part of
> > i386-pc-lnx
> > > format execution together with automatic appending lnxboot.img?
> >
> > I think if you send patch to grub-devel we'll see. It should likely go
> > into grub-install. It may even be generalized by allowing multiple boot
> > methods for a single platform.
> >
>
> I have no idea how the interface should look like so that grub-install
> puts the image onto an NTFS bootmgr partition root rather than
> its boot sector.
>
I would say, just
grub-install --target i386-pc-lnx /path/to/image
> My initial post was to fill the gap: while there is a lot
> of information on how to chainload BOOTMGR from GRUB,
> there is no information on chainloading GRUB from BOOTMGR.