From: Hasso Tepper <hasso@estpak.ee>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: /proc/sys/net/ipv[46]/conf/ issue unsolved
Date: Tue, 13 Feb 2007 15:29:04 +0200 [thread overview]
Message-ID: <200702131529.04708.hasso@estpak.ee> (raw)
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.
regards,
--
Hasso Tepper
next reply other threads:[~2007-02-13 13:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 13:29 Hasso Tepper [this message]
2007-02-13 17:02 ` /proc/sys/net/ipv[46]/conf/ issue unsolved Stephen Hemminger
2007-02-13 18:04 ` Vlad Yasevich
2007-02-13 18:07 ` Hugo Santos
2007-02-13 20:16 ` Hasso Tepper
2007-02-13 18:58 ` Neil Horman
2007-02-13 19:24 ` Hugo Santos
2007-02-13 19:45 ` Neil Horman
2007-02-13 19:49 ` Hugo Santos
2007-02-13 20:10 ` Neil Horman
2007-02-13 20:18 ` Hugo Santos
2007-02-13 20:29 ` Hasso Tepper
2007-02-13 19:43 ` Vlad Yasevich
2007-02-13 20:15 ` Neil Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200702131529.04708.hasso@estpak.ee \
--to=hasso@estpak.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).