Date: Thu, 14 Dec 2017 12:03:22 +0000 (UTC) From: Ruey-Cherng Yu <rcyu@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r51308 - head/zh_TW.UTF-8/articles/hubs Message-ID: <201712141203.vBEC3M7M048728@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: rcyu Date: Thu Dec 14 12:03:21 2017 New Revision: 51308 URL: https://svnweb.freebsd.org/changeset/doc/51308 Log: - move the old translation strings to PO translation Added: head/zh_TW.UTF-8/articles/hubs/zh_TW.po (contents, props changed) Modified: head/zh_TW.UTF-8/articles/hubs/article.xml Modified: head/zh_TW.UTF-8/articles/hubs/article.xml ============================================================================== --- head/zh_TW.UTF-8/articles/hubs/article.xml Thu Dec 14 12:01:40 2017 (r51307) +++ head/zh_TW.UTF-8/articles/hubs/article.xml Thu Dec 14 12:03:21 2017 (r51308) @@ -1,33 +1,26 @@ <?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">; -<!-- $FreeBSD$ --> -<!-- The FreeBSD Documentation Project --> -<!-- Mirroring FreeBSD --> -<!-- Translate into Chinese by chinsan.tw@gmail.com --> -<!-- English Version: 1.62 --> -<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="zh_tw"> - <info><title>Mirroring FreeBSD</title> +<!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 xml:lang="en">Mirroring FreeBSD</title> <authorgroup> - <author><personname><firstname>Jun</firstname><surname>Kuriyama</surname></personname><affiliation> - <address><email>kuriyama@FreeBSD.org</email></address> + <author xml:lang="en"><personname><firstname>Jun</firstname><surname>Kuriyama</surname></personname><affiliation> + <address xml:lang="en"><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> + <author xml:lang="en"><personname><firstname>Valentino</firstname><surname>Vaschetto</surname></personname><affiliation> + <address xml:lang="en"><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> + <author xml:lang="en"><personname><firstname>Daniel</firstname><surname>Lang</surname></personname><affiliation> + <address xml:lang="en"><email>dl@leo.org</email></address> </affiliation></author> - <author><personname><firstname>Ken</firstname><surname>Smith</surname></personname><affiliation> - <address><email>kensmith@FreeBSD.org</email></address> + <author xml:lang="en"><personname><firstname>Ken</firstname><surname>Smith</surname></personname><affiliation> + <address xml:lang="en"><email>kensmith@FreeBSD.org</email></address> </affiliation></author> </authorgroup> <legalnotice xml:id="trademarks" role="trademarks"> - &tm-attrib.freebsd; - &tm-attrib.cvsup; - &tm-attrib.general; + <para>FreeBSD 是 FreeBSD基金會的註冊商標</para> + <para>許多製造商和經銷商使用一些稱為商標的圖案或文字設計來彰顯自己的產品。 本文中出現的眾多商標，以及 FreeBSD Project 本身廣所人知的商標，後面將以 <quote>™</quote> 或 <quote>®</quote> 符號來標註。</para> </legalnotice> <pubdate>$FreeBSD$</pubdate> @@ -39,90 +32,75 @@ </abstract> </info> + <note> + <para xml:lang="en">We are not accepting new mirrors at this time.</para> + </note> + <sect1 xml:id="mirror-contact"> <title>聯繫方式</title> - <para>若要找整個 Mirror 機制的協調者，可以 email 到 <email>mirror-admin@FreeBSD.org</email>。此外，這裡也有份 - &a.hubs;。</para> + <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> - 硬碟空間是最重要的必備條件之一。 - Depending on the set of releases, architectures, - and degree of completeness you want to mirror, a huge - amount of disk space may be consumed. Also keep in mind - that <emphasis>official</emphasis> mirrors are probably required to be - complete. The CVS repository and the web pages should - always be mirrored completely. Also note that the - numbers stated here are reflecting the current - state (at &rel2.current;-RELEASE/&rel.current;-RELEASE). Further development and - releases will only increase the required amount. - Also make sure to keep some (ca. 10-20%) extra space - around just to be sure. - Here are some approximate figures: - </para> + <para>硬碟空間是最重要的必備條件之一。 Depending on the set of releases, architectures, and degree of completeness you want to mirror, a huge amount of disk space may be consumed. Also keep in mind that <emphasis>official</emphasis> mirrors are probably required to be complete. The web pages should always be mirrored completely. Also note that the numbers stated here are reflecting the current state (at 10.4-RELEASE/11.1-RELEASE). Further development and releases will only increase the required amount. Also make sure to keep some (ca. 10-20%) extra space around just to be sure. Here are some approximate figures:</para> <itemizedlist> - <listitem><para>完整 FTP Distribution: 126 GB</para></listitem> - <listitem><para>CVS repository: 2.7 GB</para></listitem> - <listitem><para>CTM deltas: 1.8 GB</para></listitem> - <listitem><para>Web pages: 300 MB</para></listitem> + <listitem><para xml:lang="en">Full FTP Distribution: 1.4 TB</para></listitem> + <listitem><para xml:lang="en">CTM deltas: 10 GB</para></listitem> + <listitem><para xml:lang="en">Web pages: 1GB</para></listitem> </itemizedlist> + <para xml:lang="en"> + The current disk usage of FTP Distribution can be found at + <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> + <para>當然，你一定要能連上 Internet。 頻寬需求多少，這要看你所想要的 mirror 程度而定。 若只想要 mirror 一部份的 FreeBSD 檔案以作為網站或 intranet 的局部用途， 那麼頻寬需求會明顯比成為公共服務用途的小一些。 若想成為 official mirror 之一的話，那麼頻寬就勢必得增加才夠用。以下，我們僅列出一些估計值以做為參考： </para> <itemizedlist> - <listitem><para>Local site, no public access: basically no minimum, + <listitem><para xml:lang="en">Local site, no public access: basically no minimum, but < 2 Mbps could make syncing too slow.</para></listitem> - <listitem><para>Unofficial public site: 34 Mbps is probably a good start.</para></listitem> - <listitem><para>Official site: > 100 Mbps is recommended, and your host + <listitem><para xml:lang="en">Unofficial public site: 34 Mbps is probably a good start.</para></listitem> + <listitem><para xml:lang="en">Official site: > 100 Mbps is recommended, and your host should be connected as close as possible to your border router.</para></listitem> </itemizedlist> </sect2> <sect2 xml:id="mirror-system"> <title>系統需求、CPU、RAM</title> - <para> + <para xml:lang="en"> One thing this depends on the expected number of clients, which is determined by the server's policy. It is also affected by the types of services you want to offer. Plain FTP or HTTP services may not require a huge amount of resources. Watch out if you provide - CVSup, rsync or even AnonCVS. This can have a huge - impact on CPU and memory requirements. Especially - rsync is considered a memory hog, and CVSup does - indeed consume some CPU. For AnonCVS it might - be a nice idea to set up a memory resident file system (MFS) of at least - 300 MB, so you need to take this into account - for your memory requirements. The following + rsync. This can have a huge + impact on CPU and memory requirements as it is + considered a memory hog. + The following are just examples to give you a very rough hint. </para> - <para> + <para xml:lang="en"> For a moderately visited site that offers - <application>Rsync</application>, you might + <application>rsync</application>, you might consider a current CPU with around 800MHz - 1 GHz, and at least 512MB RAM. This is probably the minimum you want for an <emphasis>official</emphasis> site. </para> - <para> + <para xml:lang="en"> For a frequently used site you definitely need more RAM (consider 2GB as a good start) and possibly more CPU, which could also mean that you need to go for a SMP system. </para> - <para> + <para xml:lang="en"> You also want to consider a fast disk subsystem. - Operations on the CVS repository require a fast + Operations on the SVN repository require a fast disk subsystem (RAID is highly advised). A SCSI controller that has a cache of its own can also speed up things since most of these services incur a @@ -130,8 +108,8 @@ </para> </sect2> <sect2 xml:id="mirror-services"> - <title>Services to offer</title> - <para> + <title xml:lang="en">Services to offer</title> + <para xml:lang="en"> Every mirror site is required to have a set of core services available. In addition to these required services, there are a number of optional services that @@ -139,8 +117,8 @@ which services you can provide and how to go about implementing them. </para> <sect3 xml:id="mirror-serv-ftp"> - <title>FTP (required for FTP fileset)</title> - <para> + <title xml:lang="en">FTP (required for FTP fileset)</title> + <para xml:lang="en"> This is one of the most basic services, and it is required for each mirror offering public FTP distributions. FTP access must be @@ -151,42 +129,34 @@ Also the FreeBSD archive should be available under the path <filename>/pub/FreeBSD</filename>. </para> - <para> + <para xml:lang="en"> There is a lot of software available which can be set up to allow anonymous FTP - (in alphabetical order). + (in alphabetical order).</para> <itemizedlist> - <listitem><para><command>/usr/libexec/ftpd</command>: FreeBSD's own ftpd - can be used. Be sure to read &man.ftpd.8;.</para> + <listitem><para xml:lang="en"><command>/usr/libexec/ftpd</command>: FreeBSD's own ftpd + can be used. Be sure to read <citerefentry><refentrytitle>ftpd</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para> </listitem> <listitem> - <para><package>ftp/ncftpd</package>: A commercial package, + <para xml:lang="en"><package>ftp/ncftpd</package>: A commercial package, free for educational use.</para> </listitem> <listitem> - <para><package>ftp/oftpd</package>: An ftpd designed with + <para xml:lang="en"><package>ftp/oftpd</package>: An ftpd designed with security as a main focus.</para> </listitem> <listitem> - <para><package>ftp/proftpd</package>: A modular and very flexible ftpd.</para> + <para xml:lang="en"><package>ftp/proftpd</package>: A modular and very flexible ftpd.</para> </listitem> <listitem> - <para><package>ftp/pure-ftpd</package>: Another ftpd developed with + <para xml:lang="en"><package>ftp/pure-ftpd</package>: Another ftpd developed with security in mind.</para> </listitem> - <listitem><para><package>ftp/twoftpd</package>: As above.</para></listitem> - <listitem><para><package>ftp/vsftpd</package>: The <quote>very secure</quote> ftpd.</para></listitem> - <listitem> - <para><package>ftp/wu-ftpd</package>: The ftpd from Washington - University. It has become infamous, because of the huge - amount of security issues that have been found in it. - If you do choose to use this software be sure to - keep it up to date. - </para> - </listitem> + <listitem><para xml:lang="en"><package>ftp/twoftpd</package>: As above.</para></listitem> + <listitem><para xml:lang="en"><package>ftp/vsftpd</package>: The <quote>very secure</quote> ftpd.</para></listitem> </itemizedlist> - FreeBSD's <application>ftpd</application>, <application>proftpd</application>, - <application>wu-ftpd</application> and maybe <application>ncftpd</application> + <para xml:lang="en">FreeBSD's <application>ftpd</application>, <application>proftpd</application> + and maybe <application>ncftpd</application> are among the most commonly used FTPds. The others do not have a large userbase among mirror sites. One thing to consider is that you may need flexibility in limiting @@ -195,8 +165,8 @@ </para> </sect3> <sect3 xml:id="mirror-serv-rsync"> - <title>Rsync (optional for FTP fileset)</title> - <para> + <title xml:lang="en">Rsync (optional for FTP fileset)</title> + <para xml:lang="en"> <application>Rsync</application> is often offered for access to the contents of the FTP area of FreeBSD, so other mirror sites can use your system as their source. The protocol is different from FTP in many ways. @@ -212,34 +182,30 @@ (this is the preferred method for public rsync servers). Authentication, connection limits, and other restrictions may be applied. There is just one software package - available: + available:</para> <itemizedlist> - <listitem><para><package>net/rsync</package></para></listitem> + <listitem><para xml:lang="en"><package>net/rsync</package></para></listitem> </itemizedlist> - </para> </sect3> <sect3 xml:id="mirror-serv-http"> - <title>HTTP (required for web pages, optional for FTP fileset)</title> - <para> + <title xml:lang="en">HTTP (required for web pages, optional for FTP fileset)</title> + <para xml:lang="en"> If you want to offer the FreeBSD web pages, you will need to install a web server. You may optionally offer the FTP fileset via HTTP. The choice of web server software is left up to the mirror administrator. - Some of the most popular choices are: + Some of the most popular choices are:</para> <itemizedlist> <listitem> - <para><package>www/apache13</package>: + <para xml:lang="en"><package>www/apache22</package>: <application>Apache</application> is the most widely deployed web server on the Internet. It is used - extensively by the FreeBSD Project. You may also wish to - use the next generation of the - <application>Apache</application> web server, available - in the ports collection as <package>www/apache22</package>.</para> + extensively by the FreeBSD Project.</para> </listitem> <listitem> - <para><package>www/thttpd</package>: + <para xml:lang="en"><package>www/thttpd</package>: If you are going to be serving a large amount of static content you may find that using an application such as thttpd is more efficient than <application>Apache</application>. It is @@ -247,7 +213,7 @@ </listitem> <listitem> - <para><package>www/boa</package>: + <para xml:lang="en"><package>www/boa</package>: <application>Boa</application> is another alternative to <application>thttpd</application> and <application>Apache</application>. It should provide @@ -257,170 +223,44 @@ contain the same set of optimizations for FreeBSD that are found in <application>thttpd</application>.</para> </listitem> - </itemizedlist> - </para> - </sect3> - <sect3 xml:id="mirror-serv-cvsup"> - <title>CVSup (desired for CVS repository)</title> - <para> - <application>CVSup</application> is a very efficient way of distributing files. - It works similar to <application>rsync</application>, but was specially designed for - use with CVS repositories. If you want to offer the - FreeBSD CVS repository, you really want to consider - offering it via <application>CVSup</application>. It is possible to offer - the CVS repository via <application>AnonCVS</application>, FTP, - <application>rsync</application> or HTTP, but - people would benefit much more from <application>CVSup</application> access. - <application>CVSup</application> was developed by &a.jdp;. - It is a bit tricky to install on non-FreeBSD platforms, - since it is written in Modula-3 and therefore requires - a Modula-3 environment. John Polstra has built a - stripped down version of M3 that is sufficient to - run <application>CVSup</application>, and can be installed much easier. - See <link xlink:href="http://www.polstra.com/projects/freeware/ezm3/">Ezm3</link>; - for details. Related ports are: - <itemizedlist> <listitem> - <para><package>net/cvsup</package>: The native CVSup port (client and server) - which requires <package>lang/ezm3</package> now.</para> + <para xml:lang="en"><package>www/nginx</package>: + <application>Nginx</application> is a high performance edge web + server with a low memory footprint and key features to build + a modern and efficient web infrastructure. Features include + a HTTP server, HTTP and mail reverse proxy, caching, load + balancing, compression, request throttling, connection + multiplexing and reuse, SSL offload and HTTP media + streaming.</para> </listitem> - <listitem> - <para><package>net/cvsup-mirror</package>: The CVSup mirror kit, which requires - <package>net/cvsup-without-gui</package>, and configures it mirror-ready. Some - site administrators may want a different setup though. - </para> - </listitem> </itemizedlist> - - There are a few more like - <package>net/cvsup-without-gui</package> you might want to have - a look at. If you prefer a static binary package, take a look - <link xlink:href="http://people.FreeBSD.org/~jdp/s1g/">here</link>. - This page still refers to the S1G bug that was present - in <application>CVSup</application>. Maybe - John will set up a generic download-site to get - static binaries for various platforms. - </para> - <para> - It is possible to use <application>CVSup</application> to offer - any kind of fileset, not just CVS repositories, - but configuration can be complex. - <application>CVSup</application> is known to eat some CPU on both the server and the - client, since it needs to compare lots of files. - </para> </sect3> - <sect3 xml:id="mirror-anoncvs"> - <title>AnonCVS (optional for CVS repository)</title> - <para> - If you have the CVS repository, you may want to offer - anonymous CVS access. A short warning first: - There is not much demand for it, - it requires some experience, and you need to know - what you are doing. - </para> - <para> - Generally there are two ways - to access a CVS repository remotely: via - <emphasis>pserver</emphasis> or via <command>ssh</command> - (we do not consider <command>rsh</command>). - For anonymous access, <emphasis>pserver</emphasis> is - very well suited, but some still offer <command>ssh</command> - access as well. There is a custom crafted - <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/FreeBSD-CVS/anoncvs.shar">wrapper</link>; - in the CVS repository, to be used as a login-shell for the - anonymous ssh account. It does a chroot, and therefore - requires the CVS repository to be available under the - anonymous user's home-directory. This may not be possible - for all sites. If you just offer <emphasis>pserver</emphasis> - this restriction does not apply, but you may run with - more security risks. You do not need to install any special - software, since &man.cvs.1; comes with - FreeBSD. You need to enable access via <command>inetd</command>, - so add an entry into your <filename>/etc/inetd.conf</filename> - like this: - <programlisting> -cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --allow-root=/home/ncvs pserver - </programlisting> - See the manpage for details of the options. Also see the CVS <emphasis>info</emphasis> - page about additional ways to make sure access is read-only. - It is advised that you create an unprivileged account, - preferably called <systemitem class="username">anoncvs</systemitem>. - Also you need to create a file <filename>passwd</filename> - in your <filename>/home/ncvs/CVSROOT</filename> and assign a - CVS password (empty or <literal>anoncvs</literal>) to that user. - The directory <filename>/anoncvstmp</filename> is a special - purpose memory based file system. It is not required but - advised since &man.cvs.1; creates a shadow directory - structure in your <filename>/tmp</filename> which is - not used after the operation but slows things - dramatically if real disk operations are required. - Here is an excerpt from <filename>/etc/fstab</filename>, - how to set up such a MFS: - <programlisting> -/dev/da0s1b /anoncvstmp mfs rw,-s=786432,-b=4096,-f=512,-i=560,-c=3,-m=0,nosuid,nodev 0 0 - </programlisting> - This is (of course) tuned a lot, and was suggested by &a.jdp;. - </para> - </sect3> </sect2> </sect1> <sect1 xml:id="mirror-howto"> - <title>How to Mirror FreeBSD</title> - <para> + <title xml:lang="en">How to Mirror FreeBSD</title> + <para xml:lang="en"> Ok, now you know the requirements and how to offer the services, but not how to get it. :-) This section explains how to actually mirror the various parts of FreeBSD, what tools to use, and where to mirror from. </para> - <sect2 xml:id="mirror-ftp"> - <title>FTP</title> - <para> + <sect2 xml:id="mirror-ftp-rsync"> + <title xml:lang="en">Mirroring the FTP site</title> + <para xml:lang="en"> The FTP area is the largest amount of data that needs to be mirrored. It includes the <emphasis>distribution sets</emphasis> required for network installation, the <emphasis>branches</emphasis> which are actually snapshots of checked-out source trees, the <emphasis>ISO Images</emphasis> to write CD-ROMs with the installation distribution, - a live file system, lots of packages, the ports tree, - distfiles, and a huge amount of packages. All of course - for various FreeBSD versions, - and various architectures. + a live file system, and a snapshot of the ports tree. All of + course for various FreeBSD versions, and various architectures. </para> - <sect3 xml:id="mirror-ftp-ftp"> - <title>With FTP mirror</title> - <para> - You can use a <application>FTP mirror</application> - program to get the files. Some of the most commonly used are: - <itemizedlist> - <listitem><para><package>ftp/mirror</package></para></listitem> - <listitem><para><package>ftp/ftpmirror</package></para></listitem> - <listitem><para><package>ftp/emirror</package></para></listitem> - <listitem><para><package>ftp/spegla</package></para></listitem> - <listitem><para><package>ftp/omi</package></para></listitem> - <listitem><para><package>ftp/wget</package></para></listitem> - </itemizedlist> - - <package>ftp/mirror</package> was very popular, but seemed - to have some drawbacks, as it is written in &man.perl.1;, - and had real problems with mirroring large - directories like a FreeBSD site. There are rumors that - the current version has fixed this by allowing - a different algorithm for comparing - the directory structure to be specified. - </para> - <para> - In general FTP is not really good for mirroring. It transfers - the whole file if it has changed, and does - not create a single data stream which would benefit from - a large TCP congestion window. - </para> - </sect3> - <sect3 xml:id="mirror-ftp-rsync"> - <title>With rsync</title> - <para> - A better way to mirror the FTP area is <application>rsync</application>. + <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 @@ -428,9 +268,9 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f 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. + that allows <application>rsync</application> access.</para> <note> - <para> + <para xml:lang="en"> Since the number of <application>rsync</application> clients will have a significant impact on the server machine, most admins impose limitations on their @@ -439,10 +279,9 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f an exception for your host (since you are a mirror). </para> </note> - A command line to mirror FreeBSD might look like: - <screen>&prompt.user; <userinput>rsync -vaz --delete ftp4.de.FreeBSD.org::FreeBSD/ /pub/FreeBSD/</userinput> - </screen> - Consult the documentation for <application>rsync</application>, + <para xml:lang="en">A command line to mirror FreeBSD might look like:</para> + <screen xml:lang="en"><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. @@ -451,260 +290,99 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f 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 &man.cron.8;. + via <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry>. </para> - </sect3> - <sect3 xml:id="mirror-ftp-cvsup"> - <title>With CVSup</title> - <para> - A few sites, including the one-and-only <systemitem class="fqdomainname">ftp-master.FreeBSD.org</systemitem> - even offer <application>CVSup</application> to mirror the contents of - the FTP space. You need to install a <application>CVSup</application> - client, preferably from the port <package>net/cvsup</package>. - (Also reread <xref linkend="mirror-serv-cvsup"/>.) - A sample <filename>supfile</filename> suitable for <systemitem class="fqdomainname">ftp-master.FreeBSD.org</systemitem> - looks like this: - <programlisting> - # - # FreeBSD archive supfile from master server - # - *default host=ftp-master.FreeBSD.org - *default base=/usr - *default prefix=/pub - #*default release=all - *default delete use-rel-suffix - *default umask=002 - - # If your network link is a T1 or faster, comment out the following line. - #*default compress - - FreeBSD-archive release=all preserve - </programlisting> - - It seems <application>CVSup</application> would be the best - way to mirror the archive in terms of efficiency, but - it is only available from few sites. - <note xml:id="mirror-cvsup-s-option"> - <para> - Please have look at the <application>CVSup</application> documentation - like &man.cvsup.1; and consider using the <option>-s</option> - option. This reduces I/O operations by assuming the - recorded information about each file is correct.</para> - </note> - </para> - </sect3> </sect2> - <sect2 xml:id="mirror-cvs"> - <title>Mirroring the CVS repository</title> - <para>There are various ways to mirror the CVS repository. - <application>CVSup</application> is the most common method.</para> - - <sect3 xml:id="mirror-cvs-cvsup"> - <title>Using CVSup</title> - <para> - <application>CVSup</application> is described in some - detail in <xref linkend="mirror-serv-cvsup"/> and <xref linkend="mirror-ftp-cvsup"/>. - </para> - <para>It is very easy to setup a - <application>CVSup</application> mirror. Installing - <package>net/cvsup-mirror</package> will - make sure all of the needed programs are installed and then - gather all the needed information to configure the mirror.</para> - <note> - <para> - Please do not forget to consider the hint - mentioned in <link linkend="mirror-cvsup-s-option">this note</link> - above. - </para> - </note> - </sect3> - <sect3 xml:id="mirror-cvs-other"> - <title>Using other methods</title> - <para> - Using other methods than <application>CVSup</application> is - generally not recommended. We describe them in short here - anyway. Since most sites offer the CVS repository as - part of the FTP fileset under the path - <filename>/pub/FreeBSD/development/FreeBSD-CVS</filename>, - the following methods could be used. - <itemizedlist> - <listitem><para><application>FTP</application></para></listitem> - <listitem><para><application>Rsync</application></para></listitem> - <listitem><para><application>HTTP</application></para></listitem> - </itemizedlist> - - <important> - <para>AnonCVS cannot be used to mirror the CVS repository - since CVS does not allow you to access the repository - itself, only checked out versions of the modules.</para> - </important> - </para> - </sect3> - </sect2> <sect2 xml:id="mirror-www"> - <title>Mirroring the WWW pages</title> - <para> - The best way is to check out the <emphasis>www</emphasis> - distribution from CVS. If you have a local mirror of the - CVS repository, it is as easy as: - <screen>&prompt.user; <userinput>cvs -d /home/ncvs co www</userinput></screen> - and a <emphasis>cronjob</emphasis>, that calls <command>cvs up -d -P</command> - on a regular basis, maybe just after your repository was updated. - Of course, the files need to remain in a directory available - for public WWW access. The installation and configuration of a - web server is not discussed here. - </para> + <title xml:lang="en">Mirroring the WWW pages</title> + <para xml:lang="en"> + The FreeBSD website should only be mirrored via + <application>rsync</application>.</para> + <para xml:lang="en">A command line to mirror the FreeBSD web site might look like:</para> + <screen xml:lang="en"><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 xml:lang="en">Mirroring Packages</title> + <para xml:lang="en">Due to very high requirements of bandwidth, storage and + adminstration the FreeBSD Project has decided not to allow public + mirrors of packages. For sites with lots of machines, it might + be advantagous to run a caching HTTP proxy for the <citerefentry><refentrytitle>pkg</refentrytitle><manvolnum>8</manvolnum></citerefentry> + process. Alternatively specific packages and their dependencies + can be fetched by running something like the following:</para> - <para> - If you do not have a local repository, you can use - <application>CVSup</application> to maintain an <quote>up to date copy</quote> - of the www pages. A sample supfile can be found in - <filename>/usr/share/examples/cvsup/www-supfile</filename> and - could look like this: - <programlisting> - # - # WWW module supfile for FreeBSD - # - *default host=cvsup3.de.FreeBSD.org - *default base=/usr - *default prefix=/usr/local - *default release=cvs tag=. - *default delete use-rel-suffix + <screen xml:lang="en"><prompt>%</prompt> <userinput>pkg fetch -d -o <replaceable>/usr/local/mirror</replaceable> <replaceable>vim</replaceable></userinput></screen> - # If your network link is a T1 or faster, comment out the following line. - *default compress + <para xml:lang="en">Once those packages have been fetched, the repository metadata must be generated by running:</para> - # This collection retrieves the www/ tree of the FreeBSD repository - www - </programlisting> - </para> - <para> - Using <package>ftp/wget</package> or other web-mirror tools is - not recommended. - </para> - <sect3 xml:id="mirror-www-doc"> - <title>Mirroring the FreeBSD documentation</title> - <para> - Since the documentation is referenced a lot from the - web pages, it is recommended that you mirror the - FreeBSD documentation as well. However, this is not - as trivial as the www-pages alone. - </para> - <para> - First of all, you should get the doc sources, - again preferably via <application>CVSup</application>. - Here is a corresponding sample supfile: - <programlisting> - # - # FreeBSD documentation supfile - # - *default host=cvsup3.de.FreeBSD.org - *default base=/usr - *default prefix=/usr/share - *default release=cvs tag=. - *default delete use-rel-suffix + <screen xml:lang="en"><prompt>%</prompt> <userinput>pkg repo <replaceable>/usr/local/mirror</replaceable></userinput></screen> - # If your network link is a T1 or faster, comment out the following line. - #*default compress - - # This will retrieve the entire doc branch of the FreeBSD repository. - # This includes the handbook, FAQ, and translations thereof. - doc-all - </programlisting> - </para> - <para> - Then you need to install a couple of ports. - You are lucky, there is a meta-port: - <package>textproc/docproj</package> to do the work - for you. You need to set up some - environment variables, like - <literal>SGML_CATALOG_FILES</literal>. - Also have a look at your <filename>/etc/make.conf</filename> - (copy <filename>/usr/share/examples/etc/make.conf</filename> if - you do not have one), and look at the - <literal>DOC_LANG</literal> variable. - Now you are probably ready to run <command>make</command> - in your doc directory (<filename>/usr/share/doc</filename> - by default) and build the documentation. - Again you need to make it accessible for your web server - and make sure the links point to the right location. - <important> - <para> - The building of the documentation, as well as lots - of side issues, is documented itself in the - <link xlink:href="&url.books.fdp-primer;">&os; Documentation - Project Primer</link>. - Please read this piece of documentation, especially if you - have problems building the documentation. - </para> - </important> - </para> - </sect3> + <para xml:lang="en">Once the packages have been fetched and the metadata for the + repository has been generated, serve the packages up to the + client machines via HTTP. For additional information see the + man pages for <citerefentry><refentrytitle>pkg</refentrytitle><manvolnum>8</manvolnum></citerefentry>, specifically the <citerefentry><refentrytitle>pkg-repo</refentrytitle><manvolnum>8</manvolnum></citerefentry> page. + </para> </sect2> <sect2 xml:id="mirror-how-often"> - <title>How often should I mirror?</title> - <para> - Every mirror should be updated on a regular - basis. You will certainly need some script - framework for it that will be called by - &man.cron.8;. Since nearly every admin - does this his own way, we cannot give - specific instructions. It could work - like this: + <title xml:lang="en">How often should I 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> + <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> + <para xml:lang="en"> Add some output redirections so diagnostic messages are logged to a file. </para> </step> <step> - <para> + <para xml:lang="en"> Test if your script works. Check the logs. </para> </step> <step> - <para> - Use &man.crontab.1; to add the script to the - appropriate user's &man.crontab.5;. This should be a + <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 — + 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> - Here are some recommended schedules: + <para xml:lang="en"> + Here are some recommended schedules:</para> <itemizedlist> - <listitem><para>FTP fileset: daily</para></listitem> - <listitem><para>CVS repository: hourly</para></listitem> - <listitem><para>WWW pages: daily</para></listitem> + <listitem><para xml:lang="en">FTP fileset: daily</para></listitem> + <listitem><para xml:lang="en">WWW pages: daily</para></listitem> </itemizedlist> - </para> </sect2> </sect1> <sect1 xml:id="mirror-where"> - <title>Where to mirror from</title> - <para> + <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>A few words about the organization</title> - <para> + <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>. @@ -714,7 +392,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f <emphasis>N</emphasis> is a number, telling that the host would be the <emphasis>Nth</emphasis> mirror in that country. - (Same applies to <systemitem>cvsupN.CC.FreeBSD.org</systemitem>, + (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 @@ -727,7 +405,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f <systemitem class="fqdomainname">ftp.FreeBSD.org</systemitem> so automated mirroring systems should find a different machine to mirror from. </para> - <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 @@ -748,54 +426,46 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f </para> </sect2> <sect2 xml:id="mirror-where-where"> - <title>Ok, but where should I get the stuff now?</title> - <para> + <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>I just want to mirror from somewhere!</title> - <para> + <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> - Look at available mirrors in your country. - The <link xlink:href="http://mirrorlist.FreeBSD.org/">FreeBSD - Mirror Database</link> can help you with this. - </para> - </step> - <step> - <para> + <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> - or <application>CVSup</application>). + use (like <application>rsync</application>). </para> </step> <step> - <para> + <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> + <para xml:lang="en"> Set up your mirror as described above. </para> </step> </procedure> </sect3> <sect3 xml:id="mirror-where-official"> - <title>I am an official mirror, what is the right site for me?</title> - <para> + <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 @@ -805,8 +475,8 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f </para> </sect3> <sect3 xml:id="mirror-where-master"> - <title>I want to access the master sites!</title> - <para> + <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 @@ -814,9 +484,9 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f 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 &a.hubs; first.</para> + 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> + <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 @@ -824,123 +494,72 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f <email>mirror-admin@FreeBSD.org</email> to request help with that. </para> - <para> - There are three master sites for the FTP fileset and - one for the CVS repository (the web pages and docs are - obtained from CVS, so there is no need for master). + <para xml:lang="en"> + There is one master site for the FTP fileset. </para> <sect4 xml:id="mirror-where-master-ftp"> - <title>ftp-master.FreeBSD.org</title> - <para> + <title xml:lang="en">ftp-master.FreeBSD.org</title> + <para xml:lang="en"> This is the master site for the FTP fileset. </para> - <para> + <para xml:lang="en"> <systemitem>ftp-master.FreeBSD.org</systemitem> provides - <application>rsync</application> and <application>CVSup</application> + <application>rsync</application> access, in addition to FTP. - Refer to <xref linkend="mirror-ftp-rsync"/> and - <xref linkend="mirror-ftp-cvsup"/> how to access - via these protocols. + Refer to <xref linkend="mirror-ftp-rsync"/>. </para> - <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> - <sect4 xml:id="mirror-where-master-cvsup"> - <title>cvsup-master.FreeBSD.org</title> - <para> - This is the master site for the CVS repository. - </para> - <para> - <systemitem>cvsup-master.FreeBSD.org</systemitem> provides - <application>CVSup</application> access only. - See <xref linkend="mirror-cvs-cvsup"/> for details. - </para> - <?ignore - <para> - To get access, you need to contact the &a.cvsup-master;. - Make sure you read the - <link xlink:href="http://people.FreeBSD.org/~jdp/cvsup-access/">FreeBSD CVSup Access Policy</link> - first! - </para> - ?> - <para> - Set up the required authentication by following - <link xlink:href="http://people.FreeBSD.org/~jdp/cvpasswd/">these - instructions</link>. Make sure you specify the server as - <systemitem>freefall.FreeBSD.org</systemitem> on the <command>cvpasswd</command> - command line, as described in this document, - even when you are contacting - <systemitem>cvsup-master.FreeBSD.org</systemitem> - </para> *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201712141203.vBEC3M7M048728>