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