Slackware current stability

bpcw001 · 11-30-2004, 03:38 AM

Hello all,

I'm using 10.0 at the moment, but I'd like to have a newer X.Org/Qt/KDE than included in 10.0.

I could go for a self-made compile of all this, but then it came to my mind to switch to Slack-current.

Could anyone comment on the stability of Slackware-Current (aka 10.1) ?

Will the stability be OK for a software development workstation yet ?

Thanks

BPW

mdarby · 11-30-2004, 05:51 AM

I run Current with all the programs listed in my sig. I've never had a problem at all.

Hangdog42 · 11-30-2004, 07:43 AM

Just keep in mind that while current is reasonably stable, from time to time things do get introduced that can cause problems. I've only run into one problem with using current, but that was enough to force me to re-install. Ever since then I've just stuck with the stable releases. It all depends on your appetite for risk and how crucial your machine uptime is. If you can't afford downtime or a re-install, I'd wait for 10.1.

bpcw001 · 11-30-2004, 07:44 AM

mdarby,

thanks for your reply. Good to hear you don't have problems with Slack-current.
Judging by your list of applications, you seem to run a GUI-less webserver.

Problems usually come up when using all the X stuff, KDE, Gnome etc.
Might be intersting to know about those ones.

bpcw001 · 11-30-2004, 07:49 AM

Quote:

Originally posted by Hangdog42
Just keep in mind that while current is reasonably stable, from time to time things do get introduced that can cause problems. I've only run into one problem with using current, but that was enough to force me to re-install. Ever since then I've just stuck with the stable releases. It all depends on your appetite for risk and how crucial your machine uptime is. If you can't afford downtime or a re-install, I'd wait for 10.1.

Thanks for your reply.

having to fiddle around for a long time or even reinstall due to something being seriously broken is not
really what I can afford.

I should probably stick with Slack 10.0 stable and compile latest X.Org, Qt and KDE by myself.

Unfortunately, poor Pat has to fight this strange desease, so we might not see 10.1 released soon

rotvogel · 11-30-2004, 09:09 AM

You could use the new packages on the new slackware-updates site for X.org 6.8.1 . They are running fine on my Slackware 10 machine. I'm using the default Slackware QT and a self compiled KDE 3.3.1 version. For compilation of a certain KDE component (KDE bindings I believe) you will have to remove the libqt.so* symlinks. You could also try the packages on the KDE ftp server.

eelriver · 11-30-2004, 09:23 AM

I run a complete install of -current on two machine and I have had no problems. Current packages are not typically iherently unstable, they are just -current to see how they would fit into a new release.
Remember, if you upgrade to -current, do not pick and choose. -current packages are compiled against previous -current packages, so installing any packages after a major library upgrade without doing that upgrade could cause problems.
Also, reading the -current ChangeLog very carefully will help you avoid a lot of problems.

Speek · 11-30-2004, 03:12 PM

Here is some valuable info about upgrading to current:
http://uselesstree.org/tree/trunk/the_complete_slacker

I've followed these instructions and had no problems. I do run X, but no KDE or Gnome (Icewm my preferred window manager).

ringwraith · 11-30-2004, 03:43 PM

I have run current for a few years and never had any problem. You want to carefully follow the instructions in the changelogs. There are instructions on configurations, removing, adding packages in addition to upgrading them.

reddazz · 11-30-2004, 06:14 PM

I use current as my main distro and have never had any problems due to the extensive testing that the Slackware team do before releasing packages.