From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: grub2 and hybrid MBR booting
Date: Sat, 03 Jul 2010 21:31:50 +0200 [thread overview]
Message-ID: <4C2F9026.4010400@gmail.com> (raw)
In-Reply-To: <4C2E7941.2050505@isaac.cedarswampstudios.org>
[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]
On 07/03/2010 01:41 AM, Isaac Dupree wrote:
> On 07/01/10 15:42, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> After moving of partitions containing it's recommended to reinstall
>> bootloader
>
>
>> 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.
>
> Two pieces of software: bootloader (e.g. GRUB 2) and partition
> mover/rearranger (e.g. Parted).
>
> I say it would be nice if on GPT with recommended GRUB install
> (including using BIOS Boot Partition), if we did not "[recommend] to
> reinstall bootloader" but instead promised that everything* would keep
> working without any bootloader reinstall.
>
> *except if partition numbering is rearranged and grub.cfg uses
> partition numbers not UUIDs, then the grub.cfg may need editing, but
> this is no different than a Linux partition's /etc/fstab maybe needing
> editing.
>
> Is it possible for us to promise that?--what are the disadvantages of
> doing so?
>
You answered your question yourself. Every way of locating breaks on
some changes. Which exactly depends on chosen way. While fixed LBA is
perhaps the worse method for locating a partition others offer
advantages only in face of certain kind of changes and not others. You
need to know the mechanism well in order to assess if reinstall is
needed after your changes. It's easier and safer to just always reinstall
> -Isaac
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
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-03 19:32 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
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 [this message]
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=4C2F9026.4010400@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.