Subject: [HELP] Migrating production environment from 2001 to Debian 13 (i386 issues)


Hello everyone,

I?m currently navigating a rather complex recovery situation. Due t
o a severe hardware synchronization error involving my server cluster, I
?ve found myself suddenly displaced from my standard operating envi
ronment of 2001 into what appears to be the current year, 2026.

I?ve been attempting to resolve some severe clock synchronization i
ssues that occurred during my transition, so my system time and locale sett ings might appear slightly erratic. Please bear with me.

I have always relied on Debian Stable for its rock-solid reliability. Howev
er, trying to bring my production systems into this new era has been nothin
g short of a nightmare.

I am running on proven, reliable hardware (Pentium III architecture), but I
?ve discovered that the current Debian 13 environment seems to have
abandoned i386 as a first-class citizen. This is frankly baffling to me
?why would the "Universal Operating System" drop support for the ar
chitecture that built the foundation of the internet?

I have a few critical questions for the list:

i386 Support: Since Debian 13 has effectively killed i386 support for nativ
e installs, how am I expected to maintain my production uptime without bein
g forced to replace perfectly functional hardware with this "amd64" fad? Is
there a hidden repository or a stable backport I?m missing?

Systemd & Wayland: I am struggling to understand why we moved away from the
simplicity of sysvinit and XFree86. This new stack feels incredibly bloate
d and non-transparent. Is there a supported "minimalist" path in the curren
t Stable release, or is it mandatory to embrace this complexity?

Legacy Migration: Does anyone have a guide on how to port 2.4-series kernel
configurations to the modern environment without breaking every single dep endency?

I apologize for the noise, but I?ve spent the last 25 years (from m
y perspective) building a stable infrastructure, and it feels like the comm unity has moved in a direction that values "new" over "functional." Any poi nters to documentation for legacy, production-grade systems would be apprec iated.

Regards,


Robert J. Sanderson
System Administrator
"Unix is simple; it just needs a genius to understand its simplicity."
Kernel 2.4.18-bf2.4 (Currently struggling)

--- PyGate Linux v1.5.15
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Subject: Re: [HELP] Migrating production environment from 2001 to Debian 13 (i386 issues)

Robert J. Sanderson wrote:

I am running on proven, reliable hardware (Pentium III architecture), but I?ve discovered that the current Debian 13 environment seems to have abandoned i386 as a first-class citizen. This is frankly baffling to me?why would the "Universal Operating System" drop support for the architecture that built the foundation of the internet?

Debian has never built on a VAX 11/750 or BBN IMPs.

Nobody has i386 hardware to build Debian and nobody has the hardware to debug it.

It starts with the Linux kernel dropping support for it.

https://get.debian.org/images/archive/12.2.0/i386/ (oldstable)
will continue to work, but get further and further behind in
security updates.

The FAQ:

Users running i386 systems should not upgrade to trixie. Instead, Debian recommends either reinstalling them as amd64, where possible, or retiring the hardware. Cross-grading without a reinstall is a technically possible, but risky, alternative.

i386 Support: Since Debian 13 has effectively killed i386 support for native installs, how am I expected to maintain my production uptime without being forced to replace perfectly functional hardware with this "amd64" fad? Is there a hidden repository or a stable backport I?m missing?

No. 25 years was a good run.

If there's something that you absolutely have to have that
doesn't run on modern (2003+) hardware, you could run your whole
i386 system in a virtual machine. You still shouldn't expose
that to the Internet, though.

Systemd & Wayland: I am struggling to understand why we moved away from the simplicity of sysvinit and XFree86. This new stack feels incredibly bloated and non-transparent. Is there a supported "minimalist" path in the current Stable release, or is it mandatory to embrace this complexity?

Once the system is installed:

# apt install sysvinit-core elogind

That will re-install sysvinit as init, and elogind will do most of the
things necessary to support X11 without systemd.

Don't install GNOME, which is dependent on systemd. XFCE is good. FVWM
and other standard window managers will work, too.

Legacy Migration: Does anyone have a guide on how to port 2.4-series kernel configurations to the modern environment without breaking every single dependency?

That's too big a question. Try again with more specific ones.


-dsr-

