Have you been running slackware-current for the first time for x86_64? If so . . .
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.
In the past I ran -current, but stopped because of other obligations.
Since Slackware64 -current was released in May I've been running it.
Once it becomes Slackware 13.0 the 64-bit boxen on our LAN will all
get upgraded to it. I'll keep one partition, or VBox image, of -current
on my ThinkPad T61 in order to test and offer feedback to Pat.
I usually do not run current, but this was a special case. When x86_64-current...
I waited quite a while before (changing my mind and) deciding to download -current because of my horrible dialup speed.
Both my boxii run Slackware, but I have only one nice machine (the 64bit one running -current) while the firewall machine will be staying with Slack 11 for the foreseeable future. Once S13-x86_64 is officially out, I'll be running that on my main machine.
Now, if I could *just* eventually finally get the room-mate's machine converted once and for all (it's had MANY OS's on it, but WXP is still the main one) then all the boxae in the house would be Slack!
I started to current versions for enjoy using KDE4 because Compiz never worked well. And now I enjoy 64 bits power + Kde4.
I think I did not find a more stable linux in your current version than slackware.
I'm running both 64 & 32 bit current now, but I'll settle for stable when 13.0 comes out. Although I might keep one arch as current as well, for when I'm feeling adventurous. And I'm hanging on to 12.2 too.
Some years ago I used to run the stable releases of slackware, but now I changed from bluewhite64-current to slackware64. The primary reason for continouos updating slackware64-current was to get the latest releases of kde4. I experienced some big steps in performance with every new kde4-version and with some changes in xorg. So it was worth to often update my PC.
Distribution: Caldera, CTOS, Debian, FreeBSD, Mac OS X, Mandrake, Minix, OpenBSD, Slackware, SuSE
I've run Slackware for over 9 years and have never tried current. The x86_64-current had made me curious to try it, but I haven't made the leap yet. I'm sure I won't be disappointed. I do plan on switching from 32 to 64 bit when it becomes stable.