> I'd also say that understanding libc as just a set of syscall wrappers is great misunderstanding of libc complexity.
Indeed, there are reasons for glibc being so big in the first place. Also, many functions of the libc have to be optimized by hand for each target platform, often writing them in assembler. Do the kernel developers really want to put such a burden over their own shoulders?