[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.
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Originally Posted by NonNonBa
It is not anymore. Drop an eye on the downloads page to find the i686 port.
I Just downloaded it and had a look inside the initrd. Interesting. I'll give it a try as soon as my homework is finished, in a very few weeks now. BTW, I think I will need your cooperation for UTF-8. I will send you a PM about that later today.
Last edited by Didier Spaier; 02-09-2013 at 02:46 PM.
Distribution: Slackware (mainly) and then a lot of others...
Either I missed the question or else I did not understand the seriousness of the question.
Hardware wise all I have is 32 bit (2 desktops and 1 laptop) and I do not intend to replace them soon (I wish I could).
But this in no way has anything to do with slackware development (AFAIK). Unless Pat and crew tell me that they would not be suporting 32-bit slackware anymore. I believe the slackware community (crowd) would follow them and trust them to make the right decisions.
To Slackware developers: You guys have done an awesome job thus far and I believe that you would continue the same way in the future.
It seems to be a bit of odd that Slackware devlopers would be swayed by anything (even the community views) that would hinder them from delivering the greatest and the most beautiful OS there is out there.
My 2 cents.
Thanks for everything man you have been a huge asset to the community. While Slackware certainly can get along without you; I know I and many people here are very grateful for all the hard work you have put in over the years. You have made our favorite distribution better and all our lives easier. Whatever you decide to do, best wishes and good luck.
As far as 32-bit goes. There is quite a lot of still very capable Atom and similar hardware out there that is almost contemporary. I know while I was traveling for about a year I used my HP Mini Netbook (1366x768 display) which is 32-bit only as my only machine. It served me well and Slackware enabled me to manage personal activity on it. As well as having a bit of fun gaming etc. So there is still real value in 32-bit platform. Many of these machines are really not that old, some only around 2 years. Multilib also depends on a x86 package tree being available.
That said as a developer I recognize how tedious maintaining multiple trains of the same code gets. I also know given Slackware's tradition of supporting older release with security patches for years the number of additional builds of things keeping x86 train going likely means. Older machines can run older releases especially with security patches available for some reasonable period of time. There is not much x86 only hardware being produced now if any and the remaining 32-bit only software should be shifting off to the dustbin of history over the next few years too.
I would say a library/compiler/a set/X/kde/xfce refresh on 14 as a 14.1 will probably make sense. Then perhaps a major release after the new math gets baked in, that being udev, systemd (hopefully not), etc settling down as Slackware 15. Maybe that could be the last x86 release. That way those major changes get rolled in, and folks using that last gasp of more recent x86 hardware can expect to be able to support themselves updating higher level packages from slackbuilds without major heavy lifting for a little while longer until the hardware really is quite obsolete. Hopefully by then alternatives to the remaining 32-bit only software most depend on will exist as well.
All that is just my 2 cents though; I have total faith whatever decisions Pat and his team makes will be the right ones.
Last edited by chemfire; 02-09-2013 at 06:50 PM.