|This article relies too much on references to primary sources. (December 2011)|
|Written in||Assembly, C|
|Source model||Open Source|
|Latest release||0.5 / 27 September 2013|
|Kernel type||multiserver microkernel|
|License||GNU General Public License|
GNU Hurd (usually referred to as the Hurd) is the multiserver microkernel written as part of GNU. It has been under development since 1990 by the GNU Project of the Free Software Foundation, designed as a replacement for the Unix kernel, and released as free software under the GNU General Public License.
GNU Hurd consists of a set of protocols and server processes (or daemons, in Unix terminology) that run on the GNU Mach microkernel. The Hurd aims to surpass the Unix kernel in functionality, security, and stability, while remaining largely compatible with it. The GNU Project chose the multiserver microkernel for the operating system, due to perceived advantages over the traditional Unix monolithic kernel architecture.
Name and logo
|“||It's time [to] explain the meaning of "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.||”|
As both hurd and hird are homophones of the English word herd, the full name GNU Hurd is also a play on the words herd of gnus, reflecting how the kernel works. The logo is called the Hurd boxes and it also reflects on architecture. The logo is a graph where nodes represent the Hurd kernel's servers and directed edges are IPC messages.
Richard Stallman founded the GNU project in September 1983 with an aim to create a free GNU operating system. Initially the components required for kernel and development were written: editors, shell, compiler and all the others. By 1989, GPL came into being and the only major component missing was the kernel.
Development on the Hurd began in 1990 after an abandoned kernel attempt in 1986, based on the research TRIX operating system developed by Professor Steve Ward and his group at MIT's Laboratory for Computer Science (LCS). According to Thomas Bushnell, the initial Hurd architect, their early plan was to adapt the 4.4BSD-Lite kernel and, in hindsight, "It is now perfectly obvious to me that this would have succeeded splendidly and the world would be a very different place today". In 1987 Richard Stallman proposed using the Mach microkernel developed at Carnegie Mellon University. Work on this was delayed for three years due to uncertainty over whether CMU would release the Mach code under a suitable license.
With the release of the Linux kernel in 1991, the primary user of GNU's userland components soon became operating systems based on the Linux kernel (Linux distributions), prompting the coining of the controversial term GNU/Linux.
Development of the Hurd has proceeded slowly. Despite an optimistic announcement by Stallman in 2002 predicting a release of GNU/Hurd later that year, the Hurd is still not considered suitable for production environments. Development in general has not met expectations, and there are still bugs and missing features. This has resulted in a poorer product than many (including Stallman) had expected. In 2010, after twenty years under development, Stallman said that he was "not very optimistic about the GNU Hurd. It makes some progress, but to be really superior it would require solving a lot of deep problems", but added that "finishing it is not crucial" for the GNU system because a free kernel already existed (Linux), and completing Hurd would not address the main remaining problem for a free operating system: device support.
Unlike most Unix-like kernels, the Hurd uses a server–client architecture, built on a microkernel that is responsible for providing the most basic kernel services – coordinating access to the hardware: the CPU (through process management and scheduling), RAM (via memory management), and other various input/output devices (via I/O scheduling) for sound, graphics, mass storage, etc. In theory the microkernel design would allow for all device drivers to be built as servers working in user space, but today most drivers of this kind are still contained in the GNU Mach kernel space.
According to Hurd developers the main advantage of microkernel-based design is the ability to extend the system: developing a new module would not require in depth knowledge of the rest of the kernel and a bug in one module would not crash the entire system. Hurd provides a concept of translators, a framework of modules used to extend a file system functionality.
From early on, the Hurd was developed to use GNU Mach as the microkernel. This was a technical decision made by Richard Stallman, who thought it would speed up the work by saving a large part of it. He has admitted that he was wrong about that. Other Unix-like systems working on the Mach microkernel include OSF/1, Lites, and MkLinux. Mac OS X and NeXTSTEP use hybrid kernels based on Mach.
From 2004 onward, various efforts were launched to port the Hurd to more modern microkernels. The L4 microkernel was the original choice in 2004, but progress slowed to a halt. Nevertheless, during 2005, Hurd developer Neal Walfield finished the initial memory management framework for the L4/Hurd port, and Marcus Brinkmann ported essential parts of glibc; namely, getting the process startup code working, allowing programs to run, thus allowing the first user programs (trivial ones such as the hello world program in C) to run.
Since 2005 Brinkmann and Walfield started researching Coyotos as a new kernel for HURD. In 2006, Brinkmann met with Jonathan Shapiro (a primary architect of the Coyotos Operating System) to aid in and discuss the use of the Coyotos kernel for GNU/Hurd. In further discussion HURD developers realised that Coyotos (as well as other similar kernels) are not suitable for HURD.
In 2007, Hurd developers Neal Walfield and Marcus Brinkmann gave a critique of the Hurd architecture, known as "the critique", and a proposal for how a future system may be designed, known as "the position paper". In 2008, Neal Walfield began working on the Viengoos microkernel as a modern native kernel for HURD. As of 2009[update], development on Viengoos is paused due to Walfield lacking time to work on it.
In the meantime, others have continued working on the Mach variant of Hurd.
|This section does not cite any references or sources. (March 2007)|
A number of traditional Unix concepts are replaced or extended in the Hurd.
Under Unix, every running program has an associated user id, which normally corresponds to the user that started the process. This id largely dictates the actions permitted to the program. No outside process can change the user id of a running program. A Hurd process, on the other hand, runs under a set of user ids, which can contain multiple ids, one, or none. A sufficiently privileged process can add and remove ids to another process. For example there is a password server that will hand out ids in return for a correct login password.
Regarding the file system, a suitable program can be designated as a translator for a single file or a whole directory hierarchy. Every access to the translated file, or files below a hierarchy in the second case, is in fact handled by the program. For example a file translator may simply redirect read and write operations to another file, not unlike a Unix symbolic link. The effect of Unix mounting is achieved by setting up a filesystem translator (using the "settrans" command). Translators can also be used to provide services to the user. For example, the ftpfs translator allows a user to encapsulate remote FTP sites within a directory. Then, standard tools such as ls, cp, and rm can be used to manipulate files on the remote system. Even more powerful translators are ones such as UnionFS, which allows a user to unify multiple directories into one; thus listing the unified directory reveals the contents of all the directories.
Architecture of the servers
According to the Debian documentation there are 24 servers (18 core servers and 6 file system servers) named as follows:
- auth (authentication server): Receives requests and passwords from programs and gives them an ID, which changes the privileges of the program.
- crash (crash server): Handles all fatal errors.
- exec (execution server): Translates an executable image (currently ELF and a.out are supported) to a runnable image in memory.
- fifo ([FIFO (computing and electronics)|FIFO]] translator): Implements named pipes.
- new-fifo (new FIFO server): An alternate server for named pipes.
- firmlink (the firmlink translator): Implements firmlinks ‒ "half-way between a symbolic link and a hard link".
- fwd (forward server): Forwards requests to other servers, used by fifo and symlink servers.
- hostmux (host multiplexer server)
- ifsock (server for sockets interface): Helps with UNIX domain socket addresses.
- init (init server): Basic system booting and configuration.
- magic (magic server)
- null (null server): Implements /dev/null and /dev/zero.
- pfinet (pfinet server): Implements the PF_INET protocol family.
- pflocal (pflocal server): Implements UNIX domain sockets.
- proc (process server): Assigns PIDs and manages process-level actions.
- symlink (symbolic link translator): Implements symbolic links for filesystems that don't support them.
- term (terminal server): A POSIX terminal.
- usermux (user multiplexer server): Invokes user-specific translators.
- The ext2 filesystem translator. It receives disk blocks from the microkernel and gives files and directories to the applications.
- The translator for the ISO 9660 filesystem. Translates blocks of a CD or DVD to files and directories for the applications.
- See Network File System.
- Translator for the BSD filesystem of the same name, UFS.
- File transfer protocol filesystem translator.
- The storage translator.
The servers collectively implement the POSIX API, with each server implementing a part of the interface. For instance, the various filesystem servers each implement the filesystem calls. The storage server will work as a wrapping layer, similar to the block layer of Linux. The equivalent of VFS of Linux is achieved by libdiskfs and libpager libraries.
GNU distributions running Hurd
Hurd-based GNU distributions include:
- Arch Hurd (based on Hurd kernel)
- Debian GNU/Hurd
- Bee (discontinued)
- Gentoo (discontinued)
- GNU/Hurd Live CD (discontinued)
- "Happy 30th birthday, GNU! GNU Hurd 0.5, GNU Mach 1.4, GNU MIG 1.4 released.". 27 September 2013.
- "What Is the GNU Hurd?". GNU. Retrieved 2010-03-04.
- "advantages". GNU. Retrieved 2011-12-07.
- Vervloesem, Koen (July 7, 2010). "The Hurd: GNU's quest for the perfect kernel". LWN.net. Retrieved October 5, 2012.
- "GNU Hurd: Origin of the Name". GNU. Retrieved 2010-03-04.
- Hillesley, Richard (June 30, 2010). "GNU HURD: Altered visions and lost promise". Retrieved October 1, 2012.
- "Linux and the GNU Project". GNU. 2010-01-26. Retrieved 2010-03-04.
- "The GNU Hurd History, 'How it Started'". GNU. Retrieved 2006-08-27.
- Salus, Peter. "The Daemon, the GNU and the Penguin". Retrieved 2006-08-08.
- Ribeiro, John (2002-03-11). "Free Software Sees GNU Loose of Linux". PC World. Retrieved 2012-10-05.
- "Status". GNU. Retrieved 2010-03-04.
- Stallman, Richard (2006-03-09). "The Free Software Movement and the Future of Freedom" (ogg). Free Software Foundation. Zagreb. Lay summary.
This is the way, also, that people thought was the cleanest possible way to design kernels back in 1990. Well, it took many many many years to get this kernel to run at all, and it still doesn't run well, and it looks like there may be fundamental problems with this design, which nobody knew about back in 1990.
- Stallman, Richard (2010-07-29). "RMS AMA". Reddit. Retrieved 2011-12-07.
- Kousoulos, Constantine (2007-03-21). "Re: Device drivers in Mach?". bug-hurd (Mailing list).
- Doeppner, Thomas W. (20 December 2010). Operating Systems In Depth: Design and Programming. John Wiley & Sons. p. 160. ISBN 978-0-471-68723-8. Retrieved 29 November 2012.
- Stallman, Richard (2000-10-12). "In Defense of Red Hat". Linux Today. Retrieved 2011-12-07.
I take full responsibility for the technical decision to develop the GNU kernel based on Mach, a decision which seems to have been responsible for the slowness of the development. I thought using Mach would speed the work by saving us a large part of the job, but I was wrong.
- Shapiro, Jonathan S. (2005-10-27). "Re: A comment about changing kernels". l4-hurd (Mailing list).
- Bachmann, Tom (2006-07-07). "Re: seL4, L4.sec and coyotos mess". l4-hurd (Mailing list).
- Walfield, Neal H.; Brinkmann, Marcus (July 2007). "A Critique of the GNU Hurd Multi-server Operating System" (PDF). GNU. Retrieved 2011-12-07.
- Walfield, Neal H.; Brinkmann, Marcus (2007-01-04). "Improving Usability via Access Decomposition and Policy Refinement" (PDF). GNU. Retrieved 2011-12-07.
- "viengoos". GNU. Retrieved 2010-03-04.
- "What happened to the L4/Coyotos/viengoos micro-kernels?". GNU. Retrieved 2011-01-07.
- "Preliminary GNU/Hurd User Interface Description". Debian. 1996-10-10. Retrieved 2010-03-04.
- "GNU/Hurd - Documentation". Debian. 1996-10-10. Retrieved 2012-07-12.
- "Nix-based GNU/Hurd System". Gnu.org. 2012-03-21. Retrieved 2012-07-12.
- "GNU Hurd/ hurd/ running/ live cd". Retrieved November 19, 2012.
|Wikimedia Commons has media related to Hurd.|
|Wikinews has related news: GNU Hurd operating system: first user program run using L4 microkernel|