It seems that Debian would require much more space. What are we going to
do about it?
Regards,
Shlomi Fish
----------------------------------------------------------------------
Shlomi Fish [EMAIL PROTECTED]
Home Page: http://t2.technion.ac.il/~shlomif/
Home E-mail: [EMAIL PROTECTED]
"Let's suppose you have a table with 2^n cups..."
"Wait a second - is n a natural number?"
---------- Forwarded message ----------
Date: Wed, 5 Jun 2002 23:22:38 +0100 (BST)
From: Richard Atterer <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: undisclosed-recipients: ;
Subject: Forthcoming release of CD images for Debian 3.0 rev0 ("woody")
This mail was sent to you because your address is stored in our
database of Debian CD mirror servers and your server is listed on
<http://www.debian.org/CD/http-ftp/>. Note that if you reply to this
mail, your answer will by default be sent to
<[EMAIL PROTECTED]>, a public mailing list.
Within the next weeks, Debian 3.0 "woody" will be released and new CD
images will be made available. The exact release date is not known yet
- subscribe to the debian-cd mailing list to be informed about it.
Here is some information about the release of the new CD images.
Required disc space grows to 50 or 57 GB
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The images of the current stable distribution ("potato") need 17 GB of
disc space for 28 CD images. In contrast to this, the full set of
"woody" CDs needs about 57 GB for 96 CD images!
However, by default the 1_NONUS CDs will not be available for
rsync-based mirroring (and thus also debcdmirror), which reduces the
amount of space to 50 GB for 84 images.
The increase is due to the larger number of CDs (8, used to be 4) per
architecture, and the larger number of architectures (11, used to be
6).
If you do not want to mirror the complete set of images, it is
possible to restrict which images to mirror and which to omit - see
below for instructions.
Setup changes on your mirror
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You do not need to change anything about your current mirror setup if
you want to distribute the set of 84 CD images which needs about 50 GB
- the old "debcdmirror" scheme as well as rsync or FTP/HTTP mirroring
will continue to work.
However, consider changing the mirror setup as described below if one
of the following applies:
- You want to update your mirror quickly. In our experience, the
master site will be under heavy load around release time, possibly
even to the point of not being reachable.
- You already have a local "regular" Debian FTP mirror. In this case,
the mirroring can be made much more efficient now.
- You do not want to offer the full set of 96 CD images.
New way of mirroring: jigdo-mirror
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
jigdo is a new way of generating Debian CD images. A local (=same
machine) Debian FTP mirror is required for this. Additionally, if the
mirror does not run Linux on Intel, you'll have to compile jigdo
yourself - you need a recent C++ compiler (e.g. GCC 2.95) for this.
The jigdo-mirror script to automate mirroring of Debian's CD images is
new and needs more testing - if you can, please try it out now on the
3.0 pre-release images and report any success/failure to us!
jigdo-mirror takes packages from the mirror as well as special files
with ".jigdo" and ".template" extensions, and assembles the CD images
from all this information. This makes it similar to how debcdmirror
works, with the important difference that jigdo does not rely on rsync
to produce the final image.
A jigdo-based mirror requires
- setting up a normal Debian FTP mirror <http://www.debian.org/mirror/>
- setting up HTTP mirroring of the .jigdo/.template files at
<http://cdimage.debian.org/jigdo-area/current/jigdo/>
- setting up a cronjob which runs jigdo-mirror about once a day.
Alternatively, you can also run jigdo-mirror manually whenever a
new version of the CDs is released.
- configuring jigdo-mirror. This should be easy, it hardly needs more
information than the paths to the .jigdo/.template files and your
Debian FTP mirror.
Excluding certain CD images from being stored on your mirror
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The 96 images can be broken up as follows: For each of the 11
architectures (alpha, arm, hppa, i386, ia64, m68k, mips, mipsel,
powerpc, s390, sparc), there are 8 CDs, CD 1-7 and CD 1_NONUS.
Furthermore, there are 8 "source" CDs, again 7 CDs and one NONUS
version of the first CD.
Mirror sites located in the United States should not mirror the
1_NONUS CD, because it contains software which is not distributable in
the US, e.g. because of patent issues. In contrast, mirrors outside
the US may *only* want to mirror CD 1_NONUS, not CD 1.
If 50 GB is too much for you, one possible way to restrict the needed
disc space to 17 GB is to mirror all CDs for i386 and CDs 1+2 of the
remaining architectures, and only to mirror one variant of the first
CD. Below are instructions on how to do this with the different
mirroring schemes.
rsync-based mirroring
You can use rsync's include/exclude mechanism. Add the following
switches to the rsync command:
US sites:
--exclude '*_NONUS*' --exclude 'source/*' --include 'i386/*' --exclude
'*-[3-9].iso'
Sites outside the US:
--exclude '*-1.*' --exclude 'source/*' --include 'i386/*' --exclude '*-[3-9].iso'
jigdo-mirror based mirroring
Use jigdo-mirror's include/exclude feature. The required setting is
as follows:
US sites: include='i386/|-[12]'; exclude='source/|_NONUS'
Sites outside the US: include='i386/|-[12]'; exclude='source/|-1\.'
mirroring based on debcdmirror
Refer to the instructions on debcdmirror's include/exclude files in
its documentation.
Changes in the setup of Debian's master CD mirror
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In the past, the server where Debian CDs were generated was
cdimage.debian.org, a.k.a. open.hands.com, a machine in the UK.
Starting with the release of woody, the cdimage DNS entry will point
to raff.debian.org (located in the US), while open will be available
as non-us.cdimage.debian.org.
Links
~~~~~
Debian on CD:
<http://www.debian.org/CD/>
Archives of the debian-cd mailing list:
<http://lists.debian.org/debian-cd/>
The rsync utility:
<http://rsync.samba.org/>
rsync path for stable CD images:
<rsync://cdimage.debian.org/debian-cd/>
(Try not to mirror directly from the master site if possible.)
HTTP access is disabled for the images themselves, but the MD5SUM
files and .list files can be fetched here:
<http://cdimage.debian.org/cd-images/>
Retrieving Debian CDs with jigdo:
<http://www.debian.org/CD/jigdo-cd/>
jigdo homepage:
<http://atterer.net/jigdo/>
How to set up jigdo-mirror:
<http://atterer.net/jigdo/jigdo-mirror.html>
Precompiled jigdo binary for i386 Linux, including documentation:
<http://atterer.net/jigdo/jigdo-bin-0.6.7.tar.bz2>
jigdo source code:
<http://atterer.net/jigdo/jigdo-0.6.7.tar.bz2>
.jigdo/.template files for pre-release tests of Debian 3.0:
<http://cdimage.debian.org/jigdo-area/>
The .jigdo/.template files for 3.0 will be made available here:
<http://cdimage.debian.org/jigdo-area/current/jigdo/>
The debcdmirror script:
<http://cdimage.debian.org/~costar/debcdmirror/>
In case of questions, feel free to reply to this mail. Thank you for
dedicating disc space to Debian CD images!
All the best,
Richard
--
__ _
|_) /| Richard Atterer
| \/�| http://atterer.net
� '` �
----------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED]
Archives available at http://www.mail-archive.com/[email protected]/
