future of sysctls?

[Ludwig Nussel <ludwig.nussel@suse.de>]

Hi,

I'm currently struggling to find a sane way to set
net.ipv6.conf.default.use_tempaddr.
Traditionally at some point during boot "sysctl -e -q -p /etc/sysctl.conf" is
called. That doesn't really work out anymore. The aforementioned setting needs
to be applied after the ipv6 module is loaded (could be compiled into the
kernel too though) otherwise it wouldn't apply. It needs to be set before a
network driver is loaded though as the default value is copied to
interfaces specific settings at interface creation time. On top of
that there are also network interface specific sysctls that need to
be applied after an interface is created (e.g.
net.ipv6.conf.eth0.use_tempaddr).
Are there any plans to better deal with that?
Like e.g. emitting events when some part of the kernel registers a sysctl so
userspace can override the compiled in default value?
Or just offer sysfs attributes instead of sysctls?

cu
Ludwig

-- 
 (o_   Ludwig Nussel
 //\
 V_/_  http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)