List:Commits« Previous MessageNext Message »
From:mcbrown Date:July 27 2007 4:08pm
Subject:svn commit - mysqldoc@docsrva: r7253 - trunk/falcon
View as plain text  
Author: mcbrown
Date: 2007-07-27 18:08:20 +0200 (Fri, 27 Jul 2007)
New Revision: 7253

Log:
Updating the installation instructions for a source build, binary build
Updating depends



Modified:
   trunk/falcon/Makefile.depends
   trunk/falcon/falcon-installation.xml


Modified: trunk/falcon/Makefile.depends
===================================================================
--- trunk/falcon/Makefile.depends	2007-07-27 15:39:50 UTC (rev 7252)
+++ trunk/falcon/Makefile.depends	2007-07-27 16:08:20 UTC (rev 7253)
Changed blocks: 2, Lines Added: 6, Lines Deleted: 1; 1318 bytes

@@ -6,7 +6,10 @@
 falcon_installation_IMAGES =
 falcon_installation_SOURCES = falcon-installation.xml $(falcon_installation_INCLUDES)
 falcon_installation_IDMAPS = \
+	../refman-5.1/metadata/dba-core.idmap \
 	../refman-5.1/metadata/installing.idmap \
+	../refman-5.1/metadata/se-innodb.idmap \
+	../refman-5.1/metadata/using-mysql-programs.idmap \
 	metadata/se-falcon.idmap
 falcon-installation.validpure: $(falcon_installation_SOURCES)
 falcon-installation.titles: $(falcon_installation_SOURCES)

@@ -72,11 +75,13 @@
 falcon_SOURCES = falcon.xml $(falcon_INCLUDES)
 falcon_IDMAPS = \
 	../query-browser/metadata/query-browser.idmap \
+	../refman-5.1/metadata/dba-core.idmap \
 	../refman-5.1/metadata/installing.idmap \
 	../refman-5.1/metadata/manual.idmap \
 	../refman-5.1/metadata/se-innodb.idmap \
 	../refman-5.1/metadata/se-myisam.idmap \
-	../refman-5.1/metadata/storage-engines.idmap
+	../refman-5.1/metadata/storage-engines.idmap \
+	../refman-5.1/metadata/using-mysql-programs.idmap
 falcon.validpure: $(falcon_SOURCES)
 falcon.titles: $(falcon_SOURCES)
 falcon.useless: $(falcon_SOURCES)


Modified: trunk/falcon/falcon-installation.xml
===================================================================
--- trunk/falcon/falcon-installation.xml	2007-07-27 15:39:50 UTC (rev 7252)
+++ trunk/falcon/falcon-installation.xml	2007-07-27 16:08:20 UTC (rev 7253)
Changed blocks: 3, Lines Added: 577, Lines Deleted: 192; 29391 bytes

@@ -5,267 +5,661 @@
   <!ENTITY % all.entities SYSTEM "all-entities.ent">
   %all.entities;
 ]>
-<chapter id="building-falcon">
+<chapter id="installing-falcon">
 
-  <title>Getting and Building Falcon</title>
+  <title>Installing Falcon</title>
 
   <para>
-    Falcon has been made available as a special MySQL tree called
-    <literal>mysql-6.0-falcon</literal>. In order to try out Falcon you
-    must download the source code and build the special version of the
-    MySQL tree.
+    Falcon is available for installation in binary format (for direct
+    installation), source format (for custom builds) and direct from the
+    development source tree (for custom builds of pre-release features).
   </para>
 
-  <para>
-    To build the Falcon release you will need:
-  </para>
-
   <itemizedlist>
 
     <listitem>
       <para>
-        GNU <command>make</command>
+        For instructions on installing MySQL Falcon Preview from a
+        binary installation, see
+        <xref linkend="installing-falcon-binary"/>.
       </para>
     </listitem>
 
     <listitem>
       <para>
-        GNU <command>autoconf</command> 2.58 (or newer)
+        For instructions on building MySQL Falcon Preview from a source
+        distribution, see <xref linkend="installing-falcon-source"/>.
       </para>
     </listitem>
 
     <listitem>
       <para>
-        GNU <command>automake</command> 1.8.1 (or newer)
+        For instructions on building MySQL Falcon Preview from the
+        developement source tree, see <xref linkend="building-falcon"/>.
       </para>
     </listitem>
 
