[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: BitTorrent�READMEファイル
- From: Yukiharu Yabuki <yabuki@xxxxxxxxxxxxx>
- Subject: Re: BitTorrent�READMEファイル
- Date: Fri, 18 Feb 2005 17:07:07 +0900
- List-help: <mailto:debian-doc-ctl@debian.or.jp?body=help>
- List-id: debian-doc.debian.or.jp
- List-owner: <mailto:debian-doc-admin@debian.or.jp>
- List-post: <mailto:debian-doc@debian.or.jp>
- List-software: fml [fml 4.0.3 release (20011202/4.0.3)]
- List-unsubscribe: <mailto:debian-doc-ctl@debian.or.jp?body=unsubscribe>
- Organization: LILO(netfort.gr.jp)
- X-authentication: yabuki was authenticated by viper2.netfort.gr.jp at 18 Feb 2005 08:07:05 -0000
- X-ml-info: If you have a question, send e-mail with the body "help" (without quotes) to the address debian-doc-ctl@debian.or.jp; help=<mailto:debian-doc-ctl@debian.or.jp?body=help>
- X-ml-name: debian-doc
- X-mlserver: fml [fml 4.0.3 release (20011202/4.0.3)]; post only (only members can post)
- X-original-to: debian-doc@debian.or.jp
- X-spam-level: **
- X-spam-status: No, hits=2.2 required=10.0 tests=IN_REP_TO,ISO2022JP_BODY,NOSPAM_INC,RCVD_IN_ORBS, RCVD_IN_OSIRUSOFT_COM,REFERENCES,SPAM_PHRASE_00_01, X_OSIRU_OPEN_RELAY version=2.44
- References: <20050216200652.35ecfcf2.yabuki@xxxxxxxxxxxxx> <20050217150536K.VEC05526@xxxxxxxxxxx>
- Message-id: <20050218170705.0eab1c9a.yabuki@xxxxxxxxxxxxx>
- X-mail-count: 04395
- X-mailer: Sylpheed version 1.0.1 (GTK+ 1.2.10; i386-pc-linux-gnu)
æ¦äº•伸光ã�•ã�¾
ç§�ã�®æ‹™ã�„翻訳よんã�§ã€�具体的ã�ªæ��案をã�—ã�¦ã�„ã�Ÿã� ã��ã�‚りã�Œã�¨ã�†
�����。
æ¦äº•ã�•ã�¾ã�®ä¿®æ£æ¡ˆã‚’å��æ˜ ã�•ã�›ã�¦ã�„ã�Ÿã� ã��ã�¾ã�—ã�Ÿã€‚
On Thu, 17 Feb 2005 15:05:43 +0900
TAKEI Nobumitsu <takei@xxxxxxxxxxxxxxxx> wrote:
> æ¦äº•伸光ã�§ã�™ï¼Žæ™‚é–“ã�Œã�‹ã�‹ã‚Šã�¾ã�—ã�Ÿï¼Ž
>
> 全文ã�«ã‚�ã�Ÿã‚Šï¼Œèªç‚¹ã�¨å�¥ç‚¹ã�«ã€Œï¼Œï¼Žã€�ã�Œä½¿ã‚�れã�¦ã�„ã�¾ã�™(, ã�Œä½¿ã‚�れã�¦ã�„ã‚‹
> ���も�り��).
ã€�。ã�«ä¿®æ£ã�•ã�›ã�¦ã�„ã�Ÿã� ã��ã�¾ã�—ã�Ÿã€‚
> http://www.debian.or.jp/Documents/debiandoc-guidelines-ja/debiandoc-guidelines-ja.html/ch-notation.html#s-symbols を音èªã�ªã�•ã‚‹ã�¨ã�„ã�„ã�§ã�—ょã�†ï¼Ž
ã�†ã��ã€�å�¥èªç‚¹ã�Šã‚ˆã�³ã‚«ãƒƒã‚³ã�®ã‚¹ãƒšãƒ¼ã‚¹å…·å�ˆã€�・ã�®ä½¿ç”¨ã�ªã�©ã€�Debian-docã�§ã‚„ã�£ã�¦ã�¯
ã�„ã�‘ã�ªã�„ã�“ã�¨ã�®ã‚ªãƒ³ãƒ‘レードã�®æ–‡ç« を投稿ã�—ã�¦ã�—ã�¾ã�„ã�¾ã�—ã�Ÿã€‚ã�™ã�„ã�¾ã�›ã‚“。
ã�„ã�¾ã�¯æ°—ã‚’ã�¤ã�‘ã�Ÿã�®ã�§è¨‚æ£ã�§ã��ã�Ÿã�¨ã�Šã‚‚ã�„ã�¾ã�™ã€‚
> 敬体�常体�混在���る��強��和感��り��.
ã�“れもã€�ã�“ã�®ãƒ�ージョンã�§ã�¯è¨‚æ£ã�—ã�Ÿã�¤ã‚‚りã�§ã�™ã€‚
ã�»ã�¨ã‚“ã�©ã�®å¾¡æŒ‡æ‘˜ã�¯ã��ã�®ã�¾ã�¾ä¿®æ£ã�•ã�›ã�¦ã�„ã�Ÿã� ã��ã�¾ã�—ã�Ÿã€‚
> > This command may take a while to scan over the whole file hashing it.
> > ��コマンド�,ファイル全体を�ッシュ�る��ファイルを走査���.
>
> take a while �未訳��.take a while =「��ら�時間���る�
> 案↓
> ��コマンド��全��ファイルを�ッシュ�る��走査�る�����ら
> �時間���る��ょ�。
��コマンド��ファイル全体を走査����ッシュ��ゆ����
��ら�時間���る��ょ�。
ã�“ã�“ã� ã�‘変更ã�•ã�›ã�¦ã�„ã�Ÿã� ã��ã�¾ã�—ã�Ÿã€‚
> --
> タケイノブミツカレマシタ
ã�‚りã�Œã�¨ã�†ã�”ã�–ã�„ã�¾ã�—ã�Ÿã€‚æ¦äº•ã�•ã�¾ã�¸ã�®è¬�辞を入れã�•ã�›ã�¦ã�„ã�Ÿã� ã��ã�¾ã�—ã�Ÿã€‚
--
====+====+====+====+====+====+====+====+====+====+====+====+====+====+
Yukiharu Yabuki (矢�幸治) I use Debian GNU/Linux
mail: yabuki@xxxxxxxxxxxxx クレクレタコラã�¯å¥½ã�� / クレクレタコã� ã�¯ã‚¤ãƒ¤
è°è«–パターンを実践ã�—ã�¦ã�¿ã�¾ã�›ã‚“ã�‹?
http://www.shos.info/develop/oo/dscsnptn.html
====+====+====+====+====+====+====+====+====+====+====+====+====+====+
$Id: bittorrent-readme.txt,v 1.7 2005/02/18 08:05:29 yabuki Exp $
This is EUC-JP text!
======================================================================
BitTorrent is a tool for distributing files. It's extremely
easy to use - downloads are started by clicking on hyperlinks.
Whenever more than one person is downloading at once
they send pieces of the file(s) to each other, thus relieving
the central server's bandwidth burden. Even with many
simultaneous downloads, the upload burden on the central server
remains quite small, since each new downloader introduces new
upload capacity.
BitTorrent¤Ï¡¢¥Õ¥¡¥¤¥ë¤òÇÛÉÛ¤¹¤ë¥Ä¡Ý¥ë¤Ç¤¹¡£BitTorrent¤Ï¡¢ -- ¥Ï¥¤¥Ñ¡¼
¥ê¥ó¥¯¤ò¥¯¥ê¥Ã¥¯¤¹¤ë¤À¤±¤Ç¡¢¥À¥¦¥ó¥í¡¼¥É¤¬³«»Ï¤·¤Þ¤¹¡¥ ¤È¤Æ¤â´Êñ¤Ë»È¤¨
¤Þ¤¹¡¢¤Ò¤È¤ê°Ê¾å¤¬Æ±»þ¤Ë¥À¥¦¥ó¥í¡¼¥É¤¹¤ë¤È (¥À¥¦¥ó¥í¡¼¥É¤·¤Æ¤¤¤ë) Èà¤é
¤¬¡¢¤ª¤¿¤¬¤¤¤Ë¥Õ¥¡¥¤¥ë¤Î¾®¤µ¤ÊÉôʬ¤òÁ÷¤ê¹ç¤Ã¤Æ¡¢Ãæ±û¥µ¡¼¥Ð¤ÎÂÓ°èÉý¤Ø¤Î
Éé²Ù¤ò·Ú¸º¤·¤Þ¤¹¡£Æ±»þ¤Ë¿¿ô¤Î¥À¥¦¥ó¥í¡¼¥É¤Ç¤µ¤¨¡¢--- Ãæ±û¥µ¡¼¥Ð¤Î
¥¢¥Ã¥×¥í¡¼¥ÉÉé²Ù¤Ï¡¢Á´¤¯¾®¤µ¤¤¤Þ¤Þ¤Ç¤¹ --- ¤³¤Î¤è¤¦¤Ë¿·µ¬¤Ë¥À¥¦¥ó
¥í¡¼¥É¤¹¤ë¼Ô (°Ê²¼¡¢¥À¥¦¥ó¥í¡¼¥À¡¼) ¤Ï¡¢¿·¤·¤¤¥¢¥Ã¥×¥í¡¼¥ÉǽÎϤòÄó¶¡
¤·¤Þ¤¹¡£
Windows web browser support is added by running an installer.
A prebuilt one is available, but instructions for building it
yourself are in BUILD.windows.txt
¥¦¥£¥ó¥É¥¦¥º¤Î¥¦¥§¥Ö¥Ö¥é¥¦¥¶¤Ï»Ù±çµ¡Ç½¤È¤·¤Æ¥¤¥ó¥¹¥È¡¼¥é¤ò¼Â¹Ô¤¹¤ë
(µ¡Ç½) ¤òÄɲ䷤Ƥ¤¤Þ¤¹¡£¥×¥ì¥Ó¥ë¥É¤ÏÆþ¼ê²Äǽ¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤¬¡¢
¤½¤ì¤ò¤¢¤Ê¤¿¤¬¥Ó¥ë¥É¤¹¤ë¼ê½ç¤Ë¤Ä¤¤¤Æ¤Ï¡¢BUILD.windows.txt ¤Ë¤¢¤ê¤Þ¤¹¡£
Instructions for Unix installation are in INSTALL.unix.txt
Unix¤Ø¤Î¥¤¥ó¥¹¥È¡¼¥ë¼ê½ç¤Ï¡¢INSTALL.unix.txt ¤Ë¤¢¤ë¡£
To start hosting -
¥Û¥¹¥Æ¥£¥ó¥°¤ò³«»Ï¤¹¤ë¤Ë¤Ï¡£
1) start running a tracker
1) ¥È¥é¥Ã¥«¡¼¤òµ¯Æ°¤·¤Þ¤¹¡£
First, you need a tracker. If you're on a dynamic IP or otherwise
unreliable connection, you should find someone else's tracker and
use that. Otherwise, follow the rest of this step.
ºÇ½é¤Ë¡¢¥È¥é¥Ã¥«¡¼¤¬É¬ÍפǤ¹¡£¤â¤·¡¢¤¢¤Ê¤¿¤¬Æ°Åª¤ËÊѲ½¤¹¤ëIP¤ä¡¢ÉԳμÂ
¤ÊÀܳ¾õ¶·¤Î¾å(ÌõÃí. ¤Ç¥È¥é¥Ã¥«¡¼¤Î¥µ¡¼¥Ð¤òΩ¤Æ¤è¤¦¤È¤·¤Æ¤¤¤ë)¤Ê¤é¡¢¤¢
¤Ê¤¿¤Ï¤É¤³¤«Ê̤Υȥé¥Ã¥«¡¼¤ò¸«¤Ä¤±¤ÆÍøÍѤ¹¤ë¤Ù¤¤Ç¤¹¡£¤½¤¦¤Ç¤Ê¤¤¾ì¹ç
(ÌõÃí. ¸ÇÄêIP¤Ç³Î¼Â¤ËÀܳ¤Ç¤¤ë¾ì¹ç) ¡¢°Ê¹ß¤Î¥¹¥Æ¥Ã¥×¤Ë½¾¤Ã¤Æ¤¯¤À¤µ
¤¤¡£
Trackers refer downloaders to each other. The load on the tracker
is very small, so you only need one for all your files.
¥È¥é¥Ã¥«¡¼¤Ï¡¢¥À¥¦¥ó¥í¡¼¥À¡¼¤ò¤ª¸ß¤¤¤Ë»²¾È¤µ¤»¤Þ¤¹¡£¥È¥é¥Ã¥«¡¼¤ÎÉé²Ù
¤Ï¡¢¤¿¤¤¤Ø¤ó¾®¤µ¤¯¡¢Á´¥Õ¥¡¥¤¥ë¤Î¤¿¤á¤Ë¤Ò¤È¤Ä¤À¤±É¬ÍפǤ¹¡£
To run a tracker, execute the command bttrack.py Here is an example -
¥È¥é¥Ã¥«¡¼¤òư¤«¤¹¤Ë¤Ï¡¢bttrack.py¤È¤¤¤¦¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤µ¤»¤Þ¤¹¡£
Îã¤È¤·¤Æ -
./bttrack.py --port 6969 --dfile dstate
--dfile is where persistent information is kept on the tracker across
invocations. It makes everything start working again immediately if
you restart the tracker. A new one will be created if it doesn't exist
already.
--dfile ¤Ï¡¢¥È¥é¥Ã¥«¡¼¤¬¸Æ¤Ó½Ð¤µ¤ì¤¿¤éµÏ¿¤µ¤ì¤ë±Ê³Ū¤Ê¾ðÊó¤Ç¤¹¡£
¥È¥é¥Ã¥«¡¼¤òºÆµ¯Æ°¤·¤¿¤Ê¤é¡¢Â¨ºÂ¤ËÁ´¤Æ¤Îºî¶È¤¬ºÆ³«¤µ¤ì¤Þ¤¹¡£´û¤Ë
(ÌõÃí. ¥Õ¥¡¥¤¥ë¤¬) ¸ºß¤·¤Æ¤¤¤Ê¤±¤ì¤Ï¡¢¿·¤·¤¤¤â¤Î¤¬ºîÀ®¤µ¤ì¤ë
¤Ç¤·¤ç¤¦¡£
The tracker must be on a net-addressible box, and you must know the
ip number or dns name of it.
¥È¥é¥Ã¥«¡¼¤Ï¡¢¥Í¥Ã¥È¥ï¡¼¥¯¤«¤éÅþã¤Ç¤¤ë¥µ¡¼¥Ð¤Ç¤¢¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤Þ
¤¿¡¢¤¢¤Ê¤¿¤ÏIP¥¢¥É¥ì¥¹¤ÈDNS¤ËÅÐÏ¿¤·¤Æ¤¢¤ë̾Á° (ÌõÃí¡¥FQDN ¤Î¤³¤È¤«)
¤òÃΤäƤ¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
The tracker outputs web logs to standard out. You can get information
about the files it's currently serving by getting its index page.
¥È¥é¥Ã¥«¡¼¤Ï¡¢É¸½à½ÐÎÏ¤Ø Web¤Î¥í¥°¤ò½ÐÎϤ·¤Þ¤¹¡£¥¤¥ó¥Ç¥Ã¥¯¥¹¥Ú¡¼¥¸¤ò¼è
ÆÀ¤¹¤ë¤³¤È¤Ç¡¢¸½ºßÄ󶡤·¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤Ë¤Ä¤¤¤Æ¤Î¾ðÊ󤬯À¤é¤ì¤Þ¤¹¡£
2) create a metainfo file using btmakemetafile.py
2) btmakemetafile.py¤òÍѤ¤¤Æ¥á¥¿¾ðÊó¥Õ¥¡¥¤¥ë¤òÀ¸À®¤¹¤ë¡£
To generate a metainfo file, run the publish btmakemetafile and give
it the file you want metainfo for and the url of the tracker
¥á¥¿¾ðÊó¥Õ¥¡¥¤¥ë¤òÀ¸À®¤¹¤ë¤Ë¤Ï¡¢¸ø³«¤¹¤ë btmakemetafile ¤ò¼Â¹Ô¤·¡¢¥Õ¥¡
¥¤¥ë¤Ë´õ˾¤¹¤ë¥á¥¿¾ðÊó¤È¥È¥é¥Ã¥«¡¼¤Î URL ¤òÍ¿¤¨¤Þ¤¹¡£
./btmakemetafile.py myfile.ext http://my.tracker:6969/announce
This will generate a file called myfile.ext.torrent
¤³¤ì¤Ç, myfile.ext.torrent ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤¬À¸À®¤µ¤ì¤Þ¤¹¡£
Make sure to include the port number in the tracker url if it isn't 80.
(ÌõÃí¡¥ httpd ¤¬ÂÔµ¡¤¹¤ë¥Ý¡¼¥ÈÈֹ椬) 80 ¤Ç¤Ï¤Ê¤¤¾ì¹ç¡¢¥È¥é¥Ã¥«¡¼¤Î URL
¤Ë¥Ý¡¼¥ÈÈֹ椬´Þ¤Þ¤ì¤Æ¤¤¤ë¤«³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
This command may take a while to scan over the whole file hashing it.
¤³¤Î¥³¥Þ¥ó¥É¤Ï¡¢¥Õ¥¡¥¤¥ëÁ´ÂΤòÁöºº¤·¤Æ¡¢¥Ï¥Ã¥·¥å¤·¤Æ¤æ¤¯¤Î¤Ç¡¢
¤·¤Ð¤é¤¯»þ´Ö¤¬¤«¤«¤ë¤Ç¤·¤ç¤¦¡£
The /announce path is special and hard-coded into the tracker.
Make sure to give the domain or ip your tracker is on instead of
my.tracker.
/announce ¤È¤¤¤¦¥Ñ¥¹¤ÏÆÃÊ̤ǡ¤¥È¥é¥Ã¥«¡¼¤ËËä¤á¹þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
my.tracker ¤ÎÂå¤ï¤ê¤Ë¡¢¥È¥é¥Ã¥«¡¼¤Î¥É¥á¥¤¥ó¤« IP ¤ò»ØÄꤷ¤Æ¤¤¤ë¤«¤ò
³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
You can use either a dns name or an IP address in the tracker url.
¥È¥é¥Ã¥«¡¼¤ÎURL¤ÎÂå¤ï¤ê¤Ë DNS ̾¤ä IP ¥¢¥É¥ì¥¹¤ò»È¤¦¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
3) associate .torrent with application/x-bittorrent on your web server
3) .torrent (¤È¤¤¤¦³ÈÄ¥»Ò) ¤ò¡¢¤¢¤Ê¤¿¤Î¥¦¥§¥Ö¥µ¡¼¥Ð¤Î
application/x-bittorrent ¤Ø·ë¤Ó¤Ä¤±¤Þ¤¹¡£
The way you do this is dependent on the particular web server you're using.
¤³¤ÎÊýË¡¤Ï¡¢¤¢¤Ê¤¿¤¬»È¤Ã¤Æ¤¤¤ëÆÃÄê¤Î¥¦¥§¥Ö¥µ¡¼¥Ð¤Ë°Í¸¤·¤Þ¤¹¡£
You must have a web server which can serve ordinary static files and is
addressable from the internet at large.
¤¢¤Ê¤¿¤Ï¡¢ÉáÄ̤ÎÀÅŪ¤Ê¥Õ¥¡¥¤¥ë¤òÄ󶡤Ǥ¡¢°ìÈ̤˥¤¥ó¥¿¡¼¥Í¥Ã¥È¤«¤é¥¢¥¯
¥»¥¹²Äǽ¤Ç¤¢¤ëWeb¥µ¡¼¥Ð¤ò»ý¤Ã¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
4) put the newly made .torrent file on your web server
4) ¿·¤·¤¯ºîÀ®¤·¤¿¡¢.torrent ¥Õ¥¡¥¤¥ë¤ò¥¦¥§¥Ö¥µ¡¼¥Ð¤Î¾å¤ËÇÛÃÖ¤·¤Þ¤¹¡£
Note that the file name you choose on the server must end in .torrent, so
it gets associated with the right mimetype.
Ãí. ¥Õ¥¡¥¤¥ë̾¤«¤éŬÀÚ¤Ê mimetype ¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤ë¤è¤¦¤Ë¡¢
¥µ¡¼¥Ð¤Ë¤¢¤ëÁªÂò¤·¤¿¥Õ¥¡¥¤¥ë̾¤Ï .torrent ¤Ç½ª¤ï¤Ã¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
5) put up a static page which links to the location you uploaded to in step 4
5) ¥¹¥Æ¥Ã¥×4¤Ë¤¢¤ë¡¢¤¢¤Ê¤¿¤¬¥¢¥Ã¥×¥í¡¼¥É¤·¤¿¾ì½ê¤Ø¤Î¥ê¥ó¥¯¤¬¤¢¤ëÀÅŪ¤Ê
(ÌõÃí¡¥HTML) ¥Ú¡¼¥¸¤òÇÛÃÖ¤·¤Þ¤¹¡£
The file you uploaded in step 4 is linked to using an ordinary url.
¥¹¥Æ¥Ã¥×4¤Ë¤¢¤ë¤¢¤Ê¤¿¤¬¥¢¥Ã¥×¥í¡¼¥É¤·¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤Ï¡¢Ä̾ï¤ÎURL¤È¤·¤Æ
ÍøÍѤ·¤Æ¥ê¥ó¥¯¤·¤Æ¤¤¤Þ¤¹¡£
6) start a downloader as a resume on the complete file
6) ¥À¥¦¥ó¥í¡¼¥À¡¼¤òµ¯Æ°¤·¤Æ´°Á´¤Ê¥Õ¥¡¥¤¥ë¤ò¥ì¥¸¥å¡¼¥à¤·¤Þ¤¹
You have to run a downloader which already has the complete file,
so new downloaders have a place to get it from. Here's an example -
¤¢¤Ê¤¿¤Ï¡¢¤¹¤Ç¤Ë¤â¤Ã¤Æ¤¤¤ë´°Á´¤Ê¥Õ¥¡¥¤¥ë¤òÂоݤ˥¿¥¦¥ó¥í¡¼¥À¡¼¤ò¼Â¹Ô¤·
¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£
./btdownloadheadless.py --url http://my.server/myfile.torrent --saveas myfile.ext
Make sure the saveas argument points to the already complete file.
saveas °ú¿ô¤Ë¤Ï´û¤Ë´°Á´¤Ê¥Õ¥¡¥¤¥ë¤ò»ØÄꤹ¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
If you're running the complete downloader on the same machine or LAN as
the tracker, give a --ip parameter to the complete downloader. The --ip
parameter can be either an IP address or DNS name.
¤â¤·¡¢Æ±¤¸¥Þ¥·¥ó¤Î¾å¤äLAN¤Ç¥È¥é¥Ã¥«¡¼¤È¤·¤Æ¡¢´°Á´¤Ë (¥Õ¥¡¥¤¥ë¤ò¼èÆÀ
¤·¤Æ¤¤¤ë) ¥À¥¦¥ó¥í¡¼¥À¡¼¤ò¼Â¹Ô¤·¤Æ¤¤¤ë¤Ê¤é¡¢--ip ¥Ñ¥é¥á¥¿¤Ë¤Ï¡¤´°Á´
(ÌõÃí¡¥¤Ë¥Õ¥¡¥¤¥ë¤ò¼èÆÀºÑ¤ß¤Î) ¥À¥¦¥ó¥í¡¼¥À¡¼¤ò»ØÄꤷ¤Æ¤¯¤À¤µ¤¤¡£
¤³¤Î --ip ¥Ñ¥é¥á¡¼¥¿¤Ï¡¢IP ¥¢¥É¥ì¥¹¤ä DNS ̾¤Î¤É¤Á¤é¤Ç¤â¤è¤¤¤Ç¤¹¡£
BitTorrent defaults to port 6881. If it can't use 6881, (probably because
another download is happening) it tries 6882, then 6883, etc. It gives up
after 6889.
BitTorrent ¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Ç 6881 ¤Î¥Ý¡¼¥È¤òÍøÍѤ·¤Þ¤¹¡£¤â¤·¡¢6881 ¥Ý¡¼¥È
¤¬ÍøÍѤǤ¤Ê¤¤¤Ê¤é¡¢(¿ʬ¡¢Ê̤ΥÀ¥¦¥ó¥í¡¼¥É¤¬È¯À¸¤·¤Æ¤¤¤ë¤Î¤Ç¤·¤ç¤¦)
BitTorrent ¤Ï¡¢6882 ¤ò»î¤·¤Æ¡¢¼¡¤Ë 6883 ¤ò»î¤·¤Þ¤¹¡£BitTorrent ¤Ï¡¢
6889 ¤Þ¤Ç¤ò»È¤¤¤Þ¤¹¡£
7) you're done!
7) ´°Î»¤Ç¤¹¡£
Now you just have to get people downloading! Refer them to the page you
created in step 5.
ï¤â¤¬¥À¥¦¥ó¥í¡¼¥É¤Ç¤¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿!
¥¹¥Æ¥Ã¥× 5 ¤ÇºîÀ®¤·¤¿¥Ú¡¼¥¸¤ò»²¾È¤µ¤»¤Æ¤¯¤À¤µ¤¤¡£
BitTorrent can also publish whole directories - simply point
btmakemetafile.py at the directory with files in it, they'll be published
as one unit. All files in subdirectories will be included, although files
and directories named 'CVS' and 'core' are ignored.
BitTorrent ¤Ï¡¢¥Ç¥£¥ì¥¯¥È¥êÁ´ÂΤò¸ø³«¤¹¤ë¤³¤È¤â¤Ç¤¤Þ¤¹¡£-
ñ¤Ë¡¢btmakemetafile.py (ÌõÃí¡¥¤Î°ú¿ô) ¤Ë¡¢¥Õ¥¡¥¤¥ë¤ò´Þ¤à¥Ç¥£¥ì¥¯¥È¥ê
¤ò»ØÄꤹ¤ë¤À¤±¤Ç¤¹¡£1 ¤Ä¤Îñ°Ì¤È¤·¤Æ¸ø³«¤µ¤ì¤Þ¤¹¡£¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë
¤¢¤ëÁ´¤Æ¤Î¥Õ¥¡¥¤¥ë¤â´Þ¤Þ¤ì¤Þ¤¹¤¬¡¢'CVS' ¤ä 'core' ¤È¤¤¤¦¥Õ¥¡¥¤¥ë̾¤ä
¥Ç¥£¥ì¥¯¥È¥ê̾¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£
If you have any questions, try the web site or mailing list -
¤â¤·¼ÁÌ䤬¤¢¤ë¤Ê¤é¡¢Web ¥µ¥¤¥È¤ËˬÌ䤹¤ë¤«¡¢¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤òÆÉ¤ó¤Ç
¤¯¤À¤µ¤¤¡£
http://bitconjurer.org/BitTorrent/
http://groups.yahoo.com/group/BitTorrent
You can also often find me, Bram, in #bittorrent of irc.freenode.net
¤Þ¤¿¡¢irc.freenode.net¤Î#bittorrent¥Á¥ã¥ó¥Í¥ë¤Ë¤Æ¡¢¤ï¤¿¤·(Bram)¤ò¤ß¤Ä
¤±¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
ËÝÌõ Ìð¿á ¹¬¼£(yabuki good-day co jp)
¶ñÂÎŪ¤Ê¡¢´Ö°ã¤¤¤Î½¤Àµ°Æ¤Ï´¿·Þ¤·¤Þ¤¹¡£
ËÝÌõ½éÈÇ 2005/02/16 yabuki
¼Õ¼
Debian-doc¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ë¤ª¤¤¤Æ¡£»ä¤ÎÀÛ¤¤ËÝÌõ¤ËÉð°æ¿¸÷Íͤ«¤é
¿Âç¤Ê¤ë¥³¥á¥ó¥È¤òĺ¤¤Þ¤·¤¿¡£¤¢¤ê¤¬¤È¤¦¤´¤¶¤¤¤Þ¤¹¡£