b3dabdd2e0
With these templates if a package has installed files in /usr/share/lorax/product or /usr/share/lorax/updates/ they will be used to create product.img and/or updates.img which will be included in the images/ directory of the iso and of the final output tree. These can be used to customize the installation environment or provide updates. See README.product for current documentation. Related: rhbz#1202278
19 lines
966 B
Plaintext
19 lines
966 B
Plaintext
Lorax now supports creation of product.img and updates.img as part of the build
|
|
process. This is implemented using the installimg command which will take the
|
|
contents of a directory and create a compressed archive from it. The x86, ppc,
|
|
ppc64le and aarch64 templates all look for /usr/share/lorax/product/ and
|
|
/usr/share/lorax/updates/ directories while creating the final install tree. If
|
|
there are files in those directories lorax will create images/product.img
|
|
and/or images/updates.img
|
|
|
|
These archives are just like an anaconda updates image -- they are copied over
|
|
the top of the filesystem at boot time so that you can drop in files to add to
|
|
or replace anything on the filesystem.
|
|
|
|
Anaconda has several places that it looks for updates, the one for product.img
|
|
is in /run/install/product. For example, to add an installclass to Anaconda
|
|
you would put your custom class here:
|
|
|
|
/usr/share/lorax/product/run/install/product/pyanaconda/installclasses/custom.py
|
|
|