On Wed, Jun 23, 2004, Alexander Belck wrote: Alex,
> I'm trying to build apache for a small ISP. Previosly I relayed on > distribution pre-build/choosen modules (seams to be preety all) and > have no complains of clients. With OpenPkg I must choose by my one, > where I am afraid to let something out that someone could be using. I > tried to build with common options plus nearly all php options, where > apache requires j2se. > please note that OpenPKG creates a statically bound binary. This means that everything you put into your Apache will be loaded for every server process and it will be inherited to every child. Attempting to build a server with all possible bells and whistles will create a huge memory hog. It might be even impossible to create a httpd with_EVERYTHING because some options may lock out each other. If you finally succeed anyway you can be sure to be hit by every possible security problem. I highly recommend you build an Apache that satisfies your (users) needs. Btw, OpenPKG makes it easy to run multiple variants on a single box and maintain each one without disrupting services provided by the others. > But who provides j2se? > There are two packages available providing "Java 2 Platform, Standard Edition". Due to licensing restrictions these are so called nosrc packages which means some important ingredients are missing. Instead instructions are provided enabling you to download the omitted pieces. For these reasons, the packages are not part of a release and must be downloaded from CURRENT [1]. > Also most distros now come with apache-2.x.y. > Why does OpenPkg doesn't provide an new release of apache ? > OpenPKG 2.0 introduced an apache2 PLUS package [2]. PLUS packages are only available in source format. It is my understanding that Unix users experience no real gain preferring apache2 over its predecessor but the threading capabilities cause real pain (i.e. for PHP users). We follow the apache2 development to be ready when the time comes and the life of the original Apache fades out just because everybody heads for the new version and nobody cares, security fixes and enhances the original. As you already pointed out, most Linux distros have already entered that stage. > Can I have php, postfix, perl, etc... from OpenPkg and still use > apache from the underlaying OS ? > You can mix and match OS and multiple OpenPKG intances. Borderlines between them are filesystem pathes, Unix users/groups and IP/port addresses. Obey these borders and use them to interface between the islands, i.e. let a OS app call /openpkg/sbin/sendmail or the OpenPKG Apache/mod_proxy talk to the OS apache2 via localhost ... [1] ftp://ftp.openpkg.org/current/SRC/j2se14-1.4.2.04-20040314.nosrc.rpm [1] ftp://ftp.openpkg.org/current/SRC/j2se-1.3.1-20040608.nosrc.rpm [2] ftp://ftp.openpkg.org/release/2.0/SRC/PLUS/apache2-2.0.48-2.0.0.src.rpm -- [EMAIL PROTECTED], Cable & Wireless ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
