From sacadmin Fri Oct 19 00:57:45 2007 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 l9J7vjWG006749; Fri, 19 Oct 2007 00:57:45 -0700 (PDT) Received: (from jyri@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id l9J7vjbg006745; Fri, 19 Oct 2007 00:57:45 -0700 (PDT) Date: Fri, 19 Oct 2007 00:57:45 -0700 (PDT) From: Jyri Virkki Message-Id: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> To: LSARC@sac.sfbay.sun.com Cc: Ritu.Kamboj@Sun.COM, webstack-discuss@opensolaris.org Subject: Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] Status: RO Content-Length: 21562 I am sponsoring this fast track for Jan Berg, details below. Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI This information is Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Including MySQL 5.0 with Solaris 1.2. Name of Document Author/Supplier: Author: Jan Berg 1.3 Date of This Document: 19 October, 2007 4. Technical Description Including MySQL 5.0 with Solaris 18 October 2007 1. Summary and motivation 1.1. Introduction This FastTrack delivers MySQL 5.0 as a component in OpenSolaris sfw consolidation. From the MySQL HomePage [1], "The MySQL Server 5.0 software is the most reliable, secure and up-to-date version of the world's most popular open source database for cost-effectively delivering E-commerce, Online Transaction Processing (OLTP), and multi-terabyte Data Warehousing applications." MySQL Server 5.0 delivers new enterprise features, including: * ACID Transactions to build reliable and secure business critical applications * Stored Procedures to improve developer productivity * Triggers to enforce complex business rules at the database level * Views to ensure sensitive information is not compromised * Information Schema to provide easy access to metadata * Distributed Transactions (XA) to support complex transactions across multiple databases * Pluggable Storage Engine Architecture for maximum flexibility (Choosing between InnoDB, MyIsam, Archive, Federated and others) * Archive Storage Engine for historical and audit data * Federated Storage Engine to create a single logical database from many physical servers This FastTrack proposes the integration of the most recent stable release of MySQL 5.0 into OpenSolaris This case seeks Micro Release Binding. 1.2 Previous Relevant ARC cases LSARC/2004/324 - SIP Proxy Server LSARC/2004/541 - PHP with MySQL support 2. Technical issues 2.1. Key objects MySQL objects: /usr/mysql/5.0/bin/mysql - Command line toool /usr/mysql/5.0/bin/mysql_install_db - Install New DB /usr/mysql/5.0/bin/mysql_upgrade - upgrade tables tool /usr/mysql/5.0/bin/mysqladmin - Admin tool /usr/mysql/5.0/bin/mysqld - Server Deamon /usr/mysql/5.0/bin/mysqlimport - Import Data tool /usr/mysql/5.0/bin/mysqlmanager - Server Admin and Monitoring tool /etc/mysql/my.cnf - Default MySQL config file 2.2 Versioning The MySQL development processes follow the ubiquitous "continuous development" model, typical of many Open Source projects. Currently, version 5.0.45 is the latest stable release. MySQL 5.1 is under development, slated for release end of this year/early next year. The versioning model for MySQL is ... MySQL has fairly stable interfaces between releases. MySQL as a database is using standards like SQL, JDBC, and ODBC. MySQL also provides tools for upgrading the database tables between subversions (from 4.0->4.1, and 4.1->5.0, etc). 2.3 32 and 64 bit architectures. MySQL will be delivered with 32 bit architecture for binaries. We will consider delivering 64 bit in the future. 32 bit is what has to be supported as that can run on all architectures. 64 bit adds complexity to both install and user experience, and has more issues at this point. 2.4 APIs MySQL supports the following standard APIs: SQL92,SQL97,SQL2003 - Supports, but not fully compatible with all. See mysql.org for details. MySQL has also its own C client API which is delivered with the server. 2.5 Directory Naming and Structure The proposed directory layout for MySQL is /usr/mysql/5.0 /bin binaries and scripts /lib libraries for client API. /include header files for client API /man/man1 man-pages for client programs /man/man8 man-pages for server programs /mysql-test MySQL test programs /share/mysql I18N files, sample config files and utility scripts /sql-bench SQL Benchmark test /etc/mysql configuration file location /var/mysql /datadir default location for transactional log files, data files, and pid file The detailed directory and file layout for MySQL is provided in Addendum 1. /usr/mysql/ will expose bin, include, lib, man and share directories.These will be symbolic links to corresponding directories in the highest numbered . directory in /usr/mysql hence, users will be able to use "/usr/mysql/bin/mysqld" to invoke the most recent version. 2.6 Configuration and Enviroment settings. The MySQL server (bin/mysqld) and MySQL clients uses a configuration file to start. The search path for this configuration file is as follows: 1. /etc/mysql/my.cnf 2. $MYSQL_HOME/my.cnf 3. specified on command line with --defaults-extra-file= 4. in user home: ~/.my.cnf The MySQL programs will try the whole search path, and last will override the previous. More detailed can be found at: http://mysql.org/doc/refman/5.0/en/option-files.html We will provide a default config file: /etc/mysql/my.cnf And create the default data/log directory /var/mysql/datadir MySQL will be installed by default with user mysql and group mysql as done in the standard distribution. The default smf script will also start MySQL as mysql user. 2.7 SMF We will deliver smf metafile as well as a smf startup script. To run MySQL for the first time, the user has to run the mysql_install_db to create the system tables and has to set the database root user (admin) password. There will not be any smf properties available as all options can be given in the MySQL configuration file. 3. Storage Engines The MySQL server has several storage engines built in (specified when you create tables): InnoDB - ACID storage engine MyIsam - non-ACID storage engine Memory - main-memory based engine Merge - Merge equal MyIsam tables in one Example - Example or empty engine CSV - Text file based engine Archive - Large data volume engine Federated - Store data in remote databases Blackhole - Accepts, but does not store data. 4. MySQL Documentation MySQL comes with generic documentation in man page format. These will be placed in the /usr/mysql/5.0/man/man8 and man1 directories as done by the canonical distribution. In addition MySQL documentation is provided online [1]. 4.1. Manual Pages. MySQL provides a man page, which will be delivered in the appropriate man directory, [/usr/mysql/[.]/man], with an appropriate symbolic link from /usr/mysql/man. A symbolic link will be created from the standard Solaris man page location (/usr/share/man/man1/mysql.1) to /usr/mysql/[.]. 5. MySQL Internationalization Internationalization of error messages is provided by MySQL and the localized error messages are provided in /usr/mysql/share/mysql/ directory for each supported language. 6. Packaging and Delivery We propose to package MySQL under the following packages: SUNWmysql50u - [usr] Server package (including server deamon, C API, man pages, I18N) SUNWmysql50r - [root] (config,smf files and data directory) SUNWmysql50test - MySQL test packages Multiple versions can coexist, and are distinguished by the version (50 for version 5.0.*). MySQL tests and sql-bench directories are bundled in a separate package. It is not necessary for running MySQL as such, but a convenient package for users to run a simple performance test and some examples how to use the client api's. It is also part of the standard MySQL distribution. 7. MySQL Interfaces 7.1. Interface Stability MySQL is a mature product and the interfaces are stable and has been available for a long time in the open source community as well as an established product. As a database MySQL also supports the standard database interfaces (SQL92,SQL97,SQL2003). 7.2. Imported Interfaces MySQL imports interfaces from NAME STABILITY NOTES Perl5 Standard PSARC/1999/192 (used in scripts) 7.3. Exported Interfaces NAME STABILITY NOTES MySQL Server Committed Server command line options MySQL C API Committed C Client API Utilities Uncommited Database management utilities MySQL Server config file Committed Config file syntax MySQL Data/Log files Project Private Transactional Log and Data TCP listen port Project Private TCP Port used, default 3306 PID file Project Private database deamon pid file Error messages Not an interface I18N Translated Error Messages Error codes Committed Error codes svc:/network/mysql Committed FMRI /lib/svc/method/mysql-svc Project Private SMF service method script /var/svc/manifest/network/mysql.xml Project Private SMF Manifest Interfaces for MySQL have not been listed in previous ARC cases, so all interfaces are documented. The interfaces have existed for a long time in the MySQL community, and because of the amount of users we beleive the MySQL interfaces are fairly stable. With that said, we in Sun are not controlling their development. For the 5.0 release we don't expect changes in the interfaces. 8. References [1] http://www.mysql.org/ ================================================================ Addendum 1: MySQL Integration Directory and File Structure. 1. The following files are included in the MySQL integration (except the mysql-test and sql-bench files): /usr/mysql/5.0/README /usr/mysql/5.0/bin /usr/mysql/5.0/bin/comp_err /usr/mysql/5.0/bin/innochecksum /usr/mysql/5.0/bin/msql2mysql /usr/mysql/5.0/bin/my_print_defaults /usr/mysql/5.0/bin/myisam_ftdump /usr/mysql/5.0/bin/myisamchk /usr/mysql/5.0/bin/myisamlog /usr/mysql/5.0/bin/myisampack /usr/mysql/5.0/bin/mysql /usr/mysql/5.0/bin/mysql_client_test /usr/mysql/5.0/bin/mysql_config /usr/mysql/5.0/bin/mysql_convert_table_format /usr/mysql/5.0/bin/mysql_create_system_tables /usr/mysql/5.0/bin/mysql_explain_log /usr/mysql/5.0/bin/mysql_find_rows /usr/mysql/5.0/bin/mysql_fix_extensions /usr/mysql/5.0/bin/mysql_fix_privilege_tables /usr/mysql/5.0/bin/mysql_install_db /usr/mysql/5.0/bin/mysql_tableinfo /usr/mysql/5.0/bin/mysql_secure_installation /usr/mysql/5.0/bin/mysql_setpermission /usr/mysql/5.0/bin/mysql_tzinfo_to_sql /usr/mysql/5.0/bin/mysql_upgrade /usr/mysql/5.0/bin/mysql_upgrade_shell /usr/mysql/5.0/bin/mysql_waitpid /usr/mysql/5.0/bin/mysql_zap /usr/mysql/5.0/bin/mysqlaccess /usr/mysql/5.0/bin/mysqladmin /usr/mysql/5.0/bin/mysqlbinlog /usr/mysql/5.0/bin/mysqlbug /usr/mysql/5.0/bin/mysqlcheck /usr/mysql/5.0/bin/mysqld /usr/mysql/5.0/bin/mysqld_multi /usr/mysql/5.0/bin/mysqld_safe /usr/mysql/5.0/bin/mysqldump /usr/mysql/5.0/bin/mysqldumpslow /usr/mysql/5.0/bin/mysqlhotcopy /usr/mysql/5.0/bin/mysqlimport /usr/mysql/5.0/bin/mysqlmanager /usr/mysql/5.0/bin/mysqlshow /usr/mysql/5.0/bin/mysqltest /usr/mysql/5.0/bin/mysqltestmanager /usr/mysql/5.0/bin/mysqltestmanager-pwgen /usr/mysql/5.0/bin/mysqltestmanagerc /usr/mysql/5.0/bin/perror /usr/mysql/5.0/bin/replace /usr/mysql/5.0/bin/resolve_stack_dump /usr/mysql/5.0/bin/resolveip /usr/mysql/5.0/include /usr/mysql/5.0/include/mysql /usr/mysql/5.0/include/chardefs.h /usr/mysql/5.0/include/errmsg.h /usr/mysql/5.0/include/history.h /usr/mysql/5.0/include/keycache.h /usr/mysql/5.0/include/keymaps.h /usr/mysql/5.0/include/m_ctype.h /usr/mysql/5.0/include/m_string.h /usr/mysql/5.0/include/my_alloc.h /usr/mysql/5.0/include/my_config.h /usr/mysql/5.0/include/my_dbug.h /usr/mysql/5.0/include/my_dir.h /usr/mysql/5.0/include/my_getopt.h /usr/mysql/5.0/include/my_global.h /usr/mysql/5.0/include/my_list.h /usr/mysql/5.0/include/my_net.h /usr/mysql/5.0/include/my_no_pthread.h /usr/mysql/5.0/include/my_pthread.h /usr/mysql/5.0/include/my_semaphore.h /usr/mysql/5.0/include/my_sys.h /usr/mysql/5.0/include/my_xml.h /usr/mysql/5.0/include/mysql.h /usr/mysql/5.0/include/mysql_com.h /usr/mysql/5.0/include/mysql_embed.h /usr/mysql/5.0/include/raid.h /usr/mysql/5.0/include/mysql_time.h /usr/mysql/5.0/include/mysql_version.h /usr/mysql/5.0/include/mysqld_ername.h /usr/mysql/5.0/include/mysqld_error.h /usr/mysql/5.0/include/readline.h /usr/mysql/5.0/include/rlmbutil.h /usr/mysql/5.0/include/rlprivate.h /usr/mysql/5.0/include/rlshell.h /usr/mysql/5.0/include/rltypedefs.h /usr/mysql/5.0/include/sql_common.h /usr/mysql/5.0/include/sql_state.h /usr/mysql/5.0/include/sslopt-case.h /usr/mysql/5.0/include/sslopt-longopts.h /usr/mysql/5.0/include/sslopt-vars.h /usr/mysql/5.0/include/tilde.h /usr/mysql/5.0/include/typelib.h /usr/mysql/5.0/include/xmalloc.h /usr/mysql/5.0/lib /usr/mysql/5.0/lib/mysql /usr/mysql/5.0/lib/libdbug.a /usr/mysql/5.0/lib/libheap.a /usr/mysql/5.0/lib/libmyisam.a /usr/mysql/5.0/lib/libmyisammrg.a /usr/mysql/5.0/lib/libmysqlclient.a /usr/mysql/5.0/lib/libmysqlclient.la /usr/mysql/5.0/lib/libmysqlclient_r.a /usr/mysql/5.0/lib/libmysqlclient_r.la /usr/mysql/5.0/lib/libmystrings.a /usr/mysql/5.0/lib/libmysys.a /usr/mysql/5.0/lib/libvio.a /usr/mysql/5.0/lib/libz.a /usr/mysql/5.0/lib/libz.la /usr/mysql/5.0/man /usr/mysql/5.0/man/man1 /usr/mysql/5.0/man/man1/msql2mysql.1 /usr/mysql/5.0/man/man1/my_print_defaults.1 /usr/mysql/5.0/man/man1/myisam_ftdump.1 /usr/mysql/5.0/man/man1/myisamchk.1 /usr/mysql/5.0/man/man1/myisamlog.1 /usr/mysql/5.0/man/man1/myisampack.1 /usr/mysql/5.0/man/man1/mysql.1 /usr/mysql/5.0/man/man1/mysql.server.1 /usr/mysql/5.0/man/man1/mysql_config.1 /usr/mysql/5.0/man/man1/mysql_explain_log.1 /usr/mysql/5.0/man/man1/mysql_fix_privilege_tables.1 /usr/mysql/5.0/man/man1/mysql_tzinfo_to_sql.1 /usr/mysql/5.0/man/man1/mysql_upgrade.1 /usr/mysql/5.0/man/man1/mysql_zap.1 /usr/mysql/5.0/man/man1/mysqlaccess.1 /usr/mysql/5.0/man/man1/mysqladmin.1 /usr/mysql/5.0/man/man1/mysqlbinlog.1 /usr/mysql/5.0/man/man1/mysqlcheck.1 /usr/mysql/5.0/man/man1/mysqld_multi.1 /usr/mysql/5.0/man/man1/mysqldump.1 /usr/mysql/5.0/man/man1/mysqld_safe.1 /usr/mysql/5.0/man/man1/mysqlhotcopy.1 /usr/mysql/5.0/man/man1/mysqlimport.1 /usr/mysql/5.0/man/man1/mysqlman.1 /usr/mysql/5.0/man/man1/mysqlshow.1 /usr/mysql/5.0/man/man1/perror.1 /usr/mysql/5.0/man/man1/replace.1 /usr/mysql/5.0/man/man1/safe_mysqld.1 /usr/mysql/5.0/man/man8 /usr/mysql/5.0/man/man8/mysqld.8 /usr/mysql/5.0/man/man8/mysqlmanager.8 /usr/mysql/5.0/mysql-test /usr/mysql/5.0/share /usr/mysql/5.0/share/mysql /usr/mysql/5.0/share/binary-configure /usr/mysql/5.0/share/charsets /usr/mysql/5.0/share/charsets/Index.xml /usr/mysql/5.0/share/charsets/README /usr/mysql/5.0/share/charsets/armscii8.xml /usr/mysql/5.0/share/charsets/ascii.xml /usr/mysql/5.0/share/charsets/cp1250.xml /usr/mysql/5.0/share/charsets/cp1251.xml /usr/mysql/5.0/share/charsets/cp1256.xml /usr/mysql/5.0/share/charsets/cp1257.xml /usr/mysql/5.0/share/charsets/cp850.xml /usr/mysql/5.0/share/charsets/cp852.xml /usr/mysql/5.0/share/charsets/cp866.xml /usr/mysql/5.0/share/charsets/dec8.xml /usr/mysql/5.0/share/charsets/geostd8.xml /usr/mysql/5.0/share/charsets/greek.xml /usr/mysql/5.0/share/charsets/hebrew.xml /usr/mysql/5.0/share/charsets/hp8.xml /usr/mysql/5.0/share/charsets/keybcs2.xml /usr/mysql/5.0/share/charsets/koi8r.xml /usr/mysql/5.0/share/charsets/koi8u.xml /usr/mysql/5.0/share/charsets/latin1.xml /usr/mysql/5.0/share/charsets/latin2.xml /usr/mysql/5.0/share/charsets/latin5.xml /usr/mysql/5.0/share/charsets/latin7.xml /usr/mysql/5.0/share/charsets/macce.xml /usr/mysql/5.0/share/charsets/macroman.xml /usr/mysql/5.0/share/charsets/swe7.xml /usr/mysql/5.0/share/czech /usr/mysql/5.0/share/czech/errmsg.sys /usr/mysql/5.0/share/danish /usr/mysql/5.0/share/danish/errmsg.sys /usr/mysql/5.0/share/dutch /usr/mysql/5.0/share/dutch/errmsg.sys /usr/mysql/5.0/share/english /usr/mysql/5.0/share/english/errmsg.sys /usr/mysql/5.0/share/errmsg.txt /usr/mysql/5.0/share/estonian /usr/mysql/5.0/share/estonian/errmsg.sys /usr/mysql/5.0/share/fill_help_tables.sql /usr/mysql/5.0/share/french /usr/mysql/5.0/share/french/errmsg.sys /usr/mysql/5.0/share/german /usr/mysql/5.0/share/german/errmsg.sys /usr/mysql/5.0/share/greek /usr/mysql/5.0/share/greek/errmsg.sys /usr/mysql/5.0/share/hungarian /usr/mysql/5.0/share/hungarian/errmsg.sys /usr/mysql/5.0/share/italian /usr/mysql/5.0/share/italian/errmsg.sys /usr/mysql/5.0/share/japanese /usr/mysql/5.0/share/japanese/errmsg.sys /usr/mysql/5.0/share/korean /usr/mysql/5.0/share/korean/errmsg.sys /usr/mysql/5.0/share/mi_test_all /usr/mysql/5.0/share/mi_test_all.res /usr/mysql/5.0/share/my-huge.cnf /usr/mysql/5.0/share/my-innodb-heavy-4G.cnf /usr/mysql/5.0/share/my-large.cnf /usr/mysql/5.0/share/my-medium.cnf /usr/mysql/5.0/share/my-small.cnf /usr/mysql/5.0/share/polish /usr/mysql/5.0/share/polish/errmsg.sys /usr/mysql/5.0/share/mysql-log-rotate /usr/mysql/5.0/share/mysql.server /usr/mysql/5.0/share/mysql_fix_privilege_tables.sql /usr/mysql/5.0/share/ndb-config-2-node.ini /usr/mysql/5.0/share/norwegian /usr/mysql/5.0/share/norwegian/errmsg.sys /usr/mysql/5.0/share/norwegian-ny /usr/mysql/5.0/share/norwegian-ny/errmsg.sys /usr/mysql/5.0/share/portuguese /usr/mysql/5.0/share/portuguese/errmsg.sys /usr/mysql/5.0/share/romanian /usr/mysql/5.0/share/romanian/errmsg.sys /usr/mysql/5.0/share/russian /usr/mysql/5.0/share/russian/errmsg.sys /usr/mysql/5.0/share/serbian /usr/mysql/5.0/share/serbian/errmsg.sys /usr/mysql/5.0/share/slovak /usr/mysql/5.0/share/slovak/errmsg.sys /usr/mysql/5.0/share/spanish /usr/mysql/5.0/share/spanish/errmsg.sys /usr/mysql/5.0/share/swedish /usr/mysql/5.0/share/swedish/errmsg.sys /usr/mysql/5.0/share/ukrainian /usr/mysql/5.0/share/ukrainian/errmsg.sys /usr/mysql/5.0/sql-bench /usr/mysql/bin -> /usr/mysql/5.0/bin /usr/mysql/include -> /usr/mysql/5.0/include /usr/mysql/lib -> /usr/mysql/5.0/lib /usr/mysql/man -> /usr/mysql/5.0/man /usr/mysql/share -> /usr/mysql/5.0/share /usr/share/man/man1/msql2mysql.1 -> /usr/mysql/5.0/man/man1/msql2mysql.1 /usr/share/man/man1/my_print_defaults.1 -> /usr/mysql/5.0/man/man1/my_print_defaults.1 /usr/share/man/man1/myisam_ftdump.1 -> /usr/mysql/5.0/man/man1/myisam_ftdump.1 /usr/share/man/man1/myisamchk.1 -> /usr/mysql/5.0/man/man1/myisamchk.1 /usr/share/man/man1/myisamlog.1 -> /usr/mysql/5.0/man/man1/myisamlog.1 /usr/share/man/man1/myisampack.1 -> /usr/mysql/5.0/man/man1/myisampack.1 /usr/share/man/man1/mysql.1 -> /usr/mysql/5.0/man/man1/mysql.1 /usr/share/man/man1/mysql.server.1 -> /usr/mysql/5.0/man/man1/mysql.server.1 /usr/share/man/man1/mysql_config.1 -> /usr/mysql/5.0/man/man1/mysql_config.1 /usr/share/man/man1/mysql_explain_log.1 -> /usr/mysql/5.0/man/man1/mysql_explain_log.1 /usr/share/man/man1/mysql_fix_privilege_tables.1 -> /usr/mysql/5.0/man/man1/mysql_fix_privilege_tables.1 /usr/share/man/man1/mysql_tzinfo_to_sql.1 -> /usr/mysql/5.0/man/man1/mysql_tzinfo_to_sql.1 /usr/share/man/man1/mysql_upgrade.1 -> /usr/mysql/5.0/man/man1/mysql_upgrade.1 /usr/share/man/man1/mysql_zap.1 -> /usr/mysql/5.0/man/man1/mysql_zap.1 /usr/share/man/man1/mysqlaccess.1 -> /usr/mysql/5.0/man/man1/mysqlaccess.1 /usr/share/man/man1/mysqladmin.1 -> /usr/mysql/5.0/man/man1/mysqladmin.1 /usr/share/man/man1/mysqlbinlog.1 -> /usr/mysql/5.0/man/man1/mysqlbinlog.1 /usr/share/man/man1/mysqlcheck.1 -> /usr/mysql/5.0/man/man1/mysqlcheck.1 /usr/share/man/man1/mysqld_multi.1 -> /usr/mysql/5.0/man/man1/mysqld_multi.1 /usr/share/man/man1/mysqldump.1 -> /usr/mysql/5.0/man/man1/mysqldump.1 /usr/share/man/man1/mysqld_safe.1 -> /usr/mysql/5.0/man/man1/mysqld_safe.1 /usr/share/man/man1/mysqlhotcopy.1 -> /usr/mysql/5.0/man/man1/mysqlhotcopy.1 /usr/share/man/man1/mysqlimport.1 -> /usr/mysql/5.0/man/man1/mysqlimport.1 /usr/share/man/man1/mysqlman.1 -> /usr/mysql/5.0/man/man1/mysqlman.1 /usr/share/man/man1/mysqlshow.1 -> /usr/mysql/5.0/man/man1/mysqlshow.1 /usr/share/man/man1/perror.1 -> /usr/mysql/5.0/man/man1/perror.1 /usr/share/man/man1/replace.1 -> /usr/mysql/5.0/man/man1/replace.1 /usr/share/man/man1/safe_mysqld.1 -> /usr/mysql/5.0/man/man1/safe_mysqld.1 /usr/share/man/man8/mysqld.8 -> /usr/mysql/5.0/man/man8/mysqld.8 /usr/share/man/man8/mysqlmanager.8 -> /usr/mysql/5.0/man/man8/mysqlmanager.8 /etc/mysql/my.cnf /lib/svc/method/mysql-svc /var/svc/manifest/network/mysql.xml 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 John.Plocher@sun.com Fri Oct 19 06:33:34 2007 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 l9JDXXPh010875 for ; Fri, 19 Oct 2007 06:33: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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9JDTv7D025936 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 19 Oct 2007 14:30:09 +0100 (BST) 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 <0JQ500H09UU7UH00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Fri, 19 Oct 2007 06:30:07 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQ5001W6UU7WJ60@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Fri, 19 Oct 2007 06:30:07 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9JDU7fb009635 for ; Fri, 19 Oct 2007 06:30:07 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQ500N01UR80600@fe-sfbay-09.sun.com> (original mail from John.Plocher@Sun.COM) for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Fri, 19 Oct 2007 06:30:07 -0700 (PDT) Received: from wp668.local ([208.74.177.212]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQ500I8NUU6V220@fe-sfbay-09.sun.com> for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Fri, 19 Oct 2007 06:30:06 -0700 (PDT) Date: Fri, 19 Oct 2007 06:30:03 -0700 From: John Plocher Subject: Re: Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] Sender: John.Plocher@sun.com To: webstack-discuss@opensolaris.org, LSARC-ext@sun.com Message-id: <4718B15B.9080906@Sun.Com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_uZlhp3Y5i/Tb6yr7YfBR9g)" X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) Status: RO Content-Length: 25422 This is a multi-part message in MIME format. --Boundary_(ID_uZlhp3Y5i/Tb6yr7YfBR9g) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Jyri Virkki wrote: > I am sponsoring this fast track for Jan Berg, details below. > > > Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI > This information is Copyright 2007 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Including MySQL 5.0 with Solaris I don't see any reference to Connectors in this case - am I missing something? -John > http://dev.mysql.com/downloads/connector/ > MySQL offers standard database driver connectivity for using MySQL with > applications and tools that are compatible with industry standards ODBC > and JDBC. This enables MySQL to work easily with standard development > tools on Windows, Linux, Macintosh and Unix platforms. Any system that > works with ODBC or JDBC can use MySQL. > > * Connector/ODBC: Standardized database driver Windows, Linux, Mac OS X, and Unix platforms. > * Connector/J: Standardized database driver for Java platforms and development. > * Connector/MXJ: MBean for embedding the MySQL server in Java applications. > * MySQL native driver for PHP - mysqlnd: The MySQL native driver for PHP is an additional, alternative way to connect from PHP 6 to the MySQL Server 4.1 or newer. --Boundary_(ID_uZlhp3Y5i/Tb6yr7YfBR9g) Content-type: message/rfc822; name="Attached Message" Return-path: Received: from fe-sfbay-10.sun.com ([192.18.34.120]) by sfbay2-mail1.sfbay.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0JQ500CSYFAQ4A10@sfbay2-mail1.sfbay.sun.com> for plocher@sfbay2-mail1.sfbay.Sun.COM; Fri, 19 Oct 2007 00:54:26 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQ500401F6PD900@fe-sfbay-10.sun.com> for plocher@sfbay2-mail1.sfbay.Sun.COM (ORCPT plocher@sfbay2-mail1.sfbay.Sun.COM) ; Fri, 19 Oct 2007 00:54:26 -0700 (PDT) Received: from phys-sfbay2-2.sfbay.sun.com ([129.145.47.19]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0JQ500BNDFAQXUF0@fe-sfbay-10.sun.com> for plocher@sfbay2-mail1.sfbay.Sun.COM (ORCPT plocher@sfbay2-mail1.sfbay.Sun.COM) ; Fri, 19 Oct 2007 00:54:26 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by sfbay2-mail1.sfbay.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0JQ500CSWFAQ4A10@sfbay2-mail1.sfbay.sun.com> for plocher@sfbay2-mail1.sfbay.Sun.COM; Fri, 19 Oct 2007 00:54:26 -0700 (PDT) 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 l9J7sQjH042469; Fri, 19 Oct 2007 00:54:26 -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 l9J7vjWG006749; Fri, 19 Oct 2007 00:57:45 -0700 (PDT) Received: (from jyri@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id l9J7vjbg006745; Fri, 19 Oct 2007 00:57:45 -0700 (PDT) Date: Fri, 19 Oct 2007 00:57:45 -0700 (PDT) From: Jyri Virkki Subject: Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] To: LSARC@sac.sfbay.sun.com Cc: Ritu.Kamboj@Sun.COM, webstack-discuss@opensolaris.org Message-id: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> X-Envelope-from: John.Plocher@Sun.COM X-Envelope-to: LSARC-ext <@smarthost.sun.com:LSARC-ext@Sun.Com> MIME-version: 1.0 Content-type: TEXT/PLAIN Content-transfer-encoding: 7BIT Original-recipient: rfc822;plocher@sfbay2-mail1.sfbay.Sun.COM I am sponsoring this fast track for Jan Berg, details below. Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI This information is Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Including MySQL 5.0 with Solaris 1.2. Name of Document Author/Supplier: Author: Jan Berg 1.3 Date of This Document: 19 October, 2007 4. Technical Description Including MySQL 5.0 with Solaris 18 October 2007 1. Summary and motivation 1.1. Introduction This FastTrack delivers MySQL 5.0 as a component in OpenSolaris sfw consolidation. From the MySQL HomePage [1], "The MySQL Server 5.0 software is the most reliable, secure and up-to-date version of the world's most popular open source database for cost-effectively delivering E-commerce, Online Transaction Processing (OLTP), and multi-terabyte Data Warehousing applications." MySQL Server 5.0 delivers new enterprise features, including: * ACID Transactions to build reliable and secure business critical applications * Stored Procedures to improve developer productivity * Triggers to enforce complex business rules at the database level * Views to ensure sensitive information is not compromised * Information Schema to provide easy access to metadata * Distributed Transactions (XA) to support complex transactions across multiple databases * Pluggable Storage Engine Architecture for maximum flexibility (Choosing between InnoDB, MyIsam, Archive, Federated and others) * Archive Storage Engine for historical and audit data * Federated Storage Engine to create a single logical database from many physical servers This FastTrack proposes the integration of the most recent stable release of MySQL 5.0 into OpenSolaris This case seeks Micro Release Binding. 1.2 Previous Relevant ARC cases LSARC/2004/324 - SIP Proxy Server LSARC/2004/541 - PHP with MySQL support 2. Technical issues 2.1. Key objects MySQL objects: /usr/mysql/5.0/bin/mysql - Command line toool /usr/mysql/5.0/bin/mysql_install_db - Install New DB /usr/mysql/5.0/bin/mysql_upgrade - upgrade tables tool /usr/mysql/5.0/bin/mysqladmin - Admin tool /usr/mysql/5.0/bin/mysqld - Server Deamon /usr/mysql/5.0/bin/mysqlimport - Import Data tool /usr/mysql/5.0/bin/mysqlmanager - Server Admin and Monitoring tool /etc/mysql/my.cnf - Default MySQL config file 2.2 Versioning The MySQL development processes follow the ubiquitous "continuous development" model, typical of many Open Source projects. Currently, version 5.0.45 is the latest stable release. MySQL 5.1 is under development, slated for release end of this year/early next year. The versioning model for MySQL is ... MySQL has fairly stable interfaces between releases. MySQL as a database is using standards like SQL, JDBC, and ODBC. MySQL also provides tools for upgrading the database tables between subversions (from 4.0->4.1, and 4.1->5.0, etc). 2.3 32 and 64 bit architectures. MySQL will be delivered with 32 bit architecture for binaries. We will consider delivering 64 bit in the future. 32 bit is what has to be supported as that can run on all architectures. 64 bit adds complexity to both install and user experience, and has more issues at this point. 2.4 APIs MySQL supports the following standard APIs: SQL92,SQL97,SQL2003 - Supports, but not fully compatible with all. See mysql.org for details. MySQL has also its own C client API which is delivered with the server. 2.5 Directory Naming and Structure The proposed directory layout for MySQL is /usr/mysql/5.0 /bin binaries and scripts /lib libraries for client API. /include header files for client API /man/man1 man-pages for client programs /man/man8 man-pages for server programs /mysql-test MySQL test programs /share/mysql I18N files, sample config files and utility scripts /sql-bench SQL Benchmark test /etc/mysql configuration file location /var/mysql /datadir default location for transactional log files, data files, and pid file The detailed directory and file layout for MySQL is provided in Addendum 1. /usr/mysql/ will expose bin, include, lib, man and share directories.These will be symbolic links to corresponding directories in the highest numbered . directory in /usr/mysql hence, users will be able to use "/usr/mysql/bin/mysqld" to invoke the most recent version. 2.6 Configuration and Enviroment settings. The MySQL server (bin/mysqld) and MySQL clients uses a configuration file to start. The search path for this configuration file is as follows: 1. /etc/mysql/my.cnf 2. $MYSQL_HOME/my.cnf 3. specified on command line with --defaults-extra-file= 4. in user home: ~/.my.cnf The MySQL programs will try the whole search path, and last will override the previous. More detailed can be found at: http://mysql.org/doc/refman/5.0/en/option-files.html We will provide a default config file: /etc/mysql/my.cnf And create the default data/log directory /var/mysql/datadir MySQL will be installed by default with user mysql and group mysql as done in the standard distribution. The default smf script will also start MySQL as mysql user. 2.7 SMF We will deliver smf metafile as well as a smf startup script. To run MySQL for the first time, the user has to run the mysql_install_db to create the system tables and has to set the database root user (admin) password. There will not be any smf properties available as all options can be given in the MySQL configuration file. 3. Storage Engines The MySQL server has several storage engines built in (specified when you create tables): InnoDB - ACID storage engine MyIsam - non-ACID storage engine Memory - main-memory based engine Merge - Merge equal MyIsam tables in one Example - Example or empty engine CSV - Text file based engine Archive - Large data volume engine Federated - Store data in remote databases Blackhole - Accepts, but does not store data. 4. MySQL Documentation MySQL comes with generic documentation in man page format. These will be placed in the /usr/mysql/5.0/man/man8 and man1 directories as done by the canonical distribution. In addition MySQL documentation is provided online [1]. 4.1. Manual Pages. MySQL provides a man page, which will be delivered in the appropriate man directory, [/usr/mysql/[.]/man], with an appropriate symbolic link from /usr/mysql/man. A symbolic link will be created from the standard Solaris man page location (/usr/share/man/man1/mysql.1) to /usr/mysql/[.]. 5. MySQL Internationalization Internationalization of error messages is provided by MySQL and the localized error messages are provided in /usr/mysql/share/mysql/ directory for each supported language. 6. Packaging and Delivery We propose to package MySQL under the following packages: SUNWmysql50u - [usr] Server package (including server deamon, C API, man pages, I18N) SUNWmysql50r - [root] (config,smf files and data directory) SUNWmysql50test - MySQL test packages Multiple versions can coexist, and are distinguished by the version (50 for version 5.0.*). MySQL tests and sql-bench directories are bundled in a separate package. It is not necessary for running MySQL as such, but a convenient package for users to run a simple performance test and some examples how to use the client api's. It is also part of the standard MySQL distribution. 7. MySQL Interfaces 7.1. Interface Stability MySQL is a mature product and the interfaces are stable and has been available for a long time in the open source community as well as an established product. As a database MySQL also supports the standard database interfaces (SQL92,SQL97,SQL2003). 7.2. Imported Interfaces MySQL imports interfaces from NAME STABILITY NOTES Perl5 Standard PSARC/1999/192 (used in scripts) 7.3. Exported Interfaces NAME STABILITY NOTES MySQL Server Committed Server command line options MySQL C API Committed C Client API Utilities Uncommited Database management utilities MySQL Server config file Committed Config file syntax MySQL Data/Log files Project Private Transactional Log and Data TCP listen port Project Private TCP Port used, default 3306 PID file Project Private database deamon pid file Error messages Not an interface I18N Translated Error Messages Error codes Committed Error codes svc:/network/mysql Committed FMRI /lib/svc/method/mysql-svc Project Private SMF service method script /var/svc/manifest/network/mysql.xml Project Private SMF Manifest Interfaces for MySQL have not been listed in previous ARC cases, so all interfaces are documented. The interfaces have existed for a long time in the MySQL community, and because of the amount of users we beleive the MySQL interfaces are fairly stable. With that said, we in Sun are not controlling their development. For the 5.0 release we don't expect changes in the interfaces. 8. References [1] http://www.mysql.org/ ================================================================ Addendum 1: MySQL Integration Directory and File Structure. 1. The following files are included in the MySQL integration (except the mysql-test and sql-bench files): /usr/mysql/5.0/README /usr/mysql/5.0/bin /usr/mysql/5.0/bin/comp_err /usr/mysql/5.0/bin/innochecksum /usr/mysql/5.0/bin/msql2mysql /usr/mysql/5.0/bin/my_print_defaults /usr/mysql/5.0/bin/myisam_ftdump /usr/mysql/5.0/bin/myisamchk /usr/mysql/5.0/bin/myisamlog /usr/mysql/5.0/bin/myisampack /usr/mysql/5.0/bin/mysql /usr/mysql/5.0/bin/mysql_client_test /usr/mysql/5.0/bin/mysql_config /usr/mysql/5.0/bin/mysql_convert_table_format /usr/mysql/5.0/bin/mysql_create_system_tables /usr/mysql/5.0/bin/mysql_explain_log /usr/mysql/5.0/bin/mysql_find_rows /usr/mysql/5.0/bin/mysql_fix_extensions /usr/mysql/5.0/bin/mysql_fix_privilege_tables /usr/mysql/5.0/bin/mysql_install_db /usr/mysql/5.0/bin/mysql_tableinfo /usr/mysql/5.0/bin/mysql_secure_installation /usr/mysql/5.0/bin/mysql_setpermission /usr/mysql/5.0/bin/mysql_tzinfo_to_sql /usr/mysql/5.0/bin/mysql_upgrade /usr/mysql/5.0/bin/mysql_upgrade_shell /usr/mysql/5.0/bin/mysql_waitpid /usr/mysql/5.0/bin/mysql_zap /usr/mysql/5.0/bin/mysqlaccess /usr/mysql/5.0/bin/mysqladmin /usr/mysql/5.0/bin/mysqlbinlog /usr/mysql/5.0/bin/mysqlbug /usr/mysql/5.0/bin/mysqlcheck /usr/mysql/5.0/bin/mysqld /usr/mysql/5.0/bin/mysqld_multi /usr/mysql/5.0/bin/mysqld_safe /usr/mysql/5.0/bin/mysqldump /usr/mysql/5.0/bin/mysqldumpslow /usr/mysql/5.0/bin/mysqlhotcopy /usr/mysql/5.0/bin/mysqlimport /usr/mysql/5.0/bin/mysqlmanager /usr/mysql/5.0/bin/mysqlshow /usr/mysql/5.0/bin/mysqltest /usr/mysql/5.0/bin/mysqltestmanager /usr/mysql/5.0/bin/mysqltestmanager-pwgen /usr/mysql/5.0/bin/mysqltestmanagerc /usr/mysql/5.0/bin/perror /usr/mysql/5.0/bin/replace /usr/mysql/5.0/bin/resolve_stack_dump /usr/mysql/5.0/bin/resolveip /usr/mysql/5.0/include /usr/mysql/5.0/include/mysql /usr/mysql/5.0/include/chardefs.h /usr/mysql/5.0/include/errmsg.h /usr/mysql/5.0/include/history.h /usr/mysql/5.0/include/keycache.h /usr/mysql/5.0/include/keymaps.h /usr/mysql/5.0/include/m_ctype.h /usr/mysql/5.0/include/m_string.h /usr/mysql/5.0/include/my_alloc.h /usr/mysql/5.0/include/my_config.h /usr/mysql/5.0/include/my_dbug.h /usr/mysql/5.0/include/my_dir.h /usr/mysql/5.0/include/my_getopt.h /usr/mysql/5.0/include/my_global.h /usr/mysql/5.0/include/my_list.h /usr/mysql/5.0/include/my_net.h /usr/mysql/5.0/include/my_no_pthread.h /usr/mysql/5.0/include/my_pthread.h /usr/mysql/5.0/include/my_semaphore.h /usr/mysql/5.0/include/my_sys.h /usr/mysql/5.0/include/my_xml.h /usr/mysql/5.0/include/mysql.h /usr/mysql/5.0/include/mysql_com.h /usr/mysql/5.0/include/mysql_embed.h /usr/mysql/5.0/include/raid.h /usr/mysql/5.0/include/mysql_time.h /usr/mysql/5.0/include/mysql_version.h /usr/mysql/5.0/include/mysqld_ername.h /usr/mysql/5.0/include/mysqld_error.h /usr/mysql/5.0/include/readline.h /usr/mysql/5.0/include/rlmbutil.h /usr/mysql/5.0/include/rlprivate.h /usr/mysql/5.0/include/rlshell.h /usr/mysql/5.0/include/rltypedefs.h /usr/mysql/5.0/include/sql_common.h /usr/mysql/5.0/include/sql_state.h /usr/mysql/5.0/include/sslopt-case.h /usr/mysql/5.0/include/sslopt-longopts.h /usr/mysql/5.0/include/sslopt-vars.h /usr/mysql/5.0/include/tilde.h /usr/mysql/5.0/include/typelib.h /usr/mysql/5.0/include/xmalloc.h /usr/mysql/5.0/lib /usr/mysql/5.0/lib/mysql /usr/mysql/5.0/lib/libdbug.a /usr/mysql/5.0/lib/libheap.a /usr/mysql/5.0/lib/libmyisam.a /usr/mysql/5.0/lib/libmyisammrg.a /usr/mysql/5.0/lib/libmysqlclient.a /usr/mysql/5.0/lib/libmysqlclient.la /usr/mysql/5.0/lib/libmysqlclient_r.a /usr/mysql/5.0/lib/libmysqlclient_r.la /usr/mysql/5.0/lib/libmystrings.a /usr/mysql/5.0/lib/libmysys.a /usr/mysql/5.0/lib/libvio.a /usr/mysql/5.0/lib/libz.a /usr/mysql/5.0/lib/libz.la /usr/mysql/5.0/man /usr/mysql/5.0/man/man1 /usr/mysql/5.0/man/man1/msql2mysql.1 /usr/mysql/5.0/man/man1/my_print_defaults.1 /usr/mysql/5.0/man/man1/myisam_ftdump.1 /usr/mysql/5.0/man/man1/myisamchk.1 /usr/mysql/5.0/man/man1/myisamlog.1 /usr/mysql/5.0/man/man1/myisampack.1 /usr/mysql/5.0/man/man1/mysql.1 /usr/mysql/5.0/man/man1/mysql.server.1 /usr/mysql/5.0/man/man1/mysql_config.1 /usr/mysql/5.0/man/man1/mysql_explain_log.1 /usr/mysql/5.0/man/man1/mysql_fix_privilege_tables.1 /usr/mysql/5.0/man/man1/mysql_tzinfo_to_sql.1 /usr/mysql/5.0/man/man1/mysql_upgrade.1 /usr/mysql/5.0/man/man1/mysql_zap.1 /usr/mysql/5.0/man/man1/mysqlaccess.1 /usr/mysql/5.0/man/man1/mysqladmin.1 /usr/mysql/5.0/man/man1/mysqlbinlog.1 /usr/mysql/5.0/man/man1/mysqlcheck.1 /usr/mysql/5.0/man/man1/mysqld_multi.1 /usr/mysql/5.0/man/man1/mysqldump.1 /usr/mysql/5.0/man/man1/mysqld_safe.1 /usr/mysql/5.0/man/man1/mysqlhotcopy.1 /usr/mysql/5.0/man/man1/mysqlimport.1 /usr/mysql/5.0/man/man1/mysqlman.1 /usr/mysql/5.0/man/man1/mysqlshow.1 /usr/mysql/5.0/man/man1/perror.1 /usr/mysql/5.0/man/man1/replace.1 /usr/mysql/5.0/man/man1/safe_mysqld.1 /usr/mysql/5.0/man/man8 /usr/mysql/5.0/man/man8/mysqld.8 /usr/mysql/5.0/man/man8/mysqlmanager.8 /usr/mysql/5.0/mysql-test /usr/mysql/5.0/share /usr/mysql/5.0/share/mysql /usr/mysql/5.0/share/binary-configure /usr/mysql/5.0/share/charsets /usr/mysql/5.0/share/charsets/Index.xml /usr/mysql/5.0/share/charsets/README /usr/mysql/5.0/share/charsets/armscii8.xml /usr/mysql/5.0/share/charsets/ascii.xml /usr/mysql/5.0/share/charsets/cp1250.xml /usr/mysql/5.0/share/charsets/cp1251.xml /usr/mysql/5.0/share/charsets/cp1256.xml /usr/mysql/5.0/share/charsets/cp1257.xml /usr/mysql/5.0/share/charsets/cp850.xml /usr/mysql/5.0/share/charsets/cp852.xml /usr/mysql/5.0/share/charsets/cp866.xml /usr/mysql/5.0/share/charsets/dec8.xml /usr/mysql/5.0/share/charsets/geostd8.xml /usr/mysql/5.0/share/charsets/greek.xml /usr/mysql/5.0/share/charsets/hebrew.xml /usr/mysql/5.0/share/charsets/hp8.xml /usr/mysql/5.0/share/charsets/keybcs2.xml /usr/mysql/5.0/share/charsets/koi8r.xml /usr/mysql/5.0/share/charsets/koi8u.xml /usr/mysql/5.0/share/charsets/latin1.xml /usr/mysql/5.0/share/charsets/latin2.xml /usr/mysql/5.0/share/charsets/latin5.xml /usr/mysql/5.0/share/charsets/latin7.xml /usr/mysql/5.0/share/charsets/macce.xml /usr/mysql/5.0/share/charsets/macroman.xml /usr/mysql/5.0/share/charsets/swe7.xml /usr/mysql/5.0/share/czech /usr/mysql/5.0/share/czech/errmsg.sys /usr/mysql/5.0/share/danish /usr/mysql/5.0/share/danish/errmsg.sys /usr/mysql/5.0/share/dutch /usr/mysql/5.0/share/dutch/errmsg.sys /usr/mysql/5.0/share/english /usr/mysql/5.0/share/english/errmsg.sys /usr/mysql/5.0/share/errmsg.txt /usr/mysql/5.0/share/estonian /usr/mysql/5.0/share/estonian/errmsg.sys /usr/mysql/5.0/share/fill_help_tables.sql /usr/mysql/5.0/share/french /usr/mysql/5.0/share/french/errmsg.sys /usr/mysql/5.0/share/german /usr/mysql/5.0/share/german/errmsg.sys /usr/mysql/5.0/share/greek /usr/mysql/5.0/share/greek/errmsg.sys /usr/mysql/5.0/share/hungarian /usr/mysql/5.0/share/hungarian/errmsg.sys /usr/mysql/5.0/share/italian /usr/mysql/5.0/share/italian/errmsg.sys /usr/mysql/5.0/share/japanese /usr/mysql/5.0/share/japanese/errmsg.sys /usr/mysql/5.0/share/korean /usr/mysql/5.0/share/korean/errmsg.sys /usr/mysql/5.0/share/mi_test_all /usr/mysql/5.0/share/mi_test_all.res /usr/mysql/5.0/share/my-huge.cnf /usr/mysql/5.0/share/my-innodb-heavy-4G.cnf /usr/mysql/5.0/share/my-large.cnf /usr/mysql/5.0/share/my-medium.cnf /usr/mysql/5.0/share/my-small.cnf /usr/mysql/5.0/share/polish /usr/mysql/5.0/share/polish/errmsg.sys /usr/mysql/5.0/share/mysql-log-rotate /usr/mysql/5.0/share/mysql.server /usr/mysql/5.0/share/mysql_fix_privilege_tables.sql /usr/mysql/5.0/share/ndb-config-2-node.ini /usr/mysql/5.0/share/norwegian /usr/mysql/5.0/share/norwegian/errmsg.sys /usr/mysql/5.0/share/norwegian-ny /usr/mysql/5.0/share/norwegian-ny/errmsg.sys /usr/mysql/5.0/share/portuguese /usr/mysql/5.0/share/portuguese/errmsg.sys /usr/mysql/5.0/share/romanian /usr/mysql/5.0/share/romanian/errmsg.sys /usr/mysql/5.0/share/russian /usr/mysql/5.0/share/russian/errmsg.sys /usr/mysql/5.0/share/serbian /usr/mysql/5.0/share/serbian/errmsg.sys /usr/mysql/5.0/share/slovak /usr/mysql/5.0/share/slovak/errmsg.sys /usr/mysql/5.0/share/spanish /usr/mysql/5.0/share/spanish/errmsg.sys /usr/mysql/5.0/share/swedish /usr/mysql/5.0/share/swedish/errmsg.sys /usr/mysql/5.0/share/ukrainian /usr/mysql/5.0/share/ukrainian/errmsg.sys /usr/mysql/5.0/sql-bench /usr/mysql/bin -> /usr/mysql/5.0/bin /usr/mysql/include -> /usr/mysql/5.0/include /usr/mysql/lib -> /usr/mysql/5.0/lib /usr/mysql/man -> /usr/mysql/5.0/man /usr/mysql/share -> /usr/mysql/5.0/share /usr/share/man/man1/msql2mysql.1 -> /usr/mysql/5.0/man/man1/msql2mysql.1 /usr/share/man/man1/my_print_defaults.1 -> /usr/mysql/5.0/man/man1/my_print_defaults.1 /usr/share/man/man1/myisam_ftdump.1 -> /usr/mysql/5.0/man/man1/myisam_ftdump.1 /usr/share/man/man1/myisamchk.1 -> /usr/mysql/5.0/man/man1/myisamchk.1 /usr/share/man/man1/myisamlog.1 -> /usr/mysql/5.0/man/man1/myisamlog.1 /usr/share/man/man1/myisampack.1 -> /usr/mysql/5.0/man/man1/myisampack.1 /usr/share/man/man1/mysql.1 -> /usr/mysql/5.0/man/man1/mysql.1 /usr/share/man/man1/mysql.server.1 -> /usr/mysql/5.0/man/man1/mysql.server.1 /usr/share/man/man1/mysql_config.1 -> /usr/mysql/5.0/man/man1/mysql_config.1 /usr/share/man/man1/mysql_explain_log.1 -> /usr/mysql/5.0/man/man1/mysql_explain_log.1 /usr/share/man/man1/mysql_fix_privilege_tables.1 -> /usr/mysql/5.0/man/man1/mysql_fix_privilege_tables.1 /usr/share/man/man1/mysql_tzinfo_to_sql.1 -> /usr/mysql/5.0/man/man1/mysql_tzinfo_to_sql.1 /usr/share/man/man1/mysql_upgrade.1 -> /usr/mysql/5.0/man/man1/mysql_upgrade.1 /usr/share/man/man1/mysql_zap.1 -> /usr/mysql/5.0/man/man1/mysql_zap.1 /usr/share/man/man1/mysqlaccess.1 -> /usr/mysql/5.0/man/man1/mysqlaccess.1 /usr/share/man/man1/mysqladmin.1 -> /usr/mysql/5.0/man/man1/mysqladmin.1 /usr/share/man/man1/mysqlbinlog.1 -> /usr/mysql/5.0/man/man1/mysqlbinlog.1 /usr/share/man/man1/mysqlcheck.1 -> /usr/mysql/5.0/man/man1/mysqlcheck.1 /usr/share/man/man1/mysqld_multi.1 -> /usr/mysql/5.0/man/man1/mysqld_multi.1 /usr/share/man/man1/mysqldump.1 -> /usr/mysql/5.0/man/man1/mysqldump.1 /usr/share/man/man1/mysqld_safe.1 -> /usr/mysql/5.0/man/man1/mysqld_safe.1 /usr/share/man/man1/mysqlhotcopy.1 -> /usr/mysql/5.0/man/man1/mysqlhotcopy.1 /usr/share/man/man1/mysqlimport.1 -> /usr/mysql/5.0/man/man1/mysqlimport.1 /usr/share/man/man1/mysqlman.1 -> /usr/mysql/5.0/man/man1/mysqlman.1 /usr/share/man/man1/mysqlshow.1 -> /usr/mysql/5.0/man/man1/mysqlshow.1 /usr/share/man/man1/perror.1 -> /usr/mysql/5.0/man/man1/perror.1 /usr/share/man/man1/replace.1 -> /usr/mysql/5.0/man/man1/replace.1 /usr/share/man/man1/safe_mysqld.1 -> /usr/mysql/5.0/man/man1/safe_mysqld.1 /usr/share/man/man8/mysqld.8 -> /usr/mysql/5.0/man/man8/mysqld.8 /usr/share/man/man8/mysqlmanager.8 -> /usr/mysql/5.0/man/man8/mysqlmanager.8 /etc/mysql/my.cnf /lib/svc/method/mysql-svc /var/svc/manifest/network/mysql.xml 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 --Boundary_(ID_uZlhp3Y5i/Tb6yr7YfBR9g)-- From Jan.Berg@sun.com Fri Oct 19 09:38:03 2007 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 l9JGc3fF014107 for ; Fri, 19 Oct 2007 09:38:03 -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 l9JGYeLj001641 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 19 Oct 2007 09:34:40 -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 <0JQ6003113DRBL00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 19 Oct 2007 09:34:39 -0700 (PDT) Received: from gmp-eb-mail-2.sun.com ([192.18.6.24]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQ6002WE3DPQA40@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 19 Oct 2007 09:34:38 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9JGYaWq017966 for ; Fri, 19 Oct 2007 16:34:36 +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 <0JQ600I0136P2B00@fe-emea-09.sun.com> (original mail from Jan.Berg@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 19 Oct 2007 17:34:36 +0100 (BST) Received: from [192.168.1.101] ([84.49.205.209]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQ6004ND3DN8EC0@fe-emea-09.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 19 Oct 2007 17:34:36 +0100 (BST) Date: Fri, 19 Oct 2007 18:33:53 +0200 From: Jan S Berg Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <4718B15B.9080906@Sun.Com> Sender: Jan.Berg@sun.com To: John Plocher Cc: webstack-discuss@opensolaris.org, LSARC-ext@sun.com Message-id: <4718DC71.7020304@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <4718B15B.9080906@Sun.Com> User-Agent: Thunderbird 2.0.0.4 (X11/20070723) Status: RO Content-Length: 24794 Hi John, John Plocher wrote: > Jyri Virkki wrote: > > I am sponsoring this fast track for Jan Berg, details below. > > > > > > Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI > > This information is Copyright 2007 Sun Microsystems > > 1. Introduction > > 1.1. Project/Component Working Name: > > Including MySQL 5.0 with Solaris > > > I don't see any reference to Connectors in this case - am I missing > something? No, we are not delivering any connectors in this case, but that is something we want to do in the future. Any special connector you are interested in? Jan S > > -John > > >> http://dev.mysql.com/downloads/connector/ > >> MySQL offers standard database driver connectivity for using MySQL >> with applications and tools that are compatible with industry >> standards ODBC >> and JDBC. This enables MySQL to work easily with standard development >> tools on Windows, Linux, Macintosh and Unix platforms. Any system that >> works with ODBC or JDBC can use MySQL. >> >> * Connector/ODBC: Standardized database driver Windows, Linux, >> Mac OS X, and Unix platforms. >> * Connector/J: Standardized database driver for Java platforms >> and development. >> * Connector/MXJ: MBean for embedding the MySQL server in Java >> applications. >> * MySQL native driver for PHP - mysqlnd: The MySQL native driver >> for PHP is an additional, alternative way to connect from PHP 6 to >> the MySQL Server 4.1 or newer. > > ------------------------------------------------------------------------ > > Subject: > Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout > 10/26/2007] > From: > Jyri Virkki > Date: > Fri, 19 Oct 2007 00:57:45 -0700 (PDT) > To: > LSARC@sac.sfbay.sun.com > > To: > LSARC@sac.sfbay.sun.com > CC: > Ritu.Kamboj@Sun.COM, webstack-discuss@opensolaris.org > > > I am sponsoring this fast track for Jan Berg, details below. > > > Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI > This information is Copyright 2007 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Including MySQL 5.0 with Solaris > 1.2. Name of Document Author/Supplier: > Author: Jan Berg > 1.3 Date of This Document: > 19 October, 2007 > 4. Technical Description > > Including MySQL 5.0 with Solaris > 18 October 2007 > > 1. Summary and motivation > > 1.1. Introduction > > This FastTrack delivers MySQL 5.0 as a component in > OpenSolaris sfw consolidation. > > From the MySQL HomePage [1], "The MySQL Server 5.0 software > is the most reliable, secure and up-to-date version of the world's most > popular open source database for cost-effectively delivering E-commerce, > Online Transaction Processing (OLTP), and multi-terabyte Data Warehousing > applications." > > MySQL Server 5.0 delivers new enterprise features, including: > > * ACID Transactions to build reliable and secure business critical > applications > * Stored Procedures to improve developer productivity > * Triggers to enforce complex business rules at the database level > * Views to ensure sensitive information is not compromised > * Information Schema to provide easy access to metadata > * Distributed Transactions (XA) to support complex transactions across > multiple databases > * Pluggable Storage Engine Architecture for maximum flexibility > (Choosing between InnoDB, MyIsam, Archive, Federated and others) > * Archive Storage Engine for historical and audit data > * Federated Storage Engine to create a single logical database from > many physical servers > > This FastTrack proposes the integration of the most recent stable > release of MySQL 5.0 into OpenSolaris > > This case seeks Micro Release Binding. > > 1.2 Previous Relevant ARC cases > > LSARC/2004/324 - SIP Proxy Server > LSARC/2004/541 - PHP with MySQL support > > > 2. Technical issues > > 2.1. Key objects > > MySQL objects: > > /usr/mysql/5.0/bin/mysql - Command line toool > /usr/mysql/5.0/bin/mysql_install_db - Install New DB > /usr/mysql/5.0/bin/mysql_upgrade - upgrade tables tool > /usr/mysql/5.0/bin/mysqladmin - Admin tool > /usr/mysql/5.0/bin/mysqld - Server Deamon > /usr/mysql/5.0/bin/mysqlimport - Import Data tool > /usr/mysql/5.0/bin/mysqlmanager - Server Admin and Monitoring tool > /etc/mysql/my.cnf - Default MySQL config file > > 2.2 Versioning > > The MySQL development processes follow the ubiquitous "continuous > development" model, typical of many Open Source > projects. Currently, version 5.0.45 is the latest stable > release. MySQL 5.1 is under development, slated for release end of > this year/early next year. The versioning model for MySQL is > ... > > MySQL has fairly stable interfaces between releases. MySQL as a > database is using standards like SQL, JDBC, and ODBC. MySQL also > provides tools for upgrading the database tables between > subversions (from 4.0->4.1, and 4.1->5.0, etc). > > 2.3 32 and 64 bit architectures. > > MySQL will be delivered with 32 bit architecture for > binaries. We will consider delivering 64 bit in the future. > 32 bit is what has to be supported as that can run on all > architectures. 64 bit adds complexity to both install and > user experience, and has more issues at this point. > > 2.4 APIs > > MySQL supports the following standard APIs: > > SQL92,SQL97,SQL2003 - Supports, but not fully compatible with all. > See mysql.org for details. > MySQL has also its own C client API which is delivered with the > server. > > 2.5 Directory Naming and Structure > > The proposed directory layout for MySQL is > /usr/mysql/5.0 > /bin binaries and scripts > /lib libraries for client API. > /include header files for client API > /man/man1 man-pages for client programs > /man/man8 man-pages for server programs > /mysql-test MySQL test programs > /share/mysql I18N files, sample config files > and utility scripts > /sql-bench SQL Benchmark test > /etc/mysql configuration file location > /var/mysql > /datadir default location for transactional > log files, data files, and pid file > > The detailed directory and file layout for MySQL is provided in > Addendum 1. > > /usr/mysql/ will expose bin, include, lib, man and share > directories.These will be symbolic links to corresponding directories > in the highest numbered . directory in /usr/mysql > hence, users will be able to use "/usr/mysql/bin/mysqld" > to invoke the most recent version. > > 2.6 Configuration and Enviroment settings. > > The MySQL server (bin/mysqld) and MySQL clients uses a > configuration file to start. > > The search path for this configuration file is as follows: > 1. /etc/mysql/my.cnf > 2. $MYSQL_HOME/my.cnf > 3. specified on command line with --defaults-extra-file= > 4. in user home: ~/.my.cnf > > The MySQL programs will try the whole search path, and last will > override the previous. More detailed can be found at: > http://mysql.org/doc/refman/5.0/en/option-files.html > > We will provide a default config file: /etc/mysql/my.cnf And > create the default data/log directory /var/mysql/datadir > > MySQL will be installed by default with user mysql and group > mysql as done in the standard distribution. The default smf > script will also start MySQL as mysql user. > > 2.7 SMF > > We will deliver smf metafile as well as a smf startup script. > To run MySQL for the first time, the user has to run the > mysql_install_db to create the system tables and has to set > the database root user (admin) password. There will not be > any smf properties available as all options can be given > in the MySQL configuration file. > > 3. Storage Engines > > The MySQL server has several storage engines built in > (specified when you create tables): > InnoDB - ACID storage engine > MyIsam - non-ACID storage engine > Memory - main-memory based engine > Merge - Merge equal MyIsam tables in one > Example - Example or empty engine > CSV - Text file based engine > Archive - Large data volume engine > Federated - Store data in remote databases > Blackhole - Accepts, but does not store data. > > 4. MySQL Documentation > > MySQL comes with generic documentation in man page format. These > will be placed in the /usr/mysql/5.0/man/man8 and man1 directories > as done by the canonical distribution. In addition MySQL > documentation is provided online [1]. > > 4.1. Manual Pages. > > MySQL provides a man page, which will be delivered in the > appropriate man directory, > [/usr/mysql/[.]/man], with an appropriate > symbolic link from /usr/mysql/man. A symbolic link will be created > from the standard Solaris man page location > (/usr/share/man/man1/mysql.1) to > /usr/mysql/[.]. > > 5. MySQL Internationalization > > Internationalization of error messages is provided by MySQL and > the localized error messages are provided in > /usr/mysql/share/mysql/ directory for each supported > language. > > 6. Packaging and Delivery > > We propose to package MySQL under the following packages: > > SUNWmysql50u - [usr] Server package (including server > deamon, C API, man pages, I18N) > SUNWmysql50r - [root] (config,smf files > and data directory) > SUNWmysql50test - MySQL test packages > > Multiple versions can coexist, and are distinguished by the > version (50 for version 5.0.*). > > MySQL tests and sql-bench directories are bundled in a separate > package. It is not necessary for running MySQL as such, but > a convenient package for users to run a simple performance test > and some examples how to use the client api's. It is also part > of the standard MySQL distribution. > > > 7. MySQL Interfaces > > 7.1. Interface Stability > > MySQL is a mature product and the interfaces are stable and has > been available for a long time in the open source community as > well as an established product. As a database MySQL also supports > the standard database interfaces (SQL92,SQL97,SQL2003). > > 7.2. Imported Interfaces > > MySQL imports interfaces from > > NAME STABILITY NOTES > Perl5 Standard PSARC/1999/192 (used in scripts) > > 7.3. Exported Interfaces > > NAME STABILITY NOTES > > MySQL Server Committed Server command line options > MySQL C API Committed C Client API > Utilities Uncommited Database management utilities > MySQL Server config file Committed Config file syntax > MySQL Data/Log files Project Private Transactional Log and Data > TCP listen port Project Private TCP Port used, default 3306 > PID file Project Private database deamon pid file > Error messages Not an interface I18N Translated Error Messages > Error codes Committed Error codes > svc:/network/mysql Committed FMRI > /lib/svc/method/mysql-svc Project Private SMF service method script > /var/svc/manifest/network/mysql.xml > Project Private SMF Manifest > > Interfaces for MySQL have not been listed in previous ARC cases, > so all interfaces are documented. The interfaces have existed > for a long time in the MySQL community, and because of the amount > of users we beleive the MySQL interfaces are fairly stable. With > that said, we in Sun are not controlling their development. For the > 5.0 release we don't expect changes in the interfaces. > > 8. References > > [1] http://www.mysql.org/ > > > ================================================================ > Addendum 1: MySQL Integration Directory and File Structure. > > 1. The following files are included in the MySQL integration > (except the mysql-test and sql-bench files): > > /usr/mysql/5.0/README > /usr/mysql/5.0/bin > /usr/mysql/5.0/bin/comp_err > /usr/mysql/5.0/bin/innochecksum > /usr/mysql/5.0/bin/msql2mysql > /usr/mysql/5.0/bin/my_print_defaults > /usr/mysql/5.0/bin/myisam_ftdump > /usr/mysql/5.0/bin/myisamchk > /usr/mysql/5.0/bin/myisamlog > /usr/mysql/5.0/bin/myisampack > /usr/mysql/5.0/bin/mysql > /usr/mysql/5.0/bin/mysql_client_test > /usr/mysql/5.0/bin/mysql_config > /usr/mysql/5.0/bin/mysql_convert_table_format > /usr/mysql/5.0/bin/mysql_create_system_tables > /usr/mysql/5.0/bin/mysql_explain_log > /usr/mysql/5.0/bin/mysql_find_rows > /usr/mysql/5.0/bin/mysql_fix_extensions > /usr/mysql/5.0/bin/mysql_fix_privilege_tables > /usr/mysql/5.0/bin/mysql_install_db > /usr/mysql/5.0/bin/mysql_tableinfo > /usr/mysql/5.0/bin/mysql_secure_installation > /usr/mysql/5.0/bin/mysql_setpermission > /usr/mysql/5.0/bin/mysql_tzinfo_to_sql > /usr/mysql/5.0/bin/mysql_upgrade > /usr/mysql/5.0/bin/mysql_upgrade_shell > /usr/mysql/5.0/bin/mysql_waitpid > /usr/mysql/5.0/bin/mysql_zap > /usr/mysql/5.0/bin/mysqlaccess > /usr/mysql/5.0/bin/mysqladmin > /usr/mysql/5.0/bin/mysqlbinlog > /usr/mysql/5.0/bin/mysqlbug > /usr/mysql/5.0/bin/mysqlcheck > /usr/mysql/5.0/bin/mysqld > /usr/mysql/5.0/bin/mysqld_multi > /usr/mysql/5.0/bin/mysqld_safe > /usr/mysql/5.0/bin/mysqldump > /usr/mysql/5.0/bin/mysqldumpslow > /usr/mysql/5.0/bin/mysqlhotcopy > /usr/mysql/5.0/bin/mysqlimport > /usr/mysql/5.0/bin/mysqlmanager > /usr/mysql/5.0/bin/mysqlshow > /usr/mysql/5.0/bin/mysqltest > /usr/mysql/5.0/bin/mysqltestmanager > /usr/mysql/5.0/bin/mysqltestmanager-pwgen > /usr/mysql/5.0/bin/mysqltestmanagerc > /usr/mysql/5.0/bin/perror > /usr/mysql/5.0/bin/replace > /usr/mysql/5.0/bin/resolve_stack_dump > /usr/mysql/5.0/bin/resolveip > /usr/mysql/5.0/include > /usr/mysql/5.0/include/mysql > /usr/mysql/5.0/include/chardefs.h > /usr/mysql/5.0/include/errmsg.h > /usr/mysql/5.0/include/history.h > /usr/mysql/5.0/include/keycache.h > /usr/mysql/5.0/include/keymaps.h > /usr/mysql/5.0/include/m_ctype.h > /usr/mysql/5.0/include/m_string.h > /usr/mysql/5.0/include/my_alloc.h > /usr/mysql/5.0/include/my_config.h > /usr/mysql/5.0/include/my_dbug.h > /usr/mysql/5.0/include/my_dir.h > /usr/mysql/5.0/include/my_getopt.h > /usr/mysql/5.0/include/my_global.h > /usr/mysql/5.0/include/my_list.h > /usr/mysql/5.0/include/my_net.h > /usr/mysql/5.0/include/my_no_pthread.h > /usr/mysql/5.0/include/my_pthread.h > /usr/mysql/5.0/include/my_semaphore.h > /usr/mysql/5.0/include/my_sys.h > /usr/mysql/5.0/include/my_xml.h > /usr/mysql/5.0/include/mysql.h > /usr/mysql/5.0/include/mysql_com.h > /usr/mysql/5.0/include/mysql_embed.h > /usr/mysql/5.0/include/raid.h > /usr/mysql/5.0/include/mysql_time.h > /usr/mysql/5.0/include/mysql_version.h > /usr/mysql/5.0/include/mysqld_ername.h > /usr/mysql/5.0/include/mysqld_error.h > /usr/mysql/5.0/include/readline.h > /usr/mysql/5.0/include/rlmbutil.h > /usr/mysql/5.0/include/rlprivate.h > /usr/mysql/5.0/include/rlshell.h > /usr/mysql/5.0/include/rltypedefs.h > /usr/mysql/5.0/include/sql_common.h > /usr/mysql/5.0/include/sql_state.h > /usr/mysql/5.0/include/sslopt-case.h > /usr/mysql/5.0/include/sslopt-longopts.h > /usr/mysql/5.0/include/sslopt-vars.h > /usr/mysql/5.0/include/tilde.h > /usr/mysql/5.0/include/typelib.h > /usr/mysql/5.0/include/xmalloc.h > /usr/mysql/5.0/lib > /usr/mysql/5.0/lib/mysql > /usr/mysql/5.0/lib/libdbug.a > /usr/mysql/5.0/lib/libheap.a > /usr/mysql/5.0/lib/libmyisam.a > /usr/mysql/5.0/lib/libmyisammrg.a > /usr/mysql/5.0/lib/libmysqlclient.a > /usr/mysql/5.0/lib/libmysqlclient.la > /usr/mysql/5.0/lib/libmysqlclient_r.a > /usr/mysql/5.0/lib/libmysqlclient_r.la > /usr/mysql/5.0/lib/libmystrings.a > /usr/mysql/5.0/lib/libmysys.a > /usr/mysql/5.0/lib/libvio.a > /usr/mysql/5.0/lib/libz.a > /usr/mysql/5.0/lib/libz.la > /usr/mysql/5.0/man > /usr/mysql/5.0/man/man1 > /usr/mysql/5.0/man/man1/msql2mysql.1 > /usr/mysql/5.0/man/man1/my_print_defaults.1 > /usr/mysql/5.0/man/man1/myisam_ftdump.1 > /usr/mysql/5.0/man/man1/myisamchk.1 > /usr/mysql/5.0/man/man1/myisamlog.1 > /usr/mysql/5.0/man/man1/myisampack.1 > /usr/mysql/5.0/man/man1/mysql.1 > /usr/mysql/5.0/man/man1/mysql.server.1 > /usr/mysql/5.0/man/man1/mysql_config.1 > /usr/mysql/5.0/man/man1/mysql_explain_log.1 > /usr/mysql/5.0/man/man1/mysql_fix_privilege_tables.1 > /usr/mysql/5.0/man/man1/mysql_tzinfo_to_sql.1 > /usr/mysql/5.0/man/man1/mysql_upgrade.1 > /usr/mysql/5.0/man/man1/mysql_zap.1 > /usr/mysql/5.0/man/man1/mysqlaccess.1 > /usr/mysql/5.0/man/man1/mysqladmin.1 > /usr/mysql/5.0/man/man1/mysqlbinlog.1 > /usr/mysql/5.0/man/man1/mysqlcheck.1 > /usr/mysql/5.0/man/man1/mysqld_multi.1 > /usr/mysql/5.0/man/man1/mysqldump.1 > /usr/mysql/5.0/man/man1/mysqld_safe.1 > /usr/mysql/5.0/man/man1/mysqlhotcopy.1 > /usr/mysql/5.0/man/man1/mysqlimport.1 > /usr/mysql/5.0/man/man1/mysqlman.1 > /usr/mysql/5.0/man/man1/mysqlshow.1 > /usr/mysql/5.0/man/man1/perror.1 > /usr/mysql/5.0/man/man1/replace.1 > /usr/mysql/5.0/man/man1/safe_mysqld.1 > /usr/mysql/5.0/man/man8 > /usr/mysql/5.0/man/man8/mysqld.8 > /usr/mysql/5.0/man/man8/mysqlmanager.8 > /usr/mysql/5.0/mysql-test > /usr/mysql/5.0/share > /usr/mysql/5.0/share/mysql > /usr/mysql/5.0/share/binary-configure > /usr/mysql/5.0/share/charsets > /usr/mysql/5.0/share/charsets/Index.xml > /usr/mysql/5.0/share/charsets/README > /usr/mysql/5.0/share/charsets/armscii8.xml > /usr/mysql/5.0/share/charsets/ascii.xml > /usr/mysql/5.0/share/charsets/cp1250.xml > /usr/mysql/5.0/share/charsets/cp1251.xml > /usr/mysql/5.0/share/charsets/cp1256.xml > /usr/mysql/5.0/share/charsets/cp1257.xml > /usr/mysql/5.0/share/charsets/cp850.xml > /usr/mysql/5.0/share/charsets/cp852.xml > /usr/mysql/5.0/share/charsets/cp866.xml > /usr/mysql/5.0/share/charsets/dec8.xml > /usr/mysql/5.0/share/charsets/geostd8.xml > /usr/mysql/5.0/share/charsets/greek.xml > /usr/mysql/5.0/share/charsets/hebrew.xml > /usr/mysql/5.0/share/charsets/hp8.xml > /usr/mysql/5.0/share/charsets/keybcs2.xml > /usr/mysql/5.0/share/charsets/koi8r.xml > /usr/mysql/5.0/share/charsets/koi8u.xml > /usr/mysql/5.0/share/charsets/latin1.xml > /usr/mysql/5.0/share/charsets/latin2.xml > /usr/mysql/5.0/share/charsets/latin5.xml > /usr/mysql/5.0/share/charsets/latin7.xml > /usr/mysql/5.0/share/charsets/macce.xml > /usr/mysql/5.0/share/charsets/macroman.xml > /usr/mysql/5.0/share/charsets/swe7.xml > /usr/mysql/5.0/share/czech > /usr/mysql/5.0/share/czech/errmsg.sys > /usr/mysql/5.0/share/danish > /usr/mysql/5.0/share/danish/errmsg.sys > /usr/mysql/5.0/share/dutch > /usr/mysql/5.0/share/dutch/errmsg.sys > /usr/mysql/5.0/share/english > /usr/mysql/5.0/share/english/errmsg.sys > /usr/mysql/5.0/share/errmsg.txt > /usr/mysql/5.0/share/estonian > /usr/mysql/5.0/share/estonian/errmsg.sys > /usr/mysql/5.0/share/fill_help_tables.sql > /usr/mysql/5.0/share/french > /usr/mysql/5.0/share/french/errmsg.sys > /usr/mysql/5.0/share/german > /usr/mysql/5.0/share/german/errmsg.sys > /usr/mysql/5.0/share/greek > /usr/mysql/5.0/share/greek/errmsg.sys > /usr/mysql/5.0/share/hungarian > /usr/mysql/5.0/share/hungarian/errmsg.sys > /usr/mysql/5.0/share/italian > /usr/mysql/5.0/share/italian/errmsg.sys > /usr/mysql/5.0/share/japanese > /usr/mysql/5.0/share/japanese/errmsg.sys > /usr/mysql/5.0/share/korean > /usr/mysql/5.0/share/korean/errmsg.sys > /usr/mysql/5.0/share/mi_test_all > /usr/mysql/5.0/share/mi_test_all.res > /usr/mysql/5.0/share/my-huge.cnf > /usr/mysql/5.0/share/my-innodb-heavy-4G.cnf > /usr/mysql/5.0/share/my-large.cnf > /usr/mysql/5.0/share/my-medium.cnf > /usr/mysql/5.0/share/my-small.cnf > /usr/mysql/5.0/share/polish > /usr/mysql/5.0/share/polish/errmsg.sys > /usr/mysql/5.0/share/mysql-log-rotate > /usr/mysql/5.0/share/mysql.server > /usr/mysql/5.0/share/mysql_fix_privilege_tables.sql > /usr/mysql/5.0/share/ndb-config-2-node.ini > /usr/mysql/5.0/share/norwegian > /usr/mysql/5.0/share/norwegian/errmsg.sys > /usr/mysql/5.0/share/norwegian-ny > /usr/mysql/5.0/share/norwegian-ny/errmsg.sys > /usr/mysql/5.0/share/portuguese > /usr/mysql/5.0/share/portuguese/errmsg.sys > /usr/mysql/5.0/share/romanian > /usr/mysql/5.0/share/romanian/errmsg.sys > /usr/mysql/5.0/share/russian > /usr/mysql/5.0/share/russian/errmsg.sys > /usr/mysql/5.0/share/serbian > /usr/mysql/5.0/share/serbian/errmsg.sys > /usr/mysql/5.0/share/slovak > /usr/mysql/5.0/share/slovak/errmsg.sys > /usr/mysql/5.0/share/spanish > /usr/mysql/5.0/share/spanish/errmsg.sys > /usr/mysql/5.0/share/swedish > /usr/mysql/5.0/share/swedish/errmsg.sys > /usr/mysql/5.0/share/ukrainian > /usr/mysql/5.0/share/ukrainian/errmsg.sys > /usr/mysql/5.0/sql-bench > > /usr/mysql/bin -> > /usr/mysql/5.0/bin > /usr/mysql/include -> > /usr/mysql/5.0/include > /usr/mysql/lib -> > /usr/mysql/5.0/lib > /usr/mysql/man -> > /usr/mysql/5.0/man > /usr/mysql/share -> > /usr/mysql/5.0/share > > /usr/share/man/man1/msql2mysql.1 -> > /usr/mysql/5.0/man/man1/msql2mysql.1 > /usr/share/man/man1/my_print_defaults.1 -> > /usr/mysql/5.0/man/man1/my_print_defaults.1 > /usr/share/man/man1/myisam_ftdump.1 -> > /usr/mysql/5.0/man/man1/myisam_ftdump.1 > /usr/share/man/man1/myisamchk.1 -> > /usr/mysql/5.0/man/man1/myisamchk.1 > /usr/share/man/man1/myisamlog.1 -> > /usr/mysql/5.0/man/man1/myisamlog.1 > /usr/share/man/man1/myisampack.1 -> > /usr/mysql/5.0/man/man1/myisampack.1 > /usr/share/man/man1/mysql.1 -> > /usr/mysql/5.0/man/man1/mysql.1 > /usr/share/man/man1/mysql.server.1 -> > /usr/mysql/5.0/man/man1/mysql.server.1 > /usr/share/man/man1/mysql_config.1 -> > /usr/mysql/5.0/man/man1/mysql_config.1 > /usr/share/man/man1/mysql_explain_log.1 -> > /usr/mysql/5.0/man/man1/mysql_explain_log.1 > /usr/share/man/man1/mysql_fix_privilege_tables.1 -> > /usr/mysql/5.0/man/man1/mysql_fix_privilege_tables.1 > /usr/share/man/man1/mysql_tzinfo_to_sql.1 -> > /usr/mysql/5.0/man/man1/mysql_tzinfo_to_sql.1 > /usr/share/man/man1/mysql_upgrade.1 -> > /usr/mysql/5.0/man/man1/mysql_upgrade.1 > /usr/share/man/man1/mysql_zap.1 -> > /usr/mysql/5.0/man/man1/mysql_zap.1 > /usr/share/man/man1/mysqlaccess.1 -> > /usr/mysql/5.0/man/man1/mysqlaccess.1 > /usr/share/man/man1/mysqladmin.1 -> > /usr/mysql/5.0/man/man1/mysqladmin.1 > /usr/share/man/man1/mysqlbinlog.1 -> > /usr/mysql/5.0/man/man1/mysqlbinlog.1 > /usr/share/man/man1/mysqlcheck.1 -> > /usr/mysql/5.0/man/man1/mysqlcheck.1 > /usr/share/man/man1/mysqld_multi.1 -> > /usr/mysql/5.0/man/man1/mysqld_multi.1 > /usr/share/man/man1/mysqldump.1 -> > /usr/mysql/5.0/man/man1/mysqldump.1 > /usr/share/man/man1/mysqld_safe.1 -> > /usr/mysql/5.0/man/man1/mysqld_safe.1 > /usr/share/man/man1/mysqlhotcopy.1 -> > /usr/mysql/5.0/man/man1/mysqlhotcopy.1 > /usr/share/man/man1/mysqlimport.1 -> > /usr/mysql/5.0/man/man1/mysqlimport.1 > /usr/share/man/man1/mysqlman.1 -> > /usr/mysql/5.0/man/man1/mysqlman.1 > /usr/share/man/man1/mysqlshow.1 -> > /usr/mysql/5.0/man/man1/mysqlshow.1 > /usr/share/man/man1/perror.1 -> > /usr/mysql/5.0/man/man1/perror.1 > /usr/share/man/man1/replace.1 -> > /usr/mysql/5.0/man/man1/replace.1 > /usr/share/man/man1/safe_mysqld.1 -> > /usr/mysql/5.0/man/man1/safe_mysqld.1 > /usr/share/man/man8/mysqld.8 -> > /usr/mysql/5.0/man/man8/mysqld.8 > /usr/share/man/man8/mysqlmanager.8 -> > /usr/mysql/5.0/man/man8/mysqlmanager.8 > > /etc/mysql/my.cnf > > /lib/svc/method/mysql-svc > /var/svc/manifest/network/mysql.xml > > > 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 > > > ------------------------------------------------------------------------ > > _______________________________________________ > webstack-discuss mailing list > webstack-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss > From sacadmin Mon Oct 22 11:03:10 2007 Received: from zruty.sfbay.sun.com (zruty [129.146.168.40]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9MI3Ade011868; Mon, 22 Oct 2007 11:03:10 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9MHxi6M020958; Mon, 22 Oct 2007 10:59:44 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id l9MHxijN020957; Mon, 22 Oct 2007 10:59:44 -0700 (PDT) Date: Mon, 22 Oct 2007 10:59:43 -0700 From: Danek Duvall To: Jyri Virkki Cc: LSARC@sac.sfbay.sun.com, Ritu.Kamboj@sun.com, webstack-discuss@opensolaris.org Subject: Re: Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] Message-ID: <20071022175943.GJ1976@zruty.sfbay.sun.com> References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 2244 On Fri, Oct 19, 2007 at 12:57:45AM -0700, Jyri Virkki wrote: > The proposed directory layout for MySQL is > /usr/mysql/5.0 > /bin binaries and scripts > /lib libraries for client API. > /include header files for client API > /man/man1 man-pages for client programs > /man/man8 man-pages for server programs > /mysql-test MySQL test programs > /share/mysql I18N files, sample config files > and utility scripts > /sql-bench SQL Benchmark test > /etc/mysql configuration file location > /var/mysql > /datadir default location for transactional > log files, data files, and pid file You say that multiple versions of mysql can exist on the system at the same time, and the versioning in /usr/mysql supports that. But you don't have any versioning in /etc/mysql or /var/mysql. Are multiple versions expected to share those directories? Also, would it make sense to put links to some of the executables (maybe just mysql?) in /usr/bin? > 7.3. Exported Interfaces > > NAME STABILITY NOTES > > svc:/network/mysql Committed FMRI You might want to follow postrgres' lead here and use svc:/application/database/mysql Are you planning on having an SMF instance per version, once there are multiple versions? > /usr/mysql/5.0/lib/libdbug.a > /usr/mysql/5.0/lib/libheap.a > /usr/mysql/5.0/lib/libmyisam.a > /usr/mysql/5.0/lib/libmyisammrg.a > /usr/mysql/5.0/lib/libmysqlclient.a > /usr/mysql/5.0/lib/libmysqlclient.la > /usr/mysql/5.0/lib/libmysqlclient_r.a > /usr/mysql/5.0/lib/libmysqlclient_r.la > /usr/mysql/5.0/lib/libmystrings.a > /usr/mysql/5.0/lib/libmysys.a > /usr/mysql/5.0/lib/libvio.a > /usr/mysql/5.0/lib/libz.a > /usr/mysql/5.0/lib/libz.la Why are you delivering .a files? And what use are .la files on Solaris? Danek From sacadmin Mon Oct 22 11:40:59 2007 Received: from sfbaymail1sca.SFBay.Sun.COM (sfbaymail1sca [129.145.154.35]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9MIexNs013194; Mon, 22 Oct 2007 11:40:59 -0700 (PDT) Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l9MIbXxp028078; Mon, 22 Oct 2007 11:37:33 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9MIbStw020451; Mon, 22 Oct 2007 11:37:28 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQB00901SE8JB00@fe-sfbay-09.sun.com> (original mail from Josh.Berkus@Sun.COM); Mon, 22 Oct 2007 11:37:28 -0700 (PDT) Received: from [192.168.1.27] ([64.81.245.111]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQB009CTT2C0270@fe-sfbay-09.sun.com>; Mon, 22 Oct 2007 11:37:26 -0700 (PDT) Date: Mon, 22 Oct 2007 11:39:47 -0700 From: Josh Berkus Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 =?iso-8859-1?q?FastTrack=09timeout?= 10/26/2007] In-reply-to: <20071022175943.GJ1976@zruty.sfbay.sun.com> Sender: Josh.Berkus@Sun.COM To: webstack-discuss@opensolaris.org Cc: Danek Duvall , Jyri Virkki , Ritu.Kamboj@Sun.COM, LSARC@sac.sfbay.sun.com Message-id: <200710221139.48625.josh.berkus@sun.com> Organization: PostgreSQL @ Sun MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-disposition: inline References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> User-Agent: KMail/1.8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by sac.sfbay.sun.com id l9MIexNt013195 Status: RO Content-Length: 461 Danek, > You say that multiple versions of mysql can exist on the system at the > same time, and the versioning in /usr/mysql supports that.  But you > don't have any versioning in /etc/mysql or /var/mysql.  Are multiple > versions expected to share those directories? We should version those directories as well. /var/postgres is being versioned, and it would be consistent. -- Josh Berkus PostgreSQL Lead Sun Microsystems San Francisco 01-415-752-2500 From sacadmin Mon Oct 22 16:07:12 2007 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9MN7CDO020293; Mon, 22 Oct 2007 16:07:12 -0700 (PDT) Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id l9MN3k0E060664; Mon, 22 Oct 2007 16:03:46 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9MN3fBj023712; Mon, 22 Oct 2007 16:03:41 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQC00M0152XFE00@fe-sfbay-09.sun.com> (original mail from Ritu.Kamboj@Sun.COM); Mon, 22 Oct 2007 16:03:41 -0700 (PDT) Received: from [129.145.154.107] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQC00DJH5E33960@fe-sfbay-09.sun.com>; Mon, 22 Oct 2007 16:03:39 -0700 (PDT) Date: Mon, 22 Oct 2007 16:03:39 -0700 From: Ritu Kamboj Subject: Re: Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071022175943.GJ1976@zruty.sfbay.sun.com> Sender: Ritu.Kamboj@Sun.COM To: Danek Duvall Cc: Jyri Virkki , LSARC@sac.sfbay.sun.com, webstack-discuss@opensolaris.org Reply-to: Ritu.Kamboj@Sun.COM Message-id: <471D2C4B.3040209@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20070109 Status: RO Content-Length: 2955 Danek Duvall wrote: >On Fri, Oct 19, 2007 at 12:57:45AM -0700, Jyri Virkki wrote: > > > >> The proposed directory layout for MySQL is >> /usr/mysql/5.0 >> /bin binaries and scripts >> /lib libraries for client API. >> /include header files for client API >> /man/man1 man-pages for client programs >> /man/man8 man-pages for server programs >> /mysql-test MySQL test programs >> /share/mysql I18N files, sample config files >> and utility scripts >> /sql-bench SQL Benchmark test >> /etc/mysql configuration file location >> /var/mysql >> /datadir default location for transactional >> log files, data files, and pid file >> >> > >You say that multiple versions of mysql can exist on the system at the same >time, and the versioning in /usr/mysql supports that. But you don't have >any versioning in /etc/mysql or /var/mysql. Are multiple versions expected >to share those directories? > >Also, would it make sense to put links to some of the executables (maybe >just mysql?) in /usr/bin? > > We shall be having version directory under both /var and /etc directory (ie /var/mysql/5.0/data and /etc/mysql/5.0. We shall be having a symbolic link from /usr/mysql/5.0 to /usr/mysql. We can possible link just the client mysql to /usr/bin as well. Shall update the ARC case to reflect the same. >> 7.3. Exported Interfaces >> >> NAME STABILITY NOTES >> >> svc:/network/mysql Committed FMRI >> >> > >You might want to follow postrgres' lead here and use > > svc:/application/database/mysql > >Are you planning on having an SMF instance per version, once there are >multiple versions? > > To be consistent with Postgress , we shall make the change you suggested wrt SMF. Yes the goal is to have SMF instance per version. > > >>/usr/mysql/5.0/lib/libdbug.a >>/usr/mysql/5.0/lib/libheap.a >>/usr/mysql/5.0/lib/libmyisam.a >>/usr/mysql/5.0/lib/libmyisammrg.a >>/usr/mysql/5.0/lib/libmysqlclient.a >>/usr/mysql/5.0/lib/libmysqlclient.la >>/usr/mysql/5.0/lib/libmysqlclient_r.a >>/usr/mysql/5.0/lib/libmysqlclient_r.la >>/usr/mysql/5.0/lib/libmystrings.a >>/usr/mysql/5.0/lib/libmysys.a >>/usr/mysql/5.0/lib/libvio.a >>/usr/mysql/5.0/lib/libz.a >>/usr/mysql/5.0/lib/libz.la >> >> > >Why are you delivering .a files? And what use are .la files on Solaris? > > The MYSQL release area does not have shared library version for all the libraries ...we are providing all the libraries that are provided in the default MySQL release area. Danek From sacadmin Tue Oct 23 01:59:37 2007 Received: from sfbaymail2sca.sfbay.sun.com (sfbaymail2sca [129.145.155.42]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9N8xbX1000795; Tue, 23 Oct 2007 01:59:37 -0700 (PDT) Received: from gmp-eb-mail-2.sun.com (gmp-eb-mail-2.EU.Sun.COM [192.18.6.24]) by sfbaymail2sca.sfbay.sun.com (8.13.6+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id l9N8u92K012436; Tue, 23 Oct 2007 01:56:10 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10]) by gmp-eb-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9N8u3x2006198; Tue, 23 Oct 2007 08:56:04 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 <0JQC00H01WBXUP00@fe-emea-09.sun.com> (original mail from Lars.Heill@Sun.COM); Tue, 23 Oct 2007 09:56:03 +0100 (BST) Received: from [129.159.112.186] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQC003OHWSPPT10@fe-emea-09.sun.com>; Tue, 23 Oct 2007 09:55:38 +0100 (BST) Date: Tue, 23 Oct 2007 10:55:36 +0200 From: Lars Heill Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <471D2C4B.3040209@sun.com> Sender: Lars.Heill@Sun.COM To: Ritu.Kamboj@Sun.COM Cc: Danek Duvall , LSARC@sac.sfbay.sun.com, webstack-discuss@opensolaris.org, Jyri Virkki Message-id: <471DB708.4050309@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20070802) Status: RO Content-Length: 881 Ritu Kamboj wrote, On 10/23/07 01:03: >>> >> You say that multiple versions of mysql can exist on the system at the same >> time, and the versioning in /usr/mysql supports that. But you don't have >> any versioning in /etc/mysql or /var/mysql. Are multiple versions expected >> to share those directories? >> >> Also, would it make sense to put links to some of the executables (maybe >> just mysql?) in /usr/bin? > > We shall be having version directory under both /var and /etc directory > (ie /var/mysql/5.0/data and /etc/mysql/5.0. We shall be having a > symbolic link from /usr/mysql/5.0 to /usr/mysql. We can possible link > just the client mysql to /usr/bin as well. Shall update the ARC case to > reflect the same. What will be the stability of these soft links? I.e, will a later install (of an older or a newer version) replace them or preserve them? -- Lars From sacadmin Tue Oct 23 10:25:23 2007 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9NHPN9M013951; Tue, 23 Oct 2007 10:25:23 -0700 (PDT) Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id l9NHLtE9050285; Tue, 23 Oct 2007 10:21:55 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9NHLoqX011885; Tue, 23 Oct 2007 10:21:50 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQD00601IRW1B00@fe-sfbay-09.sun.com> (original mail from Ritu.Kamboj@Sun.COM); Tue, 23 Oct 2007 10:21:50 -0700 (PDT) Received: from [129.145.154.107] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQD00DMRK89FHG0@fe-sfbay-09.sun.com>; Tue, 23 Oct 2007 10:21:46 -0700 (PDT) Date: Tue, 23 Oct 2007 10:21:45 -0700 From: Ritu Kamboj Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <471DB708.4050309@sun.com> Sender: Ritu.Kamboj@Sun.COM To: Lars Heill Cc: Danek Duvall , LSARC@sac.sfbay.sun.com, webstack-discuss@opensolaris.org, Jyri Virkki Reply-to: Ritu.Kamboj@Sun.COM Message-id: <471E2DA9.8090606@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <471DB708.4050309@sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20070109 Status: RO Content-Length: 1114 Lars Heill wrote: > Ritu Kamboj wrote, On 10/23/07 01:03: > >>>> >>> You say that multiple versions of mysql can exist on the system at >>> the same >>> time, and the versioning in /usr/mysql supports that. But you don't >>> have >>> any versioning in /etc/mysql or /var/mysql. Are multiple versions >>> expected >>> to share those directories? >>> >>> Also, would it make sense to put links to some of the executables >>> (maybe >>> just mysql?) in /usr/bin? >> >> >> We shall be having version directory under both /var and /etc >> directory (ie /var/mysql/5.0/data and /etc/mysql/5.0. We shall be >> having a symbolic link from /usr/mysql/5.0 to /usr/mysql. We can >> possible link just the client mysql to /usr/bin as well. Shall update >> the ARC case to reflect the same. > > > What will be the stability of these soft links? I.e, will a later > install > (of an older or a newer version) replace them or preserve them? /usr/local/mysql will be linked to the lastest version ...so going forward when we have higher version this link will be upgraded to the higher version. > > -- Lars > > From sacadmin Tue Oct 23 10:39:42 2007 Received: from sfbaymail1sca.SFBay.Sun.COM (sfbaymail1sca [129.145.154.35]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9NHdgSh014589; Tue, 23 Oct 2007 10:39:42 -0700 (PDT) Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l9NHaFqD023352; Tue, 23 Oct 2007 10:36:15 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9NHa9m7020778; Tue, 23 Oct 2007 10:36:09 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQD00J01KUQ8H00@fe-sfbay-10.sun.com> (original mail from Josh.Berkus@Sun.COM); Tue, 23 Oct 2007 10:36:09 -0700 (PDT) Received: from [192.168.2.3] ([63.195.55.98]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQD0019EKW82170@fe-sfbay-10.sun.com>; Tue, 23 Oct 2007 10:36:08 -0700 (PDT) Date: Tue, 23 Oct 2007 10:37:31 -0700 From: Josh Berkus Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 =?iso-8859-1?q?FastTrack=09timeout?= 10/26/2007] In-reply-to: <471D2C4B.3040209@sun.com> Sender: Josh.Berkus@Sun.COM To: webstack-discuss@opensolaris.org, Ritu.Kamboj@Sun.COM Cc: Danek Duvall , LSARC@sac.sfbay.sun.com, Jyri Virkki Message-id: <200710231037.31926.josh.berkus@sun.com> Organization: Postgres @ Sun MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> User-Agent: KMail/1.8.2 Status: RO Content-Length: 341 Ritu, > To be consistent with Postgress , we shall make the change you suggested > wrt SMF. Yes the goal is to have SMF instance per version. But all one SMF file, yes? So we'd have one mysql.xml, but services would be application-database-mysql:version_50 -- Josh Berkus PostgreSQL Lead Sun Microsystems San Francisco 01-415-752-2500 From sacadmin Tue Oct 23 10:57:22 2007 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9NHvM6h015688; Tue, 23 Oct 2007 10:57:22 -0700 (PDT) Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id l9NHrskZ003298; Tue, 23 Oct 2007 10:53:54 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9NHrnmA016285; Tue, 23 Oct 2007 10:53:49 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQD00601IRW1B00@fe-sfbay-09.sun.com> (original mail from Ritu.Kamboj@Sun.COM); Tue, 23 Oct 2007 10:53:49 -0700 (PDT) Received: from [129.145.154.107] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQD00MBPLPJNBF0@fe-sfbay-09.sun.com>; Tue, 23 Oct 2007 10:53:44 -0700 (PDT) Date: Tue, 23 Oct 2007 10:53:43 -0700 From: Ritu Kamboj Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <200710231037.31926.josh.berkus@sun.com> Sender: Ritu.Kamboj@Sun.COM To: Josh Berkus Cc: webstack-discuss@opensolaris.org, Danek Duvall , LSARC@sac.sfbay.sun.com, Jyri Virkki Reply-to: Ritu.Kamboj@Sun.COM Message-id: <471E3527.8010000@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <200710231037.31926.josh.berkus@sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20070109 Status: RO Content-Length: 419 Josh Berkus wrote: >Ritu, > > > >>To be consistent with Postgress , we shall make the change you suggested >>wrt SMF. Yes the goal is to have SMF instance per version. >> >> > >But all one SMF file, yes? So we'd have one mysql.xml, but services would be >application-database-mysql:version_50 > > > That is correct (one mysql.xml with version specific services...shall be defining the service for only 5.0) From sacadmin Tue Oct 23 11:26:29 2007 Received: from zruty.sfbay.sun.com (zruty [129.146.168.40]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9NIQTSL016817; Tue, 23 Oct 2007 11:26:29 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9NIN11U001443; Tue, 23 Oct 2007 11:23:01 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id l9NIN13Q001442; Tue, 23 Oct 2007 11:23:01 -0700 (PDT) Date: Tue, 23 Oct 2007 11:23:00 -0700 From: Danek Duvall To: Ritu Kamboj Cc: Lars Heill , LSARC@sac.sfbay.sun.com, webstack-discuss@opensolaris.org, Jyri Virkki Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] Message-ID: <20071023182300.GW1976@zruty.sfbay.sun.com> References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <471DB708.4050309@sun.com> <471E2DA9.8090606@sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <471E2DA9.8090606@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 139 On Tue, Oct 23, 2007 at 10:21:45AM -0700, Ritu Kamboj wrote: > /usr/local/mysql will be linked to the lastest version /usr/local? Danek From sacadmin Tue Oct 23 11:31:27 2007 Received: from sfbaymail2sca.sfbay.sun.com (sfbaymail2sca [129.145.155.42]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9NIVReL017078; Tue, 23 Oct 2007 11:31:27 -0700 (PDT) Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by sfbaymail2sca.sfbay.sun.com (8.13.6+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id l9NIS02I010121; Tue, 23 Oct 2007 11:28:00 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9NIRtiR020858; Tue, 23 Oct 2007 11:27:55 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQD00801MW4AB00@fe-sfbay-09.sun.com> (original mail from Ritu.Kamboj@Sun.COM); Tue, 23 Oct 2007 11:27:55 -0700 (PDT) Received: from [129.145.154.107] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQD00KMRNADPIH0@fe-sfbay-09.sun.com>; Tue, 23 Oct 2007 11:27:50 -0700 (PDT) Date: Tue, 23 Oct 2007 11:27:49 -0700 From: Ritu Kamboj Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071023182300.GW1976@zruty.sfbay.sun.com> Sender: Ritu.Kamboj@Sun.COM To: Danek Duvall Cc: Lars Heill , LSARC@sac.sfbay.sun.com, webstack-discuss@opensolaris.org, Jyri Virkki Reply-to: Ritu.Kamboj@Sun.COM Message-id: <471E3D25.4040903@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <471DB708.4050309@sun.com> <471E2DA9.8090606@sun.com> <20071023182300.GW1976@zruty.sfbay.sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20070109 Status: RO Content-Length: 355 Hi Danek, Sorry, typo on my end. I meant the latest version will be linked to /usr/mysql (so there will be a link from /usr/mysql/5.0 to /usr/mysql) Regards, Ritu Danek Duvall wrote: >On Tue, Oct 23, 2007 at 10:21:45AM -0700, Ritu Kamboj wrote: > > > >>/usr/local/mysql will be linked to the lastest version >> >> > >/usr/local? > >Danek > > From sacadmin Tue Oct 23 11:31:58 2007 Received: from zruty.sfbay.sun.com (zruty [129.146.168.40]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9NIVwMW017122; Tue, 23 Oct 2007 11:31:58 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9NISV3k001471; Tue, 23 Oct 2007 11:28:31 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id l9NISVtl001470; Tue, 23 Oct 2007 11:28:31 -0700 (PDT) Date: Tue, 23 Oct 2007 11:28:31 -0700 From: Danek Duvall To: Ritu Kamboj Cc: Jyri Virkki , LSARC@sac.sfbay.sun.com, webstack-discuss@opensolaris.org Subject: Re: Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] Message-ID: <20071023182831.GX1976@zruty.sfbay.sun.com> References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <471D2C4B.3040209@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 1554 On Mon, Oct 22, 2007 at 04:03:39PM -0700, Ritu Kamboj wrote: > We shall be having version directory under both /var and /etc directory (ie > /var/mysql/5.0/data and /etc/mysql/5.0. Okay. > We shall be having a symbolic link from /usr/mysql/5.0 to /usr/mysql. That's physically impossible. Or do you simply mean that the subdirs in /usr/mysql/5.0 will have links to them in /usr/mysql? >>> /usr/mysql/5.0/lib/libdbug.a >>> /usr/mysql/5.0/lib/libheap.a >>> /usr/mysql/5.0/lib/libmyisam.a >>> /usr/mysql/5.0/lib/libmyisammrg.a >>> /usr/mysql/5.0/lib/libmysqlclient.a >>> /usr/mysql/5.0/lib/libmysqlclient.la >>> /usr/mysql/5.0/lib/libmysqlclient_r.a >>> /usr/mysql/5.0/lib/libmysqlclient_r.la >>> /usr/mysql/5.0/lib/libmystrings.a >>> /usr/mysql/5.0/lib/libmysys.a >>> /usr/mysql/5.0/lib/libvio.a >>> /usr/mysql/5.0/lib/libz.a >>> /usr/mysql/5.0/lib/libz.la >>> >> >> Why are you delivering .a files? And what use are .la files on Solaris? >> > The MYSQL release area does not have shared library version for all the > libraries And people using mysql are generally content to rebuild their applications whenever fixes are made to these libraries? We would never allow archive libraries for a Sun-controlled project, but even though that's not the case here, I'd like to get an idea of what the impact is for the (typical?) end-user. > ...we are providing all the libraries that are provided in the default > MySQL release area. But why the .la files? And what's libz doing there? Is that the same libz as in /usr/lib/libz.so.1? Danek From sacadmin Tue Oct 23 12:33:55 2007 Received: from dm-uk-02.uk.sun.com (dm-uk-02.UK.Sun.COM [129.156.101.196]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9NJXshQ019136; Tue, 23 Oct 2007 12:33:55 -0700 (PDT) Received: from serinus.UK.Sun.COM (serinus.UK.Sun.COM [129.156.173.208]) by dm-uk-02.uk.sun.com (8.13.7+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l9NJUMaq024101; Tue, 23 Oct 2007 20:30:22 +0100 (BST) Received: from [192.168.1.100] (vpn-129-150-154-29.Japan.Sun.COM [129.150.154.29]) by serinus.UK.Sun.COM (8.13.7+Sun/8.13.7/CTE 3.0) with ESMTP id l9NJTtMs023073; Tue, 23 Oct 2007 20:30:03 +0100 (BST) Message-ID: <471E4B9A.9040702@sun.com> Date: Tue, 23 Oct 2007 15:29:30 -0400 From: James Gates User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.13) Gecko/20060509 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ritu Kamboj , Jyri Virkki CC: Danek Duvall , LSARC@sac.sfbay.sun.com, webstack-discuss@opensolaris.org Subject: Re: Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> In-Reply-To: <20071023182831.GX1976@zruty.sfbay.sun.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Status: RO Content-Length: 2772 Danek Duvall wrote: > On Mon, Oct 22, 2007 at 04:03:39PM -0700, Ritu Kamboj wrote: > > >>We shall be having version directory under both /var and /etc directory (ie >>/var/mysql/5.0/data and /etc/mysql/5.0. > > > Okay. > > >>We shall be having a symbolic link from /usr/mysql/5.0 to /usr/mysql. > > > That's physically impossible. Or do you simply mean that the subdirs in > /usr/mysql/5.0 will have links to them in /usr/mysql? > > >>>>/usr/mysql/5.0/lib/libdbug.a >>>>/usr/mysql/5.0/lib/libheap.a >>>>/usr/mysql/5.0/lib/libmyisam.a >>>>/usr/mysql/5.0/lib/libmyisammrg.a >>>>/usr/mysql/5.0/lib/libmysqlclient.a >>>>/usr/mysql/5.0/lib/libmysqlclient.la >>>>/usr/mysql/5.0/lib/libmysqlclient_r.a >>>>/usr/mysql/5.0/lib/libmysqlclient_r.la >>>>/usr/mysql/5.0/lib/libmystrings.a >>>>/usr/mysql/5.0/lib/libmysys.a >>>>/usr/mysql/5.0/lib/libvio.a >>>>/usr/mysql/5.0/lib/libz.a >>>>/usr/mysql/5.0/lib/libz.la >>>> >>> >>>Why are you delivering .a files? And what use are .la files on Solaris? >>> >> >>The MYSQL release area does not have shared library version for all the >>libraries > > > And people using mysql are generally content to rebuild their applications > whenever fixes are made to these libraries? We would never allow archive > libraries for a Sun-controlled project, but even though that's not the case > here, I'd like to get an idea of what the impact is for the (typical?) > end-user. > > I assume that means for non-Sun projects, we shouldn't ship static archive libraries if the equivalent dynamic shared library is available? This is what we do with PostgreSQL (in fact, we don't ship any *.a's with PostgreSQL). The point Danek makes about people rebuilding their applications whenever fixes are installed, is particularly relevent for client libraries. Looking at MySQL version 4.0 which is currently shipped with Solaris (and held in the SFW consolidation), I see that there are dynamic versions of the client libraries libmysqlclient_r.so & libmysqlclient.so (they're installed in /usr/sfw/lib). Are these dynamic client libraries no longer built in MySQL 5.0? If they are, do you really have a good reason to ship libmysqlclient.a & libmysqlclient_r.a? If they aren't, do you know why not (seems like a bad change to me). As for the remaining .a libraries in your list (libheap.a, libmyisam.a, etc.). Does the customer really need these? I thought all client development could be performed with just libmysqlclient? These look like libraries only needed during linking of the server binary. >>...we are providing all the libraries that are provided in the default >>MySQL release area. > > > But why the .la files? And what's libz doing there? Is that the same libz > as in /usr/lib/libz.so.1? > > Danek From sacadmin Tue Oct 23 18:13:44 2007 Received: from sfbaymail1sca.SFBay.Sun.COM (sfbaymail1sca [129.145.154.35]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9O1DiX0027961; Tue, 23 Oct 2007 18:13:44 -0700 (PDT) Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l9O1AGRB014802; Tue, 23 Oct 2007 18:10:16 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9O1ABo3002250; Tue, 23 Oct 2007 18:10:11 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQE00N015UC3B00@fe-sfbay-09.sun.com> (original mail from Ritu.Kamboj@Sun.COM); Tue, 23 Oct 2007 18:10:11 -0700 (PDT) Received: from [129.145.154.107] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQE00ER55WYQ630@fe-sfbay-09.sun.com>; Tue, 23 Oct 2007 18:10:11 -0700 (PDT) Date: Tue, 23 Oct 2007 18:10:10 -0700 From: Ritu Kamboj Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <471E4B9A.9040702@sun.com> Sender: Ritu.Kamboj@Sun.COM To: James Gates Cc: Jyri Virkki , webstack-discuss@opensolaris.org, Danek Duvall , LSARC@sac.sfbay.sun.com Reply-to: Ritu.Kamboj@Sun.COM Message-id: <471E9B72.9040709@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20070109 Status: RO Content-Length: 3703 James Gates wrote: >Danek Duvall wrote: > > >>On Mon, Oct 22, 2007 at 04:03:39PM -0700, Ritu Kamboj wrote: >> >> >> >> >>>We shall be having version directory under both /var and /etc directory (ie >>>/var/mysql/5.0/data and /etc/mysql/5.0. >>> >>> >>Okay. >> >> >> >> >>>We shall be having a symbolic link from /usr/mysql/5.0 to /usr/mysql. >>> >>> >>That's physically impossible. Or do you simply mean that the subdirs in >>/usr/mysql/5.0 will have links to them in /usr/mysql? >> >> >> >> >>>>>/usr/mysql/5.0/lib/libdbug.a >>>>>/usr/mysql/5.0/lib/libheap.a >>>>>/usr/mysql/5.0/lib/libmyisam.a >>>>>/usr/mysql/5.0/lib/libmyisammrg.a >>>>>/usr/mysql/5.0/lib/libmysqlclient.a >>>>>/usr/mysql/5.0/lib/libmysqlclient.la >>>>>/usr/mysql/5.0/lib/libmysqlclient_r.a >>>>>/usr/mysql/5.0/lib/libmysqlclient_r.la >>>>>/usr/mysql/5.0/lib/libmystrings.a >>>>>/usr/mysql/5.0/lib/libmysys.a >>>>>/usr/mysql/5.0/lib/libvio.a >>>>>/usr/mysql/5.0/lib/libz.a >>>>>/usr/mysql/5.0/lib/libz.la >>>>> >>>>> >>>>> >>>>Why are you delivering .a files? And what use are .la files on Solaris? >>>> >>>> >>>> >>>The MYSQL release area does not have shared library version for all the >>>libraries >>> >>> >>And people using mysql are generally content to rebuild their applications >>whenever fixes are made to these libraries? We would never allow archive >>libraries for a Sun-controlled project, but even though that's not the case >>here, I'd like to get an idea of what the impact is for the (typical?) >>end-user. >> >> >> >> > >I assume that means for non-Sun projects, we shouldn't ship static >archive libraries if the equivalent dynamic shared library is available? >This is what we do with PostgreSQL (in fact, we don't ship any *.a's >with PostgreSQL). > >The point Danek makes about people rebuilding their applications >whenever fixes are installed, is particularly relevent for client libraries. > >Looking at MySQL version 4.0 which is currently shipped with Solaris >(and held in the SFW consolidation), I see that there are dynamic >versions of the client libraries libmysqlclient_r.so & libmysqlclient.so >(they're installed in /usr/sfw/lib). > >Are these dynamic client libraries no longer built in MySQL 5.0? If they >are, do you really have a good reason to ship libmysqlclient.a & >libmysqlclient_r.a? If they aren't, do you know why not (seems like a >bad change to me). > > the dynamic client libraries are available for 5.0 as well...in a typical MySQL release area you will find both the static and dynamic version of client library and that was our initial plan as well....however, we can just ship the dynamic version of client libraries and take out the static library. >As for the remaining .a libraries in your list (libheap.a, libmyisam.a, >etc.). Does the customer really need these? I thought all client >development could be performed with just libmysqlclient? These look like >libraries only needed during linking of the server binary. > > The following static libraries exist in typical MySQL install area: libdbug.a, libmysys.a , libmystrings.a , libz.a. (in addition to client static library). I am working with MySQL to get a definitive answer about their use case ... > > >>>...we are providing all the libraries that are provided in the default >>>MySQL release area. >>> >>> >>But why the .la files? And what's libz doing there? Is that the same libz >>as in /usr/lib/libz.so.1? >> >>Danek >> >> >_______________________________________________ >webstack-discuss mailing list >webstack-discuss@opensolaris.org >http://mail.opensolaris.org/mailman/listinfo/webstack-discuss > > From sacadmin Tue Oct 23 18:14:40 2007 Received: from sfbaymail2sca.sfbay.sun.com (sfbaymail2sca [129.145.155.42]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9O1Ee3V027980; Tue, 23 Oct 2007 18:14:40 -0700 (PDT) Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by sfbaymail2sca.sfbay.sun.com (8.13.6+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id l9O1BCnG009142; Tue, 23 Oct 2007 18:11:12 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9O1B7gL002282; Tue, 23 Oct 2007 18:11:07 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQE00N015UC3B00@fe-sfbay-09.sun.com> (original mail from Ritu.Kamboj@Sun.COM); Tue, 23 Oct 2007 18:11:07 -0700 (PDT) Received: from [129.145.154.107] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQE00EZH5YIQ630@fe-sfbay-09.sun.com>; Tue, 23 Oct 2007 18:11:07 -0700 (PDT) Date: Tue, 23 Oct 2007 18:11:06 -0700 From: Ritu Kamboj Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071023182831.GX1976@zruty.sfbay.sun.com> Sender: Ritu.Kamboj@Sun.COM To: Danek Duvall Cc: LSARC@sac.sfbay.sun.com, webstack-discuss@opensolaris.org, Jyri Virkki Reply-to: Ritu.Kamboj@Sun.COM Message-id: <471E9BAA.4040206@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20070109 Status: RO Content-Length: 1954 Danek Duvall wrote: >On Mon, Oct 22, 2007 at 04:03:39PM -0700, Ritu Kamboj wrote: > > > >>We shall be having version directory under both /var and /etc directory (ie >>/var/mysql/5.0/data and /etc/mysql/5.0. >> >> > >Okay. > > > >>We shall be having a symbolic link from /usr/mysql/5.0 to /usr/mysql. >> >> > >That's physically impossible. Or do you simply mean that the subdirs in >/usr/mysql/5.0 will have links to them in /usr/mysql? > > I meant subdirs in /usr/mysq/5.0 will have links to them in /usr/mysql ... > > >>>>/usr/mysql/5.0/lib/libdbug.a >>>>/usr/mysql/5.0/lib/libheap.a >>>>/usr/mysql/5.0/lib/libmyisam.a >>>>/usr/mysql/5.0/lib/libmyisammrg.a >>>>/usr/mysql/5.0/lib/libmysqlclient.a >>>>/usr/mysql/5.0/lib/libmysqlclient.la >>>>/usr/mysql/5.0/lib/libmysqlclient_r.a >>>>/usr/mysql/5.0/lib/libmysqlclient_r.la >>>>/usr/mysql/5.0/lib/libmystrings.a >>>>/usr/mysql/5.0/lib/libmysys.a >>>>/usr/mysql/5.0/lib/libvio.a >>>>/usr/mysql/5.0/lib/libz.a >>>>/usr/mysql/5.0/lib/libz.la >>>> >>>> >>>> >>>Why are you delivering .a files? And what use are .la files on Solaris? >>> >>> >>> >>The MYSQL release area does not have shared library version for all the >>libraries >> >> > >And people using mysql are generally content to rebuild their applications >whenever fixes are made to these libraries? We would never allow archive >libraries for a Sun-controlled project, but even though that's not the case >here, I'd like to get an idea of what the impact is for the (typical?) >end-user. > > > >>...we are providing all the libraries that are provided in the default >>MySQL release area. >> >> > >But why the .la files? And what's libz doing there? Is that the same libz >as in /usr/lib/libz.so.1? > >Danek >_______________________________________________ >webstack-discuss mailing list >webstack-discuss@opensolaris.org >http://mail.opensolaris.org/mailman/listinfo/webstack-discuss > > From jyri@buye.red.iplanet.com Tue Oct 23 21:54:35 2007 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 l9O4sYYR001565 for ; Tue, 23 Oct 2007 21:54:35 -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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9O4p3R1009676; Wed, 24 Oct 2007 05:51:04 +0100 (BST) 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 <0JQE0022DG53GS00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 23 Oct 2007 21:51:03 -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 <0JQE00FZLG53CDD0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 23 Oct 2007 21:51:03 -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 l9O4hXJ2020587; Tue, 23 Oct 2007 21:43:33 -0700 (PDT) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id l9O4hX3h020586; Tue, 23 Oct 2007 21:43:33 -0700 (PDT) Date: Tue, 23 Oct 2007 21:43:33 -0700 From: Jyri Virkki Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <471E9B72.9040709@sun.com> To: Ritu Kamboj Cc: webstack-discuss@opensolaris.org, LSARC-ext@sun.com Message-id: <20071024044333.GQ20116@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.2.0.264296 References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 745 Ritu Kamboj wrote: > > the dynamic client libraries are available for 5.0 as well...in a > typical MySQL release area you will find both the static and dynamic > version of client library and that was our initial plan as > well....however, we can just ship the dynamic version of client > libraries and take out the static library. Sounds like a good plan, if the shared libs are available do ship those instead. > The following static libraries exist in typical MySQL install area: > libdbug.a, libmysys.a , libmystrings.a , libz.a. (in addition to > client static library). > I am working with MySQL to get a definitive answer about their use case ... Ok let us know.. -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From Matt.Ingenthron@sun.com Tue Oct 23 22:49:56 2007 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 l9O5ntrQ002043 for ; Tue, 23 Oct 2007 22:49:55 -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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9O5kNae001958 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 24 Oct 2007 06:46:26 +0100 (BST) 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 <0JQE00B0DIPBGF00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 23 Oct 2007 23:46:23 -0600 (MDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQE00B2PIPAE900@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 23 Oct 2007 23:46:23 -0600 (MDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l9O5kMtL005236 for ; Wed, 24 Oct 2007 05:46:22 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQE00I01HHE9Z00@mail-amer.sun.com> (original mail from Matt.Ingenthron@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 23 Oct 2007 23:46:22 -0600 (MDT) Received: from [192.168.0.101] ([24.152.137.245]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQE003SSIP7WL00@mail-amer.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 23 Oct 2007 23:46:20 -0600 (MDT) Date: Tue, 23 Oct 2007 22:45:23 -0700 From: Matt Ingenthron Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071024044333.GQ20116@sun.com> Sender: Matt.Ingenthron@sun.com To: Jyri Virkki Cc: Ritu Kamboj , webstack-discuss@opensolaris.org, LSARC-ext@sun.com Message-id: <471EDBF3.2070603@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> User-Agent: Thunderbird 2.0.0.4 (X11/20070723) Status: RO Content-Length: 1571 Jyri Virkki wrote: > Ritu Kamboj wrote: > >> the dynamic client libraries are available for 5.0 as well...in a >> typical MySQL release area you will find both the static and dynamic >> version of client library and that was our initial plan as >> well....however, we can just ship the dynamic version of client >> libraries and take out the static library. >> > > Sounds like a good plan, if the shared libs are available do ship > those instead. > I'd be a bit concerned about this, as I recall PHP mysql modules use the static client libraries when it builds by default. A quick search or two seems to confirm this. I wish it weren't the case, but there are probably other 'downstream' pieces of Open Source, and potential end user apps, that expect to link in the .a files. Given that the upstream build scripts leave them there by default, what do we gain by removing them? I assume the answer is discourage such linking, but it also will mean more complex porting/building for apps (both end user and other Open Source) that expect them. > >> The following static libraries exist in typical MySQL install area: >> libdbug.a, libmysys.a , libmystrings.a , libz.a. (in addition to >> client static library). >> I am working with MySQL to get a definitive answer about their use case ... >> > > Ok let us know.. > -- Matt Ingenthron - Web Infrastructure Solutions Architect Sun Microsystems, Inc. - Global Systems Practice http://blogs.sun.com/mingenthron/ email: matt.ingenthron@sun.com Phone: 310-242-6439 From danek.duvall@sun.com Tue Oct 23 22:55:19 2007 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 l9O5tIIw002418 for ; Tue, 23 Oct 2007 22:55:19 -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 l9O5pd9A016527 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 24 Oct 2007 13:51:49 +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 <0JQE00901IYB6Q00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 23 Oct 2007 22:51:47 -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 <0JQE00F3YIYBT6B0@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 23 Oct 2007 22:51:47 -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 l9O5pk3R052227; Tue, 23 Oct 2007 22:51:46 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9O5pkjw009443; Tue, 23 Oct 2007 22:51:46 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id l9O5pkWS009442; Tue, 23 Oct 2007 22:51:46 -0700 (PDT) Date: Tue, 23 Oct 2007 22:51:46 -0700 From: Danek Duvall Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <471EDBF3.2070603@sun.com> To: Matt Ingenthron Cc: Jyri Virkki , Ritu Kamboj , webstack-discuss@opensolaris.org, LSARC-ext@sun.com Message-id: <20071024055146.GS17676@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.2.0.264296 References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 355 On Tue, Oct 23, 2007 at 10:45:23PM -0700, Matt Ingenthron wrote: > I'd be a bit concerned about this, as I recall PHP mysql modules use the > static client libraries when it builds by default. A quick search or two > seems to confirm this. It actually puts the full .a file on the link line, rather than using -L and -l? /me shakes his head Danek From Matt.Ingenthron@sun.com Tue Oct 23 23:37:12 2007 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 l9O6bBuL002666 for ; Tue, 23 Oct 2007 23:37:12 -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 l9O6XZfK001113 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 24 Oct 2007 14:33:42 +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 <0JQE00B0BKW5FM00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 23 Oct 2007 23:33:41 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQE00FOFKW4T6C0@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 23 Oct 2007 23:33:40 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l9O6Xe8f002276 for ; Wed, 24 Oct 2007 06:33:40 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQE00401KPJDL00@mail-amer.sun.com> (original mail from Matt.Ingenthron@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed, 24 Oct 2007 00:33:40 -0600 (MDT) Received: from [192.168.0.101] ([24.152.137.245]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQE00EH0KW33550@mail-amer.sun.com>; Wed, 24 Oct 2007 00:33:40 -0600 (MDT) Date: Tue, 23 Oct 2007 23:32:43 -0700 From: Matt Ingenthron Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071024055146.GS17676@zruty.sfbay.sun.com> Sender: Matt.Ingenthron@sun.com To: Danek Duvall Cc: webstack-discuss@opensolaris.org, Ritu Kamboj , Jyri Virkki , LSARC-ext@sun.com Message-id: <471EE70B.4070200@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.4 (X11/20070723) Status: RO Content-Length: 1481 Danek Duvall wrote: > On Tue, Oct 23, 2007 at 10:45:23PM -0700, Matt Ingenthron wrote: > > >> I'd be a bit concerned about this, as I recall PHP mysql modules use the >> static client libraries when it builds by default. A quick search or two >> seems to confirm this. >> > > It actually puts the full .a file on the link line, rather than using -L > and -l? > > /me shakes his head Agreed... I'd have to check, but I specifically remember converting the linker args to use the shared object when working on one project. This could have been left behind in an older version though, or it could have been an artifact of the project I was working on (where PHP had been forked by the customer). Looking at the under-development Cool Stack, it is dynamically linked: # pwd /opt/coolstack/php5/lib/php/extensions/no-debug-non-zts-20060613 # ldd mysql.so ... libmysqlclient.so.15 => /opt/coolstack/mysql_32bit/lib/mysql/libmysqlclient.so.15 ... # ldd mysqli.so ... libmysqlclient.so.15 => /opt/coolstack/mysql_32bit/lib/mysql/libmysqlclient.so.15 ... The end of this posting is interesting: http://bugs.php.net/bug.php?id=34516 -- if it's correct, they didn't include shared libraries by default in MySQL circa January 2006. - Matt -- Matt Ingenthron - Web Infrastructure Solutions Architect Sun Microsystems, Inc. - Global Systems Practice http://blogs.sun.com/mingenthron/ email: matt.ingenthron@sun.com Phone: 310-242-6439 From sacadmin Wed Oct 24 03:34:51 2007 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02 [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9OAYpw6006755; Wed, 24 Oct 2007 03:34:51 -0700 (PDT) Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id l9OAVNs1017241; Wed, 24 Oct 2007 03:31:23 -0700 (PDT) Received: from relay15i.sun.com (ip125.net129179-4.block1.us.syntegra.com [129.179.4.125]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l9OAUNMD023962; Wed, 24 Oct 2007 10:31:22 GMT Received: from mmp12es.sun.com ([160.41.209.22] [160.41.209.22]) by relay15i.sun.com with ESMTP id BT-MMP-718769; Wed, 24 Oct 2007 10:31:22 Z Received: from relay15i.sun.com (relay15i.sun.com [129.179.4.125]) by mmp12es.sun.com with ESMTP id BT-MMP-46685; Wed, 24 Oct 2007 10:31:22 Z Received: from gendarme.mcslp.com ([82.70.138.102] [82.70.138.102]) by relay1i.sun.com with ESMTP id BT-MMP-3655786; Wed, 24 Oct 2007 10:31:21 Z Received: from localhost (localhost [127.0.0.1]) by gendarme.mcslp.com (Postfix) with ESMTP id 75FFD100CE73; Wed, 24 Oct 2007 11:31:23 +0100 (BST) X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Virus-Scanned: amavisd-new at mcslp.com Received: from gendarme.mcslp.com ([127.0.0.1]) by localhost (constable.mcslp.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WGFcxgAJINYN; Wed, 24 Oct 2007 11:31:18 +0100 (BST) Received: from [192.168.0.101] (sulaco.mcslp.pri [192.168.0.101]) by gendarme.mcslp.com (Postfix) with ESMTP id 0B608100CE68; Wed, 24 Oct 2007 11:31:18 +0100 (BST) In-Reply-To: <471E9B72.9040709@sun.com> References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> Message-Id: <8E255F0E-1866-47D3-868A-02C042AF4AAE@mcslp.com> Cc: James Gates , Danek Duvall , LSARC@sac.sfbay.sun.com, webstack-discuss@opensolaris.org, Jyri Virkki From: Martin MC Brown Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] Date: Wed, 24 Oct 2007 11:31:15 +0100 To: Ritu.Kamboj@sun.com X-Mailer: Apple Mail (2.752.3) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit Status: RO Content-Length: 1014 > >> As for the remaining .a libraries in your list (libheap.a, >> libmyisam.a, >> etc.). Does the customer really need these? I thought all client >> development could be performed with just libmysqlclient? These >> look like >> libraries only needed during linking of the server binary. >> >> > The following static libraries exist in typical MySQL install area: > libdbug.a, libmysys.a , libmystrings.a , libz.a. (in addition to > client static library). > I am working with MySQL to get a definitive answer about their use > case ... If you are only building clients then technically you only need libmysqlclient, but if you are developing a C app that accesses the structures and information in the response from mysqlclient you may need the other (libmystrings particularly). If you want to develop or add a storage engine to existing setup, then you need all the other libraries *except* libmysqlclient. MC -- Martin 'MC' Brown, mc@mcslp.com Everything MCslp: http://planet.mcslp.com From sacadmin Wed Oct 24 06:57:28 2007 Received: from sfbaymail1sca.SFBay.Sun.COM (sfbaymail1sca [129.145.154.35]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9ODvRkq009996; Wed, 24 Oct 2007 06:57:27 -0700 (PDT) Received: from gmp-eb-mail-1.sun.com (gmp-eb-mail-1.EU.Sun.COM [192.18.6.21]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l9ODrwCs007393; Wed, 24 Oct 2007 06:53:58 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9ODrqAo021856; Wed, 24 Oct 2007 13:53:52 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 <0JQF00G014MQ2P00@fe-emea-09.sun.com> (original mail from Jan.Berg@Sun.COM) ; Wed, 24 Oct 2007 14:53:52 +0100 (BST) Received: from [129.159.112.192] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQF00AHR5999780@fe-emea-09.sun.com>; Wed, 24 Oct 2007 14:53:34 +0100 (BST) Date: Wed, 24 Oct 2007 15:53:29 +0200 From: Jan S Berg Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <471D2C4B.3040209@sun.com> Sender: Jan.Berg@Sun.COM To: Ritu.Kamboj@Sun.COM Cc: Danek Duvall , LSARC@sac.sfbay.sun.com, webstack-discuss@opensolaris.org, Jyri Virkki Message-id: <471F4E59.1040103@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20070924) Status: RO Content-Length: 3697 Ritu Kamboj wrote: > Danek Duvall wrote: > >> On Fri, Oct 19, 2007 at 12:57:45AM -0700, Jyri Virkki wrote: >> >> >> >>> The proposed directory layout for MySQL is >>> /usr/mysql/5.0 >>> /bin binaries and scripts >>> /lib libraries for client API. >>> /include header files for client API >>> /man/man1 man-pages for client programs >>> /man/man8 man-pages for server programs >>> /mysql-test MySQL test programs >>> /share/mysql I18N files, sample config files >>> and utility scripts >>> /sql-bench SQL Benchmark test >>> /etc/mysql configuration file location >>> /var/mysql >>> /datadir default location for transactional >>> log files, data files, and pid file >>> >>> >> You say that multiple versions of mysql can exist on the system at the same >> time, and the versioning in /usr/mysql supports that. But you don't have >> any versioning in /etc/mysql or /var/mysql. Are multiple versions expected >> to share those directories? >> >> Also, would it make sense to put links to some of the executables (maybe >> just mysql?) in /usr/bin? >> >> > > We shall be having version directory under both /var and /etc directory > (ie /var/mysql/5.0/data and /etc/mysql/5.0. We shall be having a > symbolic link from /usr/mysql/5.0 to /usr/mysql. We can possible link > just the client mysql to /usr/bin as well. Shall update the ARC case to > reflect the same. Propose to have a symbolic link to all executables listed under section 2.1 key objects in the onepager, from /usr/bin. As they all are relevant for "ease of use". How should the versioning of the config file be done? Should we have only a config file in /etc/mysql/5.0/my.cnf or should we have /etc/mysql/my.cnf as well? or a symlink? (In any case we need to change the search path for the config file(s)) Jan S > >>> 7.3. Exported Interfaces >>> >>> NAME STABILITY NOTES >>> >>> svc:/network/mysql Committed FMRI >>> >>> >> You might want to follow postrgres' lead here and use >> >> svc:/application/database/mysql >> >> Are you planning on having an SMF instance per version, once there are >> multiple versions? >> >> > > To be consistent with Postgress , we shall make the change you suggested > wrt SMF. Yes the goal is to have SMF instance per version. > >> >> >>> /usr/mysql/5.0/lib/libdbug.a >>> /usr/mysql/5.0/lib/libheap.a >>> /usr/mysql/5.0/lib/libmyisam.a >>> /usr/mysql/5.0/lib/libmyisammrg.a >>> /usr/mysql/5.0/lib/libmysqlclient.a >>> /usr/mysql/5.0/lib/libmysqlclient.la >>> /usr/mysql/5.0/lib/libmysqlclient_r.a >>> /usr/mysql/5.0/lib/libmysqlclient_r.la >>> /usr/mysql/5.0/lib/libmystrings.a >>> /usr/mysql/5.0/lib/libmysys.a >>> /usr/mysql/5.0/lib/libvio.a >>> /usr/mysql/5.0/lib/libz.a >>> /usr/mysql/5.0/lib/libz.la >>> >>> >> Why are you delivering .a files? And what use are .la files on Solaris? >> >> > The MYSQL release area does not have shared library version for all the libraries ...we are providing all the libraries that are provided in the default MySQL release area. > > Danek > > > _______________________________________________ > webstack-discuss mailing list > webstack-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss > From plocher@sac.sfbay.sun.com Wed Oct 24 09:58:11 2007 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 l9OGwAvi014537 for ; Wed, 24 Oct 2007 09:58:11 -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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9OGscqo020167 for <@sunmail2sca.sfbay.sun.com:LSARC-Ext@Sun.Com>; Wed, 24 Oct 2007 17:54:41 +0100 (BST) 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 <0JQF00L03DN36F00@nwk-avmta-2.sfbay.sun.com> for LSARC-Ext@Sun.Com (ORCPT LSARC-Ext@Sun.Com); Wed, 24 Oct 2007 09:54:39 -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 <0JQF00KQQDN3BW10@nwk-avmta-2.sfbay.sun.com> for LSARC-Ext@Sun.Com (ORCPT LSARC-Ext@Sun.Com); Wed, 24 Oct 2007 09:54:39 -0700 (PDT) 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 l9OGsdaX009630 for ; Wed, 24 Oct 2007 09:54:39 -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 l9OGw8Ju014534 for ; Wed, 24 Oct 2007 09:58:08 -0700 (PDT) Received: (from plocher@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id l9OGw83s014533 for LSARC-Ext@Sun.Com; Wed, 24 Oct 2007 09:58:08 -0700 (PDT) Date: Wed, 24 Oct 2007 09:58:08 -0700 (PDT) From: John Plocher Subject: Fasttracks approved this week in LSARC: LSARC/2007/531 LSARC/2007/553 LSARC/2007/608 To: LSARC-Ext@sun.com Message-id: <200710241658.l9OGw83s014533@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 178 case exposure title 2007/531 closed Removal of dtcm 2007/553 open 64-bit Postgress 2007/608 open Including MySQL 5.0 with Solaris -John From Ritu.Kamboj@sun.com Wed Oct 24 10:12:07 2007 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 l9OHC715015640 for ; Wed, 24 Oct 2007 10:12:07 -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 l9OH8bu1009226 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 24 Oct 2007 11:08: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 <0JQF00I0NEAEJH00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed, 24 Oct 2007 11:08:38 -0600 (MDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQF00GPUEABDE10@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed, 24 Oct 2007 11:08:35 -0600 (MDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9OH8ZIG025222 for ; Wed, 24 Oct 2007 10:08:35 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQF00F01DPLTL00@fe-sfbay-10.sun.com> (original mail from Ritu.Kamboj@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Wed, 24 Oct 2007 10:08:35 -0700 (PDT) Received: from [129.145.154.107] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQF00CYUEA0EN70@fe-sfbay-10.sun.com>; Wed, 24 Oct 2007 10:08:24 -0700 (PDT) Date: Wed, 24 Oct 2007 10:08:24 -0700 From: Ritu Kamboj Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <471EE70B.4070200@sun.com> Sender: Ritu.Kamboj@sun.com To: Matt Ingenthron Cc: Danek Duvall , webstack-discuss@opensolaris.org, Jyri Virkki , LSARC-ext@sun.com Reply-to: Ritu.Kamboj@sun.com Message-id: <471F7C08.5010501@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> <471EE70B.4070200@sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20070109 Status: RO Content-Length: 2048 Hi , As Matt and Martin pointed out there are use cases of the static libraries bundled in the default MySQL installation. My proposal is that we have all the libraries that are given in the default MySQL installation. The complete list is as under: libdbug.a libmyisam.a libmysqlclient_r.a libmysqlclient_r.so libmysqlclient.a libmysqlclient.so libmystrings.a libmysys.a plus these two libraries as we are enabling the cluster engine (ndb): libndbclient.a libndbclient.so We can remove the other static library (ie libheap.a,libvio.a and all the .la files as well) Kindly let me know if that is fine and we shall update the ARC case accordingly. Regards, Ritu Matt Ingenthron wrote: > Danek Duvall wrote: > >> On Tue, Oct 23, 2007 at 10:45:23PM -0700, Matt Ingenthron wrote: >> >> >> >>> I'd be a bit concerned about this, as I recall PHP mysql modules use >>> the static client libraries when it builds by default. A quick >>> search or two seems to confirm this. >> >> >> It actually puts the full .a file on the link line, rather than using -L >> and -l? >> >> /me shakes his head > > > Agreed... > > I'd have to check, but I specifically remember converting the linker > args to use the shared object when working on one project. This could > have been left behind in an older version though, or it could have > been an artifact of the project I was working on (where PHP had been > forked by the customer). > > Looking at the under-development Cool Stack, it is dynamically linked: > # pwd > /opt/coolstack/php5/lib/php/extensions/no-debug-non-zts-20060613 > # ldd mysql.so > ... > libmysqlclient.so.15 => > /opt/coolstack/mysql_32bit/lib/mysql/libmysqlclient.so.15 > ... > # ldd mysqli.so > ... > libmysqlclient.so.15 => > /opt/coolstack/mysql_32bit/lib/mysql/libmysqlclient.so.15 > ... > > The end of this posting is interesting: > http://bugs.php.net/bug.php?id=34516 -- if it's correct, they didn't > include shared libraries by default in MySQL circa January 2006. > > > - Matt > From danek.duvall@sun.com Wed Oct 24 10:25:05 2007 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 l9OHP5DN016410 for ; Wed, 24 Oct 2007 10:25: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 l9OHLals017483 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@Sun.COM>; Wed, 24 Oct 2007 10:21:36 -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 <0JQF00J13EVZNK00@brm-avmta-1.central.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Wed, 24 Oct 2007 11:21:35 -0600 (MDT) Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQF00GHLEVYD120@brm-avmta-1.central.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Wed, 24 Oct 2007 11:21:34 -0600 (MDT) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l9OHLYFx008685; Wed, 24 Oct 2007 10:21:34 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9OHLYts012377; Wed, 24 Oct 2007 10:21:34 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id l9OHLYpU012376; Wed, 24 Oct 2007 10:21:34 -0700 (PDT) Date: Wed, 24 Oct 2007 10:21:33 -0700 From: Danek Duvall Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <471F7C08.5010501@sun.com> To: Ritu Kamboj Cc: Matt Ingenthron , webstack-discuss@opensolaris.org, Jyri Virkki , LSARC-ext@sun.com Message-id: <20071024172133.GF1976@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.2.0.264296 References: <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> <471EE70B.4070200@sun.com> <471F7C08.5010501@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 664 On Wed, Oct 24, 2007 at 10:08:24AM -0700, Ritu Kamboj wrote: > As Matt and Martin pointed out there are use cases of the static libraries > bundled in the default MySQL installation. Martin's message didn't demonstrate any use cases, and Matt said he thought he recalled them being required at some point in the past. That's pretty weak. > Kindly let me know if that is fine and we shall update the ARC case > accordingly. I'd like a definitive answer from the MySQL folks as to whether they consider the archive libraries to be a required part of an install, but that needn't hold up the case (and didn't, apparently, as it was approved yesterday). Danek From Ritu.Kamboj@sun.com Wed Oct 24 10:33:37 2007 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 l9OHXbuH016759 for ; Wed, 24 Oct 2007 10:33:37 -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 l9OHU4SZ012555 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 24 Oct 2007 10:30: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 <0JQF00K03FA6A800@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Wed, 24 Oct 2007 11:30:06 -0600 (MDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQF00GUXFA5D620@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Wed, 24 Oct 2007 11:30:06 -0600 (MDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9OHU5tK011199 for ; Wed, 24 Oct 2007 10:30:05 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQF00301EB60R00@fe-sfbay-09.sun.com> (original mail from Ritu.Kamboj@Sun.COM) for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Wed, 24 Oct 2007 10:30:05 -0700 (PDT) Received: from [129.145.154.107] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQF00HFCFA2SI40@fe-sfbay-09.sun.com>; Wed, 24 Oct 2007 10:30:02 -0700 (PDT) Date: Wed, 24 Oct 2007 10:30:02 -0700 From: Ritu Kamboj Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071024172133.GF1976@zruty.sfbay.sun.com> Sender: Ritu.Kamboj@sun.com To: Danek Duvall Cc: Matt Ingenthron , webstack-discuss@opensolaris.org, Jyri Virkki , LSARC-ext@sun.com Reply-to: Ritu.Kamboj@sun.com Message-id: <471F811A.2010307@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> <471EE70B.4070200@sun.com> <471F7C08.5010501@sun.com> <20071024172133.GF1976@zruty.sfbay.sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20070109 Status: RO Content-Length: 1386 Hi Danek, In his email yesterday Martin said the following: ----------------------- If you are only building clients then technically you only need libmysqlclient, but if you are developing a C app that accesses the structures and information in the response from mysqlclient you may need the other (libmystrings particularly). If you want to develop or add a storage engine to existing setup, then you need all the other libraries *except* libmysqlclient. -------------------------------- that explains why libmystrings and lib exist.... I shall get a definitive answer regarding libdbug and libmysys. Regards, Ritu Danek Duvall wrote: >On Wed, Oct 24, 2007 at 10:08:24AM -0700, Ritu Kamboj wrote: > > > >>As Matt and Martin pointed out there are use cases of the static libraries >>bundled in the default MySQL installation. >> >> > >Martin's message didn't demonstrate any use cases, and Matt said he thought >he recalled them being required at some point in the past. That's pretty >weak. > > > >>Kindly let me know if that is fine and we shall update the ARC case >>accordingly. >> >> > >I'd like a definitive answer from the MySQL folks as to whether they >consider the archive libraries to be a required part of an install, but >that needn't hold up the case (and didn't, apparently, as it was approved >yesterday). > >Danek > > From danek.duvall@Sun.COM Wed Oct 24 10:40:40 2007 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 l9OHeewZ017200 for ; Wed, 24 Oct 2007 10:40:40 -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 l9OHbAWQ020418 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@Sun.COM>; Wed, 24 Oct 2007 11:37:11 -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 <0JQF0000FFLY5100@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Wed, 24 Oct 2007 10:37:10 -0700 (PDT) Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQF00KM8FLWBT70@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Wed, 24 Oct 2007 10:37:08 -0700 (PDT) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l9OHb8rR015886; Wed, 24 Oct 2007 10:37:08 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9OHb8Gu012600; Wed, 24 Oct 2007 10:37:08 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id l9OHb8HZ012599; Wed, 24 Oct 2007 10:37:08 -0700 (PDT) Date: Wed, 24 Oct 2007 10:37:08 -0700 From: Danek Duvall Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <471F811A.2010307@sun.com> To: Ritu Kamboj Cc: Matt Ingenthron , webstack-discuss@opensolaris.org, Jyri Virkki , LSARC-ext@Sun.COM Message-id: <20071024173708.GJ1976@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.2.0.264296 References: <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> <471EE70B.4070200@sun.com> <471F7C08.5010501@sun.com> <20071024172133.GF1976@zruty.sfbay.sun.com> <471F811A.2010307@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 779 On Wed, Oct 24, 2007 at 10:30:02AM -0700, Ritu Kamboj wrote: > Hi Danek, > > In his email yesterday Martin said the following: > > ----------------------- > If you are only building clients then technically you only need > libmysqlclient, but if you are developing a C app that accesses the > structures and information in the response from mysqlclient you may need > the other (libmystrings particularly). > > If you want to develop or add a storage engine to existing setup, then you > need all the other libraries *except* libmysqlclient. > -------------------------------- > > that explains why libmystrings and lib exist.... But not as (and only as) archive libraries. I have no issue with any of the libraries being there, except for libz. Danek From Ritu.Kamboj@sun.com Wed Oct 24 10:52:51 2007 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 l9OHqpYn017813 for ; Wed, 24 Oct 2007 10:52:51 -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 l9OHnMDB024350 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 24 Oct 2007 11:49:22 -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 <0JQF00017G68NL00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Wed, 24 Oct 2007 10:49:20 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQF00KDLG65BT90@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Wed, 24 Oct 2007 10:49:17 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9OHnHxn001352 for ; Wed, 24 Oct 2007 10:49:17 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQF00H01G48UO00@fe-sfbay-10.sun.com> (original mail from Ritu.Kamboj@Sun.COM) for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Wed, 24 Oct 2007 10:49:17 -0700 (PDT) Received: from [129.145.154.107] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQF000AAG64RFB0@fe-sfbay-10.sun.com>; Wed, 24 Oct 2007 10:49:16 -0700 (PDT) Date: Wed, 24 Oct 2007 10:49:16 -0700 From: Ritu Kamboj Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071024173708.GJ1976@zruty.sfbay.sun.com> Sender: Ritu.Kamboj@sun.com To: Danek Duvall Cc: Matt Ingenthron , webstack-discuss@opensolaris.org, Jyri Virkki , LSARC-ext@sun.com Reply-to: Ritu.Kamboj@sun.com Message-id: <471F859C.1000500@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> <471EE70B.4070200@sun.com> <471F7C08.5010501@sun.com> <20071024172133.GF1976@zruty.sfbay.sun.com> <471F811A.2010307@sun.com> <20071024173708.GJ1976@zruty.sfbay.sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20070109 Status: RO Content-Length: 1056 Danek Duvall wrote: >On Wed, Oct 24, 2007 at 10:30:02AM -0700, Ritu Kamboj wrote: > > > >>Hi Danek, >> >>In his email yesterday Martin said the following: >> >>----------------------- >>If you are only building clients then technically you only need >>libmysqlclient, but if you are developing a C app that accesses the >>structures and information in the response from mysqlclient you may need >>the other (libmystrings particularly). >> >>If you want to develop or add a storage engine to existing setup, then you >>need all the other libraries *except* libmysqlclient. >>-------------------------------- >> >>that explains why libmystrings and lib exist.... >> >> > >But not as (and only as) archive libraries. I have no issue with any of >the libraries being there, except for libz. > >Danek > > We will be not be shipping libz as part of MySQL installation (MySQL needs to be compiled with special options to include libz in its installation...we shall not be using those options as part of our configure...) ... From sacadmin Wed Oct 24 10:59:45 2007 Received: from sfbaymail1sca.SFBay.Sun.COM (sfbaymail1sca [129.145.154.35]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9OHxjB8018578; Wed, 24 Oct 2007 10:59:45 -0700 (PDT) Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l9OHuFd7023929; Wed, 24 Oct 2007 10:56:15 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9OHuA8d014891; Wed, 24 Oct 2007 10:56:10 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQF00H01G48UO00@fe-sfbay-10.sun.com> (original mail from Ritu.Kamboj@Sun.COM); Wed, 24 Oct 2007 10:56:10 -0700 (PDT) Received: from [129.145.154.107] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQF000K0GHMRFE0@fe-sfbay-10.sun.com>; Wed, 24 Oct 2007 10:56:10 -0700 (PDT) Date: Wed, 24 Oct 2007 10:56:09 -0700 From: Ritu Kamboj Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <471F4E59.1040103@sun.com> Sender: Ritu.Kamboj@Sun.COM To: Jan S Berg Cc: webstack-discuss@opensolaris.org, Jyri Virkki , Danek Duvall , LSARC@sac.sfbay.sun.com Reply-to: Ritu.Kamboj@Sun.COM Message-id: <471F8739.2030809@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <471F4E59.1040103@sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20070109 Status: RO Content-Length: 4420 Hi , The plan is to have MySQL release area under /usr/mysql/5.0 and configuration files under /etc/mysql/5.0 The latest version (5.0 for our discussion) will be linked to /usr/mysql....so the latest release area will have a link to /usr/mysql and the configuration files will have a link to /etc/mysql. Regards, Ritu Jan S Berg wrote: >Ritu Kamboj wrote: > > >>Danek Duvall wrote: >> >> >> >>>On Fri, Oct 19, 2007 at 12:57:45AM -0700, Jyri Virkki wrote: >>> >>> >>> >>> >>> >>>> The proposed directory layout for MySQL is >>>> /usr/mysql/5.0 >>>> /bin binaries and scripts >>>> /lib libraries for client API. >>>> /include header files for client API >>>> /man/man1 man-pages for client programs >>>> /man/man8 man-pages for server programs >>>> /mysql-test MySQL test programs >>>> /share/mysql I18N files, sample config files >>>> and utility scripts >>>> /sql-bench SQL Benchmark test >>>> /etc/mysql configuration file location >>>> /var/mysql >>>> /datadir default location for transactional >>>> log files, data files, and pid file >>>> >>>> >>>> >>>> >>>You say that multiple versions of mysql can exist on the system at the same >>>time, and the versioning in /usr/mysql supports that. But you don't have >>>any versioning in /etc/mysql or /var/mysql. Are multiple versions expected >>>to share those directories? >>> >>>Also, would it make sense to put links to some of the executables (maybe >>>just mysql?) in /usr/bin? >>> >>> >>> >>> >>We shall be having version directory under both /var and /etc directory >>(ie /var/mysql/5.0/data and /etc/mysql/5.0. We shall be having a >>symbolic link from /usr/mysql/5.0 to /usr/mysql. We can possible link >>just the client mysql to /usr/bin as well. Shall update the ARC case to >>reflect the same. >> >> > >Propose to have a symbolic link to all executables listed under section >2.1 key objects in the onepager, from /usr/bin. As they all are relevant >for "ease of use". > >How should the versioning of the config file be done? >Should we have only a config file in /etc/mysql/5.0/my.cnf or should we >have /etc/mysql/my.cnf as well? or a symlink? >(In any case we need to change the search path for the config file(s)) > >Jan S > > > > >>>> 7.3. Exported Interfaces >>>> >>>> NAME STABILITY NOTES >>>> >>>> svc:/network/mysql Committed FMRI >>>> >>>> >>>> >>>> >>>You might want to follow postrgres' lead here and use >>> >>> svc:/application/database/mysql >>> >>>Are you planning on having an SMF instance per version, once there are >>>multiple versions? >>> >>> >>> >>> >>To be consistent with Postgress , we shall make the change you suggested >>wrt SMF. Yes the goal is to have SMF instance per version. >> >> >> >>> >>> >>> >>> >>>>/usr/mysql/5.0/lib/libdbug.a >>>>/usr/mysql/5.0/lib/libheap.a >>>>/usr/mysql/5.0/lib/libmyisam.a >>>>/usr/mysql/5.0/lib/libmyisammrg.a >>>>/usr/mysql/5.0/lib/libmysqlclient.a >>>>/usr/mysql/5.0/lib/libmysqlclient.la >>>>/usr/mysql/5.0/lib/libmysqlclient_r.a >>>>/usr/mysql/5.0/lib/libmysqlclient_r.la >>>>/usr/mysql/5.0/lib/libmystrings.a >>>>/usr/mysql/5.0/lib/libmysys.a >>>>/usr/mysql/5.0/lib/libvio.a >>>>/usr/mysql/5.0/lib/libz.a >>>>/usr/mysql/5.0/lib/libz.la >>>> >>>> >>>> >>>> >>>Why are you delivering .a files? And what use are .la files on Solaris? >>> >>> >>> >>> >>The MYSQL release area does not have shared library version for all the libraries ...we are providing all the libraries that are provided in the default MySQL release area. >> >>Danek >> >> >>_______________________________________________ >>webstack-discuss mailing list >>webstack-discuss@opensolaris.org >>http://mail.opensolaris.org/mailman/listinfo/webstack-discuss >> >> >> > >_______________________________________________ >webstack-discuss mailing list >webstack-discuss@opensolaris.org >http://mail.opensolaris.org/mailman/listinfo/webstack-discuss > > From dev@mcslp.com Wed Oct 24 23:58:54 2007 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 l9P6wrFj010366 for ; Wed, 24 Oct 2007 23:58: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 l9P6dtfG003922; Thu, 25 Oct 2007 14:39:57 +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 <0JQG00E03FUJYX00@brm-avmta-1.central.sun.com>; Thu, 25 Oct 2007 00:39:55 -0600 (MDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQG007ICFUI3790@brm-avmta-1.central.sun.com>; Thu, 25 Oct 2007 00:39:54 -0600 (MDT) Received: from relay42i.sun.com ([192.5.209.72]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l9P6dsjF029619; Thu, 25 Oct 2007 06:39:54 +0000 (GMT) Received: from mms49es.sun.com ([160.41.221.233] [160.41.221.233]) by relay42i.sun.com with ESMTP id BT-MMP-1034168; Thu, 25 Oct 2007 06:39:54 +0000 (Z) Received: from relay42i.sun.com ([192.5.209.72] [192.5.209.72]) by mms49es.sun.com with ESMTP id BT-MMP-3280065; Thu, 25 Oct 2007 06:39:53 +0000 (Z) Received: from gendarme.mcslp.com ([82.70.138.102] [82.70.138.102]) by relay4i.sun.com with ESMTP id BT-MMP-14812627; Thu, 25 Oct 2007 06:39:53 +0000 (Z) Received: from localhost (localhost [127.0.0.1]) by gendarme.mcslp.com (Postfix) with ESMTP id D8E0010161C9; Thu, 25 Oct 2007 07:39:49 +0100 (BST) Received: from gendarme.mcslp.com ([127.0.0.1]) by localhost (constable.mcslp.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bK97OnpRmPpr; Thu, 25 Oct 2007 07:39:44 +0100 (BST) Received: from [192.168.0.101] (sulaco.mcslp.pri [192.168.0.101]) by gendarme.mcslp.com (Postfix) with ESMTP id 4DC3210161BE; Thu, 25 Oct 2007 07:39:44 +0100 (BST) Date: Thu, 25 Oct 2007 07:39:43 +0100 From: Martin MC Brown Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <471F811A.2010307@sun.com> To: Ritu.Kamboj@sun.com Cc: Danek Duvall , Jyri Virkki , Matt Ingenthron , webstack-discuss@opensolaris.org, LSARC-ext@sun.com Message-id: <609E79E6-26C6-4A0F-AC12-C2DDCF7396A8@mcslp.com> MIME-version: 1.0 X-Mailer: Apple Mail (2.752.3) Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Virus-Scanned: amavisd-new at mcslp.com References: <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> <471EE70B.4070200@sun.com> <471F7C08.5010501@sun.com> <20071024172133.GF1976@zruty.sfbay.sun.com> <471F811A.2010307@sun.com> Status: RO Content-Length: 1194 On 24 Oct 2007, at 18:30, Ritu Kamboj wrote: > Hi Danek, > > In his email yesterday Martin said the following: > > ----------------------- > If you are only building clients then technically you only need > libmysqlclient, but if you are developing a C app that accesses the > structures and information in the response from mysqlclient you may > need the other (libmystrings particularly). > > If you want to develop or add a storage engine to existing setup, > then > you need all the other libraries *except* libmysqlclient. > -------------------------------- > > that explains why libmystrings and lib exist.... > > I shall get a definitive answer regarding libdbug and libmysys. libmysys is required when building a storage engine - it provides a number of compatibility functions that we like you to use to ensure compatibility with the rest of the system. libdbug is required if you want to run mysqld in debug mode and provide output/information either when testing your own plugins/ storage engines and/or when you provide debug trace output to us when reporting a bug. MC -- Martin 'MC' Brown, mc@mcslp.com Everything MCslp: http://planet.mcslp.com From dev@mcslp.com Wed Oct 24 23:59:23 2007 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 l9P6xMBJ010380 for ; Wed, 24 Oct 2007 23:59:22 -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 l9P6gdfc004970; Thu, 25 Oct 2007 14:42:50 +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 <0JQG00F0LFZB7Z00@brm-avmta-1.central.sun.com>; Thu, 25 Oct 2007 00:42:47 -0600 (MDT) Received: from sca-ea-mail-3.sun.com ([192.18.43.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQG0077RFZA3A80@brm-avmta-1.central.sun.com>; Thu, 25 Oct 2007 00:42:47 -0600 (MDT) Received: from relay18i.sun.com (ip128.net129179-4.block1.us.syntegra.com [129.179.4.128]) by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l9P6gkmw003345; Thu, 25 Oct 2007 06:42:46 +0000 (GMT) Received: from mmp13es.sun.com ([160.41.209.23] [160.41.209.23]) by relay18i.sun.com with ESMTP id BT-MMP-878617; Thu, 25 Oct 2007 06:42:46 +0000 (Z) Received: from relay13i.sun.com (relay13i.sun.com [129.179.4.123]) by mmp13es.sun.com with ESMTP id BT-MMP-68256; Thu, 25 Oct 2007 06:42:46 +0000 (Z) Received: from gendarme.mcslp.com ([82.70.138.102] [82.70.138.102]) by relay1ib.sun.com with ESMTP id BT-MMP-2639891; Thu, 25 Oct 2007 06:42:45 +0000 (Z) Received: from localhost (localhost [127.0.0.1]) by gendarme.mcslp.com (Postfix) with ESMTP id 3900D101623F; Thu, 25 Oct 2007 07:42:46 +0100 (BST) Received: from gendarme.mcslp.com ([127.0.0.1]) by localhost (constable.mcslp.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CFbv46FDgHAi; Thu, 25 Oct 2007 07:42:43 +0100 (BST) Received: from [192.168.0.101] (sulaco.mcslp.pri [192.168.0.101]) by gendarme.mcslp.com (Postfix) with ESMTP id 0674E1016234; Thu, 25 Oct 2007 07:42:43 +0100 (BST) Date: Thu, 25 Oct 2007 07:42:42 +0100 From: Martin MC Brown Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071024173708.GJ1976@zruty.sfbay.sun.com> To: Danek Duvall Cc: Ritu Kamboj , Jyri Virkki , Matt Ingenthron , webstack-discuss@opensolaris.org, LSARC-ext@sun.com Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.752.3) Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Virus-Scanned: amavisd-new at mcslp.com References: <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> <471EE70B.4070200@sun.com> <471F7C08.5010501@sun.com> <20071024172133.GF1976@zruty.sfbay.sun.com> <471F811A.2010307@sun.com> <20071024173708.GJ1976@zruty.sfbay.sun.com> Status: RO Content-Length: 1005 >> In his email yesterday Martin said the following: >> >> ----------------------- >> If you are only building clients then technically you only need >> libmysqlclient, but if you are developing a C app that accesses the >> structures and information in the response from mysqlclient you >> may need >> the other (libmystrings particularly). >> >> If you want to develop or add a storage engine to existing setup, >> then you >> need all the other libraries *except* libmysqlclient. >> -------------------------------- >> >> that explains why libmystrings and lib exist.... > > But not as (and only as) archive libraries. I have no issue with > any of > the libraries being there, except for libz. Some applications will want to link statically against the functions in the archive libraries. Theoretically there is no reason for them to be there, but practically some tools will want them. MC -- Martin 'MC' Brown, mc@mcslp.com Everything MCslp: http://planet.mcslp.com From danek.duvall@Sun.COM Thu Oct 25 00:04:45 2007 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 l9P74iRS011133 for ; Thu, 25 Oct 2007 00:04:44 -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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9P710iA003015 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Thu, 25 Oct 2007 08:01:15 +0100 (BST) 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 <0JQG00G03GU1Q200@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 25 Oct 2007 01:01:13 -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 <0JQG0075RGU13AA0@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 25 Oct 2007 01:01:13 -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 l9P71CNq004885; Thu, 25 Oct 2007 00:01:12 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9P71Cgp021178; Thu, 25 Oct 2007 00:01:12 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id l9P71CfY021177; Thu, 25 Oct 2007 00:01:12 -0700 (PDT) Date: Thu, 25 Oct 2007 00:01:12 -0700 From: Danek Duvall Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: To: Martin MC Brown Cc: Ritu Kamboj , Jyri Virkki , Matt Ingenthron , webstack-discuss@opensolaris.org, LSARC-ext@Sun.COM Message-id: <20071025070112.GE1976@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.2.0.264296 References: <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> <471EE70B.4070200@sun.com> <471F7C08.5010501@sun.com> <20071024172133.GF1976@zruty.sfbay.sun.com> <471F811A.2010307@sun.com> <20071024173708.GJ1976@zruty.sfbay.sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 553 On Thu, Oct 25, 2007 at 07:42:42AM +0100, Martin MC Brown wrote: > Some applications will want to link statically against the functions in the > archive libraries. Why? And do these applications generally put the archive library directly on the link line, or do they use -L and -l? If there's no technical reason for people to use archive libraries (and there almost certainly isn't) and we're not going to break application builds by removing them, then I'd much rather not ship them (as long as the shared libraries are easily generated). Danek From dev@mcslp.com Thu Oct 25 05:08:54 2007 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 l9PC8rZl015715 for ; Thu, 25 Oct 2007 05:08:53 -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 l9PC5Lb9020082; Thu, 25 Oct 2007 05:05:25 -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 <0JQG00H0BUX0V800@brm-avmta-1.central.sun.com>; Thu, 25 Oct 2007 06:05:24 -0600 (MDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQG003AQUWZ9PE0@brm-avmta-1.central.sun.com>; Thu, 25 Oct 2007 06:05:23 -0600 (MDT) Received: from relay11i.sun.com (ip121.net129179-4.block1.us.syntegra.com [129.179.4.121]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l9PC5Nwu008281; Thu, 25 Oct 2007 12:05:23 +0000 (GMT) Received: from mmp11es.sun.com ([160.41.209.21] [160.41.209.21]) by relay11i.sun.com with ESMTP id BT-MMP-742129; Thu, 25 Oct 2007 12:05:22 +0000 (Z) Received: from relay13i.sun.com (relay13i.sun.com [129.179.4.123]) by mmp11es.sun.com with ESMTP id BT-MMP-106336; Thu, 25 Oct 2007 12:05:22 +0000 (Z) Received: from gendarme.mcslp.com ([82.70.138.102] [82.70.138.102]) by relay1ib.sun.com with ESMTP id BT-MMP-2678790; Thu, 25 Oct 2007 12:05:22 +0000 (Z) Received: from localhost (localhost [127.0.0.1]) by gendarme.mcslp.com (Postfix) with ESMTP id 9F8AA101876D; Thu, 25 Oct 2007 13:05:21 +0100 (BST) Received: from gendarme.mcslp.com ([127.0.0.1]) by localhost (constable.mcslp.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id toR+d+CrBM8i; Thu, 25 Oct 2007 13:05:16 +0100 (BST) Received: from [192.168.0.101] (sulaco.mcslp.pri [192.168.0.101]) by gendarme.mcslp.com (Postfix) with ESMTP id 0D8471018760; Thu, 25 Oct 2007 13:05:16 +0100 (BST) Date: Thu, 25 Oct 2007 13:05:15 +0100 From: Martin MC Brown Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071025070112.GE1976@zruty.sfbay.sun.com> To: Danek Duvall Cc: Ritu Kamboj , Jyri Virkki , Matt Ingenthron , webstack-discuss@opensolaris.org, LSARC-ext@sun.com Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.752.3) Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== X-Virus-Scanned: amavisd-new at mcslp.com References: <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> <471EE70B.4070200@sun.com> <471F7C08.5010501@sun.com> <20071024172133.GF1976@zruty.sfbay.sun.com> <471F811A.2010307@sun.com> <20071024173708.GJ1976@zruty.sfbay.sun.com> <20071025070112.GE1976@zruty.sfbay.sun.com> Status: RO Content-Length: 1500 On 25 Oct 2007, at 08:01, Danek Duvall wrote: > On Thu, Oct 25, 2007 at 07:42:42AM +0100, Martin MC Brown wrote: > >> Some applications will want to link statically against the >> functions in the >> archive libraries. > > Why? And do these applications generally put the archive library > directly > on the link line, or do they use -L and -l? I'm not sure I can answer that question - I don't every single application currently being developed against MySQL :) I can tell you from experience here at MySQL that when we have mistakenly during a build or release not included these libraries people complain. > If there's no technical reason for people to use archive libraries > (and > there almost certainly isn't) and we're not going to break application > builds by removing them, then I'd much rather not ship them (as > long as the > shared libraries are easily generated). Well, I still don't understand why not. Are we somehow short of space or limitations on file numbers? They are part of the standard MySQL binary distribution and are built by default from the sources - if you don't include then some people may well think that the supplied installation of MySQL is either restricted or incomplete. That would somewhat diminish the impression of MySQL and Solaris/OpenSolaris, and is certainly not something I would want to perpetuate for the sake of a couple of files. MC -- Martin 'MC' Brown, mc@mcslp.com Everything MCslp: http://planet.mcslp.com From danek.duvall@sun.com Thu Oct 25 07:10:20 2007 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 l9PEAJOj017168 for ; Thu, 25 Oct 2007 07:10:20 -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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9PE6aOQ014284 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Thu, 25 Oct 2007 15:06:50 +0100 (BST) 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 <0JQH0020N0JBCQ00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 25 Oct 2007 07:06:47 -0700 (PDT) Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQH00DO60JBV1A0@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 25 Oct 2007 07:06:47 -0700 (PDT) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l9PE6kJ1000438; Thu, 25 Oct 2007 07:06:46 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9PE6kxR022546; Thu, 25 Oct 2007 07:06:46 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id l9PE6kfj022545; Thu, 25 Oct 2007 07:06:46 -0700 (PDT) Date: Thu, 25 Oct 2007 07:06:45 -0700 From: Danek Duvall Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: To: Martin MC Brown Cc: Ritu Kamboj , Jyri Virkki , Matt Ingenthron , webstack-discuss@opensolaris.org, LSARC-ext@sun.com Message-id: <20071025140645.GE17676@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.2.0.264296 References: <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> <471EE70B.4070200@sun.com> <471F7C08.5010501@sun.com> <20071024172133.GF1976@zruty.sfbay.sun.com> <471F811A.2010307@sun.com> <20071024173708.GJ1976@zruty.sfbay.sun.com> <20071025070112.GE1976@zruty.sfbay.sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 2211 On Thu, Oct 25, 2007 at 01:05:15PM +0100, Martin MC Brown wrote: > I'm not sure I can answer that question - I don't every single application > currently being developed against MySQL :) Oh, 'cmon! ;-) > I can tell you from experience here at MySQL that when we have mistakenly > during a build or release not included these libraries people complain. Okay, though that doesn't really answer the question. I was just wondering if you had a sense for how these libraries were linked, from the projects you had seen. >> If there's no technical reason for people to use archive libraries (and >> there almost certainly isn't) and we're not going to break application >> builds by removing them, then I'd much rather not ship them (as long as >> the shared libraries are easily generated). > > Well, I still don't understand why not. Are we somehow short of space or > limitations on file numbers? I thought we had a best practice about this, but I guess not. The issue is that if there are ever any problems discovered in these libraries applications linked against the shared copies can be fixed all at once, merely by replacing the shared library. If they're linked against archive libraries, they all have to be rebuilt, which may not always be possible, if source is not available, for instance. The space benefits -- sharing of text between running processes and simply having less stuff on disk -- are probably not interesting here. > They are part of the standard MySQL binary distribution and are built by > default from the sources - if you don't include then some people may well > think that the supplied installation of MySQL is either restricted or > incomplete. I don't doubt that, and I'd never suggest not shipping the libraries at all. I just would like to have a sense of whether the development experience would be diminshed if we shipped only shared libraries and not archive libraries. It sounds like we don't know, so it falls to the prject team to decide whether they want to do the experiment and find out who squawks, or be conservative and ship the archives. I'd recommend shipping shared libraries regardless, as the linker will pick them up preferentially. Danek From John.Plocher@sun.com Thu Oct 25 08:44:28 2007 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 l9PFiSF1018370 for ; Thu, 25 Oct 2007 08:44:28 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9PFevPY022649 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Thu, 25 Oct 2007 08:40:57 -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 <0JQH00A174W5PL00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 25 Oct 2007 08:40:53 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQH006KG4W5FS70@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 25 Oct 2007 08:40:53 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l9PFeqPI023765 for ; Thu, 25 Oct 2007 08:40:52 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JQH002014Q3PK00@fe-sfbay-09.sun.com> (original mail from John.Plocher@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 25 Oct 2007 08:40:52 -0700 (PDT) Received: from wp668.local ([208.74.177.212]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JQH004FJ4W33QA0@fe-sfbay-09.sun.com>; Thu, 25 Oct 2007 08:40:51 -0700 (PDT) Date: Thu, 25 Oct 2007 08:40:38 -0700 From: John Plocher Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071025070112.GE1976@zruty.sfbay.sun.com> Sender: John.Plocher@sun.com To: Danek Duvall Cc: Martin MC Brown , webstack-discuss@opensolaris.org, Ritu Kamboj , Jyri Virkki , Matt Ingenthron , LSARC-ext@sun.com Message-id: <4720B8F6.2070107@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <471EDBF3.2070603@sun.com> <20071024055146.GS17676@zruty.sfbay.sun.com> <471EE70B.4070200@sun.com> <471F7C08.5010501@sun.com> <20071024172133.GF1976@zruty.sfbay.sun.com> <471F811A.2010307@sun.com> <20071024173708.GJ1976@zruty.sfbay.sun.com> <20071025070112.GE1976@zruty.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) Status: RO Content-Length: 910 I *think* (and you know how much trouble I get into when I do that!) that this static linking has more to do with insurance against volatile API changes than it does with technical linkage issues. The technical issue for using archive libraries is simply that the environment that the consumers live in (cross platform *ix,pc,mac) has no consistant, predictable and reliable way to deploy and use versioned DSOs. Such an environment would need to take into account vendor-delivered libs as well as local admin and user generated libs (download the src, build it, link against your most recent libs...) $0.02 -John Danek Duvall wrote: > If there's no technical reason for people to use archive libraries (and > there almost certainly isn't) and we're not going to break application > builds by removing them, then I'd much rather not ship them (as long as the > shared libraries are easily generated). From jyri@buye.red.iplanet.com Thu Oct 25 10:02:18 2007 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 l9PH2IHP020676 for ; Thu, 25 Oct 2007 10:02:18 -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 l9PGwlV5009887; Thu, 25 Oct 2007 09:58:48 -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 <0JQH00H018HZY000@nwk-avmta-1.sfbay.Sun.COM>; Thu, 25 Oct 2007 09:58:47 -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 <0JQH00F4G8HZRZ20@nwk-avmta-1.sfbay.Sun.COM>; Thu, 25 Oct 2007 09:58:47 -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 l9PGpHo4021813; Thu, 25 Oct 2007 09:51:17 -0700 (PDT) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id l9PGpHU4021812; Thu, 25 Oct 2007 09:51:17 -0700 (PDT) Date: Thu, 25 Oct 2007 09:51:17 -0700 From: Jyri Virkki Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071024044333.GQ20116@sun.com> To: LSARC-ext@sun.com Cc: Ritu Kamboj , webstack-discuss@opensolaris.org, Jan.Berg@sun.com Message-id: <20071025165117.GH21733@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.2.0.264296 References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 315 Project team has updated the materials based on the discussions of the last week, available below [in a few hours, it takes some time to sync up to the latest changes]: http://www.opensolaris.org/os/community/arc/caselog/2007/608/materials/mysql-txt/ -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From jyri@buye.red.iplanet.com Mon Nov 19 16:30:47 2007 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 lAK0UlfX019726 for ; Mon, 19 Nov 2007 16:30:47 -0800 (PST) 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 lAK0Uhm3015655; Mon, 19 Nov 2007 16:30:45 -0800 (PST) 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 <0JRS00G0F438SU00@brm-avmta-1.central.sun.com>; Mon, 19 Nov 2007 17:30:44 -0700 (MST) 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 <0JRS002RX4383RD0@brm-avmta-1.central.sun.com>; Mon, 19 Nov 2007 17:30:44 -0700 (MST) 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 lAK0NExv028504; Mon, 19 Nov 2007 16:23:14 -0800 (PST) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id lAK0NEAP028503; Mon, 19 Nov 2007 16:23:14 -0800 (PST) Date: Mon, 19 Nov 2007 16:23:14 -0800 From: Jyri Virkki Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071025165117.GH21733@sun.com> To: LSARC-ext@sun.com Cc: Ritu Kamboj , webstack-discuss@opensolaris.org, Jan.Berg@sun.com Message-id: <20071120002314.GA28497@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_vrEXKDvqEpjU3L4qfgCEQA)" Content-disposition: inline X-PMX-Version: 5.2.0.264296 References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <20071025165117.GH21733@sun.com> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 3768 --Boundary_(ID_vrEXKDvqEpjU3L4qfgCEQA) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline Minor detail updates from the project team based on implementation-complete. Updated materials are in the case directory, diff attached. -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems --Boundary_(ID_vrEXKDvqEpjU3L4qfgCEQA) Content-type: text/plain; NAME=m.diff; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=m.diff ------- mysql.txt ------- --- /tmp/sccs.6IaGRL Mon Nov 19 16:20:52 2007 +++ mysql.txt Mon Nov 19 16:20:05 2007 @@ -10,7 +10,7 @@ 4. Technical Description Including MySQL 5.0 with Solaris -25 October 2007 +19 November 2007 1. Summary and motivation @@ -113,9 +113,8 @@ and utility scripts /sql-bench SQL Benchmark test /etc/mysql/5.0 configuration file location - /var/mysql/5.0 - /datadir default location for transactional - log files, data files, and pid file + /var/mysql/5.0/data default location for transactional + log files, data files, and pid file The detailed directory and file layout for MySQL is provided in Addendum 1. @@ -143,7 +142,7 @@ http://mysql.org/doc/refman/5.0/en/option-files.html We will provide a default config file: /etc/mysql/my.cnf And - create the default data/log directory /var/mysql/5.0/datadir + create the default data/log directory /var/mysql/5.0/data MySQL will be installed by default with user mysql and group mysql as done in the standard distribution. The default smf @@ -201,14 +200,14 @@ We propose to package MySQL under the following packages: - SUNWmysql50u - [usr] Server package (including server + SUNWmysql5u - [usr] Server package (including server deamon, C API, man pages, I18N) - SUNWmysql50r - [root] (config,smf files + SUNWmysql5r - [root] (config,smf files and data directory) - SUNWmysql50test - MySQL test packages + SUNWmysql5test - MySQL test packages Multiple versions can coexist, and are distinguished by the - version (50 for version 5.0.*). + version (5 for version 5.0.*). MySQL tests and sql-bench directories are bundled in a separate package. It is not necessary for running MySQL as such, but @@ -246,10 +245,9 @@ PID file Project Private database deamon pid file Error messages Not an interface I18N Translated Error Messages Error codes Committed Error codes - svc:/application/database/mysql5.0 + svc:/application/database/mysql:version_50 Committed FMRI - /lib/svc/method/mysql5.0-svc - Project Private SMF service method script + /lib/svc/method/mysql Project Private SMF service method script /var/svc/manifest/application/database/mysql.xml Project Private SMF Manifest @@ -576,11 +574,16 @@ /usr/mysql/5.0/man/man8/mysqlmanager.8 /etc/mysql/5.0/my.cnf +/etc/mysql/5.0/my-large.cnf +/etc/mysql/5.0/my-huge.cnf +/etc/mysql/5.0/my-medium.cnf +/etc/mysql/5.0/my-small-cnf.cnf +/etc/mysql/5.0/my.innodb-heavy-4G.cnf /etc/mysql/my.cnf -> /etc/mysql/5.0/my.cnf -/lib/svc/method/mysql-svc5.0 +/lib/svc/method/mysql /var/svc/manifest/application/database/mysql.xml --Boundary_(ID_vrEXKDvqEpjU3L4qfgCEQA)-- From danek.duvall@sun.com Mon Nov 19 16:35:47 2007 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 lAK0ZkOM019844 for ; Mon, 19 Nov 2007 16:35:46 -0800 (PST) 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 lAK0Zfqi006728 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@Sun.COM>; Tue, 20 Nov 2007 08:35:45 +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 <0JRS00H0D4BK6D00@brm-avmta-1.central.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Mon, 19 Nov 2007 17:35:44 -0700 (MST) Received: from sfbaymail2sca.sfbay.sun.com ([129.145.155.42]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JRS002Z64BJ3UD0@brm-avmta-1.central.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Mon, 19 Nov 2007 17:35:43 -0700 (MST) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by sfbaymail2sca.sfbay.sun.com (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id lAK0Zgum011566; Mon, 19 Nov 2007 16:35:42 -0800 (PST) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id lAK0Zg6o022430; Mon, 19 Nov 2007 16:35:42 -0800 (PST) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id lAK0ZfnL022429; Mon, 19 Nov 2007 16:35:42 -0800 (PST) Date: Mon, 19 Nov 2007 16:35:41 -0800 From: Danek Duvall Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071120002314.GA28497@sun.com> To: Jyri Virkki Cc: LSARC-ext@sun.com, Ritu Kamboj , webstack-discuss@opensolaris.org, Jan.Berg@sun.com Message-id: <20071120003541.GK5799@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.2.0.264296 References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <20071025165117.GH21733@sun.com> <20071120002314.GA28497@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 1086 On Mon, Nov 19, 2007 at 04:23:14PM -0800, Jyri Virkki wrote: > We propose to package MySQL under the following packages: > > - SUNWmysql50u - [usr] Server package (including server > + SUNWmysql5u - [usr] Server package (including server > deamon, C API, man pages, I18N) > - SUNWmysql50r - [root] (config,smf files > + SUNWmysql5r - [root] (config,smf files > and data directory) > - SUNWmysql50test - MySQL test packages > + SUNWmysql5test - MySQL test packages > > Multiple versions can coexist, and are distinguished by the > - version (50 for version 5.0.*). > + version (5 for version 5.0.*). I'm a little curious why you're dropping the "0" from the package names, but not from any of the directories. Will MySQL 5.1 be shipped in SUNWmysql5[ur], but use new directories for data and configuration? Or, as your parenthetical here implies, are you going to rename the packages for 5.1? (Or is the parenthetical incompletely updated?) Thanks, Danek From jyri@buye.red.iplanet.com Mon Nov 19 18:48:38 2007 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 lAK2mb8l022020 for ; Mon, 19 Nov 2007 18:48:37 -0800 (PST) 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 lAK2mUlV004574; Tue, 20 Nov 2007 02:48:33 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 <0JRS0070JAGVO500@nwk-avmta-2.sfbay.sun.com>; Mon, 19 Nov 2007 18:48:31 -0800 (PST) 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 <0JRS001BQAGUYQ60@nwk-avmta-2.sfbay.sun.com>; Mon, 19 Nov 2007 18:48:30 -0800 (PST) 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 lAK2f03s028650; Mon, 19 Nov 2007 18:41:00 -0800 (PST) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id lAK2f0NV028649; Mon, 19 Nov 2007 18:41:00 -0800 (PST) Date: Mon, 19 Nov 2007 18:41:00 -0800 From: Jyri Virkki Subject: Re: [webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007] In-reply-to: <20071120003541.GK5799@zruty.sfbay.sun.com> To: Danek Duvall Cc: Ritu Kamboj , webstack-discuss@opensolaris.org, LSARC-ext@sun.com, Jan.Berg@sun.com Message-id: <20071120024100.GK28220@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.2.0.264296 References: <200710190757.l9J7vjbg006745@sac.sfbay.sun.com> <20071022175943.GJ1976@zruty.sfbay.sun.com> <471D2C4B.3040209@sun.com> <20071023182831.GX1976@zruty.sfbay.sun.com> <471E4B9A.9040702@sun.com> <471E9B72.9040709@sun.com> <20071024044333.GQ20116@sun.com> <20071025165117.GH21733@sun.com> <20071120002314.GA28497@sun.com> <20071120003541.GK5799@zruty.sfbay.sun.com> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 894 Danek Duvall wrote: > > > Multiple versions can coexist, and are distinguished by the > > - version (50 for version 5.0.*). > > + version (5 for version 5.0.*). > > I'm a little curious why you're dropping the "0" from the package names, > but not from any of the directories. Will MySQL 5.1 be shipped in > SUNWmysql5[ur], but use new directories for data and configuration? Or, as > your parenthetical here implies, are you going to rename the packages for > 5.1? (Or is the parenthetical incompletely updated?) Yes that was my question as well, as this text is a bit conflictive. Apparently there is no intention of shipping a 5.1 so '5' will only stand for 5.0. The project team intends to move to 6.0 as the next step. Not sure why the choice to keep dir names. Project team can say more about their roadmap... -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From Jan.Berg@sun.com Thu Jan 24 05:58:23 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 m0ODwM4o007398 for ; Thu, 24 Jan 2008 05:58:23 -0800 (PST) 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 m0ODwH26021949 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 24 Jan 2008 21:58:21 +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 <0JV500C01IT7M300@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 06:58:19 -0700 (MST) Received: from gmp-eb-mail-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 <0JV5001AKIT67F90@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 06:58:18 -0700 (MST) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0ODwHff004295 for ; Thu, 24 Jan 2008 13:58:17 +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 <0JV500501IFKO800@fe-emea-10.sun.com> (original mail from Jan.Berg@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 13:58:17 +0000 (GMT) Received: from [129.159.112.192] by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JV50023MISY1U40@fe-emea-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 13:58:10 +0000 (GMT) Date: Thu, 24 Jan 2008 14:58:10 +0100 From: Jan S Berg Subject: LSARC/2007/608 create mysql user and group in Solaris Sender: Jan.Berg@sun.com To: lsarc-ext@sun.com Cc: Sunanda Menon Message-id: <47989972.9090300@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 2.0.0.6 (X11/20080102) Status: RO Content-Length: 746 We want to create the mysql user and mysql group in Solaris, and do it as part of the above mentioned ARC case. We suggest to use userid 70 and groupid 70, as this seems to be available. We think this is legitimate as the ARC case states: "MySQL will be installed by default with user mysql and group mysql as done in the standard distribution. The default smf script will also start MySQL as mysql user." It is filed a Bugster CR on this as well: 6648757 - mysql delivery doesn't match ARC case Which is also the CR that will be used for delivering the fix to OpenSolaris. We can file a new LSARC onepager if somebody disagrees that LSARC/2007/608 does not cover the creation of mysql user and group in solaris. Regards, Jan S Berg From Trevor.Watson@sun.com Thu Jan 24 08:22:55 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 m0OGMtLs010511 for ; Thu, 24 Jan 2008 08:22:55 -0800 (PST) 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 m0OGMqAB027935 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 24 Jan 2008 08:22:54 -0800 (PST) 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 <0JV500007PI64100@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 09:22:54 -0700 (MST) Received: from gmp-eb-mail-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 <0JV500I2XPI5V340@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 09:22:54 -0700 (MST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0OGMrq7028377 for ; Thu, 24 Jan 2008 16:22:53 +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 <0JV500301OYI4700@fe-emea-09.sun.com> (original mail from Trevor.Watson@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 16:22:53 +0000 (GMT) Received: from [129.156.63.113] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JV500FRQPHSA2F0@fe-emea-09.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 16:22:40 +0000 (GMT) Date: Thu, 24 Jan 2008 16:22:38 +0000 From: Trevor Watson Subject: Re: LSARC/2007/608 create mysql user and group in Solaris In-reply-to: <47989972.9090300@sun.com> Sender: Trevor.Watson@sun.com To: Jan S Berg Cc: lsarc-ext@sun.com, Sunanda Menon Message-id: <4798BB4E.1080105@Sun.COM> Organization: Sun Microsystems Ltd. MIME-version: 1.0 Content-type: multipart/signed; boundary=------------ms050000020401010004030002; micalg=sha1; protocol="application/x-pkcs7-signature" X-PMX-Version: 5.2.0.264296 References: <47989972.9090300@sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20071203) Status: RO Content-Length: 5748 --------------ms050000020401010004030002 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit It seems to be uid 27 on the couple of Linuxen hosts I checked. Is this already used on Solaris? Trev Jan S Berg wrote: > > We want to create the mysql user and mysql group in Solaris, > and do it as part of the above mentioned ARC case. > > We suggest to use userid 70 and groupid 70, as this seems to be > available. > > We think this is legitimate as the ARC case states: > > "MySQL will be installed by default with user mysql and group > mysql as done in the standard distribution. The default smf > script will also start MySQL as mysql user." > > It is filed a Bugster CR on this as well: > > 6648757 - mysql delivery doesn't match ARC case > > Which is also the CR that will be used for delivering the fix to > OpenSolaris. > > We can file a new LSARC onepager if somebody disagrees that > LSARC/2007/608 does not cover the creation of mysql user and group in > solaris. > > Regards, > Jan S Berg > --------------ms050000020401010004030002 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJEzCC AuQwggJNoAMCAQICEAF3zPJ4un8AzSM2bz1WwGYwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDMyODA3NTEyM1oX DTA4MDMyNzA3NTEyM1owRzEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEkMCIG CSqGSIb3DQEJARYVdHJldm9yLndhdHNvbkBzdW4uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOC AQ8AMIIBCgKCAQEAr22BHS+BPImaQdnBjJwc+6YCj594i8RKrtxfdAJqoPNVKAsl3ExDuJhX X4sTReUTzRJ/3+lFE4g3TkFjTQsXC6qbEXtCH+C3tzwKM3H6gRIZNn6aS6TfuacmwENJ3xjy ZkEgQDVaocJ1UAsM8PtFqW/4Gtq7hxDskeZj0Bi/fn6XYJP7uCa62rqaOGkX27y7Z8xGaqlQ 9V/bRd0NA0oxxIb14wOHaF3uZFLPmwo7yYlQWOgw2mxe7zGueOMqNCYLvd5b267VRKf61D0b 5vwleNgujrxqV4c6OijHIcN3TYgsMloXMAG/EzGTPrDeGup3hp/8bJ3bPS5ZS9PbS6+UpwID AQABozIwMDAgBgNVHREEGTAXgRV0cmV2b3Iud2F0c29uQHN1bi5jb20wDAYDVR0TAQH/BAIw ADANBgkqhkiG9w0BAQUFAAOBgQAWDfDYGoOhAAobnGMScxPz5vl6HOEP4fVrT4mZ9v3NkGEf hC8tytX8yX3LMhEZlASPt8Bw0sNye5doj9VVJVGRutJwNu++dWRiWzv51o3bX9S5nePjOdet 19qR9dQo402vu3jA/QtOyUzbcYJRkOPlm6rE/AnmiVasDxZgAaYYSjCCAuQwggJNoAMCAQIC EAF3zPJ4un8AzSM2bz1WwGYwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNV BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJz b25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDMyODA3NTEyM1oXDTA4MDMyNzA3NTEy M1owRzEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEkMCIGCSqGSIb3DQEJARYV dHJldm9yLndhdHNvbkBzdW4uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA r22BHS+BPImaQdnBjJwc+6YCj594i8RKrtxfdAJqoPNVKAsl3ExDuJhXX4sTReUTzRJ/3+lF E4g3TkFjTQsXC6qbEXtCH+C3tzwKM3H6gRIZNn6aS6TfuacmwENJ3xjyZkEgQDVaocJ1UAsM 8PtFqW/4Gtq7hxDskeZj0Bi/fn6XYJP7uCa62rqaOGkX27y7Z8xGaqlQ9V/bRd0NA0oxxIb1 4wOHaF3uZFLPmwo7yYlQWOgw2mxe7zGueOMqNCYLvd5b267VRKf61D0b5vwleNgujrxqV4c6 OijHIcN3TYgsMloXMAG/EzGTPrDeGup3hp/8bJ3bPS5ZS9PbS6+UpwIDAQABozIwMDAgBgNV HREEGTAXgRV0cmV2b3Iud2F0c29uQHN1bi5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0B AQUFAAOBgQAWDfDYGoOhAAobnGMScxPz5vl6HOEP4fVrT4mZ9v3NkGEfhC8tytX8yX3LMhEZ lASPt8Bw0sNye5doj9VVJVGRutJwNu++dWRiWzv51o3bX9S5nePjOdet19qR9dQo402vu3jA /QtOyUzbcYJRkOPlm6rE/AnmiVasDxZgAaYYSjCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcN AQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcT CUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRp ZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBG cmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNv bTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYD VQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVy c29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA xKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkV cI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUq VIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMG A1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZy ZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJp dmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIX oUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydx VyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x ggNkMIIDYAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGlu ZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWlu ZyBDQQIQAXfM8ni6fwDNIzZvPVbAZjAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJ KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODAxMjQxNjIyMzhaMCMGCSqGSIb3DQEJBDEW BBRYy1kOGyqb4gXOpGAO+4SeaSHU7DBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4G CCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB hQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1 bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElz c3VpbmcgQ0ECEAF3zPJ4un8AzSM2bz1WwGYwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYD VQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEAF3zPJ4un8AzSM2bz1W wGYwDQYJKoZIhvcNAQEBBQAEggEAgmU9N3XuUbzUqjvTzbfIcJm/7XfPCKPpKNVqQQuZNOdt 0t9dDtAFrW4IOAS1mHVflyCgvd3G+t2FRAWPc+ivX3Ambh1X+ZmaJaT+mmI6YL3T9vBV7JNf bKS1NbMG3DdGevY6w7chNOyUqTuimGK4VHhBcWuJRFwTV++iR8pItQKQjFUgB09gyTFHPhGc ZI6cRw6DUGXPWMtBKI8Jgnxaxj/gRX27xjBwptIsAAKn9sYAgaRJHABnSerM+xP7W+gGLYh3 q9/NheLIog85eMccPxArOXGuSSVHsOVwkaWKO5AxhAoROQzOF6y2uL7ATwLQZMrwC6pVOtRn LwAvumqjHgAAAAAAAA== --------------ms050000020401010004030002-- From james.gates@sun.com Thu Jan 24 09:29:31 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 m0OHTVWg013293 for ; Thu, 24 Jan 2008 09:29:31 -0800 (PST) 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 m0OHTU4Y017568 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 24 Jan 2008 09:29:31 -0800 (PST) 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 <0JV500L1PSL6NA00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 09:29:30 -0800 (PST) Received: from dm-uk-02.uk.sun.com ([129.156.101.196]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JV5000YNSL40RD0@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 09:29:29 -0800 (PST) Received: from serinus.UK.Sun.COM (serinus.UK.Sun.COM [129.156.173.208]) by dm-uk-02.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m0OHTPxr015906; Thu, 24 Jan 2008 17:29:26 +0000 (GMT) Received: from [192.168.1.100] (vpn-129-150-64-204.East.Sun.COM [129.150.64.204]) by serinus.UK.Sun.COM (8.13.7+Sun/8.13.7/CTE 3.0) with ESMTP id m0OHT0ii010386; Thu, 24 Jan 2008 17:29:09 +0000 (GMT) Date: Thu, 24 Jan 2008 12:28:26 -0500 From: James Gates Subject: Re: LSARC/2007/608 create mysql user and group in Solaris In-reply-to: <4798BB4E.1080105@Sun.COM> To: Trevor Watson Cc: Jan S Berg , lsarc-ext@sun.com, Sunanda Menon Message-id: <4798CABA.7000202@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <47989972.9090300@sun.com> <4798BB4E.1080105@Sun.COM> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.13) Gecko/20060509 Status: RO Content-Length: 1575 Looking at the default /etc/passwd issued with Nevada, uid 27 is free. These are the uid's (below 100) curently allocated: 0 1 2 3 4 5 9 15 25 37 50 71 80 90 95 I searched the mysql website, but it doesn't seem to make any recommendations about uids & gids. A quick Google search reveals that uid 60 is also used for mysql on both Gentoo & SUSE Linux. e.g. http://safari.samspublishing.com/067232735X/part02. Since both uids 27 & 60 are free in our default /etc/passwd, it seems we have a choice. Note that Red Hat uses 27 for mysql and 26 for postgres (but we use 90 for postgres). Trevor Watson wrote: > It seems to be uid 27 on the couple of Linuxen hosts I checked. Is this > already used on Solaris? > > Trev > > Jan S Berg wrote: > >> >> We want to create the mysql user and mysql group in Solaris, >> and do it as part of the above mentioned ARC case. >> >> We suggest to use userid 70 and groupid 70, as this seems to be >> available. >> >> We think this is legitimate as the ARC case states: >> >> "MySQL will be installed by default with user mysql and group >> mysql as done in the standard distribution. The default smf >> script will also start MySQL as mysql user." >> >> It is filed a Bugster CR on this as well: >> >> 6648757 - mysql delivery doesn't match ARC case >> >> Which is also the CR that will be used for delivering the fix to >> OpenSolaris. >> >> We can file a new LSARC onepager if somebody disagrees that >> LSARC/2007/608 does not cover the creation of mysql user and group in >> solaris. >> >> Regards, >> Jan S Berg >> > From Sunanda.Menon@sun.com Thu Jan 24 09:39: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 m0OHdY9h013812 for ; Thu, 24 Jan 2008 09:39:35 -0800 (PST) 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 m0OHdPje017724 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 24 Jan 2008 17:39:34 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 <0JV500M1DT1VNC00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 09:39:31 -0800 (PST) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JV5000Y1T1T0NE0@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 24 Jan 2008 09:39:30 -0800 (PST) Received: from fe-apac-01.sun.com (fe-apac-01.sun.com [192.18.19.172] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m0OHdSaN020350 for ; Thu, 24 Jan 2008 17:39:28 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JV500E01SZX8D00@mail-apac.sun.com> (original mail from Sunanda.Menon@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 25 Jan 2008 01:39:28 +0800 (SGT) Received: from [121.245.24.240] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JV500GMAT1EVBD1@mail-apac.sun.com>; Fri, 25 Jan 2008 01:39:28 +0800 (SGT) Date: Thu, 24 Jan 2008 23:08:57 +0530 From: Sunanda Menon Subject: Re: LSARC/2007/608 create mysql user and group in Solaris In-reply-to: <4798CABA.7000202@sun.com> Sender: Sunanda.Menon@sun.com To: James Gates Cc: Trevor Watson , Jan S Berg , lsarc-ext@sun.com Reply-to: Sunanda.Menon@sun.com Message-id: <4798CD31.5020409@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <47989972.9090300@sun.com> <4798BB4E.1080105@Sun.COM> <4798CABA.7000202@sun.com> User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) Status: RO Content-Length: 1793 Question : So are we saying in here that we cannot use 70 ,though this is free in Solaris .? What would be best to use then ?? James Gates wrote: > Looking at the default /etc/passwd issued with Nevada, uid 27 is free. > These are the uid's (below 100) curently allocated: > > 0 1 2 3 4 5 9 15 25 37 50 71 80 90 95 > > I searched the mysql website, but it doesn't seem to make any > recommendations about uids & gids. > > A quick Google search reveals that uid 60 is also used for mysql on > both Gentoo & SUSE Linux. e.g. > http://safari.samspublishing.com/067232735X/part02. > > Since both uids 27 & 60 are free in our default /etc/passwd, it seems > we have a choice. > > Note that Red Hat uses 27 for mysql and 26 for postgres (but we use 90 > for postgres). > > > Trevor Watson wrote: >> It seems to be uid 27 on the couple of Linuxen hosts I checked. Is >> this already used on Solaris? >> >> Trev >> >> Jan S Berg wrote: >> >>> >>> We want to create the mysql user and mysql group in Solaris, >>> and do it as part of the above mentioned ARC case. >>> >>> We suggest to use userid 70 and groupid 70, as this seems to be >>> available. >>> >>> We think this is legitimate as the ARC case states: >>> >>> "MySQL will be installed by default with user mysql and group >>> mysql as done in the standard distribution. The default smf >>> script will also start MySQL as mysql user." >>> >>> It is filed a Bugster CR on this as well: >>> >>> 6648757 - mysql delivery doesn't match ARC case >>> >>> Which is also the CR that will be used for delivering the fix to >>> OpenSolaris. >>> >>> We can file a new LSARC onepager if somebody disagrees that >>> LSARC/2007/608 does not cover the creation of mysql user and group >>> in solaris. >>> >>> Regards, >>> Jan S Berg >>> >> From carlsonj@phorcys.east.sun.com Thu Jan 24 10:16:56 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 m0OIGtPh015160 for ; Thu, 24 Jan 2008 10:16:56 -0800 (PST) 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 m0OIGfGj003304; Thu, 24 Jan 2008 18:16:50 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 <0JV50081HUS0MU00@brm-avmta-1.central.sun.com>; Thu, 24 Jan 2008 11:16:48 -0700 (MST) 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 <0JV500I8NURZV9A0@brm-avmta-1.central.sun.com>; Thu, 24 Jan 2008 11:16:47 -0700 (MST) 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 m0OIGlil012146; Thu, 24 Jan 2008 13:16:47 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m0OIGlsA012143; Thu, 24 Jan 2008 13:16:47 -0500 (EST) Date: Thu, 24 Jan 2008 13:16:46 -0500 From: James Carlson Subject: Re: LSARC/2007/608 create mysql user and group in Solaris In-reply-to: <4798CD31.5020409@Sun.COM> To: Sunanda.Menon@sun.com Cc: James Gates , Trevor Watson , lsarc-ext@sun.com, Jan S Berg Message-id: <18328.54798.995842.802004@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.2.0.264296 References: <47989972.9090300@sun.com> <4798BB4E.1080105@Sun.COM> <4798CABA.7000202@sun.com> <4798CD31.5020409@Sun.COM> Status: RO Content-Length: 676 Sunanda Menon writes: > Question : > So are we saying in here that we cannot use 70 ,though this is free in > Solaris .? No ... the question was about what the "best" number to use might be, not that 70 isn't available. The best number would presumably be one that matches the largest number of other distributions, so that administrators don't have to deal with the hassles caused by shared file systems and default ownerships that don't line up. -- 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 dev@mcslp.com Thu Jan 24 10:56:21 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 m0OIuIfA017770 for ; Thu, 24 Jan 2008 10:56:21 -0800 (PST) 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 m0OIuBRS020777; Thu, 24 Jan 2008 18:56:13 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 <0JV50070RWLNT200@nwk-avmta-2.sfbay.sun.com>; Thu, 24 Jan 2008 10:56:11 -0800 (PST) Received: from sca-ea-mail-2.sun.com ([192.18.43.25]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JV500MBIWLM3750@nwk-avmta-2.sfbay.sun.com>; Thu, 24 Jan 2008 10:56:10 -0800 (PST) Received: from relay23.sun.com (relay23.sun.com [192.12.251.54] (may be forged)) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0OIoFRZ000951; Thu, 24 Jan 2008 18:56:09 +0000 (GMT) Received: from mms24es.sun.com ([150.143.232.74] [150.143.232.74]) by relay23i.sun.com with ESMTP id BT-MMP-1936558; Thu, 24 Jan 2008 18:56:05 +0000 (Z) Received: from relay22.sun.com (relay22.sun.com [192.12.251.34]) by mms24es.sun.com with ESMTP id BT-MMP-999120; Thu, 24 Jan 2008 18:56:05 +0000 (Z) Received: from gendarme.mcslp.com ([82.70.138.102] [82.70.138.102]) by relay22i.sun.com with ESMTP id BT-MMP-3419549; Thu, 24 Jan 2008 18:56:04 +0000 (Z) Received: from localhost (unknown [127.0.0.1]) by gendarme.mcslp.com (Postfix) with ESMTP id BCE064D403C; Thu, 24 Jan 2008 18:56:03 +0000 (UTC) Received: from gendarme.mcslp.com ([127.0.0.1]) by localhost (constable.mcslp.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vTfB8TRZv1TA; Thu, 24 Jan 2008 18:56:01 +0000 (GMT) Received: from polarbear.wireless.mcslp.pri (polarbear.wireless.mcslp.pri [192.168.0.105]) by gendarme.mcslp.com (Postfix) with ESMTP id 673C84D4035; Thu, 24 Jan 2008 18:56:01 +0000 (GMT) Date: Thu, 24 Jan 2008 18:55:58 +0000 From: Martin MC Brown Subject: Re: [webstack-discuss] LSARC/2007/608 create mysql user and group in Solaris In-reply-to: <4798CABA.7000202@sun.com> To: James Gates Cc: Trevor Watson , lsarc-ext@sun.com, Jan S Berg , Sunanda Menon Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.915) Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 X-Brightmail-Tracker: AAAAAA== X-Virus-Scanned: amavisd-new at mcslp.com X-Antispam: No, score=-2.6/5.0, scanned in 0.135sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <47989972.9090300@sun.com> <4798BB4E.1080105@Sun.COM> <4798CABA.7000202@sun.com> Status: RO Content-Length: 1259 On 24 Jan 2008, at 17:28, James Gates wrote: > Looking at the default /etc/passwd issued with Nevada, uid 27 is free. > These are the uid's (below 100) curently allocated: > > 0 1 2 3 4 5 9 15 25 37 50 71 80 90 95 > > I searched the mysql website, but it doesn't seem to make any > recommendations about uids & gids. We don't make recommendations on uid/gid because it doesn't matter as long as it doesn't conflict :) It's possible that we could argue about synergy across NFS mounts, but we *really* don't recommend providing any of the files that really rely on the uid/gid (i.e. mainly the database files in the configured datadir) over NFS for performance, lock and stability reasons. When I last updated the documentation the basic advice was create a group and then a user (using useradd/adduser) and just make sure you use that when changing ownership. I've already agreed with Jan that I'll update the documentation for MySQL accordingly. In this instance, I can make the recommendation based on what is automatically created so that those using OpenSolaris and installing MySQL on existing environments can synchronize. MC (also mc@mysql.com) -- Martin 'MC' Brown, mc@mcslp.com Everything MCslp: http://planet.mcslp.com From jyri@buye.red.iplanet.com Thu Jan 24 12:40:15 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 m0OKeFjv022012 for ; Thu, 24 Jan 2008 12:40:15 -0800 (PST) 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 m0OKe2db001153; Thu, 24 Jan 2008 12:40:05 -0800 (PST) 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 <0JV600J0N1ERRT00@brm-avmta-1.central.sun.com>; Thu, 24 Jan 2008 13:40:03 -0700 (MST) 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 <0JV600GXM1EQHR10@brm-avmta-1.central.sun.com>; Thu, 24 Jan 2008 13:40:02 -0700 (MST) 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 m0OKe2cm028113; Thu, 24 Jan 2008 12:40:02 -0800 (PST) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id m0OKe2TY028112; Thu, 24 Jan 2008 12:40:02 -0800 (PST) Date: Thu, 24 Jan 2008 12:40:02 -0800 From: Jyri Virkki Subject: Re: [webstack-discuss] LSARC/2007/608 create mysql user and group in Solaris In-reply-to: <18328.54798.995842.802004@gargle.gargle.HOWL> To: James Carlson Cc: Sunanda.Menon@sun.com, Trevor Watson , Jan S Berg , lsarc-ext@sun.com, James Gates Message-id: <20080124204002.GA28082@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.2.0.264296 References: <47989972.9090300@sun.com> <4798BB4E.1080105@Sun.COM> <4798CABA.7000202@sun.com> <4798CD31.5020409@Sun.COM> <18328.54798.995842.802004@gargle.gargle.HOWL> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 1210 First, AFAIK (?) there isn't an architectural policy for picking the mysql uid from the set (26, 60, 70) that's been mentioned, so it probably doesn't need to be discussed too much deeper in the context of this LSARC case. The implementor & code reviewers can pick and agree on something. James Carlson wrote: > > No ... the question was about what the "best" number to use might be, > not that 70 isn't available. The best number would presumably be one > that matches the largest number of other distributions, so that > administrators don't have to deal with the hassles caused by shared > file systems and default ownerships that don't line up. It probably doesn't matter for these system users in general. These are not users which log in or share their files across NFS. The files they own, if any, are runtime log/data files typically under /var, usually not shareable across hosts anyway. Probably not a discussion to have within this case either though ;-) It's been talked about earlier in this thread http://mail.opensolaris.org/pipermail/pkg-discuss/2007-November/thread.html#819 which might be a place to continue it as needed. -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems