From owner-freebsd-doc Sat Apr 13 5:40:54 2002 Delivered-To: freebsd-doc@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 06C9437B416 for ; Sat, 13 Apr 2002 05:40:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g3DCe1S71582; Sat, 13 Apr 2002 05:40:01 -0700 (PDT) (envelope-from gnats) Received: from host213-123-130-182.in-addr.btopenworld.com (host213-123-130-182.in-addr.btopenworld.com [213.123.130.182]) by hub.freebsd.org (Postfix) with ESMTP id B8D8E37B400; Sat, 13 Apr 2002 05:33:51 -0700 (PDT) Received: by host213-123-130-182.in-addr.btopenworld.com (Postfix, from userid 1001) id 340B86AA; Sat, 13 Apr 2002 13:34:07 +0100 (BST) Message-Id: <20020413123407.340B86AA@host213-123-130-182.in-addr.btopenworld.com> Date: Sat, 13 Apr 2002 13:34:07 +0100 (BST) From: Dominic Marks Reply-To: Dominic Marks To: FreeBSD-gnats-submit@FreeBSD.org Cc: keramida@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: docs/37037: Cleaned and revised the Hubs article Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 37037 >Category: docs >Synopsis: Cleaned and revised the Hubs article >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 13 05:40:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Dominic Marks >Release: FreeBSD 4.5-STABLE i386 >Organization: Student >Environment: System: FreeBSD gallium 4.5-STABLE FreeBSD 4.5-STABLE #2: Mon Apr 8 21:19:28 BST 2002 dom@gallium:/usr/obj/usr/src/sys/GALLIUM i386 >Description: Most of my changes are relating to the text. Changing the sentences so they flow better, correcting spelling mistakes and so on. Some increased application of the right DocBook tags has also been done. I also spent time reworking the lines so that the wrap less or when they do in a cleaner fashion which makes this file easier to edit. The original file also contains a lot of ambigous statements, using words like "maybe", "probably" and so on. I have attempted to replace these with factual statements where possible. Please give the spelling, grammar and SGML a good checking, since I am likely to have made some mistakes. Thanks. >How-To-Repeat: NA. >Fix: ? article.html ? docbook.css Index: article.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/hubs/article.sgml,v retrieving revision 1.13 diff -u -3 -r1.13 article.sgml --- article.sgml 2002/04/01 01:45:14 1.13 +++ article.sgml 2002/04/13 12:28:23 @@ -24,7 +24,7 @@ Valentino Vaschetto -
logo@FreeBSD.org
+
logo@FreeBSD.org
 @@ -57,8 +57,7 @@ state (at 4.5-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: + around, just to be sure. Here are some approximate figures: Full FTP Distribution: 60 GB @@ -80,11 +79,13 @@ estimates here: - Local site, no public access: basically no minimum, - but I guess < 2 Mbps make syncing a pain. - Unofficial public site: 34 Mbps is probably a good start - Official site: > 100 Mbps is recommended, also your host - should be connected as close as possible to your border router + Local site, no public access: basically no + minimum. + Unofficial public site: 34 Mbps is a good + start. + Official site: > 100 Mbps is recommended, also + your host should be connected as close as possible to your border + router. @@ -99,110 +100,120 @@ impact on CPU and memory requirements. Especially rsync is considered a memory hog, and CVSup does indeed consume some CPU. For AnonCVS it can - even be required to set up a MFS of at least - 300 MB, so you need to take this into account - for your memory requirements. + even be required to set up a Memory resident filesystem + (MFS) of at least 300 MB, so you need to take this into + account for your memory requirements. You also want to consider a fast disk subsystem. Operations on the CVS repository require a fast - disk subsystem (RAID is greatly advised). - + disk subsystem (RAID is greatly advised). A SCSI + controller that has a cache of its own will also + be of value since most of these services incur a + very large number of small modifications to the disk. + + You may also like to experiment with enlarging the portion + of system memory which is used for the filesystem buffer cache. + This will also help to reduce the quantity of disk access. This + can be done with the BUFCACHEPERCENT kernel option. The default is + to use 5% of system memory. Services to offer - - This section describes the services that are - required for you to offer, and those that are - optional. It also gives hints, which software - can be used to provide this service. - + Every mirror site is required to have a set of core services + available. Optionally you can also add additional services. This + section explains which services you can provide and how to go + about implementing them. 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 - anonymous, and no upload/download ratios - are allowed (a ridicilous thing anyway). - Upload capability is not required (and should - never be allowed for the FreeBSD file space). - Also the FreeBSD archive should be available under - the path /pub/FreeBSD. + 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 lot of software available which - can be set up to allow anonymous FTP - (in alphabetical order). + There is lot of software available which can be set up to allow + anonymous FTP (in alphabetical order). - /usr/libexec/ftpd: FreeBSD's own ftpd, - will probably do a very good job. Be sure to read &man.ftpd.8;. - - - ftp/ncftpd: a commercial package, free for - educational institutions. - - - ftp/oftpd: an ftpd designed with - security as a main focus. - - - ftp/proftpd: a modular and very flexible ftpd. - - - ftp/pure-ftpd: another ftpd developed with - security in mind. - - ftp/twoftpd: same as above - ftp/vsftpd: the very secure ftpd - - ftp/wu-ftpd: The widely used ftpd from Washington - University. It became sort of infamous, because of the huge - amount of security issues that became obvious in wu-ftpd. - It also around for a long time, which can be positive - (experience) or negative (lots of bloated code). - + /usr/libexec/ftpd: + FreeBSD's own ftpd, can be used. Be + sure to read &man.ftpd.8;. + ftp/ncftpd: + A commercial application. Available free for educational + purposes. + ftp/oftpd: + An ftpd designed with security as a main focus. + ftp/proftpd: + A modular and very flexible ftpd. + 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 number 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. - FreeBSD's ftpd, proftpd, wu-ftpd and maybe ncftpd are among the - most used ones. The others are probably not that much widespread. + + FreeBSD's ftpd, proftpd, wu-ftpd and ncftpd are among the most + commonly used. The others do not have a large userbase among + mirror sites. - RSYNC (optional for FTP fileset) + rsync (optional for FTP fileset) - Rsync is often also offered for convenience, for the - contents of the FTP area of FreeBSD. The - protocol is different from FTP in many ways, and - overall, it can be stated, that it is much more - bandwidth friendly, as only differences between files - are transferred, not whole files. - Rsync does require significant amount of memory for + rsync is often also offered for convenience, for the contents + of the FTP area of FreeBSD. The protocol is different from + FTP, specifically, it requires much less bandwidth, as only + transfers the differences between files. + rsync does require significant amount of memory for each instance. The size depends on the size of the synced module in terms of number of directories and - files. Rsync can use rsh and + files. rsync can use rsh and ssh (now default) as a transport, or use it's own protocol for stand-alone access (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: + may be applied. At the time of writing there is just one + software package available: - net/rsync + net/rsync + HTTP (required for webpages, optional for FTP fileset) - If you want to offer the FreeBSD webpages, you need - to install a webserver a.k.a httpd. You may offer - the FTP fileset via HTTP, as well, if you like. - Some argue HTTP is more efficient for download, but - I cannot tell. The most commonly - used httpd is Apache, although there are others around, - take a look at /usr/ports/www. + If you want to offer the FreeBSD webpages, you need to + install a webserver. You may offer the FTP fileset via HTTP, + optionally. You may use your own choice of Webserver software. - www/apache13 + www/apache13: + Apache is the most widely deployed Webserver on the Internet. It + is used extensively by the FreeBSD Project. You may also + wish to use the next generation of the Apache Webserver, + available in the ports collection as www/apache2. + www/thttpd: + If you are going to be serving a lot amount of static content + you may find that using an application such as tHttpd is more + efficent than Apache. It is optimized for excellent performance + on FreeBSD. + www/boa: + Boa is another alternative to tHttpd and Apache. It should + provide considerably better performance than Apache for purely + static content. It does not, at the time of writing, contain the + same set of optimizations for FreeBSD that are found in tHttpd. + @@ -214,7 +225,7 @@ the use with CVS repositories. If you want to offer the FreeBSD CVS repository, you really want to consider offering it via CVSup. Still it is possible to offer - the CVS repository via AnonCVS, FTP, Rsync or HTTP, but + the CVS repository via AnonCVS, FTP, rsync or HTTP, but people would not benefit from CVSup access. CVSup was developed by &a.jdp;. It is a bit tricky to install on non-FreeBSD platforms, @@ -222,44 +233,49 @@ a Modula-3 environmen. 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: + See Ezm3 + for details. Related ports are: - net/cvsup: The native CVSup port (client and server) - which requires lang/ezm3 now. + + net/cvsup + : The native CVSup port (client and server) which + requires lang/ezm3 + now. + - net/cvsup-mirror: The CVSup mirror kit, which requires - net/cvsup, and configures it mirror-ready. Some - site administrators may want a different setup, though. + + net/cvsup-mirror + : The CVSup mirror kit, which requires + net/cvsup, and + configures it for use as a mirror. Some site administrators + may require a different setup. - - There are a few more like net/cvsupit and - 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 stil refers to the S1G bug, that was present - in CVSup. Maybe - John will setup a generic download-site to get - static binaries for various platforms. + Further information about CVSup can + be found its website. + - 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 the server as on the - client, since it needs to compare lots of files. + It is possible to use CVSup to offer any kind of fileset, not + just CVS repositories, but configuration can be complex. + CVSup is more intensive to run on + both the server and client than the other distribution + methods. However it is significantly faster and consumes a lot + less bandwidth than the FTP service. Please have look at the CVSup - like &man.cvsup.1; and consider using the - option, as it can reduce the amount of work to be done - a lot. + documentation, for example &man.cvsup.1; and consider using the + option, as it can reduce the workload + considerably. @@ -274,10 +290,10 @@ pserver or via ssh (we don't consider rsh). For anonymous access, pserver is - very well suited, but some still offer ssh - access as well. There is some custom crafted wrapper - program around, to be used as a login-shell for the - anonymous ssh account. It does a chroot, and therefore + very well suited, but it is possible to offer + ssh access as well. For the + ssh service you can use a login wrapper to + secure the anonymous account. It does a chroot, and therefore requires the CVS repository to be available under the anonymous user's homedirectory, which may not be possible for all sites. If you just offer pserver @@ -287,28 +303,30 @@ 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 + 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. See also the cvs info - page, about how additional ways, to make sure, access is read-only. - It is advisable, that you create an unprivileged account, - preferrably 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 filesystem. 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 + See the manpage for details of the options. See also the cvs + info page, about how additional ways, to + make sure, access is read-only. It is advisable, that you create + an unprivileged account, preferrably called + anoncvs. Also you need to create a file + passwd in your mirror's + CVSROOT subdirectory and assign a CVS password + (empty or anoncvs) to that user. The + example directory /anoncvstmp is a special + purpose memory based filesystem. 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;. + Enabling SoftUpdates on a conventional + /tmp location, or mounting it with the + mode in /etc/fstab + should also help to improve performance marginally. + This was suggested by &a.jdp;. @@ -316,70 +334,86 @@ 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. + 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 - The FTP area is the largest amount of data, that - needs to be mirrored. It includes the distributions - sets, required for network installation, the - branches, that are actually snapshots - of checked-out source trees, the ISO Images - to write CD-Roms with the installation distribution, - a live filesystem, and lots of packages, the ports tree, - distfiles and a huge amount of packages. All of course - for various FreeBSD versions, and i386 - and alpha architecture. + The FTP area is the largest amount of data, that needs to be + mirrored. It includes the distributions sets, + required for network installation, the + branches, the ISO Images + for making CD-Roms with the installation distribution, a live + filesystem, and lots of packages, the ports tree, and distfiles. + All of course for various FreeBSD versions, and + i386 and alpha + architectures. + + You can expect the amount of space required by the FTP + distribution to grow in size as the number of ports and + supported architectures grows. + With FTP mirror - - You can use a FTP mirror - program, to get the files. There are a lot around, and - widely used, like: + You can use a FTP mirror + program, to get the files. There are a lot around, and widely + used, like: - ftp/mirror - ftp/ftpmirror - ftp/emirror - ftp/spegla - ftp/omi - some even use ftp/wget + + + ftp/mirror + + + + + ftp/ftpmirror + + + + + ftp/emirror + + + + + ftp/spegla + + + + + ftp/omi + + + + + ftp/wget + + - - ftp/mirror was very popular, but seemed - to have some drawbacks, as its written in perl, - and did have real problems on mirroring large - directories like a FreeBSD site. There are rumours, that - the current version has fixed this, by allowing - to specify a different algorithm for comparing - the directory structure. - In general FTP is not really good for mirroring, since it transfers - each whole file, if it has changed, and does - not create a single data stream, that will benefit from - a large TCP congestion window. + FTP is not good for mirroring, since it transfers each whole file, + if it has changed, and does not create a single data stream, that + will benefit from a large TCP congestion window. - With RSYNC + With rsync - A better 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 - in . - Since rsync access is not - required, your preferred upstream site may not allow it, - but it already widely used, so chances are small, that - you cannot use it. You can always consider using an - upstream server, that offers it, just for the benefits - of rsync. + A better 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 in + . Since + rsync access is not required, + your preferred upstream site may not allow it. In this case + you can consider using an upstream server, that offers it, + for the benefits of rsync. Since the number of rsync @@ -396,8 +430,7 @@ Consult the documentation for rsync, which is also available at http://rsync.samba.org/ - about the various options to be used with rsync. - Also you might + about the various options to be used with rsync. Also you might want to set up a script framework, that calls such a command via &man.cron.8;. @@ -405,12 +438,14 @@ 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, preferrably from the port: net/cvsup. - (Also reread .) - A sample supfile, suitable for ftp-master.freebsd.org + 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, preferrably from the port: + net/cvsup-without-gui. + (Also reread .) A sample supfile, + suitable for ftp-master.freebsd.org looks like this: # @@ -429,27 +464,27 @@ 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. In fact I just know - ftp-master.freebsd.org for sure. + Distribution via CVSup is only + available from certain sites. Mirroring the CVS repository - Again you have various possibilities, but the most - recommended one, is to use CVSup. + Again you have various possibilities, but using + CVSup is reccomended. Using CVSup CVSup was already described to some - detail in and . + detail in and + . - Here we just describe an example to set up the supfile: + Here we just describe an example to set up the + supfile: # # FreeBSD CVS supfile from master server @@ -467,36 +502,42 @@ cvs-all - You should also have a look at /usr/share/examples/cvsup + You should also have a look at the sample files available in + /usr/share/examples/cvsup/. Using other methods - Using other methods than CVSup is + Using other methods than CVSup are 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 can of course be used. + 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 can of course be used. - FTP - RSYNC - maybe even HTTP + + + FTP + + + + + rsync + + If you find a site, that supports it, you could use - net/sup, but it is inferior to CVSup - and it's deficiencies caused John Polstra to develop - CVSup in the first place, so - it is clearly not recommended. + net/sup, but it is inferior + to CVSup and it's deficiencies + caused &a.jdp; to develop CVSup in the + first place, so it is clearly not recommended. - AFAICT, you can NOT AnonCVS to - mirror the CVS repository, since CVS does not allow - you to access the repository itself, but only checked - out versions of the modules. + To mirror the AnonCVS repository you will need to use a + method other than CVS. @@ -513,14 +554,14 @@ 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 - webserver is not discussed here. + webserver is not diskussed here. If you don't 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 + 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: + looks like this: # # WWW module supfile for FreeBSD @@ -539,8 +580,9 @@ - Using ftp/wget or other web-mirror tools, is - probably not recommended. + Using ftp/wget to index and + mirror the data using FTP or HTTP is not + reccomended. Mirroring the FreeBSD documentation @@ -548,7 +590,7 @@ As the documentation is referenced a lot from the webpages, it is recommended, that you mirror the FreeBSD documentation as well. However, this is not - so trivial as the www-pages alone. + as easy to do. First of all, you should get the doc sources, @@ -573,35 +615,27 @@ - Then you need to install a couple of ports. - You are lucky, that there is a meta-port: - textproc/docproj to do the work - for you. You need to setup some - environment variables, like - SGML_CATALOG_FILES, - also have a look at your /etc/make.conf - (copy /etc/defaults/make.conf if - you don't have one), and look at the - DOC_LANG variable. - Now you are probably ready to run make - in you doc directory (/usr/share/doc - by default) and build the documentation. - Again you need to make it accessible for your webserver - and make sure, the links point to the right location. + Then you need to install a couple of ports. You are lucky, that + there is a meta-port: + textproc/docproj to do the work + for you. You need to setup some environment variables, like + SGML_CATALOG_FILES, also have a look at your + /etc/make.conf (copy + /etc/defaults/make.conf if you do not have + a /etc/make.conf), and look at the + DOC_LANG variable. Now you are probably ready + to run make in you doc directory + (/usr/share/doc by default) and build the + documentation. Again you need to make it accessible for your + webserver 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: - fdp-primer. + The building of the documentation, as well as lots of side + issues is documented itself in: fdp-primer. Please read this piece of documentation, especially if you have problems, building the documentation. - - - XXX MAYBE THIS CAN BE LINKED FROM WITHIN - NOT USING AN ABSOLUTE URL XXX - - @@ -609,28 +643,28 @@ Where to mirror from - This is an important issue. So this section will - spend some effort to explain the backgrounds. + This is an important issue. So this section will spend some effort + to explain the issues you must consider. A few words about the organisation Mirrors are organised by country. All official mirrors have a DNS entry of the form - ftpX.CC.freebsd.org. Whith - CC (i.e. country code) beeing the + ftpX.CC.freebsd.org. Where + CC (i.e. country code) is the top level domain of the country, where this mirror is located; and X is a number, telling that the host would be the Xth mirror in that country. - (Same applies to cvsupX.CC.freebsd.org, - wwwX.CC.freebsd.org, etc.) + (Same applies to cvsupX.CC.freebsd.org, + wwwX.CC.freebsd.org, etc.) There are mirrors with no CC part. - These are usually located in the US, but don't need to. - ftp.freebsd.org is currently - located in Denmark and just another mirror - (i.e. it is NO master site). + These are usually located in the US, but it is not a requirement. + ftp.freebsd.org is currently located + in Denmark and is just another mirror (i.e. it is + not the master site). Additionally there exists a hierarchy of mirrors, which @@ -638,56 +672,54 @@ The master sites are not referred to, but can be described as Tier-0. Mirrors that mirror from these sites can be considered - Tier-1, mirrors of Tier-1-mirrors, - are Tier-2, etc. - Official sites are encouraged to be of a low tier, - but the lower the tier, the higher the requirements in - terms as described in . - Also access to low-tier-mirrors may be restricted, and - access to master sites is definetly restricted. - The tier-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 Tier-1 - (this is just a rough hint, and there's no rule). + Tier-1, mirrors of + Tier-1-mirrors, are Tier-2, + etc. Official sites are encouraged to be of a low + tier, but the lower the tier, the higher the + requirements in terms as described in + . + Also access to low-tier-mirrors may be restricted, and access to + master sites is definetly restricted. The + tier-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 + Tier-1 (this is just a rough hint, and there's + no rule). Ok, but where should I get the stuff now? - The short answer is: from the - site, that is closest to you in internet terms, or gives you - the fastest access. + The short answer is: from the site, that is closest to you in + internet terms, or that gives you the fastest access. I just want to mirror from somewhere! - If you have no special intentions or - requirements, the statement in - applies. This means: + If you have no special intentions or requirements, the statement + in applies. This means: Look at available mirrors in your country. - The FreeBSD + The + FreeBSD Mirror Database can help you with this. - Check roughly those, which provide fastest access - (number of hops, round-trip-times) - and offer the services you intend to - use (like rsync - or CVSup). + Check roughly those, which provide fastest access (number of + hops, round-trip-times) and offer the services you intend to + use (like rsync or + CVSup). Contact the admins of your chosen site, stating your - request, and asking about their terms and - policies. + request, and asking about their terms and policies. @@ -703,28 +735,26 @@ 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 - a low tier. - There are some other considerations about official - mirrors, that are described in . + a low tier. There are some further considerations about + official mirrors, that are described in + . I want to access the master sites! - If you have good reasons, and good prerequesites, - you may want and get access to one of the - master sites. Access to these sites is - generally restriced, and there are special policies - 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 + If you have good reasons, and good prerequesites, you may want + and get access to one of the master sites. Access to these sites + is restriced, and there are special policies 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 &a.hubs; first. - There are just two master sites, for the FTP fileset and - for the CVS repository (the webpages and docs are obtained from CVS, - so there is no need for it). + There are just two master sites, for the FTP fileset and for the + CVS repository (the webpages and docs are obtained from CVS, so + there is no need for it). ftp-master.freebsd.org @@ -732,22 +762,23 @@ This is the master site for the FTP fileset. - ftp-master.FreeBSD.org provides - rsync and CVSup - access, rather in addition to ftp protocol. - Refer to and - how to access - via these protocols. + ftp-master.FreeBSD.org provides + rsync and + CVSup access, rather in addition to + ftp protocol. Refer to and + how to access via these + protocols. + + + Mirrors should be encouraged to also allow + rsync access for the FTP contents, + since they are Tier-1-mirrors. + + + To get access to + ftp-master.FreeBSD.org, you need + to contact &a.peter;. - - Mirrors should be encouraged to also allow rsync - access for the FTP contents, since they are - Tier-1-mirrors. - - - To get access to ftp-master.FreeBSD.org, - you need to contact &a.peter;. - cvsup-master.freebsd.org @@ -755,24 +786,23 @@ This is the master site for the CVS repository. - cvsup-master.FreeBSD.org provides - CVSup access only. - See for details. + cvsup-master.FreeBSD.org provides + CVSup access only. See + for details. - To get access, you need to contact &a.jdp;. - Make sure you read - FreeBSD CVSup Access Policy - first! + To get access, you need to contact &a.jdp;. Make sure you read + + 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 + freefall.freebsd.org on the + cvpasswd command line, as described in this document, even + when you are contacting + cvsup-master.freebsd.org @@ -785,14 +815,14 @@ - a) have a freebsd.org DNS entry - (usually a CNAME). + Have a freebsd.org DNS entry (usually a + CNAME). - b) are listed as an official mirror in the FreeBSD - documentation (like handbook). + Are listed as an official mirror in the FreeBSD documentation + (The Handbook). @@ -805,12 +835,11 @@ Special Requirements for official (tier-1) mirrors - 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 official tier-1 mirrors - are required to. All other official mirrors, - can consider this a big should. + It is not so easy to state requirements for all official mirrors, + since the project is more tolerant here. It is more easy to say, + what official tier-1 mirrors are required to. + All other official mirrors, can consider this a big + should. The following applies mainly to the FTP fileset, @@ -823,51 +852,57 @@ Tier-1 mirrors are required to: - to carry the complete fileset - allow access to other mirror sites - provide FTP and - RSYNC access + + To carry the complete fileset + + + Allow access to other mirror sites + + + Provide FTP and + rsync access + Furthermore, admins should be subscribed to the &a.hubs;. - See this link for details, how to subscribe. + See this link for details, how + to subscribe. - It is very important for a hub administrator, especially - Tier-1 hub admins, to check the - release schedule - 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. - - - It is also eminent that hub administrators try to keep their mirrors as up-to-date as - possible (again, even more crucial for Tier-1 mirrors). If Mirror1 doesn't 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! + It is very important for a hub + administrator, especially Tier-1 hub admins, to check the + release + schedule for the next FreeBSD release. This is important + because after a release there is a large load spike on all mirrors. + + + It is also eminent that hub administrators try to keep their + mirrors as up-to-date as possible (again, even more crucial for + Tier-1 mirrors). If Mirror1 doesn't 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! How to become official then? - An interesting questions, especially, since the state - of beeing 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. + An interesting questions, especially, since the state of beeing + 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. - Before applying, please consider (again) if - another official mirror is really needed for - your region. Ask on the &a.hubs;, if in doubt. + Before applying, please consider (again) if another official mirror + is really needed for your region. Ask on the &a.hubs;, if in doubt. Ok, here is how to do it: - Get the mirror running in first place (maybe not - using a master site, yet). + Get the mirror running in first place (maybe not using a + master site, yet). @@ -886,9 +921,8 @@ in . - If there is no subdomain delegated, yet, for your - country, you probably need to contact - hostmaster@freebsd.org, + If there is no subdomain delegated, yet, for your country, you + probably need to contact hostmaster@freebsd.org, however, you can try the &a.hubs; first. @@ -916,29 +950,38 @@ ftp2.FreeBSD.org - grisha@ispol.com - - (Bandwidth) + + Bandwidth ftp.is.FreeBSD.org - oli@isnic.is - - (Bandwidth) (FTP - processes) (HTTP processes) + Bandwidth + + FTP sessions + + HTTP sessions ftp.cz.FreeBSD.org - cejkar@fit.vutbr.cz - - (Bandwidth) - (FTP processes) - (Rsync processes) + + Bandwidth + + FTP sessions + + rsync sessions ftp4.de.FreeBSD.org - dl@leo.org - - (FTP users) - (RSYNC users) - (Bandwidth) + + FTP sessions + + rsync sessions + Bandwidth @@ -947,19 +990,35 @@ CVSup site stats - cvsup5.FreeBSD.org - staff@blackened.com - (CVSup processes) + + cvsup5.FreeBSD.org - + staff@blackened.com - + + CVSup sessions + - cvsup[23456].jp.FreeBSD.org - kuriyama@FreeBSD.org - (CVSup processes) + + cvsup[23456].jp.FreeBSD.org - + kuriyama@FreeBSD.org - + + CVSup sessions + - cvsup.cz.FreeBSD.org - cejkar@fit.vutbr.cz - - (CVSup processes) + + cvsup.cz.FreeBSD.org - + cejkar@fit.vutbr.cz - + + CVSup sessions + - [cvsup3|anoncvs].de.FreeBSD.org - dl@leo.org - - (CVSup processes) + + [cvsup3|anoncvs].de.FreeBSD.org - + dl@leo.org - + + CVSup sessions + >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message