Fix using netdde's eth0

9 files changed, 10 insertions, 10 deletions

diff --git a/hurd/debugging/translator/capturing_stdout_and_stderr.mdwn b/hurd/debugging/translator/capturing_stdout_and_stderr.mdwn
index 47fbbc48..c1abc7f9 100644
--- a/hurd/debugging/translator/capturing_stdout_and_stderr.mdwn
+++ b/hurd/debugging/translator/capturing_stdout_and_stderr.mdwn
@@ -16,7 +16,7 @@ silently dying all the time, without any console output:
     $ sudo settrans -fgap ↩
       /servers/socket/2 ↩
       /bin/sh -c 'exec >> /root/pfinet.log 2>&1 && date && ↩
-        /hurd/pfinet -i eth0 -a [...]'
+        /hurd/pfinet -i /dev/eth0 -a [...]'
     $ [...]
     $ cat /root/pfinet.log
     [date]
diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn
index 369ceab6..48ab872a 100644
--- a/hurd/running/qemu.mdwn
+++ b/hurd/running/qemu.mdwn
@@ -240,7 +240,7 @@ Some further notes about [[networking]] and home hints about
 
 If you just want to access the internet from within QEMU, you can setup pfinet for QEMU's user-networking:
 
-    # settrans -afgp /servers/socket/2 /hurd/pfinet -i eth0 -a 10.0.2.15 -g 10.0.2.2 -m 255.255.255.0
+    # settrans -afgp /servers/socket/2 /hurd/pfinet -i /dev/eth0 -a 10.0.2.15 -g 10.0.2.2 -m 255.255.255.0
     # echo "nameserver 10.0.2.3" > /etc/resolv.conf
 
 If you are on [[Debian GNU/Hurd|debian]], you can even use [[debian/DHCP]].
@@ -348,7 +348,7 @@ Now it is time to start-up your QEMU Hurd system and get networking going in the
 
 Once you have logged in as `root` run the `pfinet` translator with values that apply to your network. Think of your QEMU client as another computer in your network.
 
-    # settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a xxx.xxx.xxx.xxx -g xxx.xxx.xxx.xxx -m xxx.xxx.xxx.xxx
+    # settrans -fgap /servers/socket/2 /hurd/pfinet -i /dev/eth0 -a xxx.xxx.xxx.xxx -g xxx.xxx.xxx.xxx -m xxx.xxx.xxx.xxx
 
 That should do it! Do not forget to edit/update `/etc/resolv.conf` to get DNS working.
 
diff --git a/hurd/translator/lwip.mdwn b/hurd/translator/lwip.mdwn
index 2de214f2..efa59285 100644
--- a/hurd/translator/lwip.mdwn
+++ b/hurd/translator/lwip.mdwn
@@ -12,7 +12,7 @@ To configure lwip for internet connectivity, use the
 [[`settrans`|settrans]] command, like this:
 
     # settrans -fgap /servers/socket/2 /hurd/lwip ↩
-        -i eth0 -a 192.168.0.50 -g 192.168.0.1 -m 255.255.255.0
+        -i /dev/eth0 -a 192.168.0.50 -g 192.168.0.1 -m 255.255.255.0
 
 The 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.
 
diff --git a/hurd/translator/pfinet.mdwn b/hurd/translator/pfinet.mdwn
index 6097db81..f6ceec4f 100644
--- a/hurd/translator/pfinet.mdwn
+++ b/hurd/translator/pfinet.mdwn
@@ -18,7 +18,7 @@ To configure Internet connectivity, the `pfinet` (*Protocol Family Internet*)
 [[`settrans`|settrans]] command, for example like this:
 
     # settrans -fgap /servers/socket/2 /hurd/pfinet ↩
-        -i eth0 -a 192.168.0.50 -g 192.168.0.1 -m 255.255.255.0
+        -i /dev/eth0 -a 192.168.0.50 -g 192.168.0.1 -m 255.255.255.0
 
 The 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
