From: "Bryan O'Sullivan" <bos@serpentine.com>
To: linux-kernel@vger.kernel.org
Subject: [CFT] Move ipconfig and nfsroot support from kernel to userspace
Date: 22 May 2003 17:04:29 -0700 [thread overview]
Message-ID: <1053648269.1237.96.camel@serpentine.internal.keyresearch.com> (raw)
I've put together a new klibc snapshot, along with a set of kernel
patches, to move ipconfig and nfsroot support into userspace. These can
all be found at http://www.speakeasy.org/~bos
The klibc snapshot includes kinit, a statically linked binary that
replaces the 2.5 kernel's support for IP autoconfiguration
(CONFIG_IP_PNP, aka "ipconfig") and use of NFS as the root filesystem
(CONFIG_ROOT_NFS, aka "nfsroot").
The patches remove support for ipconfig and nfsroot, and get the kernel
into an intermediate state where it can at least boot into a kinit built
in a klibc tree.
* ipconfig-2.5.69 removes support for ipconfig, and disables the
building of nfsroot.
* nfsroot-2.5.69 removes support for nfsroot.
* initramfs-2.5.69 stops the kernel from doing the usual mount
procedure if it sees "root=initramfs" or "root=/dev/nfs" on the
kernel command line. Instead, it hands control over to whatever
it finds in initramfs.
To test, you'll need to build klibc, copy kinit into the kernel's usr
directory, blow away the .cpio file in there, and rebuild your kernel.
You can then reboot with a kernel command line such as "ip=eth0
root=/dev/nfs", and your kernel should use DHCP to configure eth0 and
mount its root filesystem from whatever NFS server the DHCP server told
it.
If you're feeling impatient and don't want to build klibc, there's a
kinit binary precompiled that you can use for testing.
Note: the kinit binary currently only supports nfsroot and ipconfig used
together. It doesn't make any sense to use them separately right now,
anyway.
<b
reply other threads:[~2003-05-22 23:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1053648269.1237.96.camel@serpentine.internal.keyresearch.com \
--to=bos@serpentine.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