Hi,
what i used to do is install a base system and then install some of the package packs i've defined.
For example, if what i want is install a web server with php % perl support i use a config file what i've defined myself which contains this:
apt-get install apache2-common apache2-mpm-prefork libapache2-mod-auth-mysql libapache2-mod-perl2 php4-common libmailtools-perl libhtml-format-perl bzip2 file libio-socket-ssl-perl ca-certificates libapache2-mod-php4 php4-mysql php4-pear
For the rest of services exactly the same. I'v defined manually the whole list of packages needed for web server, ftp server, irc server, mail server (smtp, pop and imap), antivirus server, etc...
If you can build a local mirror of you version of debian, i.e. sarge, you can do local network installations, and your installs will be so fast.
That work fine for me at least :)
BR,
jonathan
Christian Hammers wrote:
On 2004-09-14 shift wrote:
Thinking maybe of a an ISP specific install. Lighter and even more secure. A minimalistic distribution...
Most ISP will probably have different servers for the different services and on each of them they will start with a secure base install with as few software installed as possible and then just install apache/postfix/proftpd whatever they need and customize it.
I don't see a big bonus in a special ISP distribution. A better integration of iptables firewalls, vlans or traffic shapers would be nice but that's nothing ISP specific.
bye,
-christian-
P.S.: pbuilder is a nice tool to build minimal installations that you can just untar onto a new harddisk
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