-    <listitem>
-      <para>
-        GNU <command>libtool</command> 1.5
-      </para>
-    </listitem>
-
   </itemizedlist>
 
   <para>
-    You can obtain the sources for Falcon from
+    For more information on Falcon features and functionality, see
+    <xref
+      linkend="se-falcon"/>. You may want to exchange
+    information on your experiences with other users on the
     <ulink
-        url="http://mysql.bkbits.com">http://mysql.bkbits.com</ulink>.
-    In order to download the sources, you must use a BitKeeper client.
-    You may use either the free client or the commercial client to
-    download the sources.
+      url="http://forums.mysql.com/list.php?133">Falcon
+    Forum</ulink>. If you think you have found a bug, use
+    <ulink url="http://bugs.mysql.com">MySQL Bugs</ulink>.
   </para>
 
-  <para>
-    To obtain a source tree, first download and install the BitKeeper
-    free client if you do not have it. The client can be obtained from
-    <ulink url="http://www.bitmover.com/bk-client2.0.shar"/>. Your
-    system will need to have <literal>gcc</literal>,
-    <literal>make</literal>, <literal>patch</literal> and
-    <literal>tar</literal> installed. <emphasis role="deprecated">Note
-    that old 1.1 versions of the BitKeeper free client will not
-    work!</emphasis>
-  </para>
+  <section id="installing-falcon-binary">
 
-  <para>
-    To install the BitKeeper client on Unix, use these commands:
-  </para>
+    <title>Installing Falcon from a Binary Distribution</title>
 
+    <para>
+      You can install the Falcon preview using a binarty distribution on
+      Linux and Windows using the same instructions as for the standard
+      MySQL installation.
+    </para>
+
+    <para>
+      To install the Falcon Preview on Linux using a binary distribution
+      pacakged as a <literal>tar.gz</literal>, see
+      <xref
+  linkend="installing-binary"/>. To install using an RPM
+      installation, see <xref linkend="linux-rpm"/>.
+    </para>
+
+    <para>
+      To install the Falcon Preview on Windows using a binary
+      distribution, see <xref linkend="windows-installation"/>.
+    </para>
+
+  </section>
+
+  <section id="installing-falcon-source">
+
+    <title>Installing Falcon from a Source Distribution</title>
+
+    <para>
+      The basic commands that you must execute to install a MySQL source
+      distribution are:
+    </para>
+
 <programlisting>
