From: Russell King <rmk@arm.linux.org.uk>
To: "Brian J. Murrell" <brian@mountainviewdata.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ip autoconfig with modules, kernel 2.4
Date: Fri, 11 May 2001 19:38:33 +0100 [thread overview]
Message-ID: <20010511193833.B12798@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20010510094953.C28095@brian-laptop.us.mvd> <20010510180039.D9771@flint.arm.linux.org.uk> <20010511111300.A27378@brian-laptop.us.mvd>
In-Reply-To: <20010511111300.A27378@brian-laptop.us.mvd>; from brian@mountainviewdata.com on Fri, May 11, 2001 at 11:13:00AM -0700
On Fri, May 11, 2001 at 11:13:00AM -0700, Brian J. Murrell wrote:
> 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.
As long as you can get the root server IP and path from the DHCP client,
then you mount it in a directory, and use pivot_root() to change to
that directory.
See the "Changing the root device" of Documentation/initrd.txt for more
information about this.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-05-11 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 16:49 [PATCH] ip autoconfig with modules, kernel 2.4 Brian J. Murrell
2001-05-10 17:00 ` Russell King
2001-05-11 18:13 ` Brian J. Murrell
2001-05-11 18:21 ` Peter Svensson
2001-05-11 18:38 ` Russell King [this message]
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=20010511193833.B12798@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=brian@mountainviewdata.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.