almalinux/lorax
13
0
Fork 0
Code Issues Pull Requests Releases Activity

Update docs for product.img (#1272361)

Browse Source 
Make it clear that the contents of product.img and updates.img comes
from the install root, not from the build host's filesystem.

Resolves: rhbz#1272361
This commit is contained in:
Brian C. Lane 2016-02-19 16:41:58 -08:00
parent cc715caaf9
commit 2795b08b1c
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.product
View File

@ -1,10 +1,13 @@
Lorax now supports creation of product.img and updates.img as part of the build 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 process. This is implemented using the installimg template command which will
contents of a directory and create a compressed archive from it. The x86, ppc, take the contents of a directory and create a compressed archive from it. The
ppc64le and aarch64 templates all look for /usr/share/lorax/product/ and directory must be created by one of the packages installed by
/usr/share/lorax/updates/ directories while creating the final install tree. If runtime-install.tmpl or by passing ``--installpkgs <pkgname>`` to lorax at
there are files in those directories lorax will create images/product.img runtime. The x86, ppc, ppc64le and aarch64 templates all look for
and/or images/updates.img /usr/share/lorax/product/ and /usr/share/lorax/updates/ directories in the
install chroot 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 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 the top of the filesystem at boot time so that you can drop in files to add to