From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Warning if grub.cfg not found
Date: Sat, 30 Aug 2008 13:43:15 +0200 [thread overview]
Message-ID: <20080830114315.GC16775@thorin> (raw)
In-Reply-To: <20080823144313.GA24757@pina.cat>
Hi
On Sat, Aug 23, 2008 at 04:43:14PM +0200, Carles Pina i Estany wrote:
> Index: normal/cmdline.c
> ===================================================================
> --- normal/cmdline.c (revision 1826)
> +++ normal/cmdline.c (working copy)
> @@ -137,12 +137,17 @@ grub_cmdline_run (int nested)
> {
> grub_normal_init_page ();
> grub_setcursor (1);
> +
> + if ( nested == -1 )
nested was intended to be a "boolean"; this changes its meaning, so the name
becomes confusing. I think there's no need to reuse the variable in this part
of GRUB, and it'd be fine to add a new one IMO. However ...
> + grub_printf ("\n\
> + WARNING: GNU GRUB couldn't open /boot/grub/grub.cfg\n\
> + Falling back to GNU GRUB Command Line\n\n");
... this looks like something that belongs whereever the decision to fall
back is taken. Then once the problem is handled there, you don't need to
tell the lower layer whether to print a message or not.
Also, I think there are two separate cases:
- grub.cfg is there but can't be opened (we need to tell the user about
_why_ via grub_print_error()).
- grub.cfg is simply not there (perhaps the user intended that).
and the messages should be somewhat different for each one.
--
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-30 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 14:43 [PATCH] Warning if grub.cfg not found Carles Pina i Estany
2008-08-23 14:48 ` Carles Pina i Estany
2008-08-30 11:43 ` Robert Millan [this message]
2008-09-05 16:59 ` Carles Pina i Estany
2008-09-27 17:37 ` Carles Pina i Estany
2008-09-28 13:26 ` Robert Millan
2008-09-28 21:41 ` Carles Pina i Estany
2008-09-29 14:54 ` 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=20080830114315.GC16775@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.