From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1O4DFy-0002dB-W6 for mharc-grub-devel@gnu.org; Tue, 20 Apr 2010 09:12:51 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O4DFw-0002cZ-K5 for grub-devel@gnu.org; Tue, 20 Apr 2010 09:12:48 -0400 Received: from [140.186.70.92] (port=38505 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O4DFv-0002bc-AS for grub-devel@gnu.org; Tue, 20 Apr 2010 09:12:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O4DFr-000530-IK for grub-devel@gnu.org; Tue, 20 Apr 2010 09:12:47 -0400 Received: from mail.gmx.net ([213.165.64.20]:40177) by eggs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1O4DFr-00052S-5k for grub-devel@gnu.org; Tue, 20 Apr 2010 09:12:43 -0400 Received: (qmail invoked by alias); 20 Apr 2010 13:12:39 -0000 Received: from 165.126.46.212.adsl.ncore.de (HELO 192.168.2.69) [212.46.126.165] by mail.gmx.net (mp009) with SMTP; 20 Apr 2010 15:12:39 +0200 X-Authenticated: #2145628 X-Provags-ID: V01U2FsdGVkX1+reQVcEkar8dlwoSGCH8o/PtqAFs3JEcrXZHAH0I nMkcPYr21yBPzZ Date: Tue, 20 Apr 2010 15:11:57 +0200 From: "Thomas Schmitt" To: grub-devel@gnu.org References: <4BCD962C.5010603@gmail.com> In-Reply-To: <4BCD962C.5010603@gmail.com> Message-Id: <10638139212250@192.168.2.69> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.63 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. Subject: Re: xorriso and EFI boot images X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Apr 2010 13:12:48 -0000 Hi, > > i have scruples about the semantics of > > Platform ID which is global to the whole boot > > catalog. > Section header specifies the platform id of section entry Oh. Somehow i oversaw that. > > [detection of capabilities of xorriso version] > What about checking error status of xorrisofs --foo -o dummy.iso dummy/ ? That should work too, of course. xorriso allows to define severity threshholds for abort, for exit values with problematic runs which did not get aborted, and for verbosity. E.g.: xorriso -abort_on FAILURE \ -return_with WARNING 32 \ -report_about HINT \ -as mkisofs ... If we let the user interpret the complaints of xorriso then we should make it rather unverbous. Severity HINT is one notch lower than severity WARNING. No NOTE or UPDATE messages will appear. Using xorriso ... -as mkisofs ... rather than xorrisofs ... has several advantages. One can use its own richer option set before switching to mkisofs emulation, and one can easily use not-installed xorriso binaries, like /home/me/xorriso-0.x.y/xorriso/xorriso Have a nice day :) Thomas