All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carles Pina i Estany <carles@pina.cat>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Warning if grub.cfg not found
Date: Sun, 28 Sep 2008 23:41:02 +0200	[thread overview]
Message-ID: <20080928214102.GA5259@pina.cat> (raw)
In-Reply-To: <20080928132626.GA23805@thorin>


Hello,

On Sep/28/2008, Robert Millan wrote:
> On Sat, Sep 27, 2008 at 07:37:52PM +0200, Carles Pina i Estany wrote:
> > --- normal/main.c	(revision 1877)
> > +++ normal/main.c	(working copy)
> > @@ -230,7 +230,13 @@
> >    /* Try to open the config file.  */
> >    file = grub_file_open (config);
> >    if (! file)
> > -    return 0;
> > +    {
> 
> This seems to include the possibility that file cannot be read simply because
> it's not there.  Perhaps user intended so, and this shouldn't be reported as
> an error.

Do you mean that we could change:
+      grub_print_error ();

by "grub_print_warning"?

Or the whole point (warn the user if file is not there) is incorrect?

If user doesn't want a grub.cfg, he/she could "touch grub.cfg" and
that's all, no?

If some user is miss-configuring Grub2 (pointing to an invalid device,
partition, etc.) he will prefer to read "cannot find grub.cfg" than just
see a shell (it's quite confusing, or it was for me when it happened :-)
)

-- 
Carles Pina i Estany		GPG id: 0x17756391
	http://pinux.info



  reply	other threads:[~2008-09-28 21:41 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
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 [this message]
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=20080928214102.GA5259@pina.cat \
    --to=carles@pina.cat \
    --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.