On Tue, 13 Feb 2007 15:29:04 +0200 Hasso Tepper <[EMAIL PROTECTED]> wrote:
> There is long standing issue in kernel which makes using /etc/sysctl.conf > useless for boottime configuration of specific interface properties and > breaks probably any software relying on unconditional existence of the > conf trees like it was in previous kernels (I alone have written several > pieces of such software). It's broken AFAIK from 2.6.15. There has been > several notes about issue in the list, but issue haven't got any (at least > efficient) attention from developers. > > The current behaviour bites users in many ways and breaks several use cases. > I asked several times in the past "what I should do now?" question, but > got no clear answer. > > References: > http://marc.theaimsgroup.com/?l=linux-netdev&m=115685059625467&w=2 > http://marc.theaimsgroup.com/?l=linux-netdev&m=115690828822486&w=2 > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169809 > > Is there any chance this will be fixed or at least clear position is > taken by developers? Breaking userspace applications is declared nonono > several times in the past ... I'm not even against breaking it if there > is _very_ good reason to do it. Ok, but I want to know how userspace is > meant to behave now. I can't continue using crappy workarounds. As Herbert Xu said: > You can disable it in /proc/sys/net/ipv6/conf/default/... and then > reenable it on the interfaces that you actually want. And Xen is broken because it tries to use the same bogus Mac address on on all pseudo devices. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/