Experiences in the community

Just another WordPress.com weblog

Jigdo-jigsaw downloader -1

Hi all,
This would be a longish post about jigsaw and probably be broken in two or three parts.

While there are many many different methods to download files, barring rsync all of them i.e. bittorrent, http:// and segmented downloading don’t fulfill an important criteria. Downloading the image and keeping it up-to-date when the source image file changes every day or week and do it network efficiently i.e. spend the least time possible updating the image and using very less network resources (read that as bandwidth).

Before I begin, few people to thank. First of it is obviously the author of the tool Richard Atterer (missing in action it seems though for sometime), Peter Jay Salzman for his ‘Jigdo mini-howto‘ , the welcoming and genuine people of http://forums.debian.net who spent quite some time answering my somewhat ignorant and fumbling questions.

Requirements :-

a. A computer
b. Network connectivity
c. Jigdo installed .

c1. In most of the GNU/Linux distributions it would be either :-

$ sudo apt-get install jigdo-file

Debian-based or Debian-derived OR

$su -c 'yum install jigdo'

That’s for RPM based distributions .

c2. For windows download the .zip file from http://atterer.net/jigdo/

d. Preferably do the jigdo session in a separate clean directory and have enough space for the image you want to download and another 10% space for the working files which would be created as part of the download process.


The Process :-

 

The .jigdo File

 
A typical jigdo-lite session is something like below :-

$ jigdo-lite

Jigsaw Download "lite"

Copyright (C) 2001-2005 | jigdo@

Richard Atterer | atterer.net

Loading settings from `/home/shirish/.jigdo-lite'

-----------------------------------------------------------------

To resume a half-finished download, enter name of .jigdo file.

To start a new download, enter URL of .jigdo file.

You can also enter several URLs/filenames, separated with spaces,or enumerate in {}, e.g. `http://server/cd-{1_NONUS,2,3}.jigdo'
jigdo [http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/]: http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.jigdo
HTTP request sent, awaiting response... 206 Partial Content
Length: 3634 (3.5K), 1027 (1.0K) remaining [text/html]
Saving to: `index.html'

100%[+++++++++++++++============>] 3,634 --.-K/s in 0s

2010-12-26 03:39:23 (158 MB/s) - `index.html' saved [3634/3634]

Downloading .jigdo file

--2010-12-26 03:40:00-- http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.jigdo

Resolving cdimage.debian.org... 130.239.18.173, 130.239.18.163, 2001:6b0:e:2018::173, ...
Connecting to cdimage.debian.org|130.239.18.173|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 114752 (112K) [text/plain]
Saving to: `debian-testing-amd64-DVD-1.jigdo'

100%[======================================>] 1,14,752 62.2K/s in 1.8s

2010-12-26 03:40:08 (62.2 KB/s) - `debian-testing-amd64-DVD-1.jigdo' saved [114752/114752]

-----------------------------------------------------------------

Images offered by `http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.jigdo':

1: 'Debian GNU/Linux testing "Squeeze" - Official Snapshot amd64 DVD Binary-1 20101220-07:28 (20101220)' (debian-testing-amd64-DVD-1.iso)

Further information about `debian-testing-amd64-DVD-1.iso':

Generated on Mon, 20 Dec 2010 07:34:32 +0000

-----------------------------------------------------------------