+shell&gt; <userinput>groupadd mysql</userinput>
+shell&gt; <userinput>useradd -g mysql mysql</userinput>
+shell&gt; <userinput>gunzip &lt; mysql-<replaceable>VERSION</replaceable>.tar.gz | tar -xvf -</userinput>
+shell&gt; <userinput>cd mysql-<replaceable>VERSION</replaceable></userinput>
+shell&gt; <userinput>./configure --prefix=/usr/local/mysql</userinput>
+shell&gt; <userinput>make</userinput>
+shell&gt; <userinput>make install</userinput>
+shell&gt; <userinput>cp support-files/my-medium.cnf /etc/my.cnf</userinput>
+shell&gt; <userinput>cd /usr/local/mysql</userinput>
+shell&gt; <userinput>chown -R mysql .</userinput>
+shell&gt; <userinput>chgrp -R mysql .</userinput>
+shell&gt; <userinput>bin/mysql_install_db --user=mysql</userinput>
+shell&gt; <userinput>chown -R root .</userinput>
+shell&gt; <userinput>chown -R mysql var</userinput>
+shell&gt; <userinput>bin/mysqld_safe --user=mysql &amp;</userinput>
+</programlisting>
+
+    <para>
+      <emphasis role="bold">Note</emphasis>: This procedure does not set
+      up any passwords for MySQL accounts. After following the
+      procedure, proceed to <xref linkend="post-installation"/>, for
+      post-installation setup and testing.
+    </para>
+
+    <para>
+      A more detailed version of the preceding description for
+      installing MySQL from a source distribution follows:
+    </para>
+
+    <orderedlist>
+
+      <listitem>
+        <para>
+          Add a login user and group for <command>mysqld</command> to
+          run as:
+        </para>
+
+<programlisting>
+shell&gt; <userinput>groupadd mysql</userinput>
+shell&gt; <userinput>useradd -g mysql mysql</userinput>
+</programlisting>
+
+        <para>
+          These commands add the <literal>mysql</literal> group and the
+          <literal>mysql</literal> user. The syntax for
+          <command>useradd</command> and <command>groupadd</command> may
+          differ slightly on different versions of Unix, or they may
+          have different names such as <command>adduser</command> and
+          <command>addgroup</command>.
+        </para>
+
+        <para>
+          You might want to call the user and group something else
+          instead of <literal>mysql</literal>. If so, substitute the
+          appropriate name in the following steps.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Perform the following steps as the <literal>mysql</literal>
+          user, except as noted.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Unpack the distribution into the current directory:
+        </para>
+
+<programlisting>
+shell&gt; <userinput>gunzip &lt;
+<replaceable>/path/to/mysql-VERSION</replaceable>.tar.gz | tar xvf -</userinput>
+</programlisting>
+
+        <para>
+          This command creates a directory named
+          <filename>mysql-<replaceable>VERSION</replaceable></filename>.
+        </para>
+
+        <para>
+          With GNU <command>tar</command>, no separate invocation of
+          <literal>gunzip</literal> is necessary. You can use the
+          following alternative command to uncompress and extract the
+          distribution:
+        </para>
+
+<programlisting>
+shell&gt; <userinput>tar zxvf <replaceable>/path/to/mysql-VERSION-OS</replaceable>.tar.gz</userinput>
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          Change location into the top-level directory of the unpacked
+          distribution:
+        </para>
+
+<programlisting>
+shell&gt; <userinput>cd mysql-<replaceable>VERSION</replaceable></userinput>
+</programlisting>
+
+        <remark role="todo">
+          [pd] It's no longer true that you must be in the top-level
+          directory, but we need information from the build team if
+          we're to describe alternative procedures.
+        </remark>
+
+        <para>
+          Note that currently you must configure and build MySQL from
+          this top-level directory. You cannot build it in a different
+          directory.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Configure the release and compile everything:
+        </para>
+
+<programlisting>
+shell&gt; <userinput>./configure --prefix=/usr/local/mysql</userinput>
+shell&gt; <userinput>make</userinput>
+</programlisting>
+
+        <para>
+          When you run <command>configure</command>, you might want to
+          specify other options. Run <command>./configure
+          --help</command> for a list of options.
+          <xref linkend="configure-options"/>, discusses some of the
+          more useful options.
+        </para>
+
+        <para>
+          If the compile fails, see
+          <xref linkend="compilation-problems"/>, for help.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Install the distribution:
+        </para>
+
+<programlisting>
+shell&gt; <userinput>make install</userinput>
+</programlisting>
+
+        <para>
+          You might need to run this command as <literal>root</literal>.
+        </para>
+
+        <para>
+          If you want to set up an option file, use one of those present
+          in the <filename>support-files</filename> directory as a
+          template. For example:
+        </para>
+
+<programlisting>
+shell&gt; <userinput>cp support-files/my-medium.cnf /etc/my.cnf</userinput>
+</programlisting>
+
+        <para>
+          You might need to run this command as <literal>root</literal>.
+        </para>
+
+        <para>
+          If you want to configure support for <literal>InnoDB</literal>
+          tables, you should edit the <literal>/etc/my.cnf</literal>
+          file, remove the <literal>#</literal> character before the
+          option lines that start with <literal>innodb_...</literal>,
+          and modify the option values to be what you want. See
+          <xref linkend="option-files"/>, and
+          <xref linkend="innodb-configuration"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Change location into the installation directory:
+        </para>
+
+<programlisting>
+shell&gt; <userinput>cd /usr/local/mysql</userinput>
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you ran the <command>make install</command> command as
+          <literal>root</literal>, the installed files will be owned by
+          <literal>root</literal>. Ensure that the installation is
+          accessible to <literal>mysql</literal> by executing the
+          following commands as <literal>root</literal> in the
+          installation directory:
+        </para>
+
+<programlisting>
+shell&gt; <userinput>chown -R mysql .</userinput>
+shell&gt; <userinput>chgrp -R mysql .</userinput>
+</programlisting>
+
+        <para>
+          The first command changes the owner attribute of the files to
+          the <literal>mysql</literal> user. The second changes the
+          group attribute to the <literal>mysql</literal> group.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have not installed MySQL before, you must create the
+          MySQL data directory and initialize the grant tables:
+        </para>
+
+<programlisting>
+shell&gt; <userinput>bin/mysql_install_db --user=mysql</userinput>
+</programlisting>
+
+        <para>
+          If you run the command as <literal>root</literal>, include the
+          <option>--user</option> option as shown. If you run the
+          command while logged in as <literal>mysql</literal>, you can
+          omit the <option>--user</option> option.
+        </para>
+
+        <para>
+          The command should create the data directory and its contents
+          with <literal>mysql</literal> as the owner.
+        </para>
+
+        <para>
+          After using <command>mysql_install_db</command> to create the
+          grant tables for MySQL, you must restart the server manually.
+          The <command>mysqld_safe</command> command to do this is shown
+          in a later step.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Most of the MySQL installation can be owned by
+          <literal>root</literal> if you like. The exception is that the
+          data directory must be owned by <literal>mysql</literal>. To
+          accomplish this, run the following commands as
+          <literal>root</literal> in the installation directory:
+        </para>
+
+<programlisting>
+shell&gt; <userinput>chown -R root .</userinput>
+shell&gt; <userinput>chown -R mysql var</userinput>
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you want MySQL to start automatically when you boot your
+          machine, you can copy
+          <filename>support-files/mysql.server</filename> to the
+          location where your system has its startup files. More
+          information can be found in the
+          <filename>support-files/mysql.server</filename> script itself;
+          see also <xref linkend="automatic-start"/>.
+        </para>
+      </listitem>
+
+    </orderedlist>
+
+    <para>
+      After everything has been installed, you should test your
+      distribution. To start the MySQL server, use the following
+      command:
+    </para>
+
+<programlisting>
+shell&gt; <userinput>/usr/local/mysql/bin/mysqld_safe --user=mysql &amp;</userinput>
+</programlisting>
+
+    <para>
+      If you run the command as <literal>root</literal>, you should use
+      the <option>--user</option> option as shown. The value of the
+      option is the name of the login account that you created in the
+      first step to use for running the server. If you run the command
+      while logged in as that user, you can omit the
+      <option>--user</option> option.
+    </para>
+
+    <para>
+      If the command fails immediately and prints <literal>mysqld
+      ended</literal>, you can find some information in the
+      <filename><replaceable>host_name</replaceable>.err</filename> file
+      in the data directory.
+    </para>
+
+    <para>
+      More information about <command>mysqld_safe</command> is given in
+      <xref linkend="mysqld-safe"/>.
+    </para>
+
+    <para>
+      <emphasis role="bold">Note</emphasis>: The accounts that are
+      listed in the MySQL grant tables initially have no passwords.
+      After starting the server, you should set up passwords for them
+      using the instructions in <xref linkend="post-installation"/>.
+    </para>
+
+  </section>
+
+  <section id="building-falcon">
+
+    <title>Getting and Building Falcon from the Development Source Tree</title>
+
+    <para>
+      Falcon has been made available as a special MySQL tree called
+      <literal>mysql-6.0-falcon</literal>. In order to try out Falcon
+      you must download the source code and build the special version of
+      the MySQL tree.
+    </para>
+
+    <para>
+      To build the Falcon release you will need:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          GNU <command>make</command>
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          GNU <command>autoconf</command> 2.58 (or newer)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          GNU <command>automake</command> 1.8.1 (or newer)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          GNU <command>libtool</command> 1.5
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+    <para>
+      You can obtain the sources for Falcon from
+      <ulink
+        url="http://mysql.bkbits.com">http://mysql.bkbits.com</ulink>.
+      In order to download the sources, you must use a BitKeeper client.
+      You may use either the free client or the commercial client to
+      download the sources.
+    </para>
+
+    <para>
+      To obtain a source tree, first download and install the BitKeeper
+      free client if you do not have it. The client can be obtained from
+      <ulink url="http://www.bitmover.com/bk-client2.0.shar"/>. Your
+      system will need to have <literal>gcc</literal>,
+      <literal>make</literal>, <literal>patch</literal> and
+      <literal>tar</literal> installed. <emphasis role="deprecated">Note
+      that old 1.1 versions of the BitKeeper free client will not
+      work!</emphasis>
+    </para>
+
+    <para>
+      To install the BitKeeper client on Unix, use these commands:
+    </para>
+
+<programlisting>
 shell&gt; <userinput>/bin/sh bk-client2.0.shar</userinput>
 shell&gt; <userinput>cd bk-client2.0</userinput>
 shell&gt; <userinput>make</userinput>
 </programlisting>
 
