Knowing Debian, it's pretty easy to just pull down the source and recompile. It's mildly annoying though.
Announcement
Collapse
No announcement yet.
Debian's i386 Builds Now Require 686-Class CPUs
Collapse
X
-
Originally posted by starshipeleven View PostKnowing Debian, it's pretty easy to just pull down the source and recompile. It's mildly annoying though.
Comment
-
This is relevant to my system. I do have some ancient VIA thin clients. I plan to replace them with Odroid-C2 ARMed boards for more RAM, faster CPU/video and gigabit/s networking for half the price I paid so long ago. I'm using an AMD64 terminal server and am considering Lemaker Cello or Huskyboard as a replacement. I left M$ over 15 years ago and 2016 could be the year I go ARMed. So many people are satisfied with the performance they get from ARMed smartphones that I figure a decent ARMed Debian GNU/Linux terminal server with gigabit/s networking should blow them away. The server boards are still light on SATA storage but they have enough CPU power and RAM and cache to do a good job. I think it's past the time we should scrap 32-bit x86 stuff. I still have a printer which has only 32-bit drivers but even it may be close to retirement. I could keep one of the VIA machines as a print server a couple of years longer.
Comment
-
They is a weird action. x64 has been deployed over a decade, most people has been using it in "modern" hardware. Those left behind is obviously using "old" hardware and they cannot change them for whatever reasons. Breaking i386 support means cutting the hardware being supported from 1987-2003 to 1998-2003.
If this is due to performance issue, they should upgrade the platform to x64. If this is due to compatibility issue, they should keep all support to the platform.
Comment
-
Originally posted by DeepDayze View PostYup, if you can build a 32-bit kernel for the i486 (which covers many of the older CPU's) you can then clap it into a 32-bit LiveUSB of any distro.
Only decent way to install is prepare a rootfs in a chroot from a newer system, you first cross-build the kernel and build-essential packages, then "install" them into the chroot, and from there on it's easy as you can apt-source.
I mean it's not impossible, it's just very annoying.
- Likes 1
Comment
-
Originally posted by dbpalan View PostThey is a weird action. x64 has been deployed over a decade, most people has been using it in "modern" hardware. Those left behind is obviously using "old" hardware and they cannot change them for whatever reasons. Breaking i386 support means cutting the hardware being supported from 1987-2003 to 1998-2003.
If this is due to performance issue, they should upgrade the platform to x64. If this is due to compatibility issue, they should keep all support to the platform.
Comment
-
Originally posted by GreatEmerald View PostMy 32-bit tablet is from 2011. Just saying.
Besides, I'm suspecting that it sucked back then and it keeps sucking big way even now.
Comment
-
Originally posted by discordian View PostHmm, actually I thought CMPXCHG8B but thats i586 already. Might be that solme conditional moves are used for lockfree operations.
I established a baseline for some software a few years ago, which widely uses atomic operations instead of locks. With i586 (some of) these depend on a library (libatomic), with i686 they all are simple cpu instructions. Sorry, would have to dig into it myself for an answer.
And of course, since then the Linux kernel has also dropped i386 support.
That being said, dropping i586 support which is what they're doing now doesn't give particularly big benefits. CMOV, mainly, which isn't such a big deal, really. But evidently they thought that the remaining i586 users were so few and far between that it was still worth it..
- Likes 1
Comment
Comment