From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Idea: Use extended blocklist format to support installing to raid device.
Date: Tue, 12 Aug 2008 10:57:31 +0200 [thread overview]
Message-ID: <20080812085731.GB381@thorin> (raw)
In-Reply-To: <ca0f59980808111838n49af5008p42dd044d0e8b18c9@mail.gmail.com>
On Tue, Aug 12, 2008 at 09:38:52AM +0800, Bean wrote:
> Hi,
>
> Currently, the blocklist format can only support traditional disk. I'm
> thinking about a new format that can be used in raid as well.
>
> The new format is like this:
>
> checksum_0 blocklist_0 checksum_1 blocklist_1 ...
>
> The checksum is the checksum of sectors in the blocklist that follows.
> For example:
>
> c1 10+20,40+10 c2 10+50
>
> This means 10-30,40-50 sectors from one disk, then 10-60 sectors from
> another disk. The checksum is used to find the correct disk.
>
> For traditional disk, we can also use this format, for example:
>
> c1 10+20,40+10
>
> This can support install to different disk than the one core.img is
> in, as it will scan all disks for the correct checksum at runtime.
IMHO, I think we should try to get rid of blocklists, or avoid reliing on
them as much as possible. Specially now that we have a good compression
ratio for msdos partmaps, and plenty of space on gpt ones.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-08-12 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 1:38 Idea: Use extended blocklist format to support installing to raid device Bean
2008-08-12 8:57 ` Robert Millan [this message]
2008-08-12 9:20 ` Bean
2008-08-12 10:27 ` Robert Millan
2008-08-13 9:53 ` Marco Gerards
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=20080812085731.GB381@thorin \
--to=rmh@aybabtu.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.