From 2795b08b1c2a669bc213aec1ac495182fff015a5 Mon Sep 17 00:00:00 2001 From: "Brian C. Lane" Date: Fri, 19 Feb 2016 16:41:58 -0800 Subject: [PATCH] Update docs for product.img (#1272361) 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 --- README.product | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/README.product b/README.product index ec6e516f..33b0fc9d 100644 --- a/README.product +++ b/README.product @@ -1,10 +1,13 @@ 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 +process. This is implemented using the installimg template command which will +take the contents of a directory and create a compressed archive from it. The +directory must be created by one of the packages installed by +runtime-install.tmpl or by passing ``--installpkgs `` to lorax at +runtime. The x86, ppc, ppc64le and aarch64 templates all look for +/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 the top of the filesystem at boot time so that you can drop in files to add to