-  <para>
-    If you get a <literal>cc: command not found</literal> error, invoke
-    this command when running <literal>make</literal>:
-  </para>
+    <para>
+      If you get a <literal>cc: command not found</literal> error,
+      invoke this command when running <literal>make</literal>:
+    </para>
 
 <programlisting>
 shell&gt; <userinput>make CC=gcc</userinput>
 </programlisting>
 
-  <para>
-    This will create the tool <command>bkf</command>, the free BitKeeper
-    client. For more information on the free BitKeeper client use:
-  </para>
+    <para>
+      This will create the tool <command>bkf</command>, the free
+      BitKeeper client. For more information on the free BitKeeper
+      client use:
+    </para>
 
 <programlisting>shell&gt; bkf --help</programlisting>
 
-  <para>
-    To install the BitKeeper client on Windows, use these instructions:
-  </para>
+    <para>
+      To install the BitKeeper client on Windows, use these
+      instructions:
+    </para>
 
-  <orderedlist>
+    <orderedlist>
 
-    <listitem>
-      <para>
-        Download and install Cygwin from
-        <ulink url="http://cygwin.com/">http://cygwin.com</ulink>.
-      </para>
-    </listitem>
+      <listitem>
+        <para>
+          Download and install Cygwin from
+          <ulink url="http://cygwin.com/">http://cygwin.com</ulink>.
+        </para>
+      </listitem>
 
