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