Lorax is a set of tools used to create bootable images.
6f6af862c6
systemd uses /var/lib/systemd/random-seed to add entropy to /dev/urandom at boot time. During image creation this file is created, and if not removed everything using the image will be adding the same seed. This is only additional entropy, NOT a seed in the sense of a starting point for a PRNG, so it will be mixed with other entropy as the system runs. It isn't a good idea to use the same value everywhere so make sure it is removed in %post Resolves: rhbz#1258986 |
||
---|---|---|
docs | ||
etc | ||
rel-eng | ||
share | ||
src | ||
tests | ||
utils | ||
.gitignore | ||
ANNOUNCE | ||
AUTHORS | ||
COPYING | ||
lorax.spec | ||
Makefile | ||
POLICY | ||
README | ||
requirements.txt | ||
setup.py | ||
TODO |
I am the Lorax. I speak for the trees [and images]. Tree building tools such as pungi and revisor rely on 'buildinstall' in anaconda/scripts/ to produce the boot images and other such control files in the final tree. The existing buildinstall scripts written in a mix of bash and Python are unmaintainable. Lorax is an attempt to replace them with something more flexible. EXISTING WORKFLOW: pungi and other tools call scripts/buildinstall, which in turn call other scripts to do the image building and data generation. Here's how it currently looks: -> buildinstall * process command line options * write temporary yum.conf to point to correct repo * find anaconda release RPM * unpack RPM, pull in those versions of upd-instroot, mk-images, maketreeinfo.py, makestamp.py, and buildinstall -> call upd-instroot -> call maketreeinfo.py -> call mk-images (which figures out which mk-images.ARCH to call) -> call makestamp.py * clean up PROBLEMS: The existing workflow presents some problems with maintaining the scripts. First, almost all knowledge of what goes in to the stage 1 and stage 2 images lives in upd-instroot. The mk-images* scripts copy things from the root created by upd-instroot in order to build the stage 1 image, though it's not completely clear from reading the scripts. NEW IDEAS: Create a new central driver with all information living in Python modules. Configuration files will provide the knowledge previously contained in the upd-instroot and mk-images* scripts. -- David Cantrell <dcantrell@redhat.com>