From: ebiederm@xmission.com (Eric W. Biederman)
To: David Woodhouse <dwmw2@infradead.org>
Cc: "H . J . Lu" <hjl@lucon.org>,
"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: 15 May 2001 07:21:59 -0600 [thread overview]
Message-ID: <m1eltqkars.fsf@frodo.biederman.org> (raw)
In-Reply-To: <m1k83kj7dj.fsf@frodo.biederman.org> <m1y9s1jbml.fsf@frodo.biederman.org> <20010511162412.A11896@lucon.org> <15100.30085.5209.499946@pizda.ninka.net> <20010511165339.A12289@lucon.org> <m13da9ky7s.fsf@frodo.biederman.org> <20010513110707.A11055@lucon.org> <16874.989832587@redhat.com> <8717.989859079@redhat.com>
In-Reply-To: David Woodhouse's message of "Mon, 14 May 2001 17:51:19 +0100"
David Woodhouse <dwmw2@infradead.org> writes:
> ebiederm@xmission.com said:
> > There wasn't even DHCP support before so yes you did. As you can't
> > get the nfs mount point from bootp.
>
> Wasn't there a default? The Indy behind me seems to try to mount
> /tftpboot/172.16.18.195, so I put a filesystem there just to make it happy.
>
> It's a 2.4.3 kernel.
Duh. I forgot about the default path.
> > Well I think in the CONFIG_BLK_DEV=n case it might wind up being a
> > ramfs or tmpfs image. Something like a simplified version of tar.
>
> Well, if it stops working and stays broken, I suppose I'll just have to
> hack up a built-in command line option. ISTR ARM already has such an option.
>
> I'd rather it didn't break, though.
The clean way to handle it, and I'll take a look it to have
root=/dev/nfs (and the rdev equivalent) to set ip=on if it isn't
already. The current 2.4.4 behavior of root=/dev/hda3 doing ip
autoconfig when the code is compiled into the kernel is just bad.
Eric
next prev parent reply other threads:[~2001-05-15 13:25 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
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 [this message]
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=m1eltqkars.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=dwmw2@infradead.org \
--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