From c4b24a0400fef21cd9bbea34c923246d4dceac22 Mon Sep 17 00:00:00 2001 From: Jared Smith Date: Tue, 27 Feb 2018 12:53:14 -0500 Subject: [PATCH] Fix up another link and create another dictionary --- en-US/anaconda/anaconda_logging.adoc | 5 +++-- en-US/anaconda/anaconda_product_image.adoc | 12 +++++++----- 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/en-US/anaconda/anaconda_logging.adoc b/en-US/anaconda/anaconda_logging.adoc index 408059b..1f57edc 100644 --- a/en-US/anaconda/anaconda_logging.adoc +++ b/en-US/anaconda/anaconda_logging.adoc @@ -38,8 +38,9 @@ Certain log messages are also written to the terminals: Log files always contain messages from all the loglevels, including debug, but the minimal loglevel on the terminals can be controlled with the `loglevel` link:https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#inst-loglevel[command line option]. There are two other log files created on the target filesystem, in the `/root` directory, also accessible at `/mnt/sysimage/root` during the installation: -* `/mnt/sysimage/root/install.log`, log of the package installation process. -* `/mnt/sysimage/root/install.log.syslog`, messages from installation chroot logged through the system's syslog. + +`/mnt/sysimage/root/install.log`:: log of the package installation process. +`/mnt/sysimage/root/install.log.syslog`:: messages from installation chroot logged through the system's syslog. Mostly information about users and groups created during dnf|yum's package installation. diff --git a/en-US/anaconda/anaconda_product_image.adoc b/en-US/anaconda/anaconda_product_image.adoc index 80fbf6d..10f5be4 100644 --- a/en-US/anaconda/anaconda_product_image.adoc +++ b/en-US/anaconda/anaconda_product_image.adoc @@ -1,24 +1,26 @@ = Creating a Product image Anaconda supports several ways to load new code at runtime. -Passing `inst.updates=` is one way to do this and is documented on the file:/anaconda/anaconda_updates.html[updates] page. +Passing `inst.updates=` is one way to do this and is documented on the link:anaconda_updates.html[updates] page. Another is to include a product.img in the install tree, inside the `/images/` directory. It will be applied at runtime and can overwrite any file on the system, just like the updates.img. One use for a product.img is to add a new installclass to Anaconda. A product image for a new installclass can be created from a directory of files like this: +[source,bash] ---- -mkdir -p product/run/install/product/pyanaconda/installclasses/ -vim product/run/install/product/pyanaconda/installclasses/custom.py +$ mkdir -p product/run/install/product/pyanaconda/installclasses/ +$ vim product/run/install/product/pyanaconda/installclasses/custom.py ---- Create new installclass, see link:https://github.com/rhinstaller/anaconda/tree/master/pyanaconda/installclasses[Anaconda code] for examples. Now you can create the product.img: +[source,bash] ---- -cd product/ -find . | cpio -c -o | pigz -9cv > ../product.img +$ cd product/ +$ find . | cpio -c -o | pigz -9cv > ../product.img ---- Now you can include product.img in the tree, inside `/images/`.