Messages in this thread | | | Date | Wed, 4 Oct 2006 22:35:01 +0200 | From | "Jesper Juhl" <> | Subject | removed sysctl system call - documentation and timeline |
| |
Hi,
With recent kernels I'm getting a lot of warnings about programs using the removed sysctl syscal.
Examples (after 5 min of uptime here) : root@dragon:/home/juhl# dmesg | grep "used the removed sysctl system call" | sort | uniq warning: process `dd' used the removed sysctl system call warning: process `ls' used the removed sysctl system call warning: process `touch' used the removed sysctl system call
and more can be found...
I'm not, as such, opposed to removing sysctl (and yes, I know what it is and what it does). What I am a little opposed to is that it is being removed on such short notice (unless I missed the memo) and that it is hidden inside EMBEDDED.
I would like to propose that, at least for 2.6.19, it be default on (as it is now), not hide it in EMBEDDED where people usually don't go, some huge deprecation warnings be added, and that it then gets the usual 6-12months before being removed (did it already get that and I'm just slow?)... ohhh, and correct the help text; it currently says "...Nothing has been using the binary sysctl interface for some time now so nothing should break if you disable sysctl syscall support" - that's obviously false as demonstrated by the above extract from my dmesg...
-- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |