[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: woody ISOs for non-i386?



On Thu, Jul 26, 2001 at 12:27:05AM +1000, jason andrade wrote:
> On Wed, 25 Jul 2001, Richard Atterer wrote:
> > - getting rid of rsync. rsync is a cool program and works well for
> >   syncing images between mirrors, but it's not good to use for end
> >   users because it puts such a high load on the server. (Also,
> >   corporate firewalls often block the port.)
> 
> i would agree to a certain point - rsync is a great tool for
> intermirror stuff.. but it doesn't scale at all well - i believe it
> is on the todo list for rsync 3 if/when it gets developed.

AIUI there are patent issues once the rsync algorithm is reversed to
shift more of the work to the client. Grrr...

[If you want, I could dig out the relevant message from my archive of
the rsync list; an employee of the company holding the patent stated
his own, *unofficial* opinion that reversing the algorithm would
definitely violate the patent in their eyes, even though they might
not prosecute the violation.]

Also, the authors of rsync have been "maintaining" rather than
"developing" it for a long time now - no good sign for a V3...

> > jigdo by itself cannot generate the image. It's more like a
> > post-processing stage: The finished image is fed to jigdo which
> > generates the much smaller ".template" file, in which .deb package
> > contents are replaced with references to the package (via a
> > checksum). Using the template and your local Debian mirror, you
> > can recreate the image.
> 
> so the end user runs jigdo and points it at their closest mirror and
> it builds the image for em - much like PIK ?

Exactly! The way I imagine it, all the end user will ever see is a
small app which looks roughly like Netscape's SmartDownload tool.

Cheers,

  Richard

-- 
  __   _
  |_) /|  Richard Atterer     |  CS student at the Technische  |  GnuPG key:
  | \/¯|  http://atterer.net  |  Universität München, Germany  |  0x888354F7
  ¯ ´` ¯

Attachment: pgpeUOIlLOqsg.pgp
Description: PGP signature


Reply to: