From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: grub2 and hybrid MBR booting
Date: Thu, 01 Jul 2010 21:42:35 +0200 [thread overview]
Message-ID: <4C2CEFAB.8090308@gmail.com> (raw)
In-Reply-To: <63A4C2F2B04E2948B033568534F6C9C578E3D737EE@GVW1095EXB.americas.hpqcorp.net>
[-- Attachment #1: Type: text/plain, Size: 2809 bytes --]
On 06/29/2010 08:37 PM, Elliott, Robert (Server Storage) wrote:
> I successfully ran ubuntu 10.04 (which uses grub2) on a 4 TB drive
> (presented by a RAID controller) on a system with legacy BIOS. The
> drive got partitioned as GPT; a BIOS boot partition was installed;
> and grub stage 1 contains the 8-byte LBA of the BIOS boot partition
> hardcoded into its 440 bytes of x86 boot code, so it can load the
> code in that BIOS boot partition.
>
> That works pretty well, but requires any program that moves the BIOS
> boot partition to know that grub is pointing to it and also adjust
> that 8-byte LBA value stored in LBA 0.
>
>
After moving of partitions containing it's recommended to reinstall
bootloader
> In the UEFI Working Group (which defines GPT) and the T13 (ATA) standards
> bodies, we defined a slightly different method: the GPT partition record
> now includes a Legacy BIOS Bootable bit that can be set for a partition
> like the BIOS boot partition, The algorithm is documented in
> T13 EDD-4 revision 2 and later (see
> http://t13.org/Documents/MinutesDefault.aspx?DocumentType=4&DocumentStage=1).
>
>
At last. It's refreshing from the usual lie that you need EFI to boot
from GPT-partitioned disk.
But I don't see the need to standartise the interface between MBR code
and the rest. Standartisation is good only for interoperability between
different software. But in this case both parts are from the same
bootloader so it will only reduce flexibility.
> and the x86 boot code in LBA 0 can search
> through the GPT partition table for a partition with that bit set to 1
> (rather than contain a hardcoded LBA).
It's closedly modeled after msdos. It annihilates most of advantages of GPT. I suppose you want to put filesystem on bootable partition too.
When we added GPT support virtually unlimited embedding zone was the great plus. Switching to msdos-like scheme would be a huge step backwards (especially that you have no MBR gap). It's a repetion of old mistakes under new sauce. MSDOS scheme already forced anti-patterns and any new scheme must be based on saner pattern.
> Would grub2 consider switching to that modified algorithm?
>
> H Peter Anvin has implemented it in syslinux-4.00-pre48 (see
> http://syslinux.zytor.com/wiki/index.php/The_Syslinux_Project).
>
Syslinux is known for hanging on the old protocol no matter the price.
> The boot code
> doesn't have enough room to verify the GPT CRC and perform all the possible
> GPT verification checks, but it can definitely walk through the structure
> and find the boot partition.
>
>
Which contradicts your spec. Unimplementable spec only forces devs to
code undefined behaviour.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2010-07-01 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 18:37 grub2 and hybrid MBR booting Elliott, Robert (Server Storage)
2010-07-01 19:42 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-07-02 0:13 ` Elliott, Robert (Server Storage)
2010-07-03 19:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-07-05 10:57 ` Robert Millan
2010-07-02 23:41 ` Isaac Dupree
2010-07-03 19:31 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-07-04 6:21 ` venkat kumar
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=4C2CEFAB.8090308@gmail.com \
--to=phcoder@gmail.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.