Lorax is a set of tools used to create bootable images.
Go to file
Robert Marshall 9543a46dac Keep fsfreeze in install environment (#1315468)
The latest POWER platform allows a host machine to configure guests
running in a different endian mode. Guests configured in this way may
have their bootloader configuration file corrupted after installation if
the file was not fully written to disk. The host machine would read the
journal and try to finish writing the file in the wrong endian mode.

Issuing an fsfreeze and unfreeze gives more assurance that the
configuration file is properly written before a reboot; this patch adds
fsfreeze to the installer runtime environment.

Related: rhbz#1315468
2016-09-08 12:13:30 -07:00
docs New lorax documentation - 25.12 2016-07-28 07:57:51 -07:00
etc Remove empty config files 2010-12-08 12:40:46 +01:00
rel-eng Automatic commit of package [lorax] release [25.14-1]. 2016-08-23 11:54:58 -07:00
share/templates.d/99-generic Keep fsfreeze in install environment (#1315468) 2016-09-08 12:13:30 -07:00
src Add ppc64le kernel path 2016-09-08 12:12:07 -07:00
tests Remove the removal of the eintr checker, which has been removed 2016-02-04 11:30:18 -05:00
utils Update things to make pylint 1.5.1 happy 2015-12-16 12:59:48 -08:00
.gitignore Clean up some pylint warnings 2015-05-15 17:11:20 -07:00
ANNOUNCE Added draft on initial announce email as I keep adding to it. 2008-10-06 09:51:01 -10:00
AUTHORS add wwoods to AUTHORS 2011-10-26 12:36:06 -04:00
COPYING Initial project description files imported. 2008-09-11 14:16:39 -10:00
lorax.spec Automatic commit of package [lorax] release [25.14-1]. 2016-08-23 11:54:58 -07:00
Makefile Use Sphinx to generate manpages 2016-03-21 14:21:56 -07:00
POLICY Update TODO and POLICY to reflect the current state of things 2012-01-06 14:41:21 -05:00
README Initial project description files imported. 2008-09-11 14:16:39 -10:00
requirements.txt Mock more modules for RTD 2015-04-09 11:01:20 -07:00
setup.py Update spec for python3 and add subpackages for lmc 2015-05-15 17:11:20 -07:00
TODO Update TODO and POLICY to reflect the current state of things 2012-01-06 14:41:21 -05:00

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>