From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Subject: Re: grub-mkrescue reacts vaguely on xorriso problems
Date: Sat, 15 Jul 2017 12:25:20 +0200 [thread overview]
Message-ID: <31472768394924736204@scdbackup.webframe.org> (raw)
In-Reply-To: <24380769927419764858@scdbackup.webframe.org>
Hi,
Ping.
(Bug or feature ? If bug: what exactly would be the desirable behavior ?)
--------------------------------------------------------------------------
Date: Wed, 14 Jun 2017 11:37:11 +0200
From: Thomas Schmitt <scdbackup@gmx.net>
To: grub-devel@gnu.org
Subject: grub-mkrescue reacts vaguely on xorriso problems
Hi,
on occasion of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864701
"grub-common: grub-mkrescue does nothing, successfully"
i wonder whether the reaction of grub-mkrescue on xorriso problems
is intended and appropriate. E.g. with:
grub-mkrescue -o output.iso SOURCE
--------------------------------------------------------------------------
If xorriso is missing, then grub-mkrescue reports
grub-mkrescue: warning: Your xorriso doesn't support `--grub2-boot-info'. Some features are disabled. Please use xorriso 1.2.9 or later..
and returns exit value 0.
I.e. it does not say that xorriso does not work at all and it does not
indicate the failure to its caller.
I understand from
http://git.savannah.gnu.org/cgit/grub.git/tree/util/grub-mkrescue.c#n571
that the warning is only emitted if the ISO gets prepared for x86 BIOS.
So in other cases the run might be totally silent (did not test).
Several distros ship grub-mkrescue in packages which do not mandatorily
depend on xorriso. So a clearer message from upstream about the necessity
of xorriso seems desirable.
--------------------------------------------------------------------------
If xorriso is executable and of sufficient version but the user makes a
mistake with grub-mkrescue argument SOURCE (or with some added xorrisofs
options), then xorriso aborts with e.g.
xorriso : FAILURE : Cannot determine attributes of source file '...' : No such file or directory
...
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
no ISO image emerges but grub-mkrescue exits with value 0.
A xorriso batch run returns exit value 5 if it aborts due to the -abort_on
threshold. But grub-mkrescue ignores the exit value of xorriso in
http://git.savannah.gnu.org/cgit/grub.git/tree/util/grub-mkrescue.c#n963
--------------------------------------------------------------------------
Have a nice day :)
Thomas
next prev parent reply other threads:[~2017-07-15 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 9:37 grub-mkrescue reacts vaguely on xorriso problems Thomas Schmitt
2017-07-15 10:25 ` Thomas Schmitt [this message]
2017-08-07 16:09 ` Vladimir 'phcoder' Serbinenko
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=31472768394924736204@scdbackup.webframe.org \
--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.