Upgrade the note about 32-bit Cygwin to a full question and answer(s).
Also close a couple of HTML tags that need it.
---
install.html | 22 +++++++++++++++-------
1 file changed, 15 insertions(+), 7 deletions(-)
diff --git a/install.html b/install.html
index cdb9948b..c948e647 100755
--- a/install.html
+++ b/install.html
@@ -201,7 +201,7 @@ version for an old, unsupported Windows?</h2>
</p>
<p>
Also use <code>--no-verify</code> with this URL.
- </p
+ </p>
</td>
</tr>
<tr>
@@ -242,7 +242,7 @@ version for an old, unsupported Windows?</h2>
64-bit:
http://ctm.crouchingtigerhiddenfruitbat.org/pub/cygwin/circa/64bit/2016/08/30/104235
<p>
Also use <code>--no-verify</code> with these URLs.
- </p
+ </p>
</td>
</tr>
<tr>
@@ -273,15 +273,23 @@ version for an old, unsupported Windows?</h2>
Time Machine</a> for providing this archive.
</p>
- <h4>A note about 32-bit Cygwin</h4>
+<h2 class="cartouche" id="unsup32bit">Q: Can I still run unsupported 32-bit
Cygwin?</h2>
+
+ <p>
+ A1: You can, but why would you? 32-bit Cygwin was frozen at version
+ 3.3.6, around August 2022. There have been and there will be no bug
+ fixes or security updates, and no new functionality added. No longer
+ supported on the mailing lists; it has joined the choir invisible.
+ </p>
<p>
- The limited address space of 32-bit Windows means that
+ A2: If you're on 32-bit Windows as well,
+ the limited address space there means that
<a href="/faq.html#faq.using.fixing-fork-failures">random
failures in the fork(2) system call</a> are more likely. Therefore, we
- recommend using 32-bit Cygwin only in limited scenarios, with only a
minimum
- of necessary packages installed, and only if there's no way to run 64-bit
- Cygwin instead.
+ recommend using 32-bit Cygwin only in limited scenarios, with only a
+ minimum of necessary packages installed, and only if there's no way
+ to run 64-bit Cygwin instead.
</p>
<p>
--
2.43.0
