LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

View Poll Results: Have you been running slackware-current for the first time because of x86_64? If so,
Yes, this is the first time. I will keep running -current even after 13 is out. 7 7.61%
Yes, this is the first time. Once 13 is out, I'm sticking with the stable release. 20 21.74%
No, I have run -current before, but I will go back to a stable release once 13 is out. 23 25.00%
No, I have always run -current. 15 16.30%
I am not running -current . . . I will wait for the stable release, thank you very much. 27 29.35%
Voters: 92. You may not vote on this poll

Reply
 
Search this Thread
Old 08-01-2009, 05:34 PM   #1
foodown
Member
 
Registered: Jun 2009
Location: Texas
Distribution: Slackware
Posts: 609

Rep: Reputation: 218Reputation: 218Reputation: 218
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."

Last edited by foodown; 08-03-2009 at 11:56 PM.
 
Old 08-01-2009, 05:44 PM   #2
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,373

Rep: Reputation: 164Reputation: 164
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.
 
Old 08-01-2009, 05:52 PM   #3
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,407

Rep: Reputation: 853Reputation: 853Reputation: 853Reputation: 853Reputation: 853Reputation: 853Reputation: 853
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

Last edited by ponce; 08-01-2009 at 05:54 PM.
 
Old 08-01-2009, 06:30 PM   #4
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
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.
 
Old 08-01-2009, 08:03 PM   #5
niels.horn
Senior Member
 
Registered: Mar 2007
Location: Rio de Janeiro - Brazil
Distribution: Slackware64-current
Posts: 1,004

Rep: Reputation: 89
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...
 
Old 08-01-2009, 09:51 PM   #6
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Arrow

Quote:
Originally Posted by mlangdn View Post
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!

Sasha
 
Old 08-01-2009, 10:40 PM   #7
ROXR
Member
 
Registered: Jan 2009
Location: Spain
Posts: 105
Blog Entries: 1

Rep: Reputation: 18
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.
 
Old 08-02-2009, 06:42 AM   #8
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,915
Blog Entries: 51

Rep: Reputation: Disabled
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.
 
Old 08-02-2009, 09:37 AM   #9
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
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
 
Old 08-02-2009, 08:01 PM   #10
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,141

Rep: Reputation: 523Reputation: 523Reputation: 523Reputation: 523Reputation: 523Reputation: 523
I will keep my partition of Slackware64 -current even after the release of 13.0. I will also upgrade to 13.0 as well.
 
Old 08-02-2009, 08:35 PM   #11
veeall
Member
 
Registered: May 2007
Location: Estonia
Distribution: Slackware 12.1, slackware64-current
Posts: 252

Rep: Reputation: 43
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.
 
Old 08-03-2009, 03:09 AM   #12
janhe
Member
 
Registered: Jul 2007
Location: Belgium
Distribution: slackware64 13.1, slackware 13.1
Posts: 369

Rep: Reputation: 45
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.
 
Old 08-03-2009, 06:49 AM   #13
Nylex
LQ Addict
 
Registered: Jul 2003
Location: London, UK
Distribution: Slackware
Posts: 7,464

Rep: Reputation: Disabled
I've never run -current, but when 13 is released, I think I'll run -current 64 alongside -stable 32.
 
Old 08-03-2009, 08:06 AM   #14
metrofox
Member
 
Registered: Jan 2009
Location: Palermo, Italy
Distribution: Slackware
Posts: 236

Rep: Reputation: 37
I've been running -current(slackware 32) for 4-5 months, when slackware64 13 will be released I'll upgrade to -current64
 
Old 08-03-2009, 08:22 AM   #15
bsdunix
Senior Member
 
Registered: May 2006
Distribution: Caldera, CTOS, Debian, FreeBSD, Mac OS X, Mandrake, Minix, OpenBSD, Slackware, SuSE
Posts: 1,757

Rep: Reputation: 78
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.

Last edited by bsdunix; 08-03-2009 at 08:23 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Setting time and time zone altogether properly in Slack-current, KDE4 spaceballs Slackware 3 04-20-2011 05:15 AM
Slackware-current (x86_64) Xorg crash chaosorama Slackware 3 08-01-2009 02:09 AM
DISCUSSION: Upgrade to Slackware -current without a -current CD truthfatal LinuxAnswers Discussion 0 09-19-2006 01:42 PM
Warning to Slapt-get/Swaret users running Slackware-Current shepper Slackware 8 07-28-2006 03:45 AM
slackware current, adsl connection problem (time out) Xavius Slackware 17 08-05-2005 09:58 AM


All times are GMT -5. The time now is 11:26 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration