diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2007-03-09 10:40:00 +0000 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2007-03-09 10:40:00 +0000 |
| commit | b65c6f9ead713bcd44d5dc517052803b78937451 (patch) | |
| tree | 4954a25975681df6e18a71a31c7f7a21cbed3e81 /Hurd | |
| parent | ba29778e7e3073ac665ea6a7793e6ea648bdcf7b (diff) | |
none
Diffstat (limited to 'Hurd')
| -rw-r--r-- | Hurd/SubhurdHowto.mdwn | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/Hurd/SubhurdHowto.mdwn b/Hurd/SubhurdHowto.mdwn index 83165d70..265a43b0 100644 --- a/Hurd/SubhurdHowto.mdwn +++ b/Hurd/SubhurdHowto.mdwn @@ -43,6 +43,8 @@ Now actually booting the subhurd is a simple matter of issuing (as root): NOTE: The partition must be unmounted (or mounted read-only) before you boot from it! +(In theory it shouldn't be neccessary to run the subhurd as user _root_, but in practice [that doesn't work at the moment](http://savannah.gnu.org/bugs/?17341).) + Now the subhurd should boot just like a normal Hurd started directly from GRUB, finally presenting a login prompt. The boot program serves as proxy for the subhurd, so you can control it from the terminal where you issued the boot command. To exit the subhurd, issue halt or reboot. This should exit it cleanly, but for some reason it doesn't always work; sometimes it will output various errors and then hang. If that happens, you need to kill the subhurd processes manually from a different terminal. @@ -57,4 +59,4 @@ If you want to access the subhurd processes from the outside, e.g. for debugging ## <a name="Further_Info"> Further Info </a> -<http://www.gnu.org/software/hurd/howto/subhurd.html> has some interesting suggestions, in a specific context. (Debugging Hurd startup process.) +On [[DebuggingViaSubhurds]] you can find information about how to use subhurd for debugging purposes. |