From jyri@sac.sfbay.sun.com Mon Mar 10 23:40:06 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2B6e5xx006792 for ; Mon, 10 Mar 2008 23:40:05 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m2B6e1ih005013; Mon, 10 Mar 2008 23:40:05 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXJ00D0FZUTEX00@brm-avmta-1.central.sun.com>; Tue, 11 Mar 2008 00:40:05 -0600 (MDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXJ00JL7ZUSVM80@brm-avmta-1.central.sun.com>; Tue, 11 Mar 2008 00:40:04 -0600 (MDT) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2B6e3DG018078; Mon, 10 Mar 2008 23:40:03 -0700 (PDT) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2B6P2wR006602; Mon, 10 Mar 2008 23:25:02 -0700 (PDT) Received: (from jyri@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id m2B6P2EG006598; Mon, 10 Mar 2008 23:25:02 -0700 (PDT) Date: Mon, 10 Mar 2008 23:25:02 -0700 (PDT) From: Jyri Virkki Subject: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] To: lsarc-ext@sun.com Cc: Amanda.Waite@sun.com, webstack-discuss@opensolaris.org Message-id: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 17130 I am sponsoring this case for Amanda Waite. Timeout set to 3/18. Case materials below and in the case directory. Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Deliver Lighttpd 1.4.x into OpenSolaris 1.2. Name of Document Author/Supplier: Author: Amanda Waite 1.3 Date of This Document: 10 March, 2008 4. Technical Description Deliver Lighttpd 1.4.x into OpenSolaris 10 March 2008 1. Summary and motivation 1.1. Introduction This project delivers Lighttpd 1.4.x into OpenSolaris Lighttpd is an Open Source Web Server that currently enjoys 4th position in the Netcraft rankings of Market Share for Top Servers across all domains. Lighttpd became popular on the back of The Ruby on Rails take-off in 2006. Much of it's popularity stems from it being extremely lightweight, hence the name. Lighttpd supports both PHP and Ruby on Rails through FastCGI For more information about Lighttpd see: http://lighttpd.net Lighttpd is a key component of an integrated Ruby on Rails stack which would include Ruby, Ruby on Rails, FastCGI, the fcgi Ruby Gem and an Open Source Database (MySQL, SQLlite and Postgres are all options here) This case seeks Minor Release Binding. 2. Technical issues 2.1. Key objects /usr/lighttpd/1.4/sbin/lighttpd /usr/lighttpd/1.4/bin/spawn-fcgi /usr/lighttpd/1.4/lib/mod_*.so /etc/lighttpd/1.4/lighttpd.conf /var/lighttpd/1.4/docroot 2.2. Versioning The versioning model for Lighttpd is ... The compatibility expectations for Lighttpd are as follows: (1) Version x.y.z is compatible for different values of z, such that z >= 0. (2) Version x.y.z is not expected to be compatible for different values of x or y At the time of writing the latest version of Lighttpd is 1.4.18, a lot of work is going into 1.5.x but given that most Lighttpd deployments are on 1.4.x, we are not considering 1.5.x at this time. We are however making provision for 1.5.x by versioning this integration as lighttpd14. 2.3 Loadable Modules Lighttpd ships with a number of loadable modules which are enabled through directives in the config file. Some of these modules have library dependencies that must be satisfied through build time package options (supplied to the configure script). An example is mod_magnet.so which has a dependency on the libraries for the Lua programming language. The module gets built even if the external library dependencies are not satisfied and is effectively a "stub" library. If such a module is enabled at runtime through the lighttpd config file, lighttpd will dlopen() the stub library but will fail when it calls dlsym() on that library. It's not clear why this was done but as the behavior and errors generated by such a scenario are well documented it's proposed that any such stub libraries be left in the distribution. Currently two modules are affected. One is mod_cml and the other is mod_magnet. mod_magnet is the replacement for mod_cml. Attempts to include LDAP support with the authentication module mod_auth.so failed due to Lighttpd's use of OpenLDAP extensions not documented in the internet draft LDAP C-API document. This case defers inclusion of the LDAP support to a future project. 2.4 Directory Naming and Structure The proposed directory layout for Lighttpd is: /usr/lighttpd/1.4 /sbin /bin /lib /etc/lighttpd/1.4 /conf.d /var/lighttpd/1.4 /docroot /logs 2.5 Users and Groups Binary distributions of Lighttpd generally include a default config file. In this file, as with the likes of Apache, the user and group name under which to run Lighttpd are specified. The most common practice for user and group in the various binary distros is to use generic web/www related names such as www-run, www-data or webservd. It's understood at this time that it is not possible to deliver a new user or group into Solaris via a package install so the proposed user name and group is webservd:webservd 2.6 Configuration File This project will use the standard convention and deliver configuration files under /etc/lighttpd/1.4 The default configuration file provided with this integration should work out of the box and should therefore avoid relying on any dependent packages, particularly FastCGI. In addition, a directory conf.d will be created in /etc/lighttpd/1.4 This directory will be used for module/directive-specific configuration files and configuration files for virtual hosts. These are added to the main configuration file using the include directive. For this integration conf.d will contain configuration files for SSL and fastcgi. 2.7 Docroot and Log Files The Document Root for Lighttpd will be located in /var/lighttpd/1.4/docroot and will include a welcome file. Lighttpd source distributions do not include such a file so one will need to be created (index.html). This would be similar to the one supplied with Apache. Log Files will be located in /var/lighttpd/1.4/logs and will be named access.log and error.log. This directory will also include the run.pid file. /var/lighttpd/1.4 and it's files and sub directories will be owned by webservd:webservd 2.8 SMF and RBAC support On OpenSolaris, the public interface to Lighttpd will be SMF and the Lighttpd SMF service for this versions will be named: svc:/network/http:lighttpd14 This was chosen to avoid confusion should multiple versions of Lighttpd be installed on the system and is consistent with SMF being the public interface to Lighttpd. Having Lighttpd be an instance of svc:/network/http follows the convention set by the Apache integration. The appropriate manifest and method files will be provided in the package. A Lighttpd Admin profile will be added to the system along with the auths required to allow the Lighttpd Admin profile to manage the lighttpd SMF service. 2.9 Build features See Appendix 2 for a list of features that Lighttpd can be built with. Build time package selection determines which Lighttpd loadable modules are available to the user at runtime. A complete list of Lighttpd modules is available on the Lighttpd Wiki[1] The core packages recommended by the Lighttpd developers are pcre, ssl and IPv6. Lua is also highly recommended as it is required by the mod_magnet module but currently there is no support for Lua in Solaris/OpenSolaris. 3. Lighttpd documentation Lighttpd provides man pages for the lighttpd and spawn-fcgi executables and the source distribution includes module documentation. It is not common practice to include the module documentation and will not be included in this integration The Lighttpd man pages that are provided with the sources don't cover all of command line flags. These man pages will be added to as part of this integration in order to include all of the command line flags and provide additional usage information to the user. The files affected by these additions are lighttpd.1 and spawn-fcgi.1 A "lighttpd" man page will be created and added to /usr/share/man/man1m This man page will provide the user with useful information for getting started with Lighttpd on OpenSolaris. 4. Packaging and Delivery We propose to package Lighttpd under the following packages: SUNWlighttpd14u - [usr] Server package (including server daemon, utility daemons, loadable modules, man pages) SUNWlighttpd14r - [root] (config files, smf files and data directory) Multiple versions can coexist, and are distinguished by the naming scheme (lighttpd14 for version 1.4.*, lighttpd15 for version 1.5.*). 5. Lighttpd Interfaces 5.1. Interface Stability Lighttpd has no obvious history of any interface instability and the expectation is that dot-dot releases of Lighttpd will be compatible. This is not completely guaranteed by the community and it is possible that interfaces may change due to the fixing of bugs. 5.2. Imported Interfaces OpenSSL External/Volatile PSARC/2003/500 PCRE Uncommitted PSARC/2007/164 libmysqlclient Committed LSARC 2007/608 5.3. Exported Interfaces NAME STABILITY NOTES SUNWlighttpd14r committed package SUNWlighttpd14u committed package lighttpd command line options uncommitted command line options lighttpd config file uncommitted config file syntax lighttpd log file not an interface log file syntax lighttpd pid file project private daemon pid file lighttpd umbrella Man Page committed man page spawn-fcgi command line options uncommitted command line options /usr/lighttpd/1.4/bin/spawn-fcgi uncommitted executable /usr/lighttpd/1.4/sbin/lighttpd uncommitted executable /usr/lighttpd/1.4/sbin/lighttpd-angel uncommitted executable /usr/lighttpd/1.4/man/man1/lighttpd.1 uncommitted man page /usr/lighttpd/1.4/man/man1/spawn-fcgi.1 uncommitted man page /var/lighttpd/1.4/docroot uncommitted document root /var/lighttpd/1.4/docroot/index.html uncommitted welcome page /var/lighttpd/1.4/docroot/logo.png uncommitted image /var/lighttpd/1.4/logs uncommitted log file dir /etc/lighttpd/1.4/lighttpd.conf uncommitted default conf file /etc/lighttpd/1.4/lighttpd.conf-fcgi uncommitted sample conf file /usr/lighttpd/1.4/lib/mod_*.so project private shared library svc:/network/http:lighttpd14 committed FMRI /lib/svc/method/lighttpd14-svc project private SMF svc method script /var/svc/manifest/network/lighttpd14.xml project private SMF Manifest 6. References [1] http://trac.lighttpd.net/trac/wiki/Docs ================================================================ Appendix 1: Lighttpd Integration Directory and File Structure. 1. The following files are included in the Lighttpd integration: /usr/lighttpd/1.4 /bin /spawn-fcgi /sbin /lighttpd /lighttpd-angel /man /man1 /lighttpd.1 /spawn-fcgi.1 /var/lighttpd/1.4 /docroot /index.html /logo.png /logs /error.log /access.log /lighttpd.pid /etc/lighttpd/1.4 /lighttpd.conf /lighttpd.conf-fcgi /usr/lighttpd/1.4/lib /mod_flv_streaming.so /mod_evasive.so /mod_webdav.so /mod_magnet.so /mod_cml.so /mod_trigger_b4_dl.so /mod_mysql_vhost.so /mod_cgi.so /mod_scgi.so /mod_staticfile.so /mod_dirlisting.so /mod_indexfile.so /mod_setenv.so /mod_alias.so /mod_userdir.so /mod_rrdtool.so /mod_usertrack.so /mod_proxy.so /mod_ssi.so /mod_secdownload.so /mod_expire.so /mod_evhost.so /mod_simple_vhost.so /mod_fastcgi.so /mod_extforward.so /mod_access.so /mod_compress.so /mod_auth.so /mod_rewrite.so /mod_redirect.so /mod_status.so /mod_accesslog.so /usr/share/man/man1m /lighttpd.1m /lib/svc/method/lighttpd14-svc /var/svc/manifest/network/lighttpd14.xml Appendix 2: Lighttpd Features and Packages The following options are provided by the configure script for enabling or disabling features and for adding/removing packages Optional Features: --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no) --enable-FEATURE[=ARG] include FEATURE [ARG=yes] --enable-maintainer-mode enable make rules and dependencies not useful (and sometimes confusing) to the casual installer --disable-dependency-tracking speeds up one-time build --enable-dependency-tracking do not reject slow dependency extractors --enable-static[=PKGS] build static libraries [default=no] --enable-shared[=PKGS] build shared libraries [default=yes] --enable-fast-install[=PKGS] optimize for fast installation [default=yes] --disable-libtool-lock avoid locking (might break parallel builds) --enable-lfs Turn on Large File System (default) --disable-ipv6 disable IPv6 support Optional Packages: --with-PACKAGE[=ARG] use PACKAGE [ARG=yes] --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) --with-gnu-ld assume the C compiler uses GNU ld [default=no] --with-pic try to use only PIC/non-PIC objects [default=use both] --with-tags[=TAGS] include additional configurations [automatic] --with-mysql[=PATH] Include MySQL support. PATH is the path to 'mysql_config' --with-ldap enable LDAP support --with-attr enable extended attribute support --with-valgrind enable internal support for valgrind --with-openssl[=DIR] Include openssl support (default no) --with-openssl-includes=DIR OpenSSL includes --with-openssl-libs=DIR OpenSSL libraries --with-kerberos5 use Kerberos5 support with OpenSSL --with-pcre Enable pcre support (default yes) --with-bzip2 Enable bzip2 support for mod_compress --with-fam fam/gamin for reducing number of stat() calls --with-webdav-props properties in mod_webdav --with-webdav-locks locks in mod_webdav --with-gdbm gdbm storage for mod_trigger_b4_dl --with-memcache memcached storage for mod_trigger_b4_dl --with-lua lua engine for mod_cml Appendix 3: Lighttpd man pages Lighttpd ======== User Commands LIGHTTPD(1) NAME lighttpd - a fast, secure and flexible webserver SYNOPSIS lighttpd -D -f DESCRIPTION FILES /etc/lighttpd/lighttpd.conf CONFORMING TO HTTP/1.0 HTTP/1.0 HTTP-Authentification - Basic, Digest FastCGI CGI/1.1 SEE ALSO spawn-fcgi(1) AUTHOR spawn-fcgi ========== User Commands SPAWNFCGI(1) NAME spawn-fcgi - spawning FastCGI processes SYNOPSIS spawn-fcgi -f [-p | -s ] [-C ] [-c ] [-u ] [-g ] spawn-fcgi -v spawn-fcgi -h DESCRIPTION spawn-fcgi is used to spawn remote FastCGI processes. SEE ALSO lighttpd(1) AUTHOR 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: sfw 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From carlsonj@phorcys.east.sun.com Tue Mar 11 07:08:22 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2BE8LKT020013 for ; Tue, 11 Mar 2008 07:08:22 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m2BE8EsK004801; Tue, 11 Mar 2008 22:08:19 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXK00801KLSRT00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 11 Mar 2008 07:08:16 -0700 (PDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXK00I53KLRIHB0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 11 Mar 2008 07:08:16 -0700 (PDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m2BE0jZY028480; Tue, 11 Mar 2008 10:00:45 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m2BE0jxY028477; Tue, 11 Mar 2008 10:00:45 -0400 (EDT) Date: Tue, 11 Mar 2008 10:00:45 -0400 From: James Carlson Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> To: Jyri Virkki Cc: lsarc-ext@sun.com, webstack-discuss@opensolaris.org, Amanda.Waite@sun.com Message-id: <18390.37005.46160.674516@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> Status: RO Content-Length: 813 Jyri Virkki writes: > Appendix 2: Lighttpd Features and Packages > > The following options are provided by the configure script for enabling or > disabling features and for adding/removing packages I don't understand. The options you're showing here are just a summary of the *compile time* options. You're the one compiling it, so you're selecting those options, not the users who enable this new server. If you're trying to document what features are enabled or disabled, please provide a list of what's actually enabled so that users can determine what the compiled code delivers. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Amanda.Waite@sun.com Tue Mar 11 07:51:57 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2BEpuFD022154 for ; Tue, 11 Mar 2008 07:51:56 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m2BEpQXI021447 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 11 Mar 2008 22:51:55 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXK0070TMMG8300@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 11 Mar 2008 07:51:52 -0700 (PDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXK003FQMLLYNA0@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 11 Mar 2008 07:51:22 -0700 (PDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m2BEpKQu023142 for ; Tue, 11 Mar 2008 14:51:20 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JXK00A01JPT4N00@fe-emea-10.sun.com> (original mail from Amanda.Waite@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 11 Mar 2008 14:51:20 +0000 (GMT) Received: from [129.156.84.169] by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JXK0009KMKV1610@fe-emea-10.sun.com>; Tue, 11 Mar 2008 14:50:56 +0000 (GMT) Date: Tue, 11 Mar 2008 14:49:31 +0000 From: Amanda Waite Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <18390.37005.46160.674516@gargle.gargle.HOWL> Sender: Amanda.Waite@sun.com To: James Carlson Cc: Jyri Virkki , lsarc-ext@sun.com, webstack-discuss@opensolaris.org Message-id: <47D69BFB.1040005@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <18390.37005.46160.674516@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.6 (X11/20080102) Status: RO Content-Length: 1211 James Carlson wrote: > Jyri Virkki writes: > >> Appendix 2: Lighttpd Features and Packages >> >> The following options are provided by the configure script for enabling or >> disabling features and for adding/removing packages >> > > I don't understand. The options you're showing here are just a > summary of the *compile time* options. You're the one compiling it, > so you're selecting those options, not the users who enable this new > server. > > If you're trying to document what features are enabled or disabled, > please provide a list of what's actually enabled so that users can > determine what the compiled code delivers. > > That wasn't my intent when including that as an appendix, it was purely meant as additional information to support the Arc case. The plan was to include information about which features/packages Lighttpd was built with in the Lighttpd umbrella man page, but I don't explicitly state this in the Arc Case, I just say "This man page will provide the user with useful information for getting started with Lighttpd on OpenSolaris". Thanks Amanda -- Amanda Waite ISV-Engineering OSS, Sun Microsystems Tel: +44 (0)1252 420693 Mobile: +44 (0)7802 175732 From carlsonj@phorcys.east.sun.com Tue Mar 11 08:02:47 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2BF2k1N022901 for ; Tue, 11 Mar 2008 08:02:47 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2BF2UqD028382; Tue, 11 Mar 2008 15:02:45 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXK00201N4K7Q00@brm-avmta-1.central.sun.com>; Tue, 11 Mar 2008 09:02:44 -0600 (MDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXK00J65N4HM980@brm-avmta-1.central.sun.com>; Tue, 11 Mar 2008 09:02:42 -0600 (MDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m2BEtBBp028784; Tue, 11 Mar 2008 10:55:11 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m2BEtBFI028781; Tue, 11 Mar 2008 10:55:11 -0400 (EDT) Date: Tue, 11 Mar 2008 10:55:11 -0400 From: James Carlson Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <47D69BFB.1040005@sun.com> To: Amanda Waite Cc: Jyri Virkki , lsarc-ext@sun.com, webstack-discuss@opensolaris.org Message-id: <18390.40271.143977.213986@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <18390.37005.46160.674516@gargle.gargle.HOWL> <47D69BFB.1040005@sun.com> Status: RO Content-Length: 786 Amanda Waite writes: > That wasn't my intent when including that as an appendix, it was purely > meant as additional information to support the Arc case. The plan was to > include information about which features/packages Lighttpd was built > with in the Lighttpd umbrella man page, but I don't explicitly state > this in the Arc Case, I just say "This man page will provide the user > with useful information for getting started with Lighttpd on OpenSolaris". In other words, the list of supported features isn't considered architectural. Is that right? -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Amanda.Waite@sun.com Tue Mar 11 08:19:24 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2BFJN8i024094 for ; Tue, 11 Mar 2008 08:19:23 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m2BFJJMo007771 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 11 Mar 2008 08:19:23 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXK007HENW9GS10@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 11 Mar 2008 08:19:21 -0700 (PDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXK003EANTYYLF0@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 11 Mar 2008 08:17:58 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m2BFHvr5028985 for ; Tue, 11 Mar 2008 15:17:57 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JXK00201NJS8M00@fe-emea-09.sun.com> (original mail from Amanda.Waite@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 11 Mar 2008 15:17:57 +0000 (GMT) Received: from [129.156.84.169] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JXK00MGDNTRPH10@fe-emea-09.sun.com>; Tue, 11 Mar 2008 15:17:51 +0000 (GMT) Date: Tue, 11 Mar 2008 15:16:27 +0000 From: Amanda Waite Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <18390.40271.143977.213986@gargle.gargle.HOWL> Sender: Amanda.Waite@sun.com To: James Carlson Cc: Jyri Virkki , lsarc-ext@sun.com, webstack-discuss@opensolaris.org Message-id: <47D6A24B.7090406@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <18390.37005.46160.674516@gargle.gargle.HOWL> <47D69BFB.1040005@sun.com> <18390.40271.143977.213986@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.6 (X11/20080102) Status: RO Content-Length: 1128 James Carlson wrote: > Amanda Waite writes: > >> That wasn't my intent when including that as an appendix, it was purely >> meant as additional information to support the Arc case. The plan was to >> include information about which features/packages Lighttpd was built >> with in the Lighttpd umbrella man page, but I don't explicitly state >> this in the Arc Case, I just say "This man page will provide the user >> with useful information for getting started with Lighttpd on OpenSolaris". >> > > In other words, the list of supported features isn't considered > architectural. Is that right? > There's a detailed section on loadable modules and we document the interfaces that are imported. Now that you've pointed it out, I can also see that a list of supported features would help to provide a more complete architectural view when looked at in conjunction with this other information. I'll talk to Jyri about what needs to be done to add this information. Thanks for the pointers Amanda -- Amanda Waite ISV-Engineering OSS, Sun Microsystems Tel: +44 (0)1252 420693 Mobile: +44 (0)7802 175732 From jyri@buye.red.iplanet.com Wed Mar 12 23:56:31 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2D6uV7j017943 for ; Wed, 12 Mar 2008 23:56:31 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m2D6uTXF017310; Thu, 13 Mar 2008 00:56:29 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXN00L01PY4EY00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 12 Mar 2008 23:56:28 -0700 (PDT) Received: from buye.red.iplanet.com ([192.18.65.224]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXN00AB9PY4BMB0@nwk-avmta-1.sfbay.Sun.COM>; Wed, 12 Mar 2008 23:56:28 -0700 (PDT) Received: from buye.red.iplanet.com (localhost [127.0.0.1]) by buye.red.iplanet.com (8.13.7+Sun/8.13.7) with ESMTP id m2D6mw3B003691; Wed, 12 Mar 2008 23:48:58 -0700 (PDT) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id m2D6mwhX003690; Wed, 12 Mar 2008 23:48:58 -0700 (PDT) Date: Wed, 12 Mar 2008 23:48:58 -0700 From: Jyri Virkki Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <47D6A24B.7090406@sun.com> To: Amanda Waite Cc: lsarc-ext@sun.com, webstack-discuss@opensolaris.org Message-id: <20080313064858.GA3598@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <18390.37005.46160.674516@gargle.gargle.HOWL> <47D69BFB.1040005@sun.com> <18390.40271.143977.213986@gargle.gargle.HOWL> <47D6A24B.7090406@sun.com> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 1457 I've updated the case materials with an updated spec from the project team addressing the previous comments. Full spec in case materials. Diffs, below. ------- lighttpd.txt ------- --- /tmp/sccs.neaq_g Wed Mar 12 23:45:25 2008 +++ lighttpd.txt Wed Mar 12 23:36:28 2008 @@ -82,6 +82,18 @@ mod_auth.so failed due to Lighttpd's use of OpenLDAP extensions not documented in the internet draft LDAP C-API document. This case defers inclusion of the LDAP support to a future project. + + Support for loadable modules and other features is enabled at + build time through flags to the configure script. The following + features are enabled by this integration: + + --with-ipv6 - Allows for handling of IPv6 connection requests + --with-bzip - Allows for the use of compression + --with-pcre= - Allows use of Regular Expressions in + the config file + --with-mysql= - allows a vhost's docroot to be stored in + a MySQL database + --with-openssl= - Adds support for SSL 2.4 Directory Naming and Structure @@ -92,6 +104,7 @@ /sbin /bin /lib + /man /etc/lighttpd/1.4 /conf.d -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From danek.duvall@sun.com Thu Mar 13 10:39:38 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2DHdciZ007925 for ; Thu, 13 Mar 2008 10:39:38 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m2DHdZWC023464 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 13 Mar 2008 10:39:38 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXO0090PJQ23R00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 13 Mar 2008 11:39:38 -0600 (MDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXO008OFJQ1KV00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 13 Mar 2008 11:39:38 -0600 (MDT) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2DHdaJJ044136; Thu, 13 Mar 2008 10:39:36 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m2DHda5u025266; Thu, 13 Mar 2008 10:39:36 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2/Submit) id m2DHdZYc025265; Thu, 13 Mar 2008 10:39:36 -0700 (PDT) Date: Thu, 13 Mar 2008 10:39:35 -0700 From: Danek Duvall Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> To: Jyri Virkki Cc: lsarc-ext@sun.com, Amanda.Waite@sun.com, webstack-discuss@opensolaris.org Message-id: <20080313173935.GI24360@zruty.sfbay.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 894 I'm curious about the versioning of the paths. Do people actually install more than one of these on a system at a given time? I'll note that none of Ubuntu, Fedora, and Gentoo version their installations. Does the HTML documentation root really need to be versioned? Are the executables you're shipping commonly run from the commandline? It seems from the manpages you provide that lighttpd is something that would most likely only ever be run via SMF, and that spawn-fcgi would only ever be run from lighttpd. Could *all* of the executable code live, better integrated with Solaris, under /usr/lib/lighttpd? Why are you providing support for mysql, but not postgres? Will you include support for sqlite once it integrates? You'll need to provide the RBAC information that you mention in passing. It's project private, so I don't care too much, but why do you have a pid file? Danek From Amanda.Waite@sun.com Thu Mar 13 12:56:15 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2DJuE1f011914 for ; Thu, 13 Mar 2008 12:56:14 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m2DJtqwP009754 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Fri, 14 Mar 2008 03:56:13 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXO00I0RQ1M7600@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 13 Mar 2008 13:56:10 -0600 (MDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXO008BVQ1KKZA0@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 13 Mar 2008 13:56:09 -0600 (MDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m2DJu8Q5021541 for ; Thu, 13 Mar 2008 19:56:08 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JXO00G01Q0JZX00@fe-emea-09.sun.com> (original mail from Amanda.Waite@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 13 Mar 2008 19:56:08 +0000 (GMT) Received: from [129.150.116.111] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JXO0027WQ1JY420@fe-emea-09.sun.com>; Thu, 13 Mar 2008 19:56:07 +0000 (GMT) Date: Thu, 13 Mar 2008 19:56:11 +0000 From: Amanda waite Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <20080313173935.GI24360@zruty.sfbay.sun.com> Sender: Amanda.Waite@sun.com To: Danek Duvall Cc: Jyri Virkki , lsarc-ext@sun.com, webstack-discuss@opensolaris.org Message-id: <47D986DB.1060602@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) Status: RO Content-Length: 3054 Danek Duvall wrote: > I'm curious about the versioning of the paths. Do people actually install > more than one of these on a system at a given time? I'll note that none of > Ubuntu, Fedora, and Gentoo version their installations. Does the HTML > documentation root really need to be versioned? > We felt that it's very likely that users will want to run more than one version of Lighttpd on the same system and so provisioned for it. In doing so we tried to stick with many of the conventions that had already been established with Apache2. The layout of the Lighttpd integration is very similar to that of Apache2 including the versioning of the document root. Once you've decided on having multiple versions then you really have to version everything on the assumption that both versions would be run simultaneously. > Are the executables you're shipping commonly run from the commandline? It > seems from the manpages you provide that lighttpd is something that would > most likely only ever be run via SMF, and that spawn-fcgi would only ever > be run from lighttpd. Could *all* of the executable code live, better > integrated with Solaris, under /usr/lib/lighttpd? > Actually, it's as likely that users would want to run the spawn-fcgi command as they would be to run the lighttpd command. spawn-fcgi is used to spawn the backend end processes that Lighttpd connects to and is run independently of the lighttpd command. Our initial thought was that the command line tools were used so much that they should go in /usr/sbin and /usr/bin but we were asked to look into it and found that they were most likely to be run only while debugging. We then decided to hide away the executables in /usr/lighttpd/1.4 and as you suggest, make SMF the public interface for Lighttpd. The exact location was again determined by the convention set by the Apache2 integration. > Why are you providing support for mysql, but not postgres? Will you > include support for sqlite once it integrates? > Lighttpd supports MySQL for the vhost module (which is actually called mod_mysql_vhost) which allows users to host a vhost's docroot in a MySQL DB, there is no equivalent module that supports Postgres. SQLite is used only with the WebDAV module and we will certainly look at adding support for that module once the integration of SQLite3 is complete. > You'll need to provide the RBAC information that you mention in passing. > Is that usual then? what level of detail would you suggest? The actual lines that will be added to auths_attr and prof_attr? > It's project private, so I don't care too much, but why do you have a pid > file? > I guess it's what happens when you are writing your first Arc Case and you look around at other Arc Cases that have been through the review process. You tend to use them as a starting point as to what to document and what not to document. When working on the final draft we felt that it actually should be noted that Lighttpd has a pid file. Thanks Amanda > Danek > From jan@kneschke.de Thu Mar 13 13:50:48 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2DKolC2013053 for ; Thu, 13 Mar 2008 13:50:47 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m2DKofEG030104; Thu, 13 Mar 2008 14:50:46 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXO0080XSKLPZ00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 13 Mar 2008 13:50:45 -0700 (PDT) Received: from sca-ea-mail-1.sun.com ([192.18.43.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXO000WKSKKMH60@nwk-avmta-1.sfbay.Sun.COM>; Thu, 13 Mar 2008 13:50:44 -0700 (PDT) Received: from relay18i.sun.com (ip128.net129179-4.block1.us.syntegra.com [129.179.4.128]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m2DKhv9G023422; Thu, 13 Mar 2008 20:50:44 +0000 (GMT) Received: from mmp12es.sun.com ([160.41.209.22] [160.41.209.22]) by relay18i.sun.com with ESMTP id BT-MMP-60911; Thu, 13 Mar 2008 20:50:40 +0000 (Z) Received: from relay12i.sun.com (relay12i.sun.com [129.179.4.122]) by mmp12es.sun.com with ESMTP id BT-MMP-1270542; Thu, 13 Mar 2008 20:50:39 +0000 (Z) Received: from mail0.metaways.net ([195.244.121.140] [195.244.121.140]) by relay1i.sun.com with ESMTP id BT-MMP-414371; Thu, 13 Mar 2008 20:50:38 +0000 (Z) Received: from [192.168.2.113] (pD9E2A0E7.dip.t-dialin.net [217.226.160.231]) by mail0.metaways.net (Postfix) with ESMTPSA id 7C06A4446; Thu, 13 Mar 2008 21:50:37 +0100 (MET) Date: Thu, 13 Mar 2008 21:50:36 +0100 From: Jan Kneschke Subject: Re: [webstack-discuss] Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <47D986DB.1060602@sun.com> To: Danek Duvall Cc: Amanda waite , webstack-discuss@opensolaris.org, lsarc-ext@sun.com, Jyri Virkki Message-id: <47D9939C.2010605@kneschke.de> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Enigmail-Version: 0.95.3 X-Virus-Scanned: ClamAV 0.92.1/6225/Thu Mar 13 15:52:37 2008 on mail-0.metaways.net X-Virus-Status: Clean X-Antispam: No, score=-2.6/5.0, scanned in 0.144sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20070801) Status: RO Content-Length: 3041 Amanda waite wrote: > Danek Duvall wrote: >> I'm curious about the versioning of the paths. Do people actually install >> more than one of these on a system at a given time? I'll note that none of >> Ubuntu, Fedora, and Gentoo version their installations. Does the HTML >> documentation root really need to be versioned? >> > > We felt that it's very likely that users will want to run more than one > version of Lighttpd on the same system and so provisioned for it. In > doing so we tried to stick with many of the conventions that had already > been established with Apache2. The layout of the Lighttpd integration is > very similar to that of Apache2 including the versioning of the document > root. Once you've decided on having multiple versions then you really > have to version everything on the assumption that both versions would be > run simultaneously. > >> Are the executables you're shipping commonly run from the commandline? It >> seems from the manpages you provide that lighttpd is something that would >> most likely only ever be run via SMF, and that spawn-fcgi would only ever >> be run from lighttpd. Could *all* of the executable code live, better >> integrated with Solaris, under /usr/lib/lighttpd? >> > > Actually, it's as likely that users would want to run the spawn-fcgi > command as they would be to run the lighttpd command. spawn-fcgi is used > to spawn the backend end processes that Lighttpd connects to and is run > independently of the lighttpd command. Our initial thought was that the > command line tools were used so much that they should go in /usr/sbin > and /usr/bin but we were asked to look into it and found that they were > most likely to be run only while debugging. We then decided to hide away > the executables in /usr/lighttpd/1.4 and as you suggest, make SMF the > public interface for Lighttpd. The exact location was again determined > by the convention set by the Apache2 integration. You usually only run lighttpd on by hand if you want to verify the configuration is valid (lighttpd -t ...) or want to print the configuration in a clean way (lighttpd -p ...). >> Why are you providing support for mysql, but not postgres? Will you >> include support for sqlite once it integrates? >> > > Lighttpd supports MySQL for the vhost module (which is actually called > mod_mysql_vhost) which allows users to host a vhost's docroot in a MySQL > DB, there is no equivalent module that supports Postgres. SQLite is used > only with the WebDAV module and we will certainly look at adding support > for that module once the integration of SQLite3 is complete. In the next major release (1.5) we have split out the db-backend: * mod_sql_vhost_core.c * mod_mysql_vhost.c * mod_postgresql_vhost.c the two are only providing the access to the storage, the core-module does the caching and everything else. cheers, Jan (lighttpd dev) -- jan: "Gee, Brain^WEric, what'd you wanna do tonight?" eric: Same thing we do everynight: Take over the HelloWorld! From danek.duvall@sun.com Thu Mar 13 14:30:15 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2DLUEOC015923 for ; Thu, 13 Mar 2008 14:30:15 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m2DLU6eo018293 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@Sun.COM>; Fri, 14 Mar 2008 05:30:14 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXO00A0DUEDGB00@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Thu, 13 Mar 2008 14:30:13 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXO008WMUEC7Y20@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Thu, 13 Mar 2008 14:30:12 -0700 (PDT) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2DLUAGf017180; Thu, 13 Mar 2008 14:30:10 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m2DLUA4j027528; Thu, 13 Mar 2008 14:30:10 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2/Submit) id m2DLUAGL027527; Thu, 13 Mar 2008 14:30:10 -0700 (PDT) Date: Thu, 13 Mar 2008 14:30:10 -0700 From: Danek Duvall Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <47D986DB.1060602@sun.com> To: Amanda waite Cc: Jyri Virkki , lsarc-ext@sun.com, webstack-discuss@opensolaris.org Message-id: <20080313213010.GO24360@zruty.sfbay.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 2871 On Thu, Mar 13, 2008 at 07:56:11PM +0000, Amanda waite wrote: > We felt that it's very likely that users will want to run more than one > version of Lighttpd on the same system and so provisioned for it. Why did you think that would be common? Like I said, it doesn't appear that this is common on a handful of common Linux distributions; what would make the situation different on Solaris? > In doing so we tried to stick with many of the conventions that had > already been established with Apache2. The layout of the Lighttpd > integration is very similar to that of Apache2 including the versioning > of the document root. Yup. I don't agree with the way Apache has been versioned, either, though I understand why we delivered both 1.3 and 2.x for a while. Why we haven't yet gotten rid of 1.3, or why we now ship two versions of 2.x is completely beyond me. I think it's nuts. > Once you've decided on having multiple versions then you really have to > version everything on the assumption that both versions would be run > simultaneously. Yup; it's that assumption I'm questioning. >> Why are you providing support for mysql, but not postgres? Will you >> include support for sqlite once it integrates? > > Lighttpd supports MySQL for the vhost module (which is actually called > mod_mysql_vhost) which allows users to host a vhost's docroot in a MySQL > DB, there is no equivalent module that supports Postgres. SQLite is used > only with the WebDAV module and we will certainly look at adding support > for that module once the integration of SQLite3 is complete. Ah, okay. Database support is not generic; it's just for one particular module to use. Is there a text or dbm database backend available, too, for folks who might not want to load a full database onto their system? >> You'll need to provide the RBAC information that you mention in passing. > > Is that usual then? what level of detail would you suggest? The actual > lines that will be added to auths_attr and prof_attr? Yup, that'd be fine. >> It's project private, so I don't care too much, but why do you have a pid >> file? > > I guess it's what happens when you are writing your first Arc Case and you > look around at other Arc Cases that have been through the review process. > You tend to use them as a starting point as to what to document and what > not to document. When working on the final draft we felt that it actually > should be noted that Lighttpd has a pid file. It's extraneous in the interface table, since you're not putting it in a Public directory and it's not a Public interface itself. But it's also extraneous on Solaris, since it's never actually going to be used by anything -- SMF manages all of that for you without the need for a pid file. You don't have to go to any trouble to remove it, but as it was, it stood out. Danek From David.Comay@sun.com Sun Mar 16 23:05:41 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2H65eRB001392 for ; Sun, 16 Mar 2008 23:05:41 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m2H65cYI052825; Mon, 17 Mar 2008 00:05:38 -0600 (MDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXV0010129EV800@brm-avmta-1.central.sun.com>; Mon, 17 Mar 2008 00:05:38 -0600 (MDT) Received: from police.SFBay.Sun.COM ([129.146.228.53]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXV00L6T29DKG20@brm-avmta-1.central.sun.com>; Mon, 17 Mar 2008 00:05:37 -0600 (MDT) Received: from localhost (localhost [127.0.0.1]) by police.SFBay.Sun.COM (8.13.8+Sun/8.13.8) with ESMTP id m2H5w7tx019641; Sun, 16 Mar 2008 22:58:07 -0700 (PDT) Date: Sun, 16 Mar 2008 22:58:05 -0700 (PDT) From: David.Comay@sun.com Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <20080313213010.GO24360@zruty.sfbay.sun.com> Sender: comay@police.sfbay.sun.com To: Danek Duvall Cc: Amanda waite , webstack-discuss@opensolaris.org, lsarc-ext@sun.com, Jyri Virkki Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> <20080313213010.GO24360@zruty.sfbay.sun.com> Status: RO Content-Length: 1054 > Yup. I don't agree with the way Apache has been versioned, either, though > I understand why we delivered both 1.3 and 2.x for a while. Why we haven't > yet gotten rid of 1.3, or why we now ship two versions of 2.x is completely > beyond me. I think it's nuts. Actually, we only have a single version of 2.x (2.2.8 currently) although as you point out, we still do include 1.3. At one time, that was partly due to something else (printing?) being dependent on it although I don't know if that's still the case. >> Once you've decided on having multiple versions then you really have to >> version everything on the assumption that both versions would be run >> simultaneously. > > Yup; it's that assumption I'm questioning. Although I agree that the versioning of things like the configuration files seems unusual, I think it's the price we need to pay here. That said, what I'd like to see (and this was discussed I think in the earlier Apache upgrade and PHP cases) is limiting the number of outstanding versions to a very small number. dsc From jyri@buye.red.iplanet.com Mon Mar 17 00:37:28 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2H7bSxr004226 for ; Mon, 17 Mar 2008 00:37:28 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m2H7bPRb015941; Mon, 17 Mar 2008 00:37:27 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXV009036ID3O00@brm-avmta-1.central.sun.com>; Mon, 17 Mar 2008 01:37:25 -0600 (MDT) Received: from buye.red.iplanet.com ([192.18.65.224]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXV00LGM6IBK560@brm-avmta-1.central.sun.com>; Mon, 17 Mar 2008 01:37:23 -0600 (MDT) Received: from buye.red.iplanet.com (localhost [127.0.0.1]) by buye.red.iplanet.com (8.13.7+Sun/8.13.7) with ESMTP id m2H7Tr0h004451; Mon, 17 Mar 2008 00:29:53 -0700 (PDT) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id m2H7TrBT004450; Mon, 17 Mar 2008 00:29:53 -0700 (PDT) Date: Mon, 17 Mar 2008 00:29:53 -0700 From: Jyri Virkki Subject: Re: [webstack-discuss] Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <20080313213010.GO24360@zruty.sfbay.sun.com> To: Danek Duvall Cc: Amanda waite , webstack-discuss@opensolaris.org, lsarc-ext@sun.com Message-id: <20080317072953.GD4234@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> <20080313213010.GO24360@zruty.sfbay.sun.com> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 1619 Danek Duvall wrote: > > On Thu, Mar 13, 2008 at 07:56:11PM +0000, Amanda waite wrote: > > We felt that it's very likely that users will want to run more than one > > version of Lighttpd on the same system and so provisioned for it. > > Why did you think that would be common? Like I said, it doesn't appear > that this is common on a handful of common Linux distributions; what would > make the situation different on Solaris? Let's see how different is it... In debian today I see for example: - php4 packages and php5 packages - apache and apache2 packages They do it presumably for the same reasons several of the OpenSolaris project teams have felt the need, which is to provide stability within a given major release family while at the same time making the newer-generation apps available. > Yup. I don't agree with the way Apache has been versioned, either, though > I understand why we delivered both 1.3 and 2.x for a while. Why we haven't > yet gotten rid of 1.3, or why we now ship two versions of 2.x is completely > beyond me. I think it's nuts. There's only one apache22. apache1 is best thought of as a different product just sharing the same first name, still with its user base. Anyway, this is not the apache case. Some of the OpenSolaris components have finer-grained versioning than in Linux, because the Solaris lifecycle and stability expectations are different. Uncommitted still means stable until the next minor release, which is a very long time. Short of declaring everything Volatile, some versioning is unavoidable. -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From danek.duvall@sun.com Mon Mar 17 09:46:28 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2HGkS04017518 for ; Mon, 17 Mar 2008 09:46:28 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m2HGkF5k054643 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Mon, 17 Mar 2008 10:46:27 -0600 (MDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXV0062HVXEH600@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 10:46:26 -0600 (MDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXV00LE9VXC6N30@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 10:46:24 -0600 (MDT) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2HGkNx2004789; Mon, 17 Mar 2008 09:46:23 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m2HGkMlk029231; Mon, 17 Mar 2008 09:46:22 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2/Submit) id m2HGkMxB029230; Mon, 17 Mar 2008 09:46:22 -0700 (PDT) Date: Mon, 17 Mar 2008 09:46:22 -0700 From: Danek Duvall Subject: Re: [webstack-discuss] Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <20080317072953.GD4234@sun.com> To: Jyri Virkki Cc: Amanda waite , webstack-discuss@opensolaris.org, lsarc-ext@sun.com Message-id: <20080317164622.GG4653@zruty.sfbay.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> <20080313213010.GO24360@zruty.sfbay.sun.com> <20080317072953.GD4234@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 3839 On Mon, Mar 17, 2008 at 12:29:53AM -0700, Jyri Virkki wrote: > Danek Duvall wrote: > > > > On Thu, Mar 13, 2008 at 07:56:11PM +0000, Amanda waite wrote: > > > We felt that it's very likely that users will want to run more than one > > > version of Lighttpd on the same system and so provisioned for it. > > > > Why did you think that would be common? Like I said, it doesn't appear > > that this is common on a handful of common Linux distributions; what would > > make the situation different on Solaris? > > Let's see how different is it... In debian today I see for example: > - php4 packages and php5 packages > - apache and apache2 packages And I understand why those are that way. But I'm not asking about why it's done in general (like you said, this isn't the apache case), but about this particular case. Does lighthttpd need to be treated the same way? Is there a rich community of end-user plugins for lighttpd the way there is for php and apache? Is there binary incompatibility between releases that will cause end-user plugins to break when we upgrade? Are there other things that would go wrong? I'm not saying there isn't, but I don't know -- I'm not terribly familiar with lighttpd. But I strongly get the sense that some teams are versioning the installations because they don't actually want to do the work to find out whether a) there actually are incompatibilities between the releases they might conceivably ship, b) those incompatibilities are relevant to customers and not something the distro can smooth over the transition, and c) customers really will want more than one version at a time, rather than making a jump. Perhaps that analysis actually has been done, but I don't see any evidence of it. > They do it presumably for the same reasons several of the OpenSolaris > project teams have felt the need, which is to provide stability within a > given major release family while at the same time making the > newer-generation apps available. I'd like to take the "presumably" out of that. If there's a real need for the versioning, let's hear it. If there isn't, let's not do it. > > Yup. I don't agree with the way Apache has been versioned, either, though > > I understand why we delivered both 1.3 and 2.x for a while. Why we haven't > > yet gotten rid of 1.3, or why we now ship two versions of 2.x is completely > > beyond me. I think it's nuts. > > There's only one apache22. apache1 is best thought of as a different > product just sharing the same first name, still with its user base. I get that. But I do have SUNWapch2u and SUNWapch22u on my build 83 system (the first delivering 2.2.3, the second 2.2.6). Perhaps the appropriate pkghistory files haven't been delivered, so the older copy isn't being removed? > Anyway, this is not the apache case. I only brought it up because I didn't think a good decision had been made there. Though the binary compatibility argument makes sense to me, as long as there are enough customers for each version range with isolated compatibility to make them worth supporting. That doesn't mean I don't still think it's nuts that people are still using 1.3 how many years after 2.x came out? > Some of the OpenSolaris components have finer-grained versioning than in > Linux, because the Solaris lifecycle and stability expectations are > different. Uncommitted still means stable until the next minor release, > which is a very long time. Unfortunately, the release taxonomy is being shredded at the moment. We used to be able to say that until the in-development release (Nevada at the moment) actually shipped, you could do pretty much anything you wanted, including making incompatible change, and you were only locked in at release. But no one's really sure what that means when you throw SXDE or Indiana into the mix. Danek From danek.duvall@sun.com Mon Mar 17 09:54:35 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2HGsYRW018321 for ; Mon, 17 Mar 2008 09:54:34 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2HGsTWC013119 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@Sun.COM>; Mon, 17 Mar 2008 16:54:33 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXV0036XWAVW900@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Mon, 17 Mar 2008 09:54:31 -0700 (PDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXV00BXCWAT1TB0@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Mon, 17 Mar 2008 09:54:29 -0700 (PDT) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2HGsSm2035089; Mon, 17 Mar 2008 09:54:28 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m2HGsRjR029269; Mon, 17 Mar 2008 09:54:27 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2/Submit) id m2HGsRlJ029268; Mon, 17 Mar 2008 09:54:27 -0700 (PDT) Date: Mon, 17 Mar 2008 09:54:27 -0700 From: Danek Duvall Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: To: David.Comay@sun.com Cc: Amanda waite , webstack-discuss@opensolaris.org, lsarc-ext@sun.com, Jyri Virkki Message-id: <20080317165427.GA29238@zruty.sfbay.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> <20080313213010.GO24360@zruty.sfbay.sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 968 On Sun, Mar 16, 2008 at 10:58:05PM -0700, David.Comay@Sun.COM wrote: > That said, what I'd like to see (and this was discussed I think in the > earlier Apache upgrade and PHP cases) is limiting the number of > outstanding versions to a very small number. Like Stephen has mentioned a couple of times, two should be the maximum. It allows for an orderly transition from one compatibility regime to the next. However, I would like not to treat the versioning as a first-class citizen. The system should behave as if we'd properly integrated one version of the component, and any versioning is there only so projects with a dependence on a particular version can be specific. Names available in /usr/bin, /usr/lib, /usr/share/man, etc, should generally be the later of the two versions, though circumstances may prefer the earlier, at least at the outset. If that means that names in /usr/bin and friends have a lower commitment level, that's probably fine. Danek From carlsonj@phorcys.east.sun.com Mon Mar 17 10:31:58 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2HHVwdE020436 for ; Mon, 17 Mar 2008 10:31:58 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m2HHVvBJ026400; Mon, 17 Mar 2008 10:31:58 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXV00B17Y19P000@nwk-avmta-2.sfbay.sun.com>; Mon, 17 Mar 2008 10:31:57 -0700 (PDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXV00BISY15IO00@nwk-avmta-2.sfbay.sun.com>; Mon, 17 Mar 2008 10:31:54 -0700 (PDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m2HHOOcx018390; Mon, 17 Mar 2008 13:24:24 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m2HHON8i018387; Mon, 17 Mar 2008 13:24:23 -0400 (EDT) Date: Mon, 17 Mar 2008 13:24:23 -0400 From: James Carlson Subject: Re: [webstack-discuss] Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <20080317164622.GG4653@zruty.sfbay.sun.com> To: Danek Duvall Cc: Jyri Virkki , webstack-discuss@opensolaris.org, lsarc-ext@sun.com Message-id: <18398.43335.756976.976860@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> <20080313213010.GO24360@zruty.sfbay.sun.com> <20080317072953.GD4234@sun.com> <20080317164622.GG4653@zruty.sfbay.sun.com> Status: RO Content-Length: 1020 Danek Duvall writes: > > They do it presumably for the same reasons several of the OpenSolaris > > project teams have felt the need, which is to provide stability within a > > given major release family while at the same time making the > > newer-generation apps available. > > I'd like to take the "presumably" out of that. If there's a real need for > the versioning, let's hear it. If there isn't, let's not do it. Having the path to the configuration files moving around from build to build like Robert Brown's pollen grains is distinctly not helpful for users. Please don't bake the version number into the path unless we _really_ need it, and then do only the minimum distinction necessary to make sure that the incompatible universe-has-changed transitions are accomodated correctly. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Amanda.Waite@sun.com Mon Mar 17 11:23:59 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2HINwxq021666 for ; Mon, 17 Mar 2008 11:23:59 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m2HINX2M006203 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 18 Mar 2008 02:23:58 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXW00D070FT7O00@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 11:23:53 -0700 (PDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXW00BQ10FRIL40@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 11:23:52 -0700 (PDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m2HINpOO006419 for ; Mon, 17 Mar 2008 18:23:51 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JXW0060109FVR00@fe-emea-10.sun.com> (original mail from Amanda.Waite@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 18:23:51 +0000 (GMT) Received: from [192.168.1.22] (host86-157-61-51.range86-157.btcentralplus.com [86.157.61.51]) by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JXW000U10FHP410@fe-emea-10.sun.com>; Mon, 17 Mar 2008 18:23:46 +0000 (GMT) Date: Mon, 17 Mar 2008 18:22:17 +0000 From: Amanda Waite Subject: Re: [webstack-discuss] Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <20080317164622.GG4653@zruty.sfbay.sun.com> Sender: Amanda.Waite@sun.com To: Danek Duvall Cc: webstack-discuss@opensolaris.org, lsarc-ext@sun.com Message-id: <47DEB6D9.5060100@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> <20080313213010.GO24360@zruty.sfbay.sun.com> <20080317072953.GD4234@sun.com> <20080317164622.GG4653@zruty.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20080102) Status: RO Content-Length: 5867 Danek Duvall wrote: > > And I understand why those are that way. But I'm not asking about why it's > done in general (like you said, this isn't the apache case), but about this > particular case. Does lighthttpd need to be treated the same way? Is > there a rich community of end-user plugins for lighttpd the way there is > for php and apache? Is there binary incompatibility between releases that > will cause end-user plugins to break when we upgrade? Are there other > things that would go wrong? > > I'm not saying there isn't, but I don't know -- I'm not terribly familiar > with lighttpd. But I strongly get the sense that some teams are versioning > the installations because they don't actually want to do the work to find > out whether a) there actually are incompatibilities between the releases > they might conceivably ship, b) those incompatibilities are relevant to > customers and not something the distro can smooth over the transition, and > c) customers really will want more than one version at a time, rather than > making a jump. > We can't really work on the off chance that releases of Lighttpd will be compatible, this would actually need commitment from the Lighttpd community, some of which they are able to give us (still talking with them about this). Not knowing what incompatibilities might exist in future releases makes it difficult to understand what would be possible when it came to having the "distro smooth over the transition". As for c) we are trying to have customers come to OpenSolaris on the basis that Lighttpd is available and well integrated, we don't have the data point as to whether OpenSolaris customers will want to have more than one version currently. I can see the point in the argument that says "well, let's integrate Lighttpd without versioning and if necessary version at some point in the future". But if we integrate Lighttpd as 'lighttpd' (as uncommitted) then we are committing to support that version until the next minor release of Solaris, we would not be able to just move to a new but incompatible release through a solaris patch or update release. We would have to create a new package: lighttpd15 or lighttpd2 in order to make the new release available to end users. Of course this all comes back to "what do you mean by incompatible" and I would say that it means that when a user installs an upgrade release of Solaris or applies a Solaris patch, some functionality of Lighttpd is either broken or missing. This could be as simple as a syntax change in the config file, it may even be that some module that they relied on is removed in the new release (probably would have been deprecated first, but even if the user knew this it would still come as a surprise to find it gone). This is why versioning was felt to be necessary for this case, not because of any specific evidence of incompatibilities but because there are no guarantees that there won't be incompatibilities. The Lighttpd community have been great, we have been talking to them, although it's difficult to get all of them in one place at the same time. Jan who's replied on this thread has been talking to us about the compatibility of Lighttpd between releases and what the community could commit to. Based on this it's possible that we could delay versioning Lighttpd, but it really would only be a delay, because at some point we will hit incompatibilities that will require us to version Lighttpd, almost definitely with the next non-micro release. Thanks Amanda > Perhaps that analysis actually has been done, but I don't see any evidence > of it. > > >> They do it presumably for the same reasons several of the OpenSolaris >> project teams have felt the need, which is to provide stability within a >> given major release family while at the same time making the >> newer-generation apps available. >> > > I'd like to take the "presumably" out of that. If there's a real need for > the versioning, let's hear it. If there isn't, let's not do it. > > >>> Yup. I don't agree with the way Apache has been versioned, either, though >>> I understand why we delivered both 1.3 and 2.x for a while. Why we haven't >>> yet gotten rid of 1.3, or why we now ship two versions of 2.x is completely >>> beyond me. I think it's nuts. >>> >> There's only one apache22. apache1 is best thought of as a different >> product just sharing the same first name, still with its user base. >> > > I get that. But I do have SUNWapch2u and SUNWapch22u on my build 83 system > (the first delivering 2.2.3, the second 2.2.6). Perhaps the appropriate > pkghistory files haven't been delivered, so the older copy isn't being > removed? > > >> Anyway, this is not the apache case. >> > > I only brought it up because I didn't think a good decision had been made > there. Though the binary compatibility argument makes sense to me, as > long as there are enough customers for each version range with isolated > compatibility to make them worth supporting. That doesn't mean I don't > still think it's nuts that people are still using 1.3 how many years after > 2.x came out? > > >> Some of the OpenSolaris components have finer-grained versioning than in >> Linux, because the Solaris lifecycle and stability expectations are >> different. Uncommitted still means stable until the next minor release, >> which is a very long time. >> > > Unfortunately, the release taxonomy is being shredded at the moment. We > used to be able to say that until the in-development release (Nevada at the > moment) actually shipped, you could do pretty much anything you wanted, > including making incompatible change, and you were only locked in at > release. But no one's really sure what that means when you throw SXDE or > Indiana into the mix. > > Danek > From Amanda.Waite@sun.com Mon Mar 17 12:22:09 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2HJM90x023992 for ; Mon, 17 Mar 2008 12:22:09 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m2HJM7ej000642 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Mon, 17 Mar 2008 12:22:08 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXW00H2F34VVC00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 13:22:07 -0600 (MDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXW00L0O34T6NE0@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 13:22:06 -0600 (MDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m2HJM566002852 for ; Mon, 17 Mar 2008 19:22:05 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JXW008012X3WM00@fe-emea-09.sun.com> (original mail from Amanda.Waite@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 19:22:05 +0000 (GMT) Received: from [192.168.1.22] (host86-157-61-51.range86-157.btcentralplus.com [86.157.61.51]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JXW00E3H345N920@fe-emea-09.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 19:21:56 +0000 (GMT) Date: Mon, 17 Mar 2008 19:20:17 +0000 From: Amanda Waite Subject: Re: [webstack-discuss] Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <18398.43335.756976.976860@gargle.gargle.HOWL> Sender: Amanda.Waite@sun.com To: James Carlson Cc: webstack-discuss@opensolaris.org, lsarc-ext@sun.com Message-id: <47DEC471.3000803@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> <20080313213010.GO24360@zruty.sfbay.sun.com> <20080317072953.GD4234@sun.com> <20080317164622.GG4653@zruty.sfbay.sun.com> <18398.43335.756976.976860@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.6 (X11/20080102) Status: RO Content-Length: 1535 James Carlson wrote: > Danek Duvall writes: > >>> They do it presumably for the same reasons several of the OpenSolaris >>> project teams have felt the need, which is to provide stability within a >>> given major release family while at the same time making the >>> newer-generation apps available. >>> >> I'd like to take the "presumably" out of that. If there's a real need for >> the versioning, let's hear it. If there isn't, let's not do it. >> > > Having the path to the configuration files moving around from build to > build like Robert Brown's pollen grains is distinctly not helpful for > users. > > Please don't bake the version number into the path unless we _really_ > need it, and then do only the minimum distinction necessary to make > sure that the incompatible universe-has-changed transitions are > accomodated correctly. > > I've been thinking about the options, a single config file shared between multiple versions won't work if the user wanted to run more than one release simultaneously. If she copies the original and modifies it for use with the later version, she'd also have to modify the SMF method script for that later version. You would really need a separate config file delivered with each new Lighttpd release and an SMF method script that was setup accordingly. So would it be ok to deliver a versioned config file? say, lighttpd14.conf . It doesn't exactly address your issue, as it's not a whole lot different than providing a separate directory. Thanks Amanda From danek.duvall@sun.com Mon Mar 17 14:06:13 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2HL6DeG027205 for ; Mon, 17 Mar 2008 14:06:13 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m2HL6CT6000150 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Mon, 17 Mar 2008 14:06:13 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXW00B1L7YBE700@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 14:06:11 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXW00AMA7YA8S60@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 14:06:10 -0700 (PDT) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2HL6806034474; Mon, 17 Mar 2008 14:06:08 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m2HL68cw001471; Mon, 17 Mar 2008 14:06:08 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2/Submit) id m2HL68Jg001470; Mon, 17 Mar 2008 14:06:08 -0700 (PDT) Date: Mon, 17 Mar 2008 14:06:08 -0700 From: Danek Duvall Subject: Re: [webstack-discuss] Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <47DEC471.3000803@sun.com> To: Amanda Waite Cc: James Carlson , webstack-discuss@opensolaris.org, lsarc-ext@sun.com Message-id: <20080317210608.GC29238@zruty.sfbay.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> <20080313213010.GO24360@zruty.sfbay.sun.com> <20080317072953.GD4234@sun.com> <20080317164622.GG4653@zruty.sfbay.sun.com> <18398.43335.756976.976860@gargle.gargle.HOWL> <47DEC471.3000803@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 482 On Mon, Mar 17, 2008 at 07:20:17PM +0000, Amanda Waite wrote: > I've been thinking about the options, a single config file shared between > multiple versions won't work if the user wanted to run more than one > release simultaneously. You really need to have the main config file be an SMF config variable. That way not only can you run more than one release simultaneously, you can run multiple instances of the same release, which would be a nice thing to be able to do. Danek From jyri@buye.red.iplanet.com Mon Mar 17 17:25:04 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2I0P3PV007895 for ; Mon, 17 Mar 2008 17:25:04 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2I0OvdL000688; Tue, 18 Mar 2008 00:25:01 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXW00901H5M2I00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 17 Mar 2008 17:24:58 -0700 (PDT) Received: from buye.red.iplanet.com ([192.18.65.224]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXW000T6H5LLHE0@nwk-avmta-1.sfbay.Sun.COM>; Mon, 17 Mar 2008 17:24:58 -0700 (PDT) Received: from buye.red.iplanet.com (localhost [127.0.0.1]) by buye.red.iplanet.com (8.13.7+Sun/8.13.7) with ESMTP id m2I0HSJ6014386; Mon, 17 Mar 2008 17:17:28 -0700 (PDT) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id m2I0HSSB014385; Mon, 17 Mar 2008 17:17:28 -0700 (PDT) Date: Mon, 17 Mar 2008 17:17:28 -0700 From: Jyri Virkki Subject: Re: [webstack-discuss] Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <47DEC471.3000803@sun.com> <47DEB6D9.5060100@sun.com> <20080317164622.GG4653@zruty.sfbay.sun.com> To: Danek Duvall , Amanda Waite Cc: webstack-discuss@opensolaris.org, lsarc-ext@sun.com Message-id: <20080318001727.GB6542@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <20080313213010.GO24360@zruty.sfbay.sun.com> <20080317072953.GD4234@sun.com> <20080317164622.GG4653@zruty.sfbay.sun.com> <47DEB6D9.5060100@sun.com> <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> <20080313213010.GO24360@zruty.sfbay.sun.com> <20080317072953.GD4234@sun.com> <20080317164622.GG4653@zruty.sfbay.sun.com> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 2748 Danek Duvall wrote: > > I'm not saying there isn't, but I don't know -- I'm not terribly familiar > with lighttpd. But I strongly get the sense that some teams are versioning > the installations because they don't actually want to do the work to find > out whether a) there actually are incompatibilities between the releases > they might conceivably ship, b) those incompatibilities are relevant to > customers and not something the distro can smooth over the transition, and I know the project team has been working closely with the community so they should have a fairly good understanding of the expectations. Maybe Amanda & Jan can add some more info here. That said, not even Jan can predict the future of lighttpd interface compatibility 5-10 years down the road. > c) customers really will want more than one version at a time, rather than > making a jump. As to (c), I'll assert that very few customers are willing or able to do a sudden jump which breaks their configuration & modules & administrative familiarity. That's noncontroversial. That's why versioning and transition periods are the norm and a messy necessity. > > They do it presumably for the same reasons several of the OpenSolaris > > project teams have felt the need, which is to provide stability within a > > given major release family while at the same time making the > > newer-generation apps available. > > I'd like to take the "presumably" out of that. If there's a real need for > the versioning, let's hear it. If there isn't, let's not do it. "presumably" refers to "they" which is a pointer to the subject in the previous paragraph: debian. I don't speak for debian, so presumably it is. > Unfortunately, the release taxonomy is being shredded at the moment. We Yah. Most of these projects have interfaces better than volatile but not quite uncommitted. Whatever comes out of future models driven by Indiana etc will surely change some things. But meanwhile, project teams will need to continue to use the existing model so work can go on. Amanda Waite wrote: > > commit to. Based on this it's possible that we could delay versioning > Lighttpd, but it really would only be a delay, because at some point we > will hit incompatibilities that will require us to version Lighttpd, > almost definitely with the next non-micro release. Delaying versioning is messy (look at the troubles that apache22 went when adding versioned directories when previous apache2 didn't have it). You're much better off introducing versioning if you suspect it is needed. It's easier to transition off it if time shows you don't end up needing it than to retrofit it in later when you're in trouble. -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From danek.duvall@sun.com Mon Mar 17 21:58:02 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2I4w1kC015398 for ; Mon, 17 Mar 2008 21:58:01 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m2I4vtJR015182 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 18 Mar 2008 12:58:00 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXW00M03TSLSP00@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 21:57:57 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXW00IXJTSKA630@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 17 Mar 2008 21:57:56 -0700 (PDT) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2I4vtXD062696; Mon, 17 Mar 2008 21:57:55 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m2I4vtaF004716; Mon, 17 Mar 2008 21:57:55 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2/Submit) id m2I4vtbg004715; Mon, 17 Mar 2008 21:57:55 -0700 (PDT) Date: Mon, 17 Mar 2008 21:57:55 -0700 From: Danek Duvall Subject: Re: [webstack-discuss] Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <20080318001727.GB6542@sun.com> To: Jyri Virkki Cc: Amanda Waite , webstack-discuss@opensolaris.org, lsarc-ext@sun.com Message-id: <20080318045755.GD26870@zruty.sfbay.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <20080317072953.GD4234@sun.com> <20080317164622.GG4653@zruty.sfbay.sun.com> <47DEB6D9.5060100@sun.com> <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <20080313173935.GI24360@zruty.sfbay.sun.com> <47D986DB.1060602@sun.com> <20080313213010.GO24360@zruty.sfbay.sun.com> <20080317072953.GD4234@sun.com> <20080317164622.GG4653@zruty.sfbay.sun.com> <20080318001727.GB6542@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 162 Okay. I don't like the road we're walking down, but I'm not going to derail this case over it, and will let it time out tomorrow without further comment. Danek From jyri@buye.red.iplanet.com Tue Mar 18 09:36:50 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2IGanhP006827 for ; Tue, 18 Mar 2008 09:36:49 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m2IGaMaH000914; Wed, 19 Mar 2008 00:36:46 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXX00M2BQ53QH00@brm-avmta-1.central.sun.com>; Tue, 18 Mar 2008 10:36:39 -0600 (MDT) Received: from buye.red.iplanet.com ([192.18.65.224]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXX00HW1Q4RY170@brm-avmta-1.central.sun.com>; Tue, 18 Mar 2008 10:36:28 -0600 (MDT) Received: from buye.red.iplanet.com (localhost [127.0.0.1]) by buye.red.iplanet.com (8.13.7+Sun/8.13.7) with ESMTP id m2IGSvYR017332; Tue, 18 Mar 2008 09:28:57 -0700 (PDT) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id m2IGSvw9017331; Tue, 18 Mar 2008 09:28:57 -0700 (PDT) Date: Tue, 18 Mar 2008 09:28:57 -0700 From: Jyri Virkki Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <20080313064858.GA3598@sun.com> To: lsarc-ext@sun.com Cc: Amanda Waite , webstack-discuss@opensolaris.org Message-id: <20080318162857.GA17327@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <18390.37005.46160.674516@gargle.gargle.HOWL> <47D69BFB.1040005@sun.com> <18390.40271.143977.213986@gargle.gargle.HOWL> <47D6A24B.7090406@sun.com> <20080313064858.GA3598@sun.com> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 1328 I've updated the case materials with an updated spec from the project team. Full spec in case materials. Diffs, below. 176,178c176,178 < A Lighttpd Admin profile will be added to the system along with the < auths required to allow the Lighttpd Admin profile to manage the < lighttpd SMF service. --- > In order to allow non-root users to manage the Lighttpd SMF service > the following RBAC authorisations (auths) will be added to > /etc/security/auth_attr: 179a180,195 > solaris.smf.value.http/lighttpd14 > solaris.smf.manage.http/lighttpd14 > > A profile named "Lighttpd 14 Adminstrator" will be added to > /etc/security/prof_attr. > This Profile will only include the two authorisations specified above, > no additions will be made to /etc/security/exec_attr. > > The Profile will be supported by the addition to the SMF manifest for > svc:/network/http:lighttpd14 of the following properties: > > NAME TYPE VALUE > > action_authorization astring solaris.smf.manage.http/lighttpd14 > value_authorization astring solaris.smf.value.http/lighttpd14 -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From jyri@buye.red.iplanet.com Tue Mar 18 23:22:03 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m2J6M29U005842 for ; Tue, 18 Mar 2008 23:22:03 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m2J6LwAU010224; Wed, 19 Mar 2008 06:22:01 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JXY00F03SCOPT00@nwk-avmta-2.sfbay.sun.com>; Tue, 18 Mar 2008 23:22:00 -0700 (PDT) Received: from buye.red.iplanet.com ([192.18.65.224]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JXY0001USCNIZB0@nwk-avmta-2.sfbay.sun.com>; Tue, 18 Mar 2008 23:22:00 -0700 (PDT) Received: from buye.red.iplanet.com (localhost [127.0.0.1]) by buye.red.iplanet.com (8.13.7+Sun/8.13.7) with ESMTP id m2J6EUVK020503; Tue, 18 Mar 2008 23:14:30 -0700 (PDT) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id m2J6EUQg020502; Tue, 18 Mar 2008 23:14:30 -0700 (PDT) Date: Tue, 18 Mar 2008 23:14:30 -0700 From: Jyri Virkki Subject: Re: Deliver Lighttpd 1.4.x into OpenSolaris [LSARC/2008/191 FastTrack timeout 03/18/2008] In-reply-to: <20080318162857.GA17327@sun.com> To: lsarc-ext@sun.com Cc: Amanda Waite , webstack-discuss@opensolaris.org Message-id: <20080319061430.GA20496@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200803110625.m2B6P2EG006598@sac.sfbay.sun.com> <18390.37005.46160.674516@gargle.gargle.HOWL> <47D69BFB.1040005@sun.com> <18390.40271.143977.213986@gargle.gargle.HOWL> <47D6A24B.7090406@sun.com> <20080313064858.GA3598@sun.com> <20080318162857.GA17327@sun.com> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 172 This case timed out today (and was approved at ARC business this morning) so I've marked it closed approved. -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From Amanda.Waite@Sun.COM Fri Jun 20 07:52:02 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m5KEq2Xw026518 for ; Fri, 20 Jun 2008 07:52:02 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m5KEptKF051967 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Fri, 20 Jun 2008 08:52:02 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K2R00103NYO1A00@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 20 Jun 2008 07:52:01 -0700 (PDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K2R00KNMNYNPX40@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 20 Jun 2008 07:52:00 -0700 (PDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m5KEpxi1013824 for ; Fri, 20 Jun 2008 14:51:59 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K2R00K01NL22M00@fe-emea-10.sun.com> (original mail from Amanda.Waite@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 20 Jun 2008 15:51:59 +0100 (BST) Received: from [129.156.84.172] by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K2R002Q5NYLC070@fe-emea-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 20 Jun 2008 15:51:58 +0100 (BST) Date: Fri, 20 Jun 2008 15:51:57 +0100 From: Amanda Waite Subject: Updating lighttpd version [LSARC/2008/191] Sender: Amanda.Waite@Sun.COM To: lsarc-ext@Sun.COM Cc: Amanda Waite Message-id: <485BC40D.8060800@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.14 (X11/20080602) Status: RO Content-Length: 467 I propose that we switch the Lighttpd integration to Lighttpd v1.4.19 (from v1.4.18). I've looked at 1.4.19 in detail and it makes no changes to the interfaces that we committed to in the Arc case and is fully compatible with 1.4.18. BTW: The integration is not yet complete, but this will hopefully be the last step in getting it done. Thanks Amanda -- Amanda Waite ISV-Engineering OSS, Sun Microsystems Tel: +44 (0)1252 420693 Mobile: +44 (0)7802 175732 From danek.duvall@sun.com Fri Jun 20 09:16:23 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m5KGGN0Y029825 for ; Fri, 20 Jun 2008 09:16:23 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m5KGGLaP027963 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Fri, 20 Jun 2008 09:16:23 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K2R0040DRV9PO00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 20 Jun 2008 09:16:21 -0700 (PDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K2R0047CRV9EV00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 20 Jun 2008 09:16:21 -0700 (PDT) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m5KGGKx1032581; Fri, 20 Jun 2008 09:16:20 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m5KGGKJI010744; Fri, 20 Jun 2008 09:16:20 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2/Submit) id m5KGGKrj010743; Fri, 20 Jun 2008 09:16:20 -0700 (PDT) Date: Fri, 20 Jun 2008 09:16:19 -0700 From: Danek Duvall Subject: Re: Updating lighttpd version [LSARC/2008/191] In-reply-to: <485BC40D.8060800@sun.com> To: Amanda Waite Cc: lsarc-ext@sun.com Message-id: <20080620161619.GI1920@zruty.sfbay.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <485BC40D.8060800@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 452 On Fri, Jun 20, 2008 at 03:51:57PM +0100, Amanda Waite wrote: > I propose that we switch the Lighttpd integration to Lighttpd v1.4.19 (from > v1.4.18). I've looked at 1.4.19 in detail and it makes no changes to the > interfaces that we committed to in the Arc case and is fully compatible > with 1.4.18. If so, then it's just a bugfix and below the ARC's radar. Technically, it's an automatic approval case that needn't actually be filed. Danek From Amanda.Waite@sun.com Tue Jun 24 07:35:53 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m5OEZqba011012 for ; Tue, 24 Jun 2008 07:35:53 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m5OEZl5m019621 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 24 Jun 2008 22:35:52 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K2Z003191VP9N00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 24 Jun 2008 08:35:49 -0600 (MDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K2Z000K31VLL120@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 24 Jun 2008 08:35:46 -0600 (MDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m5OEZjq9004259 for ; Tue, 24 Jun 2008 14:35:45 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K2Z00G011IVQJ00@fe-emea-10.sun.com> (original mail from Amanda.Waite@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 24 Jun 2008 15:35:45 +0100 (BST) Received: from [129.156.84.172] by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K2Z00LNR1UZLB20@fe-emea-10.sun.com>; Tue, 24 Jun 2008 15:35:24 +0100 (BST) Date: Tue, 24 Jun 2008 15:35:23 +0100 From: Amanda Waite Subject: Re: Updating lighttpd version [LSARC/2008/191] In-reply-to: <20080620161619.GI1920@zruty.sfbay.sun.com> Sender: Amanda.Waite@sun.com To: lsarc-ext@sun.com Cc: Danek Duvall Message-id: <4861062B.2040807@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <485BC40D.8060800@sun.com> <20080620161619.GI1920@zruty.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080602) Status: RO Content-Length: 683 Thanks Danek, I've filed CR 6718409 to cover this change. Amanda Danek Duvall wrote: > On Fri, Jun 20, 2008 at 03:51:57PM +0100, Amanda Waite wrote: > > >> I propose that we switch the Lighttpd integration to Lighttpd v1.4.19 (from >> v1.4.18). I've looked at 1.4.19 in detail and it makes no changes to the >> interfaces that we committed to in the Arc case and is fully compatible >> with 1.4.18. >> > > If so, then it's just a bugfix and below the ARC's radar. Technically, > it's an automatic approval case that needn't actually be filed. > > Danek > -- Amanda Waite ISV-Engineering OSS, Sun Microsystems Tel: +44 (0)1252 420693 Mobile: +44 (0)7802 175732 From Amanda.Waite@sun.com Tue Jul 15 07:30:54 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m6FEUsfB012578 for ; Tue, 15 Jul 2008 07:30:54 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m6FEUpWi061448 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 15 Jul 2008 08:30:54 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K410072KXNGE300@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 15 Jul 2008 07:30:52 -0700 (PDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K4100JK0XNFHCC0@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 15 Jul 2008 07:30:51 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m6FEUocA023549 for ; Tue, 15 Jul 2008 14:30:50 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K4100G01WI0Y700@fe-emea-09.sun.com> (original mail from Amanda.Waite@Sun.COM) for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 15 Jul 2008 15:30:50 +0100 (BST) Received: from grond.UK.Sun.COM ([129.156.84.184]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K4100FGJXN60L50@fe-emea-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 15 Jul 2008 15:30:42 +0100 (BST) Date: Tue, 15 Jul 2008 15:30:41 +0100 From: Amanda Waite Subject: OpenSSL contract for Lighttpd [LSARC/2008/191] Sender: Amanda.Waite@sun.com To: psarc-ext@sun.com Message-id: <487CB491.8020205@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) Status: RO Content-Length: 326 The SFWNV C-Team tell me I need to get an Arc contract in order for Lighttpd to consume the OpenSSL interface [PSARC/2003/500]. This step was missed during the Arc approval. Could someone help me with this, I can see from other Arc approvals that this requires someone to create a numbered contract? Thanks Amanda Waite From gww@eng.sun.com Tue Jul 15 07:40:27 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m6FEeQ5i012662 for ; Tue, 15 Jul 2008 07:40:26 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m6FEeMMJ004862 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 15 Jul 2008 22:40:25 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K4100K0RY3BDW00@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 15 Jul 2008 07:40:23 -0700 (PDT) Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K4100GA4Y3A3I70@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 15 Jul 2008 07:40:22 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m6FEeLEj035318; Tue, 15 Jul 2008 07:40:21 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m6FEgDec010972; Tue, 15 Jul 2008 07:42:13 -0700 (PDT) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m6FEgDYD010971; Tue, 15 Jul 2008 07:42:13 -0700 (PDT) Date: Tue, 15 Jul 2008 07:42:13 -0700 (PDT) From: Gary Winiger Subject: Re: OpenSSL contract for Lighttpd [LSARC/2008/191] To: psarc-ext@sun.com, Amanda.Waite@sun.com Message-id: <200807151442.m6FEgDYD010971@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-Sun-Charset: US-ASCII X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 255 > Could someone help me with this, I can see from other Arc approvals that > this requires someone to create a numbered contract? Talk to your case owner. Use the approved contract template of 2003/500, substutiting Bugseter information for Bugtraq.