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