summaryrefslogtreecommitdiff
path: root/faq/64-bit.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'faq/64-bit.mdwn')
-rw-r--r--faq/64-bit.mdwn17
1 files changed, 12 insertions, 5 deletions
diff --git a/faq/64-bit.mdwn b/faq/64-bit.mdwn
index 1da375ba..d3d6d046 100644
--- a/faq/64-bit.mdwn
+++ b/faq/64-bit.mdwn
@@ -13,11 +13,18 @@ License|/fdl]]."]]"""]]
[[!meta title="Is there a 64-bit version?"]]
-There are currently no plan for 64-bit userland, but there are plans for 64-bit
-kernelland with 32-bit userland, which will notably permit to efficiently make
-use of more than 2 GiB memory and provide 4 GiB userland addressing space.
-[[Work on this|open_issues/64-bit_port]] is currently in the master-x86_64 and
-port-amd64 branches for GNU Mach.
+64-bit kernelland is supported with 32-bit userland, which notably
+permits to efficiently make use of more than 2 GiB memory and provide 4 GiB
+userland addressing space.
+
+A 64-bit GNU/Hurd is also available, progress is tracked on [[open_issues/64-bit_port]]!
+As of April 2025, the Debian hurd-amd64 port works just like the hurd-i386, except for
+some bugs, namely swapping issues with rumpdisk and dumping core files.
+
+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.
+