From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1W3qFL-0006gN-4H for mharc-grub-devel@gnu.org; Thu, 16 Jan 2014 11:56:47 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45071) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W3qFD-0006fv-G5 for grub-devel@gnu.org; Thu, 16 Jan 2014 11:56:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W3qF7-0001eq-Dt for grub-devel@gnu.org; Thu, 16 Jan 2014 11:56:39 -0500 Received: from mout.gmx.net ([74.208.4.200]:51936) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W3qF7-0001ee-6j for grub-devel@gnu.org; Thu, 16 Jan 2014 11:56:33 -0500 Received: from mailout-us.gmx.com ([172.19.198.46]) by mrigmx.server.lan (mrigmxus001) with ESMTP (Nemesis) id 0M2447-1VBri02ec7-00txsR for ; Thu, 16 Jan 2014 17:56:31 +0100 Received: (qmail 4174 invoked by uid 0); 16 Jan 2014 16:56:31 -0000 Received: from 174.119.247.117 by rms-us006 with HTTP Content-Type: multipart/alternative; boundary="========GMXBoundary190771389891390377608" Date: Thu, 16 Jan 2014 11:56:30 -0500 From: "joe faith" Message-ID: <20140116165630.190770@gmx.com> MIME-Version: 1.0 Subject: Re: [RFC] Allow separate boot block and core.img location? To: "The development of GNU GRUB" ,grub-devel@gnu.org X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: aWqqcuEr3zOlOnh9+n8hBrZ+IGRvb8DG X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 74.208.4.200 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jan 2014 16:56:45 -0000 --========GMXBoundary190771389891390377608 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit May I also suggest that "--core-img-location" parameter accept a block-list in some format, in addition to the device identifier?grub-install --boot-block-location=/dev/sda --core-img-location=/dev/sda[63+1985] => embed core image in the 1985 sectors starting at LBA 63 on /dev/sda This would be helpful in dealing with certain software that tend to use the MBR area to store their configuration. For example, TrueCrypt disk encryption software uses LBA 62 (0x3E) to store the volume header of the system volume. I know that the use of the MBR area by any such software is not approriate, however, some extra flexibility in the grub-installer will certainly address some of these issues. Cheers! ----- Original Message ----- From: Andrey Borzenkov Sent: 12/16/13 02:36 PM To: grub-devel@gnu.org Subject: [RFC] Allow separate boot block and core.img location? There are many users using dual boot with Windows and Linux. In this configuration installing grub in MBR unfortunately breaks at least some updates of Windows 8 (update fails). And installing grub in partition has all sort of known problems with blocklists. What about allowing separate locations for boot block and core.img? I.e. something like grub-install --boot-block-location=/dev/sda1 --core-img-location=/dev/sda This has all advantages of embedding core.img while allowing leaving MBR alone. Actually we could assume default --core-img-location, meaning that for grub-install --boot-block-location=/dev/sda1 we assume that core.img has to be embedded in /dev/sda unless proved otherwise :) _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel --========GMXBoundary190771389891390377608 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable May I also suggest that "--core-img-location" param= eter accept a block-list in some format, in addition to the device identifi= er?
grub-install --boot-block-loca=
tion=3D/dev/sda --core-img-location=3D/dev/sda[63+1985]=20

=3D> embed core image in the 1985 sectors starting at LBA 63 on /dev/sda=
=20

This would be helpful in dealing with certain software that tend to use the=
 MBR area to store their configuration.=20
For example, TrueCrypt disk encryption software uses LBA 62 (0x3E) to store=
 the volume header of the system volume.=20
I know that the use of the MBR area by any such software is not approriate,=
 however, some extra flexibility in the grub-installer will certainly addre=
ss some of these issues.=20
Cheers!
=C2=A0

=C2=A0

----- Original Message -----

From: Andrey Borzenkov

Sent: 12/16/13 02:36 PM

To: grub-devel@gnu.org

= Subject: [RFC] Allow separate boot block and core.img location?

=C2=A0
There are many users using dual boot with Windows =
and Linux. In this=20
configuration installing grub in MBR unfortunately breaks at least some=20
updates of Windows 8 (update fails). And installing grub in partition=20
has all sort of known problems with blocklists.=20

What about allowing separate locations for boot block and core.img?=20
I.e. something like=20

grub-install --boot-block-location=3D/dev/sda1=20
--core-img-location=3D/dev/sda=20

This has all advantages of embedding core.img while allowing leaving=20
MBR alone. Actually we could assume default --core-img-location, meaning=20
that for=20

grub-install --boot-block-location=3D/dev/sda1=20

we assume that core.img has to be embedded in /dev/sda unless proved=20
otherwise :)=20

_______________________________________________=20
Grub-devel mailing list=20
Grub-devel@gnu.org=20
https://lists.gnu.org/mailman/listinfo/grub-devel

=C2=A0

--========GMXBoundary190771389891390377608--