Re: Common Live CD base and generator

[p.carsten@arcor.de]

>   -  You write an adaptation of jigdo: it could get a .deb, unpack it 
> and put the files in the right place of the iso, eventually compressing 
> them.

A regular install of a .deb into the live CDs "chroot"
eviromnent, possibly into a mounted compressed fs.

>  For that jigdolivecd-file needs to know what deb contains what 
> file in the fs.

Maybe this is not neseccary:

A .tamplate is made from the base of a live cd where the largest part that is
the compressed fs file is left out (md5sumed can be ignored in the case of
personal live cds).

On the client side jigdo or a helper program first takes a list of packages
(tasks/meta-packages?) and installs the .debs into a mounted compressed fs
file of the same size that will fits into the CD .template afterwards.

This part is actually like a normal install, you can do it manualy and choose
what you want or use a more automated method to install into the
"master chroot" location. The difference from a regular install in these days
are things like the use of a init package with permanent automatic hardware
detection. (i.e. .debs that could be brought back into debian from existing
knoppix/morphix etc. as agreed earlier [1] and with news heard to come soon) 


But maybe even the the eltorito bootimage and initrd should be
fetched/created from regular packages, in this case the adapted jigdo would
probably be run in a mode that calls mkisofs at the end,
again as disussed at [2] and later.

Peter

[1] Re: Integrate Knoppix in Debian
http://lists.debian.org/debian-devel/2003/debian-devel-200311/msg01501.html

[2] Enlighten me about jigdo .. 
https://lists.berlios.de/pipermail/jigdo-user/2003-November/000141.html