Differences between revisions 5 and 6
Revision 5 as of 2006-06-22 17:10:13
Size: 1914
Editor: ALagny-109-1-2-101
Comment: Fix up according to comments from Daniel
Revision 6 as of 2006-06-22 17:27:25
Size: 1738
Editor: ALagny-109-1-2-101
Comment: cleanup
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:
{{{dsilvers: Would 'run-parts order' be a more useful description than 'ASCII order' ?}}}

{{{tfheen: no, it's in for f in *.squashfs; ... ; done in a C locale order. }}}


The live cd file system is currently one big lump which takes a while to generate as well as being inflexible. It should rather be an ordered list of squashfs-es that are mounted on top of each other.


The current method of building the live fs makes customising the live cd harder than it needs to. It also means building another live fs for the DVD images (with additional language packs or similar) will take a long time.

Use cases

  • John wants to create a customised live CD. He takes the base livefs and builds a custom squashfs with the packages he wants, then drops that into /casper and burns the whole structure to a CD.

  • Ubuntu wants to have a DVD image with more language packs than would typically fit on a CD. The livefs build process therefore creates a separate squashfs with just the language packs in and makes it available to the DVD build process.


Affects casper and to a smaller extent the live filesystem and live ISO image building process.

Design and implementation

  • casper will look at /casper/*.squashfs in ASCII order and mount all the squashfs-es there with unionfs. The topmost layer will be a persistent device or just a tmpfs in the same way it currently is.

  • and the live ISO build process is covered by


LiveCDStackedFileSystem (last edited 2008-08-06 16:28:27 by localhost)