List:Commits« Previous MessageNext Message »
From:mc.brown Date:August 10 2010 10:04am
Subject:svn commit - mysqldoc@docsrva: r22165 - trunk/refman-5.1
View as plain text  
Author: mcbrown
Date: 2010-08-10 12:04:10 +0200 (Tue, 10 Aug 2010)
New Revision: 22165

Log:
Updating the installation notes on AIX and HP-UX, including DEPOT installation



Modified:
   trunk/refman-5.1/installing-aix.xml
   trunk/refman-5.1/installing-hpux.xml
   trunk/refman-5.1/renamed-nodes.txt


Modified: trunk/refman-5.1/installing-aix.xml
===================================================================
--- trunk/refman-5.1/installing-aix.xml	2010-08-10 09:34:56 UTC (rev 22164)
+++ trunk/refman-5.1/installing-aix.xml	2010-08-10 10:04:10 UTC (rev 22165)
Changed blocks: 3, Lines Added: 111, Lines Deleted: 199; 11708 bytes

@@ -5,22 +5,80 @@
   <!ENTITY % all.entities SYSTEM "all-entities.ent">
   %all.entities;
 ]>
-<section id="ibm-aix">
+<section id="mysql-installation-aix">
 
-  <title>Installing MySQL on AIX</title>
+  <title>Installing MySQL on IBM AIX</title>
 
   <indexterm>
+    <primary>installing</primary>
+    <secondary>installing on IBM-AIX</secondary>
+  </indexterm>
+
+  <indexterm>
     <primary>problems</primary>
     <secondary>installing on IBM-AIX</secondary>
   </indexterm>
 
   <para>
-    Automatic detection of <literal>xlC</literal> is missing from
-    Autoconf, so a number of variables need to be set before running
-    <command>configure</command>. The following example uses the IBM
-    compiler:
+    There are two ways you can install MySQL on AIX:
   </para>
 
+  <itemizedlist>
+
+    <listitem>
+      <para>
+        Using a binary tarball distribution provided at
+        <ulink url="&base-url-downloads;"/>. Please read the
+        <link linkend="mysql-installation-aix-general">general notes on
+        AIX installation</link> before continuing. For more information
+        on binary installations, see
+        <xref linkend="installing-binary"/>.
+      </para>
+    </listitem>
+
+    <listitem>
+      <para>
+        Using a source tarball and compiling MySQL. Please read the
+        <link linkend="mysql-installation-aix-general">general notes on
+        AIX installation</link> before continuing. You should also check
+        the instructions on
+        <link linkend="mysql-installation-aix-source">building on AIX
+        from source</link>. For general information on building from
+        source, see <xref linkend="installing-source"/>.
+      </para>
+    </listitem>
+
+  </itemizedlist>
+
+  <para id="mysql-installation-aix-general">
+    Some general notes on using MySQL on IBM AIX:
+  </para>
+
+  <itemizedlist>
+
+    <listitem>
+      <para>
+        If you have problems with threads on AIX 5.3, you should upgrade
+        AIX 5.3 to technology level 7 (5300-07).
+      </para>
+    </listitem>
+
+  </itemizedlist>
+
+  <para id="mysql-installation-aix-source">
+    Some general notes on building MySQL from source on IBM AIX:
+  </para>
+
+  <itemizedlist>
+
+    <listitem>
+      <para>
+        Automatic detection of <literal>xlC</literal> is missing from
+        Autoconf, so a number of variables need to be set before running
+        <command>configure</command>. The following example uses the IBM
+        compiler:
+      </para>
+
 <programlisting>
 export CC="xlc_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192 "
 export CXX="xlC_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192"

@@ -37,95 +95,41 @@
                 --enable-large-files
 </programlisting>
 
-  <para>
-    The preceding options are used to compile the MySQL distribution
-    that can be found at <ulink url="http://www-frec.bull.com/"/>.
-  </para>
+      <para>
+        The preceding options are used to compile the MySQL distribution
+        that can be found at <ulink url="http://www-frec.bull.com/"/>.
+      </para>
+    </listitem>
 
