mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@mountainviewdata.com>
To: linux-kernel@vger.kernel.org
Cc: Russell King <rmk@arm.linux.org.uk>
Subject: Re: [PATCH] ip autoconfig with modules, kernel 2.4
Date: Fri, 11 May 2001 11:13:00 -0700	[thread overview]
Message-ID: <20010511111300.A27378@brian-laptop.us.mvd> (raw)
In-Reply-To: <20010510094953.C28095@brian-laptop.us.mvd> <20010510180039.D9771@flint.arm.linux.org.uk>
In-Reply-To: <20010510180039.D9771@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Thu, May 10, 2001 at 06:00:39PM +0100

On Thu, May 10, 2001 at 06:00:39PM +0100, Russell King wrote:
> 
> Hmm, if you've got userspace up and running, and loaded kernel
> modules using insmod, then what's wrong about running a dhcp,
> bootp or rarp client from userspace?

In theory, and for just ip configuration, nothing.

I should have given more information though.  My goal is actually to
NFSRoot the machine being booted.  I could not determine a way to get
the "root path" attribute given by the dhcp/bootp server from
userspace back to the kernel so that it can
"change_root()/mount_root()" with it.  I seem to recall there was a
proc interface for doing this at one time (in the 2.2 kernel) but it
seemed to have went away.

> You can then drop the
> kernel space IP autoconfiguration code.

If there were a way to tell the kernel, from userspace, for
change_root()/mount_root() where the nfsroot path was, yes.  I have
been hunting through all of the (nfs) root mount code and I don't see
it.  It looks like it can be set either on the command line, or by the
kernel implementation of bootp.  Am I missing it somewhere?

b.


  reply	other threads:[~2001-05-11 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-10 16:49 Brian J. Murrell
2001-05-10 17:00 ` Russell King
2001-05-11 18:13   ` Brian J. Murrell [this message]
2001-05-11 18:21     ` Peter Svensson
2001-05-11 18:38     ` Russell King
2001-05-11 18:49       ` Brian J. Murrell

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=20010511111300.A27378@brian-laptop.us.mvd \
    --to=brian@mountainviewdata.com \
    --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

all inboxes | Powered by JetHome®