Launchpad Entry: https://launchpad.net/distros/ubuntu/+spec/larger-livefs
Packages affected: livefs build script, cdimage/debian-cd
As of Ubuntu 6.06 LTS, an identical live filesystem is used on Ubuntu DVDs and CDs. Since space on the CD is limited, this filesystem omits translations and language support infrastructure for many languages. These packages should be available on the DVD, where more space is available.
Note that the casper side of this will Just Work when https://launchpad.net/distros/ubuntu/+spec/live-cd-stacked-filesystems is done.
Some less-used languages have millions of potential users too. They should be able to use the live DVD in their native tongue without having to resort to custom live CDs or similar solutions.
- Peter is a Swedish user who would like to try Ubuntu. Since Swedish isn't a common enough language to make it onto the install CDs, he downloads the live DVD and tries out Ubuntu in Swedish.
Affects the live filesystem and live ISO build process.
Make livecd.sh build stacked file systems by mounting the previously built file systems and then installing the new set of packages. We will need a live-dvd seed or something similar to decide what goes onto the live DVD filesystem.
livecd.sh needs to build the language pack/DVD live fs on top of the regular squashfs and make that available beside the regular livefs.
The ISO building process currently wgets the live filesystem image from the buildd for each architecture, and places them in /casper/filesystem.squashfs on the ISO image. Following ["LiveCDStackedFileSystem"], it will be changed to wget base, desktop, and live stacked filesystems, and place them in numerically-prefixed files under /casper, e.g. /casper/05base.squashfs, /casper/10desktop.squashfs, and /casper/15live.squashfs. To deal with this specification, it will be changed for DVD builds to wget the language pack filesystem image as well and place it in e.g. /casper/20langpacks.squashfs on the ISO image. If no language pack filesystem image is available, it will degrade to using only the normal live filesystem images.
What could go wrong and how to handle it?
This spec depends on the live-cd-stacked-filesystem spec which has a certain risk associated with it. If we are unsuccessful in implementing the live-cd-stacked-filesystem spec, this spec can still be solved by just building a very large live fs. We really want to avoid that as it will require a lot more resources than a stacked file system approach, but is mentioned here for completeness