hank-test/quick-docs
1
0
Fork 0
mirror of https://pagure.io/fedora-docs/quick-docs.git synced 2024-11-24 21:35:17 +00:00
Code Issues 1 Projects Releases Packages Wiki Activity Actions

Fix up another link and create another dictionary

Browse source
This commit is contained in:
Jared Smith 2018-02-27 12:53:14 -05:00
parent f2999c65ce
commit 94389a7464
2 changed files with 10 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
en-US/anaconda/anaconda_logging.adoc
View file

@ -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.

12
en-US/anaconda/anaconda_product_image.adoc
View file

@ -1,24 +1,26 @@
= Creating a Product image
Anaconda supports several ways to load new code at runtime.
Passing `inst.updates=<url>` is one way to do this and is documented on the file:/anaconda/anaconda_updates.html[updates] page.
Passing `inst.updates=<url>` 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/`.