Linux 7.2 has landed, dragging x86 timing clean out of the nineties by making the Time Stamp Counter mandatory.
I wrote up a quick article on why ditching those ancient legacy fallbacks is good housekeeping, plus a few other bits like cache-aware scheduling and memory tweaks worth noting.
Is anyone still using legacy hardware? If so, what do you use it for?
I kinda miss the idea that the kernel would run on literally any hardware it ever did support, but I totally get it, especially now that there’s an emphasis on reducing attack surfaces.
I have some xeons in an old server running that I can’t update to the next version of Rocky because the kernel won’t support them :(
Isn’t that just Rocky configuring the kernel that way? You’re free to compile your own kernel and it’ll still support even old pentiums, just not i486 in new versions
Someone will keep up support and you’re always welcome to merge it and compile your kernel.
Lots of retro enthusiasts still use legacy hardware for all sorts of reasons… I fear that a fork of the kernel will be necessary in the near future to keep these machines running.
The notion of using Linux to revive old hardware and keep it out of the landfill may not last forever…
Or just don’t connect to the public internet and continue using a kernel that works? Even with internet, the attack vectors for such a machine are nearly non existent.
And why do they need to use the latest Linux kernel for that hardware, again?
Security updates if you use it online or copy new binaries to run on it. Even if you’re not worried about hackers, there can still be viruses and malware that destroy your data.
There are LTS versions outside of current.
But more importantly, who runs anything remotely critical on a 486 these days? These machines choke to death on TLS handshakes.
Who said anything about critical?
I just don’t want my hard disk wiped when I decide to try a piece of software.
I just don’t want my hard disk wiped when I decide to try a piece of software.
You aren’t running any relatively recent software on a 486, period. Even if you did and it turned out to be a virus, the chances of it hitting a bug in the kernel are extremely low.
This is just grasping at straws.
Industrial machine controllers frequently run on ancient hardware
Do they run the latest Linux kernel?
And they are very notoriously outdated in terms of software.
There are ultra long term support Linux kernels though.
Linux 6.12 will be supported until at least 2036 for instance.
I do agree. Maybe I’m little paranoid, but I feel like in some years, recycle old chips will be the only IT available
Just use NetBSD and never look back :)
The notion of using Linux to revive old hardware and keep it out of the landfill may not last forever…
Linux supports much less old hardware than its competitors.
On the other hand, Linux runs more software than its competitors, and it’s not even close.
You can (compile and) run almost all Linux software on the BSDs.
You can (compile and) run almost all Linux software on the BSDs.
Cool. Is there any *BSD-only software I would want to run on Linux? No? Then, what’s the point?
FreeBSD’s jails are pretty interesting though, so is NetBSD’s rump kernel. But my point was (especially older) hardware support, not software support. If all you care about is the sheer number of available applications, Windows is there for you. 😉
Your post that it was “not even close” is misleading at best and utterly wrong in total.
I’m sorry, I thought we were comparing BSD to Linux. And why would I use BSD if there isn’t a single piece of software I need that isn’t available on Linux as well, but others, like Kubernetes, aren’t natively supported on BSD.
Regardless, nobody cares about dropping 486 support. NetBSD is a novelty OS at best, and FreeBSD, the most popular BSD out there, doesn’t run on 486 since 2024. Nice attempt at trolling tho.
Emulation support doesn’t imply full ABI or driver support.
Otherwise, since Proton is supported for Linux but not BSD, Linux would still be ahead.
It’s much deeper than emulation like you would a PlayStation. Last time I checked you could run steam and proton on FreeBSD
I know how it works. My point is that, if emulated software, be under a hypervisor or an ABI compatibility layer, is considered “supported”, then we could say that Windows applications are supported in Linux, but that’s not entirely true.
More importantly, if I want to run Linux software, I would rather run it on Linux, e.g. Docker and Kubernetes.
Linuxers gonna linux.
I actually learned how to actually use a shell interface when I setup FreeBSD the first time. But other than tinkering with BSD’s on occasion, I really don’t have much experience with them.
To dismiss them outright is baffling to me.
Old news, this was clear in June: https://www.phoronix.com/news/Linux-Kernel-TSC-Unconditional
I use a Compaq CQ510-SD for writing. Lovely small keyboard, only has a resolution of 1024x600, but with some zoom configured in autostart that increases to twice that. It works as little more than a glorified text processor, but it suits my needs just fine while I can’t find its equal in the x64 or ARM market.
But why does it need updates if it works? Just don’t connect it to the Internet and you can run it until either it dies or you die.
I tend to write on it on the couch or at the library or wherever, and then use syncthing to sync with my desktop. This does require keeping syncthing updated.
Use an ultra long support kernel like 6.12
The keyboard does look lovely. Maybe a Chromebook with Linux? I don’t know what the Linux world is like for those. I’m sure you’ve looked at them before.
I did, yes. Finding a 12" or 13" mini-laptop is just tricky. Might need to build one of those custom clamshells.
I would recommend looking into the BSD’s, they have stronger support for older and unusual architectures. Something like nomadBSD, uses xfce on freeBSD
The problem is not software but hardware. The Compaq CQ510-SD is a nice compact design with round edges and small enough to fit in most any bag. Finding the same in a x64 system seems impossible. Hard edges, larger screens, flimsy chassis, or unuseable keyboards.
Well if you still like your hardware, and want continued, updated, software support, one of the BSD’s still likely to get you there for a bit longer. NetBSD likely being the one that drops it last.
But at some point, as long as you able to do your work and copy data back and forth, does it matter. Even just running winXP or 7 will get you along for sometime.
FreeDOS will always support x86, lol.
At least you not running something with an old big edian PowerPC machine. Support for those suck!
Does the machine a a socketed CPU, it appeared it runs the Core2 CPUs, if you get a core2duo, those support 64bit. I have a ThinkPad x60 with a 32bit Core2 CPU. It’s odd that there was 32bit only version of that class of CPU. I haven’t bothered to try upgrade it though.
To my knowledge the CPU is soldered to the mainboard, but I haven’t looked inside it for a while now. Mine is running an Intel Atom N455; single core, two threads.
I’ll probably swap to a BSD for it when support ends.
“Finally! Linux supports even less hardware that will be supported by BSD for years to come! Hooray!”
Because yay, planned obsolescence.
Pretty sure that FreeBSD doesn’t support 32-bit systems anymore. OpenBSD certainly hasn’t been able to run on 486 for ages.
You are welcome to take over maintenance on it.
I mean support needs to drop off somewhere, were not writing code for the eniac anymore
The LTS Kernel will also support it for years to come
2036, to be percise. And that is the officially supported time for the ULTS kernel. You can use older kernels for such old hardware
So use bsd
I do and I will continue to do.
For hardware over 20 years old? I don’t think the manufacturers planned on it lasting this long lmao
37 years old, to be precise.
There’s probably a fortunate 500 company running some load bearing server from 20 years ago, that ends up back in production, everytime they fail to migrate the critical service away from it.
There must have been demand to keep x86 32bit alive this long.
That would be running Windows NT4 or Netware 3.1, then.
I guarantee they aren’t updating that server.
It probably runs payroll and no one is willing to miss a paycheck due to a botched updated
If it’s from 20 years ago then isn’t that like 15 years too new to be affected by this patch?
