Wrong. You can't write clean glibc code that
1. Uses anything more advanced than the basic socket API
2. Configures networking in any way
3. Interfaces with the smbfs/ncpfs code
4. Uses the video capture facilities
5. Uses some of the sound facilities
the list goes on...
Standards API's are a subset of the API's for a real application. If glibc
meant I could just say 'oh I need to include blah.h' that would be fine, but
it doesnt it collides hoplelessly with the kernel includes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu