From: "H . J . Lu" <hjl@lucon.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "David S. Miller" <davem@redhat.com>,
alan@lxorguk.ukuu.org.uk,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Enable IP PNP for 2.4.4-ac8
Date: Sun, 13 May 2001 11:07:07 -0700 [thread overview]
Message-ID: <20010513110707.A11055@lucon.org> (raw)
In-Reply-To: <20010511162412.A11896@lucon.org> <15100.30085.5209.499946@pizda.ninka.net> <20010511165339.A12289@lucon.org> <m13da9ky7s.fsf@frodo.biederman.org>
In-Reply-To: <m13da9ky7s.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Sun, May 13, 2001 at 10:31:03AM -0600
On Sun, May 13, 2001 at 10:31:03AM -0600, Eric W. Biederman wrote:
> "H . J . Lu" <hjl@lucon.org> writes:
>
> > On Fri, May 11, 2001 at 04:28:05PM -0700, David S. Miller wrote:
> > >
> > > H . J . Lu writes:
> > > > 2.4.4-ac8 disables IP auto config by default even if CONFIG_IP_PNP is
> > > > defined. Here is a patch.
> > >
> > > It doesn't make any sense to enable this unless parameters are
> > > given to the kernel via the kernel command line or from firmware
> > > settings.
> >
> > >From Configure.help:
> >
> > IP: kernel level autoconfiguration
> > CONFIG_IP_PNP
> > This enables automatic configuration of IP addresses of devices and
> > of the routing table during kernel boot, based on either information
> > supplied on the kernel command line or by BOOTP or RARP protocols.
> > You need to say Y only for diskless machines requiring network
> > access to boot (in which case you want to say Y to "Root file system
> > on NFS" as well), because all other machines configure the network
> > in their startup scripts.
> >
> > It works fine for 2.4.4. However, in 2.4.4-ac8, even if I select
> > CONFIG_IP_PNP, I have to pass ip=xxxx to kernel, in addition to
> > nfsroot=x.x.x.x:/foo/bar. With 2.4.4, I can just pass
> > nfsroot=x.x.x.x:/foo/bar to kernel.
>
> O.k. Configure.help needs to be updated. "ip=on" or "ip=bootp" or
> "ip=dhcp" work fine. I wonder if I forgot to forward port the docs?
It doesn't make any senses. When I specify CONFIG_IP_PNP and
BOOTP/DHCP, I want a kernel with IP config using BOOTP/DHCP. I would
expect IP config is turned for BOOTP/DHCP by default. You can turn
it off by passing "ip=off" to kernel. Did I miss something?
>
> This same situation exists for 2.2.18 & 2.2.19 as well.
>
> The only way to get long term stability out of this is to write
> a user space client, you can put in a ramdisk. One of these days...
It doesn't work with diskless machines which don't support ramdisk
during boot.
H.J.
next prev parent reply other threads:[~2001-05-13 18:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 23:24 PATCH: Enable IP PNP for 2.4.4-ac8 H . J . Lu
2001-05-11 23:28 ` David S. Miller
2001-05-11 23:53 ` H . J . Lu
2001-05-13 16:31 ` Eric W. Biederman
2001-05-13 18:07 ` H . J . Lu [this message]
2001-05-13 19:24 ` Eric W. Biederman
2001-05-14 1:10 ` H . J . Lu
2001-05-14 1:24 ` Eric W. Biederman
2001-05-14 1:42 ` H . J . Lu
2001-05-14 3:03 ` David S. Miller
2001-05-14 10:52 ` David Woodhouse
2001-05-14 2:57 ` David S. Miller
2001-05-14 9:29 ` David Woodhouse
2001-05-14 15:08 ` Eric W. Biederman
2001-05-14 16:51 ` David Woodhouse
2001-05-14 17:20 ` Russell King
2001-05-15 13:21 ` Eric W. Biederman
2001-05-15 16:05 ` H . J . Lu
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=20010513110707.A11055@lucon.org \
--to=hjl@lucon.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=ebiederm@xmission.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