From: "joe fresh" <dzrdmwjx@gmx.com>
To: "The development of GNU GRUB" <grub-devel@gnu.org>
Subject: Re: [RFC] Allow separate boot block and core.img location?
Date: Thu, 19 Dec 2013 11:31:07 -0500 [thread overview]
Message-ID: <20131219163107.94130@gmx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
sda1 was just an example taken from the original request:grub-install --boot-block-location=/dev/sda1 --core-img-location=/dev/sda The intent there was to install the boot block (boot.img) into the first sector of sda1, which is what my suggested workaround would have done as well.
Also, if sda1 happens to be a fat or ntfs volume, this would need to be tweaked to ensure that the critical volume parameters are preserved.
The assumption in both cases is that the user knows what they are doing...
Cheers!
----- Original Message -----
From: Lennart Sorensen
Sent: 12/19/13 09:34 AM
To: The development of GNU GRUB
Subject: Re: [RFC] Allow separate boot block and core.img location?
On Thu, Dec 19, 2013 at 05:28:16AM -0500, joe fresh wrote: > 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... ? sda1 might not like having it's first sector overwritten. -- Len Sorensen _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
[-- Attachment #2: Type: text/html, Size: 2489 bytes --]
next reply other threads:[~2013-12-19 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 16:31 joe fresh [this message]
2013-12-19 18:18 ` [RFC] Allow separate boot block and core.img location? Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 22:54 ` 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 10:28 joe fresh
2013-12-19 14:34 ` Lennart Sorensen
2014-01-16 21:04 ` 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=20131219163107.94130@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).