Re: JTE (Jigdo Template Export) v1.0

2004-06-09 Thread Steve McIntyre
On Thu, Jun 10, 2004 at 12:16:23AM +0200, Richard Atterer wrote: >On Wed, Jun 09, 2004 at 05:34:03PM +0100, Steve McIntyre wrote: >> Unfortunately, I don't see us (quite) getting that far. To generate the >> md5 of the full image file (which is kind of useful), we need to read all >> of the data th

Re: JTE (Jigdo Template Export) v1.0

2004-06-09 Thread Richard Atterer
On Wed, Jun 09, 2004 at 05:34:03PM +0100, Steve McIntyre wrote: > Unfortunately, I don't see us (quite) getting that far. To generate the > md5 of the full image file (which is kind of useful), we need to read all > of the data through anyway. You can't simply lump together multiple md5 > chunks.

Re: JTE (Jigdo Template Export) v1.0

2004-06-09 Thread George Danchev
On Wednesday 09 June 2004 19:21, Richard Atterer wrote: > On Wed, Jun 09, 2004 at 05:35:10PM +0200, Santiago Garcia Mantinan wrote: > > Richard: I remember that you were about to put out a new version of jigdo > > that could help in this, how is this going? > > It's on my TODO list, but I'm afraid

Re: JTE (Jigdo Template Export) v1.0

2004-06-09 Thread Steve McIntyre
On Wed, Jun 09, 2004 at 05:35:10PM +0200, Santiago Garcia Mantinan wrote: >On Jun 07 2004, Richard Atterer wrote: >> Yes, but once you can use the cache, mkisofs needn't even read the file >> data anymore. It could just skip over the file, output the filename to the >> .jte and leave the rest to ji

Re: JTE (Jigdo Template Export) v1.0

2004-06-09 Thread Richard Atterer
On Wed, Jun 09, 2004 at 05:35:10PM +0200, Santiago Garcia Mantinan wrote: > Richard: I remember that you were about to put out a new version of jigdo > that could help in this, how is this going? It's on my TODO list, but I'm afraid I haven't found the time yet to work on it. :-/ Richard --

Re: JTE (Jigdo Template Export) v1.0

2004-06-09 Thread Santiago Garcia Mantinan
On Jun 07 2004, Richard Atterer wrote: > Yes, but once you can use the cache, mkisofs needn't even read the file > data anymore. It could just skip over the file, output the filename to the > .jte and leave the rest to jigdo-file. I can imagine that image creation > would be a matter of 30 seconds

Re: JTE (Jigdo Template Export) v1.0

2004-06-07 Thread Richard Atterer
On Mon, Jun 07, 2004 at 04:49:00PM +0100, Steve McIntyre wrote: > On Mon, Jun 07, 2004 at 05:00:04PM +0200, Richard Atterer wrote: > >Something like #2 was my favourite: Write a special .iso image, but omit > >the file data from it, just embed information about the names of files > >which were omit

Re: JTE (Jigdo Template Export) v1.0

2004-06-07 Thread Steve McIntyre
On Mon, Jun 07, 2004 at 05:00:04PM +0200, Richard Atterer wrote: >On Mon, Jun 07, 2004 at 02:02:24PM +0100, Steve McIntyre wrote: >> 1. Modify jigdo so it knows about the internals of ISO images and can >>efficiently scan them (bad, not very generic for jigdo) >> >> 2. Write a helper tool to d

Re: JTE (Jigdo Template Export) v1.0

2004-06-07 Thread Richard Atterer
On Mon, Jun 07, 2004 at 02:02:24PM +0100, Steve McIntyre wrote: > 1. Modify jigdo so it knows about the internals of ISO images and can >efficiently scan them (bad, not very generic for jigdo) > > 2. Write a helper tool to dump extra information for jigdo to use >alongside the ISO image (h

JTE (Jigdo Template Export) v1.0

2004-06-07 Thread Steve McIntyre
Guys (especially Richard), I've been looking for a while at ways to make jigdo run faster when generating template files from iso images. (See http://lists.debian.org/debian-cd/2003/12/msg00041.html for my original mail). The core problem is that once we have an ISO image, jigdo essentially has to