-    <listitem>
-      <para>
-        Make sure <command>gcc</command> and <command>make</command>
-        have been installed under Cygwin. You can test this by issuing
-        <command>which gcc</command> and <command>which make</command>
-        commands. If either one is not installed, run Cygwin's package
-        manager, select <command>gcc</command>, <command>make</command>,
-        or both, and install them.
-      </para>
-    </listitem>
+      <listitem>
+        <para>
+          Make sure <command>gcc</command> and <command>make</command>
+          have been installed under Cygwin. You can test this by issuing
+          <command>which gcc</command> and <command>which make</command>
+          commands. If either one is not installed, run Cygwin's package
+          manager, select <command>gcc</command>,
+          <command>make</command>, or both, and install them.
+        </para>
+      </listitem>
 
-    <listitem>
+      <listitem>
+        <para>
+          For the installation of the BitKeeper free client, use the
+          same installations as given for Unix-like systems above.
+        </para>
+      </listitem>
+
+    </orderedlist>
+
+    <note>
       <para>
-        For the installation of the BitKeeper free client, use the same
-        installations as given for Unix-like systems above.
+        For more information using the public BitKeeper sources for
+        MySQL, and the free BitKeeper client, see
+        <xref linkend="installing-source-tree"/>.
       </para>
-    </listitem>
+    </note>
 
-  </orderedlist>
-
-  <note>
     <para>
-      For more information using the public BitKeeper sources for MySQL,
-      and the free BitKeeper client, see
-      <xref linkend="installing-source-tree"/>.
+      After you have installed the BitKeeper client, you can access the
+      MySQL development source tree:
     </para>
-  </note>
 
-  <para>
-    After you have installed the BitKeeper client, you can access the
-    MySQL development source tree:
-  </para>
+    <orderedlist>
 
-  <orderedlist>
+      <listitem>
+        <para>
+          Change location to the directory you want to work from, and
+          then use the following command to make a local copy of the
+          <literal>mysql-6.0-falcon</literal> tree:
+        </para>
 
-    <listitem>
-      <para>
-        Change location to the directory you want to work from, and then
-        use the following command to make a local copy of the
-        <literal>mysql-6.0-falcon</literal> tree:
-      </para>
-
 <programlisting>
 shell&gt; <userinput>bkf clone bk://mysql.bkbits.net/mysql-6.0-falcon mysql-6.0-falcon</userinput>
 </programlisting>
 
