|author||Joshua Branson <firstname.lastname@example.org>||2018-11-26 11:51:44 -0500|
|committer||Samuel Thibault <email@example.com>||2018-11-27 22:14:38 +0100|
I added mach_msg to the gnumach syscall page. I tried to add some more information to the rpc and syscall pages.
Diffstat (limited to 'system_call.mdwn')
1 files changed, 5 insertions, 3 deletions
diff --git a/system_call.mdwn b/system_call.mdwn
index 45ed9dbe..d8a465b4 100644
@@ -10,11 +10,13 @@ is included in the section entitled [[GNU Free Documentation
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