Annotation of www/anoncvs.html, Revision 1.283
1.246 steven 1: <!-- DO NOT EDIT MANUALLY! This is generated from www/build/mirrors.pl -->
2:
1.180 jufi 3: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.1 deraadt 4: <html>
5: <head>
1.93 deraadt 6: <title>OpenBSD AnonCVS</title>
1.135 naddy 7: <link rev="made" href="mailto:www@openbsd.org">
1.93 deraadt 8: <meta name="resource-type" content="document">
1.249 nick 9: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
1.93 deraadt 10: <meta name="description" content="How to get OpenBSD updates via Internet using Anonymous CVS">
11: <meta name="keywords" content="openbsd,anoncvs,updates">
12: <meta name="distribution" content="global">
1.261 nick 13: <meta name="copyright" content="This document copyright 1996-2007 by OpenBSD.">
1.1 deraadt 14: </head>
15:
1.226 nick 16: <body bgcolor="#ffffff" text="#000000">
1.1 deraadt 17:
1.249 nick 18: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
1.93 deraadt 19: <p>
1.135 naddy 20: <h2><font color="#e00000">Anonymous CVS</font></h2>
1.14 downsj 21:
1.135 naddy 22: <hr>
23:
1.249 nick 24: <h3>Table Of Contents</h3>
1.135 naddy 25:
26: <ul>
1.249 nick 27: <li><a href="#anoncvs">What is Anonymous CVS?</a>
28: <li><a href="#CVS">What is CVS?</a>
29: <li><a href="#starting">Getting Started Using Anonymous CVS</a>
30: <li><a href="#using">Using CVS to Get and Update your Source Tree</a>
31: <li><a href="#CVSROOT">Available Anonymous CVS Servers</a>
32: <li><a href="#CRYPTO">Getting crypto sources through cvs(1)</a>
33: <li><a href="#EXAMPLE">Example usages for cvs(1)</a>
34: <li><a href="#WHICH">Use rsh(1) or ssh(1)?</a>
35: <li><a href="#SUP">Mirroring the CVS repository via sup(1)</a>
36: <li><a href="#MIRROR">Setting up an anoncvs mirror</a>
1.100 ericj 37: </ul>
1.135 naddy 38:
1.100 ericj 39: <hr>
40:
1.249 nick 41: <h3><a name="anoncvs"><font color="#0000e0">What is Anonymous CVS?</font></a></h3>
1.99 ericj 42:
1.15 grr 43: <p>
1.249 nick 44: Anonymous CVS is a method of keeping your local copy of the OpenBSD source
45: tree up to date with respect to changes made to current OpenBSD sources.
46: In addition to following the bleeding edge of development, it is
47: also possible to track the patches for errata of a release.
1.99 ericj 48:
1.14 downsj 49: <p>
1.249 nick 50: The major advantage of Anonymous CVS over other source code update
51: techniques is that it works directly against a central source code
52: repository or mirror. This means that you have the full set of CVS
53: commands available to control merging and updating your changes with
54: other source changes and for performing diffs, change histories
55: and other queries against the central repository.
1.99 ericj 56:
1.36 deraadt 57: <p>
1.282 nick 58: The OpenBSD Project currently has four active and two historic
59: source repositories:
1.99 ericj 60:
61: <ul>
1.249 nick 62: <li><b>src</b> - Houses all source code for the OpenBSD Operating System.
63: <li><b>ports</b> - Houses the <a href="./ports.html">OpenBSD Ports</a>.
64: <li><b>www</b> - Houses all OpenBSD web pages. (Including this one).
1.280 steven 65: <li><b>xenocara</b> - Houses OpenBSD's active X.org v7 source tree.
1.282 nick 66: <li><b>X11</b> and <b>XF4</b> - Houses OpenBSD's adaptation of the
67: <a href="http://www.XFree86.org/">XFree86-3</a> and XFree86-4
68: source trees.
69: These are here just for historical purposes, most users will have
70: no reason to use this tree, it is no longer being used.
1.99 ericj 71: </ul>
72:
1.100 ericj 73: <p>
1.249 nick 74: To summarize, the real strength of using Anonymous CVS is that it is
75: a "tolerant" source code control system - it <strong>respects</strong>
76: changes that you have made to your local sources and makes <strong>
77: "best efforts"</strong> to update your entire source tree, rather than
78: leaving you a list of arcane problems that have to be resolved before
79: continuing.
80:
81: <h3><a name="CVS"><font color="#0000e0">What is CVS?</font></a></h3>
82:
83: <p>
1.260 nick 84: <a href="http://ximbiot.com/cvs/">CVS</a> is the source code control
1.249 nick 85: system used to <a href="why-cvs.html">manage the OpenBSD source
86: tree.</a>
87: It implements a central repository for all officially released source code
88: and changes, while permitting developers to maintain local copies of the
89: source code with their working changes.
1.226 nick 90:
1.249 nick 91: There are two levels of source tree access:
1.226 nick 92: <ul>
1.249 nick 93: <li><b>Read-write access for developers:</b>
94: Developers who need to commit changes to the source tree must have an
95: account on the OpenBSD machines.
96: Getting this access will be a natural result of working on the sources
97: with other OpenBSD developers.
98: If someone does some good work and shows they can work with the team,
99: they will get an account.
100:
101: <li><b>Read-only access for everyone:</b>
102: Anyone can access the read-only CVS repositories.
103: These copies of the read-write CVS repository are mirrored often.
1.226 nick 104: </ul>
1.99 ericj 105:
1.15 grr 106: <p>
1.249 nick 107: The major strength of CVS is that it has the ability to perform intelligent
108: merges of changes to the central repository with changes that you make to
109: your local copy. This means that if you make a change to a module and
110: perform an update, your changes are not "blown away", rather CVS makes
111: best efforts to merge the changes made to the central sources with changes
112: you've made to your local copy.
113:
114: <p>
115: In the event that the changes can't be completely merged, CVS provides a
116: "soft fallback", providing you with annotated changes to your
117: local copy, preserving an unmodified copy of your version and continuing
118: to update any other source modules you requested.
119:
120: <h3><a name="starting"><font color="#0000e0">Getting Started Using Anonymous
121: CVS</font></a></h3>
122:
123: While you can download the entire source tree from an AnonCVS server,
124: you can often save a lot of time and bandwidth by "preloading" your
125: source tree with the source files from either the OpenBSD CD or from an
126: FTP server.
127: This is particularly true if you are running
128: <a href="stable.html"><i>-stable</i></a>, as relatively few files change
129: between the <i>-release</i> and <i>-stable</i>.
1.100 ericj 130:
1.22 niklas 131: <p>
1.249 nick 132: To extract the source tree from the CD to <i>/usr/src</i> (assuming the CD is
133: mounted on /mnt):
1.22 niklas 134: <pre>
1.280 steven 135: # <b>cd /usr/src</b>
136: # <b>tar xzf /mnt/src.tar.gz</b>
1.282 nick 137: # <b>cd /usr</b>
1.280 steven 138: # <b>tar xzf /mnt/xenocara.tar.gz</b>
1.226 nick 139: # <b>tar xzf /mnt/ports.tar.gz</b>
1.22 niklas 140: </pre>
1.224 nick 141:
1.249 nick 142: The source files for download from the FTP servers are separated into two
143: files to minimize the time required to download for those wishing to work
144: with only one part of the tree. The two files are <tt>sys.tar.gz</tt>,
145: which contains the files used to create the kernel, and <tt>src.tar.gz</tt>
146: which contains all the other "userland" utilities.
147: In general, however, you will usually want both of them installed.
1.280 steven 148: Assuming the downloaded files, <tt>src.tar.gz</tt>,
149: <tt>sys.tar.gz</tt> and <tt>xenocara.tar.gz</tt> are in <tt>/usr</tt>:
1.224 nick 150:
1.22 niklas 151: <pre>
1.224 nick 152: # <b>cd /usr/src</b>
153: # <b>tar xzf ../sys.tar.gz</b>
1.225 nick 154: # <b>tar xzf ../src.tar.gz</b>
1.282 nick 155: # <b>cd /usr</b>
1.280 steven 156: # <b>tar xzf ../xenocara.tar.gz</b>
1.226 nick 157: # <b>tar xzf ports.tar.gz</b>
1.22 niklas 158: </pre>
1.100 ericj 159:
160: <p>
1.249 nick 161: Not all people will wish to unpack all the file sets, but as the system
162: must be kept in sync, you will generally need to set up all trees.
1.226 nick 163:
164: <p>
1.249 nick 165: You can also just use cvs(1) to "<b>checkout</b>" the source repository
166: for you. This is discussed in the <a href="#using">next section</a>.
1.100 ericj 167:
168: <p>
1.249 nick 169: After this, <tt>/usr/src</tt> will be a nice checkout area where all
170: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html">
171: cvs(1)</a> commands will work properly.
1.100 ericj 172:
1.249 nick 173: <h3><a name="using"><font color="#0000e0">Using CVS to get and update your
174: source tree</font></a></h3>
1.100 ericj 175:
176: <p>
1.249 nick 177: CVS was designed to be a simple way to retrieve and update your sources.
178: You must first decide whether you want to track <i>-current</i> or a
179: <a href="stable.html">patch branch</a>.
180: The current tree has all of the up to the minute changes,
181: whereas a patch branch contains a formal release plus the patches
182: from the <a href="errata.html">errata</a> and lesser issues already applied.
183: For more information on these "flavors" of OpenBSD, see
184: <a href="faq/faq5.html#Flavors">here</a>.
185:
186: <p>Once you have decided which tree to follow, you must choose which Anonymous
187: CVS server you are going to use. A list of these servers is
188: <a href="#CVSROOT">below</a>.
189:
190: <p>
191: Once you have chosen which <a href="#CVSROOT">Anonymous CVS Server</a> you will
192: use, you can start using cvs. For those of you
193: who have CDs you can start with the CVS checkout that is on the CD by using
194: the method <a href="#starting">above</a> to get the sources onto your system.
195: If you don't have a CD handy, use the method below to checkout the sources.
196: This method puts the OpenBSD source tree into <i>/usr/src</i>.
1.100 ericj 197:
1.135 naddy 198: <pre>
199: # <b>cd /usr; cvs checkout -P src</b>
200: </pre>
1.99 ericj 201:
1.1 deraadt 202: <p>
1.249 nick 203: The above will checkout the <i>current</i> source tree. Many of you will
204: only want the patch branch sources. To checkout a patch branch, you must
205: specify a tag along with your command. Example:
1.1 deraadt 206:
1.135 naddy 207: <pre>
1.282 nick 208: # <b>cd /usr; cvs checkout -P -rOPENBSD_4_3 src</b>
1.135 naddy 209: </pre>
1.1 deraadt 210: <p>
1.282 nick 211: Or OPENBSD_4_2 for 4.2, etc.
1.100 ericj 212:
1.282 nick 213: <p> The OPENBSD_4_3 tag contains the release sources and
1.249 nick 214: errata already applied.
1.100 ericj 215:
1.249 nick 216: <h3><a name="CVSROOT"><font color="#0000e0">Available Anonymous CVS Servers
1.155 jsyn 217: </font></a></h3>
1.1 deraadt 218:
219: <p>
1.249 nick 220: <em>Please see the note about <a href="#WHICH">ssh vs. rsh</a> below!</em>
1.12 grr 221: <p>
1.1 deraadt 222: <ul>
1.279 grunk 223: <li><strong>CVSROOT=anoncvs@anoncvs.de.openbsd.org:/cvs</strong><br>
224: Location: University of Erlangen-Nuremberg, Erlangen, Germany.<br>
225: Maintained by <a href="mailto:grunk@pestilenz.org">Alexander von Gernler</a>.<br>
226: Protocols: ssh, ssh port 2022, pserver.<br>
227: Updated every 2 hours.<br>
228: SSH fingerprints:<br>
229: (RSA) 1024 fc:94:b0:c1:e5:b0:98:7c:58:43:99:76:97:ee:9f:b7<br>
230: (DSA) 1024 a9:00:3f:ba:50:81:16:d1:e9:b8:4f:3c:b2:10:e2:6c<br>
231: <p>
1.252 grunk 232: <li><strong>CVSROOT=anoncvs@anoncvs1.usa.openbsd.org:/cvs</strong><br>
1.249 nick 233: Host also known as <strong>anoncvs.usa.openbsd.org, anoncvs4.usa.openbsd.org</strong>.<br>
234: Location: Redwood City, CA, USA.<br>
1.273 martin 235: Maintained by <a href="mailto:millert@openbsd.org">Todd C. Miller</a>.<br>
1.249 nick 236: Protocols: rsh, ssh, ssh port 2022, pserver.<br>
237: Updated every 2 hours.<br>
1.214 millert 238: SSH fingerprints:<br>
239: (RSA1) 1024 64:de:26:16:c2:ff:1b:c7:24:ed:a4:4a:d7:2f:69:3e<br>
240: (RSA) 1024 49:67:9a:46:62:8a:3f:4e:b3:63:ca:d6:41:29:2a:2f<br>
241: (DSA) 1024 a7:75:49:77:f3:47:d1:3c:5e:65:84:84:3b:03:f1:33<br>
1.196 nick 242: <p>
1.209 david 243: <li><strong>CVSROOT=anoncvs@anoncvs3.usa.openbsd.org:/cvs</strong><br>
1.249 nick 244: Location: National Center for Atmospheric Research, Boulder, CO, USA.<br>
1.273 martin 245: Maintained by <a href="mailto:millert@openbsd.org">Todd C. Miller</a>.<br>
1.249 nick 246: Protocols: rsh, ssh, ssh port 2022, pserver.<br>
247: Updated every 2 hours.<br>
1.214 millert 248: SSH fingerprints:<br>
1.272 millert 249: (RSA1) 2048 80:cd:f6:fc:4f:0e:cb:80:6a:d0:6a:5e:dd:9e:5d:0a<br>
250: (RSA) 2048 49:6f:4a:be:02:63:0d:c0:54:b0:57:f0:48:7f:ce:16<br>
251: (DSA) 1024 f9:ab:fc:60:a3:15:8f:9c:47:24:9e:92:15:78:0d:f3<br>
1.1 deraadt 252: <p>
1.246 steven 253: <li><strong>CVSROOT=anoncvs@rt.fm:/cvs</strong><br>
1.249 nick 254: Location: Lake in the Hills, IL, USA.<br>
255: Maintained by <a href="mailto:jcs@rt.fm">Joshua Stein</a>.<br>
256: Protocols: ssh.<br>
257: Updated every 3 hours.<br>
1.231 mickey 258: SSH fingerprints:<br>
1.246 steven 259: (RSA) 1024 54:74:ca:17:d0:07:c3:53:b7:7e:1d:9b:10:bf:04:37<br>
260: (DSA) 1024 46:78:40:52:7a:18:f9:0e:68:61:b0:27:29:f9:d9:c4<br>
1.1 deraadt 261: <p>
1.281 nick 262: <li><strong>CVSROOT=anoncvs@obsd.cec.mtu.edu:/cvs</strong><br>
263: Location: Michigan Technological University, Houghton, Michigan, USA.<br>
264: Maintained by <a href="mailto:celinn@mtu.edu">Chris Linn</a>.<br>
265: Protocols: ssh.<br>
266: Updated every 2 hours.<br>
267: SSH fingerprints:<br>
268: (RSA1) 2048 d7:91:a2:f4:d2:8d:81:7f:3c:44:91:8f:b5:b9:46:48 <br>
269: (RSA) 2048 de:f1:09:85:a0:db:60:97:d4:95:0d:07:80:4e:ee:68<br>
270: (DSA) 1024 78:05:5c:c7:ce:7e:6f:c8:6d:b7:e2:7e:ba:06:1c:40<br>
271: <p>
1.271 martin 272: <li><strong>CVSROOT=anoncvs@anga.funkfeuer.at:/cvs</strong><br>
273: Location: Vienna, Austria.<br>
274: Maintained by <a href="mailto:martin@openbsd.org">Martin Reindl</a>.<br>
275: Protocols: ssh, ssh port 2022.<br>
1.275 martin 276: Updated every 2 hours from anoncvs1.usa.openbsd.org.<br>
1.273 martin 277: SSH fingerprints:<br>
278: (RSA) 2048 e4:a7:3a:ab:e1:a7:c8:eb:5c:f4:ff:38:95:6f:81:f2<br>
279: (DSA) 2048 66:03:a3:bc:46:85:f3:6c:4b:6b:e3:d4:f5:5f:a6:c4<br>
1.271 martin 280: <p>
1.246 steven 281: <li><strong>CVSROOT=anoncvs@anoncvs1.ca.openbsd.org:/cvs</strong><br>
1.249 nick 282: Host also known as <strong>anoncvs.ca.openbsd.org, openbsd.sunsite.ualberta.ca</strong>.<br>
283: Location: Edmonton, Canada.<br>
284: Maintained by <a href="mailto:beck@ualberta.ca">Bob Beck</a>.<br>
1.277 beck 285: Protocols: ssh, ssh port 2022, pserver.<br>
1.249 nick 286: Updated every 2 hours.<br>
1.246 steven 287: <p>
288: <li><strong>CVSROOT=anoncvs@anoncvs.skyrock.com:/cvs/openbsd</strong><br>
1.249 nick 289: Location: Paris, France.<br>
290: Maintained by <a href="mailto:anoncvs@pureftpd.org">Frank Denis</a>.<br>
291: Protocols: ssh, ssh port 2022.<br>
292: Updated every 2 hours from anoncvs3.usa.openbsd.org.<br>
1.246 steven 293: SSH fingerprints:<br>
294: (RSA1) 2048 4d:60:d8:ab:bc:c6:29:64:b4:45:1b:98:2b:fe:40:7e<br>
295: (RSA) 2048 01:f1:c4:25:c8:e3:0d:0e:7a:33:94:14:f4:9d:98:5f<br>
296: (DSA) 2048 73:36:41:46:fd:0a:67:df:e6:c1:4a:6b:02:61:f4:61<br>
1.121 deraadt 297: <p>
1.264 grunk 298: <li><strong>CVSROOT=anoncvs@openbsd.spline.de:/cvs</strong><br>
299: Host also known as <strong>openbsd.spline.inf.fu-berlin.de</strong>.<br>
300: Location: SPLINE, Institut für Informatik, Freie Universität, Berlin, Germany.<br>
301: Maintained by <a href="mailto:stsp@spline.de">Stefan Sperling</a>.<br>
302: Protocols: ssh, ssh port 2222, pserver.<br>
303: Updated every 2 hours from openbsd.informatik.uni-erlangen.de.<br>
304: SSH fingerprints:<br>
305: (RSA) 2048 13:d2:a6:ff:5c:29:f8:ca:15:73:75:1b:b1:d3:b0:48<br>
306: (DSA) 2048 a0:c2:60:15:54:50:af:07:64:85:89:66:29:e7:0b:86<br>
307: <p>
1.246 steven 308: <li><strong>CVSROOT=anoncvs@mirror.osn.de:/cvs</strong><br>
1.249 nick 309: Location: Nürnberg, Germany.<br>
310: Maintained by <a href="mailto:aw@osn.de">Armin Wolfermann</a>.<br>
311: Protocols: ssh.<br>
1.252 grunk 312: Updated every 4 hours from anoncvs1.usa.openbsd.org.<br>
1.215 david 313: SSH fingerprints:<br>
1.246 steven 314: (RSA) 1024 f2:73:d2:f6:e3:01:ef:ca:3b:e7:6c:80:b6:bd:bb:84<br>
315: (DSA) 1024 fb:33:05:62:96:20:cf:88:7e:10:cb:8d:91:72:57:32<br>
316: <p>
317: <li><strong>CVSROOT=anoncvs@anoncvs.silihost.hu:/cvs</strong><br>
1.249 nick 318: Location: Budapest, Hungary.<br>
319: Maintained by <a href="mailto:robert@openbsd.org">Robert Nagy</a>.<br>
320: Protocols: ssh.<br>
321: Updated every 3 hours from anoncvs.de.openbsd.org.<br>
1.123 beck 322: <p>
1.246 steven 323: <li><strong>CVSROOT=anoncvs@anoncvs.jp.openbsd.org:/cvs</strong><br>
1.249 nick 324: Host also known as <strong>kankoromochi.econ.nagasaki-u.ac.jp</strong>.<br>
325: Location: Nagasaki University, Faculty of Economics, Nagasaki, Japan.<br>
326: Maintained by <a href="mailto:sigh@net.nagasaki-u.ac.jp">Suzuki Itoshi</a>.<br>
327: Protocols: ssh, pserver.<br>
328: Updated every 3 hours.<br>
1.176 miod 329: <p>
330: <li><strong>CVSROOT=anoncvs@anoncvs.openbsd.lt:/cvs</strong><br>
1.249 nick 331: Location: TVK, Cable TV and Internet Services, Taurage, Lithuania.<br>
332: Maintained by <a href="mailto:helpas@ebox.lt">Donatas Budvytis</a>.<br>
333: Protocols: ssh.<br>
334: Updated every 3 hours from cvsup.no.openbsd.org.<br>
1.183 jufi 335: <p>
1.246 steven 336: <li><strong>CVSROOT=anoncvs@anoncvs.nl.openbsd.org:/cvs</strong><br>
1.249 nick 337: Host also known as <strong>anoncvs.calyx.nl</strong>.<br>
338: Location: Amsterdam, The Netherlands.<br>
339: Protocols: ssh.<br>
340: Updated every 3 hours.<br>
1.194 nick 341: <p>
1.246 steven 342: <li><strong>CVSROOT=anoncvs@anoncvs.no.openbsd.org:/cvs</strong><br>
1.249 nick 343: Host also known as <strong>cvs.inet.no</strong>.<br>
344: Location: Oslo, Norway.<br>
345: Maintained by <a href="mailto:cvsadmin@inet.no">Michael Schuldman</a>.<br>
346: Protocols: rsh, ssh, ssh port 2022.<br>
347: Updated every 4 hours.<br>
1.186 beck 348: <p>
349: <li><strong>CVSROOT=anoncvs@openbsd.chem.uw.edu.pl:/cvs</strong><br>
1.249 nick 350: Location: Warsaw, Poland.<br>
351: Maintained by <a href="mailto:admin@chem.uw.edu.pl">Piotr Klein</a>.<br>
352: Protocols: ssh.<br>
353: Updated every 3 hours.<br>
1.203 saad 354: <p>
1.267 grunk 355: <li><strong>CVSROOT=anoncvs@anoncvs.obsd.si:/cvs</strong><br>
356: Host also known as <strong>nina.kerberos.si</strong>.<br>
357: Location: Ljubljana, Slovenia.<br>
358: Maintained by <a href="mailto:mitja@kerberos.si">Mitja Muzenic</a>.<br>
359: Protocols: ssh.<br>
360: Updated every 2 hours from cvsync.de.openbsd.org.<br>
361: <p>
1.269 grunk 362: <li><strong>CVSROOT=anoncvs@anoncvs.btradianz.se:/cvs</strong><br>
363: Location: BT GFS Sweden, Stockholm, Sweden.<br>
1.281 nick 364: Maintained by <a href="mailto:johan@openbsd.org">Johan M:son Lindman</a>.<br>
1.269 grunk 365: Protocols: ssh, ssh port 2022.<br>
366: Updated every 2 hours from rsync.de.openbsd.org.<br>
367: <p>
1.230 naddy 368: <li><strong>CVSROOT=anoncvs@mirror.sg.depaul.edu:/cvs</strong><br>
1.249 nick 369: Location: DePaul University, Chicago, IL, USA.<br>
370: Maintained by <a href="mailto:mirror-admin@sg.depaul.edu">Eric Pancer</a>.<br>
371: Protocols: ssh, ssh port 2022, pserver.<br>
372: Updated every 2 hours.<br>
1.230 naddy 373: SSH fingerprints:<br>
374: (RSA1) 1024 5b:1c:cb:b7:5f:82:82:cc:af:13:21:a4:2c:c2:55:6b<br>
1.246 steven 375: (RSA) 1024 18:0f:97:2a:cf:6c:7f:d4:ca:2b:bc:c8:b9:56:2b:86<br>
376: (DSA) 1024 65:cb:ce:7c:3e:29:5c:82:0b:9d:fa:b7:bb:e0:4b:47<br>
1.236 grunk 377: <p>
1.254 steven 378: <li><strong>CVSROOT=anoncvs@mirror.planetunix.net:/cvs</strong><br>
1.270 steven 379: Location: CalPOP, Los Angeles, CA, USA.<br>
1.254 steven 380: Maintained by <a href="mailto:brian@planetunix.net">Brian Brombacher</a>.<br>
381: Protocols: ssh, ssh port 2022, pserver.<br>
1.270 steven 382: Updated every 3 hours from rt.fm.<br>
1.254 steven 383: SSH fingerprints:<br>
384: (RSA1) 2048 e4:22:93:81:84:e0:68:8c:0b:d5:1f:78:cd:6f:fa:c3<br>
385: (RSA) 2048 8f:42:bd:b0:a2:94:df:6b:af:1e:96:03:ea:68:03:d9<br>
386: (DSA) 1024 26:51:e8:b3:38:88:dc:a8:2a:98:59:86:ab:40:bb:a4<br>
387: <p>
1.246 steven 388: <li><strong>CVSROOT=anoncvs@anoncvs.nyc.openbsd.org:/cvs</strong><br>
1.249 nick 389: Location: New York Internet, New York, NY, USA.<br>
1.278 okan 390: Maintained by <a href="mailto:mickey@lucifier.net">Michael Shalayeff</a>.<br>
1.249 nick 391: Protocols: rsh, ssh, ssh port 2022, pserver.<br>
392: Updated every 2 hours.<br>
1.246 steven 393: SSH fingerprints:<br>
394: (RSA1) 1024 ff:97:fc:34:c6:09:7f:b2:bd:31:4e:d5:51:ce:f3:44<br>
395: (RSA) 1024 05:ac:be:be:f8:f6:ab:63:5e:80:6c:be:d3:31:41:cd<br>
396: (DSA) 1024 89:be:38:4d:2a:1b:1a:db:93:65:9d:36:7f:ee:d2:76<br>
1.240 grunk 397: <p>
1.283 ! sthen 398: <li><strong>CVSROOT=anoncvs@openbsd.mirror.frontiernet.net:/cvs</strong><br>
! 399: Location: Frontier Communications, Rochester, NY, USA.<br>
! 400: Maintained by <a href="mailto:jrrs@frontiernet.net">jared r r spiegel</a>.<br>
! 401: Protocols: ssh.<br>
! 402: Updated every 4 hours from anoncvs.ca.openbsd.org.<br>
! 403: <p>
1.246 steven 404:
1.73 deraadt 405: </ul>
1.84 beck 406:
1.73 deraadt 407: <p>
1.249 nick 408: <em>Note:</em> If your server is listed on here with inaccurate or
409: unknown information, please contact
410: <a href="mailto:beck@openbsd.org"><tt>beck@openbsd.org</tt></a>
1.104 ericj 411:
1.80 beck 412: <p>
1.249 nick 413: You may want to use
1.135 naddy 414: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=traceroute&sektion=8&format=html">traceroute(8)</a>
1.249 nick 415: to find out which server is nearest you.
416: Problems with a server should be reported to the <b>maintainer</b> of the
417: server in question.
1.104 ericj 418:
1.249 nick 419: <h3><a name="CRYPTO"><font color="#0000e0">Getting crypto sources through
420: cvs(1)</font></a></h3>
1.104 ericj 421:
1.1 deraadt 422: <p>
1.249 nick 423: <strong>IMPORTANT NOTE:</strong>
424: There are a few issues relating to cryptographic software that everyone
425: should be aware of:
1.1 deraadt 426: <ul>
1.249 nick 427: <li>The OpenBSD sources are from Canada.
428: As
1.182 nick 429: <a href="http://www.efc.ca/pages/doc/crypto-export.html">
1.249 nick 430: researched by a Canadian individual</a>
431: and as
1.135 naddy 432: <a href="http://axion.physics.ubc.ca/ECL.html">
1.249 nick 433: described in the Export Control list of Canada</a>
434: it is legal to export crypto software from Canada to the world.
1.1 deraadt 435: <p>
1.249 nick 436: <li>However, if you are outside the USA or Canada, you should not
437: fetch the cryptographic sections of the OpenBSD sources from an
438: anoncvs server located in the USA. The files in question are...
1.1 deraadt 439: <ul>
440: <li>src/kerberosIV/*
1.167 miod 441: <li>src/kerberosV/*
1.57 art 442: <li>src/lib/libdes/*
1.1 deraadt 443: <li>src/lib/libc/crypt/crypt.c
444: <li>src/lib/libc/crypt/morecrypt.c
1.167 miod 445: <li>src/sys/crypto
1.36 deraadt 446: <li>src/sys/netinet
1.67 art 447: <li>src/usr.sbin/afs/src/rxkad/*
1.167 miod 448: <li>XF4/xc-mit/lib/Xdmcp/Wraphelp.c
449: <li>XF4/xc-old/lib/Xdmcp/Wraphelp.c
450: <li>XF4/xc/lib/Xdmcp/Wraphelp.c
1.1 deraadt 451: </ul>
1.249 nick 452: Because of US Dept. of Commerce policy,
453: crypto software may only be exported to Canada from the USA.
1.1 deraadt 454: </ul>
455:
1.249 nick 456: <h3><a name="EXAMPLE"><font color="#0000e0">Example usages for cvs(1)</font>
1.155 jsyn 457: </a></h3>
1.104 ericj 458:
1.198 david 459: <p>
1.249 nick 460: NOTICE: If you want to update a branch (such as a patch branch)
461: to <i>current</i>, you would add the <code>-A</code>
462: flag to cvs, but this flag is of little use otherwise. Some older
463: versions of the OpenBSD documentation recommended use of this flag
464: in many examples. We no longer recommend this flag unless absolutely necessary.
1.163 chris 465:
1.1 deraadt 466: <p>
1.249 nick 467: A sample use of an anoncvs server would be:
1.135 naddy 468: <pre>
1.245 ray 469: $ <strong>cd /tmp</strong>
470: $ <strong>cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs get src/sys/arch/sparc</strong>
1.249 nick 471: [copies the files from the repository to your machine]
1.245 ray 472: $ <strong>cd src/sys/arch/sparc</strong>
473: $ <strong>cvs log locore.s</strong>
1.249 nick 474: [shows the commit log for the chosen file]
1.245 ray 475: $ <strong>cvs diff -bc -r1.1 -r1.5 locore.s</strong>
1.249 nick 476: [shows the changes between revisions 1.1 and rev 1.5]
1.135 naddy 477: </pre>
1.1 deraadt 478:
479: <p>
1.249 nick 480: <a name="pserver">In order to use a cvs ``pserver'' (a direct TCP connection
481: instead of using ssh or rsh) you must login once:</a>
1.104 ericj 482:
1.135 naddy 483: <pre>
1.245 ray 484: $ <strong>cvs -d :pserver:anoncvs@anoncvs.ca.openbsd.org:/cvs login</strong>
1.249 nick 485: (Logging in to anoncvs@anoncvs1.ca.openbsd.org)
1.104 ericj 486: CVS password: <strong>anoncvs</strong>
1.249 nick 487: [This writes a line to ~/.cvspass (filename over-ridden by CVS_PASSFILE).]
488: [An example line from my ~/.cvspass after typing 'blah' for the above ]
489: [password is: ]
490: [:pserver:anoncvs@anoncvs5.usa.openbsd.org:/cvs Au'yc ]
491: [After logging in ONCE every other use of the above CVSROOT will work. ]
1.245 ray 492: $ <strong>cvs -d :pserver:anoncvs@anoncvs.ca.openbsd.org:/cvs get ksrc-i386 ksrc-common</strong>
1.249 nick 493: [Allows you to retrieve ONLY that necessary to rebuild an i386 kernel. ]
1.135 naddy 494: </pre>
1.18 todd 495:
496: <p>
1.249 nick 497: Here is how someone using anoncvs regularly would update his
498: source tree:
499: <ul><li>First, start out by `get'-ing an initial tree:
1.27 todd 500:
1.249 nick 501: <p> (If you are following <i>current</i>):
1.135 naddy 502: <pre>
503: # <strong>cd /usr</strong>
1.245 ray 504: # <strong>cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -P src</strong>
1.135 naddy 505: </pre>
1.109 jason 506:
1.282 nick 507: <p> (If you are following the patch branch for 4.3):
1.135 naddy 508: <pre>
509: # <strong>cd /usr</strong>
1.282 nick 510: # <strong>cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_4_3 -P src</strong>
1.135 naddy 511: </pre>
1.37 todd 512:
1.249 nick 513: <li> Anytime afterwards, to `update' this tree:
514: <p> (If you are following <i>current</i>):
1.135 naddy 515: <pre>
516: # <strong>cd /usr/src</strong>
1.163 chris 517: # <strong>cvs -q up -Pd</strong>
1.135 naddy 518: </pre>
1.27 todd 519:
1.282 nick 520: <p> (If you are following the patch branch for 4.3):
1.135 naddy 521: <pre>
522: # <strong>cd /usr/src</strong>
1.282 nick 523: # <strong>cvs -q up -rOPENBSD_4_3 -Pd</strong>
1.135 naddy 524: </pre>
1.109 jason 525:
1.249 nick 526: Every time you ran this it would synchronize your /usr/src tree. It would
527: not destroy any of your local changes, rather it would attempt to merge
528: changes in.
1.72 millert 529:
530: <p>
1.249 nick 531: <li> NOTE:
532: If you are updating a source tree that you initially fetched
533: from a different server, or from a CD, you <strong>must</strong>
534: add the <em>-d anoncvs@anoncvs.ca.openbsd.org:/cvs</em> options to cvs.
1.135 naddy 535: <pre>
536: # <strong>cd /usr/src</strong>
1.245 ray 537: # <strong>cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs -q up -Pd</strong>
1.135 naddy 538: </pre>
1.27 todd 539: </ul>
540:
1.37 todd 541: <p>
1.249 nick 542: To <a name="ports">use</a> <a href="ports.html">ports</a>, it is similar to src:
1.37 todd 543: <ul><li>
1.249 nick 544: <p> (If you are following <i>current</i>):
1.37 todd 545: <pre>
1.135 naddy 546: # <strong>cd /usr</strong>
1.245 ray 547: # <strong>cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -P ports</strong>
1.38 deraadt 548: </pre>
1.282 nick 549: <p> (If you are following the patch branch for 4.3):
1.157 heko 550: <pre>
551: # <strong>cd /usr</strong>
1.282 nick 552: # <strong>cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_4_3 -P ports</strong>
1.157 heko 553: </pre>
1.249 nick 554: <li> Anytime afterwards, to `update' this tree:
555: <p> (If you are following <i>current</i>):
1.37 todd 556: <pre>
1.218 nick 557: # <strong>cd /usr/ports</strong>
558: # <strong>cvs -q up -Pd</strong>
1.157 heko 559: </pre>
1.282 nick 560: <p> (If you are following the patch branch for 4.3):
1.157 heko 561: <pre>
1.218 nick 562: # <strong>cd /usr/ports</strong>
1.282 nick 563: # <strong>cvs -q up -rOPENBSD_4_3 -Pd</strong>
1.157 heko 564: </pre>
1.127 jufi 565: </ul>
1.37 todd 566:
1.249 nick 567: In the above example, <i>-q</i> is optional, only intended to minimize
568: cvs's output. For those who like to see screenfulls of output, it
569: can be omitted.
1.1 deraadt 570:
571: <p>
1.250 steven 572: To make a diff of a locally patched module (here <i>cd.c</i>) to include with
1.249 nick 573: a bug report:
1.135 naddy 574: <pre>
575: # <strong>cd /usr</strong>
576: # <strong>cvs diff -u src/sys/scsi/cd.c > /tmp/patch</strong>
577: </pre>
1.12 grr 578:
579: <p>
1.249 nick 580: The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&sektion=1&format=html">
581: cvs(1) man page</a>
582: (included with the CVS sources) has much more
583: information about how CVS can be used.
1.1 deraadt 584:
1.105 ericj 585: <p>
1.249 nick 586: <strong>Warning:</strong>
587: When using cvs you should take care that your current directory is either
588: the root of the tree you are referencing or in a separate place such as /tmp.
589: Some commands such as "get" can create an arbitrary sub-tree in the current
590: directory, and a subsequent update will recursively flesh out this sub-tree.
1.12 grr 591:
592: <p>
1.249 nick 593: The anoncvs service gives fledgling developers a chance to learn CVS
594: operation and get thoroughly involved in the development process
595: before getting "commit" access -- as a result of showing useful
596: skills and high quality results they will naturally later be given
597: developer access. As well, people providing patches can create
598: their "diff"s relative to the CVS tree, which will ease integration.
1.1 deraadt 599:
1.104 ericj 600:
1.249 nick 601: <h3><a name="WHICH"><font color="#0000e0">Use rsh(1) or ssh(1)?</font></a></h3>
1.104 ericj 602:
1.249 nick 603: CVS supports three access methods between the CVS server and the CVS
604: client:
1.226 nick 605:
606: <ul>
1.249 nick 607: <li><b>ssh:</b> Secure Shell can be used to access the anonymous CVS servers.
608: This is the <i>recommended</i> way of doing so, as it is encrypted.
1.226 nick 609:
1.249 nick 610: <li><b>rsh:</b> Remote Shell can be used on some of the servers for users
611: who don't have access to <a href="http://www.openssh.com/">ssh</a>.
1.226 nick 612:
1.249 nick 613: <li><b>pserver:</b> pserver is primarily useful for users who are behind
614: firewalls that block the other two connections.
1.226 nick 615: </ul>
616:
1.249 nick 617: <p>
618: <b>NOTE:</b> For users wishing to use rsh, you must first set the
619: <tt>CVS_RSH</tt> environment variable to point to the rsh(1) program:
1.226 nick 620:
621: <ul>
1.249 nick 622: <li>For Korn/Bourne shells:
1.226 nick 623: <pre>
624: $ <b>export CVS_RSH=/usr/bin/rsh</b>
625: </pre>
1.249 nick 626: <li>For csh/tcsh:
1.226 nick 627: <pre>
628: % <b>setenv CVS_RSH /usr/bin/rsh</b>
629: </pre>
630: </ul>
631:
1.1 deraadt 632: <p>
1.249 nick 633: By default, OpenBSD's CVS client uses ssh ("secure shell":
634: <a href="http://www.openssh.com/">OpenSSH</a>) to talk to the CVS server.
1.159 jcs 635:
636: <p>
1.282 nick 637: Many of the CVS sites no longer support rsh or pserver for security reasons.
638: Local
1.249 nick 639: problems like firewalls or imperfect protocol emulators such as slirp may
640: also hinder rsh usage. However, if rsh is desired, one must set the
641: <var>CVS_RSH</var> environment variable to point to rsh
642: (typically <strong>/usr/bin/rsh</strong>).
1.159 jcs 643:
644: <p>
1.249 nick 645: If local policy prevents outgoing connections to ssh's default port of 22,
646: port 2022 may be used in its place. Note, however, that not all anoncvs
647: servers accept ssh connections on this port. Furthermore, most anoncvs servers
648: no longer accept the <strong>none</strong> cipher, as it is disabled in
649: recent versions of ssh for security reasons. Also, do not be tempted
650: to turn on compression: CVS already compresses.
1.159 jcs 651:
652: <p>
1.249 nick 653: One could specify something like the following in the
654: <strong>$HOME/.ssh/config</strong> configuration file to avoid the pitfalls
655: and restrictions mentioned above:
1.1 deraadt 656: <pre>
1.59 beck 657: Host anoncvs.ca.openbsd.org
1.159 jcs 658: Compression no
1.1 deraadt 659: Port 2022
660: </pre>
661:
662: <p>
1.249 nick 663: CVS is a little noisy starting up; to quiet it a bit you may want to
664: do this:
1.105 ericj 665:
1.135 naddy 666: <pre>
1.245 ray 667: <strong>$ export CVS_CLIENT_PORT=-1</strong>
1.135 naddy 668: </pre>
1.1 deraadt 669:
670: <p>
1.249 nick 671: <h3><a name="SUP"><font color="#0000e0">Mirroring the CVS repository via
672: sup(1)</font></a></h3>
1.107 millert 673:
674: <p>
1.249 nick 675: Users wishing to mirror the OpenBSD CVS tree itself may now do so
676: from <em>anoncvs.usa.openbsd.org</em> or <em>anoncvs3.usa.openbsd.org</em>
677: (these are different machines). Note that this is the cvs tree,
678: <b>not</b> a checked out source tree. It is only useful if you
679: want to be able to do fast cvs operations (diff, annotate, etc) or
680: if you have multiple source trees and you only want to transfer new
681: data once (you can then checkout a tree from your local cvs mirror).
1.107 millert 682: <p>
1.249 nick 683: A sample supfile would be:
1.107 millert 684: <pre>
685: cvs host=anoncvs.usa.openbsd.org hostbase=/ base=/home delete
686: </pre>
687: <p>
1.249 nick 688: which would mirror the cvs tree into /home/cvs with the sup data
689: files ending up in /home/sup. The full OpenBSD cvs tree is currently
1.260 nick 690: about 3.5GB in size, and will, of course continue to grow.
1.65 matthieu 691:
1.249 nick 692: <h3><a name="MIRROR"><font color="#0000e0">Setting up an anoncvs mirror
1.155 jsyn 693: </font></a></h3>
1.105 ericj 694:
1.107 millert 695: <p>
1.249 nick 696: If you wish to setup a new anoncvs mirror site and make it available to
697: the general public, please contact the anoncvs
698: <a href="mailto:sup@openbsd.org">maintainer</a>.
1.259 nick 699: Anoncvs mirrors currently require about 3.5GB of disk (and it will grow!),
700: and use up to 32MB of swap
1.249 nick 701: per anoncvs user (assuming the user does a large operation; while smaller
702: operations use fewer resources, anoncvs still makes much more of an
703: impact than ftp or sup). Such anoncvs machines should have excellent
704: network connectivity for the area they are expected to serve. A
705: <a href="anoncvs.shar">document</a>
706: which describes the setup of anoncvs servers is available.
707:
708: <h3><font color="#0000e0">Final notes</font></h3>
709: After upgrading your source tree, you should read the comments
710: at the top of <kbd>/usr/src/Makefile</kbd> before attempting
711: a build. Also, you should build a new kernel <strong>before</strong>
712: doing a <kbd>make build</kbd> if possible. In some cases it may be
713: necessary to rebuild and install the <kbd>config</kbd> utility before
714: you can build the kernel. If <kbd>config GENERIC</kbd> fails this
715: is probably the case.
716: <p>
717: It is important to note that upgrading from a release to the current tree
718: by rebuilding the sources can be rather difficult due to dependencies
719: that are often not obvious. Therefore, it is suggested that you first
720: install the latest snapshot before attempting a tree build from source.
1.1 deraadt 721:
722: <hr>
1.249 nick 723: <a href="index.html"><img height="24" width="24" src="back.gif" border="0"
724: alt="OpenBSD"></a>
1.135 naddy 725: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.283 ! sthen 726: <br><small>$OpenBSD: anoncvs.html.end,v 1.9 2008/05/01 00:23:37 nick Exp $
1.155 jsyn 727: </small>
1.1 deraadt 728:
729: </body>
730: </html>