At 01:42 PM 1/2/2004 -0500, you wrote:
Does there exist a set of examples for making the jigdo tools
actually produce iso images instead of downloading 4.5 gig of
file parts and then crashing with no explanation
Well, yes. The Peter Jay Salzman HOWTO has examples.
? I mean,
it _seems_ like a good
At 01:42 PM 1/2/2004 -0500, you wrote:
Does there exist a set of examples for making the jigdo tools
actually produce iso images instead of downloading 4.5 gig of
file parts and then crashing with no explanation
Well, yes. The Peter Jay Salzman HOWTO has examples.
? I mean,
it _seems_ like a goo
On Fri, Jan 02, 2004 at 01:42:59PM -0500, [EMAIL PROTECTED] wrote:
> All I ever end up with is enormous files that
> jigdo refuses to use the next pass:
I vaguely remember such a problem existed, but that was long ago - are you
using the latest version of jigdo? Under Windows or Linux?
Cheers,
On Fri, Jan 02, 2004 at 01:42:59PM -0500, [EMAIL PROTECTED] wrote:
> All I ever end up with is enormous files that
> jigdo refuses to use the next pass:
I vaguely remember such a problem existed, but that was long ago - are you
using the latest version of jigdo? Under Windows or Linux?
Cheers,
Does there exist a set of examples for making the jigdo tools
actually produce iso images instead of downloading 4.5 gig of
file parts and then crashing with no explanation? I mean,
it _seems_ like a good idea to only get the parts that have
changed, but I cannot find any clear explanation for w
Does there exist a set of examples for making the jigdo tools
actually produce iso images instead of downloading 4.5 gig of
file parts and then crashing with no explanation? I mean,
it _seems_ like a good idea to only get the parts that have
changed, but I cannot find any clear explanation for w
6 matches
Mail list logo
