LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

Better tagging throughout, use a more refined install method for Ubuntu.

This commit is contained in:
dbs 2005-11-12 02:24:01 +00:00
parent cc3c546fdb
commit e370a93989
1 changed files with 104 additions and 55 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

159
LDP/howto/docbook/DB2-HOWTO.xml
View File

@ -1344,7 +1344,7 @@ $JAVA_PATH/$JAVA_INTERPRETER $JAVA_OPTIONS \
The solution here is to run The solution here is to run
<screen>export LD_ASSUME_KERNEL="2.4.19"</screen> <screen>export LD_ASSUME_KERNEL="2.4.19"</screen>
from the from the
terminal where you launched the db2setup utility, then run db2setup terminal where you launched the <command>db2setup</command> utility, then run <command>db2setup</command>
again. This change will only affect the Java installer, not the again. This change will only affect the Java installer, not the
kernel performance.</para></sect2> kernel performance.</para></sect2>
<sect2><title>Post-installation notes</title> <sect2><title>Post-installation notes</title>
@ -1393,9 +1393,10 @@ directory tree than the JDK from IBM that DB2 UDB installs.
Therefore, there are 3 options you can choose to deal with this issue: Therefore, there are 3 options you can choose to deal with this issue:
<orderedlist> <orderedlist>
<listitem><para>Uninstall the Java2-1.3.1 package before installing, <listitem><para>Uninstall the Java2-1.3.1 package before installing,
using either the YaST tool, or with the command line rpm -e using either the YaST tool, or with the command line:
IBMJava2-SDK-1.3.1 command. After installation, this will leave the <screen>rpm -e IBMJava2-SDK-1.3.1</screen>
IBMJava2&ndash;SDK&ndash;1.4.1 package as the only Java installation After installation, this will leave the
IBMJava2-SDK-1.4.1 package as the only Java installation
on the system.</para></listitem> on the system.</para></listitem>
<listitem><para>Leave both Java packages installed. By default, DB2 UDB <listitem><para>Leave both Java packages installed. By default, DB2 UDB
will use the 1.4.1 JRE that it installs. The fact that SuSE Linux's Java will use the 1.4.1 JRE that it installs. The fact that SuSE Linux's Java
@ -1429,7 +1430,7 @@ to install the pdksh package found on CD
4.</para></sect2> 4.</para></sect2>
<sect2><title>Installation notes</title> <sect2><title>Installation notes</title>
<para>SuSE Linux Professional installs its own 1.4.2 Java JRE by default <para>SuSE Linux Professional installs its own 1.4.2 Java JRE by default
(the "java2&ndash;jre-1.4.2" package). During the DB2 UDB installation, (the "java2-jre-1.4.2" package). During the DB2 UDB installation,
this will cause a warning to be generated: this will cause a warning to be generated:
<screen>Command to be run: "/bin/rpm -ivh \ <screen>Command to be run: "/bin/rpm -ivh \
'/mnt/cdrom/db2/linux/Java-1.4/IBMJava2-SDK-1.4.1-2.0'.i386.rpm" '/mnt/cdrom/db2/linux/Java-1.4/IBMJava2-SDK-1.4.1-2.0'.i386.rpm"
@ -1439,9 +1440,9 @@ supplied by SuSE Linux, it will have been installed into a different
directory tree than the JDK from IBM that DB2 UDB installs. directory tree than the JDK from IBM that DB2 UDB installs.
Therefore, there are 3 options you can choose to deal with this issue: Therefore, there are 3 options you can choose to deal with this issue:
<orderedlist> <orderedlist>
<listitem><para>Uninstall the java2&ndash;jre&ndash;1.4.2 package <listitem><para>Uninstall the java2-jre-1.4.2 package
before installing, using either the YaST tool, or with command line rpm before installing, using either the YaST tool, or with command line <command>rpm
erase command. This will leave the IBMJava2&ndash;SDK package as the erase</command> command. This will leave the IBMJava2-SDK package as the
only Java installation on the system.</para></listitem> only Java installation on the system.</para></listitem>
<listitem><para>Leave both Java packages installed. By default, DB2 UDB <listitem><para>Leave both Java packages installed. By default, DB2 UDB
will use the 1.4.1 JRE that it installs. The fact that SuSE Linux's Java will use the 1.4.1 JRE that it installs. The fact that SuSE Linux's Java
@ -1472,17 +1473,21 @@ environment.</para>
<sect2><title>Pre-installation notes</title> <sect2><title>Pre-installation notes</title>
<para>The pdksh package is not installed by default. If you want to <para>The pdksh package is not installed by default. If you want to
install a multiple-partition environment on SuSE Linux Personal, you install a multiple-partition environment on SuSE Linux Personal, you
will have to install.</para> will have to install pdksh.</para>
<para>The installer may complain about being unable to use the SMTP <para>The installer may complain about being unable to use the SMTP
server even though postfix is installed and sendmail is available in the server even though <command>postfix</command> is installed and <command>sendmail</command> is available in the
path. Make sure that postfix has been started before path. Make sure that <command>postfix</command> has been started before
installation.</para></sect2> installation.</para></sect2>
<sect2><title>Installation notes</title> <sect2><title>Installation notes</title>
<para>The usual trick of adding an xhost entry for localhost and then <para>The usual trick of adding an xhost entry for localhost and then
exporting the DISPLAY=localhost:0 when installing (so that the graphical exporting the DISPLAY=localhost:0 when installing (so that the graphical
utilities are displayed on a non-root user's desktop) didn't seem to utilities are displayed on a non-root user's desktop) didn't seem to
work here. Instead, try executing ssh -X root@localhost and launch the work here. Instead, execute the following command to log in as root
utilities from there.</para></sect2></sect1> and forward the X server:
<screen>ssh -X root@localhost</screen>
</para>
</sect2>
</sect1>
<sect1 id='fedora2'><title>Installing DB2 Version 8.2 on Fedora Core 2</title> <sect1 id='fedora2'><title>Installing DB2 Version 8.2 on Fedora Core 2</title>
<para> <para>
Before proceeding, please ensure that you have read Before proceeding, please ensure that you have read
@ -1527,9 +1532,9 @@ Could not create the Java virtual machine.
The workaround for this error is to The workaround for this error is to
install Sun's Java 2 Platform Standard Edition 5.0 RC (Fedora Core install Sun's Java 2 Platform Standard Edition 5.0 RC (Fedora Core
2 doesn't install a Java package by default). The rpm file is available 2 doesn't install a Java package by default). The rpm file is available
from http://java.sun.com/j2se/1.5.0/download.jsp. After installing Java, from <ulink url="http://java.sun.com/j2se/1.5.0/download.jsp">http://java.sun.com/j2se/1.5.0/download.jsp</ulink>. After installing Java,
set the environment variables in the terminal where you execute the set the environment variables in the terminal where you execute the
db2setup utility: <command>db2setup</command> utility:
<screen>export DB2USELOCALJRE=TRUE <screen>export DB2USELOCALJRE=TRUE
export JAVA_HOME=/usr/java/jre1.5.0/ export JAVA_HOME=/usr/java/jre1.5.0/
</screen>/usr/java/jre1.5.0/ is the location </screen>/usr/java/jre1.5.0/ is the location
@ -1541,7 +1546,7 @@ so that db2setup works properly with the directory:
mkdir jre mkdir jre
cd jre cd jre
ln -s ../bin bin</screen></para> ln -s ../bin bin</screen></para>
<para>After making these changes, the db2setup GUI installer works <para>After making these changes, the <command>db2setup</command> GUI installer works
properly.</para> properly.</para>
<para>Alternatively, you can avoid the Java-based problems by installing <para>Alternatively, you can avoid the Java-based problems by installing
on Fedora Core 2 using on Fedora Core 2 using
@ -1571,7 +1576,7 @@ db2 UPDATE ADMIN CFG USING JDK_PATH /usr/java/jre1.5.0/</screen>
With that update, With that update,
the DB2 UDB Java-based tools will work the DB2 UDB Java-based tools will work
properly.</para></sect2></sect1> properly.</para></sect2></sect1>
<sect1 id='mand101'><title>Installing DB2 Version 8.2 on Mandrake Linux 10.1 (Community)</title> <sect1 id='mand101'><title>Installing DB2 Version 8.2 on Mandriva Linux 10.1 (Community)</title>
<para> <para>
Before proceeding, please ensure that you have read Before proceeding, please ensure that you have read
<xref linkend='planning'/> and <xref linkend='installing'/>. <xref linkend='planning'/> and <xref linkend='installing'/>.
@ -1585,8 +1590,8 @@ installing to a single-partition
environment.</para> environment.</para>
<sect2><title>Pre-installation notes</title> <sect2><title>Pre-installation notes</title>
<para>The pdksh package is not installed by default. If you want to <para>The pdksh package is not installed by default. If you want to
install a multiple-partition environment on Mandrake Linux, you will install a multiple-partition environment on Mandriva Linux, you will
have to install it using drakconf (it's on CD3). Also, no Java package have to install it using <command>drakconf</command> (it's on CD3). Also, no Java package
is installed by default, so we don't have to worry about any conflicts is installed by default, so we don't have to worry about any conflicts
arising from that.</para></sect2> arising from that.</para></sect2>
<sect2><title>Installation <sect2><title>Installation
@ -1596,12 +1601,14 @@ problems or issues. If you do experience a hang with the Java installer,
try the Sun Java workaround described in the Fedora Core 2 try the Sun Java workaround described in the Fedora Core 2
section.</para></sect2> section.</para></sect2>
<sect2><title>Post-installation notes</title> <sect2><title>Post-installation notes</title>
<para>Be careful of the Mandrake Linux security "msec" utility &ndash; <para>Be careful of the Mandriva Linux security <command>msec</command> utility &ndash;
it can mess up DB2 UDB functionality by changing world readable it can prevent DB2 from functioning correctly by changing the permissions on
directories (like /home/db2inst1/sqllib/) that are necessary to run DB2 directories like <filename class="directory">/home/db2inst1/sqllib/</filename> that must be
UDB to non-world readable. If you find that DB2 UDB is not working world-readable for DB2 UDB to non-world readable. If you find that DB2 UDB is not working
properly, investigate your properly, investigate your
security settings.</para></sect2></sect1> security settings.</para>
</sect2>
</sect1>
<sect1 id='gentoo'><title>Installing DB2 Version 8.2 on Gentoo (2005-01-17)</title> <sect1 id='gentoo'><title>Installing DB2 Version 8.2 on Gentoo (2005-01-17)</title>
<para> <para>
Before proceeding, please ensure that you have read Before proceeding, please ensure that you have read
@ -1649,7 +1656,7 @@ your home directory, issue the following command:
<screen>cp -r /mnt/cdrom/* ~/cdrom</screen></para> <screen>cp -r /mnt/cdrom/* ~/cdrom</screen></para>
</listitem> </listitem>
<listitem> <listitem>
<para>Open the ~/cdrom/db2/linux/db2_install script in your text editor and modify the following lines</para> <para>Open the <filename>~/cdrom/db2/linux/db2_install</filename> script in your text editor and modify the following lines</para>
<para> <para>
From: From:
<screen>output_df="`df -k ${dirname2?} | tail -1`"</screen> <screen>output_df="`df -k ${dirname2?} | tail -1`"</screen>
@ -1670,7 +1677,7 @@ To:
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para>Change to the ~/cdrom directory and issue the following command as root: <para>Change to the <filename class="directory">~/cdrom</filename> directory and issue the following command as root:
<screen>./db2_install</screen> <screen>./db2_install</screen>
</para> </para>
</listitem> </listitem>
@ -1746,7 +1753,7 @@ useradd -u 1002 -g dasadm1 -m -d /home/dasusr1 dasusr1
<listitem> <listitem>
<para>Before you can create the DB2 Administration Server and database instance, you have <para>Before you can create the DB2 Administration Server and database instance, you have
to modify the db2iutil library to update calls to the <command>tail</command> to modify the db2iutil library to update calls to the <command>tail</command>
command to the current GNU syntax. As root, open the /opt/IBM/db2/V8.1/instance/db2iutil command to the current GNU syntax. As root, open the <filename>/opt/IBM/db2/V8.1/instance/db2iutil</filename>
file in an editor and make the following changes (or apply the changes to the file using file in an editor and make the following changes (or apply the changes to the file using
the patch utility): the patch utility):
<screen> <screen>
@ -1803,12 +1810,10 @@ the patch utility):
</listitem> </listitem>
<listitem> <listitem>
<para>Create the DB2 Administration Server: <para>Create the DB2 Administration Server:
<screen>/opt/IBM/db2/V8.1/instance/dascrt -u dasusr1 <screen>/opt/IBM/db2/V8.1/instance/dascrt -u dasusr1</screen>
</screen>
</para> </para>
<para>Create the DB2 database instance: <para>Create the DB2 database instance:
<screen>/opt/IBM/db2/V8.1/instance/db2icrt -a server -u db2fenc1 db2inst1 <screen>/opt/IBM/db2/V8.1/instance/db2icrt -a server -u db2fenc1 db2inst1</screen>
</screen>
</para> </para>
</listitem> </listitem>
</orderedlist> </orderedlist>
@ -1821,7 +1826,7 @@ DB2 server from remote clients, perform the following steps:
<orderedlist> <orderedlist>
<listitem> <listitem>
<para>Set the port on which DB2 should communicate. Ensure that you select a port that <para>Set the port on which DB2 should communicate. Ensure that you select a port that
is not blocked by a firewall or used by another service defined in the /etc/services file. is not blocked by a firewall or used by another service defined in the <filename>/etc/services</filename> file.
To set the communications port, update the DB2 database manager configuration variable To set the communications port, update the DB2 database manager configuration variable
SVCENAME. For example, to set the communications port to 50055, issue the following command SVCENAME. For example, to set the communications port to 50055, issue the following command
as the instance user ("db2inst1", if you've been using the defaults): as the instance user ("db2inst1", if you've been using the defaults):
@ -1853,7 +1858,7 @@ Running the DB2 Control Center and other DB2 GUI tools
</title> </title>
<para>To run the DB2 Control Center or other DB2 GUI tools, you must install the IBM <para>To run the DB2 Control Center or other DB2 GUI tools, you must install the IBM
Software Developers' Kit for Java. This RPM is included in the DB2 install CD-ROM in Software Developers' Kit for Java. This RPM is included in the DB2 install CD-ROM in
the /db2/linux/Java-1.4/ directory. To install the IBM Software Developers' Kit for the <filename class="directory">/db2/linux/Java-1.4/</filename> directory. To install the IBM Software Developers' Kit for
Java, change to the root directory of the CD-ROM and issue the following command as root: Java, change to the root directory of the CD-ROM and issue the following command as root:
<screen> <screen>
rpm --force --nodeps -ivh db2/linux/Java-1.4/IBMJava2-SDK-1.4.1-2.0.i386.rpm rpm --force --nodeps -ivh db2/linux/Java-1.4/IBMJava2-SDK-1.4.1-2.0.i386.rpm
@ -1869,20 +1874,66 @@ Log in as the db2inst1 and invoke the DB2 Control Center:
<xref linkend='planning'/> and <xref linkend='installing'/>. <xref linkend='planning'/> and <xref linkend='installing'/>.
</para> </para>
<para>These notes are based on a single-partition installation on <para>These notes are based on a single-partition installation on
Ubuntu 5.04. As Ubuntu uses .deb packages, we use the <command>alien</command> Ubuntu 5.04. As Ubuntu uses <filename>.deb</filename> packages, we use the <command>alien</command>
package conversion utility to convert and install the DB2 RPM packages directly. package conversion utility to convert and install the DB2 RPM packages directly.
</para> </para>
<sect2><title>Pre-installation notes</title> <sect2><title>Pre-installation notes</title>
<para>Ensure that you have installed <command>alien</command>: <para>Ensure that you have installed <command>alien</command>:
<screen>sudo apt-get install alien</screen> <screen>sudo apt-get install alien</screen>
If you want to run a multiple-partition environment, you will need to install either the pdksh or ksh package. If you want to run a multiple-partition environment, you will need to install the pdksh package.
</para></sect2> </para></sect2>
<sect2><title>Installation notes</title> <sect2><title>Installation notes</title>
<para> <para>
To install the product into the /opt/IBM/db2/V8.1/ directory, change The RPM packages supplied with the DB2 install CD contain dependency listings that cannot
to the db2/linux/ directory of the CD or the extracted tarball be satisfied inside a Ubuntu environment, because Ubuntu does not use RPM as a native
and issue the following command: packaging method. To overcome these dependencies, you need to modify the <command>db2_install</command>
<screen>sudo alien -dic *.rpm</screen> script to ignore dependencies and force the installation of DB2 onto your system using <command>alien</command>.
</para><para>
Perform the following steps to modify the <command>db2_install</command> script
and install the product:</para>
<orderedlist>
<listitem>
<para>Open the ~/db2/linux/db2_install script in your text editor and modify the following lines</para>
<para>
From:
<screen>( rpm -ivh ${INSTDEV?}/${pkg?}${RPMEXTN?} 2>&amp;1; \
echo $? > ${TMPRC?} ) | tee -a ${DB2INSTLOG?}</screen>
</para>
<para>
To:
<screen>( alien -dic ${INSTDEV?}/${pkg?}${RPMEXTN?} 2>&amp;1; \
echo $? > ${TMPRC?} ) | tee -a ${DB2INSTLOG?}</screen>
</para>
</listitem>
<listitem>
<para>Issue the following command to begin installing DB2:
<screen>sudo ./db2_install</screen>
</para>
</listitem>
<listitem>
<para>The DB2 installer prompts you to enter the keyword of the product you want to install.
for example, issuing the <command>db2_inst</command> command for the DB2 UDB Express
Edition for Linux install displays the following screen:
<screen>
Specify one or more of the following keywords,
separated by spaces, to install DB2 products.
Keyword Product Description
DB2.EXP DB2 UDB Express Edition for LINUX
Enter "help" to redisplay product names.
Enter "quit" to exit.
***********************************************************
DB2.EXP
</screen>
</para>
</listitem>
</orderedlist>
<para>
The DB2 installer will now install many RPM packages into the
<filename class="directory">/opt/IBM/db2/V8.1/</filename> directory.
</para> </para>
</sect2> </sect2>
<sect2><title>Post-installation notes</title> <sect2><title>Post-installation notes</title>
@ -1911,12 +1962,10 @@ sudo useradd -u 1002 -g dasadm1 -m -d /home/dasusr1 dasusr1
</listitem> </listitem>
<listitem> <listitem>
<para>Create the DB2 Administration Server: <para>Create the DB2 Administration Server:
<screen>sudo /opt/IBM/db2/V8.1/instance/dascrt -u dasusr1 <screen>sudo /opt/IBM/db2/V8.1/instance/dascrt -u dasusr1</screen>
</screen>
</para> </para>
<para>Create the DB2 database instance: <para>Create the DB2 database instance:
<screen>sudo /opt/IBM/db2/V8.1/instance/db2icrt -a server -u db2fenc1 db2inst1 <screen>sudo /opt/IBM/db2/V8.1/instance/db2icrt -a server -u db2fenc1 db2inst1</screen>
</screen>
</para> </para>
</listitem> </listitem>
</orderedlist> </orderedlist>
@ -1929,7 +1978,7 @@ DB2 server from remote clients, perform the following steps:
<orderedlist> <orderedlist>
<listitem> <listitem>
<para>Set the port on which DB2 should communicate. Ensure that you select a port that <para>Set the port on which DB2 should communicate. Ensure that you select a port that
is not blocked by a firewall or used by another service defined in the /etc/services file. is not blocked by a firewall or used by another service defined in the <filename>/etc/services</filename> file.
To set the communications port, update the DB2 database manager configuration variable To set the communications port, update the DB2 database manager configuration variable
SVCENAME. For example, to set the communications port to 50055, issue the following command SVCENAME. For example, to set the communications port to 50055, issue the following command
as the instance user ("db2inst1", if you've been using the defaults): as the instance user ("db2inst1", if you've been using the defaults):
@ -1961,13 +2010,13 @@ Running the DB2 Control Center and other DB2 GUI tools
</title> </title>
<para>To run the DB2 Control Center or other DB2 GUI tools, you must install the IBM <para>To run the DB2 Control Center or other DB2 GUI tools, you must install the IBM
Software Developers' Kit for Java. This RPM is included in the DB2 install CD-ROM in Software Developers' Kit for Java. This RPM is included in the DB2 install CD-ROM in
the /db2/linux/Java-1.4/ directory. To install the IBM Software Developers' Kit for the <filename class="directory">/db2/linux/Java-1.4/</filename> directory. To install the IBM Software Developers' Kit for
Java, change to the root directory of the CD-ROM and issue the following command: Java, change to the root directory of the CD-ROM and issue the following command:
<screen> <screen>
sudo alien -d -i -c db2/linux/Java-1.4/IBMJava2-SDK-1.4.1-2.0.i386.rpm sudo alien -dic db2/linux/Java-1.4/IBMJava2-SDK-1.4.1-2.0.i386.rpm
</screen> </screen>
</para><para> </para><para>
Log in as the db2inst1 and invoke the DB2 Control Center: Log in as the db2inst1 user and invoke the DB2 Control Center:
<screen>db2cc</screen> <screen>db2cc</screen>
</para> </para>
</sect3> </sect3>
@ -1989,7 +2038,7 @@ Center has it's own Java based installer, any Java issues that you
experienced above while installing DB2 UDB will likely recur here. experienced above while installing DB2 UDB will likely recur here.
However, the fixes we've provided for the DB2 UDB install should work However, the fixes we've provided for the DB2 UDB install should work
for the DB2 UDB Information Center install too.</para> for the DB2 UDB Information Center install too.</para>
<para>After mounting, run the "db2setup" utility from the base <para>After mounting, run the <command>db2setup</command> utility from the base
directory. This will launch the Java-based setup wizard. You can also directory. This will launch the Java-based setup wizard. You can also
use the other setup methods we've talked about, but since the GUI use the other setup methods we've talked about, but since the GUI
installation sets up and configures everything for you, that's the installation sets up and configures everything for you, that's the
@ -2008,7 +2057,7 @@ settings), check the empty box, otherwise click
"Next".</para></listitem> "Next".</para></listitem>
<listitem><para>Add any additional languages that you want to have <listitem><para>Add any additional languages that you want to have
installed. English is installed by default and cannot be deselected. installed. English is installed by default and cannot be deselected.
Each additional language will add anywhere from 5&ndash;50 MB to the Each additional language will add anywhere from 5 MB to 50 MB to the
installation size. Click "Next".</para></listitem> installation size. Click "Next".</para></listitem>
<listitem><para>The next panel is where things get a little interesting. <listitem><para>The next panel is where things get a little interesting.
Here you can specify the service name that the Information Center will Here you can specify the service name that the Information Center will
@ -2021,7 +2070,7 @@ serve up the documentation. By default, this is port
51000.</para> 51000.</para>
<para>The check box on this page will change the <para>The check box on this page will change the
configuration for all DB2 UDB products installed on the local system, so configuration for all DB2 UDB products installed on the local system, so
that their help system will use the parameters you define here.Click that their help system will use the parameters you define here. Click
"Next".</para></listitem> "Next".</para></listitem>
<listitem><para>Read the summary of what will be done, then click <listitem><para>Read the summary of what will be done, then click
"Finish" to start the file "Finish" to start the file
@ -2056,11 +2105,11 @@ daemon).</para></sect3></sect2>
<sect2><title>The Information Center daemon</title> <sect2><title>The Information Center daemon</title>
<para>The Information Center daemon is set up during installation and is <para>The Information Center daemon is set up during installation and is
used to launch the background process that runs the Information Center. used to launch the background process that runs the Information Center.
The daemon script, named db2icd is installed to the <filename class='directory'>/etc/init.d/</filename> The daemon script, named <command>db2icd</command> is installed to the <filename class='directory'>/etc/init.d/</filename>
directory, and start up symbolic links are added to the directory, and start up symbolic links are added to the
<filename class='directory'>/etc/init.d/rc.X/</filename> run-level folders. By default, the daemon is turned on <filename class='directory'>/etc/init.d/rc.X/</filename> run-level folders. By default, the daemon is turned on
for run-levels 2, 3 and 5. You can modify these run-levels with any for run-levels 2, 3 and 5. You can modify these run-levels with any
system init utility (chkconfig, ntsysv, or any of the X-based system init utility (<command>chkconfig</command>, <command>ntsysv</command>, or any of the X-based
variants).</para> variants).</para>
<para>There are 5 commands you can pass to the daemon: <para>There are 5 commands you can pass to the daemon:
<orderedlist> <orderedlist>
@ -2420,9 +2469,9 @@ updates and kernel information.</para></listitem>
<para>The Fedora Project is a Red-Hat-sponsored and community-supported open source <para>The Fedora Project is a Red-Hat-sponsored and community-supported open source
project. It is not a supported product of Red Hat, project. It is not a supported product of Red Hat,
Inc.</para></listitem> Inc.</para></listitem>
<listitem><para>Mandrake Linux</para> <listitem><para>Mandriva Linux</para>
<para><ulink url='http://www.mandrakesoft.com/'>http://www.mandrakesoft.com/</ulink></para> <para><ulink url='http://www.mandriva.com/'>http://www.mandriva.com/</ulink></para>
<para>Home to the Mandrake Linux distribution. </para> <para>Home to the Mandriva Linux distribution. </para>
<para>Their current slogan is "A Linux for everyone".</para></listitem></itemizedlist></sect2></sect1> <para>Their current slogan is "A Linux for everyone".</para></listitem></itemizedlist></sect2></sect1>
<sect1 id="gfdl"><title>GNU Free Documentation License</title><titleabbrev>Version 1.2, November <sect1 id="gfdl"><title>GNU Free Documentation License</title><titleabbrev>Version 1.2, November
2002</titleabbrev> 2002</titleabbrev>