> The original thought refers to the old concept of address "class" where is
> a "class" (think subnet) went away then there was no need (and indeed
> incorrect) behaviour to still be able to have addresses on it. Thus when
> the primary address is deleted you should clear all addresses within that
I don't really think the original thought matters. What matters is that
the behavior is
a) non-obvious - you don't expect it
b) undetectable - you can't find out which alias is "primary"
c) inconsistent - some aliases act differently that other aliases
All of these violate the principle of least surprise. Whether it was
intentional or not, it behaves like a nasty hack, or worse, a bug. It is
easily fixed, and should be.
> Again - if you do not like this behaviour do not use the primary/secondary
> addressing scopes. Use /32.
Why should user-land be forced to work around what is obviously (to the
vast majority of people in this discussion) a mis-feature?
-- Tim Hockin Systems Software Engineer Sun Microsystems, Cobalt Server Appliances thockin@sun.com - 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/