<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
<span>
<style type="text/css">blockquote {color: navy !important; background-color: RGB(245,245,245) !important; padding: 0 15 10 15 !important; margin: 15 0 0 0; border-left: #1010ff 2px solid;} blockquote blockquote {color: maroon !important; background-color: RGB(235,235,235) !important; border-left-color:maroon !important} blockquote blockquote blockquote {color: green !important; background-color: RGB(225,225,225) !important; border-left-color:teal !important} blockquote blockquote blockquote blockquote {color: purple !important; background-color: RGB(215,215,215) !important; border-left-color: purple !important} blockquote blockquote blockquote blockquote blockquote {color: teal !important; background-color: RGB(205,205,205) !important; border-left-color: green !important}</style><i><b>Andre
Robatino <a class="moz-txt-link-rfc2396E" href="mailto:andre@bwh.harvard.edu"><andre@bwh.harvard.edu></a></b></i> wrote on 04/30/2010
3:13:26 PM +0450:</span><br>
<blockquote
style="border-left: 2px solid rgb(16, 16, 255); color: navy; background-color: rgb(245, 245, 245); padding-left: 15px;"
cite="mid:4BDAB44E.9080603@bwh.harvard.edu" type="cite">
<pre wrap="">On 04/30/2010 06:25 AM, Hedayat Vatankhah wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Well, I'm not going to insist on providing jigdo. However, the situation
in my mind is this one: I've downloaded Fedora 13 Beta DVD iso
previously and installed it on my system. Then, I've updated my system
regularly (using yum presto) and I use yum's "keepcache=1" option. So,
my Fedora Beta DVD iso + cached updated rpms would provide a
considerable number of files available in the next DVD iso; so if jigdo
is available I would probably be able to create the next iso without
downloading many rpm packages.
Certainly, the efficiency in this case depend on the installation. A
minimal installation will not have many rpms and so will not receive new
versions of most rpms when updating.
</pre>
</blockquote>
<pre wrap="">
That's a good point - if many of the updated RPMs in the new ISO have
already been downloaded and cached, then jigdo/rsync/zsync looks much
better, since most if not all of the exact RPMs in the new ISO are
already available. If rsync or zsync were available, you could get the
same benefit as jigdo by concatenating your old ISO and all of your new
cached RPMs together into a single large file, and running rsync/zsync
on that to convert it into the new ISO. Unfortunately, rsync runs on
the server, and turned out to be a resource hog, so it's not currently
used for development images. Zsync runs on the client so shouldn't have
this problem. Unfortunately, it's not available in Fedora yet. See
<a class="moz-txt-link-freetext" href="http://kparal.wordpress.com/2009/09/01/zsync-transfer-large-files-efficiently/">http://kparal.wordpress.com/2009/09/01/zsync-transfer-large-files-efficiently/</a>
<a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=490140">https://bugzilla.redhat.com/show_bug.cgi?id=490140</a>
<a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=495310">https://bugzilla.redhat.com/show_bug.cgi?id=495310</a>
Zsync would also be perfect for converting between different install
disc sets (currently the DVD and the CD set) since the packages are
exactly the same. It can also be used to efficiently convert from the
first disc in either set to the netinst disc. So I'd certainly like to
see it in Fedora.
</pre>
</blockquote>
Yes, I would certainly prefer zsync if it was available (it would be
even better than jigdo, as it does not even need the exact rpms). <br>
<br>
</body>
</html>