summaryrefslogtreecommitdiff
path: root/systems/cross-bootstrap-system-armv5l-generic.morph
diff options
context:
space:
mode:
authorSam Thursfield <sam.thursfield@codethink.co.uk>2015-12-23 14:31:52 +0000
committerPaul Sherwood <paul.sherwood@codethink.co.uk>2016-10-07 17:58:13 +0000
commit5bca5fc3e8215601d1e2d33ce31f6a41c4bcfcc9 (patch)
treed56cb8d83a4ee82dd2ac6ebced7c007892573782 /systems/cross-bootstrap-system-armv5l-generic.morph
parent50e5abede697ca0cfbfce46e28f9cb7775762746 (diff)
downloaddefinitions-5bca5fc3e8215601d1e2d33ce31f6a41c4bcfcc9.tar.gz
Add ostree.write deployment extension
This is a simple deployment extension to write the results of a Baserock build to an OSTree repo. See ostree.write.help for more information. The Baserock reference systems contain static device nodes, which are not supported by OSTree, and are obsolete on Linux systems. To work around this problem, I added a strip-device-nodes.configure extension. The systems should still work the same as devtmpfs will create the device nodes. I've tested this by deploying minimal-system-x86_64 to an OSTree repo, then checking it out into a temporary directory, creating a read-only bind-mount of the temporary directory and chrooting then into it. This is only going to be useful for containers systems and chroots for the time being. We would need to make some quite major changes to the Baserock reference systems to enable deployment to VMs or bare metal using OSTree. Change-Id: I8556139d118da759360cdc1ce998590b1f50b644
Diffstat (limited to 'systems/cross-bootstrap-system-armv5l-generic.morph')
0 files changed, 0 insertions, 0 deletions