From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: grub-shell: Pass -no-pad to xorriso when building floppy images
Date: Wed, 22 Jan 2014 16:12:26 +0100 [thread overview]
Message-ID: <52DFDFDA.7030703@gmail.com> (raw)
In-Reply-To: <20140116145347.GA28616@riva.ucam.org>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On 16.01.2014 15:53, Colin Watson wrote:
> On Thu, Jan 16, 2014 at 03:05:44PM +0100, Thomas Schmitt wrote:
>> Hi,
>>
>>> + mkrescue_args="${mkrescue_args} -- -no-pad"
>>
>> This "--" is most probably not what you want.
> [...]
>> mkrescue_args="${mkrescue_args} -no-pad"
>
> This doesn't work for me:
>
> + pkgdatadir=. ./grub-mkrescue --output=/tmp/tmp.NiHozwqHYv --override-directory=./grub-core --rom-directory=/tmp/tmp.Z4Kx63yul8 --themes-directory=../../themes --compress=xz --fonts= --locales= --themes= -no-pad /boot/grub/grub.cfg=/tmp/tmp.pEYe6QbufK /boot/grub/testcase.cfg=/tmp/tmp.8OxC8koxHb
> ./grub-mkrescue: invalid option -- 'n'
> Try 'grub-mkrescue --help' or 'grub-mkrescue --usage' for more information.
>
Hm, that's annoying that xorrisofs has single-dash long parameters.
Perhaps we shouldn't use argp for parsing arguments in mkrescue but own,
simpler code.
> Thanks,
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 274 bytes --]
next prev parent reply other threads:[~2014-01-22 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 12:49 [PATCH] grub-shell: Pass -no-pad to xorriso when building floppy images Colin Watson
2014-01-16 14:05 ` Thomas Schmitt
2014-01-16 14:53 ` Colin Watson
2014-01-16 16:17 ` Thomas Schmitt
2014-01-16 16:28 ` Thomas Schmitt
2014-01-16 18:21 ` Andrey Borzenkov
2014-01-16 18:56 ` Thomas Schmitt
2014-01-16 19:13 ` Andrey Borzenkov
2014-01-16 19:43 ` Thomas Schmitt
2014-01-22 15:12 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2014-01-22 15:36 ` Thomas Schmitt
2014-01-25 16:27 ` Andrey Borzenkov
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=52DFDFDA.7030703@gmail.com \
--to=phcoder@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).