Path: ...!weretis.net!feeder9.news.weretis.net!panix!.POSTED.main.lekno.ws!not-for-mail
From: Louis Epstein <le@main.lekno.ws>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Thoughts on the coming end-of-support for 32-bit architectures?
Date: Tue, 21 May 2024 19:03:28 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <v2ir60$5qd$3@reader1.panix.com>
References: <v2e72l$3krfs$1@dont-email.me>
Injection-Date: Tue, 21 May 2024 19:03:28 -0000 (UTC)
Injection-Info: reader1.panix.com; posting-host="main.lekno.ws:12.144.5.2";
	logging-data="5965"; mail-complaints-to="abuse@panix.com"
User-Agent: tin/2.6.3-20231224 ("Banff") (FreeBSD/13.3-RELEASE-p1 (amd64))
Bytes: 1913
Lines: 26

TronNerd82 <tronnerd82@aol.com> wrote:
> How badly are you affected by FreeBSD's decision to deprecate support 
> for 32-bit CPU architectures? Do you use a 32-bit machine? Do you rely
> heavily on multilib? Do you think FreeBSD should step back on this decision,
> or go for it?
> 
> Let's discuss.

I have LAN-connected 32-bit machines not currently running,
with data to which I'd like to have access...I'm not sure to
what extent this is affected,but upgrading the FBSD versions
on them is already problematic.

(When I got my first 64-bit machine I first discovered that
the "Complete 32/64-bit operating system" touted on the CDROM
cases since 64-bit became available was actually only 32-bit
on the CDROMs and had to switch my subscription to DVD...and
of course it's been a long time since this 386BSD derivative
could run on a 386,not that I ever tried to).

The decoupling of ports from older OS versions is another
issue with trying to keep older computers running...would
there need to be a "retro fork" project?

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.