Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261975AbUK3EXI (ORCPT ); Mon, 29 Nov 2004 23:23:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261977AbUK3EXI (ORCPT ); Mon, 29 Nov 2004 23:23:08 -0500 Received: from fw.osdl.org ([65.172.181.6]:21897 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S261975AbUK3EXF (ORCPT ); Mon, 29 Nov 2004 23:23:05 -0500 Date: Mon, 29 Nov 2004 20:22:29 -0800 (PST) From: Linus Torvalds To: jt@hpl.hp.com cc: Linux kernel mailing list , David Howells , Jeff Garzik , Mariusz Mazur , "H. Peter Anvin" Subject: Re: [RFC] Splitting kernel headers and deprecating __KERNEL__ In-Reply-To: <20041130014328.GA14337@bougret.hpl.hp.com> Message-ID: References: <20041130014328.GA14337@bougret.hpl.hp.com> 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: 1057 Lines: 25 On Mon, 29 Nov 2004, Jean Tourrilhes wrote: > > So, which kernel ABI should be present on my system in > /usr/include/linux and /usr/include/asm ? Should I use the ABI from > 2.6.X, 2.4.X or 2.2.X ? I have always felt (pretty strongly) that the /usr/include/xxx contents should not be kernel-dependent, but be linked to your glibc version. That's why the symlink from /usr/include/xxx to /usr/src/linux/include/ has been deprecated for the last, oh about ten years now.. Yes, there are some _very_ specific things which might care about system calls or ioctl's that have been added later, but let's face it, we don't actually do that very often. The kernel may change at a rapid pace, but user interfaces don't, and user interfaces that would bypass the C library change even less frequently. Linus - 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/