Requiring a shared library to access the kernel
Posted Sep 4, 2007 14:05 UTC (Tue) by jreiser
In reply to: LinuxConf.eu: Documentation and user-space API design
Parent article: LinuxConf.eu: Documentation and user-space API design
I have written more than handful of useful software that must access the kernel directly through an absolute system call interface. The interfaces of glibc cannot provide the required services, which include self-virtualization, auto relocation, introspection, control over binding, small size, speed, etc.
The history of glibc with regard to interface stability is not pretty, either. For example: @GLIBC_PRIVATE, hp_timing, _ctype_, *stat(), errno. It's important that both the kernel interfaces and the libc interfaces be well designed and well implemented and well documented.
to post comments)