From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Cal Peake <cp@absolutedigital.net>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Jan Beulich <jbeulich@novell.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Eric Biederman <ebiederm@xmission.com>
Subject: Re: [PATCH] Restore sysctl syscall option for non-embedded users
Date: Tue, 17 Oct 2006 23:11:36 +0100 [thread overview]
Message-ID: <1161123096.5014.0.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0610171401130.10587@lancer.cnet.absolutedigital.net>
Ar Maw, 2006-10-17 am 14:17 -0400, ysgrifennodd Cal Peake:
> My dmesg gets spammed to all hell with these warnings. Can we keep this
> option easily visible till it gets ripped out Jan of 2007 (see
> Documentation/feature-removal-schedule.txt for reference)?
NAK
The problem is that this option is available at all. Deprecating
syscalls especially trivial ones is fundamentally wrong. The correct fix
is to make sysctl always present except as an option for embedded and
not to deprecate it.
next prev parent reply other threads:[~2006-10-17 21:47 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 [this message]
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 ` [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=1161123096.5014.0.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