-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
MW real image. The issue was not the load on the debian mirrors but on the
MW debian iso mirrors that kept the real isos available for rsyncing. This
MW rsync ate a lot of cputime.
And not to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
MW real image. The issue was not the load on the debian mirrors but on the
MW debian iso mirrors that kept the real isos available for rsyncing. This
MW rsync ate a lot of cputime.
And not to
On Fri, 14 Nov 2003, Delian Krustev wrote:
On Friday 14 November 2003 12:41, Richard Atterer wrote:
An rsync-based scheme (whose design inspired that of jigdo) was used in the
old days, the pseudo image kit (PIK). The use of rsync turned out to be
problematic (too much load on the server),
On Fri, 14 Nov 2003, Delian Krustev wrote:
On Friday 14 November 2003 12:41, Richard Atterer wrote:
An rsync-based scheme (whose design inspired that of jigdo) was used in the
old days, the pseudo image kit (PIK). The use of rsync turned out to be
problematic (too much load on the server),
On Fri, Nov 14, 2003 at 01:31:05AM +0200, Delian Krustev wrote:
I wonder what this hype about jigdo is ..
Er - it's not intended to sound like hype, jigdo is just (IMVHO as its
author) better suited for Debian CD image distribution than other
solutions.
1.get two files for an image - .jigdo,
First, I'm glad the response is from You, the jigdo author .. right ?
On Friday 14 November 2003 12:41, Richard Atterer wrote:
1. the templates are BIG - as I see from 5 to 20 MB for woody
(600+ MBs for i386 sid, but I suppose the maintainer of those unofficial
templates has messed the
On Fri, Nov 14, 2003 at 02:05:03PM +0200, Delian Krustev wrote:
First are You sure the exact reconstruction of the iso is not possible with
mkisofs ? What are your concerns, different versions of mkisofs producing
different isoimages (e.g. this iso made with mkisofs-20031114cvs in the
image
On Friday 14 November 2003 14:59, Richard Atterer wrote:
On Fri, Nov 14, 2003 at 02:05:03PM +0200, Delian Krustev wrote:
First are You sure the exact reconstruction of the iso is not possible
with mkisofs ? What are your concerns, different versions of mkisofs
producing different isoimages
On Fri, Nov 14, 2003 at 01:31:05AM +0200, Delian Krustev wrote:
I wonder what this hype about jigdo is ..
Er - it's not intended to sound like hype, jigdo is just (IMVHO as its
author) better suited for Debian CD image distribution than other
solutions.
1.get two files for an image - .jigdo,
First, I'm glad the response is from You, the jigdo author .. right ?
On Friday 14 November 2003 12:41, Richard Atterer wrote:
1. the templates are BIG - as I see from 5 to 20 MB for woody
(600+ MBs for i386 sid, but I suppose the maintainer of those unofficial
templates has messed the
On Fri, Nov 14, 2003 at 02:05:03PM +0200, Delian Krustev wrote:
First are You sure the exact reconstruction of the iso is not possible with
mkisofs ? What are your concerns, different versions of mkisofs producing
different isoimages (e.g. this iso made with mkisofs-20031114cvs in the
image
On Friday 14 November 2003 14:59, Richard Atterer wrote:
On Fri, Nov 14, 2003 at 02:05:03PM +0200, Delian Krustev wrote:
First are You sure the exact reconstruction of the iso is not possible
with mkisofs ? What are your concerns, different versions of mkisofs
producing different isoimages
Hi,
I wonder what this hype about jigdo is ..
What jigdo(lite) actually does(if I got it right ..):
1.get two files for an image - .jigdo, .template
2.download the listed files in the above two from a listed mirror using wget
3.run mkisofs to create the image
what I see at first glance:
1.
Hi,
I wonder what this hype about jigdo is ..
What jigdo(lite) actually does(if I got it right ..):
1.get two files for an image - .jigdo, .template
2.download the listed files in the above two from a listed mirror using wget
3.run mkisofs to create the image
what I see at first glance:
1.
14 matches
Mail list logo
