> > So that applications will have to worry about compatibility with older
> > kernels in any case.
>
> Just hope then that no ifconfig or other binary has a two on the stack
> when calling this.
Thanks for asking, however, nothing bad will happen if there are no
4.4BSD-style aliases. If there are, you have no business using ifconfig
anyways, and ifconfig certainly has not configured the aliases (it
overwrites the primary address unless you use a separate name such as
eth0:0).
Actually, in net-tools-1.56, ifconfig does write AF_INET onto its ifr
(it gets shot otherwise), without clearing the address field (which
contains the txqueuelen result). However, the worst thing that can
happen is that ifconfig displays one of the aliases - but the alias
would match the txqueuelen then. How many people have 0.0.0.* or *.0.0.0
addresses configured as alias? Not too many. None, to be precise.
It will not bite portable applications either since those init their
address properly.
-- Matthias Andree - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/