From: "joe fresh" <dzrdmwjx@gmx.com>
To: "The development of GNU GRUB" <grub-devel@gnu.org>,grub-devel@gnu.org
Subject: Re: [RFC] Allow separate boot block and core.img location?
Date: Thu, 19 Dec 2013 05:28:16 -0500 [thread overview]
Message-ID: <20131219102816.110960@gmx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2386 bytes --]
next reply other threads:[~2013-12-19 10:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 10:28 joe fresh [this message]
2013-12-19 14:34 ` [RFC] Allow separate boot block and core.img location? Lennart Sorensen
2014-01-16 21:04 ` Chris Murphy
-- strict thread matches above, loose matches on Subject: below --
2014-01-17 12:01 joe faith
2014-01-21 18:02 ` Chris Murphy
2014-01-22 14:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-01-17 2:13 joe faith
2014-01-17 4:55 ` Chris Murphy
2014-01-16 16:56 joe faith
2013-12-19 16:31 joe fresh
2013-12-19 18:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 22:54 ` Chris Murphy
2013-12-16 19:36 Andrey Borzenkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131219102816.110960@gmx.com \
--to=dzrdmwjx@gmx.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.