11 files changed, 41 insertions, 42 deletions
diff --git a/hurd/running/chroot.mdwn b/hurd/running/chroot.mdwn
index 38bab04e..699f05a1 100644
--- a/hurd/running/chroot.mdwn
+++ b/hurd/running/chroot.mdwn
@@ -13,8 +13,7 @@ This documents the currently-needed tricks to successfully build a
 
 # Preparation
 
-For proper translator startup, the chroot storage needs to be handled by a
-separate translator, for instance:
+It can be a good idea to put the chroot on a separate translator, for instance:
 
     # dd [...] < /dev/zero > storage
     # mke2fs storage
@@ -45,3 +44,4 @@ programs inside the chroot need to be able to access them:
     # settrans -kp chroot/dev /hurd/firmlink /dev
     # settrans chroot/tmp /hurd/firmlink /tmp
     # settrans -c chroot/var/lib/dbus /hurd/firmlink /var/lib/dbus
+    # settrans -c chroot/run/dbus /hurd/firmlink /run/dbus
diff --git a/hurd/running/debian/CrossInstall.mdwn b/hurd/running/debian/CrossInstall.mdwn
index eca47a86..c7a099c6 100644
--- a/hurd/running/debian/CrossInstall.mdwn
+++ b/hurd/running/debian/CrossInstall.mdwn
@@ -17,7 +17,7 @@ Next we create a useful mountpoint and mount the partition.
 
 ### <a name="Retrieving_CrossHurd"> Retrieving CrossHurd </a>
 
-Unless you don't run Debian GNU/Linux download it from <http://packages.debian.org/crosshurd>, or simply apt-get the package from Testing or Unstable.
+Unless you don't run Debian GNU/Linux download it from <http://packages.debian.org/crosshurd>, or simply apt-get the package from Testing or Unstable. Avoid using the version from Stable since it probably is outdated. In case of problems, make sure to try the Unstable version before reporting the issue.
 
     # apt-get install crosshurd
 
@@ -36,9 +36,9 @@ Now the program starts retrieving all the necessary base packages.
 
 When all packages have been extracted we must prepare [[GRUB]] for the Hurd when we reboot. Add the below entry to your `/boot/grub/menu.lst` file to boot the Hurd in single user mode (-s). Single user mode is needed only for the two reboots when running the Native Install.
 
-    title GNU (kernel GNUmach 1.3)
+    title GNU (kernel GNUmach 1.5)
       root (hd0,2)
-      kernel /boot/gnumach.gz root=device:hd0s3 -s
+      kernel /boot/gnumach-1.5-486.gz root=device:hd0s3 -s
       module /hurd/ext2fs.static                           \
            --multiboot-command-line=${kernel-command-line} \
            --host-priv-port=${host-port}                   \
