Hi,

Looks good. But I was wondering if the /usr/apache2 directory makes
sense? I mean when apache 3.x comes out, will that mean that we'll have
apache, apache2, and apache3 directories in /usr? I saw with the PSARC
for PHP, the route was /usr/<app>/<version> kinda like how we do Java
and Perl today. Should the apache versions be reorganized to follow
this as well?

Octave

--- Bart Smaalders <bart.smaalders at Sun.COM> wrote:

> I'm sponsoring the attached fast-track for Stefan Teleman.
> The requested binding is patch/micro release, and the
> stability levels are as noted in the document.
> 
> Materials are in the case directory.
> 
> This case times out on 3/28/2007.
> 
> - Bart
> 
> -- 
> Bart Smaalders                        Solaris Kernel Performance
> barts at cyber.eng.sun.com            http://blogs.sun.com/barts
> > Including Apache 2.2.4 with Solaris
> 
> Stefan Teleman <Stefan.Teleman at Sun.COM>
> 15 March 2007
> 
> 1.    Summary and motivation
> 
>       1.1.    Introduction
> 
>       This FastTrack proposes the integration of an updated version of
>       the Apache 2 Web Server [1], Apache 2.2.4. [2]
> 
>       According to the HTTPD Home Page [3], "The Apache HTTP Server
>       Project is proud to announce the release of version 2.2.4 of
>       the Apache HTTP Server ["Apache"]. This version is principally a
>       bugfix release.
> 
>       This version of Apache is a major release and the start of a new
>       stable branch, and represents the best available version of Apache
>       HTTP Server. New features include Smart Filtering, Improved Caching,
>       AJP Proxy, Proxy Load Balancing, Graceful Shutdown support, Large
>       File Support, the Event MPM, and refactored Authentication and
>       Authorization."
> 
>       This FastTrack proposes the integration of the most recent stable
>       release of Apache 2, Apache 2.2.4. In addition to the canonical
> Apache
>       2.2.4 distribution, this FastTrack also proposes the simultaneous
>       integration of distcache 1.4.5 [8], as well as several additional
>       Modules [outlined below].
> 
>       This case also announces the EOL of the Apache 2.0.x APR Interface
>       [with an announcement to take place in a Solaris 10 Update], and
>       EOFs the Apache 2.0.x APR Interface in the next Minor Release of
>       Solaris.
> 
>       This case seeks Minor Release Binding.
> 
>       1.2.    Previous Relevant ARC Cases
> 
>       PSARC 2004/676          Apache 2.x.x in Solaris
>       PSARC 2004/278          GSSAPI auth for Apache
>       PSARC 2001/266          Addition of Jakarta Tomcat for Apache
>       PSARC 2001/244          Apache moving to SFW Consolidation
>       PSARC 2000/040          Java Servlet Support in Apache
>       PSARC 1999/542          Apache for Solaris
>       PSARC/1998/138          Kerberos V5 clients and PAM module
>       PSARC/1996/060          GSS-KRB5 (Kerberos V5 GSS-API mechanism)
> 
> 2.    Technical issues
> 
>       2.1.    Key objects
> 
>       The Solaris Apache 2 distribution installs objects under three
>       distinct directory hierarchies: /usr/apache2, /etc/apache2 and
>       /var/apache2.
> 
>       /usr/apache2/bin/apr-1-config
>       /usr/apache2/bin/apu-1-config
>       /usr/apache2/bin/dc_client
>       /usr/apache2/bin/dc_server
>       /usr/apache2/bin/dc_snoop
>       /usr/apache2/bin/dc_test
>       /usr/apache2/bin/nal_test
>       /usr/apache2/bin/piper
>       /usr/apache2/bin/sslswamp
> 
>       /usr/apache2/bin/ab
>       /usr/apache2/bin/apachectl
>       /usr/apache2/bin/apxs
>       /usr/apache2/bin/checkgid
>       /usr/apache2/bin/dbmmanage
>       /usr/apache2/bin/envvars
>       /usr/apache2/bin/envvars-std
>       /usr/apache2/bin/htcacheclean
>       /usr/apache2/bin/htdbm
>       /usr/apache2/bin/htdigest
>       /usr/apache2/bin/htpasswd
>       /usr/apache2/bin/httpd
>       /usr/apache2/bin/httxt2dbm
>       /usr/apache2/bin/logresolve
>       /usr/apache2/bin/rotatelogs
>       /usr/apache2/bin/suexec.disabled
> 
>       /usr/apache2/lib/apr.exp
>       /usr/apache2/lib/aprutil.exp
>       /usr/apache2/lib/libapr-1.so.0.2.8
>       /usr/apache2/lib/libapr-1.so -> libapr-1.so.0.2.8
>       /usr/apache2/lib/libapr-1.so.0 -> libapr-1.so.0.2.8
>       /usr/apache2/lib/libaprutil-1.so.0.2.8
>       /usr/apache2/lib/libaprutil-1.so.0 -> libaprutil-1.so.0.2.8
>       /usr/apache2/lib/libaprutil-1.so -> libaprutil-1.so.0.2.8
>       /usr/apache2/lib/libdistcache.so.1.0.1
>       /usr/apache2/lib/libdistcache.so.1 -> libdistcache.so.1.0.1
>       /usr/apache2/lib/libdistcache.so -> libdistcache.so.1.0.1
>       /usr/apache2/lib/libdistcacheserver.so.1.0.1
>       /usr/apache2/lib/libdistcacheserver.so.1 ->
> libdistcacheserver.so.1.0.1
>       /usr/apache2/lib/libdistcacheserver.so ->
> libdistcacheserver.so.1.0.1
>       /usr/apache2/lib/libnal.so.1.0.1
>       /usr/apache2/lib/libnal.so.1 -> libnal.so.1.0.1
>       /usr/apache2/lib/libnal.so -> libnal.so.1.0.1
> 
>       /etc/apache2/httpd.conf-example
>       /etc/apache2/extra/httpd-autoindex.conf-example
>       /etc/apache2/extra/httpd-dav.conf-example
>       /etc/apache2/extra/httpd-default.conf-example
>       /etc/apache2/extra/httpd-info.conf-example
>       /etc/apache2/extra/httpd-java.conf-example
>       /etc/apache2/extra/httpd-languages.conf-example
>       /etc/apache2/extra/httpd-manual.conf-example
>       /etc/apache2/extra/httpd-mpm.conf-example
>       /etc/apache2/extra/httpd-multilang-errordoc.conf-example
>       /etc/apache2/extra/httpd-proxy.conf-example
>       /etc/apache2/extra/httpd-security.conf-example
>       /etc/apache2/extra/httpd-ssl.conf-example
>       /etc/apache2/extra/httpd-userdir.conf-example
>       /etc/apache2/extra/httpd-vhosts.conf-example
> 
>       /usr/apache2/man/man1/
>       /usr/apache2/man/man3/
>       /usr/apache2/man/man8/
>       /usr/apache2/manual/
> 
>       2.2.    API and ABI compatibility
> 
>       The Apache 2.2.x Module API/ABI is NOT binary compatible with the
>       Apache 2.0.x Module API/ABI:
> 
>       "Add-in modules for Apache 1.3 or 2.0 are not compatible with
>       Apache 2.2. If you are running third party add-in modules, you
>       must obtain modules compiled or updated for Apache 2.2 from that
>       third party, before you attempt to upgrade from these previous
>       versions. Modules compiled for Apache 2.2 should continue to work
>       for all 2.2.x releases." [4]
> 
>       Simply put, upgrading from Apache 2.0.x to Apache 2.2.x will break
>       existing Apache 2.0.x applications which have installed third party
>       Apache Modules. Extensive Release Notes detailing the consequences
> of
>       this breakage will be included with this new Integration. The
> original
>       ARC Case for Apache2 [PSARC 2004/676] proposed Standard
> Classification
>       Stability Level for the APR Interface. It was not possible to
> foresee,
>       at that time, that the APR Interface for Apache 2.2.x would become
> API
>       and ABI incompatible with the Apache 2.0.x APR Interface. [4]
> 
>       In this FastTrack, we propose re-classifying the Commitment Level of
>       the APR Interface, and re-classifying it as Uncommitted. A Release
>       Note will be submitted for the Solaris Updates documenting that the
>       APR interface may change incompatibily in a subsequent release of
>       Solaris; in addition, a Release Note will be filed in that
> subsequent
>       release [aka Nevada] indicating that the interface had changed, and
>       that third-party modules will need to be recompiled and potentially
>       changed.
> 
>       2.3.    Request Handling MPM compatibility
> 
>       In addition to the APR API and ABI compatibility breakage outlined
>       above, the currently proposed Apache upgrade promotes a significant
>       and binary incompatible change in the request handling mechanism.
>       Apache 2.0.x was delivered with the prefork-mpm request handler.
>       The currently proposed integration changes the request handler
>       model to the worker-mpm.  This change introduces an Apache Module
>       ABI incompatibility: the worker-mpm assumes that all Apache Modules
>       have been written thread-safe [thread-safety refers to the actual
>       programmatic implementation of the respective modules, and is not
>       limited to run-time binding to reentrant interfaces]. Apache
>       Modules not written with concern for thread-safety will break at
>       runtime. Extensive Release Notes detailing the possiblity of
> breakage
>       will be included with this new Integration.
> 
>       2.4.    Packaging and Delivery
> 
>       The current integration proposal does NOT allow for the inclusion
> and
>       coexistence of multiple versions of Apache 2.x.x. Installing Apache
>       2.2.4 will overwrite the existing Apache 2.0.x installation [with
> the
>       exception of the configuration files located under /etc/apache2,
> which
>       will be preserved].
> 
>       This FastTrack proposes to maintain the existing Apache 2.0.x
>       packaging structure: 
> 
>               SUNWapch2r      Apache Web Server V2 [root]
>               SUNWapch2u      Apache Web Server V2 [usr]
>               SUNWapch2d      Apache Web Server V2 [Documentation]
> 
> 3.    Apache 2 Modules
> 
>       Just as the previous versions of Apache, Apache 2.2.x supports
>       dynamically loadable modules. This integration will include all
>       the modules provided by the Apache canonical distribution. In
> 
=== message truncated ===>
_______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc at opensolaris.org


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Systems Engineer
http://www.opensolaris.org/os/community/sysadmin/
http://unixconsole.blogspot.com
unixconsole at yahoo.com
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


 
____________________________________________________________________________________
Don't get soaked.  Take a quick peek at the forecast
with the Yahoo! Search weather shortcut.
http://tools.search.yahoo.com/shortcuts/#loc_weather

Reply via email to