If you already have a previous version of the CD you are
downloading, jigdo can re-use files on the old CD that are also
present in the new image, and you do not need to download them
again. Mount the old CD ROM and enter the path it is mounted under
(e.g. `/mnt/cdrom').
Alternatively, just press enter if you want to start downloading
the remaining files.
You can also enter a single digit from the list below to
select the respective entry for scanning:
Files to scan:

-----------------------------------------------------------------

The jigdo file refers to files stored on Debian mirrors. Please
choose a Debian mirror as follows: Either enter a complete URL
pointing to a mirror (in the form
`ftp://ftp.debian.org/debian/'), or enter any regular expression
for searching through the list of mirrors: Try a two-letter
country code such as `de', or a country name like `United
States', or a server name like `sunsite'.

Debian mirror [http://www.mirrorservice.org/sites/ftp.debian.org/debian/]:
Downloading .template file
--2010-12-26 03:40:12-- http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.template
Resolving cdimage.debian.org... 130.239.18.163, 130.239.18.173, 2001:6b0:e:2018::163, ...
Connecting to cdimage.debian.org|130.239.18.163|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15887752 (15M) [text/plain]
Saving to: `debian-testing-amd64-DVD-1.template'

100%[======================================>] 1,58,87,752 29.7K/s in 8m 43s

2010-12-26 03:49:01 (29.7 KB/s) - `debian-testing-amd64-DVD-1.template' saved [15887752/15887752]

-----------------------------------------------------------------
Merging parts from `file:' URIs, if any...
Found 0 of the 3856 files required by the template
Will not create image or temporary file - try again with different input files
--2010-12-26 03:49:10-- http://www.mirrorservice.org/sites/ftp.debian.org/debian/pool/main/x/xfonts-100dpi/xfonts-100dpi-transcoded_1.0.1_all.deb
Resolving http://www.mirrorservice.org... 212.219.56.134, 212.219.56.135, 212.219.56.138, ...
Connecting to http://www.mirrorservice.org|212.219.56.134|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7381250 (7.0M) [application/x-debian-package]
Saving to: `debian-testing-amd64-DVD-1.iso.tmpdir/www.mirrorservice.org/sites/ftp.debian.org/debian/pool/main/x/xfonts-100dpi/xfonts-100dpi-transcoded_1.0.1_all.deb'

61% [=======================> ] 45,52,185 29.4K/s eta 92s


Woooh! . That’s quite a handful there. I have to confess I do love the verbosity of wget as it makes easy to have a sense of where things are. At first it might not make all sense so let’s break it down into steps or pieces and start from there.

a. The first part of the process starts with running the command on the command-line and you get the following output :-

$ jigdo-lite

Jigsaw Download "lite"

Copyright (C) 2001-2005 | jigdo@

Richard Atterer | atterer.net

Loading settings from `/home/shirish/.jigdo-lite'

-----------------------------------------------------------------

The first four lines are simple for informational purposes. Where it starts being interesting is the fifth line where it says its loading settings from /home/shirish/.jigdo-lite.

Let’s see what this .jigdo-lite file has. It would be something similar to this :-


$cat .jigdo-lite]
jigdo='http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.jigdo
'debianMirror='http://www.mirrorservice.org/sites/ftp.debian.org/debian/'nonusMirror=''
tmpDir='.'
jigdoOpts='--cache jigdo-file-cache.db
'wgetOpts='--passive-ftp --dot-style=mega --continue --timeout=30'
scanMenu=''

Actually I have cheated here a bit. The first time you see the file the jigdo = ………….. (the first line) is empty or should be empty, because no values are known in them. Only in the subsequent times or runs would it be filled. The same would be the case of the ‘debianMirror’, the others should/would be same as above.

What I want to bring to your notice is all the file downloading and the beautiful summary you see of each download with progress bar and everything is done by wget. See the 7th line, the one which starts with ‘wgetOpts’ that command is the one which makes it possible. If one wants one can increase the timeout from 30 seconds to 60 seconds to whatever one is happy with. One can also do some changes with the tmpdir but I haven’t used or known use-cases where it can be useful just leave it as it is.

b. The second part/piece of the process is also easy enough to understand. It says :-


To resume a half-finished download, enter name of .jigdo file.
To start a new download, enter URL of .jigdo file.
You can also enter several URLs/filenames, separated with spaces,or enumerate in {}, e.g. `http://server/cd-{1_NONUS,2,3}.jigdo'
jigdo [http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/]: http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.jigdo
HTTP request sent, awaiting response... 206 Partial Content
Length: 3634 (3.5K), 1027 (1.0K) remaining [text/html]
Saving to: `index.html'
100%[+++++++++++++++++===========>] 3,634 --.-K/s in 0s
2010-12-26 03:39:23 (158 MB/s) - `index.html' saved [3634/3634]
Downloading .jigdo file
--2010-12-26 03:40:00-- http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.jigdo
Resolving cdimage.debian.org... 130.239.18.173, 130.239.18.163, 2001:6b0:e:2018::173, ...
Connecting to cdimage.debian.org|130.239.18.173|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 114752 (112K) [text/plain]
Saving to: `debian-testing-amd64-DVD-1.jigdo'
100%[======================================>] 1,14,752 62.2K/s in 1.8s
2010-12-26 03:40:08 (62.2 KB/s) - `debian-testing-amd64-DVD-1.jigdo' saved [114752/114752]

Ok, here we are presented with an option. The .jigdo file can be said to be similar to let’s a .torrent file or a .doc file . Its basically an encoded file which is and can be read only by the jigdo program. There might be other programs which know how to read it, parse it or look at it but I’m not aware of them. Anyways returning to the topic at hand it basically asks you whether you have already a downloaded .jigdo file (similar to a .torrent file) . If not then a URL from where it will download the .jigdo file and start another process. One can give either but as I’m quite a bit of a lazy guy I just gave the URL to it. See the ‘http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.jigdo’

That’s the one. Now of course, one is expected to know the site from where you want to download the .jigdo file. Now in this instance I am downloading a weekly DVD (4.3 GB) iso image of Debian ‘Squeeze’

1a. Here it goes and downloads the .jigdo file, interestingly though it also downloads an index.html
 

HTTP request sent, awaiting response... 206 Partial Content
Length: 3634 (3.5K), 1027 (1.0K) remaining [text/html]
Saving to: `index.html'
100%[+++++++++++++++=============>] 3,634 --.-K/s in 0s
2010-12-26 03:39:23 (158 MB/s) - `index.html' saved [3634/3634]

Ok here again I cheated a bit. Actually I had started with downloading and stopped before the index.html had downloaded. Hence you can see the little ‘ +’ signs and the 206 Partial Content remark. They both denote that a file had been partially downloaded.

b 1b.If we had already downloaded a jigdo-file the output would have been slightly different, something like this :-

$jigdo-lite

Jigsaw Download "lite"
Copyright (C) 2001-2005 | jigdo@
Richard Atterer | atterer.net
Loading settings from `/home/shirish/.jigdo-lite'

-----------------------------------------------------------------
To resume a half-finished download, enter name of .jigdo file.
To start a new download, enter URL of .jigdo file.
You can also enter several URLs/filenames, separated with spaces,
or enumerate in {}, e.g. `http://server/cd-{1_NONUS,2,3}.jigdo'
jigdo [http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.jigdo]:

Not downloading .jigdo file - `debian-testing-amd64-DVD-1.jigdo' already present

Anyways that is just another way of doing it.

c. Let’s carry on with what with the way I did or I liked :-

Downloading .jigdo file

--2010-12-26 03:40:00-- http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.jigdo

Resolving cdimage.debian.org... 130.239.18.173, 130.239.18.163, 2001:6b0:e:2018::173, ...
Connecting to cdimage.debian.org|130.239.18.173|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 114752 (112K) [text/plain]
Saving to: `debian-testing-amd64-DVD-1.jigdo'

100%[======================================>] 1,14,752 62.2K/s in 1.8s

2010-12-26 03:40:08 (62.2 KB/s) - `debian-testing-amd64-DVD-1.jigdo' saved [114752/114752]

This one is easy to explain. It simply has downloaded a file by the name ‘debian-testing-amd64-DVD-1.jigdo’ in your present working directory.

d. Then it goes on to say :-

Images offered by `http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.jigdo':

1: 'Debian GNU/Linux testing "Squeeze" - Official Snapshot amd64 DVD Binary-1 20101220-07:28 (20101220)' (debian-testing-amd64-DVD-1.iso)

Further information about `debian-testing-amd64-DVD-1.iso':

Generated on Mon, 20 Dec 2010 07:34:32 +0000

----------------------------------------------------------------

Again, easy to understand. It is just giving us some more information about the iso image. It parsed the .jigdo file and tells us the date and time when an image was put up for downloading. This is very important when you are tracking say weekly images as I do/want to as the name of each weekly is the same. Its only this information within the .jigdo file which tells me if I’m downloading the right iso image or not.

e. Now it again starts being a little interesting :-

If you already have a previous version of the CD you are
downloading, jigdo can re-use files on the old CD that are also
present in the new image, and you do not need to download them
again. Mount the old CD ROM and enter the path it is mounted under
(e.g. `/mnt/cdrom').
Alternatively, just press enter if you want to start downloading
the remaining files.
You can also enter a single digit from the list below to
select the respective entry for scanning:
Files to scan:

-----------------------------------------------------------------

As can be seen, it asks if there an old DVD or CD image which I want to re-use files from. In my specific use-case or in the case of some GNU/Linux distributions who may be doing daily or weekly downloads the possibility is many of the files remaining the same is high. The change in the .iso image maybe anything from 2~5% or even more depdependingending on time, frequency of changes, time taken by you running and updating the dailies/weeklies through jigdo and a combination of the above. Most of the time it doesn’t make sense to download a completely new image and one can reuse most of the files from the old iso image and just download the changes.
 

The .template File

 
But in our case, as we are completely new, we just press the ‘Enter’ button and by-pass it for this time.

f. The next part of the process is also pretty straight-forward :-

The jigdo file refers to files stored on Debian mirrors. Please
choose a Debian mirror as follows: Either enter a complete URL
pointing to a mirror (in the form
`ftp://ftp.debian.org/debian/'), or enter any regular expression
for searching through the list of mirrors: Try a two-letter
country code such as `de', or a country name like `United
States', or a server name like `sunsite'.

Debian mirror [http://www.mirrorservice.org/sites/ftp.debian.org/debian/]:
Downloading .template file
--2010-12-26 03:40:12-- http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.template
Resolving cdimage.debian.org... 130.239.18.163, 130.239.18.173, 2001:6b0:e:2018::163, ...
Connecting to cdimage.debian.org|130.239.18.163|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15887752 (15M) [text/plain]
Saving to: `debian-testing-amd64-DVD-1.template'

100%[======================================>] 1,58,87,752 29.7K/s in 8m 43s

2010-12-26 03:49:01 (29.7 KB/s) - `debian-testing-amd64-DVD-1.template' saved [15887752/15887752]

Here its asking us to name a debian mirror. You could name any mirror which hosts the packages, is geographically and network-wise easy, convenient and reliable. Because its so specific I used the one my Debian install mirror-test told me is the best for you. So I just clicked Enter here. It takes all of this information from /etc/apt/sources.list from your debian install and puts it in your ~/.jigdo-lite where the information can be re-used again and again.

It needs this information to download the .template file and starts downloading the files from the said server. In my specific case, the mirror does not host the specific .template file which jigdo is looking for.

Jigdo here is intelligent and hence it parses the ‘index.html’ file it downloaded before, finds where it can find the appropriate .template file it needs and downloads the same.

The .template is relatively a bigger file than the .jigdo file. It basically has the count of number of files, their md5sums (checksums), how the files have to be structured and basically how the .iso image has to be created in order to be burned later on either by jigdo itself or by some other tool.

g. Then it starts :-

Merging parts from `file:' URIs, if any...
Found 0 of the 3856 files required by the template
Will not create image or temporary file - try again with different input files
--2010-12-26 03:49:10-- http://www.mirrorservice.org/sites/ftp.debian.org/debian/pool/main/x/xfonts-100dpi/xfonts-100dpi-transcoded_1.0.1_all.deb
Resolving http://www.mirrorservice.org... 212.219.56.134, 212.219.56.135, 212.219.56.138, ...
Connecting to http://www.mirrorservice.org|212.219.56.134|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7381250 (7.0M) [application/x-debian-package]
Saving to: `debian-testing-amd64-DVD-1.iso.tmpdir/www.mirrorservice.org/sites/ftp.debian.org/debian/pool/main/x/xfonts-100dpi/xfonts-100dpi-transcoded_1.0.1_all.deb'
61% [=======================> ] 45,52,185 29.4K/s eta 92s

Now here it tries to see if any files from before are available . Because its the first time we are downloading, it doesn’t find anything as said by ‘ Found 0 of the 3856 files required by the template’.

This is what we have to achieve, we have to download 3856 files in order for the .iso to be complete.

Then it simply starts downloading the files needed from the mirror we had told .jigdo in part (f.) above.

h. Let’s now for a moment, open another tab in our favorite terminal emulator whether its GNOME-terminal emulator or some other or go to another Virtual Terminal Console and peek inside the same directory :-

03:48:59$ ls -l
total 15980
-rw-r--r-- 1 shirish shirish 114752 Dec 20 13:04 debian-testing-amd64-DVD-1.jigdo
-rw-r--r-- 1 shirish shirish 333658 Dec 26 03:40 debian-testing-amd64-DVD-1.jigdo.unpacked
-rw-r--r-- 1 shirish shirish 15887752 Dec 20 13:04 debian-testing-amd64-DVD-1.template
-rw-r--r-- 1 shirish shirish 3634 Dec 20 13:17 index.html
-rw-r--r-- 1 shirish shirish 16384 Dec 26 03:49 jigdo-file-cache.db

These are the minimum no. of files you should see in your whatever directory you are downloading if the .jigdo and the .template file have downloaded or are there successfully. They spawn the jigdo.unpacked and the jigdo-file-cache.db files. The index.html file is there as it was downloaded during part (b1a.) If these are present then some atleast we are on the right path.

i. But if you look closer at part (g.) you see these last few lines :-

Saving to: `debian-testing-amd64-DVD-1.iso.tmpdir/www.mirrorservice.org/sites/ftp.debian.org/debian/pool/main/x/xfonts-100dpi/xfonts-100dpi-transcoded_1.0.1_all.deb'
61% [=======================> ] 45,52,185 29.4K/s eta 92s

This .iso.tmpdir is created at that moment and can be seen like :-


03:49:03$ ls
debian-testing-amd64-CD-1.iso.list
debian-testing-amd64-CD-1.iso.tmpdir
debian-testing-amd64-CD-1.jigdo
debian-testing-amd64-CD-1.jigdo.unpacked
debian-testing-amd64-CD-1.template
index.html
jigdo-file-cache.db

As can be seen from above, two new files have been added to the list. First one is :-

a. ~.iso.list
b. ~.iso.tmp.dir

I have taken the liberty of putting ~ before the names as the names are long in themselves. So in all we have 7 files as of now.

i. Now we go back to the same instance/same terminal where jigdo is doing its work, it should continue to go down the list and download more files. After around 10 files we should see something like this :-


FINISHED --2010-12-26 03:57:50--
Downloaded: 10 files, 12M in 4m 23s (47.1 KB/s)
Found 10 of the 3856 files required by the template
Copied input files to temporary file `debian-testing-amd64-DVD-1.iso.tmp' - repeat command and supply more files to continue
--2010-12-26 03:58:57-- http://www.mirrorservice.org/sites/ftp.debian.org/debian/pool/main/i/iceweasel-l10n/iceweasel-l10n-ka_3.5.15+debian-1_all.deb
Resolving http://www.mirrorservice.org... 212.219.56.139, 212.219.56.153, 212.219.56.131, ...
Connecting to http://www.mirrorservice.org|212.219.56.139|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 168302 (164K) [application/x-debian-package]
Saving to: `debian-testing-amd64-DVD-1.iso.tmpdir/www.mirrorservice.org/sites/ftp.debian.org/debian/pool/main/i/iceweasel-l10n/iceweasel-l10n-ka_3.5.15+debian-1_all.deb'

100%[======================================>] 1,68,302 80.5K/s in 2.0s

2010-12-26 03:59:04 (80.5 KB/s) - `debian-testing-amd64-DVD-1.iso.tmpdir/www.mirrorservice.org/sites/ftp.debian.org/debian/pool/main/i/iceweasel-l10n/iceweasel-l10n-ka_3.5.15+debian-1_all.deb' saved [168302/168302]

--2010-12-26 03:59:04-- http://www.mirrorservice.org/sites/ftp.debian.org/debian/pool/main/d/dash/dash_0.5.5.1-7.4_amd64.deb
Reusing existing connection to http://www.mirrorservice.org:80.
HTTP request sent, awaiting response... 200 OK
Length: 107810 (105K) [application/x-debian-package]
Saving to: `debian-testing-amd64-DVD-1.iso.tmpdir/www.mirrorservice.org/sites/ftp.debian.org/debian/pool/main/d/dash/dash_0.5.5.1-7.4_amd64.deb'

99% [=====================================> ] 1,06,826 28.9K/s eta 0s

Now what’s interesting for us are these lines :-

FINISHED --2010-12-26 03:57:50--
Downloaded: 10 files, 12M in 4m 23s (47.1 KB/s)
Found 10 of the 3856 files required by the template
Copied input files to temporary file `debian-testing-amd64-DVD-1.iso.tmp' - repeat command and supply more files to continue

After the first 10 files are downloaded we get another file called ~.iso.tmp. Now let’s revisit the directory again and see what we got :-


$ ls
debian-testing-amd64-CD-1.iso.list
debian-testing-amd64-CD-1.iso.tmp
debian-testing-amd64-CD-1.iso.tmpdir
debian-testing-amd64-CD-1.jigdo
debian-testing-amd64-CD-1.jigdo.unpacked
debian-testing-amd64-CD-1.template
index.html
jigdo-file-cache.db

Cool, so now we have 8 files in the directory. Let’s get some more info. about the files, shall we :-

$ ls -l
total 4566880
-rw-r--r-- 1 shirish shirish 861876 Dec 26 03:53 debian-testing-amd64-DVD-1.iso.list
-rw-r--r-- 1 shirish shirish 4659246191 Dec 26 03:58 debian-testing-amd64-DVD-1.iso.tmp
drwxr-xr-x 3 shirish shirish 4096 Dec 26 03:59 debian-testing-amd64-DVD-1.iso.tmpdir
-rw-r--r-- 1 shirish shirish 114752 Dec 20 13:04 debian-testing-amd64-DVD-1.jigdo
-rw-r--r-- 1 shirish shirish 333658 Dec 26 03:52 debian-testing-amd64-DVD-1.jigdo.unpacked
-rw-r--r-- 1 shirish shirish 15887752 Dec 20 13:04 debian-testing-amd64-DVD-1.template
-rw-r--r-- 1 shirish shirish 3634 Dec 20 13:17 index.html
-rw-r--r-- 1 shirish shirish 16384 Dec 26 03:49 jigdo-file-cache.db

Now while I do wish I had used $ls -lh but anyways, it is easy to see that the biggest file in the whole directory is the

-rw-r--r-- 1 shirish shirish 4659246191 Dec 26 03:58 debian-testing-amd64-DVD-1.iso.tmp

It roughly translates to 4.3~4.4 GB . What happens is like this. When the files are first downloaded, they are downloaded to a holding directory called ~.iso.tmp.dir . When they are a collection of 10 files they are then moved to the ~.iso.tmp file. This saves moving data on the hdd and saves a bit of wear-and-tear of the hdd as well. The .iso.tmp file in turn has the data of the files you have downloaded and it fills the rest of the file with zeros or whatever (essentially making sure that in any case it will be possible to download the whole image.)

Now if all things go well, one just goes and sleeps or does some other things while jigdo does it work. I’m also going to stop now, the second part of the series will deal when jigdo is unable to download the whole thing in one session, either due to bad network issues, your ISP issues, bad mirror etc.

Single Post Navigation

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: