Changes between Version 52 and Version 53 of FAQ

Timestamp:

2017-05-25T19:58:25Z (7 years ago)

Author:

Jakub Jermář

Comment:

Get rid of the last defeatist FAQ, formatting

FAQ

@@ -6 +6 @@
 === What is a microkernel? ===
 
-In a microkernel operating system certain functionality such as device
-drivers, file systems and networking is moved out from the kernel space to
-the user space.  Code taken out of the kernel runs as a normal user process
-or processes. The microkernel itself provides only minimal functionality
-that is necessary for user processes to run and communicate. This
-strongly contrasts with the traditional monolithic operating systems
-that keep most of these functions inside the kernel. The main rationale
-for constructing operating systems along the microkernel design lines has been
-achieving greater extensibility by forcing most of the operating
-system policies into the user space parts and leaving the microkernel
-itself free of policies as much as possible. This makes it possible to use different operating
-system personalities, potentially even in parallel, on top of the same 
-microkernel and easily change functionality that would have otherwise been
-hardcoded in the operating system kernel. Note that multiserver
-microkernels bring the additional benefit of a limited fault-tolerance:
-a bug in a kernel driver of a monolithic operating system usually
-results in the crash of the entire system whereas a bug in a user space
-driver of a microkernel operating system is confined to the user process
+In a microkernel operating system certain functionality such as device drivers, file systems and networking is moved out from the kernel space to
+the user space.  Code taken out of the kernel runs as a normal user process or processes. The microkernel itself provides only minimal functionality
+that is necessary for user processes to run and communicate. This strongly contrasts with the traditional monolithic operating systems
+that keep most of these functions inside the kernel. The main rationale for constructing operating systems along the microkernel design lines has been achieving greater extensibility by forcing most of the operating system policies into the user space parts and leaving the microkernel
+itself free of policies as much as possible. This makes it possible to use different operating system personalities, potentially even in parallel, on top of the same microkernel and easily change functionality that would have otherwise been hardcoded in the operating system kernel. Note that multiserver microkernels bring the additional benefit of a limited fault-tolerance: a bug in a kernel driver of a monolithic operating system usually
+results in the crash of the entire system whereas a bug in a user space driver of a microkernel operating system is confined to the user process
 in which the driver runs.
- 
 
 === What is a multiserver? ===
@@ -99 +86 @@
 In comparison, HelenOS supports a slightly different set of processor architectures and despite some experimental master theses' results does not currently engage in virtualization. Instead it aims to provide a coherent, dynamic, single-user system composed of many fine-grained components. HelenOS almost exclusively rolls its own original drivers, frameworks, GUIs, networking and filesystems.
 
-== Advocacy-related Questions ==
-
-=== Oh, yet another operating system? ===
-
-No, not at all. There are definitely many more various content management systems, office suites or web browsers out there than there are microkernel-based multiserver operating systems like HelenOS. See our [wiki:FAQ#Comparisonwithothersystems comparison] with other operating systems to get an idea about in what areas is HelenOS unique.
-
 == Toolchain-related Questions ==