SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
View Poll Results: Reasons you use 32-bit Slackware
I must run 32-bit-only software (like Skype, wine, etc.)
40
21.86%
My computer is 32-bit only
69
37.70%
I'm too lazy to maintain 64-bit (possible multi-lib)
27
14.75%
I'm too afraid
3
1.64%
Other (specify below)
26
14.21%
I use ONLY 64-bit Slackware (possible multi-lib)
67
36.61%
Multiple Choice Poll. Voters: 183. You may not vote on this poll
I have Slackware 64 with multi-lib on my main PC and did the same on my SO's laptop. However, for my Dell INSPIRON Mini netbook, I decided to go for 32-bit Slackware (even though it has a 64-bit processor) and avoid the multi-lib hassles.
A lot of older software was written for 32-bit machines and compiling them on a 64-bit platform sometimes causes problems. Multi-lib usually works but sometimes . . .
I run on my main machine Slackware64-current. I have done this since AlienBob made this possible. That said, I do have a separate partition with Slackware64-current/Multilib just because of Steam. I have seriously considered going multilib with my main machine just to stop rebooting. Now this is where I get lazy not wanting to keep up with multilib on -current.
I've voted the first two but, to clarify, I go 32bit only if strictly needed (by hardware or software), I use mainly slackware64 on my workstations (sometimes with multilib) and servers.
I have Slackware 64 with multi-lib on my main PC and did the same on my SO's laptop. However, for my Dell INSPIRON Mini netbook, I decided to go for 32-bit Slackware (even though it has a 64-bit processor) and avoid the multi-lib hassles.
A lot of older software was written for 32-bit machines and compiling them on a 64-bit platform sometimes causes problems. Multi-lib usually works but sometimes . . .
In that case you would select ' I'm too lazy to maintain 64-bit (possible multi-lib)'.
For a lot of small server machines 32 bits is the best, if not only , option.
In desktop machines 64 bits is a viable option in most, but not all, situations
My computer is 64 bit so I use 64 bit, however I use wine for Quicken, I have yet to find a financial application for linux that will allow me to forward plan with recurring transactions, and output the information in a meaningful graph.
Most of my Slackware boxes are 64 bit ready, but, they are a little older having only 2 GB RAM, so it is not really worth it to run 64 bit (performance-wise).
It doesn't seem right to define myself by a netbook that I only use occasionally. I do lots of work on my PC including multi-lib support.
The netbook used to have Window$ 7 (history!!! ) but the 32-bit version. I think that's what finally persuaded me to go that way.
It's your choice, but mostly I want to find out why people still use 32-bit. They didn't want to make a poll in the other thread, so I made this to try get more info on why people still use 32-bit.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.