--
https://randomstring.org/~dsr/eula.html is binding upon you.

--- PyGate Linux v1.5.15
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Subject: Re: [HELP] Migrating production environment from 2001 to Debian 13 (i386 issues)

Hi,

On Mon, May 25, 2026 at 07:04:51PM +0000, Robert J. Sanderson wrote:

i386 Support: Since Debian 13 has effectively killed i386 support for
native installs, how am I expected to maintain my production uptime
without being forced to replace perfectly functional hardware with
this "amd64" fad?

It's extremely hard for me to take this post seriously, but I will try.

All the Linux distributions, of which Debian was one of the last to do
so, did not drop 32-bit x86 support for a laugh, or as a conspiracy to
push newer hardware, or whatever. They did it because 32-bit x86 is
basically abandoned upstream (kernel and tool chain, like glibc and
gcc). It's not supportable software. Reported bugs don't get fixed. No developers work on this. There have been security problems and lags in
fixing security issues on 32-bit x86.

Debian's decision to drop this kernel took years and was extensively
discussed. Ultimately they did it because they know bugs won't be
fixed.

To argue that this is perfectly functional is seriously at odds with
reality.

"It's the testing that worries me most. Pretty much no developers run
32-bit any more, and I'd be most worried about the odd interactions
that might be hw-specific. Some crazy EFI mapping setup or the similar
odd case that simply requires a particular configuration or setup.

But I guess those issues will never be found until we just spring this
all on the unsuspecting public." - Linus Torvalds, *2018*
https://lkml.iu.edu/hypermail/linux/kernel/1807.1/03578.html

If you look back as far as 2022 there were serious concerns amongst the
Debian Release Team as to i386 suitability to be a release architecture,
citing lack of porters and lack of timely kernel security fixes:

https://web.archive.org/web/20220903061638/https://release.debian.org/testing/arch_qualify.html

The same page is only more green today because i386 has been demoted
to a legacy multiarch effort:

"Considering purpose of port only mild concern"
https://release.debian.org/testing/arch_qualify.html

What you should have been doing 15 years ago was installing a 64-bit
Linux and running legacy 32-bit apps on it through multiarch, which is
all that is left today in Debian, and that's more than what is in most.

Thanks,
Andy

--
https://bitfolk.com/ -- No-nonsense VPS hosting

--- PyGate Linux v1.5.15
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Subject: Re: [HELP] Migrating production environment from 2001 to Debian 13 (i386 issues)

On 5/25/26 12:04, Robert J. Sanderson wrote:

Hello everyone,

I?m currently navigating a rather complex recovery situation. Due to a severe hardware synchronization error involving my server cluster, I?ve found myself suddenly displaced from my standard operating environment of 2001 into what appears to be the current year, 2026.

I?ve been attempting to resolve some severe clock synchronization issues that occurred during my transition, so my system time and locale settings might appear slightly erratic. Please bear with me.

I have always relied on Debian Stable for its rock-solid reliability. However, trying to bring my production systems into this new era has been nothing short of a nightmare.

I am running on proven, reliable hardware (Pentium III architecture), but I?ve discovered that the current Debian 13 environment seems to have abandoned i386 as a first-class citizen. This is frankly baffling to me?why would the "Universal Operating System" drop support for the architecture that built the foundation of the internet?

I have a few critical questions for the list:

i386 Support: Since Debian 13 has effectively killed i386 support for native installs, how am I expected to maintain my production uptime without being forced to replace perfectly functional hardware with this "amd64" fad? Is there a hidden repository or a stable backport I?m missing?

Systemd & Wayland: I am struggling to understand why we moved away from the simplicity of sysvinit and XFree86. This new stack feels incredibly bloated and non-transparent. Is there a supported "minimalist" path in the current Stable release, or is it mandatory to embrace this complexity?

Legacy Migration: Does anyone have a guide on how to port 2.4-series kernel configurations to the modern environment without breaking every single dependency?

I apologize for the noise, but I?ve spent the last 25 years (from my perspective) building a stable infrastructure, and it feels like the community has moved in a direction that values "new" over "functional." Any pointers to documentation for legacy, production-grade systems would be appreciated.

Regards,