-  <para>
-    If you change the <option>-O3</option> to <option>-O2</option> in
-    the preceding <command>configure</command> line, you must also
-    remove the <option>-qstrict</option> option. This is a limitation in
-    the IBM C compiler.
-  </para>
+    <listitem>
+      <para>
+        If you change the <option>-O3</option> to <option>-O2</option>
+        in the preceding <command>configure</command> line, you must
+        also remove the <option>-qstrict</option> option. This is a
+        limitation in the IBM C compiler.
+      </para>
+    </listitem>
 
-  <para>
-    If you are using <command>gcc</command> to compile MySQL, you
-    <emphasis>must</emphasis> use the <option>-fno-exceptions</option>
-    flag, because the exception handling in <command>gcc</command> is
-    not thread-safe! There are also some known problems with IBM's
-    assembler that may cause it to generate bad code when used with
-    <command>gcc</command>.
-  </para>
+    <listitem>
+      <para>
+        If you are using <command>gcc</command> to compile MySQL, you
+        <emphasis>must</emphasis> use the
+        <option>-fno-exceptions</option> flag, because the exception
+        handling in <command>gcc</command> is not thread-safe. There are
+        also some known problems with IBM's assembler that may cause it
+        to generate bad code when used with <command>gcc</command>.
+      </para>
+    </listitem>
 
-  <para>
-    Use the following <command>configure</command> line with
-    <command>gcc</command> 2.95 on AIX:
-  </para>
+    <listitem>
+      <para>
+        If you have problems with signals (MySQL dies unexpectedly under
+        high load), you may have found an OS bug with threads and
+        signals. In this case, you can tell MySQL not to use signals by
+        configuring as follows:
+      </para>
 
 <programlisting>
-CC="gcc -pipe -mcpu=power -Wa,-many" \
-CXX="gcc -pipe -mcpu=power -Wa,-many" \
-CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti" \
-./configure --prefix=/usr/local/mysql --with-low-memory
-</programlisting>
-
-  <para>
-    The <option>-Wa,-many</option> option is necessary for the compile
-    to be successful. IBM is aware of this problem but is in no hurry to
-    fix it because of the workaround that is available. We do not know
-    if the <option>-fno-exceptions</option> is required with
-    <command>gcc</command> 2.95, but because MySQL doesn't use
-    exceptions and the option generates faster code, you should always
-    use it with <command>gcc</command>.
-  </para>
-
-  <para>
-    If you get a problem with assembler code, try changing the
-    <option>-mcpu=<replaceable>xxx</replaceable></option> option to
-    match your CPU. Typically <literal>power2</literal>,
-    <literal>power</literal>, or <literal>powerpc</literal> may need to
-    be used. Alternatively, you might need to use <literal>604</literal>
-    or <literal>604e</literal>. We are not positive but suspect that
-    <literal>power</literal> would likely be safe most of the time, even
-    on a power2 machine.
-  </para>
-
-  <para>
-    If you do not know what your CPU is, execute a <literal>uname
-    -m</literal> command. It produces a string that looks like
-    <literal>000514676700</literal>, with a format of
-    <literal>xxyyyyyymmss</literal> where <literal>xx</literal> and
-    <literal>ss</literal> are always <literal>00</literal>,
-    <literal>yyyyyy</literal> is a unique system ID and
-    <literal>mm</literal> is the ID of the CPU Planar. A chart of these
-    values can be found at
-    <ulink url="http://www16.boulder.ibm.com/pseries/en_US/cmds/aixcmds5/uname.htm"/>.
-  </para>
-
-  <remark>
-    older URL...
-    http://publib.boulder.ibm.com/doc_link/en_US/a_doc_lib/cmds/aixcmds5/uname.htm
-  </remark>
-
-  <para>
-    This gives you a machine type and a machine model you can use to
-    determine what type of CPU you have.
-  </para>
-
-  <para>
-    If you have problems with threads on AIX 5.3, you should upgrade AIX
-    5.3 to technology level 7 (5300-07).
-  </para>
-
-  <para>
-    If you have problems with signals (MySQL dies unexpectedly under
-    high load), you may have found an OS bug with threads and signals.
-    In this case, you can tell MySQL not to use signals by configuring
-    as follows:
-  </para>
-
-<programlisting>
 CFLAGS=-DDONT_USE_THR_ALARM CXX=gcc \
 CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti \
 -DDONT_USE_THR_ALARM" \

