From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Subject: About the CLI of both grub-mkrescue versions
Date: Tue, 23 Sep 2014 10:12:12 +0200 [thread overview]
Message-ID: <31041545521760249029@scdbackup.webframe.org> (raw)
Hi,
i recently advertised grub-mkrescue as replacement of
script snippets for creating ISO images with legacy GRUB.
But it is not very appealing to the audience if i have
to mention the different interpretation of argument "--"
by the shell script of GRUB-2.00 and by the C program
of the git master branch.
The C program demands "--" before any custom options for
xorriso -as mkisofs are accepted. Omitting it lets argp_parser()
return ARGP_ERR_UNKNOWN rather than adding the mkisofs option
to the xorriso argument list.
The shell script forwards "--" to xorriso -as mkisofs,
where it ends the mkisofs emulation. Afterwards, the additional
mkisofs options are not understood by xorriso.
We discussed this a while ago in the thread following
http://lists.gnu.org/archive/html/grub-devel/2014-01/msg00074.html
There was no conclusion.
If this CLI change shall persist, then there needs to be
some indication for scripts, whether the "--" is mandatory or
harmful.
Further, the documentation of grub-mkrescue needs to be updated.
Including the help text in the C code, which currently describes
the behavior of the shell script.
In my personal view, it would be better to keep the behavior of
GRUB-2.00. E.g. by replacing in grub-mkrescue.c line 229
return ARGP_ERR_UNKNOWN;
by a call of xorriso_push() ... i guess ...
Have a nice day :)
Thomas
next reply other threads:[~2014-09-23 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 8:12 Thomas Schmitt [this message]
2014-09-28 16:17 ` About the CLI of both grub-mkrescue versions Andrei Borzenkov
2014-09-28 16:52 ` Thomas Schmitt
2014-09-28 18:28 ` Thomas Schmitt
2014-09-29 5:04 ` Andrei Borzenkov
2014-09-29 7:07 ` Thomas Schmitt
2014-10-01 7:25 ` Thomas Schmitt
2014-10-10 18:19 ` Andrei Borzenkov
2014-10-10 20:29 ` Thomas Schmitt
2014-11-28 19:41 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-11-29 5:38 ` Andrei Borzenkov
2014-11-29 10:55 ` 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=31041545521760249029@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.