From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@suse.de>
Cc: "Andrew Morton" <akpm@osdl.org>,
"Linus Torvalds" <torvalds@osdl.org>,
"Jesper Juhl" <jesper.juhl@gmail.com>,
linux-kernel@vger.kernel.org, alan@redhat.com,
"Russell King" <rmk+lkml@arm.linux.org.uk>,
"Jakub Jelinek" <jakub@redhat.com>,
"Mike Galbraith" <efault@gmx.de>,
"Albert Cahalan" <acahalan@gmail.com>,
"Bill Nottingham" <notting@redhat.com>,
"Marco Roeland" <marco.roeland@xs4all.nl>,
"Michael Kerrisk" <mtk-manpages@gmx.net>
Subject: Re: [PATCH] sysctl: Undeprecate sys_sysctl (take 2)
Date: Fri, 10 Nov 2006 00:28:54 -0700 [thread overview]
Message-ID: <m1u017lpzd.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200611100750.10990.ak@suse.de> (Andi Kleen's message of "Fri, 10 Nov 2006 07:50:10 +0100")
Andi Kleen <ak@suse.de> writes:
> On Wednesday 08 November 2006 20:58, Eric W. Biederman wrote:
>>
>> The basic issue is that despite have been ``deprecated'' and
>> warned about as a very bad thing in the man pages since it's
>> inception there are a few real users of sys_sysctl.
>
> But they only seem to use a small number of actually used with
> sysctl(2) sysctls.
> I still think just maintaining a conversion table for
> those is the right thing to do.
I don't know. Every distinct user of the binary sysctl interface
used a different entry. So the fact that there are a small number of
programs and thus a small number of sysctls used I agree with. I do
not agree with the conclusion that we can predict the set of binary
sysctl that are in use. We do not get good enough feedback from
the user community.
I don't have a problem with the principle of a conversion table
if it meant that we would never add any additional binary sysctls.
> The important part really is to get rid of the crufty
> old infrastructure internally.
There is certainly some cleanup we could do there. For absolutely
simple values sysctl isn't too bad. But generated values are
horrible.
Certainly some of the parts are crufty and harder to use then
they should be. The /proc side actually seems worse than the
binary side.
That said I have some plans on attacking sysctl in a very practical
sense, because it is required to implement multiple namespaces.
Eric
next prev parent reply other threads:[~2006-11-10 7:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 19:00 [PATCH] sysctl: Undeprecate sys_sysctl Eric W. Biederman
2006-11-08 19:10 ` Jesper Juhl
2006-11-08 19:58 ` [PATCH] sysctl: Undeprecate sys_sysctl (take 2) Eric W. Biederman
2006-11-10 6:50 ` Andi Kleen
2006-11-10 7:28 ` Eric W. Biederman [this message]
2006-11-11 5:27 ` H. Peter Anvin
2006-11-08 20:49 ` [PATCH] sysctl: Undeprecate sys_sysctl Alan Cox
2006-11-08 20:55 ` Arjan van de Ven
2006-11-09 17:27 ` H. Peter Anvin
2006-11-09 23:17 ` Alistair John Strachan
2006-11-10 5:21 ` Eric W. Biederman
2006-11-10 7:56 ` Russell King
2006-11-10 8:13 ` Eric W. Biederman
2006-11-11 8:04 ` Russell King
2006-11-10 8:50 ` Alistair John Strachan
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=m1u017lpzd.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=acahalan@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--cc=efault@gmx.de \
--cc=jakub@redhat.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.roeland@xs4all.nl \
--cc=mtk-manpages@gmx.net \
--cc=notting@redhat.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.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
Powered by JetHome