File: [local] / www / anoncvs.html (download) (as text)
Revision 1.379, Sat Apr 27 13:26:40 2013 UTC (11 years, 1 month ago) by sthen
Branch: MAIN
Changes since 1.378: +0 -11 lines
sync
|
<!-- DO NOT EDIT ANONCVS.HTML MANUALLY - IT IS GENERATED FROM TEMPLATES!
See comments in www/build/mirrors.dat for details -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBSD AnonCVS</title>
<link rev="made" href="mailto:www@openbsd.org">
<meta name="resource-type" content="document">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="description" content="How to get OpenBSD updates via Internet using Anonymous CVS">
<meta name="keywords" content="openbsd,anoncvs,updates">
<meta name="distribution" content="global">
<meta name="copyright" content="This document copyright 1996-2012 by OpenBSD.">
</head>
<body bgcolor="#ffffff" text="#000000">
<a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
<p>
<h2><font color="#e00000">Anonymous CVS</font></h2>
<hr>
<h3>Table Of Contents</h3>
<ul>
<li><a href="#anoncvs">What is Anonymous CVS?</a>
<li><a href="#CVS">What is CVS?</a>
<li><a href="#CRYPTO">Getting Crypto Sources Through cvs(1)</a>
<li><a href="#starting">Getting Started Using Anonymous CVS</a>
<li><a href="#using">Using CVS to Get and Update your Source Tree</a>
<li><a href="#EXAMPLE">Example usages for cvs(1)</a>
<li><a href="#CVSROOT">Available Anonymous CVS Servers</a>
<li><a href="#MIRROR">Setting up an anoncvs mirror</a>
<li><a href="#NOTES">Final notes</a>
</ul>
<hr>
<h3><a name="anoncvs"><font color="#0000e0">What is Anonymous CVS?</font></a></h3>
<p>
Anonymous CVS is a method of keeping your local copy of the OpenBSD source
tree up to date with respect to changes made to current OpenBSD sources.
In addition to following the bleeding edge of development, it is
also possible to track the patches for errata of a release.
<p>
The major advantage of Anonymous CVS over other source code update
techniques is that it works directly against a central source code
repository or mirror. This means that you have the full set of CVS
commands available to control merging and updating your changes with
other source changes and for performing diffs, change histories
and other queries against the central repository.
<p>
The OpenBSD Project currently has four active and two historic
source repositories:
<ul>
<li><b>src</b> - Houses all source code for the OpenBSD Operating System.
<li><b>ports</b> - Houses the <a href="faq/ports/index.html">OpenBSD Ports</a>.
<li><b>www</b> - Houses all OpenBSD web pages. (Including this one).
<li><b>xenocara</b> - Houses OpenBSD's active X.org v7 source tree.
<li><b>X11</b> and <b>XF4</b> - Houses OpenBSD's adaptation of the
<a href="http://www.XFree86.org/">XFree86-3</a> and XFree86-4
source trees.
These are here just for historical purposes, most users will have
no reason to use this tree, it is no longer being used.
</ul>
<p>
To summarize, the real strength of using Anonymous CVS is that it is
a "tolerant" source code control system - it <strong>respects</strong>
changes that you have made to your local sources and makes <strong>
"best efforts"</strong> to update your entire source tree, rather than
leaving you a list of arcane problems that have to be resolved before
continuing.
<h3><a name="CVS"><font color="#0000e0">What is CVS?</font></a></h3>
<p>
<a href="http://ximbiot.com/cvs/">CVS</a> is the source code control
system used to <a href="why-cvs.html">manage the OpenBSD source
tree.</a>
It implements a central repository for all officially released source code
and changes, while permitting developers to maintain local copies of the
source code with their working changes.
There are two levels of source tree access:
<ul>
<li><b>Read-write access for developers:</b>
Developers who need to commit changes to the source tree must have an
account on the OpenBSD machines.
Getting this access will be a natural result of working on the sources
with other OpenBSD developers.
If someone does some good work and shows they can work with the team,
they will get an account.
<li><b>Read-only access for everyone:</b>
Anyone can access the read-only CVS repositories.
These copies of the read-write CVS repository are mirrored often.
</ul>
<p>
The major strength of CVS is that it has the ability to perform intelligent
merges of changes to the central repository with changes that you make to
your local copy. This means that if you make a change to a module and
perform an update, your changes are not "blown away", rather CVS makes
best efforts to merge the changes made to the central sources with changes
you've made to your local copy.
<p>
In the event that the changes can't be completely merged, CVS provides a
"soft fallback", providing you with annotated changes to your
local copy, preserving an unmodified copy of your version and continuing
to update any other source modules you requested.
<h3><a name="CRYPTO"><font color="#0000e0">Getting crypto sources through
cvs(1)</font></a></h3>
<p>
<strong>IMPORTANT NOTE:</strong>
There are a few issues relating to cryptographic software that everyone
should be aware of:
<ul>
<li>The OpenBSD sources are from Canada.
As
<a href="http://www.efc.ca/pages/doc/crypto-export.html">
researched by a Canadian individual</a>
and as
<a href="http://axion.physics.ubc.ca/ECL.html">
described in the Export Control list of Canada</a>
it is legal to export crypto software from Canada to the world.
<p>
<li>However, if you are outside the USA or Canada, you should not
fetch the cryptographic sections of the OpenBSD sources from an
anoncvs server located in the USA.
Because of US Dept. of Commerce policy, crypto software may only
be exported to Canada from the USA.
</ul>
<h3><a name="starting"><font color="#0000e0">Getting Started Using Anonymous
CVS</font></a></h3>
While you can download the entire source tree from an AnonCVS server,
you can often save a lot of time and bandwidth by "preloading" your
source tree with the source files from either the OpenBSD CD or from an
FTP server.
This is particularly true if you are running
<a href="stable.html"><i>-stable</i></a>, as relatively few files change
between the <i>-release</i> and <i>-stable</i>.
<p>
To extract the source tree from the CD to <i>/usr/src</i> (assuming the CD is
mounted on /mnt):
<pre>
# <b>cd /usr/src</b>
# <b>tar xzf /mnt/src.tar.gz</b>
# <b>cd /usr</b>
# <b>tar xzf /mnt/xenocara.tar.gz</b>
# <b>tar xzf /mnt/ports.tar.gz</b>
</pre>
The source files for download from the FTP servers are separated into two
files to minimize the time required to download for those wishing to work
with only one part of the tree. The two files are <tt>sys.tar.gz</tt>,
which contains the files used to create the kernel, and <tt>src.tar.gz</tt>
which contains all the other "userland" utilities.
In general, however, you will usually want both of them installed.
Assuming the downloaded files, <tt>src.tar.gz</tt>,
<tt>sys.tar.gz</tt> and <tt>xenocara.tar.gz</tt> are in <tt>/usr</tt>:
<pre>
# <b>cd /usr/src</b>
# <b>tar xzf ../sys.tar.gz</b>
# <b>tar xzf ../src.tar.gz</b>
# <b>cd /usr</b>
# <b>tar xzf xenocara.tar.gz</b>
# <b>tar xzf ports.tar.gz</b>
</pre>
<p>
Not all people will wish to unpack all the file sets, but as the system
must be kept in sync, you will generally need to set up all trees.
<p>
You can also just use cvs(1) to "<b>checkout</b>" the source repository
for you. This is discussed in the <a href="#using">next section</a>.
<p>
After this, <tt>/usr/src</tt> will be a nice checkout area where all
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html">
cvs(1)</a> commands will work properly.
<h3><a name="using"><font color="#0000e0">Using CVS to Get and Update your
Source Tree</font></a></h3>
<p>
CVS was designed to be a simple way to retrieve and update your sources.
You must first decide whether you want to track <i>-current</i> or a
<a href="stable.html">patch branch</a>.
The current tree has all of the up to the minute changes,
whereas a patch branch contains a formal release plus the patches
from the <a href="errata.html">errata</a> and lesser issues already applied.
For more information on these "flavors" of OpenBSD, see
<a href="faq/faq5.html#Flavors">here</a>.
<p>Once you have decided which tree to follow, you must choose which Anonymous
CVS server you are going to use. A list of these servers is
<a href="#CVSROOT">below</a>.
<p>
Once you have chosen which <a href="#CVSROOT">Anonymous CVS Server</a> you will
use, you can start using cvs. For those of you
who have CDs you can start with the CVS checkout that is on the CD by using
the method <a href="#starting">above</a> to get the sources onto your system.
If you don't have a CD handy, use the method below to checkout the sources.
<p>
<ul><li>First, start out by `get'-ing an initial tree:
<p> (If you are following <i>current</i>):
<pre>
# <strong>cd /usr</strong>
# <strong>cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -P src</strong>
</pre>
<p> (If you are following the patch branch for 5.2):
<pre>
# <strong>cd /usr</strong>
# <strong>cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_5_2 -P src</strong>
</pre>
<!-- DO NOT EDIT ANONCVS.HTML MANUALLY - IT IS GENERATED FROM TEMPLATES! -->
<li> Anytime afterwards, to `update' this tree:
<p> (If you are following <i>current</i>):
<pre>
# <strong>cd /usr/src</strong>
# <strong>cvs -q up -Pd</strong>
</pre>
<p> (If you are following the patch branch for 5.2):
<pre>
# <strong>cd /usr/src</strong>
# <strong>cvs -q up -rOPENBSD_5_2 -Pd</strong>
</pre>
Every time you ran this it would synchronize your /usr/src tree.
It would not destroy any of your local changes, rather it would attempt
to merge changes in.
<p>
<li> NOTE:
If you are updating a source tree that you initially fetched
from a different server, or from a CD, you <strong>must</strong>
add the <em>-d anoncvs@anoncvs.ca.openbsd.org:/cvs</em> options to cvs.
<pre>
# <strong>cd /usr/src</strong>
# <strong>cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs -q up -Pd</strong>
</pre>
</ul>
<p>
To <a name="ports">use</a> <a href="faq/ports/index.html">ports</a>,
it is similar to src:
<ul><li>
<p> (If you are following <i>current</i>):
<pre>
# <strong>cd /usr</strong>
# <strong>cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -P ports</strong>
</pre>
<p> (If you are following the patch branch for 5.2):
<pre>
# <strong>cd /usr</strong>
# <strong>cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_5_2 -P ports</strong>
</pre>
<li> Anytime afterwards, to `update' this tree:
<p> (If you are following <i>current</i>):
<pre>
# <strong>cd /usr/ports</strong>
# <strong>cvs -q up -Pd</strong>
</pre>
<p> (If you are following the patch branch for 5.2):
<pre>
# <strong>cd /usr/ports</strong>
# <strong>cvs -q up -rOPENBSD_5_2 -Pd</strong>
</pre>
</ul>
In the above example, <i>-q</i> is optional, only intended to minimize
cvs's output.
For those who like to see screenfulls of output, it can be omitted.
<p>
To make a diff of a locally patched module (here <i>cd.c</i>) to include with
a bug report:
<pre>
# <strong>cd /usr</strong>
# <strong>cvs diff -u src/sys/scsi/cd.c > /tmp/patch</strong>
</pre>
<p>
The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html">
cvs(1) man page</a>
(included with the CVS sources) has much more
information about how CVS can be used.
<p>
<strong>Warning:</strong>
When using cvs you should take care that your current directory is either
the root of the tree you are referencing or in a separate place such as /tmp.
Some commands such as "get" can create an arbitrary sub-tree in the current
directory, and a subsequent update will recursively flesh out this sub-tree.
<p>
The anoncvs service gives fledgling developers a chance to learn CVS
operation and get thoroughly involved in the development process
before getting "commit" access -- as a result of showing useful
skills and high quality results they will naturally later be given
developer access.
As well, people providing patches can create their "diff"s relative
to the CVS tree, which will ease integration.
<h3><a name="EXAMPLE"><font color="#0000e0">Example usages for cvs(1)</font>
</a></h3>
<p>
A sample use of an anoncvs server would be:
<pre>
$ <strong>cd /tmp</strong>
$ <strong>cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs get src/sys/arch/sparc</strong>
[copies the files from the repository to your machine]
$ <strong>cd src/sys/arch/sparc</strong>
$ <strong>cvs log locore.s</strong>
[shows the commit log for the chosen file]
$ <strong>cvs diff -bc -r1.1 -r1.5 locore.s</strong>
[shows the changes between revisions 1.1 and rev 1.5]
</pre>
<h3><a name="CVSROOT"><font color="#0000e0">Available Anonymous CVS Servers
</font></a></h3>
<p>
<ul>
<li><strong>CVSROOT=anoncvs@anoncvs.openbsd.org.ar:/cvs</strong><br>
Location: Buenos Aires, Argentina.<br>
Maintained by <a href="mailto:gonzalo@openbsd.org">Gonzalo Lionel Rodriguez</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours from anoncvs.spacehopper.org.<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs.bom.nom.co:/cvs</strong><br>
Location: Sydney, Australia.<br>
Maintained by <a href="mailto:mb@ii.net">Michael W. Bombardieri</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours from anoncvs.usa.openbsd.org.<br>
SSH fingerprints:<br>
(RSA) 2048 72:97:71:77:82:80:e1:f0:1c:1d:bc:01:b5:39:97:fa<br>
(DSA) 1024 67:5d:e1:ba:b7:d3:40:7c:9c:4f:15:d4:1b:0b:e1:58<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs.au.openbsd.org:/cvs</strong><br>
Location: Brisbane, Australia.<br>
Maintained by <a href="mailto:dlg@openbsd.org">David Gwynne</a>.<br>
Protocols: ssh.<br>
Updated hourly.<br>
SSH fingerprints:<br>
(RSA1) 2048 5b:d9:89:99:3d:60:da:bf:e4:28:00:5a:1c:65:91:9f<br>
(RSA) 2048 19:4c:e2:a8:9e:42:b2:91:f3:d5:04:cf:b5:61:5e:ea<br>
(DSA) 1024 80:ff:d2:46:70:51:7d:09:a5:71:83:bb:89:98:44:b1<br>
(ECDSA) 256 fa:57:1c:55:7c:aa:d0:bc:4c:e2:05:3d:9b:bb:83:2d<br>
<p>
<li><strong>CVSROOT=anoncvs@ftp5.eu.openbsd.org:/cvs</strong><br>
Host also known as <strong>anga.funkfeuer.at</strong>.<br>
Location: Vienna, Austria.<br>
Maintained by <a href="mailto:martin@openbsd.org">Martin Reindl</a>.<br>
Protocols: ssh, ssh port 2022.<br>
Updated every 2 hours from anoncvs1.usa.openbsd.org.<br>
SSH fingerprints:<br>
(RSA) 2048 e4:a7:3a:ab:e1:a7:c8:eb:5c:f4:ff:38:95:6f:81:f2<br>
(DSA) 2048 66:03:a3:bc:46:85:f3:6c:4b:6b:e3:d4:f5:5f:a6:c4<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs1.ca.openbsd.org:/cvs</strong><br>
Host also known as <strong>anoncvs.ca.openbsd.org, openbsd.sunsite.ualberta.ca</strong>.<br>
Location: Alberta, Canada.<br>
Maintained by <a href="mailto:beck@ualberta.ca">Bob Beck</a>.<br>
Protocols: ssh, ssh port 2022.<br>
Updated every 2 hours.<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs.comstyle.com:/cvs</strong><br>
Location: Toronto, Canada.<br>
Maintained by <a href="mailto:brad@comstyle.com">Brad Smith</a>.<br>
Protocols: ssh, ssh port 2022.<br>
Updated hourly.<br>
SSH fingerprints:<br>
(RSA1) 2048 80:33:40:b7:94:9e:7b:bd:77:fb:2a:57:85:fc:09:73<br>
(RSA) 2048 43:30:9a:c6:c4:19:80:ad:7d:58:3e:7a:a0:39:57:53<br>
(DSA) 1024 66:a1:f9:47:26:d9:15:3c:62:2b:b5:e8:0d:89:4a:6f<br>
(ECDSA) 256 62:28:13:ea:cd:ba:68:e6:e9:82:94:ac:10:7f:80:d5<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs.estpak.ee:/OpenBSD</strong><br>
Location: Elion, Tallinn, Estonia.<br>
Maintained by <a href="mailto:rix@estpak.ee">Rivo Nurges</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours from cvsync.de.openbsd.org.<br>
SSH fingerprints:<br>
(RSA) 1024 e1:12:fb:6b:e5:c0:6a:b3:f8:ca:b1:4c:20:fb:5e:07<br>
(DSA) 1024 bb:5c:44:f4:d9:12:3b:22:08:a9:12:c5:0c:e7:db:49<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs.fr.openbsd.org:/cvs</strong><br>
Location: Paris, France.<br>
Maintained by <a href="mailto:landry@openbsd.org">Landry Breuil</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours from anoncvs1.ca.openbsd.org.<br>
SSH fingerprints:<br>
(RSA1) 2048 28:ce:6b:61:76:d9:0e:6d:65:a1:5c:dd:e8:d7:57:42<br>
(RSA) 2048 89:2e:84:9e:0c:f9:8d:21:41:0e:c5:80:41:27:14:c1<br>
(DSA) 1024 7f:fb:68:2f:0f:c8:63:6c:0f:32:2c:03:d4:cd:0c:47<br>
(ECDSA) 256 6f:a8:a5:93:d7:68:55:91:15:42:b0:5d:38:62:b9:c3<br>
<p>
<li><strong>CVSROOT=anoncvs@mirror.osn.de:/cvs</strong><br>
Location: Nürnberg, Germany.<br>
Maintained by <a href="mailto:aw@osn.de">Armin Wolfermann</a>.<br>
Protocols: ssh.<br>
Updated every 3 hours.<br>
SSH fingerprints:<br>
(RSA) 1024 f2:73:d2:f6:e3:01:ef:ca:3b:e7:6c:80:b6:bd:bb:84<br>
(DSA) 1024 fb:33:05:62:96:20:cf:88:7e:10:cb:8d:91:72:57:32<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs.jp.openbsd.org:/cvs</strong><br>
Host also known as <strong>kankoromochi.econ.nagasaki-u.ac.jp</strong>.<br>
Location: Nagasaki University, Faculty of Economics, Nagasaki, Japan.<br>
Maintained by <a href="mailto:sigh@net.nagasaki-u.ac.jp">Suzuki Itoshi</a>.<br>
Protocols: ssh, pserver.<br>
Updated every 3 hours.<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs.obsd.si:/cvs</strong><br>
Location: Ljubljana, Slovenia.<br>
Maintained by <a href="mailto:mitja@kerberos.si">Mitja Muzenic</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours from anoncvs.spacehopper.org.<br>
SSH fingerprints:<br>
(RSA) 2048 5b:98:6c:06:a4:1f:83:da:03:aa:ef:e4:f5:f0:99:76<br>
(DSA) 1024 2d:57:e2:9c:fd:9d:09:1c:5e:ff:3f:5d:59:78:93:cc<br>
(ECDSA) 256 3f:50:bd:1e:e5:8a:3d:a4:16:22:1c:2d:cf:8b:22:ed<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs.eu.openbsd.org:/cvs</strong><br>
Location: Stockholm University, Stockholm, Sweden.<br>
Maintained by <a href="mailto:jj@openbsd.org, ftp@it.su.se">Janne Johansson</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours.<br>
SSH fingerprints:<br>
(RSA1) 2048 4c:d2:0a:90:b8:95:5d:37:3b:32:7b:77:5a:c5:ef:26<br>
(RSA) 2048 98:e6:80:5d:95:bb:e2:15:5e:19:4d:a3:e4:d0:bc:2c<br>
(DSA) 1024 55:cd:a7:a9:e3:bc:a5:5c:81:5e:98:c0:60:a2:67:52<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs.spacehopper.org:/cvs</strong><br>
Location: London, United Kingdom.<br>
Maintained by <a href="mailto:sthen@openbsd.org">Stuart Henderson</a>.<br>
Protocols: ssh, ssh port 2022, ssh port 443.<br>
Updated hourly from anoncvs.ca.openbsd.org.<br>
SSH fingerprints:<br>
(RSA1) 2048 31:fc:3d:e0:f7:6c:47:7e:48:f0:52:17:e6:19:74:f5<br>
(RSA) 2048 e2:19:16:3f:a3:2e:eb:94:14:cd:5c:92:9a:6c:9a:8f<br>
(DSA) 1024 ff:47:13:22:83:d1:6e:df:a0:f0:4f:18:31:cb:f2:28<br>
(ECDSA) 256 a5:b0:2a:65:ff:9a:0b:ef:7d:6f:d2:95:2e:a7:c9:2c<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs1.usa.openbsd.org:/cvs</strong><br>
Host also known as <strong>anoncvs.usa.openbsd.org, anoncvs4.usa.openbsd.org</strong>.<br>
Location: Internet Systems Consortium, Redwood City, CA, USA.<br>
Maintained by <a href="mailto:millert@openbsd.org">Todd C. Miller</a>.<br>
Protocols: rsh, ssh, ssh port 2022, pserver.<br>
Updated every 2 hours.<br>
SSH fingerprints:<br>
(RSA1) 1024 64:de:26:16:c2:ff:1b:c7:24:ed:a4:4a:d7:2f:69:3e<br>
(RSA) 1024 49:67:9a:46:62:8a:3f:4e:b3:63:ca:d6:41:29:2a:2f<br>
(DSA) 1024 a7:75:49:77:f3:47:d1:3c:5e:65:84:84:3b:03:f1:33<br>
(ECDSA) 256 d3:b2:b5:68:87:3b:f6:93:21:fd:28:ea:cc:b6:e1:13<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs3.usa.openbsd.org:/cvs</strong><br>
Location: National Center for Atmospheric Research, Boulder, CO, USA.<br>
Maintained by <a href="mailto:millert@openbsd.org">Todd C. Miller</a>.<br>
Protocols: rsh, ssh, ssh port 2022, pserver.<br>
Updated every 2 hours.<br>
SSH fingerprints:<br>
(RSA1) 2048 80:cd:f6:fc:4f:0e:cb:80:6a:d0:6a:5e:dd:9e:5d:0a<br>
(RSA) 2048 49:6f:4a:be:02:63:0d:c0:54:b0:57:f0:48:7f:ce:16<br>
(DSA) 1024 f9:ab:fc:60:a3:15:8f:9c:47:24:9e:92:15:78:0d:f3<br>
(ECDSA) 256 99:4f:c8:23:6a:bf:75:1c:de:c9:11:bf:a4:fe:0a:51<br>
<p>
<li><strong>CVSROOT=anoncvs@mirror.planetunix.net:/cvs</strong><br>
Location: Chicago, IL, USA.<br>
Maintained by <a href="mailto:brian@planetunix.net">Brian Brombacher</a>.<br>
Protocols: ssh, ssh port 2022, pserver.<br>
Updated every 3 hours from anoncvs3.usa.openbsd.org.<br>
SSH fingerprints:<br>
(RSA1) 2048 e4:22:93:81:84:e0:68:8c:0b:d5:1f:78:cd:6f:fa:c3<br>
(RSA) 2048 8f:42:bd:b0:a2:94:df:6b:af:1e:96:03:ea:68:03:d9<br>
(DSA) 1024 26:51:e8:b3:38:88:dc:a8:2a:98:59:86:ab:40:bb:a4<br>
<p>
<li><strong>CVSROOT=anoncvs@anoncvs.obsd.esc7.net:/cvs</strong><br>
Location: Dallas, TX, USA.<br>
Maintained by <a href="mailto:jshupe@osre.org">James Shupe</a>.<br>
Protocols: ssh.<br>
Updated every 2 hours from anoncvs1.usa.openbsd.org.<br>
SSH fingerprints:<br>
(RSA1) 256 68:f1:e8:11:94:5c:5e:15:d0:ee:54:1f:ee:57:33:4a<br>
(RSA) 2048 2a:c8:01:6f:5c:fe:78:75:84:29:c3:11:0f:65:05:07<br>
(DSA) 1024 0e:ce:de:c4:7d:a0:d1:71:0a:af:cf:ee:34:43:bc:23<br>
<p>
</ul>
<p>
<em>Note:</em> If your server is listed on here with inaccurate or
unknown information, please contact
<a href="mailto:beck@openbsd.org"><tt>beck@openbsd.org</tt></a>
<p>
You may want to use
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=traceroute&sektion=8&format=html">traceroute(8)</a>
to find out which server is nearest you.
Problems with a server should be reported to the <b>maintainer</b> of the
server in question.
<p>
If local policy prevents outgoing connections to ssh's default port of 22,
some servers permit connections on an alternative port (typically 2022).
These are noted in the list above.
To use a different port, reconfigure your ssh client by adding a "Host"
entry to <strong>$HOME/.ssh/config</strong>, e.g.:
<pre>
Host anoncvs.ca.openbsd.org
Port 2022
</pre>
<h3><a name="MIRROR"><font color="#0000e0">Setting up an anoncvs mirror
</font></a></h3>
<p>
If you wish to setup a new anoncvs mirror site and make it available to
the general public, please contact the anoncvs
<a href="mailto:sup@openbsd.org">maintainer</a>.
Anoncvs mirrors currently require about 5GB of disk (and it will grow!),
and use up to 32MB of swap
per anoncvs user (assuming the user does a large operation; while smaller
operations use fewer resources, anoncvs still makes much more of an
impact than ftp). Such anoncvs machines should have excellent
network connectivity for the area they are expected to serve. A
<a href="anoncvs.shar">document</a>
which describes the setup of anoncvs servers is available.
<h3><a name="NOTES"><font color="#0000e0">Final notes</font></h3>
After upgrading your source tree, you should read the comments
at the top of <kbd>/usr/src/Makefile</kbd> before attempting
a build. Also, you should build a new kernel <strong>before</strong>
doing a <kbd>make build</kbd> if possible. In some cases it may be
necessary to rebuild and install the <kbd>config</kbd> utility before
you can build the kernel. If <kbd>config GENERIC</kbd> fails this
is probably the case.
<p>
It is important to note that upgrading from a release to the current tree
by rebuilding the sources can be rather difficult due to dependencies
that are often not obvious. Therefore, it is suggested that you first
install the latest snapshot before attempting a tree build from source.
<hr>
<a href="index.html"><img height="24" width="24" src="back.gif" border="0"
alt="OpenBSD"></a>
<a href="mailto:www@openbsd.org">www@openbsd.org</a>
<br><small>$OpenBSD: anoncvs.html,v 1.379 2013/04/27 13:26:40 sthen Exp $
</small>
</body>
</html>
![[BACK]](/icons/back.gif){kind=icon}
Return to anoncvs.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www