From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
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: Wed, 18 Oct 2006 12:02:10 +0100 [thread overview]
Message-ID: <1161169330.9363.11.camel@localhost.localdomain> (raw)
In-Reply-To: <m1wt6y70kg.fsf@ebiederm.dsl.xmission.com>
Ar Maw, 2006-10-17 am 21:41 -0600, ysgrifennodd Eric W. Biederman:
> > Signed-off-by: Cal Peake <cp@absolutedigital.net>
>
> NAK on the grounds that it does not fix the related wording in sysctl.h
Just post a patch to fix the wording
> As for the rest of this I disagree with this direction as it is not
> fixing the status quo, just attempting to maintain it.
Good. That is how you manage system call interfaces.
> 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
> It is wrong to maintain the status quo. Who is volunteering to step
> up to the plate and maintain this thing?
For the existing values as is that matter anyone can do it, because it
just means not making a change.
Its very simple: sysctl was a neat BSD syscall that turned out to be
less ideal than using the fs for it. We added it, we supported it, we
get to keep it. We just stick notes in the docs saying "please use /proc
instead".
Alan
next prev parent reply other threads:[~2006-10-18 10:59 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 [this message]
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 ` [PATCH] " Eric W. Biederman
2006-10-19 16:35 ` 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=1161169330.9363.11.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=cp@absolutedigital.net \
--cc=ebiederm@xmission.com \
--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