public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Craig <penguin@wombat.ca>
Cc: Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, <marcelo@conectiva.com.br>
Subject: Re: [PATCH] 2.4: BOOTPC /proc info.
Date: 04 Apr 2002 09:13:54 -0700	[thread overview]
Message-ID: <m1pu1fqw59.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.42.0204031837450.711-100000@wombat>

Craig <penguin@wombat.ca> writes:

> Yes, Alan mentions the same thing.
> We didn't realize that was the long term plan.  Is that documented anywhere, or
> was it discussed on this list eons ago and 'decided'? ;)

It has been discussed on this list several times.  In fact every time
this has come up.  There are a lot of policy decisions the in kernel
dhcp/bootpc code that are generally best left to user space.  

Al Viro has gone so far as proposed moving a lot of other parts into
user space as well.  But initramfs needs to be in the kernel for that.

Eric

  reply	other threads:[~2002-04-04 16:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1017802992.2940.602.camel@phantasy.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.42.0204031759090.711-100000@wombat.suse.lists.linux.kernel>
2002-04-03 23:35   ` [PATCH] 2.4: BOOTPC /proc info Andi Kleen
2002-04-03 23:41     ` Craig
2002-04-04 16:13       ` Eric W. Biederman [this message]
2002-04-03  3:03 [PATCH] 2.4: BUG_ON (2/2) Robert Love
2002-04-03 23:09 ` [PATCH] 2.4: BOOTPC /proc info Craig
2002-04-03 23:51   ` Alan Cox

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=m1pu1fqw59.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=penguin@wombat.ca \
    /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