diff --git a/LDP/howto/docbook/RedHat-CD-HOWTO/RedHat-CD-HOWTO.sgml b/LDP/howto/docbook/RedHat-CD-HOWTO/RedHat-CD-HOWTO.sgml index fabbca04..f5999b86 100644 --- a/LDP/howto/docbook/RedHat-CD-HOWTO/RedHat-CD-HOWTO.sgml +++ b/LDP/howto/docbook/RedHat-CD-HOWTO/RedHat-CD-HOWTO.sgml @@ -59,9 +59,18 @@ + + v2.1 + 2003-10-17 + lb + + Added RedHat 9. Fixed some minor bugs. Thanks to all the people who have sent + in comments and patches. + + v2.03 - 2002-03-10 + 2003-03-10 lb Added some comments and fixes to the howto. The anaconda updates are now @@ -70,7 +79,7 @@ v2.02 - 2002-03-06 + 2003-03-06 lb The signature checking now works for packages targeted to versions @@ -99,6 +108,7 @@ 2002 + 2003 Luigi Bitonti @@ -110,7 +120,7 @@ This document describes how to make your own CDs from different releases of - the Red Hat Linux distribution (up to and including release 8.0), equivalent + the Red Hat Linux distribution (up to and including release 9), equivalent to the ones commercially available from Red Hat. The structure of the distribution is described, as well as the procedure needed to include updated RPMS into the distribution. Some hints and @@ -141,15 +151,15 @@ 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 + i386 architecture and releases 7.3, 8.0 and 9 of the distribution in the examples. The notes related to the previous releases (<=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 section. The procedure given in the following sections for RedHat 7.3 and 8.0 is likely to work - on all platforms supported by Red Hat (Alpha, ppc, etc.), for all the 7.x (and maybe 8.x + on all platforms supported by Red Hat (Alpha, ppc, etc.), for all the 7.x (and maybe 8.x/9 in a not too far future) releases, but I have only tested it on the i386 platform with - Redhat Linux 7.3 and 8.0 (I would be interested in additional information). + Redhat Linux 7.3, 8.0 and 9 (I would be interested in additional information). @@ -198,20 +208,20 @@ Let's have a look at the distribution tree. - - Redhat 8.0 directories organization + + Redhat 9 directories organization The latest distribution is, as of this writing, available only for the i386 platform. The toplevel directory appears a bit shallow, given the presence of a single architecture. (pub/redhat/linux/8.0/en/os/ + url="ftp://ftp.redhat.com/pub/redhat/linux/9/en/os/">pub/redhat/linux/9/en/os/ ). i386/ - Otherwise, the toplevel directory, for releases slightly older than 8.0, contains + Otherwise, the toplevel directory, for releases slightly older than 9, contains distributions for the different platforms. For example, the corresponding directory for release 7.1 of Redhat Linux, is structured this way: @@ -220,38 +230,41 @@ - The root of the i386 directory looks like this: + The root of the i386 directory in a Redhat 9 distribution looks like this: - -rwxr-xr-x 1 root root 248 Sep 10 21:19 autorun - drwxr-xr-x 7 root root 4096 Oct 25 10:43 dosutils - -rwxr-xr-x 1 root root 6194 Sep 10 21:19 EULA - -rwxr-xr-x 1 root root 18385 Sep 10 21:19 GPL - drwxr-xr-x 3 root root 4096 Oct 25 10:43 images - drwxr-xr-x 2 root root 4096 Oct 25 10:43 isolinux - -rw-r--r-- 1 root root 28320 Oct 24 22:36 pkgorder.txt - -rwxr-xr-x 1 root root 5350 Sep 10 21:19 README - -rwxr-xr-x 1 root root 13342 Sep 10 21:19 README-Accessibility - -rwxr-xr-x 1 root root 5781 Sep 10 21:19 README.de - -rwxr-xr-x 1 root root 5956 Sep 10 21:19 README.es - -rwxr-xr-x 1 root root 6351 Sep 10 21:19 README.fr - -rwxr-xr-x 1 root root 5684 Sep 10 21:19 README.it - -rwxr-xr-x 1 root root 6836 Sep 10 21:19 README.ja - -rwxr-xr-x 1 root root 6566 Sep 10 21:19 README.ko - -rwxr-xr-x 1 root root 4965 Sep 10 21:19 README.zh_CN - -rwxr-xr-x 1 root root 5267 Sep 10 21:19 README.zh_TW - drwxr-xr-x 4 root root 4096 Oct 25 10:43 RedHat - -rwxr-xr-x 1 root root 37493 Sep 10 21:19 RELEASE-NOTES - -rwxr-xr-x 1 root root 47340 Sep 10 21:19 RELEASE-NOTES-de.html - -rwxr-xr-x 1 root root 44726 Sep 10 21:19 RELEASE-NOTES-es.html - -rwxr-xr-x 1 root root 47994 Sep 10 21:19 RELEASE-NOTES-fr.html - -rwxr-xr-x 1 root root 42160 Sep 10 21:19 RELEASE-NOTES.html - -rwxr-xr-x 1 root root 44680 Sep 10 21:19 RELEASE-NOTES-it.html - -rwxr-xr-x 1 root root 56720 Sep 10 21:19 RELEASE-NOTES-ja.html - -rwxr-xr-x 1 root root 50814 Sep 10 21:19 RELEASE-NOTES-ko.html - -rwxr-xr-x 1 root root 37770 Sep 10 21:19 RELEASE-NOTES-zh_CN.html - -rwxr-xr-x 1 root root 39122 Sep 10 21:19 RELEASE-NOTES-zh_TW.html - -rwxr-xr-x 1 root root 1910 Sep 10 21:19 RPM-GPG-KEY - -rwxr-xr-x 1 root root 338 Sep 10 21:56 TRANS.TBL + -rwxr-xr-x 2 root root 248 Mar 14 2003 autorun + drwxr-xr-x 7 root root 4096 Mar 14 2003 dosutils + -rw-r--r-- 3 root root 6192 Mar 14 2003 EULA + -rw-r--r-- 3 root root 18385 Mar 14 2003 GPL + drwxr-xr-x 3 root root 2048 Mar 14 2003 images + drwxr-xr-x 2 root root 2048 Mar 14 2003 isolinux + -rw-r--r-- 3 root root 6127 Mar 14 2003 README + -rw-r--r-- 2 root root 13052 Mar 14 2003 README-Accessibility + -rw-r--r-- 2 root root 6686 Mar 14 2003 README.de + -rw-r--r-- 2 root root 6990 Mar 14 2003 README.es + -rw-r--r-- 2 root root 6492 Mar 14 2003 README.fr + -rw-r--r-- 2 root root 6805 Mar 14 2003 README.it + -rw-r--r-- 2 root root 7995 Mar 14 2003 README.ja + -rw-r--r-- 2 root root 7312 Mar 14 2003 README.ko + -rw-r--r-- 2 root root 5070 Mar 14 2003 README.pt + -rw-r--r-- 2 root root 6613 Mar 14 2003 README.pt_BR + -rw-r--r-- 2 root root 5879 Mar 14 2003 README.zh_CN + -rw-r--r-- 2 root root 5892 Mar 14 2003 README.zh_TW + drwxr-xr-x 4 root root 2048 Mar 14 2003 RedHat + -rw-r--r-- 2 root root 25824 Mar 14 2003 RELEASE-NOTES + -rw-r--r-- 2 root root 29902 Mar 14 2003 RELEASE-NOTES-de.html + -rw-r--r-- 2 root root 30409 Mar 14 2003 RELEASE-NOTES-es.html + -rw-r--r-- 2 root root 32354 Mar 14 2003 RELEASE-NOTES-fr.html + -rw-r--r-- 2 root root 30064 Mar 14 2003 RELEASE-NOTES.html + -rw-r--r-- 2 root root 29925 Mar 14 2003 RELEASE-NOTES-it.html + -rw-r--r-- 2 root root 34666 Mar 14 2003 RELEASE-NOTES-ja.html + -rw-r--r-- 2 root root 33520 Mar 14 2003 RELEASE-NOTES-ko.html + -rw-r--r-- 2 root root 29496 Mar 14 2003 RELEASE-NOTES-pt_BR.html + -rw-r--r-- 2 root root 22747 Mar 14 2003 RELEASE-NOTES-pt.html + -rw-r--r-- 2 root root 25217 Mar 14 2003 RELEASE-NOTES-zh_CN.html + -rw-r--r-- 2 root root 26645 Mar 14 2003 RELEASE-NOTES-zh_TW.html + -rw-r--r-- 3 root root 1910 Mar 14 2003 RPM-GPG-KEY + -r--r--r-- 1 root root 1823 Mar 14 2003 TRANS.TBL @@ -262,14 +275,14 @@ The images directory contains boot and drivers floppy images that can be copied to a diskette if needed. In the - 8.0 release, there are three boot disk images available. The first boot - image is called boot.img, and is required when installation - is performed directly from a CD-ROM. If installing from a NFS mounted disk or FTP - is required, the bootnet.img disk image is needed. - Installs through PCMCIA adapters need the pcmcia.img - floppy. See section and references therein for - details and consult the README file in the directory for a more detailed explanation - of the various files. + 9 release, there is only one boot disk image available. This boot image is named + bootdisk.img. A secondary driver disk is required beside + this one if the installation is not performed directly from a CD-ROM or HD. A + boot.iso file has now been added to boot a machine from + the cdrom drive and start (network) installations more easily (i.e. without messing up + with too many floppies). See section and references + therein for details and consult the README file in the directory for a more detailed + explanation of the various files. The isolinux directory contains @@ -360,6 +373,7 @@ drwxrwsr-x 4 root root 4096 Jul 13 10:13 7.2 drwxrwsr-x 3 root root 4096 Jul 13 10:14 7.3 drwxrwsr-x 3 root root 4096 Jul 13 10:14 8.0 + drwxrwsr-x 3 root root 4096 Jul 13 10:14 9 @@ -384,6 +398,27 @@ + + Differences for the 8.0 tree + + The 8.0 distribution layout is almost identical to the one just described. The only + major differences, in this respect, can be found in the images directory. + + + The images directory contains boot + and drivers floppy images that can be copied to a diskette if needed. In the + 8.0 release, there are three boot disk images available. The first boot + image is called boot.img, and is required when installation + is performed directly from a CD-ROM. If installing from a NFS mounted disk or FTP + is required, the bootnet.img disk image is needed. + Installs through PCMCIA adapters need the pcmcia.img + floppy. See section and references therein for + details and consult the README file in the directory for a more detailed explanation + of the various files. + + + + Differences for the 7.x tree @@ -395,8 +430,8 @@ to the way the installation CDs are made bootable in releases prior to 8.0 (floppy emulation has been superseded by no emulation in release 8.0), while the second is an effect of the migration of - the comps file format to XML in Redhat 8.0 - (that's why it was renamed comps.xml). + the comps file format to XML in Redhat + releases after 8.0 (that's why it was renamed comps.xml). The Redhat/base/comps file is, in fact, a simple textual file with a quite inflexible syntax in releases prior to and including Redhat 7.3. @@ -442,12 +477,12 @@ can be found in HTML format in the directory or on the Redhat website ( Redhat 6.2 Installation guide). Next, there are the reference guide - and the getting started guide. The documentation for the 7.x/8.x releases is on + and the getting started guide. The documentation for the 7.x/8.0/9 releases is on a separate CD (in a different tree, on the ftp site). The images directory contains boot floppy - images that can be copied to a diskette if needed, like for 8.0 and 7.3. See + images that can be copied to a diskette if needed, like for 8.0, 7.3 and 9. See section and references therein for details. The misc directory contains source and executables of a number of programs needed for the installation. @@ -469,7 +504,7 @@ already known to you. See the section for more informations. The base directory holds different book-keeping files needed during the installation process, - like for releases 7.3 and 8.0. The only noticeable differences being represented + like for releases 7.3, 8.0 and 9. The only noticeable differences being represented by a single hdlist file and a missing stage2.img file whose functionalities should be provided by the files included in the instimage @@ -478,7 +513,7 @@ The updates directory is really similar - to the one described for release 8.0 with the only difference of having more + to the one described for release 9 with the only difference of having more architecture related directories. @@ -559,9 +594,9 @@ .src.rpm and are situated in the SRPMS directory. These packages compose the last two CDs and part of the third one out of the five which compose the 8.0 (or - 7.3) release. For 6.2 (and previous, not too old, versions), things change a bit because - there is only one installation CD not comprising the SRPMS packages, which you can - burn on a different disc, if you want. + 7.3) release. For release 9 they are on three separate CDs. For 6.2 (and previous, + not too old, versions), things change a bit because there is only one installation CD + not comprising the SRPMS packages, which you can burn on a different disc, if you want. To obtain more informations on the Redhat package manager, I suggest you to read @@ -652,7 +687,7 @@ Create a directory to hold the installation files and cd into it, then issue the command (which will download ~3Gb of data on your - hard drive, for RedHat 7.3 and 8.0): + hard drive): @@ -693,7 +728,7 @@ website. The key is imported by running the command: gpg --import <filename> in releases up to and including 7.3, which is to be changed to read rpm --import <filename> - for release 8.0 (for more informations on this have a look at the + for releases 8.0 and 9 (for more informations on this have a look at the GNU Privacy Guard and at the RPM - Redhat Package Manager websites). @@ -709,14 +744,14 @@ - For release 8.0 (and for future releases as well I guess): + For release 8.0 and 9 (and for future releases as well I guess): $ find . -name "*.rpm" -exec rpm -K {} \; |grep "NOT *OK" If you don't want to bother yourself with all these steps, I hope you - want at least to check for the integrity of the downloaded files (which doesn't mean + want to check (at least) for the integrity of the downloaded files (which doesn't mean nobody has tampered with them), verifying the md5 signatures. This is done with: @@ -726,7 +761,7 @@ - For release 8.0 (and for future releases as well, I guess): + For release 8.0 and 9 (and for future releases as well, I guess): $ find . -name "*.rpm" -exec rpm -K --nosignature {} \; |grep "NOT *OK" @@ -835,8 +870,6 @@ 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). - Nevertheless, I believe this has had, so far, much more testing than my scripts, - so you want to maybe consider using it. @@ -882,7 +915,7 @@ updatePerm.sh script on your local copy of the distribution. It is really needed only for version 6.2 and older, the only part useful to - the 7.3/8.0 releases procedure is the directories permissions update, even if the + the 7.3/8.0/9 releases procedure is the directories permissions update, even if the rest won't hurt and things are kept coherent. It is almost equal to the updatePerm script included in the previous version of the howto, just some slight changes were made. Before using this script you @@ -1172,7 +1205,7 @@ The mkisofs and cdrecord steps can be executed by means of a graphical frontend like X-CD-Roast which should currently - support the creation of bootable CDs (I've never done it, so don't expect me + support the creation of bootable CDs (I've never used it, so don't expect me to give you any explanation). @@ -1186,7 +1219,7 @@ The introduction of version 4 of the Redhat Package Manager (RPM), made the procedure to update the anaconda installer fail. So the procedures listed will work only if the updated packages were built using a version of the RPM - software which is older than or equal to 3.0.5 (so, basically, 3.0.4 or 3.0.5). + software which is older than or equal to 3.0.4 (so, basically, 3.0.4 or 3.0.5). If you are using the original packages from Redhat, you have to avoid using @@ -1216,7 +1249,7 @@ - RedHat 8.0 and 7.3 + RedHat 9, 8.0 and 7.3 Once again a lot of things have changed with the release of the 7.x series of the distribution. There are now more operations to complete to obtain a fresh and @@ -1224,9 +1257,9 @@ and now the tree has to be split to fit on the media. This is done by means of the splitdistro script, which is written in python like most of the anaconda installer. To complete this part, you must use - a Linux RedHat 7.3 or 8.0 machine with the anaconda-runtime - 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: + a Linux RedHat 7.3, 8.0 or 9 machine with the anaconda-runtime + package installed (it will probably have version 7.3.7, 8.0.4 or 9.0.4), depending + on the release you want to rebuild. The procedure is composed by seven steps: @@ -1275,7 +1308,7 @@ invocation of the scripts which don't need this modification. - For redhat 8.0: + For redhat 9 and 8.0: $ chmod -R u+w /absolute-path-to-toplevel-dir $ mkdir -p /absolute-path-to-toplevel-dir/i386 @@ -1326,14 +1359,17 @@ now based on XML. It provides much more flexibility and ease of customization as you can read in . If you have modified or intend to modify the list of the installed packages, you need to complete this step. This, - in turn, implies having the + in turn, implies having the modified version of comps-9.tar.gz + + comps-9.tar.gz (the original one doesn't work for me) or - comps-8.0.tar.gz package including the master comps file found on the - Redhat website and the comps-extras rpm package installed. - Follow these steps (only fo Redhat 8.0): + comps-8.0.tar.gz package (depending on the release you are building) + including the master comps file found on the Redhat website and the + comps-extras rpm package installed. + Follow these steps for Redhat 9 and 8.0: $ cd /some-dir-of-your-choice - $ tar xzvf /path-to-comps-8.0.tar.gz/comps-8.0.tar.gz + $ tar xzvf /path-to-comps-9.tar.gz/comps-9.tar.gz $ cd comps $ make $ cat comps-milan.xml |sed 's!</comps>!!g' >comps-tmp.xml @@ -1344,11 +1380,12 @@ Beside /absolute-path-to-toplevel-dir, you should take care of assigning valid names to /some-dir-of-your-choice and - /path-to-comps-8.0.tar.gz. The rest of the commands can be just - copied. + /path-to-comps-9.tar.gz. The rest of the commands can be just + copied. And... you must (obviously) change 9 to read 8.0 if you are building + a Redhat 8.0 distribution. - Before issuing the make command, you should modify the file + Again, before issuing the make command, you should modify the file comps-milan.xml.in using your favourite text editor and following the guidelines and the suggestions found in and on the @@ -1377,17 +1414,28 @@ This will rebuild the anaconda installer in your local copy of the distribution using your updated packages. + For Redhat 9 execute: + + $ /usr/lib/anaconda-runtime/buildinstall \ + --pkgorder /absolute-path-to-toplevel-dir/pkgorder.txt \ + --comp dist-9 --product "Red Hat Linux" --version 9 \ + --release "Redhat 9 (Shrike)" /absolute-path-to-toplevel-dir/i386 + + Where, once again, /absolute-path-to-toplevel-dir is + the directory where the root of your local copy of the distribution is located. + + + For Redhat 8.0, the procedure is pretty much the same (the --product + option is missing): $ /usr/lib/anaconda-runtime/buildinstall \ --pkgorder /absolute-path-to-toplevel-dir/pkgorder.txt \ --comp dist-8.0 --version 8.0 --release "Redhat 8.0 (Psyche)" \ /absolute-path-to-toplevel-dir/i386 - Where, once again, /absolute-path-to-toplevel-dir is - the directory where the root of your local copy of the distribution is located. - For Redhat 7.3, the procedure is pretty much the same: + Or if you are still using Redhat 7.3 (as I am): $ /usr/lib/anaconda-runtime/buildinstall \ --pkgorder /absolute-path-to-toplevel-dir/pkgorder.txt \ @@ -1410,7 +1458,7 @@ This will not work at all for Redhat 7.3 if you don't use the modified version of the splitdistro script reported in the next - paragraph. For Redhat 8.0, a modified version of + paragraph. For Redhat 8.0 and 9, a modified version of splitdistro is provided mainly because even if the problems in the previous script were fixed, the execution now fails if there are not enough packages to fill all the CDs (the first four completely and the @@ -1420,11 +1468,11 @@ $ $/usr/lib/anaconda-runtime/splitdistro \ --fileorder /absolute-path-to-toplevel-dir/pkgorder.txt --release \ - "Redhat 8.0 (Psyche)" /absolute-path-to-toplevel-dir i386 + "Redhat 9 (Shrike)" /absolute-path-to-toplevel-dir i386 - The only thing you need to change for 7.3 is the string passed to the - --release option (which should be - Redhat 7.3 (Valhalla)) + The only thing you need to change for 8.0 and 7.3 is the string passed to the + --release option (which should read + Redhat 8.0 (Psyche) or Redhat 7.3 (Valhalla)) For Redhat 7.3 the version of the @@ -1457,6 +1505,12 @@ failing, but generates the CDs without source packages) or there is one CD which hasn't any package on it (instead of failing, generates an empty directory). + + For Redhat 9 you can find a copy of the script with the same modifications + applied to the version included in release 8.0 here: + splitdistro9. Everything said + for Redhat 8.0 in the previous paragraph applies to release 9. + @@ -1464,7 +1518,7 @@ This is needed to recreate the hdlist and hdlist2 files, using some of the informations obtained in the previous steps. There are no differences - between 7.3 and 8.0 for this execution of the program + between 7.3, 8.0 and 9 for this execution of the program The command to issue is the following: $ /usr/lib/anaconda-runtime/genhdlist \ @@ -1487,7 +1541,7 @@ Generating the iso images - Here you will prepare the 5 iso images to be burned on the actual CDs. There are + Here you will prepare the iso images to be burned on the actual CDs. There are two different commands to be used for the first disc and for the rest of them. This is due to the need of obtaining a first CD which is bootable. This is actually, not strictly necessary, because you could use a boot floppy instead @@ -1498,15 +1552,16 @@ $ mkdir /images-destination-dir - $ mkisofs -r -J -T -v -V "Red Hat 8.0 (Psyche) disc 1" \ + $ mkisofs -r -J -T -v -V "Red Hat 9 (Shrike) disc 1" \ -c isolinux/boot.cat -b isolinux/isolinux.bin -no-emul-boot \ -boot-load-size 4 -boot-info-table -o /images-destination-dir/i386-disc1.iso . - This is needed to burn the first (bootable) disc for RedHat 8.0 (with no floppy + This is needed to burn the first (bootable) disc for RedHat 8.0 and 9 (with no floppy emulation) and is executed from the top level directory of the distribution. The /images-destination-dir directory is the container for the five iso images you are generating, and it must exist - before starting the procedure. + before starting the procedure. The only thing which needs to be changed for Redhat 8.0 + is the volume name (it should be "Red Hat 8.0 (Psyche) disc 1"). @@ -1522,14 +1577,16 @@ The rest of the images can be written by means of this for loop $ for i in `echo 2 3 4 5` ; do mkisofs -r -J -T -v \ - -V "Red Hat 8.0 (Psyche) disc ${i}" \ + -V "Red Hat 9 (Shrike) disc ${i}" \ -o /images-destination-dir/i386-disc${i}.iso . ; done The loop just presented will prepare the last four images giving them the correct numbers. As you can see, there are just two missing options from the first run, and, as you can guess, they are needed only to create a bootable CD. In , you can read a brief explanation of - the various options and their meanings (most of it was extracted from the man page). + the various options and their meanings (most of it was extracted from the man page). + Again if you are building a Redhat 8.0 you should change the volume name to read + "Red Hat 8.0 (Psyche) disc ${i}". @@ -1544,8 +1601,8 @@ The following commands permit to inject and verify an md5 signature on an iso image: - $ /usr/lib/anaconda/implantisomd5 iso-image - $ /usr/lib/anaconda/checkisomd5 iso-image + $ /usr/lib/anaconda-runtime/implantisomd5 iso-image + $ /usr/lib/anaconda-runtime/checkisomd5 iso-image @@ -1562,7 +1619,7 @@ The updateBuild.sh script will execute all the steps needed to rebuild the - distribution CDs for RedHat 7.3 or 8.0 in a single run (as root). Before using this + distribution CDs for RedHat 7.3, 8.0 or 9 in a single run (as root). Before using this script you have to configure the rhcd.conf configuration file after exporting a RHCDPATH variable pointing to the directory where this file is. If you want to include @@ -1604,9 +1661,9 @@ will be wrong. The (optional) test can be done by issuing the command: - + # mount -t iso9660 -o ro,loop=/dev/loop0 iso-image /mnt/cdrom - + Where iso-image is the name you gave to the iso image file @@ -1614,9 +1671,9 @@ When you're done, don't forget to unmount it - + # umount /mnt/cdrom - + @@ -1959,9 +2016,9 @@ - Format of comps file in RedHat version 8.0 + Format of comps file in RedHat version 8.0 and 9 - With RedHat version 8.0, the format of the comps file + With RedHat version 8.0 and 9, the format of the comps file has changed completely and now an XML file, whose name is comps.xml, is used. Details on the file syntax can be found in the anaconda comps section @@ -1977,9 +2034,8 @@ Base and Core. The Base group should represent the minimal possible installation. - - Our first example revisited... + Our first example revisited for Redhat 8.0 This time, to customize your installation you have to edit the comps-milan.xml.in file with your favourite text editor. @@ -2010,9 +2066,8 @@ only ~220 packages (probably too many, again...). - - Our second example revisited... + Our second example revisited for Redhat 8.0 In the second comps file included, we build on the previous setup and strip @@ -2037,8 +2092,63 @@ - + + Customizing the default installation of RedHat version 9 + + We will reproduce (again) the examples presented for release 7.3/8 taking into + account the modifications the various groups were submitted to. + + + Our first example revisited for Redhat 9 + + As in the case of 8.0, to customize your installation you have to edit the + comps-milan.xml.in file with your favourite text editor. + This file can be found in the + + comps-9.tar.gz file among the script (as I said it is not + the same you can find on the Redhat website). To add the packages + information to the file you create, you need to have the + comps-extras rpm package installed. The commands + to be issued to complete the operation are listed in + and in the + documentation. + After you create the file, you have to copy it to the + Redhat/base directory overwriting the original one. + If you are using , you should only copy the + comps-milan.xml, (after having modified the + comps-milan.xml.in found in the + comps-9.tar.gz tar/gzip package and issued the + make command), to the destination you should have + already configured in the COMPSFILE variable + (rhcd.conf). + + + In the + first comps file included the libsafe + package was added to the Base group (component) and almost + every group (component) was deselected, apart from Base and + Core, so to have a default installation comprising + only ~240 packages (mmmhhh complexity is raising high...). + + + + Our second example revisited for Redhat 9 + + In the + second comps file included, we build on the previous setup and strip + down the default installation a bit more (this time, there will be only ~175 packages + in the default installation). This is really similar to the example presented for + Redhat 8.0, so I will avoid boring you with the same explanations. Once again, similar + results can be obtained using kickstart, for more informations + about it you can read + + The RedHat Linux Customization Guide. + + + + + @@ -2203,23 +2313,29 @@ - Morten Kjeldgaard, <mok@imsb.au.dk> + Morten Kjeldgaard, <mok (at) imsb (dot) au (dot) dk> - Peter von der Ahé, <pahe+rhcd@daimi.au.dk> + Peter von der Ahé, <pahe+rhcd (at) daimi (dot) au (dot) dk> - + + Giulia Tomaselli + + Jacinta Conneely Filippo Carcaci - Guillaume Lelarge <gleu@wanadoo.fr> + Guillaume Lelarge <gleu (at) wanadoo (dot) fr> - Alain Portal <> - + Alain Portal <aportal (at) univ-montp2 (dot) fr> + + + All the people on the anaconda-devel and kickstart mailing lists + @@ -2229,31 +2345,31 @@ - Lars Christensen <larsch@cs.auc.dk> + Lars Christensen <larsch (at) cs (dot) auc (dot) dk> - Thomas Duffy <tbd@cs.brown.edu> + Thomas Duffy <tbd (at) cs (dot) brown (dot) edu> - Dawn Endico <dawn@math.wayne.edu> + Dawn Endico <dawn (at) math (dot) wayne (dot) edu> - Seva <seva@null.cc.uic.edu> + Seva <seva (at) null (dot) cc (dot) uic (dot) edu> - Michael Thomas Cope <mcope@orion.ac.hmc.edu> + Michael Thomas Cope <mcope (at) orion (dot) ac (dot) hmc (dot) edu> - Charles J. Fisher <charles_fisher@bigfoot.com> + Charles J. Fisher <charles_fisher (at) bigfoot (dot) com> - Eric Thomas <eric.thomas@ericsson.com> + Eric Thomas <eric.thomas (at) ericsson (dot) com> - Gordon Yuen <gdccyuen@yahoo.com> + Gordon Yuen <gdccyuen (at) yahoo (dot) com> - Dave Morse <morse@nichimen.com> + Dave Morse <morse (at) nichimen (dot) com> diff --git a/LDP/howto/docbook/RedHat-CD-HOWTO/rhcd-scripts.tar.gz b/LDP/howto/docbook/RedHat-CD-HOWTO/rhcd-scripts.tar.gz index 09137194..de246922 100644 Binary files a/LDP/howto/docbook/RedHat-CD-HOWTO/rhcd-scripts.tar.gz and b/LDP/howto/docbook/RedHat-CD-HOWTO/rhcd-scripts.tar.gz differ