From: ebiederm@xmission.com (Eric W. Biederman)
To: "H . J . Lu" <hjl@lucon.org>
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: 13 May 2001 13:24:18 -0600 [thread overview]
Message-ID: <m1y9s1jbml.fsf@frodo.biederman.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> <20010513110707.A11055@lucon.org>
In-Reply-To: "H . J . Lu"'s message of "Sun, 13 May 2001 11:07:07 -0700"
"H . J . Lu" <hjl@lucon.org> writes:
> 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?
Since you have to set the command line anyway ip=dhcp is no extra
burden and it lets you use the same kernel to boot of the harddrive etc.
> > 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.
I don't believe that is a real world situation.
I boot diskless all of time and supporting a ramdisk is trivial. You
just a have a program that slaps a kernel a ramdisk, and some command
line arguments into a single image, along with a touch of adapter code
to set the kernel parameters correctly and then boot that.
Eric
next prev parent reply other threads:[~2001-05-13 19:28 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
2001-05-13 19:24 ` Eric W. Biederman [this message]
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=m1y9s1jbml.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=hjl@lucon.org \
--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