All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub.cfg parser still doesn't abort on error
Date: Sun, 3 Feb 2008 14:09:21 +0100	[thread overview]
Message-ID: <200802031409.21922.okuji@enbug.org> (raw)
In-Reply-To: <20080203105506.GA19947@thorin>

On Sunday 03 February 2008 11:55, Robert Millan wrote:
> You mean it is intentional?  I think it's a bad plan to assume user will
> check for error status of each command, specially in situations like
> font/gfxterm.

It is quite intentional. This behavior is consistent with Bash and GRUB 
Legacy. The concept is that the user still gets something, even if there is a 
small error. Since GRUB supports rewriting menu entries at runtime, this is 
generally a good thing.

Okuji



      parent reply	other threads:[~2008-02-03 13:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 20:44 grub.cfg parser still doesn't abort on error Robert Millan
2008-02-02 20:59 ` Marco Gerards
2008-02-02 21:07   ` Robert Millan
2008-02-03  3:05     ` Bean
2008-02-03 10:55       ` Robert Millan
2008-02-03 13:05         ` Bean
2008-02-03 13:29           ` Robert Millan
2008-02-03 14:53             ` Robert Millan
2008-02-03 18:26               ` Robert Millan
2008-02-03 13:09         ` Yoshinori K. Okuji [this message]

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=200802031409.21922.okuji@enbug.org \
    --to=okuji@enbug.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.