|author||Samuel Thibault <firstname.lastname@example.org>||2016-11-21 00:22:17 +0100|
|committer||Samuel Thibault <email@example.com>||2016-11-21 00:22:17 +0100|
note that /dev/eth0 should be used to get it working
1 files changed, 1 insertions, 1 deletions
diff --git a/hurd/subhurd.mdwn b/hurd/subhurd.mdwn
index f8e1c32..c9fe15d 100644
@@ -113,7 +113,7 @@ proc server will kill all tasks belonging to the Subhurd.
In the subhurd, you can do basically all the same things as in the main Hurd.
You can even set up networking: Just invoke `settrans` on the
-`/servers/socket/2` as usual inside the subhurd, only using a different local
+`/servers/socket/2` as usual inside the subhurd, using `/dev/eth0`, only using a different local
IP than in the main Hurd. This way, the subhurd will be able to communicate to
the outside world with its own IP -- allowing for example to do `apt-get`
inside the subhurd, or to `ssh` directly into the subhurd.