diff options
Diffstat (limited to 'faq/64-bit.mdwn')
| -rw-r--r-- | faq/64-bit.mdwn | 19 |
1 files changed, 6 insertions, 13 deletions
diff --git a/faq/64-bit.mdwn b/faq/64-bit.mdwn index ae25b500..cfda4554 100644 --- a/faq/64-bit.mdwn +++ b/faq/64-bit.mdwn @@ -17,19 +17,12 @@ 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. -A 64-bit GNU/Hurd is also coming soon, -progress is tracked on [[open_issues/64-bit_port]]! -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 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, 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 +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 the hurd-console fails to +start, which means that you cannot use X. + +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. |