public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 18:42:37 -0700	[thread overview]
Message-ID: <20010513184237.A10604@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> <20010513110707.A11055@lucon.org> <m1y9s1jbml.fsf@frodo.biederman.org> <20010513181006.A10057@lucon.org> <m1sni8k9io.fsf@frodo.biederman.org>
In-Reply-To: <m1sni8k9io.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Sun, May 13, 2001 at 07:24:31PM -0600

On Sun, May 13, 2001 at 07:24:31PM -0600, Eric W. Biederman wrote:
> 
> I agree it isn't intuitive, and if nfsroot=xxx is specified it should
> probably turn on if there is missing information.
> 
> But if you have to select the command line anyway....
> 
> 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.
> 

In fact, I like the idea. But passing nfsroot=xxx to kernel doesn't
imply "ip=on" is very annoying. My setup worked fine with 2.4.4. It
took me a while to figure out why it didn't work with 2.4.4-ac8.

> > Have you tried
> > ramdisk on diskless alpha, arm, m68k, mips, ppc, sh, sparc, booting
> > over network?
> 
> First the booting situation on linux with respect to multiple platform
> sucks.  We pass parameters in weird ways on every platform.  The command
> line is the only thing that stays mostly the same.  I'm looking at what
> it takes to clean that up, so we can have multiplatform bootloaders.

I don't think we have total control over how to boot over network on
all platforms. On some platforms, you may only load kernel over the
network and run from it.

> 
> I have implemented what it takes to attach a ramdisk, and if you can
> boot an arbitrary kernel it isn't hard to have a program that attaches
> a ramdisk.  
> 
> Now although I believe this is the right direction to go, you will
> notice I ported the dhcp IP auto configuration from 2.2.19 to to 2.4.x
> Buying a little more time to get this working.

Thanks. I appreciate it.


H.J.

  reply	other threads:[~2001-05-14  1:42 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
2001-05-14  1:10           ` H . J . Lu
2001-05-14  1:24             ` Eric W. Biederman
2001-05-14  1:42               ` H . J . Lu [this message]
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=20010513184237.A10604@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