From bc652bac4ffedfb0444100a027727a5ea9dcee75 Mon Sep 17 00:00:00 2001 From: Joshua Branson Date: Mon, 26 Nov 2018 11:51:44 -0500 Subject: I added mach_msg to the gnumach syscall page. I tried to add some more information to the rpc and syscall pages. --- system_call.mdwn | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'system_call.mdwn') diff --git a/system_call.mdwn b/system_call.mdwn index 45ed9dbe..d8a465b4 100644 --- a/system_call.mdwn +++ b/system_call.mdwn @@ -10,11 +10,13 @@ is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] In an [[UNIX]]-like system, a *system call* (*syscall*) is used to request all -kinds of functionality from the operating system kernel. +kinds of functionality from the operating system kernel. On GNU/Linux, glibc +translates function calls to system calls by packing arguments appropriately +and using that trap or syscall instruction. A [[microkernel]]-based system typically won't offer a lot of system calls -- -apart from one central one, and that is *send message* -- but instead [[RPC]]s -will be used instead. +apart from one central one, and that is *send message* (mach_msg) -- but +instead [[RPC]]s will be used instead. See [[GNU Mach's system calls|microkernel/mach/gnumach/interface/syscall]]. In the [[GNU Hurd|hurd]], a lot of what is traditionlly considered to be a UNIX -- cgit v1.2.3