diff --git a/hurd/translator/wishlist.mdwn b/hurd/translator/wishlist.mdwn
index 4d074df0..6554912e 100644
--- a/hurd/translator/wishlist.mdwn
+++ b/hurd/translator/wishlist.mdwn
@@ -285,7 +285,7 @@ Probably both [LVM2](http://sourceware.org/lvm2/) and the [Device-mapper](http:/
 
 A [bridging](http://bridge.sourceforge.net/faq.html) translator could improve the Hurd's networking facilities.
 
-    # settrans -cap /dev/br0 /hurd/bridge -i eth0 -i eth1 ...
+    # settrans -cap /dev/br0 /hurd/bridge -i /dev/eth0 -i eth1 ...
     # settrans -cap /servers/socket/2 /hurd/pfinet -i /dev/br0 -a ... -g ... -m ...
 
 Perhaps Linux's bridging code and [utilities](http://bridge.sourceforge.net/) can be ported (or glued in) or code from one of the BSDs.
diff --git a/microkernel/mach/gnumach/ports/xen/networking_configuration.mdwn b/microkernel/mach/gnumach/ports/xen/networking_configuration.mdwn
index 52e6db87..a41e1e64 100644
--- a/microkernel/mach/gnumach/ports/xen/networking_configuration.mdwn
+++ b/microkernel/mach/gnumach/ports/xen/networking_configuration.mdwn
@@ -83,7 +83,7 @@ eth1 is the interface that is connected to the Internet on the LAN:
 
 ## Doing settrans on domU
 
-    settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a 192.168.1.210 -g 192.168.1.1 -m 255.255.255.0
+    settrans -fgap /servers/socket/2 /hurd/pfinet -i /dev/eth0 -a 192.168.1.210 -g 192.168.1.1 -m 255.255.255.0
 
 ## /sbin/ifconfig on dom0 
 
diff --git a/open_issues/emacs.mdwn b/open_issues/emacs.mdwn
index 749649be..e00c3d4e 100644
--- a/open_issues/emacs.mdwn
+++ b/open_issues/emacs.mdwn
@@ -520,7 +520,7 @@ Thus, the rootfs still is responsive; /media/data/ is not.
       131        8     1     6     6  2  147M  880K  0.0  0:00.01  0:00.07 /usr/sbin/nullmailer-send -d
             0                                        0.0  0:00.01  0:00.07 
             1                                        0.0  0:00.00  0:00.00 
-      139        0     3     1     1 19  133M 2.19M  0.3  0:18.66  1:17.98 /hurd/pfinet -i eth0 -a 192.168.10.63 -g 192.168.10.1 -m 255.255.255.0
+      139        0     3     1     1 19  133M 2.19M  0.3  0:18.66  1:17.98 /hurd/pfinet -i /dev/eth0 -a 192.168.10.63 -g 192.168.10.1 -m 255.255.255.0
             0                                        0.0  0:00.01  0:00.03 
             1                                        0.0  0:00.00  0:00.00 
             2                                        0.1  0:12.72  0:14.56 
diff --git a/open_issues/wrong_reply_message_id.mdwn b/open_issues/wrong_reply_message_id.mdwn
index e84e2571..4148a281 100644
--- a/open_issues/wrong_reply_message_id.mdwn
+++ b/open_issues/wrong_reply_message_id.mdwn
@@ -12,7 +12,7 @@ is included in the section entitled
 
 [[!tag open_issue_gnumach open_issue_mig open_issue_glibc]]
 
-    <tschwinge> # settrans -P -a /servers/socket/2 /hurd/pfinet -i eth0 -a 192.168.10.61 -g 192.168.10.1 -m 255.255.255.0
+    <tschwinge> # settrans -P -a /servers/socket/2 /hurd/pfinet -i /dev/eth0 -a 192.168.10.61 -g 192.168.10.1 -m 255.255.255.0
     <tschwinge> Translator pid: 2289
     <tschwinge> Pausing...
     <tschwinge> pfinet: /build/buildd/hurd-20080607/build-tree/hurd/libports/create-internal.c:115: _ports_create_port_internal: Unexpected error: (ipc/mig) wrong reply message ID.
diff --git a/unsorted/CrossHurd.mdwn b/unsorted/CrossHurd.mdwn
index 69cc1dfb..3313eba3 100644
--- a/unsorted/CrossHurd.mdwn
+++ b/unsorted/CrossHurd.mdwn
@@ -76,7 +76,7 @@ Finally, a complete bootstrapped GNU system.
     nano /etc/ttys
     [remove all hashes to enable the new Hurd Console]
 
-    settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a 192.168.1.3 -g 192.168.1.1 -m 255.255.255.0
+    settrans -fgap /servers/socket/2 /hurd/pfinet -i /dev/eth0 -a 192.168.1.3 -g 192.168.1.1 -m 255.255.255.0
 
     dselect