No. Only 64-current. no multilib no wine

Hello, Slackware 14.2 32 bits for laptops that can't do Slackware 14.2 64 bits, the later otherwise.

current 32bit on a Samsung NC10.

I use slackware-current on a old Pentium 4 3ghz with 3gb ram and ide-160gb disc, a Soundblaster live, and a Geforce card and a old CRT monitor connected

I love that slackware still ships with svgalib.. i play a game at 154fps in 320x200 at 154hz with it sometimes when i get bored. :-)
And yeah.. the nvidia driver in svgalib actual works, and adding modelines is no problem

Call me legacy.. but i love it!

I am running 32-current on my Thinkpad T460. Works well, sometimes there are some quirks, but none last long.

Yes, but only because my Slackware system has a 32-bit processor. There are otherwise no benefits to using 32-bit for me personally.

My home network has two 32-bit laptops (well, one is an Asus EeePC 900), two 64-bit mini-towers (one is the firewall and network server, the other is my desktop), and two RPi's (one for tinkering, one for the HTPC running Kodi). Except for the HTPC, they're all running Slackware-current.

The x86 and x86_64 systems I update usually at the same time, using multixterm to drive the updates simultaneously. I keep the local package repo on the Slackware ARM RPi's NFS server, and have some symlinks set up to take each remote login to the proper 32-/64-bit repo for that machine. Having the /etc/mkinitrd.conf set up for each machine means I can also generate the initrd's at the same time. The Asus EeePC boots using extlinux; the rest use LILO.

I have 32 bit Slackware 14.2 running on a 2009-vintage netbook PC. It's used as part of a FCC Part 15 FM radio station, with Audacious in shuffle mode and the audio plugged into a cheap FM transmitter. Works perfectly.

Everything else I have is 64 bits.

I only moved to 64bit to use Skype to communicate with my kids and just stuck with it. 32bit did just about everything I needed.

Attached Thumbnails

 

I still have an old PIII running 14.2 (old hardware requirement that newer HW cannot meet). It'll be around at least until I finish a migration project and then it'll likely be headed to the electronics recycler.

Interesting thread. Quite a few folks still on 32-bit.

Slackware Current 32bit on virtual machine, for dns and mail services.

it was originally bare metal 32bit and I virtualized it as is.
I might sooner or later migrate the services to a 64bit VM, but considering that all is working without any issue, I don't feel any pressure. Also it's nice to have diversity.

I run 64 bit 14.2 on my main box with multilib simply because this was my first 64 bit install and I didn't want to immediately recompile the 500 or so bins in /usr/local. I have had no problem with multilib but maybe that is because I don't update the box. It is not internet facing so I don't worry about security patches.

Late to the party...sorry.

Running -current on a Dual Pentium Pro w/512MB ram. Providing dhcp, ntp and dns services for my home network. This system was fresh installed with 14.2 when it was released, then immediately switched to the current branch. I usually do 'update/install-new/upgrade-all' once a week. Was also running Nagios and Cacti to monitor about 70 systems over 4 VPN links, but moved these services to a RasPi B+, running SARPi 14.2, just to get my feet wet with the Pi & Slack. Would like to move these services back to the PPro...maybe next winter.

The issue I have with the '32-bit' branch is that current is being coded and compiled for a CPU that has SSE/SSE2/SSE4 instructions, which my true '686' knows nothing about. Can't even use XFCE since librsvg uses the SSE instructions. Fluxbox works, but I run XFCE everywhere else. I like to run X so that I can open multiple terms for debugging and logging. I know it's SLOW...but it works.

The old saying was that: Slackware would run on 'anything,' especially OLD-er hardware. The evolving 15.0 branch is creating a divide that I understand, but it makes me sad.

This isn't a kernel issue, yet. That's a GOOD thing! Want to talk about Token Ring support?

Another 32-bit system is an old P4 that's running 13.0 as a MythTV 0.20 backend server. Built in 2007...and still running. Used along with two AMD Phenom's and a secondary backend and frontend running 13.0 64-bit. The video chips are Nvidia GeForce 5100/6100's that use old XvMC features that newer MythTV versions dropped. These three systems are pretty much the definition of an appliance - still in use - thirteen years after they were built.

The last major 32-bit system I use daily is the ThinkPad A21p P3 that I'm using right now to compose this. It's running 13.37, running a remote Seamonkey instance hosted on a 64-bit AMD Athlon 64 X2 running 13.37. Odd arrangement here, but I LOVE the 1600x1200 display and TrackPoint! Every PC I run MUST have a TrackPoint keyboard or my carpal tunnel flares up and my right hand goes numb.

The 32-bit branch is still important, but I can see at some point it will be left to bit-rot.

1 members found this post helpful.

I've got a few half-depth 1u servers with Atom procs in them, so 64bit isn't an option, but they're overqualified for their designated roles, and so they will continue in those roles :-) I also have a 2010-ish laptop with an Atom proc - it lives in my shop for when I need to research a part or some such and don't want to walk back inside...