From: "joe faith" <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, 16 Jan 2014 21:13:47 -0500 [thread overview]
Message-ID: <20140117021347.232860@gmx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
----- Original Message -----
From: Chris Murphy
Sent: 01/16/14 04:04 PM
To: The development of GNU GRUB
Subject: Re: [RFC] Allow separate boot block and core.img location?
Is there a good reason why we don't have a separate partition for core.img? It doesn't seem like it's an OK idea for anything to be using the unallocated MBR gap, it's essentially a free for all. So why not an 0xEA partition of 1MB that's the MBR equivalent of the GPT BIOS Boot partition? I don't know if it even necessarily requires use of a primary partition if the boot.img code in the MBR simply points to an LBA to load. If that's the case core.img could be in an extended partition. And once GRUB is running, it doesn't care about primary or extended partitions anyway, right? When using TrueCrypt whole disk encryption, for example, extended partitions are not supported (with WinXP anyway).
That leaves you with a maximum of 4 partitions - often not enough to spare one for grub (especially in multi-boot setups).
[-- Attachment #2: Type: text/html, Size: 1940 bytes --]
next reply other threads:[~2014-01-17 2:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 2:13 joe faith [this message]
2014-01-17 4:55 ` [RFC] Allow separate boot block and core.img location? 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-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-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=20140117021347.232860@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).