summaryrefslogtreecommitdiff
path: root/faq/system_port.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2011-09-15 01:04:47 +0200
committerThomas Schwinge <thomas@schwinge.name>2011-09-15 01:04:47 +0200
commite4e6f8027157b14425904d67243bba241ce740f9 (patch)
treeb76f58fd6cf9cb114a275b56da3df65ad340d442 /faq/system_port.mdwn
parent32ea5e0d86a60edd27f73961122882f86ada4b4b (diff)
faq/system_port: Mach IPC as Linux kernel module.
Suggested by Samuel.
Diffstat (limited to 'faq/system_port.mdwn')
-rw-r--r--faq/system_port.mdwn12
1 files changed, 7 insertions, 5 deletions
diff --git a/faq/system_port.mdwn b/faq/system_port.mdwn
index eec7c917..c831c36f 100644
--- a/faq/system_port.mdwn
+++ b/faq/system_port.mdwn
@@ -38,8 +38,10 @@ attempts|microkernel/mach/gnumach/ports]] for the Alpha, MIPS and PowerPC
architectures. These have not been completed due to little developer interest.
Another option is to do the port at a different layer: port the Hurd servers to
-not run on the GNU Mach microkernel but on another [[microkernel]], or even on
-the Linux kernel, for example. While there have been experiments for [[using
-another microkernels|which_microkernel]] or [[having Mach run as a POSIX
-user-space process|open_issues/mach_on_top_of_posix]], such a port has not yet
-been completed.
+not run on the GNU Mach microkernel, but instead on top of [[another
+microkernel|which_microkernel]]. Or, even by providing a Mach emulation layer
+on top of a monolithic kernel. For example, there could be a port for [[having
+Mach run as a POSIX user-space process|open_issues/mach_on_top_of_posix]], or
+by implementing the [[Mach IPC|microkernel/mach/ipc]] facility (as well as
+several others) as Linux kernel modules. While there have been some
+experiments, no such port has been completed yet.