Stories
Slash Boxes
Comments

SoylentNews is people

posted by FatPhil on Thursday January 26 2017, @11:46AM   Printer-friendly
from the all-the-world's-a-Cray dept.

Arch Linux is moving ahead with preparing to deprecate i686 (x86 32-bit) support in their distribution.

Due to declining usage of Arch Linux i686, they will be phasing out official support for the architecture. Next month's ISO spin will be the last for offering a 32-bit Arch Linux install. Following that will be a nine month deprecation period where i686 packages will still see updates.

Any Soylentils still making major use of 32-bit x86? And any of you using Arch Linux? Distrowatch still lists Arch Linux as a top 10 distribution.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by tonyPick on Thursday January 26 2017, @01:33PM

    by tonyPick (1237) on Thursday January 26 2017, @01:33PM (#458902) Homepage Journal

    From memory I've think I've still got some legacy toolchain things (& bespoke tools from vendors) for embedded system cross compiles that are 32 bit only and would be impossible and/or a royal PITA to try and rebuild or run on a 64/multilib system, but you still want a decent host development environment to use them.

    Of course there's VirtualBox, and the older install iso images aren't going anywhere, so just running legacy tools inside a 32 bit VM on the older distro means this isn't a problem provided ssh & X-remoting continues to work.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by Runaway1956 on Thursday January 26 2017, @03:07PM

    by Runaway1956 (2926) Subscriber Badge on Thursday January 26 2017, @03:07PM (#458950) Journal

    Is the old VMware tool still available? Plug in a running system, and the virtualization tool would move it from hardware into a virtual machine. Or, if the hardware wasn't running, it would make a copy of the hard disk, then fire it up for the move. Or, that's how I remember it working, anyway.

    Ahhhh, we have something here - https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1018406 [vmware.com] Looks like names have changed (presumably to protect the guilty) but the end goal is the same. Migrate hardware OS's to VM's.

    --
    “I have become friends with many school shooters” - Tampon Tim Walz
  • (Score: 2) by The Mighty Buzzard on Thursday January 26 2017, @06:55PM

    by The Mighty Buzzard (18) Subscriber Badge <themightybuzzard@proton.me> on Thursday January 26 2017, @06:55PM (#459053) Homepage Journal

    Fair nuff. That only means you need those specific 32bit libs though, rather than an entire 32bit system.

    --
    My rights don't end where your fear begins.