syscall(2) function (really: syscall(3))

[Boyd Roberts]

This discussion is really getting beyond the pale.  The _correct_
evaluation is probably three-fold:

   1.  In V[67] there was such a feature which worked out the
       system call from the byte following the trap instruction.

       From a historical perspective such functionality was turned
       into a library routine.

   2.  Portability in some bizzare sense.  Although, by rights there
       should be a function for every system call you'd need to make.

   3.  A simple mechanisam for adding system calls without having to
       mess with libc.  Useful for debugging during kernel development.


Now, enough!  Desist!  Stop!


Boyd Roberts			NEC Information Systems Australia

boyd at necisa.necisa.oz

``When the going gets wierd, the weird turn pro...''