Basically, i think Slackers got their own tips in order to configure the system. Of course admins can just install and run a pure server machine behind a firewall, running ftp, http, sql, nfs etc...
I got mine too. Here's my philosophy:
-I don't want to change anything to the stable version i installed. It means i don't replace any original Slackware package. That's why i don't use dropline, even freerock or optimized linuxpackages.net.
Slack is "perfect" and i'll be crazy to touch anything.
---BUT i can change the configuration. I change the language, disable the beeps, add the famous mouse zaxismapping to xorg.conf and some other things (like desktop preferences). I did this after every install. So i take the original config files, modify them, then i put them in a .tgz, in their right directories. I add other stuff too:
This is a "basic" customization. But i also need some "basic" useful programs, like xbindkeys, checkinstall, kde-i18n-fr...
I called this package def-pack-base.tgz.
No need to edit manually any file after each install.
At this point i added just a few non-Slack programs. Just the vital ones.
Now i have a standard ready to use stable Slackware.
That's where the fun begins:
---We all need more: blender for 3D makers, audacity for audio people, Open Office for almost everyone, aMule
, games, etc...
Here comes the all-you-ever-need def-pack-bonus.tgz.
Now i have a Super Slackware System. 3S
. I like this name Shilo, and i'll put a patent on it then you'll give me money
That's fun because i choosen The Super Shinobi as my pack's symbol.
So that's my cooking and i'm sure many other people have a similar way to proceed. I reached a point where users don't phone me when i install it on their PC. But it's still perfectible.
I insist on the fact that i don't want to make a new Slackware-based distro.
I use Slackware.