summaryrefslogtreecommitdiff
path: root/faq.en.in
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2008-07-14 16:43:52 +0200
committerThomas Schwinge <tschwinge@gnu.org>2008-07-14 17:18:52 +0200
commitfe223de474375f8a306ad33d3d5e755de1cb5c6e (patch)
treeb5a176fda7cfbd5e1411da7226db40a4ba764586 /faq.en.in
parent8a07f5c259ef2a93d976ef02096b4ac89323ca05 (diff)
microkernel/faq/multiserver_microkernel: Split out of faq.en.in.
Diffstat (limited to 'faq.en.in')
-rw-r--r--faq.en.in19
1 files changed, 0 insertions, 19 deletions
diff --git a/faq.en.in b/faq.en.in
index 16b22529..a9c1e436 100644
--- a/faq.en.in
+++ b/faq.en.in
@@ -27,25 +27,6 @@ license is included in the file COPYRIGHT.
? Generally Speaking
-?? What is a Multiserver Microkernel?
-
-{NHW} A Microkernel has nothing to do with the size of the kernel.
-Rather, it refers to the functionality that the kernel provides. It is
-generally agreed that this is; a set of interfaces to allow processes to
-communicate and a way to talk to the hardware. ``Software drivers,'' as
-I like to call them, are then implemented in user space as servers. The
-most obvious examples of these are the TCP/IP stack, the ext2 filesystem
-and NFS. In the case of the Hurd, users now have access to
-functionality that, in a monolithic kernel, they could never use, but
-now, because the server runs in user space as the user that started it,
-they may, for instance, mount an FTP filesystem in their home directory.
-
-For more information about the design of the Hurd, read the paper by
-Thomas Bushnell, BSG: ``Towards a new strategy on OS design'',
-available at:
-
- http://www.gnu.org/software/hurd/hurd-paper.html
-
?? Grammatically speaking, what is the Hurd?
{NHW} ``Hurd'', as an acronym, stands for ``Hird of Unix-Replacing