These scripts are for use on Slackware 12.0 and Slackware 12.1. Also, I am primarily a web developer and run web and mail servers (on Slackware Linux) as something of a hobby. I need my servers to be safe, secure, and reliable and I also need to be able to build them quickly. Therefore, I've developed some scripts to help me out.... The point is, I'm no Linux guru - these things could likely be more elegant, etc. but they work great....

A few notes:

• You need to have some familiarty with Linux and Slackware (the installation is a bit quirky) or all of this is meaningless (well....obviously).
  
• For the LAMP server you need to know how to configure Apache and Webalizer (using Webalizer is optional, anyway). The mail server requires a lot of background and I talk about that a bit further down this list.....
  
• You need to run these on a fresh, full install of Slackware.
  
• The scripts are brain-dead; the LAMP server has two scripts (labeled "1.script" and "2.script") which you just run consecutively. The mail scripts - which must be run after the LAMP install - have 5 scripts which you run the same way.
  
• These LAMP scripts throw some simple, dumb scripts to /root to start and stop Apache. generate webalizer reports, etc.
  
• The mail scripts are something that you should not even screw around with unless you have run a mail server before. They grew out of the Qmailrocks tutorial and, again, if you have not run a mail server before you will not know what the hell you are doing. Also, while it includes some updated packages it does not include all of the most current packages nor patches. So (1) downloading this is pointless unless you really have some experience with a mail server, and, (2) if you choose to download this you might want to update some patches, yourself. Although it's denounced all over the net by serious IT people, if you want to get some general insight into running a mail server (and these scripts) take a look at the Qmailrocks tutorial. Even better, go grab a copy of "Life With Qmail" (or something similar), read it, and you'll really know what you're doing....
  

Both of these LAMP scripts install older versions of Apache (versions 1.3.37 and 1.3.41). If you need version 2.x, I dunno what to tell ya..... I'm constantly downloading and experimenting with new open source, web packages and I've run into one - period - that absolutely required Apache 2.x. I don't even recall what it was called. I just haven't found a really pressing need to upgrade to Apache 2.x.

Why are some of the packages redundant?

If you do a full install of Slackware a lot of these things are already installed. However, using these scripts is the only way that I could always get everything working together, know what was going on, etc. Go figure.

Another quirk....

Also, I had installed some nifty open source packages (eg. Boonex Dolphin) and the only way that I could get PHP to work with XSLT (which a couple of such packages needed) was to compile PHP, do a make clean, and recompile with different arguments. Again - go figure. Is there a better way to do this? Probably...but nothing gets broken. Apache is compiled to work with open ssl, etc. - it's a great little package, if I do say so myself!

All I know is this: do a fresh, full install of one of these versions of Slackware, run these scripts as directed, and everything works famously. You can run Boonex Dolphin and install 99% of the popular open source PHP/MySQL packages (Wordpress, Joomla, etc.).....

LAMP SERVER SLACKWARE 12.0

Lamp Server for Slack 12.0

ALL PACKAGES:

The packages in this tarball are virtually identical to those for Slack 12.1 (see list, below) with the following exceptions:

openssl-0.9.8a.tar (as opposed to openssl-0.9.8k.tar)
apache 1.3.37 (as opposed to apache 1.3.41)

LAMP SERVER SLACKWARE 12.1

Lamp Server Updated for Slack 12.1 (APACHE 1.3.41)

ALL PACKAGES:

mod_perl-1.30
mod_ssl-2.8.31-1.3.41
openssl-0.9.8k.tar.gz
php-5.2.6
phpMyAdmin-3.1.0
libmcrypt-2.5.8
php-5.2.6
Sablot-0.71
expat-1.95.2
apache_1.3.41
mysql-5.0.67-linux-i686-icc-glibc23
mcrypt-2.6.8
vsftpd-2.0.3 with tcp_wrappers, a crazy banner, and my own configuration
Webalizer and the gd, jpeg, and freetype libraries (redundant, I know)

WARNING: I can think of about 100 reasons why downloading/using this tarball is probably not a great idea for a whole lot of people.

As I mentioned at the top of this page you are really going to need some prior experience with a mail server to get this working worth a damn.

Some issues:

• The httpd.conf file gets overwritten with one of my domains - not a big deal and you could use it to get everything working. But it might confuse people who never done a mail server install.
• The script password protects Vqadmin with my own .htaccess file - you'll need to know how to generate your own...
• You will need to edit the /var/qmail/supervise/qmail-smtpd/run - and pop3 run files - with the FQDN of your mail server. Again, this ain't much but if you're totally new at all of this you're simply going to have a mess on your hands...
• You will need to edit the SMTProutes in Vqadmin so as to link to well-known smtp server. Otherwise many large servers will reject your mail. You'll need an ISP that allows you to link to their SMTP server, or, a "for pay" service. By the way, you edit the SMTProutes file by adding the IP of the linked smtp server preceded by a colon (eg, :79.119.89.20).
• This install includes a line in the smtpd-run file to check emails against a list of spam IPs from spamhaus.org. Some people don't like to use this as, conceivably, it could block a legitimate email (highly unlikely!)
• If your linking to an extrenal SMTP server I suggest that you create an account on the order of ' This e-mail address is being protected from spambots. You need JavaScript enabled to view it ' and edit the .qmail-default files so that they send emails there as opposed to the default bounce (the last portion of the line should simply read "" This e-mail address is being protected from spambots. You need JavaScript enabled to view it ). Otherwise, you could be bouncing a shitload of emails through your ISPs server (Comcast, which I have, is fine with linking to their server but the default qmail config files got me cut off for awhile when I didn't realize I was, essentially, sending thousands of emails a week through their SMTP server). That was before I added the Spamhaus filter, and, Qtrap.

Bottom line: this is based upon the Qmailrocks.org Guide and - while it's roundly criticized on the net for being out of date (justifiably) - you would be better off, at least, starting there if you've never messed with a mail server before.

I used to have a lot of issues with portions of this thing - this one includes the most recent Clamav release (as of November 16th, 2009) and works fine - just read the directions.......

MAIL SERVER SCRIPT (Slackware 12.0 & 12.1)

QMAIL_CLAMAV_95

UNTESTED QMAIL TOASTER SCRIPT (Slackware 11.0, 12.0 & 12.1)

There's a guy named Fritz on the Qmailrocks forum. he's developed some scripts to build a Qmail toaster. I have no idea if these work, but, they contain some enhancments and updates to my scripts.....

Qmail Toaster by "Fritz"(???)