From owner-svn-doc-all@freebsd.org Thu Dec 14 12:03:23 2017 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EEA4EA1F23; Thu, 14 Dec 2017 12:03:23 +0000 (UTC) (envelope-from rcyu@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EEAC612B8; Thu, 14 Dec 2017 12:03:22 +0000 (UTC) (envelope-from rcyu@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id vBEC3MZ9048730; Thu, 14 Dec 2017 12:03:22 GMT (envelope-from rcyu@FreeBSD.org) Received: (from rcyu@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id vBEC3M7M048728; Thu, 14 Dec 2017 12:03:22 GMT (envelope-from rcyu@FreeBSD.org) Message-Id: <201712141203.vBEC3M7M048728@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: rcyu set sender to rcyu@FreeBSD.org using -f From: Ruey-Cherng Yu Date: Thu, 14 Dec 2017 12:03:22 +0000 (UTC) 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 X-SVN-Group: doc-head X-SVN-Commit-Author: rcyu X-SVN-Commit-Paths: head/zh_TW.UTF-8/articles/hubs X-SVN-Commit-Revision: 51308 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 12:03:23 -0000 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 @@ - - - - - - -
- Mirroring FreeBSD + +
+ Mirroring FreeBSD - JunKuriyama -
kuriyama@FreeBSD.org
+ JunKuriyama +
kuriyama@FreeBSD.org
 - ValentinoVaschetto -
logo@FreeBSD.org
+ ValentinoVaschetto +
logo@FreeBSD.org
 - DanielLang -
dl@leo.org
+ DanielLang +
dl@leo.org
 - KenSmith -
kensmith@FreeBSD.org
+ KenSmith +
kensmith@FreeBSD.org
 - &tm-attrib.freebsd; - &tm-attrib.cvsup; - &tm-attrib.general; + FreeBSD 是 FreeBSD基金會的註冊商標 + 許多製造商和經銷商使用一些稱為商標的圖案或文字設計來彰顯自己的產品。 本文中出現的眾多商標，以及 FreeBSD Project 本身廣所人知的商標，後面將以 ™ 或 ® 符號來標註。 $FreeBSD$ @@ -39,90 +32,75 @@ + + We are not accepting new mirrors at this time. + + 聯繫方式 - 若要找整個 Mirror 機制的協調者，可以 email 到 mirror-admin@FreeBSD.org。此外，這裡也有份 - &a.hubs;。 + The Mirror System Coordinators can be reached through email + at mirror-admin@FreeBSD.org. There is also + a FreeBSD mirror sites mailing lists. 成為 FreeBSD mirrors 的必備條件 硬碟空間 - - 硬碟空間是最重要的必備條件之一。 - 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 official 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: - + 硬碟空間是最重要的必備條件之一。 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 official 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: - 完整 FTP Distribution: 126 GB - CVS repository: 2.7 GB - CTM deltas: 1.8 GB - Web pages: 300 MB + Full FTP Distribution: 1.4 TB + CTM deltas: 10 GB + Web pages: 1GB + + The current disk usage of FTP Distribution can be found at + ftp://ftp.FreeBSD.org/pub/FreeBSD/dir.sizes. + 網路頻寬 - - 當然，你一定要能連上 Internet。 - 頻寬需求多少，這要看你所想要的 mirror 程度而定。 - 若只想要 mirror 一部份的 FreeBSD 檔案以作為網站或 intranet 的局部用途， - 那麼頻寬需求會明顯比成為公共服務用途的小一些。 - 若想成為 official mirror 之一的話，那麼頻寬就勢必得增加才夠用。以下，我們僅列出一些估計值以做為參考： - + 當然，你一定要能連上 Internet。 頻寬需求多少，這要看你所想要的 mirror 程度而定。 若只想要 mirror 一部份的 FreeBSD 檔案以作為網站或 intranet 的局部用途， 那麼頻寬需求會明顯比成為公共服務用途的小一些。 若想成為 official mirror 之一的話，那麼頻寬就勢必得增加才夠用。以下，我們僅列出一些估計值以做為參考： - Local site, no public access: basically no minimum, + Local site, no public access: basically no minimum, but < 2 Mbps could make syncing too slow. - Unofficial public site: 34 Mbps is probably a good start. - Official site: > 100 Mbps is recommended, and your host + Unofficial public site: 34 Mbps is probably a good start. + Official site: > 100 Mbps is recommended, and your host should be connected as close as possible to your border router. 系統需求、CPU、RAM - + 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. - + For a moderately visited site that offers - Rsync, you might + rsync, 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 official site. - + 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. - + 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 @@ - Services to offer - + Services to offer + 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. - FTP (required for FTP fileset) - + FTP (required for FTP fileset) + 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 /pub/FreeBSD. - + There is a lot of software available which can be set up to allow anonymous FTP - (in alphabetical order). + (in alphabetical order). - /usr/libexec/ftpd: FreeBSD's own ftpd - can be used. Be sure to read &man.ftpd.8;. + /usr/libexec/ftpd: FreeBSD's own ftpd + can be used. Be sure to read ftpd8. - ftp/ncftpd: A commercial package, + ftp/ncftpd: A commercial package, free for educational use. - ftp/oftpd: An ftpd designed with + ftp/oftpd: An ftpd designed with security as a main focus. - ftp/proftpd: A modular and very flexible ftpd. + ftp/proftpd: A modular and very flexible ftpd. - ftp/pure-ftpd: Another ftpd developed with + ftp/pure-ftpd: Another ftpd developed with security in mind. - ftp/twoftpd: As above. - ftp/vsftpd: The very secure ftpd. - - ftp/wu-ftpd: 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. - - + ftp/twoftpd: As above. + ftp/vsftpd: The very secure ftpd. - FreeBSD's ftpd, proftpd, - wu-ftpd and maybe ncftpd + FreeBSD's ftpd, proftpd + and maybe ncftpd 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 @@ - Rsync (optional for FTP fileset) - + Rsync (optional for FTP fileset) + Rsync 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: - net/rsync + net/rsync - - HTTP (required for web pages, optional for FTP fileset) - + HTTP (required for web pages, optional for FTP fileset) + 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: - www/apache13: + www/apache22: Apache 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 - Apache web server, available - in the ports collection as www/apache22. + extensively by the FreeBSD Project. - www/thttpd: + www/thttpd: 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 Apache. It is @@ -247,7 +213,7 @@ - www/boa: + www/boa: Boa is another alternative to thttpd and Apache. It should provide @@ -257,170 +223,44 @@ contain the same set of optimizations for FreeBSD that are found in thttpd. - - - - - CVSup (desired for CVS repository) - - CVSup is a very efficient way of distributing files. - It works similar to rsync, 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 CVSup. It is possible to offer - the CVS repository via AnonCVS, FTP, - rsync or HTTP, but - people would benefit much more from CVSup access. - CVSup 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 CVSup, and can be installed much easier. - See Ezm3 - for details. Related ports are: - - net/cvsup: The native CVSup port (client and server) - which requires lang/ezm3 now. + www/nginx: + Nginx 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. - - net/cvsup-mirror: The CVSup mirror kit, which requires - net/cvsup-without-gui, and configures it mirror-ready. Some - site administrators may want a different setup though. - - - - There are a few more like - net/cvsup-without-gui you might want to have - a look at. If you prefer a static binary package, take a look - here. - This page still refers to the S1G bug that was present - in CVSup. Maybe - John will set up a generic download-site to get - static binaries for various platforms. - - - It is possible to use CVSup to offer - any kind of fileset, not just CVS repositories, - but configuration can be complex. - CVSup is known to eat some CPU on both the server and the - client, since it needs to compare lots of files. - - - AnonCVS (optional for CVS repository) - - 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. - - - Generally there are two ways - to access a CVS repository remotely: via - pserver or via ssh - (we do not consider rsh). - For anonymous access, pserver is - very well suited, but some still offer ssh - access as well. There is a custom crafted - wrapper - 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 pserver - 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 inetd, - so add an entry into your /etc/inetd.conf - like this: - -cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --allow-root=/home/ncvs pserver - - See the manpage for details of the options. Also see the CVS info - page about additional ways to make sure access is read-only. - It is advised that you create an unprivileged account, - preferably called anoncvs. - Also you need to create a file passwd - in your /home/ncvs/CVSROOT and assign a - CVS password (empty or anoncvs) to that user. - The directory /anoncvstmp 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 /tmp which is - not used after the operation but slows things - dramatically if real disk operations are required. - Here is an excerpt from /etc/fstab, - how to set up such a MFS: - -/dev/da0s1b /anoncvstmp mfs rw,-s=786432,-b=4096,-f=512,-i=560,-c=3,-m=0,nosuid,nodev 0 0 - - This is (of course) tuned a lot, and was suggested by &a.jdp;. - - - How to Mirror FreeBSD - + How to Mirror FreeBSD + 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. - - FTP - + + Mirroring the FTP site + The FTP area is the largest amount of data that needs to be mirrored. It includes the distribution sets required for network installation, the branches which are actually snapshots of checked-out source trees, the ISO Images 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. - - With FTP mirror - - You can use a FTP mirror - program to get the files. Some of the most commonly used are: - - ftp/mirror - ftp/ftpmirror - ftp/emirror - ftp/spegla - ftp/omi - ftp/wget - - - ftp/mirror 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. - - - 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. - - - - With rsync - - A better way to mirror the FTP area is rsync. + + The best way to mirror the FTP area is rsync. You can install the port net/rsync and then use rsync to sync with your upstream host. rsync is already mentioned @@ -428,9 +268,9 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f Since rsync 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 rsync access. + that allows rsync access. - + Since the number of rsync 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). - A command line to mirror FreeBSD might look like: - &prompt.user; rsync -vaz --delete ftp4.de.FreeBSD.org::FreeBSD/ /pub/FreeBSD/ - - Consult the documentation for rsync, + A command line to mirror FreeBSD might look like: + % rsync -vaHz --delete rsync://ftp4.de.FreeBSD.org/FreeBSD/ /pub/FreeBSD/ + Consult the documentation for rsync, which is also available at http://rsync.samba.org/, 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 cron8. - - - With CVSup - - A few sites, including the one-and-only ftp-master.FreeBSD.org - even offer CVSup to mirror the contents of - the FTP space. You need to install a CVSup - client, preferably from the port net/cvsup. - (Also reread .) - A sample supfile suitable for ftp-master.FreeBSD.org - looks like this: - - # - # 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 - - - It seems CVSup would be the best - way to mirror the archive in terms of efficiency, but - it is only available from few sites. - - - Please have look at the CVSup documentation - like &man.cvsup.1; and consider using the - option. This reduces I/O operations by assuming the - recorded information about each file is correct. - - - - - Mirroring the CVS repository - There are various ways to mirror the CVS repository. - CVSup is the most common method. - - - Using CVSup - - CVSup is described in some - detail in and . - - It is very easy to setup a - CVSup mirror. Installing - net/cvsup-mirror will - make sure all of the needed programs are installed and then - gather all the needed information to configure the mirror. - - - Please do not forget to consider the hint - mentioned in this note - above. - - - - - Using other methods - - Using other methods than CVSup 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 - /pub/FreeBSD/development/FreeBSD-CVS, - the following methods could be used. - - FTP - Rsync - HTTP - - - - 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. - - - - - Mirroring the WWW pages - - The best way is to check out the www - distribution from CVS. If you have a local mirror of the - CVS repository, it is as easy as: - &prompt.user; cvs -d /home/ncvs co www - and a cronjob, that calls cvs up -d -P - 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. - + Mirroring the WWW pages + + The FreeBSD website should only be mirrored via + rsync. + A command line to mirror the FreeBSD web site might look like: + % rsync -vaHz --delete rsync://bit0.us-west.freebsd.org/FreeBSD-www-data/ /usr/local/www/ + + + Mirroring Packages + 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 pkg8 + process. Alternatively specific packages and their dependencies + can be fetched by running something like the following: - - If you do not have a local repository, you can use - CVSup to maintain an up to date copy - of the www pages. A sample supfile can be found in - /usr/share/examples/cvsup/www-supfile and - could look like this: - - # - # 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 + % pkg fetch -d -o /usr/local/mirror vim - # If your network link is a T1 or faster, comment out the following line. - *default compress + Once those packages have been fetched, the repository metadata must be generated by running: - # This collection retrieves the www/ tree of the FreeBSD repository - www - - - - Using ftp/wget or other web-mirror tools is - not recommended. - - - Mirroring the FreeBSD documentation - - 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. - - - First of all, you should get the doc sources, - again preferably via CVSup. - Here is a corresponding sample supfile: - - # - # 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 + % pkg repo /usr/local/mirror - # 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 - - - - Then you need to install a couple of ports. - You are lucky, there is a meta-port: - textproc/docproj to do the work - for you. You need to set up some - environment variables, like - SGML_CATALOG_FILES. - Also have a look at your /etc/make.conf - (copy /usr/share/examples/etc/make.conf if - you do not have one), and look at the - DOC_LANG variable. - Now you are probably ready to run make - in your doc directory (/usr/share/doc - 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. - - - The building of the documentation, as well as lots - of side issues, is documented itself in the - &os; Documentation - Project Primer. - Please read this piece of documentation, especially if you - have problems building the documentation. - - - - + 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 pkg8, specifically the pkg-repo8 page. + - How often should I mirror? - - 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: + How often should I mirror? + + 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 + cron8. Since nearly every admin does this in their own + way, specific instructions cannot be provided. It could work + something like this: - + Put the command to run your mirroring application in a script. Use of a plain /bin/sh script is recommended. - + Add some output redirections so diagnostic messages are logged to a file. - + Test if your script works. Check the logs. - - Use &man.crontab.1; to add the script to the - appropriate user's &man.crontab.5;. This should be a + + Use crontab1 to add the script to the + appropriate user's crontab5. 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 stage releases — + FTP. This is used to stage releases — making sure all of the official mirror sites have all of the necessary release files on release day. - - Here are some recommended schedules: + + Here are some recommended schedules: - FTP fileset: daily - CVS repository: hourly - WWW pages: daily + FTP fileset: daily + WWW pages: daily - - Where to mirror from - + Where to mirror from + 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 ftp.FreeBSD.org. - A few words about the organization - + A few words about the organization + Mirrors are organized by country. All official mirrors have a DNS entry of the form ftpN.CC.FreeBSD.org. @@ -714,7 +392,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f N is a number, telling that the host would be the Nth mirror in that country. - (Same applies to cvsupN.CC.FreeBSD.org, + (Same applies to wwwN.CC.FreeBSD.org, etc.) There are mirrors with no CC 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 ftp.FreeBSD.org so automated mirroring systems should find a different machine to mirror from. - + Additionally there exists a hierarchy of mirrors, which is described in terms of tiers. The master sites are not referred to but can be @@ -748,54 +426,46 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f - Ok, but where should I get the stuff now? - + Ok, but where should I get the stuff now? + Under no circumstances should you mirror from ftp.FreeBSD.org. The short answer is: from the site that is closest to you in Internet terms, or gives you the fastest access. - I just want to mirror from somewhere! - + I just want to mirror from somewhere! + If you have no special intentions or requirements, the statement in applies. This means: - - Look at available mirrors in your country. - The FreeBSD - Mirror Database can help you with this. - - - - + Check for those which provide fastest access (number of hops, round-trip-times) and offer the services you intend to - use (like rsync - or CVSup). + use (like rsync). - + Contact the administrators of your chosen site stating your request, and asking about their terms and policies. - + Set up your mirror as described above. - I am an official mirror, what is the right site for me? - + I am an official mirror, what is the right site for me? + In general the description in 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 - I want to access the master sites! - + I want to access the master sites! + 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 official 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 zone administrator (hostmaster@CC.FreeBSD.org) or &a.hubs; first. + If it already has three or more, ask the zone administrator (hostmaster@CC.FreeBSD.org) or FreeBSD mirror sites mailing lists first. - + Whoever helped you become, an official 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 mirror-admin@FreeBSD.org to request help with that. - - 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). + + There is one master site for the FTP fileset. - ftp-master.FreeBSD.org - + ftp-master.FreeBSD.org + This is the master site for the FTP fileset. - + ftp-master.FreeBSD.org provides - rsync and CVSup + rsync access, in addition to FTP. - Refer to and - how to access - via these protocols. + Refer to . - + Mirrors are also encouraged to allow rsync access for the FTP contents, since they are Tier-1-mirrors. - - cvsup-master.FreeBSD.org - - This is the master site for the CVS repository. - - - cvsup-master.FreeBSD.org provides - CVSup access only. - See for details. - - - To get access, you need to contact the &a.cvsup-master;. - Make sure you read the - FreeBSD CVSup Access Policy - first! - - ?> - - Set up the required authentication by following - these - instructions. Make sure you specify the server as - freefall.FreeBSD.org on the cvpasswd - command line, as described in this document, - even when you are contacting - cvsup-master.FreeBSD.org - *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***