Messages in this thread | | | From | (richard offer) | Date | Mon, 18 Dec 2000 09:04:58 -0800 |
| |
In article <91gr99$bs81o$1@fido.engr.sgi.com> you write: > >[Dana Lacoste] >> Essentially, whatever solution is implemented MUST ensure : >> >> 1 - glibc will work properly (the headers in /usr/include/* don't >> change in an incompatible manner) >> >> 2 - programs that need to compile against the current kernel MUST >> be able to do so in a quasi-predictable manner. > >(2) is bogus. NO program needs to compile against the current kernel >headers. The only things that need to compile against the current >kernel headers are kernel modules and perhaps libc itself.
Or userland libraries/applications that need to bypass libc and make direct kernel calls because libc hasn't yet implemented those new kernel calls.
> >Peter
richard.
----------------------------------------------------------------------- Richard Offer Widget FAQ --> http://reality.sgi.com/widgetFAQ/ {X,Motif,Trust} on {Irix,Linux} __________________________________________http://reality.sgi.com/offer/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |