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

Minor corrections (mainly typos).

This commit is contained in:
luigi 2002-12-04 00:37:11 +00:00
parent 03a009e528
commit bcfbabffd1
1 changed files with 79 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

118
LDP/howto/docbook/RedHat-CD-HOWTO/RedHat-CD-HOWTO.sgml
View File

@ -1,5 +1,4 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<article lang="en">
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> <article lang="en">
<!-- $Id$ -->
@ -17,32 +16,59 @@
<email>uknadors (at) yahoo (dot) com</email>
</address>
</affiliation>
<authorblurb>
<para>
Author of the current version and maintainer.
</para>
</authorblurb>
</author>
<author>
<firstname>Morten</firstname>
<surname>Kjeldgaard</surname>
<affiliation>
<address>
<email>&lt;mok (at) imsb (dot) au (dot) dk&gt;</email>
<email></email>
</address>
</affiliation>
<authorblurb>
<para>
Author of the original version.
</para>
</authorblurb>
</author>
<author>
<firstname>Peter</firstname>
<surname>von der Ah&eacute;</surname>
<affiliation>
<address>
<email>&lt;pahe+rhcd (at) daimi (dot) au (dot) dk&gt;</email>
<email></email>
</address>
</affiliation>
<authorblurb>
<para>
Author of the original version.
</para>
</authorblurb>
</author>
</authorgroup>
<revhistory>
<revision>
<revnumber>v2.0</revnumber>
<revnumber>v2.01</revnumber>
<date>2002-12-04</date>
<authorinitials>lb</authorinitials>
<revremark>
Second release of the new version of the howto.
All the scripts were reviewed and cleaned.
The updateDist.sh script now checks that all the
updates were downloaded before checking the signatures.
</revremark>
</revision>
<revision>
<revnumber>v2.00</revnumber>
<date>2002-10-28</date>
<authorinitials>lb</authorinitials>
<revremark>First release of the new version (2.00) of the HOWTO</revremark>
</revision>
</revhistory>
@ -56,8 +82,6 @@
<holder>Morten Kjeldgaard, and Peter von der Ah&eacute;</holder>
</copyright>
<releaseinfo>Fourth BETA version for release 2.0 of the HOWTO</releaseinfo>
<abstract>
<para>
This document describes how to make your own CDs from different releases of
@ -67,7 +91,7 @@
needed to include updated RPMS into the distribution. Some hints and
examples on how to customize the default installation are also presented.
Scripts to automate as much as possible the (re)generation of the CD images
are also included. Prerequisites are a good network connection, and a CD-writer
are included. Prerequisites are a good network connection, and a CD-writer
(a working knowledge of shell scripting could be really useful, though).
</para>
</abstract>
@ -93,7 +117,7 @@
<para>
This is what you will be taught in the next sections (hopefully). I will use the
i386 architecture and releases 7.3 and 8.0 of the distribution in the examples. The
notes related to the previous releases (<=6.1) were contained in a previous version of
notes related to the previous releases (&lt;=6.1) were contained in a previous version of
this document and were compiled by the original authors. The notes related to release
6.2 are based on tests I've not completed (and I don't know if I ever will) and some
documents you can find linked in the <xref linkend="related-doc"> section.
@ -317,7 +341,7 @@
The structure of each of these directories is similar to that described in
the section <xref linkend="redhat-main-tree">. So you will find for each version,
in the subdirectory <filename class='directory'>en/os/</filename> a series of
subdirectories representing the various architecture and a
subdirectories representing the various architectures and a
<filename class='directory'>noarch</filename> and <filename class='directory'>
SRPMS</filename> subdirectories, for packages which work on every architecture
or are in source form respectively.
@ -420,7 +444,7 @@
already known to you. See the section <xref linkend="rpm-packages"> for more
informations. The <filename class='directory'>base</filename> directory
holds different book-keeping files needed during the installation process,
like for release 7.3 and 8.0. The only noticeable differences being represented
like for releases 7.3 and 8.0. The only noticeable differences being represented
by a single <filename>hdlist</filename> file and a missing
<filename>stage2.img</filename> file whose functionalities should be provided
by the files included in the <filename class='directory'>instimage</filename>
@ -505,7 +529,7 @@
</screen>
</para>
<para>
Another version of the RPM packages contain the original sources
Another version of the RPM packages contains the original sources
used to build the binaries. These packages have the suffix
<emphasis>.src.rpm</emphasis> and are situated in the
<filename class='directory'>SRPMS</filename> directory. These packages compose
@ -627,16 +651,16 @@
<para>
If you want to check the GPG signatures to make sure of the authenticity of the
packages (which is something I suggest) you should install the
<emphasis>gnupg</emphasis> package and import the
<emphasis>security@redhat.com</emphasis> public key you can find in the root directory
of the CDs (<filename>RPM-GPG-KEY</filename>) or on the
<emphasis>gnupg</emphasis> package (needed only on Redhat 7.3) and import the
<emphasis>security@redhat.com</emphasis> public key you can find in the root
directory of the CDs (<filename>RPM-GPG-KEY</filename>) or on the
<ulink url="http://www.redhat.com/solutions/security/news/publickey.html#key">RedHat
website</ulink>. The key is imported by running the command:
<emphasis>gpg --import &lt;filename&gt; </emphasis> in releases up to and including
7.3, which is to be changed to read <emphasis>rpm --import &lt;filename&gt; </emphasis>
for release 8.0 (for more informations on this have a look at the
<ulink url="http://www.gnupg.org/">GNU Privacy Guard</ulink> and at the
<ulink url="http://www.rpm.org/">RPM</ulink> (Redhat Package Manager) websites).
<ulink url="http://www.rpm.org/">RPM</ulink> - Redhat Package Manager websites).
</para>
<para>
If you want to check the rpm packages you can do it using the following command
@ -696,12 +720,17 @@
The script will download the new updates excluding the subdirectories contained in
the <emphasis>EXCLUDELIST</emphasis> variable, moving the old ones (i.e. just
superseded by new versions) to the directory represented by the
<emphasis>OLDDIR</emphasis> variable and check their signatures depending on the
values of the two variables <emphasis>CHECKSIG</emphasis> and
<emphasis>USEGPG</emphasis>. In case of a failure in the signature checking process
the script will move the offending packages to <emphasis>OLDDIR</emphasis>
assigning them the <quote>.UPDcheckfail</quote> extension and exit without moving the
old updates to <emphasis>OLDDIR</emphasis>.
<emphasis>OLDDIR</emphasis> variable after having completed two tests.
The first test compares the <filename>.listing</filename> files generated by
<filename>wget</filename> to the content of the local directories to make sure
all the files were downloaded.
The second test verifies the packages signatures depending on the values of the
two variables <emphasis>CHECKSIG</emphasis> and <emphasis>USEGPG</emphasis> (set both
of them to <quote>yes</quote> if you want the operation to be completed). In case
of a failure in the signature checking process the script will move the offending
packages to <emphasis>OLDDIR</emphasis> assigning them the
<quote>.UPDcheckfail</quote> extension and exit without moving the old updates to
<emphasis>OLDDIR</emphasis>.
</para>
</sect2>
@ -770,7 +799,7 @@
<note>
<para>
I haven't personally tested this procedure. It was the only proposed one
for the older versions of the howto (up to version 1.34, regarding RedHat <=6.1).
for the older versions of the howto (up to version 1.34, regarding RedHat &lt;=6.1).
Nevertheless, I believe this has had, so far, much more testing than my scripts,
so you want to maybe consider using it.
</para>
@ -898,7 +927,7 @@
</para>
<sect3 id="rh61-rebuild" xreflabel="Rebuilding the 6.1 installer">
<title>RedHat <= 6.1</title>
<title>RedHat &lt;= 6.1</title>
<sect4>
<title>Regenerating the hdlist file</title>
<para>
@ -1162,14 +1191,19 @@
of the anaconda installer. To complete this part, you <emphasis>must</emphasis> use
a Linux RedHat 7.3 or 8.0 machine with the <emphasis>anaconda-runtime</emphasis>
package installed (it will probably have version 7.3.7 or 8.0.4), depending on the
release you want to rebuild. The procedure is composed by seven steps
which are put together in a shell script in the last section:
release you want to rebuild. The procedure is composed by seven steps:
<orderedlist numeration='lowerroman'>
<listitem>
<para>Regenerating the hdlist and hdlist2 files</para>
<para>
Regenerating the <filename>hdlist</filename> and
<filename>hdlist2</filename> files
</para>
</listitem>
<listitem>
<para>Updating the <emphasis>comps.xml</emphasis> file</para>
<para>
Updating the <filename>comps.xml</filename> (or
<filename>comps</filename>) file
</para>
</listitem>
<listitem>
<para>Rebuilding the installer</para>
@ -1178,7 +1212,10 @@
<para>Splitting the distribution in CD-sized chunks</para>
</listitem>
<listitem>
<para>Regenerating the hdlist and hdlist2 files (again)</para>
<para>
Regenerating the <filename>hdlist</filename>
and <filename>hdlist2</filename> files (again)
</para>
</listitem>
<listitem>
<para>Generating the iso images</para>
@ -1529,7 +1566,7 @@
If you're paranoid, you can test your new disk image(s) by mounting it. If you
forgot to fix the file permissions or set the rock ridge extensions then
the error will be obvious here since the file names and directory structure
will be wrong. The (optional) test can be done by issuing the commad:
will be wrong. The (optional) test can be done by issuing the command:
</para>
<para>
<screen>
@ -1844,7 +1881,8 @@
minimal installation which fits (this time, almost perfectly) our needs (they are,
actually, my needs, your mileage may definitely vary). If you want to include a
modified <emphasis>comps</emphasis> file in your CDs, you should copy
it into the main tree just before starting <xref linkend="rh73-rebuild">.
it into the main tree just before starting the operations described in
<xref linkend="rh73-rebuild">.
</para>
<sect4>
@ -1948,17 +1986,19 @@
<emphasis>kickstart</emphasis>, for more informations about it you can read
<ulink url="http://www.redhat.com/docs/manuals/linux/RHL-8.0-Manual/custom-guide/ch-kickstart2.html">
The RedHat Linux Customization Guide</ulink>. In the example, I didn't unselect
completely the installation of the <quote>core</quote> group, because there are
completely the installation of the <quote>Base</quote> group, because there are
too many packages I usually need, so I just unselected the default installation
for these packages making them optional. As you can see, even the
<filename>redhat-logos</filename> package in the <quote>Base</quote> group was made
<filename>redhat-logos</filename> package in the <quote>Core</quote> group was made
optional. Considering that all of the packages in this group, together, should
represent the <emphasis>smallest possible</emphasis> installation, you probably
don't want to do this (by the way my CDs work even with this, there should be
some failure I cannot see, yet). The last noticeable modification was made to
the <quote>dialup</quote> group, which will be installed even if unselected because
the <quote>core</quote> group depends on it (as declared in the group definition
itself).
some failure I cannot see, yet). The <filename>tripwire</filename> package was
also added to the <quote>Base</quote> group. The last noticeable modification
was made to the <quote>dialup</quote> group, which will be installed even if
unselected because the <quote>Base</quote> group depends on it (as declared in
the group definition itself). I have selected only some packages I usually need
from this group for installation and left the rest of them unselected.
</para>
</sect4>
</sect3>
@ -2031,7 +2071,7 @@
instead of <filename>mkisofs</filename> and this should be the only difference.
</para>
<para>
The informations supplied for the new releases of Redhat (>6.1) shouldn't
The informations supplied for the new releases of Redhat (&gt;6.1) shouldn't
work with Mandrake, which has now a fairly different installer from the
Redhat one. I really don't know if some other clone of Redhat can have its
distribution CDs updated this way, but I would be happy if you let me know.
@ -2043,7 +2083,7 @@
<para>
The SGML source of the most recent version of this document can be
retrieved from
<ulink url="http://www.personam.it/luigi/redhat-cd-howto/RedHat-CD.sgml">here</ulink>.
<ulink url="http://www.personam.it/luigi/redhat-cd-howto/RedHat-CD-HOWTO.sgml">here</ulink>.
The previous version, created by Morten Kjeldgaard, and Peter von der Ah&eacute;,
can be found on
<ulink url="http://imsb.au.dk/~mok/linux/doc/RedHat-CD.sgml">imsb.au.dk</ulink>