From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [Wishlist] Better warning if grub.cfg not found
Date: Fri, 22 Aug 2008 14:56:35 +0200 [thread overview]
Message-ID: <20080822125635.GB20330@thorin> (raw)
In-Reply-To: <20080821195144.GA17536@pina.cat>
On Thu, Aug 21, 2008 at 09:51:44PM +0200, Carles Pina i Estany wrote:
>
> Hello,
>
> Doing some tests with Grub2 and qemu I've made a mistake that Grub (I
> think) could warn me better.
>
> The mistake is that I didn't have a grub.cfg file (well, I had but in
> the wrong place).
>
> The Grub2 feedback for a standard user it's just flickering (I think
> that Grub2 paints the menu) and after that shows the command line.
>
> I would expect a warning, before the command line or in the command line
> screen informing user that grub.cfg has not been found in the expected
> place.
Agreed. Can you fix this? Also, it shouldn't bother to draw the menu if it
isn't going to use it for anything.
> I'm doing the Grub2 imagine file using grub-mkrescue.
>
> Should already grub-mkrescue warn if grub.cfg is not there? (at least if
> using overlay option). I could take a look if grub-mkrescue should do
> it.
AFAICT, this problem is in GRUB itself, and shouldn't affect what grub-mkrescue
does.
--
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-22 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 19:51 [Wishlist] Better warning if grub.cfg not found Carles Pina i Estany
2008-08-22 12:56 ` Robert Millan [this message]
2008-08-22 15:22 ` Carles Pina i Estany
2008-08-23 11: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=20080822125635.GB20330@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.