Re: Update 2.2r3 images via rsync?
I do not have room for a full Debian mirror, so I do not have the sources for
the PIK on the local network. I will have to snag them from another Debian
mirror over the Net.
Given that information, I will use rsync to update my 2.2r3 ISOs to 2.2r4?
This is the way to go if I am interpreting the information correctly. My
conclusions presume that using PIK will xfer as much as a whole new rsync. So,
give rsync a chance to sort things out.
Any recommendations for block size?
flonesaw at longship dot net
> On Wed, 7 Nov 2001 email@example.com wrote:
> > Hi,
> > Concerning using the pseudo-image kit to update to the 2.2rev4 images...
> > I already have the 2.2rev3 images in place just as they were at the end of a
> > pseudo-image + rsynch build.
> > Wouldn't it be more efficient to update my 2.2r3 ISO images to 2.2r4 directly
> > using rsync (omitting the pseudo-image step)?
> you can try and find out.. on one image and let us know. my guess is you will
> at best get a 50% saving and likely 10-20%. worst case 1-5% saving.
> > If I already have a substantial amount of the CD contents here in my 2.2r3 ISO
> > images why do I want to download everything again with the pseudo image kit?
> i have a full debian mirror as well as debian-cd images. using PIK2, there was
> between 20-50M to download per ISO after building them locally.
> > Isn't this just what rsync was designed to do?
> to a certain extent. if all the packages are rebuilt (and recompressed) there
> is very little rsync can do about that within an ISO. it's block comparison
> system can't deal with that.
> > Maybe I don't understand what the pseudo-image kit is doing...
> assuming that if you're a debian-cd mirror, you're probably a full debian
> mirror too. this is not always the case of course, particularly for cdrom
> To UNSUBSCRIBE, email to firstname.lastname@example.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com