Annotation of www/anoncvs.html, Revision 1.7
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
1.2 deraadt 4: <title>OpenBSD AnonCVS</title>
1.1 deraadt 5: <link rev=made href=mailto:www@openbsd.org>
6: <meta name="resource-type" content="document">
7: <meta name="description" content="the main OpenBSD page">
8: <meta name="keywords" content="openbsd,main">
9: <meta name="distribution" content="global">
10: <meta name="copyright" content="This document copyright 1996 by OpenBSD, Inc.">
11: </head>
12:
13: <body>
14:
15: <h1>OpenBSD</h1>
1.6 jkatz 16: <hr>
1.1 deraadt 17: <h3>CVS Access:</h3>
18: CVS is used to manage the OpenBSD source tree. This allows
19: developers to work on a local source tree and commit their changes when
20: ready. Also <strong>anyone</strong> can edit source files on their
21: local machines, and automatically track and merge in any changes made
22: in the OpenBSD CVS repository. Additionally they can easily see the
23: logs of, check out, or "diff" the source files in the OpenBSD source
24: tree.
25: </p>
26:
27: <p>
28: Most importantly, the <strong>anoncvs</strong> service does NOT
29: delete the changes you make in your local copy of the source tree --
30: read on for more details!
31: </p>
32:
33: <p>
34: The latest version of CVS is available at
35: <a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>.
36: Versions earlier than 1.6 are not recommended, and may not work.
37: If you already have OpenBSD installed, CVS is included.
38: </p>
39:
40: <p>
41: There are two levels of source tree access:
42: </p>
43:
44: <dl>
45: <dt><strong>Read-write access for developers:</strong>
46: <dd>Developers who need to commit changes to the source tree must have
47: an account on the OpenBSD machines. Getting this access will be a
48: natural result of working on the sources with other OpenBSD developers.
49: If someone does some good work and shows they can work with the team,
50: they will get an account.
51: </dl>
52:
53: <dl>
54: <dt><strong>Read-only access for everyone:</strong>
55: <dd>Anyone can access the read-only CVS repositories. These copies
56: of the read-write CVS repository are mirrored often. To use one,
57: set your <strong>CVSROOT</strong> environment variable to one of
58: the following values:
59: <ul>
60: <p>
61: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
62: Host also known as <strong>anoncvs.openbsd.org</strong> and
63: <strong>eap.ccrc.wustl.edu</strong>.<br>
64: located at Washington University, St. Louis, mid-west USA.<br>
65: maintained by <a href=mailto:chuck@maria.wustl.edu>Chuck Cranor</a>.<br>
66: protocols: rsh, ssh, ssh port 2022.<br>
67: updated every 4 hours.<br>
68: <p>
69: <li><strong>CVSROOT=anoncvs@anoncvs2.usa.openbsd.org:/cvs</strong><br>
1.5 johns 70: Host also known as <strong>hydra.heuris.com</strong>.<br>
1.4 deraadt 71: located in St. Louis, Missouri, mid-western USA.<br>
1.1 deraadt 72: maintained by <a href=mailto:johns@heuris.com>John Stone</a>.<br>
73: protocols: rsh, ssh, ssh port 2022.<br>
74: updated every 12 hours.<br>
75: <p>
76: <li><strong>CVSROOT=anoncvs@anoncvs3.usa.openbsd.org:/cvs</strong><br>
77: Host also known as <strong>freestuff.cs.colorado.edu</strong>.<br>
78: located at the University of Colorado, Boulder, western USA.<br>
79: maintained by <a href=mailto:Todd.Miller@cs.colorado.edu>Todd Miller</a>.<br>
80: protocols: ssh, ssh port 2022.<br>
81: updated every 6 hours.<br>
82: <p>
1.7 ! deraadt 83: <li><strong>CVSROOT=anoncvs@anoncvs4.usa.openbsd.org:/cvs</strong><br>
! 84: located in California.<br>
! 85: maintained by <a href=mailto:niklas@openbsd.org>Niklas Hallqvist</a>.<br>
! 86: protocols: rsh, ssh, ssh port 2022.<br>
! 87: updated every 4 hours.<br>
! 88: <p>
1.1 deraadt 89: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
90: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
91: located in London, UK.<br>
92: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
93: protocols: rsh.<br>
94: updated every 12 hours.<br>
95: <p>
96: <li><strong>CVSROOT=anoncvs@anoncvs.tw.openbsd.org:/cvs</strong><br>
97: Host also known as <strong>hercules.secc.fju.edu.tw</strong>.<br>
98: located in Taipei, Taiwan.<br>
99: maintained by <a href=mailto:shawn@openbsd.org>Shawn Hsiao</a>.<br>
100: protocols: rsh, ssh, ssh port 2022.<br>
101: updated every 12 hours.<br>
102: <p>
103: <li><strong>CVSROOT=anoncvs@anoncvs.no.openbsd.org:/cvs</strong><br>
104: located in Norway.<br>
105: maintained by <a href=mailto:micheals@openbsd.org>Michael Shuldman</a>.<br>
106: protocols: rsh, ssh, ssh port 2022.<br>
107: updated every 4 hours.<br>
108: </ul>
109: <p>
110: You may want to use `traceroute' to find out which server is nearest you.
111: </dl>
112: </p>
113:
114: <p>
115: <strong>IMPORTANT NOTE:</strong>
116: There are a few issues relating to cryptographic software that everyone
117: should be aware of:
118: <ul>
119: <li>The OpenBSD sources are from Canada.
120: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>It
121: is legal to export crypto software from Canada to the world.</a>
122: <p>
123: <li>However, if you are outside the USA or Canada, you should not
124: fetch the cryptographic sections of the OpenBSD sources from an
125: anoncvs server located in the USA. The files in question are...
126: <ul>
127: <li>src/kerberosIV/*
128: <li>src/lib/libc/crypt/crypt.c
129: <li>src/lib/libc/crypt/morecrypt.c
130: </ul>
131: Because of the USA ITAR munitions list,
132: crypto software may only be exported to Canada from the USA.
133: <p>
134: <li>The OpenBSD project is looking for more anoncvs servers -- read
135: on to find out how you can help.
136: </ul>
137: </p>
138:
139: <p>
140: A sample use of an anoncvs CVS server would be:
141: <pre>
142: % setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
143: % cd /tmp
144: % cvs get src/sys/arch/sparc
145: [copies the files from the repository to your machine]
146: % cvs log src/sys/arch/sparc/sparc/locore.s
147: [shows the commit log for the chosen file ]
148: % cvs diff -bc -r1.1 -r1.5 src/sys/arch/sparc/sparc/locore.s
149: [shows the changes between revisions 1.1 and rev 1.5]
150: </pre>
151: </p>
152:
153: <p>
154: Here is how someone using anoncvs regularily would update his
155: source tree:
156: <pre>
157: # setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
158: # cd /usr
159: # cvs -q get -PA src
160: </pre>
161: or similarily later on he might try
162: <pre>
163: # cd /usr/src
164: # cvs -q up -PAd
165: </pre>
166: Everytime you ran this it would syncronize your /usr/src tree. It would
167: not destroy any of your local changes, rather it would attempt to merge
168: changes in. If you use obj directories (not obj symbolic links) you may
169: wish to append "-I obj" to the cvs command line, this will keep cvs from
170: spitting out a warning about all the obj directories it is going to
171: encounter which are not in the repository.
172: </p>
173:
174: <p>
175: The CVS man page (included with the CVS sources) has much more
176: information about how CVS can be used.
177: </p>
178:
179: <p>
180: The anoncvs service gives fledgling developers a chance to learn CVS
181: operation and get thoroughly involved in the development process
182: before getting "commit" access -- as a result of showing useful
183: skills and high quality results they will naturally later be given
184: developer access. As well, people providing patches can create
185: their "diff"s relative to the CVS tree, which will ease integration.
186: </p>
187:
188: <p>
189: The CVS client uses rsh to talk to the CVS server. If some local
190: security measure like a firewall (or imperfect protocol emulators
191: like slirp) prevents you from using rsh, you may be able to use
192: <a href=http://www.cs.hut.fi/ssh>ssh</a> instead. In this case,
193: one sets the environment variable <strong>CVS_RSH</strong> to point
194: to ssh (typically <strong>/usr/local/bin/ssh</strong>). To reduce the
195: performance hit the anoncvs server would take it is recommended (and
196: requested) that you disable encryption. If your local site prevents
197: you from connecting out to port 22 (which ssh defaults to using) use
198: port 2022.
199: </p>
200:
201: <p>
202: Do not be tempted to turn on compression since CVS already compresses.
203: Use something like the following in your <strong>$HOME/.ssh/config</strong>
204: file.
205: </p>
206: <pre>
207: Host anoncvs.usa.openbsd.org
208: Cipher none
209: Port 2022
210: </pre>
211:
212: <p>
213: CVS is a little noisy starting up; to quiet it a bit you may want to
214: do this:
215: <pre>
216: setenv CVS_CLIENT_PORT -1
217: </pre>
218: </p>
219:
220: <p>
221: If you wish to be a new anoncvs mirror site, please contact the anoncvs
222: <a href=mailto:deraadt@theos.com>maintainer</a>.
223: Anoncvs mirrors require about 300MB of disk, and use up to 4MB of swap
224: per anoncvs user (assuming the user does a large operation; while smaller
225: operations use fewer resources, anoncvs still makes much more of an
226: impact than ftp or sup). Such anoncvs machines should have excellent
227: network connectivity for the area they are expected to serve. A
228: <a href=anoncvs.shar>document</a>
229: which describes the setup of anoncvs servers is available.
230: </p>
231:
232: </dl>
233:
234: <hr>
1.3 deraadt 235: <a href=index.html><img src=back.gif border=0 alt=OpenBSD></a>
1.1 deraadt 236: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.7 ! deraadt 237: <br><small>$OpenBSD: anoncvs.html,v 1.6 1996/12/16 19:28:43 jkatz Exp $</small>
1.1 deraadt 238:
239: </body>
240: </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