1 |
On Thu, May 03, 2007 at 04:34:19PM -0700, Robin H. Johnson wrote: |
2 |
> Would all mirrors that carry the experimental tree please see my |
3 |
> follow-up email about BitTorrent HTTP-seeding? |
4 |
|
5 |
Hi folks, |
6 |
|
7 |
So now stuff on BitTorrent for the 2007.0 release. |
8 |
|
9 |
There's two portions to this email, firstly stuff distributed by |
10 |
BitTorrent only, and then everything else. |
11 |
|
12 |
We have 94 torrents in total, 2 of which are only media that is only |
13 |
being distributed by BitTorrent. |
14 |
|
15 |
We needs seeds for all of it, but the bittorrent-only stuff more than |
16 |
the rest. I have one sponsor offering 50Mbit * 2 weeks for seeding |
17 |
everything so far. |
18 |
|
19 |
In terms of basic structure, there is a .torrent for every .tar.bz2 or |
20 |
.iso in releases or experimental, containing the core file, plus it's |
21 |
DIGESTS, signature, and CONTENTS files. |
22 |
|
23 |
BitTorrent-only: |
24 |
3.7G livedvd-amd64-installer-2007.0/ |
25 |
3.8G livedvd-i686-installer-2007.0/ |
26 |
|
27 |
If you're interested in direct BitTorrent seeding (esp. for the above |
28 |
two, even if you aren't seeding anything else), please give me a shout |
29 |
so that I can arrange to get them to you. |
30 |
|
31 |
Now for the experimental part... |
32 |
|
33 |
To help out long-term seeding of the majority of torrents (those that |
34 |
aren't bittorrent-only), I'd like to take advantage of the newish |
35 |
HTTP-seeding support of BitTorrent [1]. |
36 |
|
37 |
HTTP-seeding kicks in at a MUCH lower priority than regular BitTorrent |
38 |
peering, basically helping clients that cannot contact any other source |
39 |
for missing pieces. It effectively converts the BitTorrent client to a |
40 |
slightly-smart HTTP fetcher that then shares the blocks back over |
41 |
BitTorrent to other clients. |
42 |
|
43 |
For all experimental/ mirrors, that means we're adding a directory tree |
44 |
under experimental/ that has directories containing only symlinks. Your |
45 |
rsync options will need to have the various symlink-transfer options, |
46 |
which I think should be in place already. |
47 |
|
48 |
Here's an example of one. |
49 |
experimental/torrent-symlinks/stage3-x86-2007.0: |
50 |
lrwxrwxrwx stage3-x86-2007.0.tar.bz2 -> ../../releases/x86/2007.0/stages/stage3-x86-2007.0.tar.bz2 |
51 |
lrwxrwxrwx stage3-x86-2007.0.tar.bz2.CONTENTS -> ../../releases/x86/2007.0/stages/stage3-x86-2007.0.tar.bz2.CONTENTS |
52 |
lrwxrwxrwx stage3-x86-2007.0.tar.bz2.DIGESTS -> ../../releases/x86/2007.0/stages/stage3-x86-2007.0.tar.bz2.DIGESTS |
53 |
lrwxrwxrwx stage3-x86-2007.0.tar.bz2.asc -> ../../releases/x86/2007.0/stages/stage3-x86-2007.0.tar.bz2.asc |
54 |
|
55 |
This in itself doesn't make the BitTorrent clients contact you, so even |
56 |
if you aren't participating, it doesn't cause harm to have it. |
57 |
|
58 |
For part two of the HTTP-seeding (eg making the BT clients actually use |
59 |
the mirrors), I'd like to know which of the experimental mirrors are |
60 |
interested in being used for HTTP seeding. |
61 |
|
62 |
Your webservers will need to support HTTP Range requests for this to |
63 |
work. The BitTorrent clients will send range requests for 32K..256K |
64 |
blocks (powers of two only). |
65 |
|
66 |
I'll be placing the base potion of your URLs into the .torrent files, as |
67 |
"$BASEURL/experimental/torrent-symlinks/" |
68 |
|
69 |
[1] The actual specification for the HTTP-seeding is here: |
70 |
http://www.getright.com/seedtorrent.html |
71 |
|
72 |
-- |
73 |
Robin Hugh Johnson |
74 |
Gentoo Linux Developer & Council Member |
75 |
E-Mail : robbat2@g.o |
76 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |