Debian GNU/Hurd Configuration
This document aims to provide an easy and relatively painless set of instructions on how to configure Debian GNU/Hurd with a minimum amount of effort.
It is based in Neal H. Walfield's
The Hurd Installation Guide.
Many thanks to Neal for his contribution.
GNU is similar in nature to any Unix-like system: after logging in, the user is
presented with a shell and the familiar Unix VFS (virtual filesystem). Although
GNU tries to be POSIX compliant, it is
Not Unix. GNU/Hurd builds upon many of
the Unix concepts and extends them to either add new functionality or to fix
what has been perceived as flaws in the original design. The most noticeable
difference is translators, user space programs which interact with the VFS.
These filesystems do not live in the kernel nor do they need to be run
as root; they only need access to the backing store and the
mount point. Another difference is that processes, rather than having a single
user identity fixed at creation time, have identity tokens which are disjoint
from the process, i.e. they may be added with the appropriate permission from
an authority or destroyed.
Being familiar with the Unix environment (and especially GNU userland, found in popular variants such as GNU/Linux) is an imperative for feeling at ease in GNU. Having experience with the Debian tools will also prove invaluable to the configuration and maintenance of a GNU/Hurd box.
This guide endeavors to make installing GNU/Hurd as painless a process as possible. If there are errors, they are most certainly the author's. Please report them, along with any other suggestions or criticisms, to him; all are gladly accepted.
You can simply use the Debian installer, see the prepared CD images. Then the following steps will be needed for proper configuration.
The Debian way is not supported yet: /etc/network/interfaces is ignored, ifup and ifdown do not work. Only the Hurdish way is supported for now.
If network does not seem to work, use the following to get debugging information from the DDE driver:
# settrans -fgap /dev/netdde /hurd/netdde
and then kill any devnode and pfinet process to let them restart with the newer
netdde. If it still does not work, please post the output of the netdde settrans
above, as well as the output of
lspci -n .
To configure the network, the pfinet translator must be configured.
This can be done by using
dhclient from the
isc-dhcp-client package, but its start has not been made
automatic yet, so one has to start it by hand, e.g.
This can also be done by hand by using
inetutils-tools package, and
available in the
Last but not least, this can be done (and recorded for good) by hand using the
settrans command to attach a translator to a given
filesystem node. When programs access the node by, for example sending an RPC,
the operating system will transparently start the server to handle the request.
# settrans -fgap /servers/socket/2 /hurd/pfinet -i /dev/eth0 -a a.b.c.d -g e.f.g.h -m i.j.k.l
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. By making the
translator active, we will immediately see any error messages on
stderr. The latter saves the translator and arguments in the node
so it can be transparently restarted later (i.e. making the setting persistent
across reboots). The options are followed by the node to which the translator
is to be attached, then the program (i.e. translator) to run and any arguments
to give it. The
-i option is the interface
will listen on,
-a is the IP address,
-g is the
-m is the network mask.
Be sure to add name servers to your
To test the configuration,
ping -c2 gateway. The
-c is important to limit the number of pings; recall,
CONTROL-C does not work in single user mode.
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 such as
To also configure IPv6 support, the same configuration has to be recorded on both /servers/socket/2 and /servers/socket/26, referencing each other so that only one is actually started, bound to both nodes:
# settrans -fgap /servers/socket/2 /hurd/pfinet -6 /servers/socket/26 -i /dev/eth0 -a a.b.c.d -g e.f.g.h -m i.j.k.l # settrans -fgap /servers/socket/26 /hurd/pfinet -4 /servers/socket/2 -i /dev/eth0 -a a.b.c.d -g e.f.g.h -m i.j.k.l
The pfinet server enables IPv6 autoconfiguration by default. The current status can be obtained from fsysopts /servers/socket/26. Addresses can also be set by hand, by using e.g. -A 2001:123:123::42/64 -G 2001:123:123::1.
The configuration of pfinet can also be changed live (without record on disk) by using fsysopts:
# fsysopts /servers/socket/2 /hurd/pfinet --interface=/dev/eth0 --address=10.3.0.1 --netmask=255.255.0.0 --gateway=10.3.0.128 # fsysopts /server/socket/2 -a 10.3.0.2 -m 255.255.0.0 -g 10.3.0.128
A firewall can be set up by interposing the eth-filter translator, for instance, this prevents access to port 22:
# settrans -c /dev/eth0f /hurd/eth-filter -i /dev/eth0 -r "not port 22"
The filtered device, /dev/eth0f, can then be given to pfinet or dhclient instead of /dev/eth0.
The layout of the keyboard can be configured through the standard
keyboard-configuration package. Make sure that it is installed, and
dpkg-reconfigure keyboard-configuration. Only the layout is
supported, variants are not (yet). The effect will not
be immediate, as the console needs to be restarted to take the parameter into
account. Rebooting should be fine for instance.
Other File Systems
/etc/fstab to add any additional filesystems as well as
swap space. It is very important that swap space be used; the Hurd
will be an order of magnitude more stable. Note that the Hurd can transparently
share a swap partition with Linux but will happily page to any device including
a raw partition such as your home partition. By default,
the only editors installed by the base distribution.
Here is an example
# <file system> <mount point> <type> <options> <dump> <pass> /dev/hd0s1 / ext2 rw 0 1 /dev/hd0s2 /home ext2 rw 0 2 /dev/hd0s3 none swap sw 0 0
/dev device entry is missing, remember to create it using the
# cd /dev # ./MAKEDEV hd0s1 hd0s2 hd0s3
You can also mount a filesystem by hand by calling
# settrans /mnt /hurd/ext2fs /dev/hd0s5
The idea behind this command is that you set on the
/mnt node the
/hurd/ext2fs /dev/hd0s5 translator.
get executed and start read/writing
/dev/hd0s5 and show its content
/mnt. More information can be found in the
To mount an nfs filesystem,
/hurd/nfs translator is used. When
run as non-root, the translator will connect to the server using a port above
1023. By default, GNU/Linux will reject this. To tell GNU/Linux to accept
connections originating from a non-reserved port, add the
insecure option to the export line. Here is an example
/etc/exports file assuming the client's ip address is
To mount this from a GNU box and assuming that nfs server's ip address is
# settrans -cgap /mount/point /hurd/nfs 192.168.1.1:/home
Have fun with Debian GNU/Hurd
Now, what nice things can we do with the Hurd?
Mount disk images
Accessing the content of a CD image is a bit tedious with standard Unix systems if you are not root. On GNU/Hurd, it amounts to this:
settrans ~/mnt /hurd/iso9660fs CD_image.iso
And it is completely safe: the
iso9660fs translator is running
under your identity, not root. You can even code your own translator for any
kind of filesystem. Yes, this is like FUSE. Without all the kludge.
The following sets up a transparent
settrans -c /ftp: /hurd/hostmux /hurd/ftpfs /
cd to e.g.
/ftp://ftp.gnu.org/, and run
Yes, you can from your home simply run
tar xf ftp://ftp.gnu.org/pub/gnu/gcc/gcc-4.6.0/gcc-4.6.0.tar.bz2 !
A sub-Hurd is a complete subsystem. Very much like virtualization containers on first sight. Except that you do not need to be root at all to run one.
gdb ext2fs, pfinet, ...
Yes, you can run gdb on e.g. the ext2fs implementation, the
pfinet TCP/IP stack, etc.
And many more things!
Some in-progress work include
Installing More Packages
There are several ways to add packages. Downloading and using
dpkg -i works but is very inconvenient. The easiest method
is to use
and add one of the following unreleased entries from one of the
http://www.debian-ports.org/mirrors and install the
deb http://ftp.debian-ports.org/debian unreleased main
http://ftp.debian-ports.org/ and its mirrors contain packages that have hacks or patches that have not yet been integrated upstream or in Debian.
And unstable from one of the Debian mirrors (see http://www.debian.org/mirror/list for the complete list) carrying this architecture (if apt says it is a "bad archive mirror", try another one):
deb http://ftp.fr.debian.org/debian unstable main
If when doing your first
dpkg complains of
missing programs, get root in a login shell (i.e.
su -, not just
If GNU Mach does not recognize your network card or you use a modem, the only
way to upgrade will be to download the packages and then transfer them to the
GNU system. The easiest way to do this is to use apt off-line. Refer to
/usr/share/doc/apt-doc/offline.text.gz for detailed instructions.
The Hurd console
Besides the Mach console you encountered during installation, the GNU/Hurd features a powerful user-space console providing virtual terminals. If you have installed in pseudo-graphical mode, it should be started automatically at boot, otherwise you can start it manually with the following command:
# console -d vga -d pc_mouse --repeat=mouse -d pc_kbd --repeat=kbd -d generic_speaker -c /dev/vcs
Auto-start of the console is enabled from /etc/default/hurd-console
Inside the Hurd console, you can switch between virtual terminals via ALT+F1, ALT+F2 and so on. ALT+CTRL+BACKSPACE detachs the Hurd console and brings you back to the Mach console, from where you can reattach again with the above command.
X.Org has been ported and all video cards, which it supports that do not require a kernel module or drm should work.
You need to already be running the Hurd console and have repeaters setup as
indicated in the previous section. For instance, check that
hurd, and check that
You need to run dpkg-reconfigure x11-common to allow any user to start Xorg, because the X wrapper does not know about the Hurd and Mach consoles.
You also need to create a /etc/X11/xorg.conf to enable the control-alt-backspace shortcut:
Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection
You will need several X packages.
rxvt and a window manager:
are a good start.
X.Org should work out the box without any configuration file. You might however have to use the vesa driver in some cases.
The SysV rc system is not used yet. To shutdown your system, simply use