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 errata patches
of a release.
Anonymous CVS works directly against a central source code repository.
This means that you have the full set of CVS commands available to control
merging and updating your changes with other source changes, performing diffs,
change histories and other queries against the central repository.
In the event that the changes can't be completely merged, CVS provides annotated
changes to your local copy and preserves an unmodified copy of your version.
The OpenBSD Project currently has four active source repositories:
- src - source code for the base system
- ports - the ports tree
- www - web pages
- xenocara - xenocara
What is CVS?
CVS is the
source code control system used to manage the OpenBSD source tree.
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:
- Read-write access for developers
- Read-only access for everyone
Pre-Loading the Source Tree
While you can download the entire source tree from an AnonCVS server, you can
save time and bandwidth by pre-loading your tree with the source tarballs.
This is particularly true if you are running
-stable, as relatively few files change
between the release and -stable.
The source files for download from the mirrors are
separated into two files to reduce the download time for those wishing to
work with only one part of the tree.
The kernel sources are in sys.tar.gz
and the userland sources
are in src.tar.gz
.
The following commands assume you have followed
these instructions to give a non-root
user write access to the src, ports and xenocara directories.
$ cd /usr/src
$ tar xzf /tmp/src.tar.gz
$ tar xzf /tmp/sys.tar.gz
$ cd /usr
$ tar xzf /tmp/ports.tar.gz
$ cd /usr/xenocara
$ tar xzf /tmp/xenocara.tar.gz
Using CVS to Get and Update Your Source Trees
cvs(1) was designed to be a simple way
to retrieve and update your sources.
You must first decide whether you want to track -current or a
-stable branch.
The current tree has all of the up to the minute changes, whereas the
-stable branch contains the sources for the release plus the patches from
the errata and lesser issues already applied.
For more information on the flavors of OpenBSD, see
here.
Choose the Anonymous CVS server you are going to use from the
list of servers below, then you can start using cvs.
If you begin with src.tar.gz
and sys.tar.gz
as mentioned
above, you can skip the initial checkout and proceed to updating.
Warning:
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 cvs checkout, can create an arbitrary sub-tree
in the current directory, and a subsequent update will recursively flesh out
this sub-tree.
Getting an Initial Tree
The following commands assume that your user is member of the wsrc
group; replace anoncvs.example.org
with a mirror from the
list below.
If you are following -current:
$ cd /usr
$ cvs -qd anoncvs@anoncvs.example.org:/cvs checkout -P src
If you are following the 7.7 -stable branch:
$ cd /usr
$ cvs -qd anoncvs@anoncvs.example.org:/cvs checkout -rOPENBSD_7_7 -P src
Anonymous CVS uses passwordless SSH as a transport.
If this is the first time you have connected to a server,
you will be asked to confirm the SSH fingerprint to ensure that you
are connecting to the expected server:
$ cvs -d anoncvs@anoncvs.spacehopper.org:/cvs checkout -P src
The authenticity of host 'anoncvs.spacehopper.org (2001:67c:15f4:a423::28)' can't be established.
ED25519 key fingerprint is SHA256:oaJ7VEyjt2EHMeixzKn9zJGiV5YlWHIUls070tKdBzI.
Are you sure you want to continue connecting (yes/no)?
In most cases, the list below includes the fingerprints for the server,
so you can compare it against the displayed fingerprint as additional
verification that you are connecting to the correct server.
Confirm this, and the fingerprint will then be saved as usual.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'anoncvs.spacehopper.org' (ED25519) to the list of known hosts.
Updating an Existing Tree
If you are following -current:
$ cd /usr/src
$ cvs -q up -Pd -A
If you are following the 7.7 -stable branch:
$ cd /usr/src
$ cvs -q up -Pd -rOPENBSD_7_7
Every time you run this, cvs(1) synchronizes your /usr/src
tree.
It does not destroy any of your local changes; rather it attempts to merge
changes in.
Changing the Server
If you are updating a source tree that you initially fetched
from a different server, or from a tar file, you must
add the -d [cvsroot] option to cvs.
$ cd /usr/src
$ cvs -d anoncvs@anoncvs.example.org:/cvs -q up -Pd
Getting the ports and xenocara Trees
Make sure your user is member of the wsrc
group and that
/usr/ports
is group writable by wsrc
.
Replace ports with xenocara throughout to get or update a
xenocara tree.
-
If you are following -current:
$ cd /usr
$ cvs -qd anoncvs@anoncvs.example.org:/cvs checkout -P ports
If you are following the 7.7 -stable branch:
$ cd /usr
$ cvs -qd anoncvs@anoncvs.example.org:/cvs checkout -rOPENBSD_7_7 -P ports
- Any time afterwards, to update this tree:
If you are following -current:
$ cd /usr/ports
$ cvs -q up -Pd -A
If you are following the 7.7 -stable branch:
$ cd /usr/ports
$ cvs -q up -Pd -rOPENBSD_7_7
Creating a Diff
To make a diff of a locally patched module (here cd.c
) to include with
a bug report:
$ cd /usr/src
$ cvs diff -u sys/scsi/cd.c > /tmp/patch
Example Usage
$ cd /tmp
$ cvs -d anoncvs@anoncvs.example.org:/cvs checkout -P src/sys/arch/sparc
[copies the files from the repository to your machine]
$ cd src/sys/arch/sparc
$ cvs log locore.s
[shows the commit log for the chosen file]
$ cvs diff -bc -r1.1 -r1.5 locore.s
[shows the changes between revisions 1.1 and rev 1.5]
Mirroring the Repository
As noted in the list below, some repository mirrors also allow fetching
the entire repository via rsync.
Please use the reposync
wrapper script which checks for updates to
CVSROOT/ChangeLog and avoids a full directory scan in some cases where no update
was detected.
It also handles SSH port forwarding for mirrors where this is available,
allowing to connect to an "rsync --daemon" server over an
authenticated and encrypted channel.
Install reposync
from packages, create a user and directory to
hold the repository, and a directory for reposync's own use:
# pkg_add reposync
# useradd cvs
# install -d -o cvs /home/cvs /var/db/reposync
Now the following command might be used to mirror or update the repository.
If your chosen mirror does not support SSH port-forwarding, either switch to
a better mirror, or change to "reposync -p".
# su -m cvs -c "reposync rsync://mirror.example.org/cvs /home/cvs"
After mirroring, you can use the local directory as your cvsroot, for example:
$ cd /usr/src
$ cvs -d /home/cvs -q up -Pd
As of March 2024, repository sizes are as follows:
$ du -shc *
224M CVSROOT
1.6G ports
3.9G src
936M www
2.3G xenocara
9.0G total
The overall repository size currently increases at a rate
of about 530MB per annum. The src repository increases by about
220MB.
Available Anonymous CVS Servers
- CVSROOT=anoncvs@anoncvs.au.openbsd.org:/cvs
reposync rsync://anoncvs.au.openbsd.org/cvs/
Location: Brisbane, Australia.
Maintained by David Gwynne.
Protocols: ssh.
Updated hourly.
SSH fingerprints:
(RSA) SHA256:pPcBY4E33vwreETbz5KJUIzZpWWzaZPhrpnLaFa7WuQ
(ECDSA) SHA256:kg2Zaqpd8ZuluPzlpFS9rEw0KR1UmxD9jSG6+2tr28A
(ED25519) SHA256:4CbDtzH/6mqQ/f6KDLz0rdqK2Thk4dQQtHXOxTONEvk
- CVSROOT=anoncvs@anoncvs.comstyle.com:/cvs
reposync rsync://anoncvs.comstyle.com/cvs/
Location: Toronto, Canada.
Maintained by Brad Smith.
Protocols: ssh, ssh port 2022.
Updated hourly.
SSH fingerprints:
(RSA) SHA256:vYSNKOoCHReBzmdJy3SiULg7YyEZVoib3X3jGJShezA
(ECDSA) SHA256:W2WEQDka4xicJzeQY0Nm0iCv3h2xZLzfp+TT1UvtBTw
(ED25519) SHA256:cqNaOU0KSmJ/S7jrV4UbZ6WkkyXWZ07rhWK8yrRZUV0
- CVSROOT=anoncvs@obsdacvs.cs.toronto.edu:/cvs
reposync rsync://obsdacvs.cs.toronto.edu/obsdcvs/
Location: University of Toronto, Toronto, ON, Canada.
Maintained by Nick Holland.
Protocols: ssh.
Updated every 2 hours from main server.
SSH fingerprints:
(RSA) SHA256:BosSX+gUL/17cUdppQlmXht1S5GGHrHNrL6+U3hyG+o
(ECDSA) SHA256:4I5R4/tGayGG0KDEsj6CY1eCqt2sbcYtA3nqnhUaD04
(ED25519) SHA256:AqblfWV4KT2ptlpV3mq3gb4jNPzgYtjDvlBBcaeohxQ
- CVSROOT=anoncvs@anoncvs.fr.openbsd.org:/cvs
reposync rsync://anoncvs.fr.openbsd.org/openbsd-cvs/
Location: Paris, France.
Maintained by Landry Breuil, Antoine Jacoutot.
Protocols: ssh.
Updated every 2 hours from main server.
SSH fingerprints:
(RSA) SHA256:d3o82eY/kIfUfmhVpwFu7Do1I7+Wol/tvWmm6Ye9HZ4
(ECDSA) SHA256:WXN4m8NHd4vcTqxmzLMMVenSh6gp8060nv39JIiCSss
(ED25519) SHA256:STeC5WGChnZjIi5Rb+XTAQSbKXQJ+B9wxhaacYNff7k
- CVSROOT=anoncvs@mirror.osn.de:/cvs
reposync -p rsync://mirror.osn.de/openbsd-all/
Location: Nürnberg, Germany.
Maintained by Armin Wolfermann.
Protocols: ssh.
Updated every 3 hours.
SSH fingerprints:
(RSA) SHA256:fQGY+UhLdbB3oDI4frFtSKF2BjQIkSY0lnSA6lVv8+o
(ECDSA) SHA256:plj+1CPTaKi0AIId/aDMCGgZZnkxc1ow+ffBNMvYW4A
(ED25519) SHA256:np+DK8xlo9A4YnYXO/22GBV8iyuL13r3g5I0/N1Mf8g
- CVSROOT=anoncvs@ftp.hostserver.de:/cvs
reposync rsync://ftp.hostserver.de/cvs/
Location: Frankfurt, Germany.
Maintained by Sebastian Benoit, Florian Obser.
Protocols: ssh.
Updated hourly from main server.
SSH fingerprints:
(RSA) SHA256:XrjDaKqJ6J02iSQ/eoiqII0LxJX9D/41eeC6pSQAJXs
(ECDSA) SHA256:v6G11hMFfS2+zPh44hhZcpUqDEppyvGQe0vzmrtIHA8
(ED25519) SHA256:KeG1InAfAnQKqpCewmXw/Egb+4UZZuIMGdlYVG+uxNg
- CVSROOT=anoncvs@anoncvs.jp.openbsd.org:/cvs
reposync rsync://anoncvs.jp.openbsd.org/cvs/
Host also known as kankoromochi.econ.nagasaki-u.ac.jp.
Location: Nagasaki University, Faculty of Economics, Nagasaki, Japan.
Maintained by SUZUKI Hitoshi.
Protocols: ssh.
Updated every 2 hours.
SSH fingerprints:
(RSA) SHA256:3XcKWDBEcB5XE4shCmRfh0LmSOyDcp4vcSQp8NK62Gk
(ECDSA) SHA256:aXpmw11DuXXLm8PsJ37L65jEXbu8JF2cnVfQptSkoyQ
(ED25519) SHA256:vLLJFhJCzzmXd7FwgQ+vJpnAQiDibSS2aZOgeuVZmjQ
- CVSROOT=anoncvs@mirror.litnet.lt:/cvs
Location: Kaunas, Lithuania.
Maintained by Patrikas Kugrinas.
Protocols: ssh.
Updated every 2 hours from anoncvs.eu.openbsd.org.
SSH fingerprints:
(RSA) SHA256:RmbGnT7IGLvVd9tm5mAx7rz6VntYlwqW6qyT2QuritY
(ECDSA) SHA256:hj1btBB8gqLdm3EumX3T3LaUZkY9fm1RFvw9DVS2oi8
(ED25519) SHA256:EnczVm1Q8+lE+Zmue3jAPh/pA6BJhEDwL+HNMfedpXI
- CVSROOT=anoncvs@anoncvs.eu.openbsd.org:/cvs
reposync -p rsync://anoncvs.eu.openbsd.org/OpenBSD-cvs/
Location: Safespring AB, Stockholm, Sweden.
Maintained by Janne Johansson.
Protocols: ssh.
Updated every 2 hours from main server.
SSH fingerprints:
(RSA) SHA256:QcoosLgIy8UxR6PF82E+0wS+2F0WzSaavJSIUxBL8oE
(ECDSA) SHA256:OUJAC3qFB0Qs8/Oyw5SaUPr0rRlb6wcR2fR9laKBGRs
(ED25519) SHA256:ZW5umXyiwexF5Tcz3SXgDIA/+vgPFGZ6EE44WLi+x3U
- CVSROOT=anoncvs@anoncvs.spacehopper.org:/cvs
reposync rsync://anoncvs.spacehopper.org/cvs/
Location: Plymouth, United Kingdom.
Maintained by Stuart Henderson.
Protocols: ssh, ssh port 2022, ssh port 443.
Updated hourly from main server.
SSH fingerprints:
(RSA) SHA256:orTIOu6IKP7Ndz317tyCaz8LJnJWz4jmzSuG+FK7jwM
(ECDSA) SHA256:p+VCx2KynGtiFFaaiF010SIQu6gJgmJb//yokW2sGBE
(ED25519) SHA256:oaJ7VEyjt2EHMeixzKn9zJGiV5YlWHIUls070tKdBzI
- CVSROOT=anoncvs@anoncvs4.usa.openbsd.org:/cvs
reposync rsync://anoncvs4.usa.openbsd.org/cvs/
Host also known as ftp3.usa.openbsd.org, ftp4.usa.openbsd.org, ftp5.usa.openbsd.org.
Location: New York Internet, New York, NY, USA.
Maintained by Todd C. Miller.
Protocols: ssh, ssh port 2022.
Updated hourly from main server.
SSH fingerprints:
(RSA) SHA256:RT7vVXrvmKgZ7VkrVZ0lgugDFCBPVT6iSwMh+m1vZTA
(ECDSA) SHA256:JreaFNTlm2Uhlk3iaMs4Rweq27KPSVYUgj9sZUsOxCc
(ED25519) SHA256:iLsNcXOnluavlGUV+O4JE7TNppEwIMvsjZ7m1VVObiM
- CVSROOT=anoncvs@anoncvs1.usa.openbsd.org:/cvs
reposync rsync://anoncvs1.usa.openbsd.org/cvs/
Host also known as anoncvs.usa.openbsd.org, anoncvs2.usa.openbsd.org, anoncvs3.usa.openbsd.org.
Location: Network Media, LLC, Bend, OR, USA.
Maintained by Todd C. Miller.
Protocols: ssh, pserver.
Updated hourly from main server.
SSH fingerprints:
(RSA) SHA256:PFKE28DFbJLmqoLkq9xfBuiYl9GN2LABsvUpzNk+LlE
(ECDSA) SHA256:Ofstc7xq/W+73vBMUpb3A4ZqLNhKI3u2FdzbOkJpOHI
(ED25519) SHA256:IYHq/zKqYnd2wy71Br6X8Q1Jk0XGjOJA4PU6CAr6pDo
If your server is listed on here with inaccurate or unknown information, please
contact beck@openbsd.org
.
You may want to use
traceroute(8)
to find out which server is nearest you.
Problems with a server should be reported to the maintainer of the
server in question.
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 $HOME/.ssh/config
, e.g.:
Host anoncvs.example.org
Port 2022
Setting up an AnonCVS Mirror
AnonCVS mirrors currently require about 9GB of disk (and it will grow!), and use
up to 64MB 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 document which describes the setup of AnonCVS
servers is available.
Final Notes
After upgrading your source tree, you should read the comments at the top of
/usr/src/Makefile
before attempting a build.
Also, you should build a new kernel before doing a make build
if possible.
In some cases it may be necessary to rebuild and install the config
utility before you can build the kernel.
If config GENERIC fails this is probably the case.
It is important to note that upgrading from a release to the current tree
by rebuilding the sources is not supported.
Therefore, it is suggested that you first install the latest snapshot before
attempting a tree build from source.
¡®Yes, sir. I felt sure you understood that. She said she had told you.¡¯ "Why, eh,--I--I don't know that my movements need have anything to do with his. Yours, of course,--" "Ah, but if it saved your life!" "No, I'm not," grumbled the Doctor, "I've had enough of this wild-goose chase. And besides, it's nearly dinner time." "I am coming to that," Lawrence said, lighting a fresh cigarette. "As soon as Bruce was in trouble and the plot began to reel off I saw that it was mine. Of course there were large varyings in the details, but the scheme was mine. It was even laid on the same spot as my skeleton story. When I grasped that, I knew quite well that somebody must have stolen my plot." Judy In a coach-house, through which we passed on our way to see the prince's favourite horses with the state carriages¡ªquite commonplace and comfortable, and made at Palitana¡ªwas a chigram,[Pg 68] off which its silk cover was lifted; it was painted bright red and spangled with twinkling copper nails. This carriage, which is hermetically closed when the Ranee goes out in it, was lined with cloth-of-gold patterned with Gohel Sheri's initials within a horseshoe: a little hand-glass on one of the cushions, two boxes of chased silver, the curtains and hangings redolent of otto of roses. "Are you certain of it? You have seen so very little of him, and you may be mistaken." "And your wife?" "I drawed on my man's bundle o' wood," said Gid, "and then dropped a little, so's to git him where he was biggest and make sure o' him." HoME²¨¶àÒ°½áÒÂ×óÏßÊÓÆµ
ENTER NUMBET 0016www.kokty.net.cn
www.ibangkf.com.cn
izjtlx.com.cn
www.kijik141.com.cn
www.niania.com.cn
shyunze.com.cn
technion.com.cn
pkjyzx.com.cn
qfkjsp.com.cn
www.xbchain.com.cn