1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
[[!meta copyright="Copyright © 2013, 2016, 2017, 2018 Free Software Foundation,
Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
[[!tag faq/support]]
[[!meta title="Is there a 64-bit version?"]]
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 GNUMach 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
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.
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.
|
