[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CBE80F1.5080003@redhat.com>
Date: Wed, 20 Oct 2010 13:41:05 +0800
From: Cong Wang <amwang@...hat.com>
To: Andi Kleen <ak@...ux.intel.com>
CC: Andreas Schwab <schwab@...hat.com>, linux-kernel@...r.kernel.org,
Randy Dunlap <rdunlap@...otime.net>,
Mauro Carvalho Chehab <mchehab@...hat.com>,
Len Brown <len.brown@...el.com>, Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
David Howells <dhowells@...hat.com>,
Eric Paris <eparis@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Eric Dumazet <eric.dumazet@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Andy Shevchenko <ext-andriy.shevchenko@...ia.com>,
linux-doc@...r.kernel.org
Subject: Re: [PATCH 2/2] sysctl: remove sysctl syscall
On 10/19/10 23:05, Andi Kleen wrote:
> On 10/19/2010 4:10 PM, Andreas Schwab wrote:
>>> On 10/19/2010 10:22 AM, Amerigo Wang wrote:
>>>> Remove the obsolete sysctl syscall. It was scheduled
>>>> to be removed in Sept.
>>>
>>> I thought at least older glibc was still using it? Did anyone check
>>> what happens if it sees no sysctl(2)?
>> It will fall back reading from /proc/sys.
>
> First that's slow (but ok), but that will fail if there is no /proc.
>
I strongly doubt glibc will work if there is no /proc,
a quick grep shows lots of "/proc" strings in glibc code.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists