$FreeBSD: doc/en_US.ISO8859-1/articles/hubs/article.sgml,v 1.55 2006/02/07 21:32:42 joel Exp $
FreeBSD is a registered trademark of the FreeBSD Foundation.
FreeBSD 是 FreeBSD基金会的注册商标。
CVSup is a registered trademark of John D. Polstra.
CVSup 是 John D. Polstra 的注册商标。
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the '™' or the '®' symbol.
An in-progress article on how to mirror FreeBSD, aimed at hub administrators.
文章还是草稿告诉管理员介绍如何镜象freebsd，目标是中心管理员。
[ Split HTML / Single HTML ]
[ 章节模式 / 完整模式 ]
Table of Contents
目录
1 Contact Information
1联系信息
2 Requirements for FreeBSD mirrors
2 镜象freebsd的需求
3 How to Mirror FreeBSD
3 如何作freebsd镜象
4 Where to mirror from
4 从什么地方镜象
5 Official Mirrors
5 官方镜象
6 Some statistics from mirror sites
6 镜象站点大约统计
1 Contact Information
1 联系信息
The Mirror System Coordinators can be reached through email at <[email]mirror-admin@FreeBSD.org[/email]>. There is also a FreeBSD mirror sites mailing lists.
Disk space is one of the most important requirements. 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 5.4-RELEASE/6.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:
Of course, you need to be connected to the Internet. The required bandwidth depends on your intended use of the mirror. If you just want to mirror some parts of FreeBSD for local use at your site/intranet, the demand may be much smaller than if you want to make the files publicly available. If you intend to become an official mirror, the bandwidth required will be even higher. We can only give rough estimates here:
Local site, no public access: basically no minimum, but < 2 Mbps could make syncing too slow.
本地站点非公共访问：基本上没有最低，但小于2 Mbps同步太慢。
Unofficial public site: 34 Mbps is probably a good start.
非官方的公共站点: 34 Mbps或许是个好的开始。
Official site: > 100 Mbps is recommended, and your host should be connected as close as possible to your border router.
官方站点:推荐100 Mbps以上，你主机的联接应当尽可能靠近你的边际路由。
2.3 System Requirements, CPU, RAM
2.3 系统需求，处理器、内存
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 are just examples to give you a very rough hint.
For a moderately visited site that offers 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 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 large number of small modifications to the disk.
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 server administrators may choose to offer. This section explains which services you can provide and how to go about implementing them.
This is one of the most basic services, and it is required for each mirror offering public FTP distributions. FTP access must be anonymous, and no upload/download ratios are allowed (a ridiculous thing anyway). Upload capability is not required (and must never be allowed for the FreeBSD file space). 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).
有许多软件可以设置允许匿名的FTP(字母序排列)
/usr/libexec/ftpd: FreeBSD's own ftpd can be used. Be sure to read ftpd(8).
/usr/libexec/ftpd: 使用freebsd自带的ftpd，一定要读ftpd(8)。
ftp/ncftpd: A commercial package, free for educational use.
ftp/ncftpd: 商业软件包，免费为教育使用。
ftp/oftpd: An ftpd designed with security as a main focus.
ftp/oftpd: 以安全为设计重点
ftp/proftpd: A modular and very flexible ftpd.
ftp/proftpd: 非常灵活、模块化ftpd。
ftp/pure-ftpd: Another ftpd developed with security in mind.
另一个ftpd开发侧重安全
ftp/twoftpd: As above.
ftp/twoftpd: 同上。
ftp/vsftpd: The “very secure”ftpd.
ftp/vsftpd: “非常安全”的 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.