-      <para>
-        In the preceding example, the source tree is set up in the
-        <filename>mysql-6.0-falcon/</filename> subdirectory of your
-        current directory.
-      </para>
+        <para>
+          In the preceding example, the source tree is set up in the
+          <filename>mysql-6.0-falcon/</filename> subdirectory of your
+          current directory.
+        </para>
 
-      <para>
-        The initial download of the source tree may take a while,
-        depending on the speed of your connection. Please be patient.
-      </para>
-    </listitem>
+        <para>
+          The initial download of the source tree may take a while,
+          depending on the speed of your connection. Please be patient.
+        </para>
+      </listitem>
 
-  </orderedlist>
+    </orderedlist>
 
-  <para>
-    Once you have downloaded the Falcon tree:
-  </para>
+    <para>
+      Once you have downloaded the Falcon tree:
+    </para>
 
-  <orderedlist>
+    <orderedlist>
 
-    <listitem>
-      <para>
-        Change into the directory containing the Falcon tree:
-      </para>
+      <listitem>
+        <para>
+          Change into the directory containing the Falcon tree:
+        </para>
 
 <programlisting>shell&gt; cd mysql-6.0-falcon</programlisting>
-    </listitem>
+      </listitem>
 
-    <listitem>
-      <para>
-        Run the appropropriate build script to start the build process.
-        For Pentium CPUs, use
-        <command>compile-pentium-debug-falcon</command>, for AMD 64
-        CPUs, use <command>compile-amd64-debug-falcon</command>. The
-        build scripts are located in the <filename>BUILD</filename>, but
-        they should be executed from the root directory of the tree:
-      </para>
+      <listitem>
+        <para>
+          Run the appropropriate build script to start the build
+          process. For Pentium CPUs, use
+          <command>compile-pentium-debug-falcon</command>, for AMD 64
+          CPUs, use <command>compile-amd64-debug-falcon</command>. The
+          build scripts are located in the <filename>BUILD</filename>,
+          but they should be executed from the root directory of the
+          tree:
+        </para>
 
 <programlisting>shell&gt; ./BUILD/compile-pentium-debug-falcon</programlisting>
-    </listitem>
+      </listitem>
 
-    <listitem>
-      <para>
-        The build script will create the necessary stubs for the
-        configure process, run <command>configure</command>, and then
-        execute the <command>make</command> to start the compilation
-        process.
-      </para>
-    </listitem>
+      <listitem>
+        <para>
+          The build script will create the necessary stubs for the
+          configure process, run <command>configure</command>, and then
+          execute the <command>make</command> to start the compilation
+          process.
+        </para>
+      </listitem>
 
-    <listitem>
-      <para>
-        Rather than installing directly from this build, you may want to
-        create a binary package that can be distributed and relocated to
-        the right location. To create such a distribution, use the
-        <command>make_binary_distribution</command> script:
-      </para>
+      <listitem>
+        <para>
+          Rather than installing directly from this build, you may want
+          to create a binary package that can be distributed and
+          relocated to the right location. To create such a
+          distribution, use the
+          <command>make_binary_distribution</command> script:
+        </para>
 
 <programlisting>shell&gt; ./scripts/make_binary_distribution</programlisting>
 
-      <para>
-        The above command will create an archive with all the files you
-        need configured to behave as if they were in a directory named
-        according to the version and tag for this release. For example,
-        on a Linux Pentium machine, the Falcon release will create an
-        archive with the name
-        <filename>mysql-6.0.0-falcon-alpha-linux-i686.tar</filename>,
-        which contains the directory
-        <filename>mysql-6.0.0-falcon-alpha-linux-i686</filename>.
-      </para>
+        <para>
+          The above command will create an archive with all the files
+          you need configured to behave as if they were in a directory
+          named according to the version and tag for this release. For
+          example, on a Linux Pentium machine, the Falcon release will
+          create an archive with the name
+          <filename>mysql-6.0.0-falcon-alpha-linux-i686.tar</filename>,
+          which contains the directory
+          <filename>mysql-6.0.0-falcon-alpha-linux-i686</filename>.
+        </para>
 
