From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [patch] grub incorrectly identifies ext3 as fat
Date: Sat, 31 Oct 2009 11:04:51 +0100 [thread overview]
Message-ID: <1256983491.3186.2.camel@fz.local> (raw)
In-Reply-To: <57a6d2110910302344x4209dcb4mb745e30487ad7428@mail.gmail.com>
Am Samstag, den 31.10.2009, 02:44 -0400 schrieb Andrew Clausen:
> Hi,
>
> 2009/10/30 Robert Millan <rmh@aybabtu.com>:
> >> What about probing in the boot-loader?
> >
> > It's too late then. grub-install needs to know which filesystem module has
> > to be included in core.img.
>
> What if the core.img contains modules for 2 or more file systems?
>
That only happens if you use grub-install with --modules or you directly
create it with grub-mkimage.
By default there's just one module and there only needs to be one.
The one to access /boot/grub.
It doestn't make sense to include more then one fs module into core.img
With grub.efi the situation seems to be different though. But IMO it's a
bug there.
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
next prev parent reply other threads:[~2009-10-31 10:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 14:58 [patch] grub incorrectly identifies ext3 as fat Andrew Clausen
2009-10-30 18:57 ` Robert Millan
2009-10-30 19:06 ` Felix Zielcke
2009-10-30 19:19 ` Andrew Clausen
2009-10-30 22:46 ` Robert Millan
2009-10-31 6:44 ` Andrew Clausen
2009-10-31 10:04 ` Felix Zielcke [this message]
2009-10-31 15:39 ` Andrew Clausen
2009-10-31 16:06 ` Robert Millan
2009-10-31 18:43 ` Andrew Clausen
2009-10-31 18:52 ` Vladimir 'phcoder' Serbinenko
2009-11-11 16:28 ` Andrew Clausen
2009-10-31 19:15 ` Robert Millan
2009-11-09 23:14 ` Robert Millan
2009-11-11 17:24 ` Andrew Clausen
2009-10-31 18:02 ` rubisher
2009-10-31 18:46 ` Felix Zielcke
2009-10-31 10:10 ` Robert Millan
2009-10-31 10:34 ` Felix Zielcke
2009-10-31 11:30 ` Robert Millan
2009-10-31 11:38 ` Felix Zielcke
2009-10-31 18:31 ` Robert Millan
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=1256983491.3186.2.camel@fz.local \
--to=fzielcke@z-51.de \
--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.