mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: "Guillermo López Alejos" <glalejos@gmail.com>
Cc: Linh Dang <linhd@nortel.com>, linux-kernel@vger.kernel.org
Subject: Re: Environment variables inside the kernel?
Date: Mon, 22 Aug 2005 22:38:05 +0200	[thread overview]
Message-ID: <20050822203805.GA29754@aitel.hist.no> (raw)
In-Reply-To: <4fec73ca05081811488ec518e@mail.gmail.com>

On Thu, Aug 18, 2005 at 08:48:04PM +0200, Guillermo López Alejos wrote:
> 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.
> 
> Excuse me if the topic was so obvious (it was not to me) and thank you again,

It is obvious to someone who knows what the kernel is. A kernel and
a process is very different things.  A comparison to something
different:

A book always have a "page 1".  It is usually only the title, so it
is a nice place for writing some notes as well. 
(similiar to how a process have an environment.)

A library is a big collection of books, (similiar to how the kernel
manages a collection of processes.)  Still, it does not make sense
at all to talk about "page 1 of the library!"  Even if it _is_ useful
to write some library-specific notes somewhere.

The kernel does not have an environment of its own.  It manages all
the processes, and jave equal access all of the environmnts 
(albeit in a hackish way only) for process envirnments are _not_
part of the kernel/process communication interface.  

|1
Helge Hafting


  parent reply	other threads:[~2005-08-22 20:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 15:44 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
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 [this message]
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=20050822203805.GA29754@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=glalejos@gmail.com \
    --cc=linhd@nortel.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

all inboxes | Powered by JetHome®