@@ -133,116 +137,24 @@
     --with-low-memory
 </programlisting>
 
-  <para>
-    This doesn't affect the performance of MySQL, but has the side
-    effect that you can't kill clients that are <quote>sleeping</quote>
-    on a connection with <command>mysqladmin kill</command> or
-    <command>mysqladmin shutdown</command>. Instead, the client dies
-    when it issues its next command.
-  </para>
+      <para>
+        This doesn't affect the performance of MySQL, but has the side
+        effect that you can't kill clients that are
+        <quote>sleeping</quote> on a connection with <command>mysqladmin
+        kill</command> or <command>mysqladmin shutdown</command>.
+        Instead, the client dies when it issues its next command.
+      </para>
+    </listitem>
 
-  <para>
-    On some versions of AIX, linking with <literal>libbind.a</literal>
-    makes <literal>getservbyname()</literal> dump core. This is an AIX
-    bug and should be reported to IBM.
-  </para>
+    <listitem>
+      <para>
+        On some versions of AIX, linking with
+        <literal>libbind.a</literal> makes
+        <literal>getservbyname()</literal> dump core. This is an AIX bug
+        and should be reported to IBM.
+      </para>
+    </listitem>
 
-  <para>
-    For AIX 4.2.1 and <command>gcc</command>, you have to make the
-    following changes.
-  </para>
+  </itemizedlist>
 
-  <para>
-    After configuring, edit <filename>config.h</filename> and
-    <filename>include/my_config.h</filename> and change the line that
-    says this:
-  </para>
-
-<programlisting>
-#define HAVE_SNPRINTF 1
-</programlisting>
-
-  <para>
-    to this:
-  </para>
-
-<programlisting>
-#undef HAVE_SNPRINTF
-</programlisting>
-
-  <para>
-    And finally, in <filename>mysqld.cc</filename>, you need to add a
-    prototype for <literal>initgroups()</literal>.
-  </para>
-
-<programlisting>
-#ifdef _AIX41
-extern "C" int initgroups(const char *,int);
-#endif
-</programlisting>
-
-  <para>
-    For 32-bit binaries, if you need to allocate a lot of memory to the
-    <command>mysqld</command> process, it is not enough to just use
-    <command>ulimit -d unlimited</command>. You may also have to modify
-    <command>mysqld_safe</command> to add a line something like this:
-  </para>
-
-<programlisting>
-export LDR_CNTRL='MAXDATA=0x80000000'
-</programlisting>
-
-  <para>
-    You can find more information about using a lot of memory at
-    <ulink url="http://publib16.boulder.ibm.com/pseries/en_US/aixprggd/genprogc/lrg_prg_support.htm"/>.
-  </para>
-
-  <para>
-    Users of AIX 4.3 should use <command>gmake</command> instead of the
-    <command>make</command> utility included with AIX.
-  </para>
-
-  <para>
-    As of AIX 4.1, the C compiler has been unbundled from AIX as a
-    separate product. <command>gcc</command> 3.3.2 can be obtained here:
-    <ulink url="ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/gcc/"/>
-  </para>
-
-  <para>
-    The steps for compiling MySQL on AIX with <command>gcc</command>
-    3.3.2 are similar to those for using <command>gcc</command> 2.95 (in
-    particular, the need to edit <filename>config.h</filename> and
-    <filename>my_config.h</filename> after running
-    <command>configure</command>). However, before running
-    <command>configure</command>, you should also patch the
-    <filename>curses.h</filename> file as follows:
-  </para>
-
-<programlisting>
-/opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/curses.h.ORIG
-       Mon Dec 26 02:17:28 2005
---- /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/curses.h
-Mon Dec 26 02:40:13 2005
-***************
-*** 2023,2029 ****
-
-
-  #endif /* _AIX32_CURSES */
-! #if defined(__USE_FIXED_PROTOTYPES__) || defined(__cplusplus) || defined
-(__STRICT_ANSI__)
-  extern int delwin (WINDOW *);
-  extern int endwin (void);
-  extern int getcurx (WINDOW *);
---- 2023,2029 ----
-
-
-  #endif /* _AIX32_CURSES */
-! #if 0 &amp;&amp; (defined(__USE_FIXED_PROTOTYPES__) || defined(__cplusplus)
-|| defined
-(__STRICT_ANSI__))
-  extern int delwin (WINDOW *);
-  extern int endwin (void);
-  extern int getcurx (WINDOW *);
-</programlisting>
-
 </section>


