SV: Defining ISP?
Is it possible to define with some accuracy the needs of ISPs? Some list of all the components in a Debian that are absolutely necessary for the ISP work. Is it possible to compose a custom ISP Debian? or I.e compose your own debian-distribution? I'd install base-system and dpkg --get-selections my-needs /Chris custom ISP debians (different flavours: mail specific, routage-specific, hosting, db etc...) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Defining ISP?
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]
Re: Defining ISP?
Well, it seems to be the best method. But isn't it possible to define a general list of necessary packages used by ISPs and regroup the whole in a minimalistic optimized distribution specificly made for ISP use? And excluding all other packages (desktop, non-necessary libraries, windowing etc...). It's even possible to integrate some optimization tools (apt-build) and automatize some installation jobs At my actual knowledge, such a distribution doesn't exist. Should it be interesting or is it only the remanent effects of a very good long week-end? :) BR shift - Original Message - From: Jonathan G - Mailing Lists [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, September 14, 2004 3:39 PM Subject: Re: Defining ISP? 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] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Defining ISP?
yep shift, is what i've done. I've been playing with apt-get and apt-cache in order to discover all minimal dependencies por a serie of packages. My procedure is the following: 1. NetInstall or Minimal install using CD1 from Woody 2. Minimal Config 3. Change apt-sources, changing stable for sarge 3. apt-get update 4. apt-get distro-upgrade At this step my system is converted from 3.0 Woody to 3.1 Sarge. Starting from sarge now i star the installation of groups of packages. Suppouse that i want to install in a unique box a web, smtp, pop3, imap4, ftp, database and dns server. I have the same config files as servers i want to install. I have in a file the list of packages for server needed. From console i launch a batch process calling those files. In about 15' i have a whole system installed. About the configuration, of course, i have done the config once and then i only copy files from a repository and fix some permission issues on files, but all documented fine. This is my way! BR, jonathan shift wrote: Well, it seems to be the best method. But isn't it possible to define a general list of necessary packages used by ISPs and regroup the whole in a minimalistic optimized distribution specificly made for ISP use? And excluding all other packages (desktop, non-necessary libraries, windowing etc...). It's even possible to integrate some optimization tools (apt-build) and automatize some installation jobs At my actual knowledge, such a distribution doesn't exist. Should it be interesting or is it only the remanent effects of a very good long week-end? :) BR shift - Original Message - From: Jonathan G - Mailing Lists [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, September 14, 2004 3:39 PM Subject: Re: Defining ISP? 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] -- Jonathan Gonzalez Fernandez (o mail : [EMAIL PROTECTED] //\ jabber: [EMAIL PROTECTED] V_/ site : www.surestorm.com ::: Registered Linux User #86 ::: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Defining ISP?
About this. (comments in line) shift wrote: At my actual knowledge, such a distribution doesn't exist. Should it be interesting or is it only the remanent effects of a very good long week-end? i'm quite interested. :) jonathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Defining ISP?
Well, about the week-end, you're welcome for another one (...) About the install, I do almost the same. the second part is the optimization. Using an optimized distrib on an SR2200 (dual PIII 1.4GHz Tualatin-S), SCSI U160, I have better results on Mysql nemchmarks than with a non-optimized SR2300-SKU0 dual xeon 3.0 1MB L3 cache and SCSI U320!! - Original Message - From: Jonathan G [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, September 14, 2004 5:14 PM Subject: Re: Defining ISP? yep shift, is what i've done. I've been playing with apt-get and apt-cache in order to discover all minimal dependencies por a serie of packages. My procedure is the following: 1. NetInstall or Minimal install using CD1 from Woody 2. Minimal Config 3. Change apt-sources, changing stable for sarge 3. apt-get update 4. apt-get distro-upgrade At this step my system is converted from 3.0 Woody to 3.1 Sarge. Starting from sarge now i star the installation of groups of packages. Suppouse that i want to install in a unique box a web, smtp, pop3, imap4, ftp, database and dns server. I have the same config files as servers i want to install. I have in a file the list of packages for server needed. From console i launch a batch process calling those files. In about 15' i have a whole system installed. About the configuration, of course, i have done the config once and then i only copy files from a repository and fix some permission issues on files, but all documented fine. This is my way! BR, jonathan shift wrote: Well, it seems to be the best method. But isn't it possible to define a general list of necessary packages used by ISPs and regroup the whole in a minimalistic optimized distribution specificly made for ISP use? And excluding all other packages (desktop, non-necessary libraries, windowing etc...). It's even possible to integrate some optimization tools (apt-build) and automatize some installation jobs At my actual knowledge, such a distribution doesn't exist. Should it be interesting or is it only the remanent effects of a very good long week-end? :) BR shift - Original Message - From: Jonathan G - Mailing Lists [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, September 14, 2004 3:39 PM Subject: Re: Defining ISP? 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] -- Jonathan Gonzalez Fernandez (o mail : [EMAIL PROTECTED] //\ jabber: [EMAIL PROTECTED] V_/ site : www.surestorm.com ::: Registered Linux User #86 ::: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Defining ISP?
Hello On 2004-09-14 shift wrote: Using an optimized distrib on an SR2200 (dual PIII 1.4GHz Tualatin-S), SCSI U160, I have better results on Mysql nemchmarks than with a non-optimized SR2300-SKU0 dual xeon 3.0 1MB L3 cache and SCSI U320!! Sounds very unrealistic. Are you sure that it wasn't just a question of how much memory was available, using a different MySQL config or chosing the right kernel so that the dual procs were actually detected etc? bye, -christian- pgpTwzk64JGg3.pgp Description: PGP signature
UNDELIVERED (was Re: Re: Thanks!)
Dear Netflix User, Your email has reached an automated mailbox. Email sent to this address does not reach our Customer Service team and will not receive a personal response. If you have a question you need answered right away, please visit our online Help Center at http://www.netflix.com/Help. It covers a wide variety of commonly asked questions. If you need to contact a customer service representative please visit http://www.netflix.com/ContactCustService. Thanks for contacting Netflix. Sincerely, Your Friends at Netflix
Re: Defining ISP?
On Tue, 14 Sep 2004 17:14:02 +0200, Jonathan wrote in message [EMAIL PROTECTED]: 4. apt-get distro-upgrade ..you meant dist-upgrade, or is distro-upgrade different from apt-get dist-upgrade??? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Defining ISP?
Oh no, was a typo, is dist-upgrade :) thanks for the note BR, jonthan Arnt Karlsen wrote: On Tue, 14 Sep 2004 17:14:02 +0200, Jonathan wrote in message [EMAIL PROTECTED]: 4. apt-get distro-upgrade ..you meant dist-upgrade, or is distro-upgrade different from apt-get dist-upgrade??? -- Jonathan Gonzalez Fernandez (o mail : [EMAIL PROTECTED] //\ jabber: [EMAIL PROTECTED] V_/ site : www.surestorm.com ::: Registered Linux User #86 ::: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Defining ISP?
-Original Message- From: shift [mailto:[EMAIL PROTECTED] Sent: Wednesday, 15 September 2004 4:13 AM To: [EMAIL PROTECTED] Subject: Defining ISP? Hej till alla Is it possible to define with some accuracy the needs of ISPs? Some list of all the components in a Debian that are absolutely necessary for the ISP work. Is it possible to compose a custom ISP Debian? or custom ISP debians (different flavours: mail specific, routage-specific, hosting, db etc...) There are a lot of ways to go about this. I do a bit of research and build my own boot CD depending on hardware requirements. It has an update-to-date kernel with the support you need for various bits of hardware compiled into it. I've usually rolled my own packages from scratch and grouped them depending on function into a larger meta package. An example... I did some contracting for a service provider about 7 months ago. One of the main things they wanted was the ability to deploy new servers that can conform to their standards quickly. I had a base-conform package that pulled down customised packages that were preconfigured (pam, nfs, sudo and others) and removed a lot of crud it didn't need. Depending on what the function of the machine I then did the same sort of deal for that... so mail-server, name-server, samba-server, radius-server, etc. The mail-server meta package pulled down a version of postfix with all the usual extras (clamav, amavis, spamassasin, auth via LDAP, etc.) The post install scripts finished off the rest of the configuration by asking a few questions that it needed to know about. This is a double-edged sword though... you usually take a hit in the ease of upgrade later on. Last I heard they have an administrator who speaks good Debian and he works with it pretty well so it worked out well in the end. Once you start getting larger you might want to investigate using cfengine or something similar for large deployments and making them conform to whatever they are meant to be doing. mvh shift -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]