Re: IP autoconfig doesn't work in 2.3.46

From: Jeff Garzik (jgarzik@mandrakesoft.com)
Date: Sun Feb 20 2000 - 13:17:59 EST


Wakko Warner wrote:
> > However I can't imagine ramdisk loading and starting on a machine with only
> > 4MB RAM (eg. 386SX). Question is: mark such hardware as obsolete or keep
> > Linux hardware requirement as low as possible ...

> My point is, why remove something that's not all that big and WORKS?

That's only because noone has created a quick/cookbook solution for this
yet.

> It's a
> helluva lot simpler than the userland way of doing it.

See Alan's message at the beginning of the thread. CONFIG_IP_PNP
doesn't work for all cases and interface types, it doesn't fully support
BOOTP, and it doesn't work at all for DHCP which is quickly becoming the
most common (and most maintained) dynamic net client protocol.

The cases for which CONFIG_IP_PNP applies continues to diminish over
time.

In any case it stays for 2.4, and it "has-to-go" in 2.5 so it's a moot
point either way...

-- 
Jeff Garzik         | I never vote for anyone.
Building 1024       | I always vote against.
MandrakeSoft, Inc.  |       -- W.C. Fields

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:25 EST