Modified: trunk/refman-5.1/installing-hpux.xml
===================================================================
--- trunk/refman-5.1/installing-hpux.xml	2010-08-10 09:34:56 UTC (rev 22164)
+++ trunk/refman-5.1/installing-hpux.xml	2010-08-10 10:04:10 UTC (rev 22165)
Changed blocks: 2, Lines Added: 110, Lines Deleted: 1; 3997 bytes

@@ -9,14 +9,30 @@
 
   <title>Installing MySQL on HP-UX</title>
 
+  <indexterm>
+    <primary>installing</primary>
+    <secondary>installing on HP-UX</secondary>
+  </indexterm>
+
   <para>
-    There are two ways you can install MySQL on HP-UX:
+    There are three ways you can install MySQL on HP-UX:
   </para>
 
   <itemizedlist>
 
     <listitem>
       <para>
+        Using a DEPOT distribution provided at
+        <ulink url="&base-url-downloads;"/>. Please read the
+        <link linkend="mysql-installation-hpux-general">general notes on
+        HP-UX installation</link> before continuing. For more
+        information on DEPOT installations, see
+        <xref linkend="mysql-installation-hpux-depot"/>.
+      </para>
+    </listitem>
+
+    <listitem>
+      <para>
         Using a binary tarball distribution provided at
         <ulink url="&base-url-downloads;"/>. Please read the
         <link linkend="mysql-installation-hpux-general">general notes on

@@ -135,4 +151,97 @@
 
   </itemizedlist>
 
+  <section id="mysql-installation-hpux-depot">
+
+    <title>Installing MySQL using DEPOT on HP-UX</title>
+
+    <para>
+      The HP-UX DEPOT format packages can be installed using the
+      <command>swinstall</command> command. You should install the
+      <literal>ncurses</literal> and <literal>zlib</literal> libraries
+      before installing the MySQL DEPOT package. You can use the free
+      software <literal>depothelper</literal> tool to install these
+      packages and any dependencies for you automatically.
+    </para>
+
+    <para>
+      To install using the MySQL DEPOT packages, follow this guide:
+    </para>
+
+    <orderedlist>
+
+      <listitem>
+        <para>
+          Download the MySQL DEPOT package from
+          <ulink url="&base-url-downloads;"/>. You must decompress the
+          package before installation:
+        </para>
+
+<programlisting>
+root-shell&gt; gunzip mysql-5.1.48-hpux11.31-ia64-64bit.depot.gz
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          Install the DEPOT package using <command>swinstall</command>:
+        </para>
+
+<programlisting>root-shell&gt; swinstall -s <replaceable>mysql-5.1.49-hpux11.31-ia64-64bit.depot</replaceable></programlisting>
+
+        <para>
+          MySQL will be installed into a directory matching the depot
+          package name, within <filename>/usr/local</filename>. For
+          convenience, you may want to create a symbolic link to the
+          installed directory, for example:
+        </para>
+
+<programlisting>
+root-shell&gt; ln -s mysql-5.1.49-hpux11.31-ia64-64bit mysql
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          Your package is now installed. You should complete the
+          configuration of MySQL by creating a user and group:
+        </para>
+
+<programlisting>
+root-shell&gt; /usr/sbin/groupadd mysql
+root-shell&gt; /usr/sbin/useradd -g mysql -d /var/lib/mysql/ -s /bin/false mysql
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          Create the standard database using the new user/group you have
+          created, and set the permissions:
+        </para>
+
+<programlisting>
+root-shell&gt; cd /usr/local/
+root-shell&gt; scripts/mysql_install_db --user=mysql
+root-shell&gt; chown -R root .
+root-shell&gt; chown -R mysql data
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          Finally, secure your new installation by setting the root
+          passwords, and then start your MySQL server using the
+          <literal>mysql</literal> user:
+        </para>
+
+<programlisting>
+root-shell&gt; mysql_secure_installation
+root-shell&gt; mysqld_safe --user=mysql &amp;
+</programlisting>
+      </listitem>
+
+    </orderedlist>
+
+  </section>
+
 </section>


