From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Subject: [PATCH] _chain can break stuff
Date: Fri, 6 Jun 2008 18:13:57 +0200 [thread overview]
Message-ID: <20080606161357.GA13885@thorin> (raw)
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
Turns out that right now, if you try to boot from LVM on ext3 with msdos
partmap, you get a core.img that is slightly too big to fit in the post-MBR
region. When you're booting from LVM, if it won't fit there you have no
other option, which makes this a big problem.
If you remove _chain from the list, it fits again. Since _chain can make the
difference between core.img fitting or not fitting, I think it should not be
included unless user requests it.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)
[-- Attachment #2: chain.diff --]
[-- Type: text/x-diff, Size: 878 bytes --]
diff -x ChangeLog -x configure -x config.h.in -x CVS -x '*~' -x '*.mk' -urp ../grub2/util/i386/pc/grub-install.in ./util/i386/pc/grub-install.in
--- ../grub2/util/i386/pc/grub-install.in 2008-06-06 17:49:43.000000000 +0200
+++ ./util/i386/pc/grub-install.in 2008-06-06 18:11:28.000000000 +0200
@@ -231,8 +231,8 @@ partmap_module=`$grub_probe --target=par
# Device abstraction module, if any (lvm, raid).
devabstraction_module=`$grub_probe --target=abstraction --device ${grub_device}`
-# _chain is often useful
-modules="$modules $fs_module $partmap_module biosdisk $devabstraction_module _chain"
+# The order in this list is critical. Be careful when modifiing it.
+modules="$modules $fs_module $partmap_module biosdisk $devabstraction_module"
$grub_mkimage --output=${grubdir}/core.img --prefix=`make_system_path_relative_to_its_root ${grubdir}`/ $modules || exit 1
next reply other threads:[~2008-06-06 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 16:13 Robert Millan [this message]
2008-06-14 19:05 ` [PATCH] _chain can break stuff 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=20080606161357.GA13885@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.