GNU/HURD is the name of the GNU operating system when TheHurd is used as the kernel.

The Hurd is a MultiServer MicroKernel ["POSIX"]-emulating operating system kernel, based on the Mach microkernel, although there has been talk about porting it to the ["L4"] microkernel too.

Currently, TheHurd is not in a production-ready state yet, but you can still install it, if you just work a bit and already got linux working. You have to use ["Grub"] to boot (["LILO"] doesn't support "Mach"), which is a good thing anyway.

You can follow also the instructions about Hurd on ["QEMU"]:

or use the Hurd [ LiveCD].

What the name "Hurd" means

According to Thomas Bushnell, BSG, the primary architect of the Hurd, "Hurd' stands for 'Hird of Unix-Replacing Daemons'. And, then, 'Hird' stands for 'Hurd of Interfaces Representing Depth'. We have here, to my knowledge, the first software to be named by a pair of mutually recursive acronyms." (from the ["GNU"] HURD webpage)


Buildd Requirements

Every once in a while, people ask why there is no second autobuilder running for hurd-i386, or they volunteer to set one up.

These are the requirements for a buildd:

To clarify on the mail requirements, build logs are sent by the autobuilder (<> for the current autobuilder) after the build to the Debian GNU/Hurd buildd admin (currently <>) and for publically archiving the logs. The buildd admin will reply to the build logs and those replies need to reach the autobuilder (again, currently <>). Additionally, mails from the Debian archive system need to reach the autobuilder.i


This is a list of archive building issues, i.e. things which affect more than package build and which are not toolchain problems (like PATH_MAX etc.)

External links

Developer Resources