diff --git a/hurd/running/debian/dhcp.mdwn b/hurd/running/debian/dhcp.mdwn
index 8846769a..aa9adfd9 100644
--- a/hurd/running/debian/dhcp.mdwn
+++ b/hurd/running/debian/dhcp.mdwn
@@ -1,5 +1,5 @@
-[[!meta copyright="Copyright © 2011, 2012, 2013, 2014 Free Software Foundation,
-Inc."]]
+[[!meta copyright="Copyright © 2011, 2012, 2013, 2014, 2015 Free Software
+Foundation, Inc."]]
 
 [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
 id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -11,20 +11,6 @@ License|/fdl]]."]]"""]]
 
 [[!tag open_issue_porting]]
 
-In order to use DHCP, you need to install the `ifupdown` and `isc-dhcp-client`
-packages, and manually create the following symbolic link:
-
-    # ln -s ../rcS.d/S10networking /etc/rc.boot/
-
-During execution at boot time, the `S10networking` script will emit some error
-messages while trying to configure the loopback interface.  These are not
-fatal.
-
-Debian GNU/Hurd doesn't currently execute Debian standard `/etc/rcS.d/*` boot
-scripts, but has its own `/libexec/rc` script -- which integrates scripts from
-`/etc/rc.boot/` instead.
-
-
 # Open Issues
 
   * [[!debbug 616290]]
diff --git a/hurd/running/debian/qemu_image.mdwn b/hurd/running/debian/qemu_image.mdwn
index 97af245c..af22de13 100644
--- a/hurd/running/debian/qemu_image.mdwn
+++ b/hurd/running/debian/qemu_image.mdwn
@@ -16,7 +16,7 @@ Usage:
 
     $ wget http://people.debian.org/~sthibault/hurd-i386/debian-hurd.img.tar.gz
     $ tar -xz < debian-hurd.img.tar.gz
-    $ qemu -m 512 -net nic,model=rtl8139 -net user -drive cache=writeback,index=0,media=disk,file=$(echo debian-hurd-*.img)
+    $ qemu -m 512 -drive cache=writeback,file=$(echo debian-hurd-*.img)
 
 If you have troubles extracting the image, you can use
 the gz version <http://people.debian.org/~sthibault/hurd-i386/debian-hurd.img.gz>,
diff --git a/hurd/running/distrib.mdwn b/hurd/running/distrib.mdwn
index 74325e25..8c411fd0 100644
--- a/hurd/running/distrib.mdwn
+++ b/hurd/running/distrib.mdwn
@@ -1,3 +1,14 @@
+[[!template id=note text="""**GNU Free System Distribution Guidelines (GNU
+FSDG)**
+
+The [Free Software Foundation](http://www.fsf.org/) can't recommend Debian
+GNU/Hurd or the Arch distribution; we must suppose that they don't meet our
+freedom standards any more than Debian GNU/Linux and the Arch distribution
+based on the Linux kernel do.  Likewise we have not evaluated other GNU/Hurd
+distributions in regard to ethical criteria.  Please visit
+<http://www.gnu.org/distros/free-system-distribution-guidelines.html> to learn
+what those standards are."""]]
+
 Working distributions of GNU/Hurd: 
 
 * [[Debian]]
diff --git a/hurd/running/nix.mdwn b/hurd/running/nix.mdwn
index 68052948..b77404a4 100644
--- a/hurd/running/nix.mdwn
+++ b/hurd/running/nix.mdwn
@@ -47,7 +47,7 @@ Nix, and because of that, it uses per-package installation directories under
       Guix
 
 
-# <a href="guix">Guix</a>
+# <a name="guix">Guix</a>
 
 ## <http://www.gnu.org/software/guix/>
 
diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn
index 5a13a655..dfc9cdd2 100644
--- a/hurd/running/qemu.mdwn
+++ b/hurd/running/qemu.mdwn
@@ -33,7 +33,7 @@ volunteers and may not have been tested extensively.
 
 * [Disk image](http://draketo.de/dateien/hurd/bab-hurd-qemu-2008-10-29.img.tar.bz2) 
   with a short intro on translators.  Just start it with `qemu -m 512
-  -drive cache=writeback,index=0,media=disk,file=disk_image.img`.
+  -drive cache=writeback,file=disk_image.img`.
   It should work without any of the configuration below. If you want to know what you can do 
   with it, please have a look at [[its_wikipage|hurd/running/qemu/babhurd_image]]. And when 
   you use it, please [tell me your experience with it](http://draketo.de/contact)! - [[community/weblogs/ArneBab]]
@@ -139,7 +139,7 @@ First off you will need to create a disk image using `qemu-img`. I have set mine
 
 Next you will want to start up QEMU and begin the installation process.
 
-    $ qemu -m 512 -drive cache=writeback,index=0,media=disk,file=hd0.img -cdrom mini.iso -net nic,model=rtl8139 -net user
+    $ qemu -m 512 -drive cache=writeback,file=hd0.img -cdrom debian-7.0-hurd-i386-NETINST-1.iso -net nic,model=rtl8139 -net user
 
 Now at his point do the regular install using `hd0` as your harddrive. Partition it and install the base system.
 
@@ -187,7 +187,7 @@ Once you have finished installing the base system (might take some time) the sys
 
 Starting qemu/qemu-kvm:
 
-    $ kvm -m 512 -net nic,model=rtl8139 -net user,hostfwd=tcp::5555-:22 -drive cache=writeback,index=0,media=disk,file=hd0.img -vga vmware
+    $ kvm -m 512 -net nic -net user,hostfwd=tcp::5555-:22 -drive cache=writeback,file=hd0.img -vga vmware
     vmsvga_value_write: guest runs Linux.
 
 Note: See below on port forwarding in the networking section.
@@ -200,6 +200,14 @@ If you have problems with grub hanging during boot with the vmware vga driver: D
     uncomment GRUB_TERMINAL=console
     $ /usr/sbin/update-grub
 
+### `qemu: fatal: Trying to execute code outside RAM or ROM at 0x000000010010001e`
+
+This is due to a bug in QEMU, where the x86_64 QEMU binary fails to properly
+truncate addresses in 32-bit mode.  Waiting for [[!message-id
+"1386334344-24620-1-git-send-email-agraf@suse.de"]] to be applied and become
+generally available, just use the `qemu-system-i386` binary instead.
+See [[!debbug 719633]]
+
 ### A few words about the qemu console
 
 During the graphical emulation, you can use the following keys:
@@ -302,7 +310,7 @@ This is the recommended way to work with a Command Line Interface (CLI) since al
 
 a) with ssh (assuming you have installed openssh-server)
 
-    $ kvm -m 512 -net nic,model=rtl8139 -net user,hostfwd=tcp::5555-:22 -drive cache=writeback,index=0,media=disk,file=hd0.img &
+    $ kvm -m 512 -net nic -net user,hostfwd=tcp::5555-:22 -drive cache=writeback,file=hd0.img &
 
 Logging in to the running Hurd:
 
@@ -319,7 +327,7 @@ Copying files:
 
 b) with telnet (assuming you have installed a telnet server, like telnetd)
 
-    $ kvm -m 512 -net nic,model=rtl8139 -net user,hostfwd=tcp::5556-:23 -drive cache=writeback,index=0,media=disk,file=hurd-install.qemu &
+    $ kvm -m 512 -net nic -net user,hostfwd=tcp::5556-:23 -drive cache=writeback,file=hurd-install.qemu &
 
 Logging in to the running Hurd:
 
@@ -360,7 +368,7 @@ Now it is time to start-up your QEMU Hurd system and get networking going in the
 
 **Important:** Remember you may need to use the `-M isapc` or `-isa` flag if using an older version of the gnumach package.
 
-    $ qemu -m 512 -drive cache=writeback,index=0,media=disk,file=hd0.img -cdrom debian-K9-hurd-i386-CD1.iso -fda floppy.img -boot a -net nic -net tap
+    $ qemu -m 512 -drive cache=writeback,file=hd0.img -cdrom debian-K9-hurd-i386-CD1.iso -fda floppy.img -boot a -net nic -net tap
 
 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.
 
@@ -395,14 +403,7 @@ on their command line...
 
 You can also use `--append [...]`, which will show up in `/proc/cmdline`.
 
-
-# `qemu: fatal: Trying to execute code outside RAM or ROM at 0x000000010010001e`
-
-This is due to a bug in QEMU, where the x86_64 QEMU binary fails to properly
-truncate addresses in 32-bit mode.  Waiting for [[!message-id
-"1386334344-24620-1-git-send-email-agraf@suse.de"]] to be applied and become
-generally available, just use the `qemu-system-i386` binary instead.
-
+Command line above crashes with old qemu versions, for instance qemu 1.1.2 on Debian Wheezy, fixed by upgrading to wheezy-backports currently qemu 1.7.0, see [[!debbug 741873]]
 
 # Related Links
 
diff --git a/hurd/running/qemu/babhurd_image.mdwn b/hurd/running/qemu/babhurd_image.mdwn
index 6a3bb30e..0bb9c074 100644
--- a/hurd/running/qemu/babhurd_image.mdwn
+++ b/hurd/running/qemu/babhurd_image.mdwn
@@ -6,8 +6,7 @@ What this little Hurd image can do
 This is the README file accompanying a 
 [disk\_image](http://draketo.de/dateien/hurd/bab-hurd-qemu-2008-10-29.img.tar.bz2) for 
 [[running the GNU/Hurd via qemu|hurd/running/qemu]].  To run the disk image,
-just use `qemu -m 512 -drive
-cache=writeback,index=0,media=disk,file=disk_image.img`.
+just use `qemu -m 512 -drive cache=writeback,file=disk_image.img`.
 
 You can find the custom *.bashrc* used to tell the user about it as well as this text itself 
 in the Mercurial repository [hurd_intro](http://bitbucket.org/ArneBab/hurd_intro). 
diff --git a/hurd/running/qemu/microsoft_windows.mdwn b/hurd/running/qemu/microsoft_windows.mdwn
index e2c8636c..f426a793 100644
--- a/hurd/running/qemu/microsoft_windows.mdwn
+++ b/hurd/running/qemu/microsoft_windows.mdwn
@@ -48,4 +48,4 @@ Welcome, This document is for getting you started in a few minutes.
 The Debian GNU/Hurd K16 QEmu image hangs during the boot process. You may have better luck by converting the image to qcow format
 
     ..\qemu-0.9.0-x86\qemu-img.exe convert debian-hurd-k16-qemu.img -O qcow debian-hurd-k16-qemu.qcow
-    ..\qemu-0.9.0-x86\qemu.exe -L ..\qemu-0.9.0-x86 -m 512 -drive cache=writeback,index=0,media=disk,file=debian-hurd-k16-qemu.qcow -localtime -M pc
+    ..\qemu-0.9.0-x86\qemu.exe -L ..\qemu-0.9.0-x86 -m 512 -drive cache=writeback,file=debian-hurd-k16-qemu.qcow -localtime -M pc
diff --git a/hurd/running/qemu/networking.mdwn b/hurd/running/qemu/networking.mdwn
index d20b84b1..0c8e0ae8 100644
--- a/hurd/running/qemu/networking.mdwn
+++ b/hurd/running/qemu/networking.mdwn
@@ -21,7 +21,7 @@ Netmask is 255.255.255.0
 
 You can setup the pfinet translator with the command
 
-    $ settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a 10.0.2.15 -g 10.0.2.2 -m 255.255.255.0
+    $ settrans -fgap /servers/socket/2 /hurd/pfinet -i /dev/eth0 -a 10.0.2.15 -g 10.0.2.2 -m 255.255.255.0
 
 Configure nameserver in /etc/resolve.conf
 
diff --git a/hurd/running/virtualbox.mdwn b/hurd/running/virtualbox.mdwn
index 23a0b156..b48f7ebd 100644
--- a/hurd/running/virtualbox.mdwn
+++ b/hurd/running/virtualbox.mdwn
@@ -1,4 +1,5 @@
-[[!meta copyright="Copyright © 2011, 2013 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2011, 2013, 2015 Free Software Foundation,
+Inc."]]
 
 [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
 id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -21,6 +22,7 @@ supported.
 The network controller should be configured as PCnet-PCI II or PCNet-FAST III
 for instance. INTEL PRO or Paravirtualized Network do not work.
 
+Note: If your Hurd image freezes on startup with "start ext2fs: ext2fs: device:hd0s1: No such device or address", then you may need to manually edit the hard disk controller to be "IDE", because VirtualBox defaults to "SATA" which does not work. Go in to the "Storage" tab and check whether there is an entry for "Controller: SATA". If the SATA entry exists and the Hurd disk image is attached to it, delete the SATA controller and then add a new hard disk under "Controller: IDE". Restart the virtual machine. The hard disk should now be accessible via an IDE interface and Hurd should start successfully and reach the login prompt. (This is the case on VirtualBox 4.3.28 on Mac OS.)
 
 ## Converting from qemu image