none

1 files changed, 14 insertions, 3 deletions

diff --git a/Hurd/GetNetworkRunning.mdwn b/Hurd/GetNetworkRunning.mdwn
index c43bf790..3f2f6dd4 100644
--- a/Hurd/GetNetworkRunning.mdwn
+++ b/Hurd/GetNetworkRunning.mdwn
@@ -1,6 +1,17 @@
-Neal's Install guide covers this pretty well.
+First make sure that Mach recognizes your hardware. If it doesn't you have to recompile it in most cases.
 
-* Hopefully Mach will recognize your hardware. If it doesn't you have to recompile in most cases.
-* copy over your `/etc/resolv.conf` from GNU/Linux to allow your DNS to resolve correctly.
+To configure the network, the pfinet translator must be configured. This is done using the settrans command to attache a translator to a given file system node. When programs access the node, by, for example sending an RPC, the Hurd will transparently start the server to handle the request.
+
+# settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a a.b.c.d -g e.f.g.h -m i.j.k.l
+
+Here, settrans is passed several options. The first two, \`fg', force any existing translator to go away. The next two, \`ap', make both active and passive translators. This means that the operating system both starts the translator immediately and saves the settings in the node on the file system. This former also means that any error messages are sent to \`stderr'. The next argument, \`/server/socket/2', is the node that the translator is to be attached to. This is followed by the translator program to run and any arguments to give it.
+
+Help on settrans can be obtained by passing it the \`--help' option. Help on a specific translator can be gotten by invoking it from the command line with the same argument, e.g.:
+
+# /hurd/pfinet --help
+
+As there can be a lot of output, consider piping this through a pager.
+
+Finally copy over your `/etc/resolv.conf` from GNU/Linux to allow your DNS to resolve correctly.
 
 -- [[Main/GrantBow]] - 26 Oct 2002