[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

kernel includes

Perhaps we should have kernel includes arranged like this:

/usr/include/linux -> 2.2.5/linux
/usr/include/asm -> 2.2.5/asm

The issue is kernel modules.  Right now, I think we require a user to
install kernel source for each kernel version they're using, and manually
deal with building the module for each such version.  Some people (Ted T'so
comes to mind) are actively campaigning that /usr/include/linux should
reflect the current running kernel, to address this issue.

Do you have any thoughts on this?  Is there some on-going discussion that's
already happening?



Date: Tue, 7 Dec 1999 11:19:43 +0100 (CET)
From: Ingo Molnar <mingo@chiara.csoma.elte.hu>
To: Raul Miller <moth@magenta.com>
cc: linux-kernel@vger.rutgers.edu
Subject: Re: Portable binary drivers
In-Reply-To: <19991207013506.B14004@hazel>

On Tue, 7 Dec 1999, Raul Miller wrote:

> However, note that we don't have a general way of managing include
> files for the case where the user has more than one kernel version
> they'll be using on the system.

this presumes a tightly controlled and clean package system, like Debian's
or all the RPM based ones.

-- mingo

Reply to: