![]() | |||||||||||||
Messages in this thread |
On Sat, 15 Jul 2006 16:40:36 +0200 Tilman Schmidt <tilman@imap.cc> wrote: > After installing a 2.6.18-rc1-mm2 kernel without sysctl syscall support > on a standard SuSE 10.0 system, I find the following in my dmesg: > > > [ 36.955720] warning: process `showconsole' used the removed sysctl system call > > [ 39.656410] warning: process `showconsole' used the removed sysctl system call > > [ 43.304401] warning: process `showconsole' used the removed sysctl system call > > [ 45.717220] warning: process `ls' used the removed sysctl system call > > [ 45.789845] warning: process `touch' used the removed sysctl system call > > which at face value seems to contradict the statement in the help text > for the CONFIG_SYSCTL_SYSCALL option that "Nothing has been using the > binary sysctl interface for some time time now". (sic) > > Meanwhile, the second part of that sentence that "nothing should break" > by disabling it seems to hold true anyway. The system runs fine, and > activating CONFIG_SYSCTL_SYSCALL in the kernel doesn't seem to have any > effect apart from changing the word "removed" to "obsolete" in the above > messages. Thanks. Eric, that tends to make the whole idea inviable, doesn't it? - 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/ | ||||||||||||
| Last update: 2006-07-16 00:45 [from the cache] ©2003-2008 | |||||||||||||