LiveCDStackedFileSystem

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2006-06-07 13:15:48 →
Size: 1390
Editor: 92
Comment: Initial framework
← Revision 2 as of 2006-06-22 16:03:14 → ⇥
Size: 1606
Editor: ALagny-109-1-2-101
Comment: Draft
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 * '''Packages affected''':  * '''Packages affected''':  casper
Line 19: Line 19:
Line 23: Line 24:
== Design == To be included in Edgy Eft.
Line 25: Line 26:
== Implementation == == Design and implementation ==
Line 27: Line 28:
=== Code ===  * 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.
Line 29: Line 30:
=== Data preservation and migration ===

== Outstanding issues ==

== BoF agenda and discussion ==		  * livecd.sh is covered by https://launchpad.net/distros/ubuntu/+spec/livefs-build-speedups

Summary

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.

Rationale

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 on and burns it to a CD.
  • Ubuntu wants to have a DVD image with more language packs than what there's room for on a CD. The livefs build process therefore creates a separate squashfs with just the language packs on and makes it available to the DVD build process.

Scope

To be included in Edgy Eft.

Design and implementation

CategorySpec

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