[webstack-discuss] Including MySQL 5.0 with Solaris [LSARC/2007/608 FastTrack timeout 10/26/2007]
Jan S Berg
Jan.Berg at Sun.COM
Wed Oct 24 06:53:29 PDT 2007
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 at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/webstack-discuss
>
More information about the webstack-discuss
mailing list