-      <para>
-        To install the files to a new location, extract them specifying
-        the new base directory:
-      </para>
+        <para>
+          To install the files to a new location, extract them
+          specifying the new base directory:
+        </para>
 
 <programlisting>shell&gt; tar zxf mysql-6.0.0-falcon-alpha-linux-i686 -C /usr/local</programlisting>
 
-      <para>
-        You can either use directory or link to an alternative location.
-        For example, you may want to create a link to
-        <filename>/usr/local/mysql-falcon</filename>:
-      </para>
+        <para>
+          You can either use directory or link to an alternative
+          location. For example, you may want to create a link to
+          <filename>/usr/local/mysql-falcon</filename>:
+        </para>
 
 <programlisting>shell&gt; cd /usr/local
 shell&gt; ln -s mysql-6.0.0-falcon-alpha-linux-i686 mysql-falcon</programlisting>
-    </listitem>
+      </listitem>
 
-    <listitem>
-      <para>
-        You must configure the new installation, including creating the
-        base databases. Running <command>configure</command> in this
-        directory will perform this function for you, and start an
-        instance of <literal>mysqld</literal>:
-      </para>
+      <listitem>
+        <para>
+          You must configure the new installation, including creating
+          the base databases. Running <command>configure</command> in
+          this directory will perform this function for you, and start
+          an instance of <literal>mysqld</literal>:
+        </para>
 
 <programlisting>shell&gt; cd mysql-falcon
 shell&gt; ./configure</programlisting>
 
-      <para>
-        If <literal>mysqld</literal> fails to start, ensure that the
-        files in your chosen directory are owned by the
-        <literal>mysql</literal> user:
-      </para>
+        <para>
+          If <literal>mysqld</literal> fails to start, ensure that the
+          files in your chosen directory are owned by the
+          <literal>mysql</literal> user:
+        </para>
 
 <programlisting>shell&gt; chown -R mysql:mysql *</programlisting>
-    </listitem>
+      </listitem>
 
-    <listitem>
-      <para>
-        Confirm that <command>mysqld</command> is running by obtaining
-        the version from the server:
-      </para>
+      <listitem>
+        <para>
+          Confirm that <command>mysqld</command> is running by obtaining
+          the version from the server:
+        </para>
 
 <programlisting>shell&gt; ./bin/mysqladmin version
 ./bin/mysqladmin  Ver 8.42 Distrib 6.0.0-falcon-alpha, for pc-linux-gnu on i686

@@ -282,21 +676,21 @@
 Threads: 1  Questions: 1  Slow queries: 0  Opens: 14  Flush tables: 1 &raquo;
             Open tables: 7  Queries per second avg: </programlisting>
 
-      <para>
-        You may need to update your <literal>LD_LIBRARY_PATH</literal>
-        with the MySQL libraries:
-      </para>
+        <para>
+          You may need to update your <literal>LD_LIBRARY_PATH</literal>
+          with the MySQL libraries:
+        </para>
 
 <programlisting>shell&gt; export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/mysql-falcon/lib</programlisting>
-    </listitem>
+      </listitem>
 
-  </orderedlist>
+    </orderedlist>
 
-  <para>
-    Once Falcon has been installed, you can try creating tables using
-    the Falcon engine. For example, to create a simple table with
-    Falcon:
-  </para>
+    <para>
+      Once Falcon has been installed, you can try creating tables using
+      the Falcon engine. For example, to create a simple table with
+      Falcon:
+    </para>
 
 <programlisting>shell&gt; ./bin/mysql
 Welcome to the MySQL monitor.  Commands end with ; or \g.

@@ -310,15 +704,6 @@
 mysql&gt; CREATE TABLE falcon_basic (id int, fname varchar(20)) ENGINE=Falcon;
 Query OK, 0 rows affected (1.07 sec)</programlisting>
 
-  <para>
-    For more information on Falcon features and functionality, see
-    <xref
-    linkend="se-falcon"/>. You may want to exchange
-    information on your experiences with other users on the
-    <ulink
-      url="http://forums.mysql.com/list.php?133">Falcon
-    Forum</ulink>. If you think you have found a bug, use
-    <ulink url="http://bugs.mysql.com">MySQL Bugs</ulink>.
-  </para>
+  </section>
 
 </chapter>


Thread
svn commit - mysqldoc@docsrva: r7253 - trunk/falconmcbrown27 Jul