From: "David S. Miller" <davem@redhat.com>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: "H . J . Lu" <hjl@lucon.org>,
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 20:03:33 -0700 (PDT) [thread overview]
Message-ID: <15103.19205.369749.71491@pizda.ninka.net> (raw)
In-Reply-To: <m1sni8k9io.fsf@frodo.biederman.org>
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> <m1y9s1jbml.fsf@frodo.biederman.org> <20010513181006.A10057@lucon.org> <m1sni8k9io.fsf@frodo.biederman.org>
Eric W. Biederman writes:
> Mostly I like the situation where I can compile it in and turn it on
> when I need it, instead of having to do thing differently if it is
> compiled in or not.
>
> ip=on is all it really takes.
This is the main reason I like the current 2.4.x behavior.
I hate config options that change how the core of the kernel
boot makes decisions. Things like "where is root", "what is
my network address or where do I get that information" have
no reasonable default. This is why the command line args
are there.
If you want a kernel which automatically does "foo", you have
several options already by which to do this:
1) Many platforms allow you to store a boot comand line
in the firmware (Sparc, several MIPS, PPC, etc.)
2) Failing #1, you can add a default prefix/postfix to the
kernel command line at build time if you wish, just add
some simple variable to the toplevel Makefile and have
init/main.c frob this thing onto the kernel command
line string after initially fetching it.
Really, H. J., you are asking for a static command line feature.
That's cool, so add it :-)
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-05-14 3:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 23:24 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
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 10:52 ` David Woodhouse
2001-05-14 3:03 ` David S. Miller [this message]
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=15103.19205.369749.71491@pizda.ninka.net \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.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
all inboxes | Powered by JetHome®