From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Subject: Re: xorriso and EFI boot images
Date: Tue, 20 Apr 2010 15:11:57 +0200 [thread overview]
Message-ID: <10638139212250@192.168.2.69> (raw)
In-Reply-To: <4BCD962C.5010603@gmail.com>
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
next prev parent reply other threads:[~2010-04-20 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 11:10 xorriso and EFI boot images Thomas Schmitt
2010-04-20 11:55 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-20 13:11 ` Thomas Schmitt [this message]
2010-04-22 18:00 ` Thomas Schmitt
2010-04-22 20:27 ` Seth Goldberg
2010-04-22 20:29 ` Seth Goldberg
2010-04-22 22:30 ` Thomas Schmitt
2010-04-24 19:30 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-24 19:07 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-25 8:22 ` Thomas Schmitt
2010-04-29 16:46 ` Thomas Schmitt
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=10638139212250@192.168.2.69 \
--to=scdbackup@gmx.net \
--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.