From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1JLPRK-0006yl-Np for mharc-grub-devel@gnu.org; Sat, 02 Feb 2008 15:58:18 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JLPRJ-0006vf-1C for grub-devel@gnu.org; Sat, 02 Feb 2008 15:58:17 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JLPRH-0006sg-CI for grub-devel@gnu.org; Sat, 02 Feb 2008 15:58:16 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JLPRH-0006sK-1z for grub-devel@gnu.org; Sat, 02 Feb 2008 15:58:15 -0500 Received: from smtp-vbr3.xs4all.nl ([194.109.24.23]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JLPRG-0005P9-MU for grub-devel@gnu.org; Sat, 02 Feb 2008 15:58:14 -0500 Received: from localhost.localdomain (249-174.surfsnel.dsl.internl.net [145.99.174.249]) by smtp-vbr3.xs4all.nl (8.13.8/8.13.8) with ESMTP id m12KwD2n034792 for ; Sat, 2 Feb 2008 21:58:13 +0100 (CET) (envelope-from mgerards@xs4all.nl) From: Marco Gerards To: The development of GRUB 2 References: <20080202204400.GA346@thorin> Mail-Copies-To: mgerards@xs4all.nl Date: Sat, 02 Feb 2008 21:59:57 +0100 In-Reply-To: <20080202204400.GA346@thorin> (Robert Millan's message of "Sat, 2 Feb 2008 21:44:00 +0100") Message-ID: <87r6fvcbw2.fsf@xs4all.nl> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by XS4ALL Virus Scanner X-detected-kernel: by monty-python.gnu.org: FreeBSD 4.6-4.9 Subject: Re: grub.cfg parser still doesn't abort on error X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2008 20:58:17 -0000 Robert Millan writes: > Try the following grub.cfg: > > cat (memdisk)/non-existant-file > echo this point should never be reached > read > > You'll see that the echo is reached, even if cat returned an error. > > This becomes much worse when found in situations like: > > font (xxx)/some-file.pff > terminal gfxterm > > and the font wasn't loaded. Urgh! Bean committed a patch that zero'ed the error. Perhaps it was wrong? ;-) Can you try reverting it? :-) -- Marco