Modified: trunk/refman-5.1/renamed-nodes.txt
===================================================================
--- trunk/refman-5.1/renamed-nodes.txt	2010-08-10 09:34:56 UTC (rev 22164)
+++ trunk/refman-5.1/renamed-nodes.txt	2010-08-10 10:04:10 UTC (rev 22165)
Changed blocks: 2, Lines Added: 5, Lines Deleted: 4; 2092 bytes

@@ -44,6 +44,7 @@
 events-limitations-restrictions stored-program-restrictions 2009-09-19
 german-character-set charset-we-sets 2010-08-08
 group-by-hidden-fields group-by-hidden-columns 2010-01-01
+ibm-aix mysql-installation-aix 2011-08-01
 indexes column-indexes 2011-07-14
 innodb-and-autocommit innodb-transaction-model 2009-11-24
 innodb-consistent-read-example innodb-consistent-read 2010-03-10

@@ -182,14 +183,14 @@
 mysql-cluster-ndbd-command-options mysql-cluster-programs-ndbd 2010-05-05
 mysql-cluster-ndbd-process mysql-cluster-programs-ndbd 2010-05-05
 mysql-cluster-ndbmtd-process mysql-cluster-programs-ndbmtd 2010-05-05
+mysql-cluster-news-5-1-41-ndb-6-2-19 mysql-cluster-news-5-1-47-ndb-6-2-19 2011-03-15
+mysql-cluster-news-5-1-41-ndb-6-3-33 mysql-cluster-news-5-1-44-ndb-6-3-33 2011-03-15
+mysql-cluster-news-5-1-41-ndb-7-0-14 mysql-cluster-news-5-1-44-ndb-7-0-14 2011-03-15
+mysql-cluster-news-5-1-41-ndb-7-1-3 mysql-cluster-news-5-1-44-ndb-7-1-3 2011-03-15
 mysql-cluster-news-5-1-44-ndb-6-2-19 mysql-cluster-news-5-1-47-ndb-6-2-19 2011-07-01
 mysql-cluster-news-5-1-44-ndb-6-3-35 mysql-cluster-news-5-1-47-ndb-6-3-35 2011-07-01
 mysql-cluster-news-5-1-44-ndb-7-0-16 mysql-cluster-news-5-1-47-ndb-7-0-16 2011-07-01
 mysql-cluster-news-5-1-44-ndb-7-1-5 mysql-cluster-news-5-1-47-ndb-7-1-5 2011-07-01
-mysql-cluster-news-5-1-41-ndb-6-2-19 mysql-cluster-news-5-1-47-ndb-6-2-19 2011-03-15
-mysql-cluster-news-5-1-41-ndb-6-3-33 mysql-cluster-news-5-1-44-ndb-6-3-33 2011-03-15
-mysql-cluster-news-5-1-41-ndb-7-0-14 mysql-cluster-news-5-1-44-ndb-7-0-14 2011-03-15
-mysql-cluster-news-5-1-41-ndb-7-1-3 mysql-cluster-news-5-1-44-ndb-7-1-3 2011-03-15
 mysql-cluster-news-6-4 mysql-cluster-news-7-0 2010-03-15
 mysql-cluster-news-combined mysql-cluster-news-series 2010-09-27
 mysql-cluster-news-combined-6-1 mysql-cluster-news-6-1-series 2010-09-27


Thread
svn commit - mysqldoc@docsrva: r22165 - trunk/refman-5.1mc.brown10 Aug