LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2002-08-20 20:41:01 +00:00
parent 27629d10d8
commit 9ea21f44e1
4 changed files with 146 additions and 72 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

212
LDP/howto/docbook/Debian-Jigdo.sgml
View File

@ -16,7 +16,8 @@
</affiliation>
</author>
<pubdate>v0.108, 2002-07-31</pubdate>
<!-- year-month-day -->
<pubdate>v0.113, 2002-08-11</pubdate>
<copyright>
<year>2001</year>
@ -48,44 +49,6 @@
<sect1 id="administrata"><title>Administrata</title>
<sect2 id="acknowledgements"><title>Acknowledgements</title>
<para>Originally, I was going to thank the author of jigdo, <ulink url="mailto:atterer@debian.org">Richard
Atterer</ulink>, simply for writing jigdo. Anyone who has ever tried to use Debian's PIK (or worse, downloaded enitre
Debian ISOs) will know why. However, my thanks needs to go further. This HOWTO started out as some webpages I wrote
about my experience with jigdo. Richard took the time to email me extensive corrections, clarifications and answers to
questions I still had about jigdo. In the process of updating the web pages and their transformation into a
HOWTO, he has read my work many times. Richard is obviously a developer who not only cares
about his work, but cares about the people who use it. Sadly, this is something that is becoming less common in this busy
world we live in. Thanks, Richard, and keep up the excellent work.</para>
<para>I would like to thank Conrad Wood <email>cnw@conradwood.net</email> for translating this mini-HOWTO. I feel honored
that Conrad found my words worthy of his time and effort.</para>
</sect2>
<sect2 id="version"><title>Latest Version And Translations</title>
<para>Conrad Wood <email>cnw@conradwood.net</email> has been kind enough to make a German translation of this mini-HOWTO
available. It will be available at linuxdoc.org shortly, but for now you can download it from <ulink
url="http://www.dirac.org/linux/debian/">http://www.dirac.org/linux/debian/</ulink>.</para>
<para>If you would like to translate this HOWTO to another language, please contact me at <email><ulink
url="mailto:p@dirac.org">p@dirac.org</ulink></email>. As of 24 July 2002, there is a Portuguese translation in the works,
but it's not available yet.</para>
<para>The latest stable version can be found at The Linux Documentation Project: <ulink
url="http://linuxdoc.org/docs.html">http://linuxdoc.org/docs.html</ulink> in the mini-HOWTO section. If you want to see
the work in progress (it's can be pretty ugly if you catch me before I use a spellchecker) you can download the "bleeding
edge" version of this document from my own pages at <ulink
url="http://www.dirac.org/linux/debian/jigdo">http://www.dirac.org/linux/debian</ulink>.</para>
</sect2>
<sect2 id="authorship"><title>Authorship and Copyright</title>
@ -101,6 +64,61 @@
</sect2>
<sect2 id="acknowledgements"><title>Acknowledgements</title>
<para>Originally, I was going to thank the author of jigdo, <ulink url="mailto:atterer@debian.org">Richard
Atterer</ulink>, simply for writing jigdo. Anyone who has obtained Debian ISOs by other means will know why. However, my
thanks needs to go further. This HOWTO started out as some webpages I wrote about my experience with jigdo. Richard took
the time to email me extensive corrections, clarifications and answers to questions I had about jigdo. Since then, he has
read my work many times. Richard is a developer who not only cares about his work, but also about the people who use it.
Sadly, this is becoming less common in this busy world we live in. Thanks, Richard!
work.</para>
<para>I'd also like to thank <ulink url="mailto:cnw@conradwood.net">Conrad Wood</ulink>, <ulink
url="mailto:mello@ajato.com.br">Elcio Mello</ulink> and <ulink url="mailto:mramos@montevideo.com.uy">Marcelo Ramos</ulink>
for translating this mini-HOWTO. I feel totally honored that they have found my words worthy of their time and effort.
Thanks, guys!</para>
</sect2>
<sect2><title>Comments and Corrections</title>
<para>I care a great deal about the people who use this document. Even mini-HOWTOs take a long time to write, and I
wouldn't have invested so much effort into something people don't understand. If you have comments, corrections or
suggestions, even in matters like writing style, don't hesitate to email me. As long as I'm not totally swamped by my
PhD, I'll do my best to respond to each email I receive about this mini-HOWTO.</para>
</sect2>
<sect2 id="version"><title>Latest Version And Translations</title>
<para>Conrad Wood <email>cnw@conradwood.net</email> has translated this HOWTO to German.</para>
<para>Elcio Mello <email>mello@ajato.com.br</email> has translated this HOWTO to Portuguese.</para>
<para>Marcelo Ramos <email>mello@ajato.com.br</email> has translated this HOWTO to Spanish.</para>
<para>The translations are available from <ulink url="http://www.dirac.org/linux/debian/jigdo"
>http://www.dirac.org/linux/debian/jigdo</ulink>. See <xref linkend="disacknowledgements">.</para>
<para>The stable English version can be found at The Linux Documentation Project: <ulink
url="http://tldp.org/docs.html">http://tldp.org/docs.html</ulink> in the mini-HOWTO section. If you want to see the work
in progress, you can get the "bleeding edge" version from <ulink
url="http://www.dirac.org/linux/debian/jigdo">http://www.dirac.org/linux/debian</ulink>. If you'd like to translate this
mini-HOWTO to another language, please contact me at <email><ulink
url="mailto:p@dirac.org">p@dirac.org</ulink></email>.</para>
</sect2>
</sect1>
@ -117,7 +135,7 @@
time.</para>
<para>Another way of getting a set of Debian CDs is to burn your own set. This entails first obtaining an ISO image and
<para>Another way of getting a set of Debian CDs is to burn your own set. This first entails obtaining an ISO image and
then burning that ISO image to a blank CD. Before jigdo, there were two ways of creating Debian CDs:</para>
@ -140,7 +158,7 @@
sites, and their bandwidth can't support everyone who wants Debian ISOs. For example, fsn.hu has reportedly saturated
the connection of its provider. The outgoing traffic reaches a few terabytes per month!</para>
<para>In addition, Debian testing and unstable get updated often. Your ISOs will become outdated the same day you
<para>In addition, Debian testing and unstable get updated often. Your ISOs may become outdated the same day you
download them unless you find some sneaky way of updating them like mounting the ISO on a loopback device and using rsync
(which is what the PIK does). So if you want up-to-date ISO images, you must download a new set of ISO images every day.
Clearly, this is not the way you want to obtain Debian ISOs!</para>
@ -155,9 +173,9 @@
<sect2 id="whynotusethewholepik"><title>Why Not Use The Pseudo Image Kit (PIK)?</title>
<para>The PIK addresses the problems of downloading entire ISO images. The downloads are fast, and the PIK uses rsync to
update only those portions of an ISO image that need to be updated, so it's an efficient way of keeping your ISO set
up-to-date. However, there are some hefty problems with the PIK:</para>
<para>The PIK addresses most of the problems of downloading entire ISO images. The downloads are fast, and the PIK uses
rsync to update only those portions of an ISO image that need to be updated, so it's an efficient way of keeping your ISO
set up-to-date. However, there are some hefty problems with the PIK:</para>
<itemizedlist>
<listitem><para>It's difficult to use and not very user friendly.</para></listitem>
@ -167,8 +185,8 @@
the mirrors.</para></listitem>
<listitem><para>The PIK uses rsync, which is blocked by many of the stricter firewalls. So even if you wanted to use that
nice fast corporate network at work, you might run into problems using the PIK.
<listitem><para>Each image needs to be stored on the server. That was OK in the good old potato days, when the 28 CD
images took "only" 17 GB. Starting with woody, the 96 CDs need 57 GB or so. Now imagine that we also want to offer
<listitem><para>Each image needs to be stored on the server. That was OK in the good old Potato days, when the 28 CD
images "only" took 17 GB. Starting with Woody, the 96 CDs need 57 GB or so. Now imagine that we also want to offer
DVDs and this figure doubles.</para></listitem>
</itemizedlist>
@ -182,23 +200,36 @@
<para>Jigdo (which stands for "Jigsaw Download") was written by <ulink url="mailto:atterer@debian.org">Richard
Atterer</ulink> and is released under the GNU GPL. It's a tool that allows efficient downloading and updating of an ISO
image. Any ISO image. Jigdo is not Debian specific, however Debian has chosen it to be the prefered method of
downloading ISO images. The jigdo tool comes with two utilities: jigdo-file which prepares an ISO image for download
and jigdo-lite which is used to download ISO images which were prepared by jigdo-file.</para>
downloading ISO images.</para>
<para>Jigdo doesn't create ISO images. It simply prepares them for downloading and also downloads them. The ISO image
needs to be made in advance, and that's usually done with mkisofs or debian-cd.</para>
<para>The jigdo tool comes with two utilities:</para>
<itemizedlist>
<listitem><para>jigdo-file is used by the person offering the ISO image. It enables anyone to download that image by
creating a .jigdo and .template file for the image.</para></listitem>
<listitem><para>jigdo-lite is used by people who want to download the ISO image. It downloads the image using the
image's .jigdo and .template files which were created by jigdo-file. If your main concern is simply downloading Debian
ISO images, you'll just be using jigdo-lite.</para></listitem>
</itemizedlist>
<para>A common misconception is that jigdo creates ISO images; it doesn't. Jigdo-file simply allows people to download
an ISO image by creating a .jigdo and .template file. The people who want to download the ISO image will get these two
files and use jigdo-lite to download the image. The ISO image needs to be made in advance, before jigdo-file is used,
and that's usually done with a utility like mkisofs or debian-cd.</para>
<para>Jigdo addresses all the problems with the other two methods of obtaining Debian ISO images:</para>
<itemizedlist>
<listitem><para>It's much faster than downloading the entire ISO image.</para></listitem>
<listitem><para>Unlike downloading the entire ISO image, it can take an outdated CD image (or a loop mounted outdated ISO
<listitem><para>Unlike downloading the entire ISO image, it can take an outdated CD (or a loop mounted outdated ISO
image), download <emphasis>only</emphasis> the files that have changed since the CD (or ISO image) was created and
create a new updated ISO. Very similar to how you use cvs to update source code.</para></listitem>
<listitem><para>jigdo-lite is much easier to use than the PIK.</para></listitem>
<listitem><para>jigdo-lite uses wget which, by default, uses http to transfer files. The PIK uses rsync. While rsync
may be blocked by some firewalls, the only firewalls that block http are the ones from which you shouldn't be using
jigdo to begin with. You'll almost never run into firewall problems with jigdo-lite.</para></listitem>
<listitem><para>jigdo-lite is much more user friendly than the PIK.</para></listitem>
<listitem><para>jigdo-lite is much more server friendly than the PIK.</para></listitem>
</itemizedlist>
<para>Clearly, jigdo is the best method of obtaining Debian ISO images.</para>
@ -226,7 +257,7 @@
<sect2 id="preparingtheisofordownload"><title>Preparing The ISO For Download</title>
<para>A CD image is a filesystem called iso9660, but for this discussion, we can safely talk about a cd image as being a
<para>A CD image is a filesystem called iso9660, but for this discussion, we can safely talk about a CD image as being a
big file called an "ISO image" (about 650MB) that contains files at various offsets. For instance, if a CD contains a 567
byte file named README, the ISO image might contain the README file's contents between offsets 20480000 and 20480567. You
can visualize a CD image as:</para>
@ -274,7 +305,7 @@
<para>jigdo-file found that the files <filename>file-0</filename>, <filename>file-1</filename> and
<filename>file-3</filename> were contained in the ISO image. It removed the contents of the these files and replaced them
with each file's md5 checksum.</para>
with each file's md5 checksum (the <filename>md5-0</filename>, <filename>md5-1</filename>, etc).</para>
<para>The "<literal remap="bf">x</literal>" data (directory information, zero padding, etc) within the ISO image is
compressed and written to the .template file. Finally, any files within the ISO image that weren't supplied as loose
@ -292,8 +323,8 @@
<sect2 id="the.jigdofile"><title>The .jigdo File</title>
<para>Given an input of an ISO image and a set of loose files which may or may not be in the ISO image, jigdo-file outputs
a .jigdo file for that ISO image. The Debian .jigdo files are gzipped, so you need to use zcat or zless to view it.
Here's what the .jigdo file looks like when you gunzip it:</para>
a .jigdo file for that ISO image. The Debian .jigdo files are gzipped, so you need to use zcat or zless to view them.
Here's what a .jigdo file looks like when you gunzip it:</para>
<screen>
md5-0=http://somemirror.org/file-0
@ -318,8 +349,9 @@
<sect2 id="downloadingtheimage"><title>Downloading The Image</title>
<para>Once you use jigdo-file to prepare the ISO for downloading, anyone can use jigdo-lite to download the ISO.
jigdo-lite downloads all the files of a Debian ISO using wget, assembles them and forms an ISO on the fly.</para>
<para>Once you use jigdo-file to generate a .jigdo and .template file for an ISO image, anyone can use jigdo-lite to
download that image. jigdo-lite downloads all the files of a Debian ISO using wget, assembles them and forms a copy of
the original ISO image on the fly.</para>
</sect2>
@ -749,6 +781,52 @@
<sect1><title>Frequently Asked Questions</title>
<para>Questions prepended with with a date indicate a time sensitive question, in other words, a question that relates to a
temporary situation. If you see one of these questions and know that the temporary situation has changed, please <ulink
url="mailto:p@dirac.org">contact me</ulink> and let me know so I can remove the question from the mini-HOWTO.</para>
<sect2><title>[11 Aug 2002]: I see the Woody and Sid .jigdo files. Where are the Sarge .jigdo files?</title>
<para>The testing ISO images aren't being offered at the moment because the boot floppies are broken. When they get
fixed, .jigdo files for weekly snapshots of Sarge will be available from a semi-official source (probably
<ulink url="http://non-us.cdimage.debian.org">http://non-us.cdimage.debian.org</ulink>).
</sect2>
<sect2><title>[11 Aug 2002]: Can I have two jigdo-lite sessions at the same time in the same directory?</title>
<para>Not at the moment. The two sessions will clash over the <filename>tmp/</filename> and
<filename>jigdo-file-cache.db</filename> files. This will being worked on. If you want to run concurrent jigdo-lite
sessions, use different working directories.</para>
</sect2>
<sect2 id="disacknowledgements"><title>[11 Aug 2002]: Why aren't the translations of this HOWTO on LDP?</title>
<para>I've been having trouble getting the translations of this HOWTO submitted to the non-English LDP editors.</para>
<para>The German LDP editor, Marco Budde <email>Budde@tu-harburg.de</email> refuses to accept the German translation
because it was written in Docbook and not Linuxdoc, even though Docbook is the preferred SGML language for the LDP.</para>
<para>The Portuguese LDP editor, Alfredo Carvalho <email>ajpc@poli.org</email>, has completely ignored my submission of
the Portuguese translation.</para>
<para>If you care about having LDP documents in these languages, I urge you to write to these editors and ask them to
please be more responsible about accepting translated documents. For the time being, you can download these translations
from my personal website, <ulink url="http://www.dirac.org/linux/debian/jigdo"
>http://www.dirac.org/linux/debian/jigdo</ulink>.</para>
</sect2>
<sect2><title>How can I make jigdo use a proxy?</title>
@ -758,6 +836,8 @@
</sect2>
<sect2 id="interrupted"><title>What do I do if my jigdo download gets interrupted?</title>
<para>If your download gets interrupted, all you need to do is restart jigdo-lite and hit &lt;ENTER&gt; at all the
@ -767,6 +847,7 @@
<sect2><title>My jigdo download won't complete because the .jigdo file is broken. When I download a new, fixed .jigdo file,
do I need to download all the data over again?</title>
@ -794,6 +875,9 @@
download the .jigdo and .template files for DVDs instead of CDs. You can find the DVD .jigdo and .template files at
<ulink url="http://www.debian.org/CD/jigdo-cd/">http://www.debian.org/CD/jigdo-cd/</ulink>.</para>
<para>Note that you need Linux 2.4 or later to create DVD-sized files. Under Windows, DVD-sized images can't be created
at all at the moment because the C++ library of the mingw gcc port doesn't have big file support yet.</para>
</sect2>
@ -836,7 +920,7 @@
<sect2 id="needtoupgrade"><title>I'm having trouble getting jigdo-lite to download Sarge or Sid.</title>
<sect2 id="needtoupgrade"><title>I'm having trouble getting jigdo to download Sarge or Sid.</title>
<para>If you're using Potato or Woody, upgrade to jigdo-lite 0.6.8. Because of a change in Jigdo, the version of
jigdo-lite that comes with Woody (rev 0) cannot download Sarge and Sid images. The version that comes with Sarge is
@ -862,17 +946,6 @@
<sect2><title>Can I have two jigdo-lite sessions at the same time in the same directory?</title>
<para>Not at the moment. The two sessions will clash over the <filename>tmp/</filename> and
<filename>jigdo-file-cache.db</filename> files. This will being worked on. If you want to run concurrent jigdo-lite
sessions, use different working directories.</para>
</sect2>
<sect2 id="otherplatforms"><title>Can I use jigdo on platforms other than Linux?</title>
<para>Certainly. If you're interested in Potato or Woody under Microsoft Windows, old SunOS, HP-UX and IRIX you can use
@ -984,3 +1057,4 @@ vim: tw=128
<!-- don't run as root -->

2
LDP/howto/docbook/HOWTO-INDEX/adminSect.sgml
View File

@ -81,7 +81,7 @@ Debian-Jigdo</ULink>, <CiteTitle>
Debian Jigdo mini-HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>
Updated: July 2002</CiteTitle>.
Updated: August 2002</CiteTitle>.
Describes why you should use jigdo (a tool for obtaining Debian ISOs),
a little bit about how it works and how you use it to get and update
Debian ISOs. </Para>

2
LDP/howto/docbook/HOWTO-INDEX/miniChap.sgml
View File

@ -350,7 +350,7 @@ Debian-Jigdo</ULink>, <CiteTitle>
Debian Jigdo mini-HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>
Updated: July 2002</CiteTitle>.
Updated: August 2002</CiteTitle>.
Describes why you should use jigdo (a tool for obtaining Debian ISOs),
a little bit about how it works and how you use it to get and update
Debian ISOs. </Para>

2
LDP/howto/docbook/HOWTO-INDEX/osSect.sgml
View File

@ -244,7 +244,7 @@ Debian-Jigdo</ULink>, <CiteTitle>
Debian Jigdo mini-HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>
Updated: July 2002</CiteTitle>.
Updated: August 2002</CiteTitle>.
Describes why you should use jigdo (a tool for obtaining Debian ISOs),
a little bit about how it works and how you use it to get and update
Debian ISOs. </Para>