871 lines
21 KiB
HTML
871 lines
21 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Frequently Asked Questions</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
|
REL="HOME"
|
|
TITLE="Debian Jigdo mini-HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Updating Your Image"
|
|
HREF="updatingyourimage.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Errata"
|
|
HREF="errata.html"></HEAD
|
|
><BODY
|
|
CLASS="SECT1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>Debian Jigdo mini-HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="updatingyourimage.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="errata.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="FAQ"
|
|
></A
|
|
>6. Frequently Asked Questions</H1
|
|
><P
|
|
>Questions prepended with a date indicate a time sensitive question (a question that relates
|
|
to a temporary situation). If you see one of these questions and know that the temporary
|
|
situation has changed, please <A
|
|
HREF="mailto:p@dirac.orgZZZ"
|
|
TARGET="_top"
|
|
>contact me</A
|
|
> and let me know
|
|
so I can remove the question from the mini-HOWTO.</P
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN351"
|
|
></A
|
|
>6.1. Why does jidgo ask <EM
|
|
>twice</EM
|
|
> for scanning for existing files? Is
|
|
it enough to say yes once ?</H2
|
|
><P
|
|
>It keeps asking this as long as you enter a path to scan. The idea is that you may want
|
|
to scan several old CDs, so you can insert one after the other into the drive and keep
|
|
supplying the path "<TT
|
|
CLASS="LITERAL"
|
|
>D:\</TT
|
|
>" (or whatever). See also <A
|
|
HREF="errata.html#MORE-ABOUT-SCAN"
|
|
>Section 7.2</A
|
|
>, "More About Scan Sources".</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN357"
|
|
></A
|
|
>6.2. Jigdo Has Problems Downloading Certain Filenames.</H2
|
|
><P
|
|
>When downloading Debian images under Windows, jigdo-lite may appear to have trouble
|
|
downloading one or more of the following files:</P
|
|
><TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> libbusiness-onlinepayment-bankofamerica-perl_xxx_all.deb
|
|
libbusiness-onlinepayment-authorizenet-perl_xxx_all.deb
|
|
libbusiness-onlinepayment-payconnect-perl_xxx_all.deb
|
|
libmasonx-request-withapachesession-perl_xxx_all.deb
|
|
libtemplate-plugin-calendar-simple-perl_xxx_all.deb
|
|
</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><P
|
|
>Move the jigdo download directory up by as many directories as possible, closer to the
|
|
drives's root directory.</P
|
|
><P
|
|
>The NTFS filesystem has a 255 character limit on a file's pathname. When jigdo-lite
|
|
downloads files from the internet, it makes a copy of the server directory structure in its
|
|
download directory. With their very long names, the above Debian packages may exceed the
|
|
allowed path length, which leads to error messages like "<TT
|
|
CLASS="LITERAL"
|
|
>Cannot write to `[very long
|
|
pathname]' (No such file or directory)</TT
|
|
>".</P
|
|
><P
|
|
>Some people may now wonder: Why does jigdo-lite use wget's
|
|
"<TT
|
|
CLASS="LITERAL"
|
|
>--force-directories</TT
|
|
>" switch, which creates these problematic directory
|
|
hierarchies?</P
|
|
><P
|
|
>Early versions of jigdo-lite did not use it, but then some folks requested that
|
|
jigdo-lite always use the "<TT
|
|
CLASS="LITERAL"
|
|
>--continue</TT
|
|
>" switch to avoid half-downloaded
|
|
.deb files being ignored and deleted when you interrupt and restart jigdo-lite.</P
|
|
><P
|
|
>Unfortunately, it turned out that this led to problems: The Debian servers contained
|
|
several identically named files (e.g. "<TT
|
|
CLASS="LITERAL"
|
|
>root.bin</TT
|
|
>") in different directories,
|
|
and if you interrupted jigdo-lite at roughly the right time during the download, the chances
|
|
were high that the resumed download would append data to the wrong half-downloaded file,
|
|
corrupting it and making the entire jigdo download fail.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="USEPROXY"
|
|
></A
|
|
>6.3. How do I make jigdo use my proxy?</H2
|
|
><P
|
|
>Edit <TT
|
|
CLASS="FILENAME"
|
|
>~/.jigdo-lite</TT
|
|
> (or <TT
|
|
CLASS="FILENAME"
|
|
>jigdo-lite-settings.txt</TT
|
|
>
|
|
for the Microsoft Windows version) into a text editor and find the line that starts with
|
|
"<TT
|
|
CLASS="LITERAL"
|
|
>wgetOpts</TT
|
|
>". The following switches can be added to that line:</P
|
|
><TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> -e ftp_proxy=http://LOCAL-PROXY:PORT/
|
|
-e http_proxy=http://LOCAL-PROXY:PORT/
|
|
--proxy-user=USER
|
|
--proxy-passwd=PASSWORD
|
|
</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><P
|
|
>Of course, substitute the correct values for your proxy server. The last two options
|
|
are only necessary if your proxy uses password authentication. The switches need to be added
|
|
to the end of the wgetOpts line before the final <TT
|
|
CLASS="LITERAL"
|
|
>'</TT
|
|
> character. All options
|
|
must be on one line.</P
|
|
><P
|
|
>Alternatively, under Linux you can also set up the <TT
|
|
CLASS="VARNAME"
|
|
>ftp_proxy</TT
|
|
> and
|
|
<TT
|
|
CLASS="VARNAME"
|
|
>http_proxy</TT
|
|
> environment variables, for example in the file
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>/etc/environment</TT
|
|
> or <TT
|
|
CLASS="FILENAME"
|
|
>~/.bashrc</TT
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN384"
|
|
></A
|
|
>6.4. Jigdo-lite fails with an error - have I downloaded all those MBs in vain?</H2
|
|
><P
|
|
>If <SPAN
|
|
CLASS="APPLICATION"
|
|
>jigdo-file</SPAN
|
|
> aborts after downloading a considerable chunk
|
|
of the ISO contents, you'll have a large "<TT
|
|
CLASS="LITERAL"
|
|
>.iso.tmp</TT
|
|
>" file. There are
|
|
several things to try to salvage your download:</P
|
|
><P
|
|
></P
|
|
><UL
|
|
><LI
|
|
><P
|
|
>Restart the download by pressing <B
|
|
CLASS="KEYCAP"
|
|
>RETURN</B
|
|
>. Maybe some of the
|
|
files could not be downloaded because of timeouts or other transient errors. Try to download
|
|
the missing files again.</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Try a different mirror. Some Debian mirrors are slightly out of sync -- maybe
|
|
a different mirror still holds files that were deleted from the one you specified, or it has
|
|
already been updated with files that are not yet present on your mirror. This has happened
|
|
quite a few times with me.</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Retrieve the missing parts of the image using <A
|
|
HREF="http://rsync.samba.org"
|
|
TARGET="_top"
|
|
>rsync</A
|
|
>. First, you need to find out the correct rsync URL
|
|
of the image you are downloading: Choose a server that offers rsync access to the <A
|
|
HREF="http://www.debian.org/CD/mirroring/rsync-mirrors"
|
|
TARGET="_top"
|
|
>stable</A
|
|
> or <A
|
|
HREF="http://www.debian.org/CD/http-ftp/#testing"
|
|
TARGET="_top"
|
|
>testing</A
|
|
> images, then determine the
|
|
correct path and filename. Directory listings can be obtained with commands like
|
|
<B
|
|
CLASS="COMMAND"
|
|
>rsync rsync://cdimage.debian.org/debian-cd/</B
|
|
>.</P
|
|
><P
|
|
>Next, remove the "<TT
|
|
CLASS="LITERAL"
|
|
>.tmp</TT
|
|
>" extension from jigdo-lite's temporary file
|
|
by renaming it, and pass both the remote URL and the local filename to rsync: <B
|
|
CLASS="COMMAND"
|
|
>rsync
|
|
rsync://server.org/path/binary-i386-1.iso binary-i386-1.iso</B
|
|
> You may want to use
|
|
rsync's <TT
|
|
CLASS="LITERAL"
|
|
>--verbose</TT
|
|
> and <TT
|
|
CLASS="LITERAL"
|
|
>--progress</TT
|
|
> switches to get
|
|
status messages, and <TT
|
|
CLASS="LITERAL"
|
|
>--block-size=8192</TT
|
|
> to increase its
|
|
speed.</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Under Linux, you can loop-mount the <TT
|
|
CLASS="LITERAL"
|
|
>.tmp</TT
|
|
> file to access the
|
|
packages that were already downloaded, and reuse them for generating an image from a newer
|
|
.jigdo file. To do this, first issue the following commands as root in the directory
|
|
with the broken download: <B
|
|
CLASS="COMMAND"
|
|
>mkdir mnt; mount -t iso9660 -o loop *.tmp mnt</B
|
|
>.
|
|
Next, start a new download in a different directory, and enter the path of the mnt directory
|
|
at the "Files to scan" prompt.</P
|
|
><P
|
|
>Under Microsoft Windows you can do the same thing by loop mounting the temporary ISO
|
|
image using "virtual drive" software. <SPAN
|
|
CLASS="APPLICATION"
|
|
><A
|
|
HREF="http://www.daemon-tools.cc"
|
|
TARGET="_top"
|
|
>Daemon tools</A
|
|
></SPAN
|
|
> and <SPAN
|
|
CLASS="APPLICATION"
|
|
>Nero
|
|
Image Drive</SPAN
|
|
> are both very popular. See also <A
|
|
HREF="http://tinyurl.com/c39zr"
|
|
TARGET="_top"
|
|
>http://tinyurl.com/c39zr</A
|
|
> for more options.</P
|
|
></LI
|
|
></UL
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="DISACKNOWLEDGEMENTS"
|
|
></A
|
|
>6.5. [11 Aug 2002]: Why aren't the translations of this HOWTO on LDP?</H2
|
|
><P
|
|
>I've been having trouble getting the translations of this HOWTO submitted to the
|
|
non-English LDP editors.</P
|
|
><P
|
|
>The German LDP editor, Marco Budde <TT
|
|
CLASS="EMAIL"
|
|
><<A
|
|
HREF="mailto:Budde@tu-harburg.de"
|
|
>Budde@tu-harburg.de</A
|
|
>></TT
|
|
> 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. It's a shame that we have people within the open
|
|
source community who would sabotage our community from the inside.</P
|
|
><P
|
|
>The Portuguese LDP editor, Alfredo Carvalho <TT
|
|
CLASS="EMAIL"
|
|
><<A
|
|
HREF="mailto:ajpc@poli.org"
|
|
>ajpc@poli.org</A
|
|
>></TT
|
|
>, has completely
|
|
ignored my submission of the Portuguese translation.</P
|
|
><P
|
|
>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, <A
|
|
HREF="http://www.dirac.org/linux/debian/jigdo"
|
|
TARGET="_top"
|
|
>http://www.dirac.org/linux/debian/jigdo</A
|
|
>.</P
|
|
><P
|
|
>Shame on you, Marco Budde <TT
|
|
CLASS="EMAIL"
|
|
><<A
|
|
HREF="mailto:Budde@tu-harburg.de"
|
|
>Budde@tu-harburg.de</A
|
|
>></TT
|
|
>.</P
|
|
><P
|
|
>Shame on you, Alfredo Carvalho <TT
|
|
CLASS="EMAIL"
|
|
><<A
|
|
HREF="mailto:ajpc@poli.org"
|
|
>ajpc@poli.org</A
|
|
>></TT
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="INTERRUPTED"
|
|
></A
|
|
>6.6. What do I do if my jigdo download gets interrupted?</H2
|
|
><P
|
|
>If your download gets interrupted, all you need to do is restart jigdo-lite and hit
|
|
<B
|
|
CLASS="KEYCAP"
|
|
>ENTER</B
|
|
> at all the question prompts. Jigdo-lite will pick up where it left
|
|
off.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN433"
|
|
></A
|
|
>6.7. 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?</H2
|
|
><P
|
|
>You may find that the .jigdo file you downloaded is broken. It's uncommon, but it does
|
|
happen from time to time with moving targets like Debian testing or unstable.</P
|
|
><P
|
|
>If you find that <TT
|
|
CLASS="FILENAME"
|
|
>.jigdo</TT
|
|
> is broken, you'll need to download a new
|
|
.jigdo file (when a fixed one becomes available), but you <EM
|
|
>won't</EM
|
|
> need to
|
|
download all the ISO data again.</P
|
|
><P
|
|
>You can use the same loop mounting trick we use when updating an ISO image. The
|
|
difference is that there's no finished .iso file to start with, but the .iso.tmp file is an
|
|
ISO image too and can be used to finish the download without having to re-download all the
|
|
data that was downloaded before the broken .jigdo file caused jigdo-lite to halt. Simply loop
|
|
mount the .iso.tmp file on <TT
|
|
CLASS="FILENAME"
|
|
>/mnt</TT
|
|
> and when you re-run
|
|
jigdo-lite with the fixed .jigdo file, tell jigdo-lite to scan <TT
|
|
CLASS="FILENAME"
|
|
>/mnt</TT
|
|
>. Don't forget to rename or move the .iso.tmp file so it
|
|
doesn't interfere with jigdo-lite which will want to create a new .iso.tmp file.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="DVDSIZEDIMAGES"
|
|
></A
|
|
>6.8. Can I use jigdo to download images for DVD?</H2
|
|
><P
|
|
>Absolutely; the process is identical to downloading CD images. The only thing you need
|
|
to do differently is to download the .jigdo and .template files for DVDs instead of CDs. You
|
|
can find the DVD .jigdo and .template files at <A
|
|
HREF="http://www.debian.org/CD/jigdo-cd/"
|
|
TARGET="_top"
|
|
>http://www.debian.org/CD/jigdo-cd/</A
|
|
>.</P
|
|
><P
|
|
>On Linux, you need kernel 2.4 or later to create DVD-sized files.</P
|
|
><P
|
|
>Under MS Windows, you need to use <TT
|
|
CLASS="LITERAL"
|
|
>jigdo-win-0.7.1a</TT
|
|
> (released 21 July
|
|
2004) or later to create DVD-sized images. This is because of a bug in the large file support
|
|
of Mingw32, the compiler used to create the MS Windows executables. The bug got fixed on this
|
|
date, and <TT
|
|
CLASS="LITERAL"
|
|
>jigdo-win-0.7.1a</TT
|
|
> was released.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN450"
|
|
></A
|
|
>6.9. Can I burn the <TT
|
|
CLASS="FILENAME"
|
|
>.iso.tmp</TT
|
|
> file to CD?</H2
|
|
><P
|
|
>Thanks to Gordon Huff and David Anselmi, we now know the answer is "yes you can". But
|
|
more importantly, Gordon gave a good reason why you'd want to do this in the first place.
|
|
Paraphrasing Gordon:</P
|
|
><A
|
|
NAME="AEN454"
|
|
></A
|
|
><BLOCKQUOTE
|
|
CLASS="BLOCKQUOTE"
|
|
><P
|
|
>My friend's Win98 has a *nice* cable connection. I arrive in the morning, start jigdo
|
|
(more than one, actually) and then we go to the store, tie back the kiwi plant, put up the
|
|
Christmas lights and Christmas tree, trim the tree, order and split a pizza and fire up the
|
|
satellite dish.</P
|
|
><P
|
|
>I leave my friends place with several iso.tmp's on CDRWs. When I get home, I use the
|
|
iso's that didn't finish to update my jigdo setup at home which is a dial-up.</P
|
|
></BLOCKQUOTE
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN457"
|
|
></A
|
|
>6.10. Jigdo-lite is broken! It downloads packages and deletes them. I know it doesn't write them to the
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>iso.tmp</TT
|
|
> file because the file size doesn't change!</H2
|
|
><P
|
|
>Jigdo works just fine -- the <TT
|
|
CLASS="FILENAME"
|
|
>.iso.tmp</TT
|
|
> file is created at the
|
|
beginning with its final size, but filled with zero bytes. Later, parts of it are overwritten
|
|
with the downloaded data.</P
|
|
><P
|
|
>You can tell that jigdo is making progress by looking at the messages "<TT
|
|
CLASS="LITERAL"
|
|
>Found X
|
|
of the Y files required by the template</TT
|
|
>" that are printed from time to time. The
|
|
first value "<TT
|
|
CLASS="LITERAL"
|
|
>X</TT
|
|
>" should increase. When <TT
|
|
CLASS="LITERAL"
|
|
>X</TT
|
|
> equals
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>Y</TT
|
|
>, the download is finished.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="TROUBLEWITHJIGDOEASY"
|
|
></A
|
|
>6.11. I'm having trouble getting jigdo-easy to work.</H2
|
|
><P
|
|
>See <A
|
|
HREF="errata.html#JIGDO-EASY"
|
|
>Section 7.1</A
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="SCANMULTIPLEIMAGES"
|
|
></A
|
|
>6.12. For image updates, I want jigdo-lite to scan 14
|
|
loop-mounted images in one go. How can I do this?</H2
|
|
><P
|
|
>When updating CD images, it's tiresome to keep loop-mounting and unmounting images.
|
|
However, by default the Linux kernel only supports eight loop devices, and jigdo-lite's menu
|
|
of previously entered paths only has five entries.</P
|
|
><P
|
|
>To scan many loop-mounted images, you must first tell the Linux kernel to support more
|
|
than the default eight devices. This is done by giving the "<TT
|
|
CLASS="LITERAL"
|
|
>max_loop</TT
|
|
>"
|
|
parameter to the module when loading it, e.g. with "<TT
|
|
CLASS="LITERAL"
|
|
>modprobe loop
|
|
max_loop=16</TT
|
|
>" on the command line or by adding the line "<TT
|
|
CLASS="LITERAL"
|
|
>options loop
|
|
max_loop=16</TT
|
|
>" to <TT
|
|
CLASS="FILENAME"
|
|
>/etc/modules.conf</TT
|
|
>. In Debian, you must put
|
|
this line into a file named e.g. <TT
|
|
CLASS="FILENAME"
|
|
>/etc/modutils/local-loop</TT
|
|
> and then run
|
|
<B
|
|
CLASS="COMMAND"
|
|
>update-modules</B
|
|
> because direct changes to
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>/etc/modules.conf</TT
|
|
> will be overwritten.</P
|
|
><P
|
|
>Having mounted the individual images, you can pass the parent directory of their mount
|
|
points to jigdo-lite for scanning. For example, if the images are mounted under <TT
|
|
CLASS="FILENAME"
|
|
>/mnt/myloopmounts/image1/</TT
|
|
> etc., pass "<TT
|
|
CLASS="FILENAME"
|
|
>/mnt/myloopmounts</TT
|
|
>" as the path to scan. If passing the parent
|
|
directory is inconvenient, you can also create a directory and fill it with symlinks to the
|
|
mount points.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="WGETOPTIONS"
|
|
></A
|
|
>6.13. Jigdo-lite is too verbose. How can I supress some or all of its messages?</H2
|
|
><P
|
|
>Jigdo-lite uses wget, and wget's output can be quite verbose. If this is unsettling,
|
|
you can make wget more quiet by adding <TT
|
|
CLASS="LITERAL"
|
|
>--non-verbose</TT
|
|
> to the
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>wgetOpts</TT
|
|
> switch in your <TT
|
|
CLASS="FILENAME"
|
|
>~/.jigdo-lite</TT
|
|
> file. If you
|
|
want wget to print no messages at all, use <TT
|
|
CLASS="LITERAL"
|
|
>--quiet</TT
|
|
> in the
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>wgetOpts</TT
|
|
> switch.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="OTHERPLATFORMS"
|
|
></A
|
|
>6.14. Can I use jigdo on platforms other than Linux?</H2
|
|
><P
|
|
>Certainly. If you're interested in Potato or Woody under Microsoft Windows, old SunOS,
|
|
HP-UX and IRIX you can use jigdo-easy. See <A
|
|
HREF="errata.html#JIGDO-EASY"
|
|
>Section 7.1</A
|
|
> and <A
|
|
HREF="errata.html#LINKS"
|
|
>Section 7.4</A
|
|
>.</P
|
|
><P
|
|
>If you want to download Potato, Woody, Sarge or Sid under Microsoft Windows, jigdo-lite
|
|
has been ported to that platform and can be downloaded from the main jigdo site (<A
|
|
HREF="errata.html#LINKS"
|
|
>Section 7.4</A
|
|
>).</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN500"
|
|
></A
|
|
>6.15. On MS Windows, why do I get a "<TT
|
|
CLASS="LITERAL"
|
|
>No such file or directory</TT
|
|
>" error message?</H2
|
|
><P
|
|
>You might find that under MS Windows, jigdo-lite will download some files but then fail
|
|
to read their contents, which will produce a "<TT
|
|
CLASS="LITERAL"
|
|
>No such file or directory</TT
|
|
>"
|
|
error message.
|
|
|
|
</P
|
|
><P
|
|
>It seems that this occurs if the length of the filenames that jigdo processes exceeds a
|
|
certain limit. The solution is to move the half-finished download up in the directory
|
|
hierarchy, closer to the top-level directory of the drive.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN506"
|
|
></A
|
|
>6.16. On MS Windows, why won't my image grow larger than 2GB?</H2
|
|
><P
|
|
>You're using an old version of jigdo. Please upgrade to
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>jigdo-win-0.7.1a </TT
|
|
> or newer. See <A
|
|
HREF="faq.html#DVDSIZEDIMAGES"
|
|
>Section 6.8</A
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN511"
|
|
></A
|
|
>6.17. On MS Windows, <TT
|
|
CLASS="FILENAME"
|
|
>jigdo-lite.bat</TT
|
|
> fails with an error message
|
|
saying "sh" was not found.</H2
|
|
><P
|
|
>This means that the <TT
|
|
CLASS="LITERAL"
|
|
>PATH</TT
|
|
> command in the <TT
|
|
CLASS="LITERAL"
|
|
>.bat</TT
|
|
> file failed. For some
|
|
reason, this is the case if you unpacked jigdo on a Windows network share using a path like
|
|
"<TT
|
|
CLASS="FILENAME"
|
|
>\\SomeServer\Files\jigdo</TT
|
|
>". Solution: Use "<B
|
|
CLASS="COMMAND"
|
|
>Map
|
|
network drive</B
|
|
>" (in the explorer "tools" menu) to assign a drive letter like
|
|
"<TT
|
|
CLASS="LITERAL"
|
|
>Z:</TT
|
|
>", then double-click on the <TT
|
|
CLASS="LITERAL"
|
|
>.bat</TT
|
|
> file inside
|
|
"<TT
|
|
CLASS="LITERAL"
|
|
>Z:\jigdo</TT
|
|
>". Alternatively, a workaround is to move
|
|
everything in the <TT
|
|
CLASS="FILENAME"
|
|
>jigdo-bin</TT
|
|
> subdirectory up to where the
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>.bat</TT
|
|
> file is.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN524"
|
|
></A
|
|
>6.18. Can I run multiple instances of jigdo-lite to download images in parallel?</H2
|
|
><P
|
|
>Absolutely. However, to avoid filename clashing, you should run each
|
|
<SPAN
|
|
CLASS="APPLICATION"
|
|
>jigdo-lite</SPAN
|
|
> instance in its own separate directory. You can start
|
|
as many instances as you want, go to bed, and when you wake up, all the ISO images will be
|
|
waiting for you on your hard drive. Be aware that <SPAN
|
|
CLASS="APPLICATION"
|
|
>jigdo-lite</SPAN
|
|
> is
|
|
bandwidth and CPU intensive, so you won't want to use your computer with multiple instances
|
|
running in tandem.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN529"
|
|
></A
|
|
>6.19. Is there a GUI interface available?</H2
|
|
><P
|
|
>A GTK+ interface to jigdo is being worked on. Both Linux and Microsoft Windows GUI
|
|
clients are planned. Unfortunately, it's been 80% done for over 1.5 years, so don't hold your
|
|
breath for its release.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="updatingyourimage.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="errata.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Updating Your Image</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Errata</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |