Re: klibc development release

["H. Peter Anvin" <hpa@zytor.com>]

Matti Aarnio wrote:
> 
>   History...   Initially I thought you are describing something
>   different from Linux model (after all, different platforms have
>   different ABIs for syscalls, leading to different call-vector
>   tables, etc.)  but no, I see no difference from this description.
> 
>   How NetBSD handles the issue, I don't know.   One interpretation
>   of what you say is that when a new architecture is added to NetBSD,
>   it will instantly inherit the entire historical set of syscalls,
>   including the obsolete ones.
> 

What NetBSD does is that they treat the system call mechanism as a
special kind of function call... like an RPC stub kind of thing.  Just
like it's not visible to the C programmer how a particular architecture
is implementing a function call, on NetBSD all one really needs to know
is the system call number (which is architecture independent!) and its
prototype, and you can generate both user-side and kernel-side stubs for
this system call, ending up with it calling a function in the generic
kernel code (sys_mmap(), or whatever.)

It seems to me that the big losers of the Linux model are the smaller
architectures, since most people aren't going to be able to know when
they're breaking something on, for example, alpha, cris or s390, and
they're certainly not going to know how to add something to them.

	-hpa