public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: egallego@telefonica.net (Emilio Jesús Gallego Arias)
To: linux-kernel@vger.kernel.org
Cc: glalejos@gmail.com
Subject: Re: Environment variables inside the kernel?
Date: Thu, 18 Aug 2005 21:43:31 +0200	[thread overview]
Message-ID: <87wtmjhvz0.fsf@telefonica.net> (raw)
In-Reply-To: 4fec73ca05081811488ec518e@mail.gmail.com

Guillermo López Alejos <glalejos@gmail.com> writes:

> Whoa!, I did not expect so many replies. Thank you for your answers.
>
> The thing is that the Computer Architecture area of the University I
> am studying at is developing a parallel filesystem. Currently it works
> as a stand-alone program (this is why it uses resources like
> environment variables), and I have been told to integrate it in the
> Linux kernel.
>
> I have to justify changes on this filesystem code (like avoiding the
> use of environment variables) to my tutor. In this case I needed to
> find why it is not possible to use environment variables in kernel
> space.
>
> I was looking for a reference documentation which give a definition of
> environment variables that exclude their use inside the kernel, or,
> simply, I expected to find a design decision to justify this. But I
> think I have enough information with your answers, I will be able to
> elaborate a satisfactory conclusion.

A good reference is in Debian Policy Section 9.9, where it is stated:

A program must not depend on environment variables to get reasonable
defaults. (That's because these environment variables would have to be
set in a system-wide configuration file like /etc/profile, which is
not supported by all shells.)

Although this is not applicable to the kernel, goggling about this
section of the Debian Policy will give you some arguments against
environment variables in general.



  reply	other threads:[~2005-08-18 20:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 15:44 Environment variables inside the kernel? Guillermo López Alejos
2005-08-18 16:02 ` linux-os (Dick Johnson)
2005-08-18 16:03 ` jerome lacoste
2005-08-18 16:12 ` Ingo Oeser
2005-08-18 17:27   ` Christoph Lameter
2005-08-18 16:37 ` Douglas McNaught
2005-08-18 18:23   ` Linh Dang
2005-08-18 18:48     ` Guillermo López Alejos
2005-08-18 19:43       ` Emilio Jesús Gallego Arias [this message]
2005-08-21 22:12       ` Eric W. Biederman
2005-08-22  9:05         ` Guillermo López Alejos
2005-08-22  9:18           ` Eric W. Biederman
2005-08-25  8:59             ` Guillermo López Alejos
2005-08-22 20:38       ` Helge Hafting
2005-08-18 23:12     ` Alan Cox
2005-08-18 22:55       ` Peter M. Groen
2005-08-19 10:28         ` Guillermo López Alejos

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=87wtmjhvz0.fsf@telefonica.net \
    --to=egallego@telefonica.net \
    --cc=glalejos@gmail.com \
    --cc=linux-kernel@vger.kernel.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