[klink@clouddancer.com (Colonel)]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

From: Colonel <klink@clouddancer.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.17 has broken RTNETLINK
Reply-to: klink@clouddancer.com


Previously.....
On Tue, Dec 25, 2001 at 05:17:01PM +0100, Manfred Spraul wrote:
> > When I went to build 2.4.17 on a dinky box (486, 16M RAM), the
> > config option was missing.  The box is a wall mount and is not very
> > capable of multiple kernel experimentation alas.  Can someone
> > supply some background as to what has happened?
>
> It seems that RTNETLINK is now unconditionally enabled, I don't know
> why.
It's required by newer RedHat and MDK initscripts, perhaps others.
ip, iproute and similar utilities use it, and so since it's commonly
required DaveM made it unconditional...  I think the checkin comment was
something along the lines of "make it unconditional unless Alan
complains about kernel bloat" :)
        Jeff
..................................................................

So I went ahead, built 2.4.17, and BIRD doesn't work.  Dropped back to
2.4.16, enabled the RTNETLINK option and all is fine.  Something is
amiss here.

r