![[OpenBSD]](images/smalltitle.gif){kind=small}
>ualberta.ca # University of Alberta 129.128.1.131 #file13.ucs.ualberta.ca 129.128.98.17 #mystery.ucs.ualberta.ca 129.128.125.40 #drake-en0.ucs.ualberta.ca
>stacken.kth.se # Royal Institute of Technology Computer Club 130.237.234.3 #milko.stacken.kth.se 130.237.234.43 #hot.stacken.kth.se 130.237.237.230 #fishburger.stacken.kth.se
>cs.wisc.edu # Univ. of Wisconsin-Madison, Computer Sciences Dept. 128.105.132.14 #timon.cs.wisc.edu 128.105.132.15 #pumbaa.cs.wisc.edu 128.105.132.16 #zazu.cs.wisc.edu
| Australia (Perth) | rsync://ftp.it.net.au/openbsd/ |
| Australia (Sydney) | rsync://rsync.planetmirror.com/openbsd/ |
| Austria (Vienna) | rsync://gd.tuwien.ac.at/gds/opsys/OpenBSD/ |
| Finland | rsync://ftp.fi.debian.org/OpenBSD/ |
| France (Paris) | rsync://rsync.bsdfr.org/OpenBSD/ |
| Germany (München) | rsync://ftp.leo.org/OpenBSD/ |
| Germany (Stuttgart) | rsync://ftp.uni-stuttgart.de/OpenBSD/ |
| Germany (Erlangen) | rsync://openbsd.informatik.uni-erlangen.de/OpenBSD/ |
| Greece (Thrace) | rsync://ftp.duth.gr/OpenBSD/ |
| Japan (Tokyo) | rsync://ftp.kddlabs.co.jp/openbsd/ |
| The Netherlands (Utrecht) | rsync://ftp.nluug.nl/OpenBSD/ |
| Norway (Oslo) | rsync://ftp.uninett.no/OpenBSD/ |
| Poland | rsync://sunsite.icm.edu.pl/ftp/pub/OpenBSD/ |
| Sweden (Uppsala) | rsync://ftp.sunet.se/pub/OpenBSD/ |
| Switzerland | rsync://mirror.solnet.ch/OpenBSD/ |
| Taiwan | rsync://openbsd.nsysu.edu.tw/OpenBSD/ |
| Turkey | rsync://ftp.linux.org.tr/OpenBSD/ |
| United Kingdom (London) | rsync://rsync.plig.org/OpenBSD/ |
| USA (Redwood City, CA) | rsync://ftp5.usa.openbsd.org/ftp/ |
| USA (Boulder, CO) | rsync://ftp3.usa.openbsd.org/ftp/ |
| USA (Newark, DE) | rsync://ftp.lug.udel.edu/OpenBSD/ |
| USA (State College, PA) | rsync://carroll.cac.psu.edu/openbsd/ |
| USA (Springfield, VA) | rsync://ftp.tux.org/ftp/bsd/openbsd/ |
| USA (Madison, WI) | rsync://mirror.cs.wisc.edu/openbsd/ |
The file structure of each server is roughly:
People setting up new FTP/ANONCVS mirrors
will be interested in the following disk space usage estimates for
what is maintained at
ftp://ftp.openbsd.org:/pub/OpenBSD/.
The current policy requires mirrors listed on this page to provide at least
the last two releases in binary form (currently 3.3 and 3.4) for all
architectures, as well as the OpenSSH/, patches/ and tools/ directories.
Depending on the disk space available, mirrors may provide more contents, such
as snapshots, older releases, current source tree, etc.
The current disk space usage on the master ftp site is as follows:
current could be
pub/OpenBSD/2.9 3.0GB 3.0GB (OpenBSD 2.9 release)
pub/OpenBSD/3.0 4.5GB 4.5GB (OpenBSD 3.0 release)
pub/OpenBSD/3.1 6.9GB 6.9GB (OpenBSD 3.1 release)
pub/OpenBSD/3.2 11.8GB 11.8GB (OpenBSD 3.2 release)
pub/OpenBSD/3.3 14.0GB 14.0GB (OpenBSD 3.3 release)
pub/OpenBSD/3.4 11.0GB 14.0GB (OpenBSD 3.4 release)
pub/OpenBSD/snapshots 8.5GB bigger! (current snapshots, normally >= the
last distribution in size)
pub/OpenBSD/src .6GB .7GB (ftpable src tree, checked out from
anoncvs nightly You should probably
avoid using ftp mirror to get this,
It's better to just update it yourself
with a checkout from a nearby anoncvs
server.)
Hence, a complete mirror requires about 50GB of disk space, but limiting to the
last two releases, only 25GB are necessary.
Note that the master ftp site also provides the following directories, that
mirrors should not need to provide:
pub/OpenBSD/distfiles 4.4GB bigger! (distfiles used by the ports subsystem
makefiles. You probably should not
mirror these unless you want them for
other reasons yourself. The ports
makefiles will only look at
ftp.openbsd.org and ftp.usa.openbsd.org
by default for these)
If you add a new FTP, HTTP, AFS or RSYNC mirror site, please contact www@openbsd.org.
www@openbsd.org