Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 16 Aug 2002 06:13:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 16 Aug 2002 06:13:27 -0400 Received: from mx1.elte.hu ([157.181.1.137]:27847 "HELO mx1.elte.hu") by vger.kernel.org with SMTP id ; Fri, 16 Aug 2002 06:13:26 -0400 Date: Fri, 16 Aug 2002 12:17:57 +0200 (CEST) From: Ingo Molnar Reply-To: Ingo Molnar To: Jamie Lokier Cc: Linus Torvalds , Subject: Re: [patch] complain about unknown CLONE_* flags In-Reply-To: <20020815233802.A30018@kushida.apsleyroad.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1349 Lines: 31 On Thu, 15 Aug 2002, Jamie Lokier wrote: > Ingo, how do you handle this sort of backward compatibility in your > latest pthreads library, or don't you do backward compatibility? [btw., it's not me doing it but Ulrich Drepper. I'm mostly doing the 'lets find out how the kernel could help' side of things.] the proper way of doing this is a way of getting fundamental kernel capabilities, not the 'probing' of the kernel in various ways. Glibc starts looking like old ISA drivers trying to do nonintrusive autodetection: 'lets try this port carefully without disturbing state, perhaps this feature is there'. one way to handle this cleanly would be to add a kernel capabilities bitmask to sysconf(), and backport this to all mainstream Linux kernels where current glibc is supposed to run. Support for something like this would be added to glibc the day it's in the main kernel. Eg. glibc has to symlink in the old pthreads library upon bootup, if the feature-set does not enable the more integrated threading library. (nevertheless your patch makes good sense, from an API-cleanliness POV.) Ingo - 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/