From: "Sven Köhler" <skoehler@upb.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: grub weirdness
Date: Wed, 07 May 2008 04:26:11 +0200 [thread overview]
Message-ID: <fvr409$6hj$1@ger.gmane.org> (raw)
In-Reply-To: <200805070036.32019.peter.ruskin@dsl.pipex.com>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
> When you emerged grub-0.97-r5, this was displayed on your console:
> WARN: postinst
> *** IMPORTANT NOTE: you must run grub and install
> the new version's stage1 to your MBR. Until you do,
> stage1 and stage2 will still be the old version, but
> later stages will be the new version, which could
> cause problems such as an unbootable system.
Yes, the ebuild writes that to the screen.
But silently, in the background (because every output is piped to
/dev/null - how evil!), the ebuild calls grub with some commands inside
your grub.conf.
If there's a setup-command in your grub.conf, it is indeed executed. So
if that command is outdated (something you won't notice, since that
command is not used by grub in any situation i know), the ebuild will
execute that setup-command and write to some device's boot sector. How
evil, again!
Regards,
Sven
P.S.: here's the code from grub-0.97-r5.ebuild:
if [[ -e ${dir}/grub.conf ]] ; then
egrep \
-v
'^[[:space:]]*(#|$|default|fallback|initrd|password|splashimage|timeout|title)'
\
"${dir}"/grub.conf | \
/sbin/grub --batch \
--device-map="${dir}"/device.map \
> /dev/null
fi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2008-05-07 2:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 23:10 [gentoo-user] grub weirdness »Q«
2008-05-06 23:36 ` Peter Ruskin
2008-05-07 2:26 ` Sven Köhler [this message]
2008-05-07 2:57 ` [gentoo-user] " Wolf Canis
2008-05-07 10:13 ` Sven Köhler
2008-05-08 4:47 ` »Q«
2008-05-07 3:54 ` [gentoo-user] Re: grub weirdness [solved] »Q«
2008-05-07 0:24 ` [gentoo-user] grub weirdness Ian Hilt
2008-05-07 9:22 ` Neil Bothwick
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='fvr409$6hj$1@ger.gmane.org' \
--to=skoehler@upb.de \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox