diff options
Diffstat (limited to 'zh_TW.UTF-8/articles/hubs/article.xml')
| -rw-r--r-- | zh_TW.UTF-8/articles/hubs/article.xml | 520 |
1 files changed, 0 insertions, 520 deletions
diff --git a/zh_TW.UTF-8/articles/hubs/article.xml b/zh_TW.UTF-8/articles/hubs/article.xml deleted file mode 100644 index 5d87a92f21..0000000000 --- a/zh_TW.UTF-8/articles/hubs/article.xml +++ /dev/null @@ -1,520 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd"> -<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:its="http://www.w3.org/2005/11/its" version="5.0" xml:lang="zh_TW"> - <info><title>Mirroring FreeBSD</title> - - <authorgroup> - <author><personname><firstname>Jun</firstname><surname>Kuriyama</surname></personname><affiliation> <address><email>kuriyama@FreeBSD.org</email></address> </affiliation></author> - <author><personname><firstname>Valentino</firstname><surname>Vaschetto</surname></personname><affiliation> <address><email>logo@FreeBSD.org</email></address> </affiliation></author> - <author><personname><firstname>Daniel</firstname><surname>Lang</surname></personname><affiliation> <address><email>dl@leo.org</email></address> </affiliation></author> - <author><personname><firstname>Daniel</firstname><surname>Lang</surname></personname><affiliation> <address><email>kensmith@FreeBSD.org</email></address> </affiliation></author> - </authorgroup> - - <legalnotice xml:id="trademarks" role="trademarks"> - <para>FreeBSD 是 FreeBSD基金會的註冊商標.</para> - <para>許多製造商和經銷商使用一些稱為商標的圖案或文字設計來彰顯自己的產品.本文中出現的眾多商標,以及 FreeBSD Project 本身廣所人知的商標,後面將以 <quote>™</quote> 或 <quote>®</quote> 符號來標註.</para> - </legalnotice> - - <pubdate xml:lang="en">$FreeBSD$</pubdate> - - <releaseinfo xml:lang="en">$FreeBSD$</releaseinfo> - - <abstract> - <para>這是份介紹如何 mirror FreeBSD,主要是針對網路中心管理者或託管於大型資料中心的管理者.</para> - </abstract> - </info> - - <note> - <para>我們目前不接受新Mirror站點的申請.</para> - </note> - - <sect1 xml:id="mirror-contact"> - <title>聯繫方式</title> - - <para xml:lang="en">The Mirror System Coordinators can be reached through email - at <email>mirror-admin@FreeBSD.org</email>. There is also - a <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-hubs">FreeBSD mirror sites mailing lists</link>.</para> - </sect1> - - <sect1 xml:id="mirror-requirements"> - <title>FreeBSD mirrors 的需求</title> - <sect2 xml:id="mirror-diskspace"> - <title>磁碟空間</title> - <para>磁碟空間是最為需要. 根據你想要 mirror 的發行版、CPU架構 ,可能會消耗大量的磁碟空間.另外請注意 <emphasis>官方</emphasis> 鏡像站需要完整 mirror。網站內容亦需要完整鏡像。且這裡所述的數字是反應目前版本狀態 (如 10.4-RELEASE/11.1-RELEASE )。而不斷的開發與發行將會增加所需空間。並請務必保留一些 ( 約10-20% ) 額外空間。這裡大約估計如下：</para> - <itemizedlist> - <listitem><para>完整的作業系統套件 FTP 站所需：1.4 TB</para></listitem> - <listitem><para>CTM deltas： 10 GB</para></listitem> - <listitem><para>網站： 1GB</para></listitem> - </itemizedlist> - <para>目前 FTP Distribution 的磁碟使用可在 <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/dir.sizes">ftp://ftp.FreeBSD.org/pub/FreeBSD/dir.sizes</link> 找到。</para> - </sect2> - <sect2 xml:id="mirror-bandwidth"> - <title>網路連線/頻寬</title> - <para>當然，你一定要能連上 Internet。 頻寬需求多少，這要看你所想要的 mirror 程度而定。 若只想要 mirror 一部份的 FreeBSD 檔案以作為網站或 intranet 的局部用途， 那麼頻寬需求會明顯比成為公共服務用途的小一些。 若想成為 official mirror 之一的話，那麼頻寬就勢必得增加才夠用。以下，我們僅列出一些估計值以做為參考： </para> - <itemizedlist> - <listitem><para>本地站台，沒有要公共存取： 基本上沒有最低需求，但是 < 2Mbps 同步將會非常緩慢</para></listitem> - <listitem><para>非官方公共站台: 34Mbps 是不錯的開始.</para></listitem> - <listitem><para>官方站台: > 100Mbps 是建議值,並且你的主機必須盡可能連接靠近邊界路由器.</para></listitem> - </itemizedlist> - </sect2> - <sect2 xml:id="mirror-system"> - <title>系統需求，CPU，RAM</title> - <para>這取決於預期的客戶端數量,這是由伺服器的策略決定的。也會受到您提供的服務類型而影響.普通的 FTP 或 HTTP 服務可能不需要大量的資源。注意如果您提供rsync. 這可能會對 CPU 和記憶體的需求產生巨大的影響，因為會消耗大量記憶體。 以下只是給你一個非常粗略的的例子。</para> - <para>針對一個較常被瀏覽的網站 <application>rsync</application>，您須考量處理器大約 800Mhz 至 1Ghz，並且安裝最少 512MB RAM，這或許是成為一個 <emphasis>官方</emphasis> 站台的最小需求.</para> - <para>為了一個經常使用的網站你絕對需要更多 RAM (2GB是不錯的開始) 並且儘可能有更多 CPU ， 這也表示你需要一個 SMP 系統。</para> - <para>您也會需要考慮有一個較快的磁碟系統。在管理 SVN repository 需要一個快速的磁碟系統 ( 強烈建議 RAID)。有自己的快取記憶體的 SCSI 控制器也可以加快速度，因為大多數這些服務會對磁碟進行大量的小幅修改。</para> - </sect2> - <sect2 xml:id="mirror-services"> - <title>提供的服務</title> - <para>每個鏡像站都需要一有一組可用的核心服務。除了這些所需的服務之外，還有許多伺服器管理員可以選擇提供的選用服務。本節將說明您可以提供哪些服務以及如何實作這些服務。</para> - <sect3 xml:id="mirror-serv-ftp"> - <title>FTP (需要提供給FTP檔案集)</title> - <para>這是最基本的服務之一。需要為每個鏡像站提供公共的 FTP distributions 。 FTP 存取必須是匿名的， 不允許上傳/下載比率 （這是一件荒謬的事），上傳功能不是必需的 （且<emphasis>必須 </emphasis>絕不允許 FreeBSD 檔案空間）。另外，FreeBSD archive 應該在路徑<filename>/pub/FreeBSD</filename>下。</para> - <para>這裡有很多可用的軟體可以架設允許匿名的 FTP 服務 （按字母順序）。</para> - <itemizedlist> - <listitem><para><command>/usr/libexec/ftpd</command>: FreeBSD 內建的 ftpd 可以使用。請您參閱 <citerefentry><refentrytitle>ftpd</refentrytitle><manvolnum>8</manvolnum></citerefentry>。</para> - </listitem> - <listitem> - <para><package>ftp/ncftpd</package>。一個商業軟體套件，免費供教育使用。</para> - </listitem> - <listitem> - <para><package>ftp/oftpd</package>：一個以安全性作為主要考量的 ftpd。</para> - </listitem> - <listitem> - <para><package>ftp/proftpd</package>：一個模組化且非常有彈性的 ftpd。</para> - </listitem> - <listitem> - <para><package>ftp/pure-ftpd</package>: 另一個為安全所設計的 ftpd。</para> - </listitem> - <listitem><para><package>ftp/twoftpd</package>：如上。</para></listitem> - <listitem><para><package>ftp/vsftpd</package>：<quote>非常安全的</quote> ftpd。</para></listitem> - </itemizedlist> - <para>FreeBSD 的 <application>ftpd</application>、<application>proftpd</application> 和也許 <application>ncftpd</application> 是最常使用的 FTP 軟體。其他的在鏡像站並沒有大量用戶基礎。需要考慮的一件事情是,您可能需要性地來限制允許同時連線數，從而限制消耗多少網路頻寬和系統資源。</para> - </sect3> - <sect3 xml:id="mirror-serv-rsync"> - <title>Rsync (給FTP檔案集選用)</title> - <para><application>Rsync</application> 通常是用在存取 FreeBSD 系統中的FTP內容，其他的鏡像站可以使用你的系統當作他們的來源。這個協定和 FTP 有很多不同，它比較不那麼消耗頻寬，只有當比對檔案間有變動才傳輸檔案，而不是整個檔案傳完。<application>Rsync</application> 需要較多的記憶體。大小取決於檔案與目錄的數目及同步模組大小。<application>Rsync</application> 可以使用 <command>rsh</command> 和 <command>ssh</command> （現在為預設）來傳輸， 或使用自己的協定單獨存取（這是公共rsync伺服器的首選方法）。可以用認證、連接限制和其他限制。只有一個軟體套件可以用：</para> - <itemizedlist> - <listitem><para><package>net/rsync</package></para></listitem> - </itemizedlist> - </sect3> - <sect3 xml:id="mirror-serv-http"> - <title>HTTP（網頁需要，FTP 檔案集則是選用）</title> - <para>如果您想提供 FreeBSD 的網頁，您需要安裝一個網頁伺服器。您可以選擇利用 HTTP 提供 FTP 檔案集。網頁伺服器軟體的選擇留給鏡像站管理員選擇。一些最受歡迎的選擇是：</para> - - <itemizedlist> - <listitem> - <para><package>www/apache22</package>：<application>Apache</application> 是網際網路上最廣泛使用的網頁伺服器。 它被 FreeBSD 計畫廣泛使用。</para> - </listitem> - - <listitem> - <para><package>www/thttpd</package>：如果您要提供大量的靜態內容，您可能會發現使用諸如 thttpd 之類的應用程式會比 <application>Apache</application> 更有效率。它針對 FreeBSD 的優秀性能進行了最佳化。</para> - </listitem> - - <listitem> - <para><package>www/boa</package>：<application>Boa</application> 是 <application>thttpd</application> 和 <application>Apache</application> 外的另一個選擇。對於純粹的靜態網頁，它應該會提供比 <application>Apache</application> 更好的性能。在寫這篇文章的時候，它並不包含像在 <application>thttpd</application> 中一樣針對FreeBSD 做最佳化。</para> - </listitem> - - <listitem> - <para><package>www/nginx</package>：<application>Nginx</application> 是一款高性能的最新網頁服務器，具有低記憶體佔用量和關鍵特色，可以構建現代高效率網頁基礎架構，功能包括 HTTP 伺服器，HTTP 和郵件反向代理，快取，負載平衡，壓縮，請求限制(request throtting)，連接多工與再利用，SSL 卸載和 HTTP 媒體串流。</para> - </listitem> - </itemizedlist> - </sect3> - </sect2> - </sect1> - <sect1 xml:id="mirror-howto"> - <title>如何Mirror FreeBSD 站台</title> - <para>好，現在你知道硬體需求和如何提供服務，但不知道如何做。:-) 這節將解釋如何實際 mirror FreeBSD 的不同部分，使用哪些工具以及從哪裡 mirror。</para> - <sect2 xml:id="mirror-ftp-rsync"> - <title>鏡像 FTP 站</title> - <para>FTP 部份有最大量的資料需要被 mirror。它包括網路安裝所需的<emphasis>發布集</emphasis>，實際上是原始碼樹快照的<emphasis>分支</emphasis>，可燒錄光碟供安裝系統的<emphasis>ISO映像檔</emphasis> ，一個可 live 開機的檔案系統，以及一個 port tree 的快照。當然，全都有各種 FreeBSD 版本和各種CPU架構。</para> - <para xml:lang="en"> - The best way to mirror the FTP area is <application>rsync</application>. - You can install the port <package>net/rsync</package> and then use - rsync to sync with your upstream host. - <application>rsync</application> is already mentioned - in <xref linkend="mirror-serv-rsync"/>. - Since <application>rsync</application> access is not - required, your preferred upstream site may not allow it. - You may need to hunt around a little bit to find a site - that allows <application>rsync</application> access.</para> - <note> - <para>由於 <application>rsync</application> 客戶端的數量將對伺服器主機產生重大影響，因此大多數管理員會對伺服器負荷加以限制。對於 mirror 站台，您應該詢問您要 mirror 站台的管理人員他們的管理政策，也許需要對您的主機開放例外（因為您是一個 mirror 站）。</para> - </note> - <para>一個需要mirror FreeBSD官網的指令如下:</para> - <screen><prompt>%</prompt> <userinput>rsync -vaHz --delete rsync://ftp4.de.FreeBSD.org/FreeBSD/ /pub/FreeBSD/</userinput></screen> - <para xml:lang="en">Consult the documentation for <application>rsync</application>, - which is also available at - <link xlink:href="http://rsync.samba.org/">http://rsync.samba.org/</link>, - about the various options to be used with rsync. - If you sync the whole module (unlike subdirectories), - be aware that the module-directory (here "FreeBSD") - will not be created, so you cannot omit the target directory. - Also you might - want to set up a script framework that calls such a command - via <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry>. - </para> - </sect2> - <sect2 xml:id="mirror-www"> - <title>Mirroring 網頁</title> - <para>FreeBSD 網站應只能透過<application>rsync</application>指令來mirror.</para> - <para>一個 mirror FreeBSD 網站的指令應該看起像這樣：</para> - <screen><prompt>%</prompt> <userinput>rsync -vaHz --delete rsync://bit0.us-west.freebsd.org/FreeBSD-www-data/ /usr/local/www/</userinput></screen> - </sect2> - <sect2 xml:id="mirror-pkgs"> - <title>Mirroring 套件</title> - <para>由於對頻寬，儲存空間和管理的要求非常高，FreeBSD 計畫決定不允許公眾 mirror 套件. 對於擁有大量伺服主機的網站，建議為 <citerefentry><refentrytitle>pkg</refentrytitle><manvolnum>8</manvolnum></citerefentry> 使用 HTTP proxy 快取可能會有所幫助。或者，您可以使用以下指令獲得套件與相依套件：</para> - - <screen><prompt>%</prompt> <userinput>pkg fetch -d -o <replaceable>/usr/local/mirror</replaceable> <replaceable>vim</replaceable></userinput></screen> - - <para>一旦這些套件包被下載，就必須執行以下命令來產生套件庫數據：</para> - - <screen><prompt>%</prompt> <userinput>pkg repo <replaceable>/usr/local/mirror</replaceable></userinput></screen> - - <para>一旦套件被下載並且已經生成了套件庫的數據，就可以透過 HTTP 協定將套件提供給客戶端機器。有關更多訊息，請參閱 <citerefentry><refentrytitle>pkg</refentrytitle><manvolnum>8</manvolnum></citerefentry> 的 man pages，特別是<citerefentry><refentrytitle>pkg-repo</refentrytitle><manvolnum>8</manvolnum></citerefentry> 頁面。</para> - </sect2> - <sect2 xml:id="mirror-how-often"> - <title>我多久應該mirror?</title> - <para xml:lang="en"> - Every mirror should be updated at a minimum of once per day. - Certainly a script with locking to prevent multiple runs - happening at the same time will be needed to run from - <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Since nearly every admin does this in their own - way, specific instructions cannot be provided. It could work - something like this: - </para> - <procedure> - <step> - <para xml:lang="en"> - Put the command to run your mirroring application - in a script. Use of a plain <command>/bin/sh</command> - script is recommended. - </para> - </step> - <step> - <para xml:lang="en"> - Add some output redirections so diagnostic - messages are logged to a file. - </para> - </step> - <step> - <para xml:lang="en"> - Test if your script works. Check the logs. - </para> - </step> - <step> - <para xml:lang="en"> - Use <citerefentry><refentrytitle>crontab</refentrytitle><manvolnum>1</manvolnum></citerefentry> to add the script to the - appropriate user's <citerefentry><refentrytitle>crontab</refentrytitle><manvolnum>5</manvolnum></citerefentry>. This should be a - different user than what your FTP daemon runs as so that - if file permissions inside your FTP area are not - world-readable those files can not be accessed by anonymous - FTP. This is used to <quote>stage</quote> releases — - making sure all of the official mirror sites have all of the - necessary release files on release day. - </para> - </step> - </procedure> - <para xml:lang="en"> - Here are some recommended schedules:</para> - <itemizedlist> - <listitem><para xml:lang="en">FTP fileset: daily</para></listitem> - <listitem><para xml:lang="en">WWW pages: daily</para></listitem> - </itemizedlist> - </sect2> - </sect1> - <sect1 xml:id="mirror-where"> - <title xml:lang="en">Where to mirror from</title> - <para xml:lang="en"> - This is an important issue. So this section will - spend some effort to explain the backgrounds. We will say this - several times: under no circumstances should you mirror from - <systemitem class="fqdomainname">ftp.FreeBSD.org</systemitem>. - </para> - <sect2 xml:id="mirror-where-organization"> - <title xml:lang="en">A few words about the organization</title> - <para xml:lang="en"> - Mirrors are organized by country. All - official mirrors have a DNS entry of the form - <systemitem class="fqdomainname">ftpN.CC.FreeBSD.org</systemitem>. - <emphasis>CC</emphasis> (i.e. country code) is the - <emphasis>top level domain</emphasis> (TLD) - of the country where this mirror is located. - <emphasis>N</emphasis> is a number, - telling that the host would be the <emphasis>Nth</emphasis> - mirror in that country. - (Same applies to - <systemitem>wwwN.CC.FreeBSD.org</systemitem>, etc.) - There are mirrors with no <emphasis>CC</emphasis> part. - These are the mirror sites that are very well connected and - allow a large number of concurrent users. - <systemitem class="fqdomainname">ftp.FreeBSD.org</systemitem> is actually two machines, one currently - located in Denmark and the other in the United States. - It is <emphasis>NOT</emphasis> a master site and should never be - used to mirror from. Lots of online documentation leads - <quote>interactive</quote>users to - <systemitem class="fqdomainname">ftp.FreeBSD.org</systemitem> so automated mirroring - systems should find a different machine to mirror from. - </para> - <para xml:lang="en"> - Additionally there exists a hierarchy of mirrors, which - is described in terms of <emphasis>tiers</emphasis>. - The master sites are not referred to but can be - described as <emphasis>Tier-0</emphasis>. Mirrors - that mirror from these sites can be considered - <emphasis>Tier-1</emphasis>, mirrors of <emphasis>Tier-1</emphasis>-mirrors, - are <emphasis>Tier-2</emphasis>, etc. - Official sites are encouraged to be of a low <emphasis>tier</emphasis>, - but the lower the tier the higher the requirements in - terms as described in <xref linkend="mirror-requirements"/>. - Also access to low-tier-mirrors may be restricted, and - access to master sites is definitely restricted. - The <emphasis>tier</emphasis>-hierarchy is not reflected - by DNS and generally not documented anywhere except - for the master sites. However, official mirrors with low numbers - like 1-4, are usually <emphasis>Tier-1</emphasis> - (this is just a rough hint, and there is no rule). - </para> - </sect2> - <sect2 xml:id="mirror-where-where"> - <title xml:lang="en">Ok, but where should I get the stuff now?</title> - <para xml:lang="en"> - Under no circumstances should you mirror from <systemitem class="fqdomainname">ftp.FreeBSD.org</systemitem>. - The short answer is: from the - site that is closest to you in Internet terms, or gives you - the fastest access. - </para> - <sect3 xml:id="mirror-where-simple"> - <title xml:lang="en">I just want to mirror from somewhere!</title> - <para xml:lang="en"> - If you have no special intentions or - requirements, the statement in <xref linkend="mirror-where-where"/> - applies. This means: - </para> - <procedure> - <step> - <para xml:lang="en"> - Check for those which provide fastest access - (number of hops, round-trip-times) - and offer the services you intend to - use (like <application>rsync</application>). - </para> - </step> - <step> - <para xml:lang="en"> - Contact the administrators of your chosen site stating your - request, and asking about their terms and - policies. - </para> - </step> - <step> - <para xml:lang="en"> - Set up your mirror as described above. - </para> - </step> - </procedure> - </sect3> - <sect3 xml:id="mirror-where-official"> - <title xml:lang="en">I am an official mirror, what is the right site for me?</title> - <para xml:lang="en"> - In general the description in <xref linkend="mirror-where-simple"/> - still applies. Of course you may want to put some - weight on the fact that your upstream should be of - a low tier. - There are some other considerations about <emphasis>official</emphasis> - mirrors that are described in <xref linkend="mirror-official"/>. - </para> - </sect3> - <sect3 xml:id="mirror-where-master"> - <title xml:lang="en">I want to access the master sites!</title> - <para xml:lang="en"> - If you have good reasons and good prerequisites, - you may want and get access to one of the - master sites. Access to these sites is - generally restricted, and there are special policies - for access. If you are already an <emphasis>official</emphasis> - mirror, this certainly helps you getting access. - In any other case make sure your country really needs another mirror. - If it already has three or more, ask the <quote>zone administrator</quote> (<email>hostmaster@CC.FreeBSD.org</email>) or <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-hubs">FreeBSD mirror sites mailing lists</link> first.</para> - - <para xml:lang="en"> - Whoever helped you become, an <emphasis>official</emphasis> - should have helped you gain access to an appropriate upstream - host, either one of the master sites or a suitable Tier-1 - site. If not, you can send email to - <email>mirror-admin@FreeBSD.org</email> to request help with - that. - </para> - <para xml:lang="en"> - There is one master site for the FTP fileset. - </para> - <sect4 xml:id="mirror-where-master-ftp"> - <title xml:lang="en">ftp-master.FreeBSD.org</title> - <para xml:lang="en"> - This is the master site for the FTP fileset. - </para> - <para xml:lang="en"> - <systemitem>ftp-master.FreeBSD.org</systemitem> provides - <application>rsync</application> - access, in addition to FTP. - Refer to <xref linkend="mirror-ftp-rsync"/>. - </para> - <para xml:lang="en"> - Mirrors are also encouraged to allow <application>rsync</application> - access for the FTP contents, since they are - <emphasis>Tier-1</emphasis>-mirrors. - </para> - </sect4> - </sect3> - </sect2> - </sect1> - <sect1 xml:id="mirror-official"> - <title xml:lang="en">Official Mirrors</title> - <para xml:lang="en"> - Official mirrors are mirrors that</para> - <itemizedlist> - <listitem> - <para xml:lang="en"> - a) have a <systemitem>FreeBSD.org</systemitem> DNS entry - (usually a CNAME). - </para> - </listitem> - <listitem> - <para xml:lang="en"> - b) are listed as an official mirror in the FreeBSD - documentation (like handbook). - </para> - </listitem> - </itemizedlist> - - <para xml:lang="en">So far to distinguish official mirrors. - Official mirrors are not necessarily <emphasis>Tier-1</emphasis>-mirrors. - However you probably will not find a <emphasis>Tier-1</emphasis>-mirror, - that is not also official. - </para> - <sect2 xml:id="mirror-official-requirements"> - <title xml:lang="en">Special Requirements for official (tier-1) mirrors</title> - <para xml:lang="en"> - It is not so easy to state requirements for all - official mirrors, since the project is sort of - tolerant here. It is more easy to say, - what <emphasis>official tier-1 mirrors</emphasis> - are required to. All other official mirrors - can consider this a big <emphasis>should</emphasis>.</para> - <para xml:lang="en"> - Tier-1 mirrors are required to:</para> - <itemizedlist> - <listitem><para xml:lang="en">carry the complete fileset</para></listitem> - <listitem><para xml:lang="en">allow access to other mirror sites</para></listitem> - <listitem><para xml:lang="en">provide <application>FTP</application> and - <application>rsync</application> access</para></listitem> - </itemizedlist> - - <para xml:lang="en">Furthermore, admins should be subscribed to the <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-hubs">FreeBSD mirror sites mailing lists</link>. - See <link xlink:href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL">this link</link> for details, how to subscribe. - </para> - <important> - <para xml:lang="en">It is <emphasis>very</emphasis> important for a hub administrator, especially - Tier-1 hub admins, to check the - <link xlink:href="https://www.FreeBSD.org/releng/">release schedule</link> - for the next FreeBSD release. This is important because it will tell you when the - next release is scheduled - to come out, and thus giving you time to prepare for the big spike of traffic which follows it. - </para> - <para xml:lang="en"> - It is also important that hub administrators try to keep their mirrors as up-to-date as - possible (again, even more crucial for Tier-1 mirrors). If Mirror1 does not update for a - while, lower tier mirrors will begin to mirror old data from Mirror1 and thus begins - a downward spiral... Keep your mirrors up to date! - </para> - </important> - </sect2> - <sect2 xml:id="mirror-official-become"> - <title xml:lang="en">How to become official then?</title> - <!-- - <para> - An interesting question, especially, since the state - of being official comes with some benefits, like a much - higher bill from your ISP as more people will be using - your site. Also it may be a key requirement to get access - to a master site. - </para> - <para> - Before applying, please consider (again) if - another official mirror is really needed for - your region. Check first with your zone administrator (<email>hostmaster@CC.FreeBSD.org</email>) or, if that fails, ask on the &a.hubs;. - </para> - <para>Ok, here is how to do it:</para> - <procedure> - <step> - <para> - Get the mirror running in first place (maybe not - using a master site, yet). - </para> - </step> - <step> - <para> - <ulink url="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL">Subscribe</ulink> to the &a.hubs;. - </para> - </step> - <step> - <para> - If everything works so far, contact the DNS administrator responsible - for your region/country, and ask for a DNS entry for your - site. The admin should able to be contacted via - <email>hostmaster@CC.FreeBSD.org</email>, where - <emphasis>CC</emphasis> is your country code/TLD. - Your DNS entry will be as described - in <xref linkend="mirror-where-organization"/>. - </para> - <para> - If there is no subdomain set up for your - country yet, you should contact - <email>mirror-admin@FreeBSD.org</email>, - or you can try the &a.hubs; first. - </para> - </step> - <step> - <para> - Whoever helps you get an official name should send email - to <email>mirror-admin@FreeBSD.org</email> so your site will be - added to the mirror list in the - <ulink url="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook">FreeBSD - Handbook</ulink>. - </para> - </step> - </procedure> - <para>That is it.</para> - --> - <para xml:lang="en"> - We are not accepting any new mirrors at this time. - </para> - </sect2> - </sect1> - <sect1 xml:id="mirror-statpages"> - <title xml:lang="en">Some statistics from mirror sites</title> - <para xml:lang="en"> - Here are links to the stat pages of your favorite mirrors - (a.k.a. the only ones who feel like providing stats). - </para> - <sect2 xml:id="mirror-statpagesftp"> - <title xml:lang="en">FTP site statistics</title> - <itemizedlist> - <listitem> - <para xml:lang="en">ftp.is.FreeBSD.org - <email>hostmaster@is.FreeBSD.org</email> - - <link xlink:href="http://www.rhnet.is/status/draupnir/draupnir.html"> - (Bandwidth)</link> <link xlink:href="http://www.rhnet.is/status/ftp/ftp-notendur.html">(FTP - processes)</link> <link xlink:href="http://www.rhnet.is/status/ftp/http-notendur.html">(HTTP processes) - </link> - </para> - </listitem> - <listitem> - <para xml:lang="en">ftp2.ru.FreeBSD.org - <email>mirror@macomnet.ru</email> - - <link xlink:href="http://mirror.macomnet.net/mrtg/mirror.macomnet.net_195.128.64.25.html">(Bandwidth)</link> - <link xlink:href="http://mirror.macomnet.net/mrtg/mirror.macomnet.net_proc.html">(HTTP and FTP users)</link> - </para> - </listitem> - </itemizedlist> - </sect2> - </sect1> -</article> |