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.
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.
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
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.
Distribution: Slackware 10.2 kernel 2.6.13, Gentoo amd64, Some mish-mash of programs that started with slack 9.0
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.
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.