public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Janak <J.Janak@sh.cvut.cz>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: User/kernelspace stuff to set/get kernel variables
Date: Thu, 13 Dec 2001 20:48:28 +0100	[thread overview]
Message-ID: <20011213204828.A21032@devitka.sh.cvut.cz> (raw)
In-Reply-To: <20011213155532Z284289-18284+114@vger.kernel.org> <20011213172037.B22634@devitka.sh.cvut.cz> <20011213165805.F8007@flint.arm.linux.org.uk>
In-Reply-To: <20011213165805.F8007@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Thu, Dec 13, 2001 at 04:58:05PM +0000

On Thu, Dec 13, 2001 at 04:58:05PM +0000, Russell King wrote:
> On Thu, Dec 13, 2001 at 05:20:37PM +0100, Jan Janak wrote:
> > If you pass a parameter that is not recognized by the kernel, it will be
> > passed to init as environment variable, so all you need to do is check
> > for the variable in your init scripts ($network in your example).
> 
> IIRC, Red Hat scripts grab them from /proc/cmdline

  Only parameters of the form foo=bar will be set as environment variables (if not
recognized by the kernel).
  AFAIK Red Hat scripts grab parameters of different form from /proc/cmdline.

  But parameter of the form network=dhcp will be set as environment variable and
 this is IMHO the easiest way how to get the parameter value in startup scripts.

  regards, Jan.

> 
> --
> Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
>              http://www.arm.linux.org.uk/personal/aboutme.html

  reply	other threads:[~2001-12-13 19:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13 15:54 User/kernelspace stuff to set/get kernel variables DevilKin
2001-12-13 16:03 ` Daniel Freedman
2001-12-13 16:07 ` Richard B. Johnson
2001-12-13 16:11 ` Yann E. MORIN
2001-12-13 16:20 ` Jan Janak
2001-12-13 16:58   ` Russell King
2001-12-13 19:48     ` Jan Janak [this message]
2001-12-13 20:34 ` H. Peter Anvin

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=20011213204828.A21032@devitka.sh.cvut.cz \
    --to=j.janak@sh.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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