From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Subject: Re: sanitized kernel headers
Date: Sun, 8 Jan 2006 10:31:02 +0000
User-Agent: KMail/1.8.2
References: <43BF9114.7040102@gmail.com>
In-Reply-To: <43BF9114.7040102@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="koi8-r"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200601081031.02563.andrew@walrond.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1455
Lines: 34

On Saturday 07 January 2006 09:59, Alexander E. Patrakov wrote:
>
> What is the recommended (non-dead) alternative implementation of such
> "sanitized" headers? Where is the roadmap for this area?

I still don't buy the arguments of the kernel maintainers who shun 
responsibility for this. My undoubtedly naive position is that

1) The kernel does a load of really clever low level stuff, and presents a 
stable API that the rest of the world (userspace) can use

2) Every part of that API that userspace needs should be presented to 
userspace in a consistent and reliably useable way

3) Any part of the kernel to which userspace absolutely needs access _must_ be 
part of that consistently and reliably presented API.

This 'sanitized kernel headers' mess (the single biggest _PITA_ for all small 
independent  linux distro creators/maintainers) should either

1) be unnecessary
2) be included as part of the kernel sources and acknowledged as specifically 
for use by userspace

Currently affected userspace packages include stuff like glibc, directfb, 
netfilter, iproute2, alsa, iputils, pcmcia-cs, udev and wireless-tools.

Andrew Walrond
[thumbs nose, dons hardhat, dives into hastily prepared bunker]
-
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/