Gnu Hurd Article Index for
Gnu 		Website Links For
Gnu Hurd 		 

Information About

Gnu Hurd
  CATEGORIES ABOUT GNU HURD
   
microkernels
   
gnu project software
   
livecd
   
SHOPPER'S DELIGHT
 
Shop For:  
Department
Price Minimum:
Price Maximum:
      



Hurd redirects here. For other uses of this term, see Hurd (disambiguation)


The GNU Hurd is a Computer program. It is a set of Servers (or Daemons , in Unix -speak) that work on top of either the GNU Mach microkernel or the L4 Microkernel ; together, they form the Kernel of the GNU Operating System . It has been under development since 1990 by the GNU Project and is distributed as Free Software under the GPL . The Hurd aims to surpass Unix kernels in functionality, security, and stability, while remaining largely compatible with them. This is done by having the Hurd track the POSIX specification, while avoiding arbitrary restrictions on the user.

"HURD" is an indirectly Recursive Acronym , standing for "HIRD of Unix -Replacing Daemons ", where "HIRD" stands for "HURD of Interfaces Representing Depth".


DEVELOPMENT HISTORY

By the early 1990s, the kernel was the only major component missing from the GNU OS.

Development on the Hurd began in programmers, Stallman decided instead to use the Mach Microkernel , which subsequently proved unexpectedly difficult, and the Hurd's development proceeded slowly.

Because of this slow pace, the GNU Userland components came to be used with the Linux Kernel and are now commonly associated with " Linux " systems (see also GNU/Linux Naming Controversy ).

Despite an optimistic announcement by Richard Stallman in 2002 {Link without Title} predicting a release of GNU/Hurd, further development and design are still required. No official release of the Hurd has yet been made, and the system is currently unstable.

OSKit-Mach began as a branch of the Gnu Mach 1.2 kernel, but since the release of GNU Mach 1.3, OSKit-Mach has been merged as the new Gnu Mach 2.x mainline. Development of the Hurd has also shifted significantly for some developers towards the L4 Microkernel Family .

In 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.

The Debian project, among others, have contributed funding to speed up development.

In 2006, Marcus Brinkmann and associates have met with Jonathan Shapiro (one of the primary achitects of the Coyotos Operating System) to aid in and discuss the use of the Coyotos kernel for GNU/Hurd as there is no focus on L4 anymore.


ARCHITECTURE

Unlike ( EROS successor) and L4.sec (not yet complete).

Other Unix-like systems running on top of the Mach Microkernel include Mac OS X , OSF/1 , NEXTSTEP , Lites , and MkLinux . These share one detail in common, in that they are implemented as a single so-called ''server''. In effect they replace the Monolithic Kernel from a traditional Unix system with two parts, the microkernel and Unix server.

The Hurd instead consists of multiple servers working together. Instead of a single large code base which includes everything from handling the clock to handling the Networking , in Hurd each of these are handled by a separate server. This makes developing the Hurd much easier (at least in theory) as making changes to one is less likely to have Side-effect s in others.

In the original Mach efforts, this sort of "set of servers" was considered to be one of the main goals of the design, but the Hurd appears to be the first Mach-based system to actually be implemented in this fashion (whereas QNX is similar but based on its own microkernel). It's not entirely clear why this happened, but it appears that groups working on Mach were too busy working on Mach to work on the operating system as a whole. Hurd also aims to be microkernel-independent.


Unix extensions

A number of traditional Unix concepts are replaced or extended in the Hurd:
Under Unix every program running 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 . What '' Mounting '' is to Unix, the Hurd achieves 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; so that listing the unified directory reveals the contents of all the unified directories (a feature that is missing in many Unixes, although available in FreeBSD , NetBSD and DragonFly BSD ).

Perhaps the most empowering aspect of the Hurd is the ability for any user to start their own system services. Any user can attach any translator to the filesystem for their own personal use. A user could even replace system servers, such as the auth server, with other servers of their own choosing. All this can be done without affecting other users, due to well defined scopes. Indeed, it is even possible for a user to run the Hurd within itself, which is known as a sub-Hurd.

The Hurd requires a Multiboot -compliant Boot Loader , such as GRUB .


Architecture of the servers


According with the Debian documentation they are as following: {Link without Title}

  • The authentication server "auth"

  • The crash server "crash"

  • The exec server "exec"

  • The ext2fs server "ext2fs"

  • The fifo translator "fifo"

  • The firmlink translator "firmlink"

  • The ftp filesystem translator "ftpfs"

  • The fwd server "fwd"

  • The hostmux server "hostmux"

  • The ifsock server "ifsock"

  • The init server "init"

  • The iso filesystem server "isofs"

  • The magic server "magic"

  • The new-fifo server "new-fifo"

  • The nfs server "nfs"

  • The null server "null"

  • The pfinet server "pfinet"

  • The pflocal server "pflocal"

  • The process server "proc"

  • The storage translator "storeio"

  • The symbolic link translator "symlink"

  • The terminal server "term"

  • The ufs server "ufs"

  • The usermux server "usermux"


Among all of them, they implement the POSIX interface


GNU/HURD-BASED DISTRIBUTIONS




SEE ALSO



EXTERNAL LINKS