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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
How far you push slackware for your server ?
My home server, which holds dns, dhcp, proxy, mysql, postgresql, apache, nginx, git, mercurial, zabbix, network bandwidth monitoring, is working great.
Although, i don't know the stability since the load not quite high.
Running on C2D E4400, 4Gb of RAM, headless without X.
My current longest 'uptime' for a server is 558 days, and it's still running. last night my companies backup server hit a load average of over 20 for a sustained 2 hours solid (but it is a 24 core server :-).
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
I had one data base server running for 1-1/2 year (before the power went off for too long and the UPS shut it down). Just sits in a closest mumbling to itself and its next door neighbor, another data base server. I'm putting together two new data base servers (Dell, quad-core, 16G RAM, 2 500G drives each) that will be Slackware 14.0 (stable). I expect them to run 24/7 for a long, long time; they're going to be running DSpace, managing large collections. They aren't mine, but I'm going to be administering them and ain't nothing going to ever touch those machines but Slackware.
Had a few Slackware servers in a (primarily) Sun shop -- never a lick of problems with them, just sat there doing their thing and never bothering anybody (as far as I know, they're still running after 10 years, with updates, of course).
The better question might be, what can't you do with Slackware.
On the negative side, if you want to use LDAP, you will need LDAP-enabled applications or the ability to use LDAP gateways. While LDAP usage should only increase, currently there are not very many LDAP-enabled applications available for Linux. Also, while LDAP does support some access control, it does not possess as many security features as X.500.
Might be a little out-of-date, but whenever I've had to use it it turned in the Royal PITA.
Stability under fire is one of the most important characteristics in a system, to me, and of all the server operating systems I've used in production, Slackware has proven the most stable.
My personal server (a Slackware 13.1 system) has been horribly abused and neglected by myself and its other users, and had about 780 days of uptime when the hosting company powered it down to move it to Fremont last weekend. It showed no signs of sickening, as some other distributions are prone to do.
There have been "bad" Slackware releases, from a stability perspective, but on the most part they've been really good. 13.1 and 14.0 both seem well-suited to any server use. I cannot attest to 13.37 because I have not used it.
Push it as hard as you need. If it breaks, no other operating system would have done any better (and most would have broken sooner).
There have been "bad" Slackware releases, from a stability perspective
Ye shalt be committed as follows...
The accused shall be, henceforth: tarred, feathered, hanged by the feet, fed lima beans, made to stand on his head in the rain, tied to the hood of Patrick's car, and finally made to drink a full bottle of castor oil and syrup of ipecac, and spend one day in the pillory as pies are thrown at thine face.