SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've heard people say that using a beta distro-release such as Slackware-current is a bad idea. But I always thought that the new packages that were added to the tree were stable to begin with. It's just that <that guy who releases all the slackware releases, can't remember name> didn't want to call it a new version yet.
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
My understanding of Slackware-current is that Patrick is still working
on getting everything integrated. It's unstable because at any time
any package may be missing dependencies, only half installed, or
any number of other problems. Sure, the packages are stable
releases, but the entire conglomeration of them isn't necessarily
stable. Putting together a linux distribution isn't as easy as slapping
a bunch of packages together on a disk -- check out Linux From
Scratch. . .
Slackware-current is the development branch of the distribution. For the most part things will work under current, but it is still being tested for stability. Look through the change logs , say the last 5-10 entries in current, and you should understand what I mean. As an example there WERE (are?) some problems with the new RPM binaries so they had to be regressed a few versions. If you happened to be using current before this was fixed and needed to use RPM...
Overall current is fine for a tinkerer or someone who wants to test/help make the new release of Slackware stable. But it is absolutely not for production server use, IMHO not production workstation use either. Not to say current is crash happy, but it has quirks, and quirks are not good for 24/7 servers.
Iīve been using slack-current for almost 3 months now (almost since it got out). Iīve yet to see any problem...
The box is running 24/7 ssh, http, ftp, pop and smtp servers and used as a worksation almost every day, and i still havenīt witnessed any problem due to it being an "unstable" release..
The only real problem i see, is that it is built on the new gcc, therefore many or most of the .tgz slack package (which are built on the old gcc) will not work or have problems.
If can live happily building every software you need then you will probably be just fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.