From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Cal Peake <cp@absolutedigital.net>, Andrew Morton <akpm@osdl.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Jan Beulich <jbeulich@novell.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Undeprecate the sysctl system call
Date: Thu, 19 Oct 2006 09:09:45 -0600 [thread overview]
Message-ID: <m1irig5oli.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1161169330.9363.11.camel@localhost.localdomain> (Alan Cox's message of "Wed, 18 Oct 2006 12:02:10 +0100")
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>> The status quo is that we don't properly maintain sysctl.h and we arbitrarily
>> change the numbers.
>
> Not the core basic ones that are those people care about
I agree. It just appears that the core basic ones that people
care about is the empty set.
And we the kernel developers have made no promises to keep any
of the sysctl values constant.
>From sysctl.h:
> ****************************************************************
> ****************************************************************
> **
> ** The values in this file are exported to user space via
> ** the sysctl() binary interface. However this interface
> ** is unstable and deprecated and will be removed in the future.
> ** For a stable interface use /proc/sys.
> **
> ****************************************************************
> ****************************************************************
>From the sysctl(2) man page.
> BUGS
> The object names vary between kernel versions. THIS MAKES THIS SYSTEM CALL WORTHLESS FOR APPLICATIONS. Use the
> /proc/sys interface instead.
The empirical evidence is also that no one uses sysctl, and that no one cares.
Once we can find that one user that really cares we can have serious conversations
about keeping sys_sysctl.
Eric
next prev parent reply other threads:[~2006-10-19 15:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 15:59 config SYSCTL_SYSCALL Jan Beulich
2006-10-17 16:19 ` Randy Dunlap
2006-10-17 18:17 ` [PATCH] Restore sysctl syscall option for non-embedded users Cal Peake
2006-10-17 22:11 ` Alan Cox
2006-10-17 21:59 ` Cal Peake
2006-10-17 22:00 ` Andrew Morton
2006-10-17 23:09 ` [PATCH] Undeprecate the sysctl system call Cal Peake
2006-10-17 23:19 ` Alan Cox
2006-10-18 3:41 ` Eric W. Biederman
2006-10-18 11:02 ` Alan Cox
2006-10-18 11:33 ` Andi Kleen
2006-10-18 12:15 ` Alan Cox
2006-10-18 12:41 ` Andi Kleen
2006-10-18 12:59 ` Alan Cox
2006-10-18 13:08 ` Andi Kleen
2006-10-18 16:20 ` [PATCHv2] " Cal Peake
2006-10-18 16:28 ` Andi Kleen
2006-10-18 16:41 ` Alan Cox
2006-10-18 19:31 ` Andrew Morton
2006-10-18 22:13 ` Alan Cox
2006-10-19 15:09 ` Eric W. Biederman [this message]
2006-10-19 16:35 ` [PATCH] " Alan Cox
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=m1irig5oli.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cp@absolutedigital.net \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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