summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2025-04-29 15:55:07 +0200
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2025-04-29 15:55:07 +0200
commitc73bb163d57aeddca937f32815517abf1c7998dd (patch)
tree97f47e46f2165548d2e721845096eeedf0fc888f
parentef1ea796d80b4bb2ad11d9dfb287be3a3bd8f026 (diff)
parent90c3b980466d6c77722ffdf17d5473b2ae9847ba (diff)
Merge branch 'master' of braunbox:~hurd-web/hurd-web
-rw-r--r--faq/64-bit.mdwn16
-rw-r--r--faq/drivers.mdwn13
-rw-r--r--hurd/what_is_the_gnu_hurd.mdwn17
3 files changed, 32 insertions, 14 deletions
diff --git a/faq/64-bit.mdwn b/faq/64-bit.mdwn
index a41d215d..ae25b500 100644
--- a/faq/64-bit.mdwn
+++ b/faq/64-bit.mdwn
@@ -19,17 +19,19 @@ userland addressing space.
A 64-bit GNU/Hurd is also coming soon,
progress is tracked on [[open_issues/64-bit_port]]!
-Hurd developers ported GNUMach to
+Hurd developers ported GNU Mach to
64-bit some time ago. Then they started making significant progress
-on the x86_64 userland port in Feb 2023. As of September 2024, the
+on the x86_64 userland port in Feb 2023. As of April 2025, the
Debian hurd-amd64 port works just like the hurd-i386, except for
missing packages and more
[[bugs|https://lists.gnu.org/archive/html/bug-hurd/2024-07/msg00058.html]],
-namely swapping issues with rumpdisk and deadlocking issues with
-libdiskfs/ext2fs. We are currently building
-64-bit packages. We plan on supporting both a 32-bit and 64-bit Debian
-GNU/Hurd, only not both at the same time. However, there is no plan to fix the
-year 2038 concern on a 32-bit system.
+namely swapping issues with rumpdisk, deadlocking issues with
+libdiskfs/ext2fs, and the hurd-console fails to start, which means that
+you cannot use X.
+
+We are currently building 64-bit packages. We plan on supporting both a
+32-bit and 64-bit Debian GNU/Hurd, only not both at the same time.
+However, there is no plan to fix the year 2038 concern on a 32-bit system.
That being said, you can always run a 32-bit version on a 64-bit machine, it
just works, processes are just limited to a couple GiB available memory.
diff --git a/faq/drivers.mdwn b/faq/drivers.mdwn
index 923e3b38..390c2e4d 100644
--- a/faq/drivers.mdwn
+++ b/faq/drivers.mdwn
@@ -19,14 +19,19 @@ and you can use an [[SSD|hurd/rump/rumpdisk]]. If you have difficulty
installing the Hurd, then try setting your harddrive mode to "legacy"
in the BIOS. A cheaper option is the T43 (2GB max RAM).
-Other working Thinkpads include the X200, T400, or T500 Thinkpads,
+Other working Thinkpads include the X200, T400,
+[[T410|https://logs.guix.gnu.org/hurd/2025-04-25.log#103752]] or T500 Thinkpads,
which support internet connectivity via the ethernet port. You can
use an [[SSD|hurd/rump/rumpdisk]] on these laptops, which support a
maximum of 8GB of RAM. The Debian installer images from 2023 fail to
boot these machines, but you can install the Hurd via [[Debian's
-CrossInstall|hurd/running/debian/CrossInstall]]. Until we fix the
-libdiskfs/ext2fs issues on the [[64 bit port|faq/64-bit]], we
-recommend that you use the 32 bit version of the Hurd.
+CrossInstall|hurd/running/debian/CrossInstall]] or
+[[mmdebstrap|https://lists.debian.org/debian-hurd/2024/12/msg00003.html]].
+
+_While the [[64 bit port|faq/64-bit]] is about as stable as the 32-bit
+port, please be advised that many packages are failing to build on the
+64 bit port. For this reason we recommend casual Hurd users to use
+the 32 bit port._
Other hardware that is known to work includes the [[Dell Inspiron
1750|https://logs.guix.gnu.org/hurd/2024-09-28.log]] on i386
diff --git a/hurd/what_is_the_gnu_hurd.mdwn b/hurd/what_is_the_gnu_hurd.mdwn
index 09c26ee7..0ccead52 100644
--- a/hurd/what_is_the_gnu_hurd.mdwn
+++ b/hurd/what_is_the_gnu_hurd.mdwn
@@ -12,6 +12,13 @@ License|/fdl]]."]]"""]]
[[!meta title="What Is the GNU Hurd?"]]
The Hurd is the GNU project's replacement for the [[UNIX]] system's [[kernel]].
+There are several
+[[free software operating systems|https://www.gnu.org/distros/free-distros.en.html]]
+using the [[Linux kernel|https://en.wikipedia.org/wiki/Linux_kernel]]. The
+Hurd is an alternate operating system that uses a different kernel. You can
+read more about the status of the Hurd [[here|hurd/status]]. If you decide
+to use the Hurd, then we would recommend
+[[the Debian GNU/Hurd distribution|https://www.debian.org/ports/hurd/]].
The Hurd is firstly a collection of protocols formalizing how different
components may interact. The protocols are designed to reduce the mutual
@@ -23,7 +30,8 @@ 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|translator]] that implement these
-protocols. They include file systems, network protocols and authentication.
+protocols. They include [[file systems|hurd/translator/ext2fs]], network
+protocols and [[authentication|hurd/translator/auth]].
The servers run on top of the [[microkernel/Mach]] [[microkernel]] and use
Mach's [[microkernel/mach/IPC]] mechanism to transfer information.
@@ -39,8 +47,8 @@ programs and libraries to operate. Let's look at an example.
Firefox invokes glibc's `send ()`, which in turn uses the pfinet (or
lwip) TCP/IP stack, which talk to our device drivers (rump or netdde),
-which finally talk to GNU Mach. Only GNU Mach runs in kernel space!
-Everything else is userspace!
+which can actually access the hardware without entering kernel space
+(GNU Mach). That's a lot of power for userspace!
The Hurd supplies the last major software component needed for a complete
[[GNU_operating_system|running/gnu]] as originally conceived by Richard
@@ -51,7 +59,10 @@ organization that is the home of the [GNU project](http://gnu.org/gnu/).
The Hurd development effort is a somewhat separate project from the
[[Debian_GNU/Hurd|hurd/running/debian]] port.
+Want to know what the Hurd can do? Read the [[status|hurd/status]] page.
Read about what the GNU Hurd is [[gramatically_speaking]].
Read about the [[origin_of_the_name]].
+
+Want to read more [[Hurd documentation|hurd/documentation]]?