From 6acf489ffd59ef5213ddc7d8d3836bc499ca9d3a Mon Sep 17 00:00:00 2001 From: "Brian C. Lane" Date: Wed, 2 Dec 2015 13:22:44 -0800 Subject: [PATCH] Update docs for product.img Make it clear that the contents of product.img and updates.img comes from the install root, not from the build host's filesystem. --- docs/product-images.rst | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/docs/product-images.rst b/docs/product-images.rst index 5ad6cd81..9b75afd8 100644 --- a/docs/product-images.rst +++ b/docs/product-images.rst @@ -2,12 +2,15 @@ Product and Updates Images ========================== 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 -- their contents are copied over the top of the filesystem at boot time so that you can drop in