i386 architecture will be dropped starting with Ubuntu 19.10
discourse.ubuntu.com
discourse.ubuntu.com
Are Ubuntu's 32-bit x86 packages limited to those targeting the i386 instruction set? As in, "we ship x64, or ancient i386, but nothing in between"?
Or do they use the i386 moniker used as an umbrella for all x86 architectures?
AMD was the first to develop and announce a 64-bit x86 extension back in 1999 and since they shipped the first hardware, the amd64 name distinguished it from Intel's IA-64. When Intel wrote off IA-64 and adopted AMD's extensions the “amd64” name was already used in a number of places.
Calling i686 i386 doesn't, unless packages are actually compiled for i386 (which I don't think they are).
I don't know how much of a difference this makes in practice however.
Or just use REP MOVS. Modern CPUs recognize it and do optimal memory copy internally. Prefetch instructions are rarely beneficial, and often cause worse performance.
Edit: Apparently AMD Ryzen lacks REP MOVS optimization. SIMD based memcpy performs the best on it. (Intel supports REP MOVS optimization since Ivy Bridge.)
https://en.wikipedia.org/wiki/IA-32
i586 / i686 are later iterations of IA-32
It won't run in i486 or i386, though, so they're both inaccurate names
This would have some crappy implications for Wine and games in particular.
> Q. How can I run 32-bit Windows applications if 32-bit WINE isn’t available in the archive?
> Try 64-bit WINE first. Many applications will “just work”. If not use similar strategies as for 32 bit games. That is use an 18.04 LTS based Virtual Machine or LXD container that has full access to multiarch 32-bit WINE and related libraries.
Your post is really slanted "upgrading to Debian", "Company vs Community", suggesting that profit goes against the user's best interest
I'm writing this as someone who uses Arch at home & Debian at work
'"Company vs Community", suggesting that profit goes against the user's best interest'
That depends on what users interests are: if they match with the company goals, then profit will help users as well. Killing parts of a project because they don't bring money is perfectly acceptable for a company (just look at how many project were axed by Google recently), but again, we should ask to users who invested time and money working with them.
BTW, Many small appliances, embedded systems etc. still run 32 bit cpus. Linux isn't just for servers or desktops.
There's a post about Lockheed looking for VAX people. I guess a lot of people are using 32 bit machines.
OTOH, they don't tend to run the latest software.
Say, what's the state of fanless dual (or even triple) NIC boards these days? Intel network chips please, the CPU can be whatever. It looks like I need one that does 64 bit before 18.04 runs out of support.
Edit: x86_64 CPU please, not ARM.
Thanks for the suggestion (amazon reviewers aren't so happy with it though). I want a motherboard not a NUC-like system though. Still using sata, running some servers on it etc.
https://askubuntu.com/questions/877703/only-32-bit-distros-a...
The CPU may be, but the bios and motherboard... possibly not so much. The system is pretty old and could use a replacement anyway before it croaks on me.
There's also the espressobin, which is an AArch64 board with 2 NICs, one attached to a Topaz switch. The espressobin has mainline Linux support, which is awesome.
And people will no longer need a duplicate set of libraries on their machines, all the way down to the gfx drivers. New software, and old stuff with 64-bit support, should have a lot less compatibility issues.
I'm running Debian not Ubuntu, but the absolute minimum they owe their users is an automatic upgrade path.
How exactly do you purpose they perform an "automatic upgrade" on their user's hardware? You don't just patch or upgrade to go from 32 bit to 64 bit. You can't hotfix hardware like that.
Personally I would go for unpacking the 64bit userland+packages in a subdirectory, boot once into a rescue userland which just switches the directories around, then boot normally.
GRUB already has support for "boot once in this alternate configuration", so it's all there.
But shifting the packages from 32 bit to 64 bit is not supported automatically.
And that despite the ability to install both 32 and 64 bit packages side by side.
It's like they did all the hard part for the upgrade, and just didn't finish that last little bit (find 64 bit versions of existing 32 bit packages, and install them, then remove the 32 bit).
It would still require setting everything up again, but at least once you've done that once you can put the settings in a git repository and be done with it forevermore. Reinstalling is a trivial operation.
In dpkg, add the amd64 architecture. Install and boot a 64-bit kernel. Then carefully replace 32-bit packages with 64-bit packages. You'll hit a few bumps along the way, but it's possible to do without reinstalling from scratch.
That said, it'd likely be easier to install 64-bit, diff and copy across configuration files, and port over your installed package list (dpkg --get-selections) with a bit of care for packages whose names differ between 32-bit and 64-bit. I've done something similar when setting up new systems, and it's about a half-day's work, not a month.
With my latest PC I went with a clean install though.
1. dpkg --get-selections 2. Backup global data (databases and such) 3. Backup global config (/etc, /use/local/etc) 4. Backup home directories 5. Reinstall and apply all to the new system.
This is a weekend job at most if it ends up being complicated.
I guess I should have clarified that I already have a 64 bit CPU, and 64 bit kernel, but my initial installation is 20 or more years old and has been updated since then, from that same initial installation. (It's even the same initial ext3 filesystem, since I used md raid to shift the installation to new hard disks over time, it used to be ext2, but that upgrade was automatic.)
Debian has the ability to have both 32 and 64 bit packages installed side-by-side.
I.e. they did the hard part. I just need some way to automatically shift each package to its 64 bit equivalent, then remove the 32 bit one, and eventually the libraries too once nothing depends on them.
https://wiki.debian.org/CrossGrading
as well as several articles linked and scripts available.
Do you have a support contract? If not, ask yourself about the complexity of what you feel entitled to — especially given that a system which will “take a month to get everything set up again” is far from a clean upgrade — and ask how much effort you've contributed to the project helping make that feature exist.
I even used to have a [minor] package I maintained there (it's gone now).
The feature almost exists, Debian can run both 32 and 64 bit versions of a package side-by-side.
Except firefox who become useless on 32 Bit after quantum I don’t have any problem with Debian on my netbooks. I am really curious about the “lack of support” in the kernel, Any idea?
I'm in turn getting annoyed at the complete lack of cost/benefit analysis that this entails.
Every software project has to deal with limited resources and the attitude that the vast majority of people running on more mainstream platforms should forsake improvements (in security or usability by Rust for example) in order to support Solaris, Illumos, HP-UX or any of those niche platforms, well that just pisses me off.
I still have a 32bit Debian installation (originally installed around 2003 and been Ship of Theseus-d over the years so it actually has 64bit hardware now) that I didn't have the time or motivation to upgrade, but if 32bit support would go away tomorrow I'd understand. What's the percentage of 32bit vs 64bit users? 0.3%?
Commercial interests have little incentive to serve this demographic, due to their lack of buying power. That leaves open source projects that were created for the public good.
From the article:
Q. What happens if I use a flavour of Ubuntu (Xubuntu / Lubuntu / Kubuntu etc)?
All the official flavours are built from the same common archive of software packages. As the Ubuntu archive drops support for i386, it would not be available to any flavours. If you absolutely need an i386 version then 18.04 LTS is still available.
> What are som good alternatives to these that will continue to run on older 32-bit machines?
Puppy, maybe?
The kernel still supports i386 and surely it's not that much effort to make sure Gnome and the various packages compile for it? They still plan to support 32 bit ARM systems?
It's been years since I saw a 32 bit laptop anywhere in Asia.
Every mainstream desktop CPU since late 2005 has had support for 64-bit, and mobile CPUs since 2008. If you're still running pre-2005 hardware, is the latest version of Ubuntu even really running that well at all?
Besides, they can continue to use 19.04 or 18.04 LTS. It's not like discontinuing support means existing installs are going to break.
> version of Ubuntu even really running that well at all?
Ubuntu server and Lubuntu are still very agreeable for older hardware.
> Besides, they can continue to use 19.04 or 18.04 LTS. It's
> not like discontinuing support means existing installs are
> going to break.
After just a few versions of Ubuntu it becomes harder to find archive repositories, especially if you want to do anything like cross-compiling. It basically is a death sentence.
How does it compare on single core benchmarks?
I just have a psychological aversion to replacing something that is still fulfilling its job.
Nevertheless, I'll get around to replacing before then.
UPDATE: Looks like Ubuntu isn't dropping just the distro - they want to drop multiarch packages as well. That's already nasty.
> Q. Doesn’t Steam use 32 bit libraries? How can I play my games?
> Q. How can I run 32-bit Windows applications if 32-bit WINE isn’t available in the archive?
It means they are dropping 32-bit packages for good, not just the distro.
I'm using GOG, not Steam. They don't commonly rely on bundled runtime. Proposed solutions with lxc and such are quite annoying. And it's not about 32-bit Wine, it's about WoW64 Wine requiring 32-bit libraries to run 32-bit stuff. Lot's of older games are 32-bit and will never be converted to 64-bit.
If there is no 32-bit multiarch, how are we supposed to build 32-bit Mesa and dxvk / d9vk for example? And if we can't, everything will be stuck with outdated versions. It's a huge mess they are pushing for. I hope Debain won't do this horror if they can avoid it.
Dropping support for 32 bit software is super sucky.