public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Werner Almesberger <werner@almesberger.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] boot parameters: quoting of environment variablesrevisited
Date: 20 Oct 2004 03:16:01 -0400	[thread overview]
Message-ID: <1098256561.26603.4289.camel@d845pe> (raw)
In-Reply-To: <1098253261.10571.129.camel@localhost.localdomain>

On Wed, 2004-10-20 at 02:21, Rusty Russell wrote:
> On Wed, 2004-10-20 at 08:23, Werner Almesberger wrote:
> > When passing boot parameters, they can be quoted as follows:
> > param="value"
> > 
> > Unfortunately, when passing environment variables this way, the
> > quoting causes confusion: in 2.6.7 (etc.), only the variable name
> > was placed in the environment, which caused it to be ignored.

2.6.8.1 was also broken for kernel parameters.
acpi_os_string="Brand X" resulted in acpi_os_string="" in the kernel.

> > I've sent a patch that adjusted the name, but this patch was
> > dropped. Instead, apparently a different fix was attempted in
> > 2.6.9, but this now yields param="value in the environment (note
> > the embeded double quote), which isn't much better.

In 2.6.9 acpi_os_string="Brand X" correctly results in
acpi_os_string="Brand X" in the kernel -- so at least we got that part
right.

> AFAICT 2.4 didn't remove quotes, but I have no problem with removing
> them now, and for __setup for that matter.  Hope noone relies on it.

I verified that this new patch doesn't break the acpi_os_string="Brand
X" kernel parameter.

I'm not sure what quoted parameters for init's environment are used for,
but it looks like FOO="FOO BAR" now results in
FOO=FOO BAR
in the environment.

thanks,
-Len


  reply	other threads:[~2004-10-20  7:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 22:23 [PATCH] boot parameters: quoting of environment variables revisited Werner Almesberger
2004-10-20  1:04 ` Andrew Morton
2004-10-20  1:47   ` Werner Almesberger
2004-10-20  6:21 ` Rusty Russell
2004-10-20  7:16   ` Len Brown [this message]
2004-10-20  7:35     ` [PATCH] boot parameters: quoting of environment variablesrevisited Rusty Russell
2004-10-20  7:53       ` [PATCH] boot parameters: quoting of environmentvariablesrevisited Len Brown
2004-10-20  8:03         ` Rusty Russell
2004-10-22  1:01         ` Rusty Russell
2004-10-20  9:04     ` [PATCH] boot parameters: quoting of environment variablesrevisited Werner Almesberger
2004-10-20  9:27   ` [PATCH] boot parameters: quoting of environment variables revisited Werner Almesberger

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=1098256561.26603.4289.camel@d845pe \
    --to=len.brown@intel.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=werner@almesberger.net \
    /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