Author: paul
Date: 2006-01-11 21:54:58 +0100 (Wed, 11 Jan 2006)
New Revision: 768
Log:
r6093@frost: paul | 2006-01-11 14:09:38 -0600
Move some blocks of text around.
Modified:
trunk/
trunk/refman-4.1/installing.xml
trunk/refman-5.0/installing.xml
trunk/refman-5.1/installing.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6091
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6093
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994
Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml 2006-01-11 20:39:12 UTC (rev 767)
+++ trunk/refman-4.1/installing.xml 2006-01-11 20:54:58 UTC (rev 768)
@@ -10151,126 +10151,6 @@
<command>mysql_install_db</command>, see
<xref linkend="mysql-install-db"/>.
</para>
-
- <para>
- There are some alternatives to running the
- <command>mysql_install_db</command> script as it is provided
- in the MySQL distribution:
- </para>
-
- <indexterm>
- <primary>grant tables</primary>
- <secondary>re-creating</secondary>
- </indexterm>
-
- <indexterm>
- <primary>re-creating</primary>
- <secondary>grant tables</secondary>
- </indexterm>
-
- <itemizedlist>
-
- <listitem>
- <para>
- If you want the initial privileges to be different from
- the standard defaults, you can modify
- <command>mysql_install_db</command> before you run it.
- However, a preferable technique is to use
- <literal>GRANT</literal> and <literal>REVOKE</literal>
- to change the privileges after the grant tables have
- been set up. In other words, you can run
- <command>mysql_install_db</command>, and then use
- <command>mysql -u root mysql</command> to connect to the
- server as the MySQL <literal>root</literal> user so that
- you can issue the <literal>GRANT</literal> and
- <literal>REVOKE</literal> statements.
- </para>
-
- <para>
- If you want to install MySQL on several machines with
- the same privileges, you can put the
- <literal>GRANT</literal> and <literal>REVOKE</literal>
- statements in a file and execute the file as a script
- using <literal>mysql</literal> after running
- <command>mysql_install_db</command>. For example:
- </para>
-
-<programlisting>
-shell> <userinput>bin/mysql_install_db --user=mysql</userinput>
-shell> <userinput>bin/mysql -u root < your_script_file</userinput>
-</programlisting>
-
- <para>
- By doing this, you can avoid having to issue the
- statements manually on each machine.
- </para>
- </listitem>
-
- <listitem>
- <para>
- It is possible to re-create the grant tables completely
- after they have previously been created. You might want
- to do this if you are just learning how to use
- <literal>GRANT</literal> and <literal>REVOKE</literal>
- and have made so many modifications after running
- <command>mysql_install_db</command> that you want to
- wipe out the tables and start over.
- </para>
-
- <para>
- To re-create the grant tables, remove all the
- <filename>.frm</filename>, <filename>.MYI</filename>,
- and <filename>.MYD</filename> files in the directory
- containing the <literal>mysql</literal> database. (This
- is the directory named <filename>mysql</filename> under
- the data directory, which is listed as the
- <literal>datadir</literal> value when you run
- <command>mysqld --help</command>.) Then run the
- <command>mysql_install_db</command> script again.
- </para>
-
- <para>
- <emphasis role="bold">Note</emphasis>: For MySQL
- versions older than 3.22.10, you should not delete the
- <filename>.frm</filename> files. If you accidentally do
- this, you should copy them back into the
- <filename>mysql</filename> directory from your MySQL
- distribution before running
- <command>mysql_install_db</command>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You can start <command>mysqld</command> manually using
- the <option>--skip-grant-tables</option> option and add
- the privilege information yourself using
- <command>mysql</command>:
- </para>
-
-<programlisting>
-shell> <userinput>bin/mysqld_safe --user=mysql --skip-grant-tables &</userinput>
-shell> <userinput>bin/mysql mysql</userinput>
-</programlisting>
-
- <para>
- From <command>mysql</command>, manually execute the SQL
- commands contained in
- <command>mysql_install_db</command>. Make sure that you
- run <command>mysqladmin flush-privileges</command> or
- <command>mysqladmin reload</command> afterward to tell
- the server to reload the grant tables.
- </para>
-
- <para>
- Note that by not using
- <command>mysql_install_db</command>, you not only have
- to populate the grant tables manually, you also have to
- create them first.
- </para>
- </listitem>
-
- </itemizedlist>
</listitem>
<listitem>
@@ -10749,6 +10629,126 @@
</itemizedlist>
+ <para>
+ There are some alternatives to running the
+ <command>mysql_install_db</command> script as it is provided
+ in the MySQL distribution:
+ </para>
+
+ <indexterm>
+ <primary>grant tables</primary>
+ <secondary>re-creating</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>re-creating</primary>
+ <secondary>grant tables</secondary>
+ </indexterm>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ If you want the initial privileges to be different from
+ the standard defaults, you can modify
+ <command>mysql_install_db</command> before you run it.
+ However, a preferable technique is to use
+ <literal>GRANT</literal> and <literal>REVOKE</literal> to
+ change the privileges after the grant tables have been set
+ up. In other words, you can run
+ <command>mysql_install_db</command>, and then use
+ <command>mysql -u root mysql</command> to connect to the
+ server as the MySQL <literal>root</literal> user so that
+ you can issue the <literal>GRANT</literal> and
+ <literal>REVOKE</literal> statements.
+ </para>
+
+ <para>
+ If you want to install MySQL on several machines with the
+ same privileges, you can put the <literal>GRANT</literal>
+ and <literal>REVOKE</literal> statements in a file and
+ execute the file as a script using
+ <literal>mysql</literal> after running
+ <command>mysql_install_db</command>. For example:
+ </para>
+
+<programlisting>
+shell> <userinput>bin/mysql_install_db --user=mysql</userinput>
+shell> <userinput>bin/mysql -u root < your_script_file</userinput>
+</programlisting>
+
+ <para>
+ By doing this, you can avoid having to issue the
+ statements manually on each machine.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ It is possible to re-create the grant tables completely
+ after they have previously been created. You might want to
+ do this if you are just learning how to use
+ <literal>GRANT</literal> and <literal>REVOKE</literal> and
+ have made so many modifications after running
+ <command>mysql_install_db</command> that you want to wipe
+ out the tables and start over.
+ </para>
+
+ <para>
+ To re-create the grant tables, remove all the
+ <filename>.frm</filename>, <filename>.MYI</filename>, and
+ <filename>.MYD</filename> files in the directory
+ containing the <literal>mysql</literal> database. (This is
+ the directory named <filename>mysql</filename> under the
+ data directory, which is listed as the
+ <literal>datadir</literal> value when you run
+ <command>mysqld --help</command>.) Then run the
+ <command>mysql_install_db</command> script again.
+ </para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: For MySQL versions
+ older than 3.22.10, you should not delete the
+ <filename>.frm</filename> files. If you accidentally do
+ this, you should copy them back into the
+ <filename>mysql</filename> directory from your MySQL
+ distribution before running
+ <command>mysql_install_db</command>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ You can start <command>mysqld</command> manually using the
+ <option>--skip-grant-tables</option> option and add the
+ privilege information yourself using
+ <command>mysql</command>:
+ </para>
+
+<programlisting>
+shell> <userinput>bin/mysqld_safe --user=mysql --skip-grant-tables &</userinput>
+shell> <userinput>bin/mysql mysql</userinput>
+</programlisting>
+
+ <para>
+ From <command>mysql</command>, manually execute the SQL
+ commands contained in <command>mysql_install_db</command>.
+ Make sure that you run <command>mysqladmin
+ flush-privileges</command> or <command>mysqladmin
+ reload</command> afterward to tell the server to reload
+ the grant tables.
+ </para>
+
+ <para>
+ Note that by not using
+ <command>mysql_install_db</command>, you not only have to
+ populate the grant tables manually, you also have to
+ create them first.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
</section>
<section id="automatic-start">
@@ -17160,20 +17160,101 @@
</section>
- <section id="sco-unixware">
+ <section id="sco-openserver">
- <title>&title-sco-unixware;</title>
+ <title>&title-sco-openserver;</title>
<para>
+ Key improvements of OpenServer 6 include:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Larger file support up to 1 TB
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Multiprocessor support increased from 4 to 32 processors
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Increased memory support up to 64 GB
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Extending the power of UnixWare into OpenServer 6
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Dramatic performance improvement
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ OpenServer 6.0.0 has the following:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <filename>/bin</filename> is for commands that behave
+ exactly the same as on OpenServer 5.0.x.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>/u95/bin</filename> is for commands that have
+ better standards conformance, for example Large File
+ System (LFS) support.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>/udk/bin</filename> is for commands that behave
+ the same as on UnixWare 7.1.4. The default is for the LFS
+ support.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ The following is a guide to setting <literal>PATH</literal> on
+ OpenServer 6. If the user wants the traditional OpenServer
+ 5.0.x then <literal>PATH</literal> should be
+ <filename>/bin</filename> first. If the user wants LFS
+ support, the path should be
+ <filename>/u95/bin:/bin</filename>. If the user wants UnixWare
+ 7 support first, the path would be
+ <filename>/udk/bin:/u95/bin:/bin:</filename>.
+ </para>
+
+ <para>
We recommend using the latest production release of MySQL.
- Should you choose to use an older release of MySQL on UnixWare
- 7.1.x, you must use a version of MySQL at least as recent as
- 3.22.13 to get fixes for some portability and OS problems.
+ Should you choose to use an older release of MySQL on
+ OpenServer 6.0.x, you must use a version of MySQL at least as
+ recent as 3.22.13 to get fixes for some portability and OS
+ problems.
</para>
<para>
We have been able to compile MySQL with the following
- <command>configure</command> command on UnixWare 7.1.x:
+ <command>configure</command> command on OpenServer 6.0.x:
</para>
<programlisting>
@@ -17181,7 +17262,8 @@
CXX="CC" CXXFLAGS="-I/usr/local/include" \
./configure --prefix=/usr/local/mysql \
--enable-thread-safe-client --with-berkeley-db=./bdb \
- --with-innodb --with-openssl --with-extra-charsets=complex
+ --with-innodb --with-openssl --with-extra-charsets=complex \
+ --enable-readline
</programlisting>
<para>
@@ -17254,59 +17336,35 @@
<para>
This allows both the shared and dynamic libraries to be made
- and work.
+ and work. OpenServer 6.0.0 also needs patches to the MySQL
+ source tree and the patch for
+ <filename>config.guess</filename> applied to
+ <filename>bdb/dist/config.guess</filename>. You can download
+ the patches from
+ <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.1.12-osr6-patches.tar.gz"/>
+ and from
+ <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.x.x-osr6-patches"/>.
+ There is a <filename>README</filename> file there to assist.
</para>
<para>
- SCO provides operating system patches at
- <ulink url="ftp://ftp.sco.com/pub/unixware7"/> for UnixWare
- 7.1.1, <ulink url="ftp://ftp.sco.com/pub/unixware7/713/"/> for
- UnixWare 7.1.3,
- <ulink url="ftp://ftp.sco.com/pub/unixware7/714/"/> for
- UnixWare 7.1.4, and
- <ulink url="ftp://ftp.sco.com/pub/openunix8"/> for OpenUNIX
- 8.0.0.
+ SCO provides OpenServer 6 operating system patches at
+ <ulink url="ftp://ftp.sco.com/pub/openserver6"/>.
</para>
<para>
SCO provides information about security fixes at
- <ulink url="ftp://ftp.sco.com/pub/security/OpenUNIX"/> for
- OpenUNIX and
- <ulink url="ftp://ftp.sco.com/pub/security/UnixWare"/> for
- UnixWare.
+ <ulink url="ftp://ftp.sco.com/pub/security/OpenServer"/>.
</para>
<para>
- By default, the maximum file size on a UnixWare 7.1.1 system
- is 1GB, but UnixWare 7.1.4 file size limit is 1 TB with VXFS.
- Some OS utilities have a limitation of 2GB. The maximum
- possible file size on UnixWare 7 is 1TB with VXFS.
+ By default, the maximum file size on a OpenServer 6.0.0 system
+ is 1TB. Some operating system utilities have a limitation of
+ 2GB. The maximum possible file size on UnixWare 7 is 1TB with
+ VXFS or HTFS.
</para>
<para>
- On UnixWare 7.1.4 you do not need to do anything to get large
- file support, but to enable large file support on prior
- versions of UnixWare 7.1.x, run <literal>fsadm</literal>.
- </para>
-
-<programlisting>
-# fsadm -Fvxfs -o largefiles /
-# fsadm / * Note
-# ulimit unlimited
-# cd /etc/conf/bin
-# ./idtune SFSZLIM 0x7FFFFFFF ** Note
-# ./idtune HFSZLIM 0x7FFFFFFF ** Note
-# ./idbuild -B
-
-* This should report "largefiles".
-** 0x7FFFFFFF represents infinity for these values.
-</programlisting>
-
- <para>
- Reboot the system using <literal>shutdown</literal>.
- </para>
-
- <para>
By default, the entries in
<filename>/etc/conf/cf.d/mtune</filename> are set to:
</para>
@@ -17372,8 +17430,8 @@
</programlisting>
<para>
- 13 is what has been found to be the best for both Progress and
- MySQL.
+ <literal>13</literal> has been found to be best for both
+ Progress and MySQL.
</para>
<para>
@@ -17401,101 +17459,20 @@
</section>
- <section id="sco-openserver">
+ <section id="sco-unixware">
- <title>&title-sco-openserver;</title>
+ <title>&title-sco-unixware;</title>
<para>
- Key improvements of OpenServer 6 include:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Larger file support up to 1 TB
- </para>
- </listitem>
-
- <listitem>
- <para>
- Multiprocessor support increased from 4 to 32 processors
- </para>
- </listitem>
-
- <listitem>
- <para>
- Increased memory support up to 64 GB
- </para>
- </listitem>
-
- <listitem>
- <para>
- Extending the power of UnixWare into OpenServer 6
- </para>
- </listitem>
-
- <listitem>
- <para>
- Dramatic performance improvement
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- OpenServer 6.0.0 has the following:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <filename>/bin</filename> is for commands that behave
- exactly the same as on OpenServer 5.0.x.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <filename>/u95/bin</filename> is for commands that have
- better standards conformance, for example Large File
- System (LFS) support.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <filename>/udk/bin</filename> is for commands that behave
- the same as on UnixWare 7.1.4. The default is for the LFS
- support.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- The following is a guide to setting <literal>PATH</literal> on
- OpenServer 6. If the user wants the traditional OpenServer
- 5.0.x then <literal>PATH</literal> should be
- <filename>/bin</filename> first. If the user wants LFS
- support, the path should be
- <filename>/u95/bin:/bin</filename>. If the user wants UnixWare
- 7 support first, the path would be
- <filename>/udk/bin:/u95/bin:/bin:</filename>.
- </para>
-
- <para>
We recommend using the latest production release of MySQL.
- Should you choose to use an older release of MySQL on
- OpenServer 6.0.x, you must use a version of MySQL at least as
- recent as 3.22.13 to get fixes for some portability and OS
- problems.
+ Should you choose to use an older release of MySQL on UnixWare
+ 7.1.x, you must use a version of MySQL at least as recent as
+ 3.22.13 to get fixes for some portability and OS problems.
</para>
<para>
We have been able to compile MySQL with the following
- <command>configure</command> command on OpenServer 6.0.x:
+ <command>configure</command> command on UnixWare 7.1.x:
</para>
<programlisting>
@@ -17503,8 +17480,7 @@
CXX="CC" CXXFLAGS="-I/usr/local/include" \
./configure --prefix=/usr/local/mysql \
--enable-thread-safe-client --with-berkeley-db=./bdb \
- --with-innodb --with-openssl --with-extra-charsets=complex \
- --enable-readline
+ --with-innodb --with-openssl --with-extra-charsets=complex
</programlisting>
<para>
@@ -17577,35 +17553,59 @@
<para>
This allows both the shared and dynamic libraries to be made
- and work. OpenServer 6.0.0 also needs patches to the MySQL
- source tree and the patch for
- <filename>config.guess</filename> applied to
- <filename>bdb/dist/config.guess</filename>. You can download
- the patches from
- <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.1.12-osr6-patches.tar.gz"/>
- and from
- <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.x.x-osr6-patches"/>.
- There is a <filename>README</filename> file there to assist.
+ and work.
</para>
<para>
- SCO provides OpenServer 6 operating system patches at
- <ulink url="ftp://ftp.sco.com/pub/openserver6"/>.
+ SCO provides operating system patches at
+ <ulink url="ftp://ftp.sco.com/pub/unixware7"/> for UnixWare
+ 7.1.1, <ulink url="ftp://ftp.sco.com/pub/unixware7/713/"/> for
+ UnixWare 7.1.3,
+ <ulink url="ftp://ftp.sco.com/pub/unixware7/714/"/> for
+ UnixWare 7.1.4, and
+ <ulink url="ftp://ftp.sco.com/pub/openunix8"/> for OpenUNIX
+ 8.0.0.
</para>
<para>
SCO provides information about security fixes at
- <ulink url="ftp://ftp.sco.com/pub/security/OpenServer"/>.
+ <ulink url="ftp://ftp.sco.com/pub/security/OpenUNIX"/> for
+ OpenUNIX and
+ <ulink url="ftp://ftp.sco.com/pub/security/UnixWare"/> for
+ UnixWare.
</para>
<para>
- By default, the maximum file size on a OpenServer 6.0.0 system
- is 1TB. Some operating system utilities have a limitation of
- 2GB. The maximum possible file size on UnixWare 7 is 1TB with
- VXFS or HTFS.
+ By default, the maximum file size on a UnixWare 7.1.1 system
+ is 1GB, but UnixWare 7.1.4 file size limit is 1 TB with VXFS.
+ Some OS utilities have a limitation of 2GB. The maximum
+ possible file size on UnixWare 7 is 1TB with VXFS.
</para>
<para>
+ On UnixWare 7.1.4 you do not need to do anything to get large
+ file support, but to enable large file support on prior
+ versions of UnixWare 7.1.x, run <literal>fsadm</literal>.
+ </para>
+
+<programlisting>
+# fsadm -Fvxfs -o largefiles /
+# fsadm / * Note
+# ulimit unlimited
+# cd /etc/conf/bin
+# ./idtune SFSZLIM 0x7FFFFFFF ** Note
+# ./idtune HFSZLIM 0x7FFFFFFF ** Note
+# ./idbuild -B
+
+* This should report "largefiles".
+** 0x7FFFFFFF represents infinity for these values.
+</programlisting>
+
+ <para>
+ Reboot the system using <literal>shutdown</literal>.
+ </para>
+
+ <para>
By default, the entries in
<filename>/etc/conf/cf.d/mtune</filename> are set to:
</para>
@@ -17671,8 +17671,8 @@
</programlisting>
<para>
- <literal>13</literal> has been found to be best for both
- Progress and MySQL.
+ 13 is what has been found to be the best for both Progress and
+ MySQL.
</para>
<para>
Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml 2006-01-11 20:39:12 UTC (rev 767)
+++ trunk/refman-5.0/installing.xml 2006-01-11 20:54:58 UTC (rev 768)
@@ -10041,116 +10041,6 @@
<command>mysql_install_db</command>, see
<xref linkend="mysql-install-db"/>.
</para>
-
- <para>
- There are some alternatives to running the
- <command>mysql_install_db</command> script as it is provided
- in the MySQL distribution:
- </para>
-
- <indexterm>
- <primary>grant tables</primary>
- <secondary>re-creating</secondary>
- </indexterm>
-
- <indexterm>
- <primary>re-creating</primary>
- <secondary>grant tables</secondary>
- </indexterm>
-
- <itemizedlist>
-
- <listitem>
- <para>
- If you want the initial privileges to be different from
- the standard defaults, you can modify
- <command>mysql_install_db</command> before you run it.
- However, it is preferable to use
- <literal>GRANT</literal> and <literal>REVOKE</literal>
- to change the privileges <emphasis>after</emphasis> the
- grant tables have been set up. In other words, you can
- run <command>mysql_install_db</command>, and then use
- <literal>mysql -u root mysql</literal> to connect to the
- server as the MySQL <literal>root</literal> user so that
- you can issue the necessary <literal>GRANT</literal> and
- <literal>REVOKE</literal> statements.
- </para>
-
- <para>
- If you want to install MySQL on several machines with
- the same privileges, you can put the
- <literal>GRANT</literal> and <literal>REVOKE</literal>
- statements in a file and execute the file as a script
- using <literal>mysql</literal> after running
- <command>mysql_install_db</command>. For example:
- </para>
-
-<programlisting>
-shell> <userinput>bin/mysql_install_db --user=mysql</userinput>
-shell> <userinput>bin/mysql -u root < your_script_file</userinput>
-</programlisting>
-
- <para>
- By doing this, you can avoid having to issue the
- statements manually on each machine.
- </para>
- </listitem>
-
- <listitem>
- <para>
- It is possible to re-create the grant tables completely
- after they have previously been created. You might want
- to do this if you're just learning how to use
- <literal>GRANT</literal> and <literal>REVOKE</literal>
- and have made so many modifications after running
- <command>mysql_install_db</command> that you want to
- wipe out the tables and start over.
- </para>
-
- <para>
- To re-create the grant tables, remove all the
- <filename>.frm</filename>, <filename>.MYI</filename>,
- and <filename>.MYD</filename> files in the directory
- containing the <literal>mysql</literal> database. (This
- is the directory named <filename>mysql</filename> under
- the data directory, which is listed as the
- <literal>datadir</literal> value when you run
- <command>mysqld --help</command>.) Then run the
- <command>mysql_install_db</command> script again.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You can start <command>mysqld</command> manually using
- the <option>--skip-grant-tables</option> option and add
- the privilege information yourself using
- <command>mysql</command>:
- </para>
-
-<programlisting>
-shell> <userinput>bin/mysqld_safe --user=mysql --skip-grant-tables &</userinput>
-shell> <userinput>bin/mysql mysql</userinput>
-</programlisting>
-
- <para>
- From <command>mysql</command>, manually execute the SQL
- commands contained in
- <command>mysql_install_db</command>. Make sure that you
- run <command>mysqladmin flush-privileges</command> or
- <command>mysqladmin reload</command> afterward to tell
- the server to reload the grant tables.
- </para>
-
- <para>
- Note that by not using
- <command>mysql_install_db</command>, you not only have
- to populate the grant tables manually, you also have to
- create them first.
- </para>
- </listitem>
-
- </itemizedlist>
</listitem>
<listitem>
@@ -10631,6 +10521,116 @@
</itemizedlist>
+ <para>
+ There are some alternatives to running the
+ <command>mysql_install_db</command> script as it is provided
+ in the MySQL distribution:
+ </para>
+
+ <indexterm>
+ <primary>grant tables</primary>
+ <secondary>re-creating</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>re-creating</primary>
+ <secondary>grant tables</secondary>
+ </indexterm>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ If you want the initial privileges to be different from
+ the standard defaults, you can modify
+ <command>mysql_install_db</command> before you run it.
+ However, it is preferable to use
+ <literal>GRANT</literal> and <literal>REVOKE</literal>
+ to change the privileges <emphasis>after</emphasis> the
+ grant tables have been set up. In other words, you can
+ run <command>mysql_install_db</command>, and then use
+ <literal>mysql -u root mysql</literal> to connect to the
+ server as the MySQL <literal>root</literal> user so that
+ you can issue the necessary <literal>GRANT</literal> and
+ <literal>REVOKE</literal> statements.
+ </para>
+
+ <para>
+ If you want to install MySQL on several machines with
+ the same privileges, you can put the
+ <literal>GRANT</literal> and <literal>REVOKE</literal>
+ statements in a file and execute the file as a script
+ using <literal>mysql</literal> after running
+ <command>mysql_install_db</command>. For example:
+ </para>
+
+<programlisting>
+shell> <userinput>bin/mysql_install_db --user=mysql</userinput>
+shell> <userinput>bin/mysql -u root < your_script_file</userinput>
+</programlisting>
+
+ <para>
+ By doing this, you can avoid having to issue the
+ statements manually on each machine.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ It is possible to re-create the grant tables completely
+ after they have previously been created. You might want
+ to do this if you're just learning how to use
+ <literal>GRANT</literal> and <literal>REVOKE</literal>
+ and have made so many modifications after running
+ <command>mysql_install_db</command> that you want to
+ wipe out the tables and start over.
+ </para>
+
+ <para>
+ To re-create the grant tables, remove all the
+ <filename>.frm</filename>, <filename>.MYI</filename>,
+ and <filename>.MYD</filename> files in the directory
+ containing the <literal>mysql</literal> database. (This
+ is the directory named <filename>mysql</filename> under
+ the data directory, which is listed as the
+ <literal>datadir</literal> value when you run
+ <command>mysqld --help</command>.) Then run the
+ <command>mysql_install_db</command> script again.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ You can start <command>mysqld</command> manually using
+ the <option>--skip-grant-tables</option> option and add
+ the privilege information yourself using
+ <command>mysql</command>:
+ </para>
+
+<programlisting>
+shell> <userinput>bin/mysqld_safe --user=mysql --skip-grant-tables &</userinput>
+shell> <userinput>bin/mysql mysql</userinput>
+</programlisting>
+
+ <para>
+ From <command>mysql</command>, manually execute the SQL
+ commands contained in
+ <command>mysql_install_db</command>. Make sure that you
+ run <command>mysqladmin flush-privileges</command> or
+ <command>mysqladmin reload</command> afterward to tell
+ the server to reload the grant tables.
+ </para>
+
+ <para>
+ Note that by not using
+ <command>mysql_install_db</command>, you not only have
+ to populate the grant tables manually, you also have to
+ create them first.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
</section>
<section id="automatic-start">
@@ -16328,17 +16328,96 @@
</section>
- <section id="sco-unixware">
+ <section id="sco-openserver">
- <title>&title-sco-unixware;</title>
+ <title>&title-sco-openserver;</title>
<para>
+ Key improvements of OpenServer 6 include:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Larger file support up to 1 TB
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Multiprocessor support increased from 4 to 32 processors
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Increased memory support up to 64 GB
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Extending the power of UnixWare into OpenServer 6
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Dramatic performance improvement
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ OpenServer 6.0.0 has the following:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <filename>/bin</filename> is for commands that behave
+ exactly the same as on OpenServer 5.0.x.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>/u95/bin</filename> is for commands that have
+ better standards conformance, for example Large File
+ System (LFS) support.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>/udk/bin</filename> is for commands that behave
+ the same as on UnixWare 7.1.4. The default is for the LFS
+ support.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ The following is a guide to setting PATH on OpenServer 6. If
+ the user wants the traditional OpenServer 5.0.x then
+ <literal>PATH</literal> should be <filename>/bin</filename>
+ first. If the user wants LFS support then the path should be
+ <filename>/u95/bin:/bin</filename>. If the user want UnixWare
+ 7 support first then the path would be
+ <filename>/udk/bin:/u95/bin:/bin:</filename>.
+ </para>
+
+ <para>
We recommend using the latest production release of MySQL.
</para>
<para>
We have been able to compile MySQL with the following
- <command>configure</command> command on UnixWare 7.1.x:
+ <command>configure</command> command on OpenServer 6.0.x:
</para>
<programlisting>
@@ -16346,7 +16425,8 @@
CXX="CC" CXXFLAGS="-I/usr/local/include" \
./configure --prefix=/usr/local/mysql \
--enable-thread-safe-client --with-berkeley-db=./bdb \
- --with-innodb --with-openssl --with-extra-charsets=complex
+ --with-innodb --with-openssl --with-extra-charsets=complex \
+ --enable-readline
</programlisting>
<para>
@@ -16419,59 +16499,35 @@
<para>
This allows both the shared and dynamic libraries to be made
- and work.
+ and work. OpenServer 6.0.0 also needs patches to the MySQL
+ source tree and the patch for
+ <filename>config.guess</filename> applied to
+ <filename>bdb/dist/config.guess</filename>. You can download
+ the patches from
+ <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.1.12-osr6-patches.tar.gz"/>
+ and from
+ <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.x.x-osr6-patches"/>.
+ There is a <filename>README</filename> file there to assist.
</para>
<para>
- SCO provides operating system patches at
- <ulink url="ftp://ftp.sco.com/pub/unixware7"/> for UnixWare
- 7.1.1, <ulink url="ftp://ftp.sco.com/pub/unixware7/713/"/> for
- UnixWare 7.1.3,
- <ulink url="ftp://ftp.sco.com/pub/unixware7/714/"/> for
- UnixWare 7.1.4, and
- <ulink url="ftp://ftp.sco.com/pub/openunix8"/> for OpenUNIX
- 8.0.0.
+ SCO provides OpenServer 6 operating system patches at
+ <ulink url="ftp://ftp.sco.com/pub/openserver6"/>.
</para>
<para>
SCO provides information about security fixes at
- <ulink url="ftp://ftp.sco.com/pub/security/OpenUNIX"/> for
- OpenUNIX and
- <ulink url="ftp://ftp.sco.com/pub/security/UnixWare"/> for
- UnixWare.
+ <ulink url="ftp://ftp.sco.com/pub/security/OpenServer"/>.
</para>
<para>
- By default, the maximum file size on a UnixWare 7.1.1 system
- is 1GB, but UnixWare 7.1.4 file size limit is 1 TB with VXFS.
- Some OS utilities have a limitation of 2GB. The maximum
- possible file size on UnixWare 7 is 1TB with VXFS.
+ By default, the maximum file size on a OpenServer 6.0.0 system
+ is 1TB. Some operating system utilities have a limitation of
+ 2GB. The maximum possible file size on UnixWare 7 is 1TB with
+ VXFS or HTFS.
</para>
<para>
- On UnixWare 7.1.4 you do not need to do anything to get large
- file support, but to enable large file support on prior
- versions of UnixWare 7.1.x, run <literal>fsadm</literal>.
- </para>
-
-<programlisting>
-# fsadm -Fvxfs -o largefiles /
-# fsadm / * Note
-# ulimit unlimited
-# cd /etc/conf/bin
-# ./idtune SFSZLIM 0x7FFFFFFF ** Note
-# ./idtune HFSZLIM 0x7FFFFFFF ** Note
-# ./idbuild -B
-
-* This should report "largefiles".
-** 0x7FFFFFFF represents infinity for these values.
-</programlisting>
-
- <para>
- Reboot the system using <literal>shutdown</literal>.
- </para>
-
- <para>
By default, the entries in
<filename>/etc/conf/cf.d/mtune</filename> are set to:
</para>
@@ -16566,96 +16622,17 @@
</section>
- <section id="sco-openserver">
+ <section id="sco-unixware">
- <title>&title-sco-openserver;</title>
+ <title>&title-sco-unixware;</title>
<para>
- Key improvements of OpenServer 6 include:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Larger file support up to 1 TB
- </para>
- </listitem>
-
- <listitem>
- <para>
- Multiprocessor support increased from 4 to 32 processors
- </para>
- </listitem>
-
- <listitem>
- <para>
- Increased memory support up to 64 GB
- </para>
- </listitem>
-
- <listitem>
- <para>
- Extending the power of UnixWare into OpenServer 6
- </para>
- </listitem>
-
- <listitem>
- <para>
- Dramatic performance improvement
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- OpenServer 6.0.0 has the following:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <filename>/bin</filename> is for commands that behave
- exactly the same as on OpenServer 5.0.x.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <filename>/u95/bin</filename> is for commands that have
- better standards conformance, for example Large File
- System (LFS) support.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <filename>/udk/bin</filename> is for commands that behave
- the same as on UnixWare 7.1.4. The default is for the LFS
- support.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- The following is a guide to setting PATH on OpenServer 6. If
- the user wants the traditional OpenServer 5.0.x then
- <literal>PATH</literal> should be <filename>/bin</filename>
- first. If the user wants LFS support then the path should be
- <filename>/u95/bin:/bin</filename>. If the user want UnixWare
- 7 support first then the path would be
- <filename>/udk/bin:/u95/bin:/bin:</filename>.
- </para>
-
- <para>
We recommend using the latest production release of MySQL.
</para>
<para>
We have been able to compile MySQL with the following
- <command>configure</command> command on OpenServer 6.0.x:
+ <command>configure</command> command on UnixWare 7.1.x:
</para>
<programlisting>
@@ -16663,8 +16640,7 @@
CXX="CC" CXXFLAGS="-I/usr/local/include" \
./configure --prefix=/usr/local/mysql \
--enable-thread-safe-client --with-berkeley-db=./bdb \
- --with-innodb --with-openssl --with-extra-charsets=complex \
- --enable-readline
+ --with-innodb --with-openssl --with-extra-charsets=complex
</programlisting>
<para>
@@ -16737,35 +16713,59 @@
<para>
This allows both the shared and dynamic libraries to be made
- and work. OpenServer 6.0.0 also needs patches to the MySQL
- source tree and the patch for
- <filename>config.guess</filename> applied to
- <filename>bdb/dist/config.guess</filename>. You can download
- the patches from
- <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.1.12-osr6-patches.tar.gz"/>
- and from
- <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.x.x-osr6-patches"/>.
- There is a <filename>README</filename> file there to assist.
+ and work.
</para>
<para>
- SCO provides OpenServer 6 operating system patches at
- <ulink url="ftp://ftp.sco.com/pub/openserver6"/>.
+ SCO provides operating system patches at
+ <ulink url="ftp://ftp.sco.com/pub/unixware7"/> for UnixWare
+ 7.1.1, <ulink url="ftp://ftp.sco.com/pub/unixware7/713/"/> for
+ UnixWare 7.1.3,
+ <ulink url="ftp://ftp.sco.com/pub/unixware7/714/"/> for
+ UnixWare 7.1.4, and
+ <ulink url="ftp://ftp.sco.com/pub/openunix8"/> for OpenUNIX
+ 8.0.0.
</para>
<para>
SCO provides information about security fixes at
- <ulink url="ftp://ftp.sco.com/pub/security/OpenServer"/>.
+ <ulink url="ftp://ftp.sco.com/pub/security/OpenUNIX"/> for
+ OpenUNIX and
+ <ulink url="ftp://ftp.sco.com/pub/security/UnixWare"/> for
+ UnixWare.
</para>
<para>
- By default, the maximum file size on a OpenServer 6.0.0 system
- is 1TB. Some operating system utilities have a limitation of
- 2GB. The maximum possible file size on UnixWare 7 is 1TB with
- VXFS or HTFS.
+ By default, the maximum file size on a UnixWare 7.1.1 system
+ is 1GB, but UnixWare 7.1.4 file size limit is 1 TB with VXFS.
+ Some OS utilities have a limitation of 2GB. The maximum
+ possible file size on UnixWare 7 is 1TB with VXFS.
</para>
<para>
+ On UnixWare 7.1.4 you do not need to do anything to get large
+ file support, but to enable large file support on prior
+ versions of UnixWare 7.1.x, run <literal>fsadm</literal>.
+ </para>
+
+<programlisting>
+# fsadm -Fvxfs -o largefiles /
+# fsadm / * Note
+# ulimit unlimited
+# cd /etc/conf/bin
+# ./idtune SFSZLIM 0x7FFFFFFF ** Note
+# ./idtune HFSZLIM 0x7FFFFFFF ** Note
+# ./idbuild -B
+
+* This should report "largefiles".
+** 0x7FFFFFFF represents infinity for these values.
+</programlisting>
+
+ <para>
+ Reboot the system using <literal>shutdown</literal>.
+ </para>
+
+ <para>
By default, the entries in
<filename>/etc/conf/cf.d/mtune</filename> are set to:
</para>
Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml 2006-01-11 20:39:12 UTC (rev 767)
+++ trunk/refman-5.1/installing.xml 2006-01-11 20:54:58 UTC (rev 768)
@@ -10043,116 +10043,6 @@
<command>mysql_install_db</command>, see
<xref linkend="mysql-install-db"/>.
</para>
-
- <para>
- There are some alternatives to running the
- <command>mysql_install_db</command> script as it is provided
- in the MySQL distribution:
- </para>
-
- <indexterm>
- <primary>grant tables</primary>
- <secondary>re-creating</secondary>
- </indexterm>
-
- <indexterm>
- <primary>re-creating</primary>
- <secondary>grant tables</secondary>
- </indexterm>
-
- <itemizedlist>
-
- <listitem>
- <para>
- If you want the initial privileges to be different from
- the standard defaults, you can modify
- <command>mysql_install_db</command> before you run it.
- However, it is preferable to use
- <literal>GRANT</literal> and <literal>REVOKE</literal>
- to change the privileges <emphasis>after</emphasis> the
- grant tables have been set up. In other words, you can
- run <command>mysql_install_db</command>, and then use
- <literal>mysql -u root mysql</literal> to connect to the
- server as the MySQL <literal>root</literal> user so that
- you can issue the necessary <literal>GRANT</literal> and
- <literal>REVOKE</literal> statements.
- </para>
-
- <para>
- If you want to install MySQL on several machines with
- the same privileges, you can put the
- <literal>GRANT</literal> and <literal>REVOKE</literal>
- statements in a file and execute the file as a script
- using <literal>mysql</literal> after running
- <command>mysql_install_db</command>. For example:
- </para>
-
-<programlisting>
-shell> <userinput>bin/mysql_install_db --user=mysql</userinput>
-shell> <userinput>bin/mysql -u root < your_script_file</userinput>
-</programlisting>
-
- <para>
- By doing this, you can avoid having to issue the
- statements manually on each machine.
- </para>
- </listitem>
-
- <listitem>
- <para>
- It is possible to re-create the grant tables completely
- after they have previously been created. You might want
- to do this if you're just learning how to use
- <literal>GRANT</literal> and <literal>REVOKE</literal>
- and have made so many modifications after running
- <command>mysql_install_db</command> that you want to
- wipe out the tables and start over.
- </para>
-
- <para>
- To re-create the grant tables, remove all the
- <filename>.frm</filename>, <filename>.MYI</filename>,
- and <filename>.MYD</filename> files in the directory
- containing the <literal>mysql</literal> database. (This
- is the directory named <filename>mysql</filename> under
- the data directory, which is listed as the
- <literal>datadir</literal> value when you run
- <command>mysqld --help</command>.) Then run the
- <command>mysql_install_db</command> script again.
- </para>
- </listitem>
-
- <listitem>
- <para>
- You can start <command>mysqld</command> manually using
- the <option>--skip-grant-tables</option> option and add
- the privilege information yourself using
- <command>mysql</command>:
- </para>
-
-<programlisting>
-shell> <userinput>bin/mysqld_safe --user=mysql --skip-grant-tables &</userinput>
-shell> <userinput>bin/mysql mysql</userinput>
-</programlisting>
-
- <para>
- From <command>mysql</command>, manually execute the SQL
- commands contained in
- <command>mysql_install_db</command>. Make sure that you
- run <command>mysqladmin flush-privileges</command> or
- <command>mysqladmin reload</command> afterward to tell
- the server to reload the grant tables.
- </para>
-
- <para>
- Note that by not using
- <command>mysql_install_db</command>, you not only have
- to populate the grant tables manually, you also have to
- create them first.
- </para>
- </listitem>
-
- </itemizedlist>
</listitem>
<listitem>
@@ -10633,6 +10523,116 @@
</itemizedlist>
+ <para>
+ There are some alternatives to running the
+ <command>mysql_install_db</command> script as it is provided
+ in the MySQL distribution:
+ </para>
+
+ <indexterm>
+ <primary>grant tables</primary>
+ <secondary>re-creating</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>re-creating</primary>
+ <secondary>grant tables</secondary>
+ </indexterm>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ If you want the initial privileges to be different from
+ the standard defaults, you can modify
+ <command>mysql_install_db</command> before you run it.
+ However, it is preferable to use <literal>GRANT</literal>
+ and <literal>REVOKE</literal> to change the privileges
+ <emphasis>after</emphasis> the grant tables have been set
+ up. In other words, you can run
+ <command>mysql_install_db</command>, and then use
+ <literal>mysql -u root mysql</literal> to connect to the
+ server as the MySQL <literal>root</literal> user so that
+ you can issue the necessary <literal>GRANT</literal> and
+ <literal>REVOKE</literal> statements.
+ </para>
+
+ <para>
+ If you want to install MySQL on several machines with the
+ same privileges, you can put the <literal>GRANT</literal>
+ and <literal>REVOKE</literal> statements in a file and
+ execute the file as a script using
+ <literal>mysql</literal> after running
+ <command>mysql_install_db</command>. For example:
+ </para>
+
+<programlisting>
+shell> <userinput>bin/mysql_install_db --user=mysql</userinput>
+shell> <userinput>bin/mysql -u root < your_script_file</userinput>
+</programlisting>
+
+ <para>
+ By doing this, you can avoid having to issue the
+ statements manually on each machine.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ It is possible to re-create the grant tables completely
+ after they have previously been created. You might want to
+ do this if you're just learning how to use
+ <literal>GRANT</literal> and <literal>REVOKE</literal> and
+ have made so many modifications after running
+ <command>mysql_install_db</command> that you want to wipe
+ out the tables and start over.
+ </para>
+
+ <para>
+ To re-create the grant tables, remove all the
+ <filename>.frm</filename>, <filename>.MYI</filename>, and
+ <filename>.MYD</filename> files in the directory
+ containing the <literal>mysql</literal> database. (This is
+ the directory named <filename>mysql</filename> under the
+ data directory, which is listed as the
+ <literal>datadir</literal> value when you run
+ <command>mysqld --help</command>.) Then run the
+ <command>mysql_install_db</command> script again.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ You can start <command>mysqld</command> manually using the
+ <option>--skip-grant-tables</option> option and add the
+ privilege information yourself using
+ <command>mysql</command>:
+ </para>
+
+<programlisting>
+shell> <userinput>bin/mysqld_safe --user=mysql --skip-grant-tables &</userinput>
+shell> <userinput>bin/mysql mysql</userinput>
+</programlisting>
+
+ <para>
+ From <command>mysql</command>, manually execute the SQL
+ commands contained in <command>mysql_install_db</command>.
+ Make sure that you run <command>mysqladmin
+ flush-privileges</command> or <command>mysqladmin
+ reload</command> afterward to tell the server to reload
+ the grant tables.
+ </para>
+
+ <para>
+ Note that by not using
+ <command>mysql_install_db</command>, you not only have to
+ populate the grant tables manually, you also have to
+ create them first.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
</section>
<section id="automatic-start">
@@ -15640,17 +15640,96 @@
</section>
- <section id="sco-unixware">
+ <section id="sco-openserver">
- <title>&title-sco-unixware;</title>
+ <title>&title-sco-openserver;</title>
<para>
+ Key improvements of OpenServer 6 include:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Larger file support up to 1 TB
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Multiprocessor support increased from 4 to 32 processors
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Increased memory support up to 64 GB
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Extending the power of UnixWare into OpenServer 6
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Dramatic performance improvement
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ OpenServer 6.0.0 has the following:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <filename>/bin</filename> is for commands that behave
+ exactly the same as on OpenServer 5.0.x.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>/u95/bin</filename> is for commands that have
+ better standards conformance, for example Large File
+ System (LFS) support.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>/udk/bin</filename> is for commands that behave
+ the same as on UnixWare 7.1.4. The default is for the LFS
+ support.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ The following is a guide to setting PATH on OpenServer 6. If
+ the user wants the traditional OpenServer 5.0.x then
+ <literal>PATH</literal> should be <filename>/bin</filename>
+ first. If the user wants LFS support then the path should be
+ <filename>/u95/bin:/bin</filename>. If the user want UnixWare
+ 7 support first then the path would be
+ <filename>/udk/bin:/u95/bin:/bin:</filename>.
+ </para>
+
+ <para>
We recommend using the latest production release of MySQL.
</para>
<para>
We have been able to compile MySQL with the following
- <command>configure</command> command on UnixWare 7.1.x:
+ <command>configure</command> command on OpenServer 6.0.x:
</para>
<programlisting>
@@ -15658,7 +15737,8 @@
CXX="CC" CXXFLAGS="-I/usr/local/include" \
./configure --prefix=/usr/local/mysql \
--enable-thread-safe-client --with-berkeley-db=./bdb \
- --with-innodb --with-openssl --with-extra-charsets=complex
+ --with-innodb --with-openssl --with-extra-charsets=complex \
+ --enable-readline
</programlisting>
<para>
@@ -15731,59 +15811,35 @@
<para>
This allows both the shared and dynamic libraries to be made
- and work.
+ and work. OpenServer 6.0.0 also needs patches to the MySQL
+ source tree and the patch for
+ <filename>config.guess</filename> applied to
+ <filename>bdb/dist/config.guess</filename>. You can download
+ the patches from
+ <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.1.12-osr6-patches.tar.gz"/>
+ and from
+ <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.x.x-osr6-patches"/>.
+ There is a <filename>README</filename> file there to assist.
</para>
<para>
- SCO provides operating system patches at
- <ulink url="ftp://ftp.sco.com/pub/unixware7"/> for UnixWare
- 7.1.1, <ulink url="ftp://ftp.sco.com/pub/unixware7/713/"/> for
- UnixWare 7.1.3,
- <ulink url="ftp://ftp.sco.com/pub/unixware7/714/"/> for
- UnixWare 7.1.4, and
- <ulink url="ftp://ftp.sco.com/pub/openunix8"/> for OpenUNIX
- 8.0.0.
+ SCO provides OpenServer 6 operating system patches at
+ <ulink url="ftp://ftp.sco.com/pub/openserver6"/>.
</para>
<para>
SCO provides information about security fixes at
- <ulink url="ftp://ftp.sco.com/pub/security/OpenUNIX"/> for
- OpenUNIX and
- <ulink url="ftp://ftp.sco.com/pub/security/UnixWare"/> for
- UnixWare.
+ <ulink url="ftp://ftp.sco.com/pub/security/OpenServer"/>.
</para>
<para>
- By default, the maximum file size on a UnixWare 7.1.1 system
- is 1GB, but UnixWare 7.1.4 file size limit is 1 TB with VXFS.
- Some OS utilities have a limitation of 2GB. The maximum
- possible file size on UnixWare 7 is 1TB with VXFS.
+ By default, the maximum file size on a OpenServer 6.0.0 system
+ is 1TB. Some operating system utilities have a limitation of
+ 2GB. The maximum possible file size on UnixWare 7 is 1TB with
+ VXFS or HTFS.
</para>
<para>
- On UnixWare 7.1.4 you do not need to do anything to get large
- file support, but to enable large file support on prior
- versions of UnixWare 7.1.x, run <literal>fsadm</literal>.
- </para>
-
-<programlisting>
-# fsadm -Fvxfs -o largefiles /
-# fsadm / * Note
-# ulimit unlimited
-# cd /etc/conf/bin
-# ./idtune SFSZLIM 0x7FFFFFFF ** Note
-# ./idtune HFSZLIM 0x7FFFFFFF ** Note
-# ./idbuild -B
-
-* This should report "largefiles".
-** 0x7FFFFFFF represents infinity for these values.
-</programlisting>
-
- <para>
- Reboot the system using <literal>shutdown</literal>.
- </para>
-
- <para>
By default, the entries in
<filename>/etc/conf/cf.d/mtune</filename> are set to:
</para>
@@ -15878,96 +15934,17 @@
</section>
- <section id="sco-openserver">
+ <section id="sco-unixware">
- <title>&title-sco-openserver;</title>
+ <title>&title-sco-unixware;</title>
<para>
- Key improvements of OpenServer 6 include:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Larger file support up to 1 TB
- </para>
- </listitem>
-
- <listitem>
- <para>
- Multiprocessor support increased from 4 to 32 processors
- </para>
- </listitem>
-
- <listitem>
- <para>
- Increased memory support up to 64 GB
- </para>
- </listitem>
-
- <listitem>
- <para>
- Extending the power of UnixWare into OpenServer 6
- </para>
- </listitem>
-
- <listitem>
- <para>
- Dramatic performance improvement
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- OpenServer 6.0.0 has the following:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- <filename>/bin</filename> is for commands that behave
- exactly the same as on OpenServer 5.0.x.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <filename>/u95/bin</filename> is for commands that have
- better standards conformance, for example Large File
- System (LFS) support.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <filename>/udk/bin</filename> is for commands that behave
- the same as on UnixWare 7.1.4. The default is for the LFS
- support.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- The following is a guide to setting PATH on OpenServer 6. If
- the user wants the traditional OpenServer 5.0.x then
- <literal>PATH</literal> should be <filename>/bin</filename>
- first. If the user wants LFS support then the path should be
- <filename>/u95/bin:/bin</filename>. If the user want UnixWare
- 7 support first then the path would be
- <filename>/udk/bin:/u95/bin:/bin:</filename>.
- </para>
-
- <para>
We recommend using the latest production release of MySQL.
</para>
<para>
We have been able to compile MySQL with the following
- <command>configure</command> command on OpenServer 6.0.x:
+ <command>configure</command> command on UnixWare 7.1.x:
</para>
<programlisting>
@@ -15975,8 +15952,7 @@
CXX="CC" CXXFLAGS="-I/usr/local/include" \
./configure --prefix=/usr/local/mysql \
--enable-thread-safe-client --with-berkeley-db=./bdb \
- --with-innodb --with-openssl --with-extra-charsets=complex \
- --enable-readline
+ --with-innodb --with-openssl --with-extra-charsets=complex
</programlisting>
<para>
@@ -16049,35 +16025,59 @@
<para>
This allows both the shared and dynamic libraries to be made
- and work. OpenServer 6.0.0 also needs patches to the MySQL
- source tree and the patch for
- <filename>config.guess</filename> applied to
- <filename>bdb/dist/config.guess</filename>. You can download
- the patches from
- <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.1.12-osr6-patches.tar.gz"/>
- and from
- <ulink url="ftp://ftp.zenez.com/pub/zenez/prgms/mysql-4.x.x-osr6-patches"/>.
- There is a <filename>README</filename> file there to assist.
+ and work.
</para>
<para>
- SCO provides OpenServer 6 operating system patches at
- <ulink url="ftp://ftp.sco.com/pub/openserver6"/>.
+ SCO provides operating system patches at
+ <ulink url="ftp://ftp.sco.com/pub/unixware7"/> for UnixWare
+ 7.1.1, <ulink url="ftp://ftp.sco.com/pub/unixware7/713/"/> for
+ UnixWare 7.1.3,
+ <ulink url="ftp://ftp.sco.com/pub/unixware7/714/"/> for
+ UnixWare 7.1.4, and
+ <ulink url="ftp://ftp.sco.com/pub/openunix8"/> for OpenUNIX
+ 8.0.0.
</para>
<para>
SCO provides information about security fixes at
- <ulink url="ftp://ftp.sco.com/pub/security/OpenServer"/>.
+ <ulink url="ftp://ftp.sco.com/pub/security/OpenUNIX"/> for
+ OpenUNIX and
+ <ulink url="ftp://ftp.sco.com/pub/security/UnixWare"/> for
+ UnixWare.
</para>
<para>
- By default, the maximum file size on a OpenServer 6.0.0 system
- is 1TB. Some operating system utilities have a limitation of
- 2GB. The maximum possible file size on UnixWare 7 is 1TB with
- VXFS or HTFS.
+ By default, the maximum file size on a UnixWare 7.1.1 system
+ is 1GB, but UnixWare 7.1.4 file size limit is 1 TB with VXFS.
+ Some OS utilities have a limitation of 2GB. The maximum
+ possible file size on UnixWare 7 is 1TB with VXFS.
</para>
<para>
+ On UnixWare 7.1.4 you do not need to do anything to get large
+ file support, but to enable large file support on prior
+ versions of UnixWare 7.1.x, run <literal>fsadm</literal>.
+ </para>
+
+<programlisting>
+# fsadm -Fvxfs -o largefiles /
+# fsadm / * Note
+# ulimit unlimited
+# cd /etc/conf/bin
+# ./idtune SFSZLIM 0x7FFFFFFF ** Note
+# ./idtune HFSZLIM 0x7FFFFFFF ** Note
+# ./idbuild -B
+
+* This should report "largefiles".
+** 0x7FFFFFFF represents infinity for these values.
+</programlisting>
+
+ <para>
+ Reboot the system using <literal>shutdown</literal>.
+ </para>
+
+ <para>
By default, the entries in
<filename>/etc/conf/cf.d/mtune</filename> are set to:
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r768 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 11 Jan |
