DJ Lucas wrote:
> Randy McMurchy wrote:
>>
>> Though development stopped for a while, the effectiveness of the
>> tool did not. Other folks also recognize this.
>
> Actually, from rough memory, it did for the entire duration of 2.2
> kernels and most of 2.4, just not for basic configuration of a NIC. As
> Bruce mentioned later in this thread, the existing tools weren't easily
> modified to meet the needs of the routing for 2.2 and 2.4 kernels, or
> IPv6, so a new tool was created. I have no idea of the full
> capabilities of either tool{,set}, then or now.
Forgot to mention that it might be useful to search LFS-Dev archives for
when iproute2 debate happened for some details better than my fuzzy
memory of it. I did a little searching on the net for details and not
much came up, best quick ref I could find to support the above statement
is here in the Linux Advanced Routing & Traffic Control HOWTO:
http://lartc.org/howto/lartc.iproute2.html#LARTC.IPROUTE2.WHY
I did find a good explanation for why a single tool...but I can't find
it again. Rehashed in my own words, it manages the kernel netlink
interface, instead of 4 tools doing it.
BTW, this is probably way OT for -dev now, but I'm not sub'd to chat
anymore.
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
