diff options
Diffstat (limited to 'hurd/neighborhurd.mdwn')
| -rw-r--r-- | hurd/neighborhurd.mdwn | 22 |
1 files changed, 5 insertions, 17 deletions
diff --git a/hurd/neighborhurd.mdwn b/hurd/neighborhurd.mdwn index 76ae20d1..088214d8 100644 --- a/hurd/neighborhurd.mdwn +++ b/hurd/neighborhurd.mdwn @@ -17,23 +17,11 @@ redistribute your contributions. It is possible to run multiple instances of the Hurd in parallel, on a single instance of Mach. Other than -performance crosstalk, they are essentially isolated. +performance [[crosstalk]], they are essentially isolated. Practically, as many devices do not allow multiple -non-cooperating users, e.g., hard drive and network +non-[[cooperating]] users, e.g., hard drive and network this is not currently possible. It can be overcome, -however, by virtualizing these problematic devices. +however, by [[virtualizing]] these problematic devices. -When extra hardware is not available, it is possible to -use a sub-hurd. A sub-Hurd is like a neighbor Hurd, -however, makes use of some resources provided by another -Hurd. For instance, backing store and the console. -([[subhurd]]) - -Sub-hurds are extremely useful for debugging core -servers as it is possible to attach to them with gdb -from the parent ([[debugging_via_neighborhurds|debugging/neighborhurd]]). -This avoids -deadlock, e.g., when the instance of gdb stops the -server but requires its use. -(Note: it is possible to use [[noninvasivedebugging]], -but this is less flexible.) +When extra hardware is not available, it is possible to use a +[[sub-Hurd|subhurd]]. |