From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1VtaqG-0004op-FO for mharc-grub-devel@gnu.org; Thu, 19 Dec 2013 05:28:32 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60771) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vtaq8-0004o1-H9 for grub-devel@gnu.org; Thu, 19 Dec 2013 05:28:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vtaq2-0002Jj-MJ for grub-devel@gnu.org; Thu, 19 Dec 2013 05:28:24 -0500 Received: from mout.gmx.net ([74.208.4.201]:51269) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vtaq2-0002JT-G7 for grub-devel@gnu.org; Thu, 19 Dec 2013 05:28:18 -0500 Received: from mailout-us.gmx.com ([172.19.198.48]) by mrigmx.server.lan (mrigmxus002) with ESMTP (Nemesis) id 0Lz2GK-1VOdnc3XZA-014DO1 for ; Thu, 19 Dec 2013 11:28:16 +0100 Received: (qmail 25493 invoked by uid 0); 19 Dec 2013 10:28:16 -0000 Received: from 174.119.247.117 by rms-us022 with HTTP Content-Type: multipart/alternative; boundary="========GMXBoundary110961387448896619988" Date: Thu, 19 Dec 2013 05:28:16 -0500 From: "joe fresh" Message-ID: <20131219102816.110960@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: F6/AcjxK3zOlOnh9+n8hj65+IGRvb8AC X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 74.208.4.201 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, 19 Dec 2013 10:28:30 -0000 --========GMXBoundary110961387448896619988 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Isn't this as simple as: grub-install /dev/sda dd if=/dev/sda of=/dev/sda1 bs=512 count=1 followed by restoring DOS MBR... ? 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 --========GMXBoundary110961387448896619988 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Isn't th= is as simple as:

grub-install /dev/sda
dd if=3D/dev/sda of= =3D/dev/sda1 bs=3D512 count=3D1
followed by restoring DOS MBR... ?

Cheers!

=C2=A0

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

<= p style=3D"margin:0px; padding:0px;" ><= span style=3D"font-size:12px">From: Andrey Borzenkov

Sent: 12/16/13 02:36 PM

To: grub-devel@gnu.org

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

=C2=A0
There are many users using dua=
l 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

 


  --========GMXBoundary110961387448896619988--