Have you been running slackware-current for the first time for x86_64? If so . . .
 

Have you been running slackware-current for the first time for x86_64? If so, will you keep running -current once version 13 is released?

1) Yes, this is the first time. Also, I find that I enjoy running -current and will keep running it even after 13 is out.

2) Yes, this is the first time. Once 13 is out, I'm sticking with the stable release.

3) No, I have run -current before, but I will go back to a stable release once 13 is out.

4) No, I have always run -current.

5) I am not running -current . . . I will wait for the stable release, thank you very much.
________________________________________________
foodown
"The best defense against logic is ignorance."

I usually do not run current, but this was a special case. When x86_64-current was made available, I immediately started using it. I have not looked back since.

i think, as usual, current will restart a while after 13 will be released, so we will have to stick with stable for a little :D

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 run Slackware64-current on a test machine (with daily use), Slackware-current in a VM and -stable on all "production" machines...

Running -current is fun and an opportunity to learn new things. I have been following -current on a separate test machine for some time now.

But - although it has been very stable lately - it should not be run on boxes with critical data etc.
Things *can* stop working...

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!

Sasha

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.

Markus

I will keep my partition of Slackware64 -current even after the release of 13.0. I will also upgrade to 13.0 as well.

I will probably run current even after the release of slackware 13 because i'm interested in trying out shiny kde4.3 when it appears in current at some point.

I started using -current again after the libraries became incompatible with 12.2

Not for the 64 bit, but for the updated KDE 4.2

In fact, I'm still running slackware32-current, and will do so untill I _need_ the other 32 bits. I sometimes use commercial pre-compiled software, and for now I have no compelling reason to switch.

I've never run -current, but when 13 is released, I think I'll run -current 64 alongside -stable 32.

I've been running -current(slackware 32) for 4-5 months, when slackware64 13 will be released I'll upgrade to -current64 :)

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.

I upgraded a test box to current, very cool. :cool:

I have been using BlueWhite64, a 64-bit version of Slackware with some additional bells and whistles. Is there any reason to switch to Slackware 64-bit instead when the BlueWhite64 works so well. What are the benefits of switching to this new version?

current or stable?
 

I was running wolvix for some time, then dual booted with slackware current-32 (as it had almost the applications I wanted):cool:, until I had it configured and was happy with it. When slackware64current was released 32 replaced wolvix and I have slackware64-current to test and configure as my main system.

I now intend to use slackware13 for my workstation, and test current to move up to and learn from. From my experience, current has been more stable than other distro stable versions. I have learnt very much since moving to only slackware.

i have been running -Current on my laptop since i installed Slackware 10.1 on 2005 and i don't have any issues with it. Everything is running well and i don't need to reinstall whenever next Slackware is released.

The same thing also applies on my desktop at home and also at my office. Everything is running -Current and very stable

I am not running -current . . . I will wait for the stable release...

I use dial-up !!!!!!!!!!! I love kopete :(

thank you very much.

afreitascs

ps: the stable version will take ?

my en is bad ...