From: Matthew Wilcox <matthew@wil.cx>
To: Andi Kleen <ak@suse.de>
Cc: Anton Blanchard <anton@samba.org>,
Matthew Wilcox <matthew@wil.cx>,
akpm@osdl.org, paulus@samba.org, tony.luck@intel.com,
ralf@linux-mips.org, schwidefsky@de.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Problems disabling SYSCTL
Date: Mon, 24 Jan 2005 16:14:56 +0000 [thread overview]
Message-ID: <20050124161456.GK31455@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050124160053.GB29950@wotan.suse.de>
On Mon, Jan 24, 2005 at 05:00:53PM +0100, Andi Kleen wrote:
> But seriously I wouldn't bother - the syscall interface is deprecated anyways
> and has been for a long time. The only sysctl that needs to be handled
> is (CTL_KERN,KERN_VERSION) [used by glibc], the others are not needed
> and I hoep to eventually remove them even natively.
>
> -Andi
>
> P.S.: Andrew I just discovered you removed the printk code for this.
> That's not good, how are users supposed to know it's deprecated?
How are kernel hackers to know it's been deprecated? ;-)
Index: Documentation/feature-removal-schedule.txt
===================================================================
RCS file: /var/cvs/linux-2.6/Documentation/feature-removal-schedule.txt,v
retrieving revision 1.2
diff -u -p -r1.2 feature-removal-schedule.txt
--- Documentation/feature-removal-schedule.txt 12 Jan 2005 20:14:53 -0000 1.2
+++ Documentation/feature-removal-schedule.txt 24 Jan 2005 16:13:54 -0000
@@ -32,3 +32,11 @@ Why: /proc/sys/cpu/* has been deprecated
/sys/devices/system/cpu/cpu%n/cpufreq/.
Who: Dominik Brodowski <linux@brodo.de>
+---------------------------
+
+What: The sysctl() syscall
+When: January 2006
+Files: kernel/sysctl.c
+Why: Dunno.
+Who: Andi Kleen <ak@suse.de>
+
Want to finish it off and send it to Andrew? ;-)
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-01-24 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 5:01 [PATCH] Problems disabling SYSCTL Anton Blanchard
2005-01-23 14:35 ` Matthew Wilcox
2005-01-23 19:17 ` Andi Kleen
2005-01-24 13:50 ` Anton Blanchard
2005-01-24 16:00 ` Andi Kleen
2005-01-24 16:14 ` Matthew Wilcox [this message]
2005-01-24 16:21 ` Andi Kleen
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=20050124161456.GK31455@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=tony.luck@intel.com \
/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