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.
I'm thinking of making that ISO-image of Slackware-current and installing it to replace slackware 8.1. My question is how trusthworty is it? ... is guarenteed to have bugs and problems or should it be quite good to use?
Location: Rome, Italy ; Novi Sad, Srbija; Brisbane, Australia
Distribution: Ubuntu / ITOS2008
Well since Patrick includes only stable programs, and only if its necessary (as to fix a security hole, a bug, etc..) slackware current should be fairly stable. I suggest you wait a bit moe tho, since slackware-current is probably going to become slackware 9.0 in a short while. (Hopefully!)
Slackware-current is usable, but I would strongly discourage it for a production server. Slackware-current is meant to help in the finding of bugs/problems prior to release, perforce it is not going to be as stable as a final release.
For a desktop machine that is non-mission critical or a test server I would say go for it, but expect some problems. If you are not willing to work out the kinks then stick with 8.1.
I am running slackware-current right now on my desktop and I haven't run into any problems yet. Well, that isn't entirely true, but all my problems are in KDE 3.0.9 (aka 3.1RC1) which isn't even in the normal tree, but was included in the extra's directory.
I also noticed I had to make the softlimit of a few daemons I run a bit bigger because of the new libc.
Eitherway, MOST packages in slackware-current are considered stable by the developers. The big change is of course GCC3.2 and glibc 2.3.1.
I noticed that some mirrors are not that current if checked against ftp://ftp.slackware.com ,so I suggest checking a couple of mirrors, ftp://ftp.slackware.com mirror is usually filled up with users and bandwidth is terrible - I was getting dial-up downloads speeds with my DSL. So always double check with main site.