[SOLVED] Use 32-bit Slackware? Post here to let the developers know!
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I do not use 32-bit software. I could, I have 3 or 4 old machines that I could install it on, if I wanted to. And if I did, I would be confident that, even if Slackware-15 was 64-bit only, I would have a safe, secure OS that would probably outlast the hardware it was installed on. The future is 64-bit & beyond, the past is 32-bit; Slackware can cover it all, even if the new versions are 64-bit only.
Maybe 32 bit is the past for some but the world community still uses 32 bit. Sure the future is x86_64 but let us not exclude other users that depend on their present hardware. I think that PV is presently providing a good means but we as a community can provide additional support for those Slackers that do not have the latest & greatest hardware. We can continue providing additional 32 bit support here at LQ for legacy hardware.
Last week I downloaded the new Slackware 14.0 image, and it was the 32-bit version.
I'm using mostly x86-32 machines and they do the job beautifully. When I decided to install Linux it was, among other reasons, because it allowed me *not* to throw away my perfectly working computer. I think this is one important reason why many people all over the world decide to migrate to Linux: it is the great alternative solution for people not willing to trash their computers simply because the Redmond folks & Co decided they have to.
In my case, I can still use a 15 years-old machine as a stripped-down firewall, a few old Pentiums as servers, and so on and so forth. They're working perfectly, I don't need anything more. And for more demanding tasks a Pentium IV does the job, and it's 32-bit. In my opinion, dropping the 32-bit architecture would make lots of still perfectly working machines, all over the world, perfectly unusable.
Best regards, and thank you for the great work you're doing,
Last edited by Philip Lacroix; 02-04-2013 at 12:58 PM.
Distribution: Slint64-14.2rc on Lenovo Thinkpad W520
Originally Posted by H_TeXMeX_H
Ok, so what kind of information is needed ? Obviously not opinions ... so then what ?
Use cases for _32-bit_only_ -- if any, of course.
BTW I have one: my laptop includes a 64-bit dual core processor (with 3 GB of RAM as it had Windows Vista pre-installed), but I use Skype, do not feel a real need for 64-bit Slackware (mainly scripts editing or office tasks) and am a little bit too lazy for multi-lib.
I own two 64-bit capable laptops and use 32-bit Slackware on both
Hello fellow Slackers.
Yes I own two 64-bit capable laptops with more than 4G of RAM, and 32-bit Slackware is installed on both, even it it was actually hard configuring UEFI and GRUB2 and all that stuff to boot a 32-bit OS from 64-bit firmware. All other boxes I own are not 64-bit capable, including my mother's PC.
-I use proprietary software which do not have 64-bit native versions. Multilib seems problematic, at least I have not tried yet.
-Some commercial software I use and depend on for critical tasks (engineering software) would require recompiling, and it's certainly a problem maintaining compatibility. (and yes I'm a little lazy to keep my boostrapping and toolchaining up to date. I slack a lot and watch kitties on youtube too). (I recommend the flying kittens video btw http://www.youtube.com/watch?v=3oem-M2tQU4)
In sum, it's quite comfortable to use 32-bit Slackware. I know the future is 64-bit, but I'm waiting for upstream commercial software I depend on to release stable and reliable 64-bit versions.
From their website:
The critical dependencies should be met on most platforms, but there are a few recommended packages that could not be included in the installers. This is partly because the respective package format does not easily support combining 32 bit and 64 bit dependencies. Another reason is that one installer spans more than one distribution versions.
Other application I frequently use has only support for 32-bit distros except for Debian, which in turn creates other problems.
In the meantime, good old 32-bit Slackware just works.
Last edited by folkenfanel; 02-04-2013 at 01:46 PM.
Reason: adding link-URL for the flying kittens video
My desktop has 64-bit Slackware installed, however my laptop, an older Lenovo ThinkPad X60, only supports 32-bit, and has for years run 32-bit Slackware. Almost 7 years old and still does everything I need to do perfectly! So, I'll be using 32-bit until it falls apart.
That's not so sure. Maybe the future of gaming consoles. In the mainstream ARM (32 bit by the way) will overtake everything.
I respect your opinion but ARM is still evolving and we do still have x86_32 machines in use by the world community. Not just hackers or die hard Gnu/Linux users. More people are moving from their Xp/Vista/Win/7 based OS to the freedom of a x86_32 Gnu/Linux to continue use of the older hardware throughout the world community for legacy hardware.
Personally, I do have laptops that are used as controllers with x86_32 and will continue to use long into the future. Education departments are still using revived hardware via 32bit Gnu/Linux. Look at the Open Source software available for new Gnu/Linux users with legacy hardware without much investment, mostly time and some bandwidth.
Using 32 bit here. I've never run 64 bit Slackware, even though my last two systems have been amd64 arch - I did run 64 bit Debian for a few years but never really saw the benefits (my CPU's are not that high end and the most RAM I've had has been 2GB.
If multi-lib is integrated better into slackware64, I think we can get rid of slackware32.
If we were to make a poll, I bet most people are using slackware32 because of 1 or 2 proprietary 32-bit programs. That's just silly, but it's probably true.
I think it's clear from this thread, that many people still use old 32-bit hardware, and even some newer hardware (e.g. netbooks with Atom N270 CPU; we have one at home and it's being used actively) is only 32-bit capable. Also I'll repeat myself, that 32-bit Slackware is a smart choice for a small VPS with a limited amount of RAM, if one wants to squeeze more out of it (64-bit applications consume more RAM). So no, we can't get rid of Slackware32 yet.