--- faq/64-bit.mdwn | 15 ++++++++------- open_issues/64-bit_port.mdwn | 6 +----- 2 files changed, 9 insertions(+), 12 deletions(-)
diff --git a/faq/64-bit.mdwn b/faq/64-bit.mdwn index 2e1278cb..9c8ecc9c 100644 --- a/faq/64-bit.mdwn +++ b/faq/64-bit.mdwn @@ -13,11 +13,12 @@ License|/fdl]]."]]"""]] [[!meta title="Is there a 64-bit version?"]] -There are currently no plan for 64-bit userland for the short term, 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. The kernel support was merged into GNU Mach, the currently -missing bit is the 32/64 mig translation for kernel RPCs. +A 64-bit GNU/Hurd is coming soon! Hurd developers ported GNUMach to +64-bit some time ago. Then they started making significant progress +on the x86_64 userland port in Feb 2023. As of May 2023, the 64-bit +port works well enough to start all the essential Hurd servers and run +/bin/sh. We are currently building 64-bit packages. We plan on +supporting both a 32-bit and 64-bit Debian GNU/Hurd. 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/open_issues/64-bit_port.mdwn b/open_issues/64-bit_port.mdwn index 95761828..ca30ba64 100644 --- a/open_issues/64-bit_port.mdwn +++ b/open_issues/64-bit_port.mdwn @@ -13,11 +13,7 @@ License|/fdl]]."]]"""]] [[!inline pages="title(Is there a 64-bit version?)" feeds="no" raw="yes"]] -**What is left for initial support (32-on-64) is** - - * Fixing bugs :) - -**For pure 64bit support, we need to** +**For 64-bit support, we need to** * Fix bugs :) * bootstrap a distrib -- 2.32.0
