The Hurd is the GNU project’s replacement for UNIX, a popular operating system kernel.
The Hurd is firstly a collection of protocols formalizing how different components may interact. The protocols are designed to reduce the mutual trust requirements of the actors thereby permitting a more extensible system. These include interface definitions to manipulate files and directories and to resolve path names. This allows any process to implement a file system. The only requirement is that it have access to its backing store and that the principal that started it own the file system node to which it connects.
The Hurd is also a set of servers that implement these protocols. They include file systems, network protocols and authentication. The servers run on top of the Mach microkernel and use Mach’s IPC mechanism to transfer information.
The Hurd provides a compatibility layer such that compiling higher level programs is essentially transparent; that is, by means of the glibc, it provides the same standard interfaces known from other UNIX-like systems. Thus, for a typical user, the Hurd is intended to silently work in the background providing the services and infrastructure which the microkernel itself has no business implementing, but that are required for higher level programs and libraries to operate.
I might be wrong somewhere, but think of Hurd server as an orchestrator, which runs atop the GNU/Mach microkernel, as opposed to monolithic kernels like BSD and Linux.
It’s an OS that’s still not in existence - I mean, well, technically, it is, the QEMU images, as well as Debian/Arch ISOs are available on the internet, but the Mach microkernel is slow, which is a blocker, so they’re looking into alternative ones.
What is GNU hurd
https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html
The Hurd is the GNU project’s replacement for UNIX, a popular operating system kernel.
The Hurd is firstly a collection of protocols formalizing how different components may interact. The protocols are designed to reduce the mutual trust requirements of the actors thereby permitting a more extensible system. These include interface definitions to manipulate files and directories and to resolve path names. This allows any process to implement a file system. The only requirement is that it have access to its backing store and that the principal that started it own the file system node to which it connects.
The Hurd is also a set of servers that implement these protocols. They include file systems, network protocols and authentication. The servers run on top of the Mach microkernel and use Mach’s IPC mechanism to transfer information.
The Hurd provides a compatibility layer such that compiling higher level programs is essentially transparent; that is, by means of the glibc, it provides the same standard interfaces known from other UNIX-like systems. Thus, for a typical user, the Hurd is intended to silently work in the background providing the services and infrastructure which the microkernel itself has no business implementing, but that are required for higher level programs and libraries to operate.
I might be wrong somewhere, but think of Hurd server as an orchestrator, which runs atop the GNU/Mach microkernel, as opposed to monolithic kernels like BSD and Linux.
It’s an OS that’s still not in existence - I mean, well, technically, it is, the QEMU images, as well as Debian/Arch ISOs are available on the internet, but the Mach microkernel is slow, which is a blocker, so they’re looking into alternative ones.