From: Willy Tarreau <w@1wt.eu>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: William Estrada <MrUmunhum@popdial.com>, linux-kernel@vger.kernel.org
Subject: Re: Mounting NFS root FS
Date: Sat, 2 Dec 2006 23:55:28 +0100 [thread overview]
Message-ID: <20061202225528.GA27342@1wt.eu> (raw)
In-Reply-To: <Pine.LNX.4.61.0612022253280.25553@yvahk01.tjqt.qr>
On Sat, Dec 02, 2006 at 10:56:38PM +0100, Jan Engelhardt wrote:
>
> >> > I have been trying to make FC5's kernel do a boot with an NFS root file
> >> > system. I see
> >> > the support is in the kernel(?). I have tried this:
> >> >
> >> >> root=/dev/nfs nfsroot=10.1.1.12:/tftpboot/NFS/Root_FS
> >>
> >> This feature is almost deprecated. One is supposed to use initramfs,
> >> /sbin/ip or some DHCP client, and a mount program nowadays.
> >
> >But I think that there are plenty of light terminals still booting like
> >this which will not be able to upgrade anymore then. Even right here,
> >my web server (parisc) boot from the network that way. At least an
> >initramfs would need to be able to cope with the same syntax,
>
> No problem:
>
> <<</init<<<
> #!/bin/bash
>
> for o in `cat /proc/cmdline`; do
> case "$o" in
> nfsroot=*)
> arg="${o##nfsroot=}";
> ;;
> esac;
> done;
>
> ### further parse $arg
> >>>
>
> simplified example of how this can be accomplished. This is why
> initrds/initramfs are so much more powerful than in-kernel software.
I'm not saying initramfs is not powerful, and indeed your example is
the common way of parsing cmdline for me too. What I'm saying is that
before nfsroot stops being supported, we'll need a working replacement
(and not "### further parse $arg"), if possible within the kernel tree
so that people who used to build kernels to boot such machines will
still be able to build kernels for them, even if this implies using
an initramfs with some tools in it.
The real danger of removing support for in-kernel features like this
is to leave people with no solution at all (because they don't know
how to proceed), and their workarounds are often worse than the
problem that we tried to fix in the first place.
Willy
next prev parent reply other threads:[~2006-12-02 22:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 19:03 Mounting NFS root FS William Estrada
2006-12-02 19:07 ` Jan Engelhardt
2006-12-02 21:15 ` Willy Tarreau
2006-12-02 21:56 ` Jan Engelhardt
2006-12-02 22:55 ` Willy Tarreau [this message]
2006-12-03 2:37 ` Trond Myklebust
2006-12-03 6:02 ` Willy Tarreau
2006-12-03 7:05 ` Trond Myklebust
2006-12-03 8:30 ` Willy Tarreau
2006-12-03 11:04 ` Jan Engelhardt
2006-12-03 16:59 ` Trond Myklebust
2006-12-04 11:51 ` Janne Karhunen
2006-12-04 15:29 ` Trond Myklebust
2006-12-04 17:12 ` Janne Karhunen
2006-12-04 18:21 ` Trond Myklebust
2006-12-04 20:05 ` Janne Karhunen
2006-12-04 21:27 ` Trond Myklebust
2006-12-05 0:20 ` H. Peter Anvin
2006-12-04 20:03 ` Jan Engelhardt
2006-12-04 20:27 ` Janne Karhunen
2006-12-04 20:47 ` Trond Myklebust
2006-12-05 18:43 ` Jan Engelhardt
2006-12-05 19:37 ` Trond Myklebust
2006-12-05 19:59 ` Jan Engelhardt
2006-12-05 20:12 ` Trond Myklebust
2007-01-27 14:47 ` Jan Engelhardt
2006-12-07 22:27 ` Hans-Peter Jansen
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=20061202225528.GA27342@1wt.eu \
--to=w@1wt.eu \
--cc=MrUmunhum@popdial.com \
--cc=jengelh@linux01.gwdg.de \
--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.