6장. Completing post customization tasks

Procedure

1. Navigate to a working directory such as /tmp, and create a subdirectory named product/:

   $ cd /tmp

2. Create a subdirectory product/

   $ mkdir product/

3. Create a directory structure identical to the location of the file you want to replace. For example, if you want to test an add-on that is present in the /usr/share/anaconda/addons directory on the installation system, create the same structure in your working directory:

   $ mkdir -p product/usr/share/anaconda/addons

   참고

   To view the installer’s runtime filesystem, boot the installation and switch to virtual console 1 (Ctrl+Alt+F1) and then switch to the second tmux window (Ctrl+b+2). A shell prompt that can be used to browse a file system opens.

4. Place your customized files (in this example, custom add-on for Anaconda) into the newly created directory:

   $ cp -r ~/path/to/custom/addon/ product/usr/share/anaconda/addons/

5. Repeat steps 3 and 4 (create a directory structure and place the custom files into it) for every file you want to add to the installer.

6. Create a .buildstamp file in the root of the directory. The .buildstamp file describes the system version, the product and several other parameters. The following is an example of a .buildstamp file from Red Hat Enterprise Linux 8.4:

   [Main]
   Product=Red Hat Enterprise Linux
   Version=8.4
   BugURL=https://bugzilla.redhat.com/
   IsFinal=True
   UUID=202007011344.x86_64
   [Compose]
   Lorax=28.14.49-1

   The IsFinal parameter specifies whether the image is for a release (GA) version of the product (True), or a pre-release such as Alpha, Beta, or an internal milestone (False).

7. Navigate to the product/ directory, and create the product.img archive:

   $ cd product

   $ find . | cpio -c -o | gzip -9cv > ../product.img

   This creates a product.img file one level above the product/ directory.

8. Move the product.img file to the images/ directory of the extracted ISO image.

   The product.img file is now created and the customizations that you want to make are placed in the respective directories.

   참고

   Instead of adding the product.img file on the boot media, you can place this file into a different location and use the inst.updates= boot option at the boot menu to load it. In that case, the image file can have any name, and it can be placed in any location (USB flash drive, hard disk, HTTP, FTP or NFS server), as long as this location is reachable from the installation system.