Klibc

klibc

Developer(s)	H. Peter Anvin
Stable release	2.0.9 / April 30, 2021; 44 days ago (2021-04-30)
Repository	git.kernel.org/pub/scm/libs/klibc/klibc.git
Operating system	Linux
Type	Runtime library
License	BSD licenses/GPLv2
Website	www.kernel.org/pub/linux/libs/klibc/

In computing, klibc is a minimalistic subset of the standard C library developed by H. Peter Anvin. It was developed mainly to be used during the Linux startup process, and it is part of the early user space, i.e. components used during kernel startup, but which do not run in kernel mode.^[1] These components do not have access to the standard library (usually glibc or musl) used by normal userspace programs.

The development of klibc library was part of the 2002 effort to move some Linux initialization code out of the kernel.^[2][3][4] According to its documentation, the klibc library is optimized for correctness and small size.^[1] Because of its design, klibc is also technically suitable for embedded software in general on a variety of platforms, and is used even by full-featured programs such as the MirBSD Korn Shell. klibc is dual-licensed under a BSD three-clause^[5] (formerly four-clause, rectified via the Historical Permission Notice and Disclaimer), as well as the GPLv2 (GPLv2 only, due to Linux-kernel restrictions). This dual license allows compatibility with both non-copyleft software, as well as GPLv3 programs via the BSD license (which otherwise would not be compatible). (However, if klibc includes any GPLv2 kernel code such as that in glibc, the entire application reverts to GPLv2.)

During the Linux startup process, klibc is loaded from within a temporary RAM file system, initramfs. It is incorporated by default into initial RAM file systems that are created by the mkinitramfs script in Debian^[6] and Ubuntu. Furthermore, it has a set of small Unix utilities that are useful in early user space: cpio, dash, fstype, mkdir, mknod, mount, nfsmount, run-init, etc. all using the klibc library.^[7] An alternate strategy is to include everything in one executable, like BusyBox, which determines the requested applet via arguments or hard links or symlinks.