DragonFly BSD DragonFly kernel List (threaded) for 2005-05  Re:
The time has come for a kernel interfacing library layer  From:
Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx> Date: Mon, 9 May
2005 07:54:47 -0700 (PDT)  :Do you mean kernel will directly
write errno into userland memory?      No, what I'm working on
is a system call 'library' layer which is     intended to be
part of libc without actually being part of libc.     The way it
will work is that libc will declare a special code section
(whether dynamic or statically linked) which the kernel will
recognize     and remap/override.  In the best case libc's code
section will simply     be a BSS section (not take up any space
in the filesystem).      This section will contain function
entry points for system calls at     fixed offsets.  I'm trying
to make this layer completely independant     of everything
else, which means that I would prefer that the kernel     simply
map the appropriate system call library into it without doing
any further reloc