Slackware as a server OS?
 

I will be setting up a server to run a LAMP application in a business environment. The database is not huge, less than 1GB of data. There are only a dozen or so users, and there is not a lot of traffic nor is there heavy usage. The application is not available from the internet, but is for internal usage only. It is, however, mission critical, and we need up-time approaching 100%.

We've been using Ubuntu, and I don't want to bash Ubuntu so I'll keep to myself the things about it that annoy me. Suffice to say that we are considering using Slackware to host the app.

Are there any reasons why Slackware would *not* be a good choice for this? And are there any settings/tweaks that would be recommended to increase reliability or performance?

I've used Slackware since version 9. My first post to these forums was 4/4/2004 (seriously - 4 April 2004 lol 4/4/4 I just now noticed that)(dang, has it really been that long???). Today I use it as my development and testing box for this application, and it is 100% rock solid. I'm using fairly current version of apache, mysql, and php, and they are all 100% rock solid.

So, having said all that, how well suited would you consider Slackware as the OS to host a mission critical LAMP application?

Yes.

I think you answered your own question. ;)

Six topics down the index page (at the moment),

http://www.linuxquestions.org/questi...er-4175477005/

In my brain, Slackware is a server OS :)

Desktop, Laptop, and Server OS.

Slackware is for everything.

Absolutely. 133.7% server OS Slackware is.

Regards.

Slackware is all.
It is my girlfriend.

Of course -- been running a Slackware box doing exactly that for some years (installing updates as they come along, releases as they come along, total downtime about 30 minutes and back up and running after a release installation). Same box serves CVS and Bugzilla, no runs, no drips, no errors.

At home I've got two Dell Dimension 8400's (dating from 2004) that sit in a closet mumbling to themselves serving up data bases (MySQL on one and PostgreSQL on the other). LAMP? Oh, yes. They came with Win XP (which went bye-bye after first boot to make sure they worked), nothing but Slackware ever since. They typically run for as long as it takes for a new stable Slackware release to become available, don't get rebooted, don't crash, don't stop, just do what servers are supposed to do.

I'm in the process of building two Dell PowerEdge T110 II servers for a non-profit institute that will be running DSpace (it's a Java collection management system). Slackware, of course.

For me it's not a question, it's a given.

Hope this helps some.

Slackware is the answer.
What's the question?

Slackware or FreeBSD are really the only choices if you believe that simplicity is important for security. LAMP is easier to setup on Slackware than on FreeBSD if you have a full install of the a ap d l n x series (x probably not necessary - there may be a library in there needed by something and there is no reason not to install it). Mr Goblin has a good tutorial at http://www.slackware.com/~mrgoblin/slackware-lamp.php

Great information, thanks all!

I don't use the versions of apache/mysql/php that come with Slackware, I'm keeping the bleeding edge versions on until we go into testing - then I lock down the versions. But compiling and configuring the versions I want is a breeze. Well, figuring out the PHP configure options was a serious pain in the arse, but once you get it right the process goes quickly. I can remove the versions that come with slack, compile and configure my versions, dump my database and web content onto the box, and we are up and running in less than an hour.

We were using Ubuntu, and I don't want to start a bash-fest, but let's just say that I was less than satisfied with it. I'll take Slack any day.

Here's all you need to know:

http://docs.slackware.com

And here too:

http://www.microlinux.fr/slackware/Linux-HOWTOs

Cheers,

Niki