From: Daniel Kiper <dkiper@net-space.pl>
To: mchang@suse.com
Cc: grub-devel@gnu.org, phcoder@gmail.com
Subject: Re: [PATCH] pass kernel command line as verbatim
Date: Tue, 17 Apr 2018 18:37:06 +0200 [thread overview]
Message-ID: <20180417163706.GC21283@router-fw-old.local.net-space.pl> (raw)
In-Reply-To: <20180411091703.z3eypksfbwvdtsrj@mazu>
On Wed, Apr 11, 2018 at 05:17:03PM +0800, Michael Chang wrote:
> And this bug report seems relevant ..
>
> https://savannah.gnu.org/bugs/?49937
>
> On Wed, Apr 11, 2018 at 04:58:54PM +0800, Michael Chang wrote:
> > The command line has been processed by grub shell, then the result is expected
> > to be passed to kernel command line as verbatim according to the grub manual
> > [1][2].
> >
> > This patch removes extra escape character added as it helps nothing but only
> > creates trouble as you want them to be literal. Besides the surrounding
> > double-quotes added is kept as it used to protect space.
CC-ing Vladmir.
Hmmm... Have you tested this patch on all platforms supported by GRUB2?
I understand that current behavior is not accepted on some but I have
a feeling that somebody make it work in that way due to some reason.
Sadly I cannot find anything about that in git log. So, I have to think
how to cope with that. Or...
Vladmir, do you know why command line is processed in that way?
Daniel
next prev parent reply other threads:[~2018-04-17 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 8:58 [PATCH] pass kernel command line as verbatim Michael Chang
2018-04-11 9:17 ` Michael Chang
2018-04-17 16:37 ` Daniel Kiper [this message]
2018-04-18 7:07 ` Michael Chang
2018-04-24 10:03 ` Daniel Kiper
2018-04-26 8:42 ` Michael Chang
2018-05-09 13:23 ` Daniel Kiper
2018-05-11 7:01 ` Michael Chang
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=20180417163706.GC21283@router-fw-old.local.net-space.pl \
--to=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=mchang@suse.com \
--cc=phcoder@gmail.com \
/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.