All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] grub-install message should mention --recheck
Date: Sat, 27 Dec 2008 02:48:25 -0500	[thread overview]
Message-ID: <1230364105.2633.61.camel@dv> (raw)
In-Reply-To: <87wsdmu2bx.fsf_-_@jidanni.org>

On Sat, 2008-12-27 at 04:08 +0800, jidanni@jidanni.org wrote:
> *** grub-installORIG.in	2008-12-27 02:43:09.000000000 +0800
> --- grub-install.in	2008-12-27 04:06:02.000000000 +0800
> ***************
> *** 304,310 ****
>   # Prompt the user to check if the device map is correct.
> ! echo "Installation finished. No error reported."
> ! echo "This is the contents of the device map $device_map."
> ! echo "Check if this is correct or not. If any of the lines is incorrect,"
> ! echo "fix it and re-run the script \`grub-install'."
> ! echo
>   
> --- 304,310 ----
>   # Prompt the user to check if the device map is correct.
> ! cat <<EOF
> ! Installation finished. No error reported. These are the contents of
> ! the device map $device_map. If any of the lines are incorrect, fix it
> ! and/or re-run grub-install [--recheck].
> ! EOF

Actually, grub-install should not dump the whole device.map to the
screen.  It should only show the entries that it actually used during
the installation.  If no device.map entries were used (which is true in
99% cases, I guess), there should be no message at all.

I'm not against mentioning "grub-install --recheck", although I'd like
to see comment from the users of cross-device setups where device.map is
actually used.  They should know better if grub-install --recheck" does
the right thing or grossly discards their manually crafted device.map
files.  If the later is true, maybe it's better to keep the current
message.
> 
-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-12-27  7:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 21:19 grub-install message should mention --recheck jidanni
2008-10-15 19:13 ` Isaac Dupree
2008-10-15 21:32   ` jidanni
2008-12-26 20:08     ` [PATCH] " jidanni
2008-12-27  7:48       ` Pavel Roskin [this message]
2008-12-27 22:52         ` jidanni
2009-02-07 19:58         ` 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=1230364105.2633.61.camel@dv \
    --to=proski@gnu.org \
    --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.