Re: jigdo for debian-live images ? (was: Debian mirrors: ftp.coe.psu.ac.th)
On Sun, Sep 27, 2009 at 10:39:37PM +0200, Diederik de Haas wrote:
> On 2009-09-27 Simon Paillard wrote:
> > Hi debian-live,
> > In short: what is the similar (and easy) wat to build images as jigdo
> > does ?
> Can you explain more about the reason(s) to use jigdo to update the live-images?
No, not using jigdo for update live-image, but is there any template files
to build live images identical to ones mirroring at
We are mirroring debian, debian-volatile, security, and backports here
at the moment, and trying to proper mirror debian-cd too. But using the same
mechanism for other archives with debian-cd (rsync) seems not appropriate.
Since it means download almost everything for next stable cd image release.
We can reduce the traffic a lot for those release isos, by download only
.jigdo and .template files and create isos locally (since we already have
debian archive here) using jigdo-lite. And we will have the identical isos
with the master mirror without download every iso files.
Are there any templates that we can do the same with live-cd/live-usb
> I think that jigdo is (far) less suited to updating live-images then it is to installer-images,
> since installer-images contain a lot less and bigger files, namely a bunch of .deb files, then a live-
> images does.
> A live-image is basically a normal (debian) system, which consists of a whole bunch of small(er)
> files, but compressed + some files to set it up.
> I've recently build a live image myself (sid, kde4.3.1) which is 534MB in size, but when I extract
> that it turns into 60839 files and 6976 folders.
> So when you want to update that with jigdo it'll have to check 60839 files and update all the
> different once.
> My experience with jigdo* learns me that connecting to the server to retrieve a file takes by far the
> most time, the download itself is quite swift. With soo many files, that can take quite a while (to
> update a couple of MBs?).
> On the other hand, bittorrent seems quite appropriate for this and I wouldn't mind that being
> stimulated more. It gives the users speedy (most of the time) downloads, while it doesn't drain on
> debian's bandwidth.
> I'm currently seeding debian-live-kde_4.3.0-i386.iso (via http://pkg-
> kde.alioth.debian.org/kde4livecd.html), but it's a 'shame' that in the trackers I only find
> torrentbox.com and thepiratebay.org and not debian.org.
> And if Debian Live is meant to make official debian live-images, it would help if it gets a more
> prominent place so that ppl can find (and use) it more.
> And to answer your original question:
> You need to unpack the iso, extract the squash file system from it and unpack that, remove the squash
> file system file, update the files from the squashfs file and pack that up again and construct the iso
> with the updated squashfs file.
> is a good place to start and with method 1, 'replace' the chroot steps with the jigdo updates.
> * When a new stable DVD images comes available, I'll update it with jigdo feeding it my .iso/DVD and
> let it generate a new .iso file and then I download the .torrent file and point that to the existing
> .iso file, so it'll check it and starts seeding since it's already fully up-to-date.