Robert J. Sanderson
System Administrator
"Unix is simple; it just needs a genius to understand its simplicity."
Kernel 2.4.18-bf2.4 (Currently struggling)

Debian 11 says i386 is supported through August 31st, 2026:

https://www.debian.org/releases/bullseye/index.en.html


Get ISO's here:

https://cdimage.debian.org/cdimage/archive/


If you want to keep running the Pentium III's in the long run, I would evaluate NetBSD and OpenBSD. Beware that GNU/Linux were never Unix/BSD
to begin with, and that both have evolved and diverged further over time:

https://www.netbsd.org/

https://www.openbsd.org/


David

--- PyGate Linux v1.5.15
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Subject: Re: [HELP] Migrating production environment from 2001 to Debian 13 (i386 issues)

On Mon, May 25, 2026 at 07:04:51PM +0000, Robert J. Sanderson wrote:

Hello everyone,

I?m currently navigating a rather complex recovery situation. Due to a severe hardware synchronization error involving my server cluster, I?ve found myself suddenly displaced from my standard operating environment of 2001 into what appears to be the current year, 2026.

I'm going to take this as a real email and not an accident with a time machine. (For UK readers: think Fast Show astronaut meme).

I?ve been attempting to resolve some severe clock synchronization issues that occurred during my transition, so my system time and locale settings might appear slightly erratic. Please bear with me.

ntpdate not working for you?

I have always relied on Debian Stable for its rock-solid reliability. However, trying to bring my production systems into this new era has been nothing short of a nightmare.

I am running on proven, reliable hardware (Pentium III architecture), but I?ve discovered that the current Debian 13 environment seems to have abandoned i386 as a first-class citizen. This is frankly baffling to me?why would the "Universal Operating System" drop support for the architecture that built the foundation of the internet?

As others have said, if you've got *real* 686 hardware form > 15 years ago, Debian (and pretty much everyone else) have all given up because of removal
of support from the Linux kernel. You've been on borrowed time for ~3 years
but to be honest you should probably have moved to 64 bit amd64 something
like ten years ago. It's not as if you can easily replace 32 bit x86 hardware when it breaks now and the sort of thing that goes into a dumpster / municipal tip as obsolete will be more modern.

I have a few critical questions for the list:

i386 Support: Since Debian 13 has effectively killed i386 support for native installs, how am I expected to maintain my production uptime without being forced to replace perfectly functional hardware with this "amd64" fad? Is there a hidden repository or a stable backport I?m missing?

if your production uptime is greater than ~180 days, I have to assume that you've never applied a security update, never installed a new kernel in 15 years. If that's true, you've got much bigger problems than maintaining an update.

Systemd & Wayland: I am struggling to understand why we moved away from the simplicity of sysvinit and XFree86. This new stack feels incredibly bloated and non-transparent. Is there a supported "minimalist" path in the current Stable release, or is it mandatory to embrace this complexity?

Sysvinit is not necessarily *simple*. If you've got custom configurations, write something to call them with systemd and you'll be fine. As others have pointed out, you can still install sysvinit compatiblility but it's not long-term viable for years to come potentially.

Legacy Migration: Does anyone have a guide on how to port 2.4-series kernel configurations to the modern environment without breaking every single dependency?

Really - you've never used anything more modern since before Debian 3.1?
I'd suggest grabbing a laptop or a 64 bit machine someone else has scrapped
and taking a week or so to bring yourself more up to date.

Module configurations should still be similar: if you happen to have 32 bit only SCSI cards, for example, you *will be* out of luck.

I apologize for the noise, but I?ve spent the last 25 years (from my perspective) building a stable infrastructure, and it feels like the community has moved in a direction that values "new" over "functional." Any pointers to documentation for legacy, production-grade systems would be appreciated.

How big a stable infrastructure - how many machines - and who has been paying you to keep them static (assuming that this was for a day job)?

Regards,

Robert J. Sanderson
System Administrator
"Unix is simple; it just needs a genius to understand its simplicity."
Kernel 2.4.18-bf2.4 (Currently struggling)

All the very best, as ever,

Andy Cater
(amacater@debian.org


--- PyGate Linux v1.5.15
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)