On Thu, May 23, 2013 at 6:26 PM, Christopher Covington <cov@codeaurora.org> wrote:
> Out of curiosity where is the code that outputs the root file system
> for a tarball or ext3 img?

The decision to generate these images is made in conf/site.conf which is
generated by openembedded/meta-aarch64/scripts/init.sh. (In my opinion, it'd
be nice if site.conf could be put under revision control itself.) Anyhow,
openembedded-core/meta/classes/image_types.bbclass has the filesystem
generation commands. Ext2 support, for example:

http://git.openembedded.org/openembedded-core/tree/meta/classes/image_types.bbclass#n144

note that if you *just* need to alter/tweak the generated ext3 (or any other image type) that is already generated by OE, it might be simple to 'post process' the image using something along these lines:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor/tree/classes/deploy-license-manifest.bbclass

basically, the IMAGE_POSTPROCESS_COMMAND is a list of python scripts that is executed immediately after the 'image' is generated, so at that point you can prepare it for the Foundations model.