diff --git a/en_US.ISO8859-1/articles/hubs/article.sgml b/en_US.ISO8859-1/articles/hubs/article.sgml index ba058abf0e..5ea79108d8 100644 --- a/en_US.ISO8859-1/articles/hubs/article.sgml +++ b/en_US.ISO8859-1/articles/hubs/article.sgml @@ -36,13 +36,28 @@
dl@leo.org
+ + Ken + Smith + +
kensmith@cse.buffalo.edu
+ + An in-progress article on how to mirror FreeBSD, aimed at - hub administrators + hub administrators. + + Contact Information + + The Mirror System Coordinators can be reached through email + at mirror-admin@FreeBSD.org. There is also + a &a.hubs;. + + Requirements for FreeBSD mirrors @@ -51,21 +66,21 @@ 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, + 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 4.5-RELEASE). Further development and + always be mirrored completely. Also note that the + numbers stated here are reflecting the current + state (at 4.8-RELEASE/5.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. + Also make sure to keep some (ca. 10-20%) extra space + around just to be sure. Here are some approximate figures: - Full FTP Distribution: 100 GB - CVS repository: 2 GB - CTM deltas: 1.5 GB + Full FTP Distribution: 126 GB + CVS repository: 2.7 GB + CTM deltas: 1.8 GB Webpages: 300 MB @@ -76,27 +91,27 @@ 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 or even if you intend - to become an official mirror. We can only give rough + 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 a pain. + but < 2 Mbps could make syncing too slow. Unofficial public site: 34 Mbps is probably a good start. - Official site: > 100 Mbps is recommended, also your host + Official site: > 100 Mbps is recommended, and your host should be connected as close as possible to your border router. System Requirements, CPU, RAM - This also depends on the expected amount of clients, - which is determined by the servers policy. It is + 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 + 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 @@ -107,7 +122,7 @@ are just examples to give you a very rough hint. - For a moderately visited site, that offers + 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 @@ -115,18 +130,18 @@ site. - For a frequently used site you need definitely - more RAM (consider 2GB as a good start), - and possibly more CPU, which could also mean, + 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 greatly advised). A SCSI + 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 - very large number of small modifications to the disk. + speed up things since most of these services incur a + large number of small modifications to the disk. You can also experiment with enlarging the portion of system memory which is used for the file system buffer cache. @@ -139,8 +154,8 @@ Services to offer Every mirror site is required to have a set of core services - available. In addition to these basic services, which mirrors are - required to provide, there is a number of optional services that + 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. @@ -148,7 +163,7 @@ FTP (required for FTP fileset) This is one of the most basic services, and - it is required for each mirror, offering public + 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). @@ -194,22 +209,25 @@ FreeBSD's ftpd, proftpd, wu-ftpd and maybe ncftpd are among the most commonly ones. - The others do not have a large userbase among mirror sites. + The others do not have a large userbase among mirror sites. One + thing to consider is that you may need flexibility in limiting + how many simultaneous connections are allowed, thus limiting how + much network bandwidth and system resources are consumed. 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 + 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. + It is much more bandwidth friendly, as only differences between files - are transferred, not whole files. - Rsync does require significant amount of memory for + are transferred instead of whole files when they change. + rsync does require a 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 + the synced module in terms of the number of directories 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). @@ -242,7 +260,7 @@ www/thttpd: - If you are going to be serving a lot amount of static content + 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 optimized for excellent performance on FreeBSD. @@ -263,10 +281,10 @@ CVSup (desired for CVS repository) CVSup is a very efficient way of distributing files. - It works similar as rsync, but was specially designed for - the use with CVS repositories. If you want to offer the + 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. Still it is possible to offer + 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. @@ -274,7 +292,7 @@ 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 + stripped down version of M3 that is sufficient to run CVSup, and can be installed much easier. See Ezm3 for details. Related ports are: @@ -287,7 +305,7 @@ 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. + site administrators may want a different setup though. @@ -296,16 +314,16 @@ 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 + This page still 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. - It is possible to use CVSup to offer + 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 + CVSup is known to eat some CPU on both the server and the client, since it needs to compare lots of files. @@ -314,12 +332,12 @@ If you have the CVS repository, you may want to offer anonymous CVS access. A short warning first: - There is not that much demand for it, - and it requires some experience and you need to know, + 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, how + Generally there are two ways to access a CVS repository remotely: via pserver or via ssh (we don't consider rsh). @@ -330,7 +348,7 @@ 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, which may not be possible + 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 don't need to install any special @@ -341,19 +359,19 @@ 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 additional ways to make sure, access is read-only. - It is advisable, that you create an unprivileged account, + 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 + 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. + 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: @@ -365,9 +383,9 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all - How to mirror FreeBSD + How to Mirror FreeBSD - Ok now, you know the requirements, and how to offer + 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, @@ -376,22 +394,22 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all 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 + 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, 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. + 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. With FTP mirror You can use a FTP mirror - program, to get the files. There are a lot around, and + program to get the files. There are a lot around and widely used, like: ftp/mirror @@ -404,40 +422,38 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all ftp/mirror was very popular, but seemed to have some drawbacks, as it is written in &man.perl.1;, - and did have real problems on mirroring large - directories like a FreeBSD site. There are rumors, that - the current version has fixed this, by allowing - to specify a different algorithm for comparing - the directory structure. + 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, since it transfers - each whole file, if it has changed, and does - not create a single data stream, that will benefit from + 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. + 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. - Since it is quite common, though, 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. + You may need to hunt around a little bit to find a site + 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 server. For a mirror, you should ask the site maintainer - you are syncing from, about their policy, and maybe + you are syncing from about their policy, and maybe an exception for your host (since you are a mirror). @@ -452,19 +468,19 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all be aware that the module-directory (here "FreeBSD") will not be created, so you cannot omit the target directory. Also you might - want to set up a script framework, that calls such a command + want to set up a script framework that calls such a command via &man.cron.8;. With CVSup - A few sites, including the one-and-only 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, preferably from the port: net/cvsup. + client, preferably from the port net/cvsup. (Also reread .) - A sample supfile, suitable for ftp-master.FreeBSD.org + A sample supfile suitable for ftp-master.FreeBSD.org looks like this: # @@ -484,9 +500,8 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all 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. + way to mirror the archive in terms of efficiency, but + it is only available from few sites. Please have look at the CVSup documentation @@ -502,7 +517,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all Mirroring the CVS repository Again you have various possibilities, but the most - recommended one, is to use CVSup. + recommended one is to use CVSup. Using CVSup @@ -533,7 +548,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all - Please don't forget to consider the hint, + Please do not forget to consider the hint mentioned in this note above. @@ -554,16 +569,16 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all maybe even HTTP - 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 + If you find a site that supports it, you could use + net/sup. But it is inferior to CVSup + and its deficiencies caused John Polstra to develop CVSup in the first place, so it is clearly not recommended. You can NOT use AnonCVS to - mirror the CVS repository, since CVS does not allow + mirror the CVS repository since CVS does not allow you to access the repository itself, but only checked out versions of the modules. @@ -574,13 +589,13 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all Mirroring the WWW pages - The best way is, to check out the www + The best way is to check out the www distribution from CVS. If you have a local mirror of the CVS repository, it is probably 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 + 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. @@ -588,7 +603,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all For the website to be visible, users must execute the &man.make.1; command in the main www directory. This command will create the standard *.html files for web - viewing. For this to work, however, the + viewing. For this to work however, the textproc/docproj port must be installed. @@ -615,16 +630,16 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all - Using ftp/wget or other web-mirror tools, is + Using ftp/wget or other web-mirror tools is probably not recommended. Mirroring the FreeBSD documentation - As the documentation is referenced a lot from the - webpages, it is recommended, that you mirror the + Since 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 trivial as the www-pages alone. First of all, you should get the doc sources, @@ -650,27 +665,27 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all Then you need to install a couple of ports. - You are lucky, that there is a meta-port: + You are lucky, there is a meta-port: textproc/docproj to do the work - for you. You need to setup some + for you. You need to set up some environment variables, like - SGML_CATALOG_FILES, - also have a look at your /etc/make.conf + 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 + you do not 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. + 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. Please read this piece of documentation, especially if you - have problems, building the documentation. + have problems building the documentation. @@ -686,7 +701,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all Every mirror should be updated on a regular basis. You will certainly need some script - framework for it, that will be called by + 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 @@ -702,19 +717,25 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all - Add some output redirections, so diagnostic + Add some output redirections so diagnostic messages are logged to a file. - Test, if your script works. Check the logs. + Test if your script works. Check the logs. - Use &man.crontab.1; to add the script the - appropriate user's &man.crontab.5;. + Use &man.crontab.1; to add the script to the + appropriate user's &man.crontab.5;. 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 — + making sure all of the official mirror sites have all of the + necessary release files on release day. @@ -732,53 +753,62 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all Where to mirror from This is an important issue. So this section will - spend some effort to explain the backgrounds. + 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 Mirrors are organized by country. All official mirrors have a DNS entry of the form - ftpN.CC.FreeBSD.org. With - CC (i.e. country code) being the - top level domain - of the country, where this mirror is located; - and N is a number, + ftpN.CC.FreeBSD.org. + CC (i.e. country code) is the + top level domain (TLD) + of the country where this mirror is located. + N is a number, telling that the host would be the Nth mirror in that country. (Same applies to cvsupN.CC.FreeBSD.org, wwwN.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 the mirror sites that are very well connected and + allow a large number of concurrent users. + ftp.FreeBSD.org is actually two machines, one currently + located in Denmark and the other in the United States. + It is NOT a master site and should never be + used to mirror from. Lots of online documentation leads + interactiveusers to + 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 terms of tiers. - The master sites are not referred to, but can be + is described in terms of tiers. + 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 + 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 definitely 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, + 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). + (this is just a rough hint, and there is no rule). 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 + site that is closest to you in Internet terms, or gives you the fastest access. @@ -798,7 +828,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all - Check roughly those, which provide fastest access + Check for those which provide fastest access (number of hops, round-trip-times) and offer the services you intend to use (like rsync @@ -807,7 +837,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all - Contact the admins of your chosen site, stating your + Contact the administrators of your chosen site stating your request, and asking about their terms and policies. @@ -824,28 +854,36 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all 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 + 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 . + mirrors that are described in . I want to access the master sites! - If you have good reasons, and good prerequisites, + If you have good reasons and good prerequisites, you may want and get access to one of the master sites. Access to these sites is generally restricted, and there are special policies for access. If you are already an 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. + If it already has three or more, ask the zone administrator (hostmaster@CC.freebsd.org) or &a.hubs; 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 + site. If not, you can send email to + mirror-admin@FreeBSD.org to request help with + that. - There are just two master sites, one for the FTP fileset and + There are three master sites for the FTP fileset and one for the CVS repository (the webpages and docs are - obtained from CVS, so there is no need for it). + obtained from CVS, so there is no need for master). ftp-master.FreeBSD.org @@ -865,10 +903,6 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all access for the FTP contents, since they are Tier-1-mirrors. - - To get access to ftp-master.FreeBSD.org, - you need to contact &a.ftp-master;. - cvsup-master.FreeBSD.org @@ -956,13 +990,13 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all It is very important for a hub administrator, especially Tier-1 hub admins, to check the - release schedule + 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 + It is also important that hub administrators try to keep their mirrors as up-to-date as possible (again, even more crucial for Tier-1 mirrors). If Mirror1 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! @@ -974,14 +1008,14 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all An interesting question, especially, since the state of being official comes with some benefits, like a much - higher bill from your ISP, as more people will be using - your site. Also it may be a key requirement, to get access + 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. + your region. Check first with your zone administrator (hostmaster@CC.FreeBSD.org) or, if that fails, ask on the &a.hubs;. Ok, here is how to do it: @@ -998,32 +1032,32 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all - If everything works so far, contact the DNS admin, responsible + If everything works so far, contact the DNS administrator responsible for your region/country, and ask for a DNS entry for your site. The admin should able to be contacted via - hostmaster@cc.FreeBSD.org, which - cc being your country code/TLD - again. Your DNS entry will look like described + hostmaster@CC.FreeBSD.org, where + CC is your country code/TLD. + Your DNS entry will be as described in . - 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. + If there is no subdomain set up for your + country yet, you should contact + mirror-admin@FreeBSD.org, + or you can try the &a.hubs; first. - Then you can ask the &a.doc; or the &a.hubs; - to add your mirror site to the mirror list in the + Whoever helps you get an official name should send email + to mirror-admin@FreeBSD.org so your site will be + added to the mirror list in the FreeBSD - Handbook. Make sure you tell them the email address, - to list as the maintainer of the site. + Handbook. - This is it. + That is it.