Glibc and the kernel user-space API
Posted Jan 31, 2013 1:19 UTC (Thu) by skissane
In reply to: Glibc and the kernel user-space API
Parent article: Glibc and the kernel user-space API
Officially GNU LibC is not just to support the Linux kernel, but other kernels as well. Of course, in reality Linux is the main kernel it gets used with, but the portability is a nice idea to maintain.
This suggests it is useful to distinguish new functionality into two groups:
- functions that another kernel could well implement, even if no other kernel does so right now; functionality that could potentially be standardised as part of SUS/POSIX, even if it isn't right now
- functionality which is inherently very kernel-specific, and while other kernels may provide the functionality, they are likely to do so with rather different API designs. These kinds of functions are unlikely to ever be standardised, and there is little value in providing cross-kernel APIs for them
I think module loading, kexec, etc., really belong to group (2). That then suggests, that these functions don't belong in LibC, but instead in some separate Linux-specific library or header file (a "liblinux").
to post comments)