public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysctl: Undeprecate sys_sysctl
Date: Thu, 09 Nov 2006 22:21:13 -0700	[thread overview]
Message-ID: <m1ejsbnagm.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200611092317.26459.s0348365@sms.ed.ac.uk> (Alistair John Strachan's message of "Thu, 9 Nov 2006 23:17:26 +0000")

Alistair John Strachan <s0348365@sms.ed.ac.uk> writes:

> On Wednesday 08 November 2006 19:00, you wrote:
>> The basic issue is that despite have been deprecated and warned about
>> as a very bad thing in the man pages since its inception there are a
>> few real users of sys_sysctl.  It was my assumption that because
>> sysctl had been deprecated for all of 2.6 there would be no user space
>> users by this point, so I initially gave sys_sysctl a very short
>> deprecation period.
>>
>> Now that I know there are a few real users the only sane way to
>> proceed with deprecation is to push the time limit out to a year or
>> two work and work with distributions that have big testing pools like
>> fedora core to find these last remaining users.
>
> Eric, do you have a list of the remaining users? It'd be good to know for 
> people using Linux in an embedded environment, where they may want to switch 
> off the option, but only if it doesn't break their userspace.

They are very very few.  The ones I recall are kudzu, radvd, and
libpthreads (which doesn't care).  

There is a thread a month or so ago about this where I did a request
for testers, that listed all of the users we could find.

The reality is that I don't think kernel developers can seriously find
them.

If someone actually wants to kill sys_sysctl more power to them.  As
long as we don't add more binary numbers I think it is actually easier
to support it than to find those weird users and remove it.

Eric

  reply	other threads:[~2006-11-10  5:21 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
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 [this message]
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=m1ejsbnagm.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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