The kernel and the C library as a single project

Posted Nov 30, 2010 21:12 UTC (Tue) by madscientist (subscriber, #16861)
In reply to: The kernel and the C library as a single project by sfeam
Parent article: The kernel and the C library as a single project

"Making libc a kernel module"? Was that suggested somewhere? I don't even know what that means.

The kernel and the C library as a single project

Posted Nov 30, 2010 22:27 UTC (Tue) by sfeam (subscriber, #2841) [Link] (2 responses)

It was suggested in an earlier response to this article (by pj). But yeah, I don't know exactly what that would mean either.

Libc as a module ...

Posted Dec 1, 2010 12:06 UTC (Wed) by AnswerGuy (guest, #1256) [Link]

Concievably one could use a design similar to the VDSO "linuxgate" which was part of the Linux threads NG support a few years ago.

A default might simply implement the same mmap/linkage semantics that are in use already. However, any specific kernel image could over-ride that behavior.

I'm not advocating such an approach. I'm merely speculating on what someone might reasonably mean by saying such things.

The kernel and the C library as a single project

Posted Dec 3, 2010 19:34 UTC (Fri) by Spudd86 (subscriber, #51683) [Link]

Well that wasn't the suggestion, it the suggestion was basically make linuxgate.so into libc. (OR at least make libc work like linuxgate.so, probably making it relocatable, unlike linuxgate)