Re: libc5 FAQ
Hello,
> I must second Andreas here. The ISDN stuff is an exception.
Oh come on, there are millions of exceptions. The KErnel Development has
never stoped and will never stop. There is a lot of redesign goiug on:
new routing, new address families, new arp, new console, new device drivers,
new memory management, new ACL support, new filesystems, new privelege
support, RT support...
all this stuff will come and without access to the kernel headers you always
have to wait for the next libc release (which actually depends on the fact
that the libc ppl actually know what they have to support).
I wont speak about patches to the kernel which are not in the mainstream
source. I agree that it is a very good idea to have a stable API, but on the
other hand I dont see anything wrong with relying on kernel headers for all
those little kernel tools which are exceptions. The only important thing is,
that the normal libc header do not rely on kernel headers. Then you can
compile all applications which dont need to know kernel details, and only
those tools who include <linux/..> will break.
Greetings
Bernd
--
(OO) -- Bernd_Eckenfels@Wittumstrasse13.76646Bruchsal.de --
( .. ) ecki@{inka.de,linux.de,debian.org} http://home.pages.de/~eckes/
o--o *plush* 2048/93600EFD eckes@irc +4972573817 BE5-RIPE
(O____O) If privacy is outlawed only Outlaws have privacy
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: