[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] faq/64-bit.mdwn: added up to date 64-bit porting info open_i
From: |
Guy-Fleury Iteriteka |
Subject: |
Re: [PATCH] faq/64-bit.mdwn: added up to date 64-bit porting info open_issues/64-bit_port.mdwn: added up to date 64-bit porting info |
Date: |
Sat, 13 May 2023 19:44:31 +0200 |
On May 13, 2023 6:38:15 PM GMT+02:00, "jbranso@dismail.de" <jbranso@dismail.de>
wrote:
>---
> faq/64-bit.mdwn | 11 ++++-------
> open_issues/64-bit_port.mdwn | 6 +-----
> 2 files changed, 5 insertions(+), 12 deletions(-)
>
>diff --git a/faq/64-bit.mdwn b/faq/64-bit.mdwn
>index 2e1278cb..36afbbc3 100644
>--- a/faq/64-bit.mdwn
>+++ b/faq/64-bit.mdwn
>@@ -13,11 +13,8 @@ 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.
>+Hurd developers are adding 64-bit support, and they plan to drop the
>+32-bit support, once the 64-bit support is deemed stable.
I don't think anyone told the drop of 32 bit support
>+
>+
>
>-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..2cb77d90 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 64bit support, we need to**
>
> * Fix bugs :)
> * bootstrap a distrib
Hello,