From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Split of raid scan code
Date: Sat, 16 Aug 2008 14:16:54 +0200 [thread overview]
Message-ID: <20080816121654.GA6334@thorin> (raw)
In-Reply-To: <ca0f59980808160207t2752631foc20d853a722ed704@mail.gmail.com>
On Sat, Aug 16, 2008 at 05:07:00PM +0800, Bean wrote:
> Hi,
>
> This new patch seperates raid5 and raid6 recover code from raid.c, and
> place them in module raid5rec.mod and raid6rec.mod. The recover code
> is only needed when some of the disk are missing or corrupted, which
> is not common. But raid.c is installed to mbr, so size is important.
> If there is enough room in mbr for the extra module, they can use
> --modules option in grub-install to add these modules.
I find this scary in the sense that users need to know about these modules
to get the benefit of recovery, and even then, they also need to know they
are affected by this problem when they install GRUB (since otherwise they
won't be able to bootstrap).
Is it possible to detect whether recover code will be needed when grub-install
is run, and then either add the extra modules or abort with an error?
--
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-16 12:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 11:52 [PATCH] Split of raid scan code Bean
2008-08-10 12:13 ` Felix Zielcke
2008-08-10 14:29 ` Robert Millan
2008-08-10 14:45 ` Bean
2008-08-10 15:49 ` Bean
2008-08-11 18:45 ` Bean
2008-08-11 20:13 ` Bean
2008-08-11 20:24 ` Bean
2008-08-11 20:30 ` Robert Millan
2008-08-12 11:49 ` Bean
2008-08-12 12:24 ` Felix Zielcke
2008-08-12 13:32 ` Robert Millan
2008-08-13 10:05 ` Marco Gerards
2008-08-13 18:43 ` Bean
2008-08-13 20:01 ` Bean
2008-08-16 9:07 ` Bean
2008-08-16 12:16 ` Robert Millan [this message]
2008-08-16 15:20 ` Bean
2008-08-17 14:19 ` Bean
2008-08-17 14:52 ` Robert Millan
2008-08-17 15:08 ` Bean
2008-08-17 15:23 ` Robert Millan
2008-08-18 17:20 ` Bean
2008-08-23 14:51 ` Bean
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=20080816121654.GA6334@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.