Annotation of www/anoncvs.html, Revision 1.83
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
1.49 ian 4: <title>OpenBSD AnonCVS</title>
5: <link rev=made href=mailto:www@openbsd.org>
6: <meta name="resource-type"
7: content="document">
8: <meta name="description"
9: content="How to get OpenBSD updates via Internet using Anonymous CVS">
10: <meta name="keywords"
11: content="openbsd,anoncvs,updates">
12: <meta name="distribution"
13: content="global">
14: <meta name="copyright"
15: content="This document copyright 1996-1998 by OpenBSD.">
1.1 deraadt 16: </head>
17:
1.14 downsj 18: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
1.1 deraadt 19:
1.58 pauls 20: <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
1.14 downsj 21:
1.43 deraadt 22: <h3><font color=#0000e0>Anonymous CVS Access:</font></h3>
1.15 grr 23: <p>
24: Anonymous CVS is a method of keeping your local copy of the OpenBSD source
25: tree up to date with respect to changes made to current OpenBSD sources.
1.14 downsj 26: <p>
1.15 grr 27: The major advantage of Anonymous CVS over other source code update
28: techniques is that it works directly against a central source code
29: repository or mirror. This means that you have the full set of CVS
30: commands available to control merging and updating your changes with
31: other source changes and for performing diff's, change histories
32: and other queries against the central repository.
1.36 deraadt 33: <p>
34: You can use anoncvs to access our three main source repositories:
35: <strong>src</strong>, <strong>ports</strong>, and <strong>www</strong>.
36: <p>
1.43 deraadt 37: <h3><font color=#0000e0>CVS:</font></h3>
1.36 deraadt 38: <a href=why-cvs.html>
39: CVS is the source code control system used to manage the OpenBSD source tree.</a>
1.16 deraadt 40: It implements a central repository for all officially released source code
1.15 grr 41: and changes, while permitting developers to maintain local copies of the
42: source code with their working changes. Developers with "write access"
43: can commit changes directly to the OpenBSD source tree, while "Anonymous
44: CVS" users have "read access" and can keep their local copies of the source
45: up to date and issue queries against the central depository.
46: <p>
1.22 niklas 47: The major strength of CVS is that it has the ability to perform intelligent
1.15 grr 48: merges of changes to the central repository with changes that you make to
49: your local copy. This means that if you make a change to a module and
50: perform an update, your changes are not "blown away", rather CVS makes
51: best efforts to merge the changes made to the central sources with changes
52: you've made to your local copy.
53: <p>
54: In the event that the changes can't be completely merged, CVS provides a
55: "soft fallback", in terms of providing you with annotated changes to your
1.39 todd 56: local copy, preserving an unmodified copy of your version and continuing
1.15 grr 57: to update any other source modules you requested.
1.22 niklas 58: <p>
1.23 mickey 59: People who own an OpenBSD CD may have seen the CVS/ dirs on it.
1.22 niklas 60: Actually there is a reason, the CD has a checkout of the OpenBSD src/ module
1.23 mickey 61: usable to continue updating from. Using this tree will results in a much
62: faster initial CVS update than a fresh checkout of the full OpenBSD
63: source tree. There are two ways of using the CD:
64: <ul>
65: <li>copy the tree off it, (assuming the CD is mounted on /mnt):
1.22 niklas 66: <pre>
1.23 mickey 67: <b>#</b> cd /mnt; cp -Rp CVS Makefile bin distrib etc games gnu \
68: <b>></b> include kerberosIV lib libexec lkm regress sbin share \
69: <b>></b> sys usr.bin usr.sbin /usr/src
1.22 niklas 70: </pre>
1.23 mickey 71: <li>use a union mount with the CD below a writable directory.
1.22 niklas 72: <pre>
1.23 mickey 73: <b>#</b> mount -t union -o -b /mnt /usr/src
1.22 niklas 74: </pre>
1.23 mickey 75: </ul>
1.22 niklas 76: After this, /usr/src will be a nice checkout area where all cvs(1) commands
77: will work OK.
1.15 grr 78: <h4>CVS COMMAND SUMMARY</h4>
1.27 todd 79: <dt> cvs [cvs args] [cvs command] [cvs command args]
80: <dd> below is a listing of commonly used cvs commands.
1.15 grr 81: <dl>
82: <DT>add
83: <dd>Add a new file or directory to the repository.
84: <dt>get
85: <dd>Make a working directory of source files for editing.
86: <dt>commit
87: <dd>Apply changes to the source repository (write access)
88: <dt>diff
89: <dd>Show differences between local files and the source repository.
90: <dt>history
91: <dd>Show reports on cvs commands against the source repository.
92: <dt>log
93: <dd>Display CVS log information.
94: <dt>rdiff
95: <dd>Prepare a collection of diffs reflecting changes between release.
96: <dt>status
97: <dd>Show current status of files in the repository and local copies.
98: <dt>update
99: <DD>Bring your working directory up to date with the repository.
100: </dl>
1.1 deraadt 101: <p>
1.39 todd 102: To summarize, the real strength of using Anonymous CVS is that it is
1.15 grr 103: a "tolerant" source code control system - it <strong>respects</strong>
104: changes that you have made to your local sources and makes <strong>
105: "best efforts"</strong> to update your entire source tree, rather than
106: leaving you a list of arcane problems that have to be resolved before
107: continuing.
1.1 deraadt 108:
1.43 deraadt 109: <h3><font color=#0000e0>Using Anonymous CVS:</font></h3>
1.1 deraadt 110: <p>
111: The latest version of CVS is available at
1.47 pauls 112: <a href=http://download.cyclic.com/pub/>Cyclic</a>.
1.1 deraadt 113: Versions earlier than 1.6 are not recommended, and may not work.
114: If you already have OpenBSD installed, CVS is included.
115:
116: <p>
117: There are two levels of source tree access:
118:
119: <dl>
120: <dt><strong>Read-write access for developers:</strong>
121: <dd>Developers who need to commit changes to the source tree must have
122: an account on the OpenBSD machines. Getting this access will be a
123: natural result of working on the sources with other OpenBSD developers.
124: If someone does some good work and shows they can work with the team,
125: they will get an account.
126: </dl>
127:
128: <dl>
129: <dt><strong>Read-only access for everyone:</strong>
130: <dd>Anyone can access the read-only CVS repositories. These copies
131: of the read-write CVS repository are mirrored often. To use one,
132: set your <strong>CVSROOT</strong> environment variable to one of
133: the following values:
1.12 grr 134: <p>
135: <strong>Please see the note about using ssh vs. rsh below!</strong>
136: <p>
1.1 deraadt 137: <ul>
138: <p>
1.83 ! millert 139: <li><strong>CVSROOT=anoncvs@anoncvs1.usa.openbsd.org:/cvs</strong><br>
! 140: Host also known as <strong>anoncvs@anoncvs4.usa.openbsd.org</strong>.<br>
1.10 millert 141: located in California, western USA.<br>
1.46 millert 142: maintained by <a href=mailto:millert@openbsd.org>Todd Miller</a>.<br>
1.83 ! millert 143: protocols: pserver only.<br>
1.1 deraadt 144: updated every 4 hours.<br>
145: <p>
1.83 ! millert 146: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
! 147: Host also known as <strong>anoncvs3.usa.openbsd.org</strong>.<br>
1.1 deraadt 148: located at the University of Colorado, Boulder, western USA.<br>
149: maintained by <a href=mailto:Todd.Miller@cs.colorado.edu>Todd Miller</a>.<br>
1.71 millert 150: protocols: ssh, ssh port 2022, pserver.<br>
1.1 deraadt 151: updated every 6 hours.<br>
152: <p>
1.76 deraadt 153: <li><strong>CVSROOT=anoncvs@anoncvs5.usa.openbsd.org:/cvs</strong><br>
154: Host also known as <strong>squid.nas.nasa.gov</strong>.<br>
155: located at Ames Research Center, Moffett Field, California, USA.<br>
1.78 deraadt 156: maintained by <a href=mailto:allison@mail.arc.nasa.gov>Tyler Allison</a>.<br>
1.77 deraadt 157: protocols: ssh only.<br>
158: updated every 3 hours.<br>
1.76 deraadt 159: <p>
1.31 deraadt 160: <li><strong>CVSROOT=anoncvs@anoncvs6.usa.openbsd.org:/cvs</strong><br>
161: Host also known as <strong>openbsd.citi.umich.edu</strong>.<br>
162: located at the University of Michigan, central USA.<br>
163: maintained by <a href=mailto:rees@umich.edu>Jim Rees</a>.<br>
164: protocols: ssh, ssh port 2022.<br>
165: updated every 12 hours.<br>
166: <p>
1.24 deraadt 167: <li><strong>CVSROOT=anoncvs@anoncvs1.ca.openbsd.org:/cvs</strong><br>
1.40 beck 168: Host also known as <strong>anoncvs.ca.openbsd.org</strong>,
1.74 beck 169: <strong>openbsd.sunsite.ualberta.ca</strong><br>
1.24 deraadt 170: located in Edmonton, Alberta, Canada.<br>
1.80 beck 171: maintained by <A HREF="mailto:beck@ualberta.ca">Bob Beck</A><br>
1.53 beck 172: protocols: ssh, rsh, ssh port 2022, pserver<br>
1.45 beck 173: updated every 2 hours.<br>
1.24 deraadt 174: <p>
1.1 deraadt 175: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
176: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
177: located in London, UK.<br>
178: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
179: protocols: rsh.<br>
180: updated every 12 hours.<br>
181: <p>
182: <li><strong>CVSROOT=anoncvs@anoncvs.tw.openbsd.org:/cvs</strong><br>
1.64 deraadt 183: Host also known as <strong>OpenBSD.csie.NCTU.edu.tw</strong>.<br>
1.1 deraadt 184: located in Taipei, Taiwan.<br>
1.63 deraadt 185: maintained by <a href=mailto:lkchu@OpenBSD.csie.NCTU.edu.tw>Liang-Kai Chu</a>.<br>
1.1 deraadt 186: protocols: rsh, ssh, ssh port 2022.<br>
187: updated every 12 hours.<br>
188: <p>
189: <li><strong>CVSROOT=anoncvs@anoncvs.no.openbsd.org:/cvs</strong><br>
1.64 deraadt 190: Host also known as <strong>cvs.inet.no</strong>.<br>
1.1 deraadt 191: located in Norway.<br>
1.64 deraadt 192: maintained by <a href=mailto:cvsadmin@inet.no>Michael Shuldman</a>.<br>
1.1 deraadt 193: protocols: rsh, ssh, ssh port 2022.<br>
194: updated every 4 hours.<br>
195: <p>
1.33 deraadt 196: <li><strong>CVSROOT=anoncvs@anoncvs.se.openbsd.org:/cvs</strong><br>
1.54 art 197: Host also known as <strong>anoncvs.stacken.kth.se</strong>.<br>
1.33 deraadt 198: located in Sweden.<br>
199: maintained by <a href=mailto:anoncvs@stacken.kth.se>Magnus Holmberg</a>.<br>
200: protocols: rsh, ssh, ssh port 2022.<br>
1.57 art 201: updated every 3 hours.<br>
1.68 wvdputte 202: <p>
203: <li><strong>CVSROOT=anoncvs@anoncvs.be.openbsd.org:/cvs</strong><br>
204: Host also known as <strong>badlands.rug.ac.be</strong>.<br>
205: located in Belgium.<br>
206: maintained by <a href=mailto:wvdputte@reptile.rug.ac.be>Wim Vandeputte</a>.<br>
207: protocols: ssh, ssh port 2022.<br>
208: updated every 3 hours.<br>
1.69 deraadt 209: <p>
210: <li><strong>CVSROOT=anoncvs@anoncvs.jp.openbsd.org:/cvs</strong><br>
211: Host also known as <strong>kankoromochi.econ.nagasaki-u.ac.jp</strong>.<br>
212: located at Nagasaki Univ. Faculty of Economics, JAPAN.<br>
213: maintained by <a href=mailto:sigh@net.nagasaki-u.ac.jp>SUZUKI Hitoshi</a>.<br>
1.79 deraadt 214: protocols: ssh, pserver.<br>
215: updated every 3 hours.<br>
1.73 deraadt 216: <li><strong>CVSROOT=anoncvs@anoncvs.cz.openbsd.org:/cvs</strong><br>
217: Host also known as <strong>com-os2.ms.mff.cuni.cz</strong>.<br>
218: located at Faculty Math & Physics, Charles University, Prague, Czech republic.<br>
219: maintained by <a href=mailto:galambos@com-os2.ms.mff.cuni.cz>Leo Galambos</a>.<br>
220: protocols: ssh, ssh port 2022.<br>
221: updated every 3 hours.<br>
1.80 beck 222:
223: <li><strong>CVSROOT=anoncvs@exokernel.lcs.mit.edu:/cvs</strong><br>
224: located at M.I.T, Eastern USA.<br>
225: maintained by ????<br>
226: protocols: ssh, ???<br>
227: updated every ? hours.<br>
228:
229: <li><strong>CVSROOT=anoncvs@xyzzy.gsnig.net:/cvs</strong><br>
230: Located in Goteborg, Sweden<br>
231: maintained by martin@openbsd.org<br>
232: protocols: ssh, ???<br>
233: updated every ? hours.<br>
234:
235: <li><strong>CVSROOT=anoncvs@stl-isaas.ey.com:/cvs</strong><br>
1.81 beck 236: Located in the St. Louis, MO, Eastern USA<br>
237: maintained by <A HREF="mailto:aaron11@sprynet.com">Aaron Miller</A><br>
238: protocols: ssh, ssh port 2022, pserver<br>
239: updated every 3 hours.<br>
1.80 beck 240:
241: <li><strong>CVSROOT=anoncvs@headend-vlan1-cm19.fibertel.com.ar:/cvs</strong><br>
242: Located in Buenos Aires, Argentina<br>
243: maintained by ????<br>
244: protocols: ssh?, ???<br>
245: updated every ? hours.<br>
1.73 deraadt 246: </ul>
247: <p>
1.80 beck 248: <EM>Note:</EM>, If your server is listed on here with inaccurate or
249: unknown information, please contact <A
250: HREF="mailto:beck@openbsd.org"><tt>beck@openbsd.org></tt></A>
251: <p>
1.1 deraadt 252: You may want to use `traceroute' to find out which server is nearest you.
1.11 michaels 253: Problems with a server should be reported to the <b>maintainer</b> of the
254: server in question.
1.1 deraadt 255: </dl>
256: <p>
257: <strong>IMPORTANT NOTE:</strong>
258: There are a few issues relating to cryptographic software that everyone
259: should be aware of:
260: <ul>
261: <li>The OpenBSD sources are from Canada.
1.9 deraadt 262: As
263: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>
264: researched by a Canadian individual</a>
265: and as
266: <a href=http://axion.physics.ubc.ca/ECL.html>
267: described in the Export Control list of Canada</a>
268: is legal to export crypto software from Canada to the world.
1.1 deraadt 269: <p>
270: <li>However, if you are outside the USA or Canada, you should not
271: fetch the cryptographic sections of the OpenBSD sources from an
272: anoncvs server located in the USA. The files in question are...
273: <ul>
274: <li>src/kerberosIV/*
1.57 art 275: <li>src/lib/libdes/*
1.1 deraadt 276: <li>src/lib/libc/crypt/crypt.c
277: <li>src/lib/libc/crypt/morecrypt.c
1.36 deraadt 278: <li>src/sys/netinet
1.67 art 279: <li>src/usr.sbin/afs/src/rxkad/*
1.56 matthieu 280: <li>X11/xc/lib/Xdmcp/Wraphelp.c
1.1 deraadt 281: </ul>
282: Because of the USA ITAR munitions list,
283: crypto software may only be exported to Canada from the USA.
284: <p>
285: <li>The OpenBSD project is looking for more anoncvs servers -- read
286: on to find out how you can help.
287: </ul>
288:
289: <p>
290: A sample use of an anoncvs CVS server would be:
1.27 todd 291: <ul>
1.1 deraadt 292: <pre>
1.59 beck 293: % setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs
1.1 deraadt 294: % cd /tmp
295: % cvs get src/sys/arch/sparc
1.12 grr 296: [copies the files from the repository to your machine]
1.1 deraadt 297: % cvs log src/sys/arch/sparc/sparc/locore.s
1.12 grr 298: [shows the commit log for the chosen file ]
1.1 deraadt 299: % cvs diff -bc -r1.1 -r1.5 src/sys/arch/sparc/sparc/locore.s
1.12 grr 300: [shows the changes between revisions 1.1 and rev 1.5]
1.1 deraadt 301: </pre>
1.27 todd 302: </ul>
1.1 deraadt 303:
304: <p>
1.18 todd 305: <a name=pserver>In order to use a cvs ``pserver'' (a direct tcp connection instead of using ssh or rsh) you must login once:</a>
306: <pre>
307: [ *NOTE* You must be using cvs version 1.8 or higher to do this ]
1.59 beck 308: % setenv CVSROOT :pserver:anoncvs@anoncvs.ca.openbsd.org:/cvs
1.18 todd 309: % cvs login
1.59 beck 310: (Logging in to anoncvs@anoncvs1.ca.openbsd.org)
1.71 millert 311: CVS password: anoncvs
1.18 todd 312: [this writes a line to ~/.cvspass (filename over-ridden by CVS_PASSFILE).]
313: [An example line from my ~/.cvspass after typing 'blah' for the above ]
314: [password is: ]
315: [:pserver:anoncvs@anoncvs5.usa.openbsd.org:/cvs Au'yc ]
316: [...after logging in ONCE every other use of the above CVSROOT will work ]
317: % cvs -z9 get ksrc-i386 ksrc-common
318: [allows you to retrieve ONLY that necessary to rebuild an i386 kernel ]
319: [ -z9 allows gzip -9 compression, GOOD medicine for slow links ]
320: </pre>
321:
322: <p>
1.39 todd 323: Here is how someone using anoncvs regularly would update his
1.1 deraadt 324: source tree:
1.60 millert 325: <ul><li>First, start out by `get'-ing an initial tree:
1.27 todd 326:
1.1 deraadt 327: <pre>
1.59 beck 328: # setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs
1.1 deraadt 329: # cd /usr
330: # cvs -q get -PA src
331: </pre>
1.27 todd 332: </li>
1.37 todd 333:
1.27 todd 334: <li> Anytime afterwards, to `update' this tree:
1.1 deraadt 335: <pre>
1.41 deraadt 336: # cd /usr/src
337: # cvs -q up -PAd
1.1 deraadt 338: </pre>
1.27 todd 339:
1.39 todd 340: Everytime you ran this it would synchronize your /usr/src tree. It would
1.1 deraadt 341: not destroy any of your local changes, rather it would attempt to merge
342: changes in. If you use obj directories (not obj symbolic links) you may
343: wish to append "-I obj" to the cvs command line, this will keep cvs from
344: spitting out a warning about all the obj directories it is going to
345: encounter which are not in the repository.
1.72 millert 346:
347: <p>
348: <li> NOTE: if you are updating a source tree that you initially fetched
349: from a different server, or from a CD, you <strong>must</strong>
350: add the <em>-d $CVSROOT</em> options to cvs. You must also set the
351: <em>CVS_IGNORE_REMOTE_ROOT</em> environment variable.
352:
353: <pre>
354: # cd /usr/src
355: # cvs -d $CVSROOT -q up -PAd
356: </pre>
357:
1.27 todd 358: </li>
359: </ul>
360:
1.37 todd 361: <p>
362: To <a name=ports>use</a> <a href=ports.html>ports</a>, it is similar to src:
363: <ul><li>
364: <pre>
1.59 beck 365: # setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs
1.37 todd 366: # cd /usr
367: # cvs -q get -PA ports
1.38 deraadt 368: </pre>
1.37 todd 369: </li>
370: <li> Anytime afterwards, to `update' this tree:
371: <pre>
372: # cd /usr
373: # cvs -q up -PAd ports
374: </pre>
375: </li>
376: </p>
377: </ul>
378:
1.27 todd 379: In the above example, '-q' is optional, only intended to minimize
380: cvs's output. For those who like to see screenfulls of output, it
381: can be omitted.
1.1 deraadt 382:
383: <p>
1.12 grr 384: or to make a diff of a locally patched module (here cd.c) to include with
385: a bug report:
386: <pre>
387: # cd /usr
388: # cvs diff -u src/sys/scsi/cd.c > /tmp/patch
389: </pre>
1.37 todd 390: </p>
1.12 grr 391:
392: <p>
1.1 deraadt 393: The CVS man page (included with the CVS sources) has much more
394: information about how CVS can be used.
395:
396: <p>
1.12 grr 397: <strong>Warning:</strong>
398: When using cvs you should take care that your current directory is either
399: the root of the tree you're referencing or in a separate place such as /tmp.
400: Some commands such as "get" can create an arbitrary sub-tree in the current
401: directory, and a subsequent update will recursively flesh out this sub-tree.
402:
403: <p>
1.1 deraadt 404: The anoncvs service gives fledgling developers a chance to learn CVS
405: operation and get thoroughly involved in the development process
406: before getting "commit" access -- as a result of showing useful
407: skills and high quality results they will naturally later be given
408: developer access. As well, people providing patches can create
409: their "diff"s relative to the CVS tree, which will ease integration.
410:
411: <p>
1.15 grr 412: <strong>Anoncvs: rsh vs. ssh</strong>
1.12 grr 413: <br>
414: By default, the CVS client uses rsh to talk to the CVS server. Many
1.39 todd 415: of the CVS sites no longer support rsh for security reasons or a local
1.12 grr 416: problem like a firewall or imperfect protocol emulator such as slirp
417: may prevent you from using rsh.
418: The alternative is a to use a "secure shell" connection using
1.48 ryker 419: <a href=http://www.cs.hut.fi/ssh/>ssh</a>. This is a commercial product
1.12 grr 420: offered by <a href=http://www.ssh.fi>SSH Communications Security Ltd</a>,
421: however they make a free unix version available that can be easily
1.68 wvdputte 422: installed under OpenBSD. Make sure you read the LICENSING doc! If you have
423: installed the OpenBSD <A HREF="ports.html">ports tree</A> you can download,
424: compile, and install the free UNIX version just by changing directory into the
425: directory /usr/ports/security/ssh and typing <KBD>make install</KBD>.
426: If you installed "ports" from the OpenBSD 2.4 CD-ROM, you get ssh
427: version 1.2.26 and should eventually "cvs update ports" and rebuild it as above
1.49 ian 428: after you get ssh and anoncvs working, to get the latest version.
1.68 wvdputte 429: Alternately, you can manually download the latest 1.2.* Unix version from
430: <a href= "ftp://ftp.funet.fi/pub/unix/security/login/ssh/">
431: ftp://ftp.funet.fi/pub/unix/security/login/ssh/</a> or
432: <a href= "http://www.datafellows.com/f-secure/fnetsys.htm">
433: http://www.datafellows.com/f-secure/fnetsys.htm</a>,
434: compile, and install it yourself.
435:
436: <p>
437: The OpenBSD anoncvs repositries support the SSH1 protocol, not the SSH2 protocol
438: due to the use of a "strict non-commercial use licensing policy".
1.28 beck 439:
1.75 millert 440: <p>
441: Once ssh is installed, one sets the environment variable
1.28 beck 442: <strong>CVS_RSH</strong> to point to ssh (typically
443: <strong>/usr/local/bin/ssh</strong>). If your local site prevents you
444: from connecting out to port 22 (which ssh defaults to using) use port
445: 2022.
1.1 deraadt 446:
447: <p>
448: Do not be tempted to turn on compression since CVS already compresses.
449: Use something like the following in your <strong>$HOME/.ssh/config</strong>
1.10 millert 450: file. Note that not all anoncvs servers allow ssh connections on
1.21 millert 451: port 2022. Also note that most anoncvs servers no longer accept
452: the <strong>none</strong> cipher as it is disabled in recent
453: versions of ssh for security reasons.
1.1 deraadt 454: <pre>
1.59 beck 455: Host anoncvs.ca.openbsd.org
1.1 deraadt 456: Port 2022
457: </pre>
458:
459: <p>
460: CVS is a little noisy starting up; to quiet it a bit you may want to
461: do this:
462: <pre>
463: setenv CVS_CLIENT_PORT -1
464: </pre>
465:
466: <p>
1.8 deraadt 467: If you wish to change from one CVS server to another (say your normal one is
468: down, or for any other reason), the environment variable which will let you
469: do this is
470: <pre>
471: setenv CVS_IGNORE_REMOTE_ROOT
472: </pre>
1.72 millert 473: Note that you will also need to use the <strong>-d</strong> flag
474: as mentioned above.
1.8 deraadt 475:
1.65 matthieu 476: <p><strong>X11 Source tree</strong>
477: <br>
478: Anoncvs mirrors also carry the OpenBSD X11 source tree. You can adapt
479: the recipe above to update your X11 source tree from the second CD.
480: Either copy or use a union mount to get the X11 sources in /usr/X11:
481: <ul>
482: <li>copy the tree off it (assuming the 2nd CD is mounted on /mnt):
483: <pre>
484: <b>#</b> cd /mnt; cp -Rp X11 /usr
485: </pre>
486: <li>use a union mount with the CD below a writable directory.
487: <pre>
488: <b>#</b> mount -t union -o -b /mnt/X11 /usr/X11
489: </pre>
490: </ul>
491: After this, /usr/X11 will be ready to be used by cvs. You can for
492: example update it to -current source (assuming you've already set
493: the <b>CVSROOT</b> environment variable):
494: <pre>
495: <b>#</b> cd /usr/X11
496: <b>#</b> cvs -q update -PAd
497: </pre>
498:
499: <p><strong>Setting up a new anoncvs mirror</strong>
500: <br>
1.1 deraadt 501: If you wish to be a new anoncvs mirror site, please contact the anoncvs
502: <a href=mailto:deraadt@theos.com>maintainer</a>.
1.30 beck 503: Anoncvs mirrors require about 500MB of disk, and use up to 4MB of swap
1.1 deraadt 504: per anoncvs user (assuming the user does a large operation; while smaller
505: operations use fewer resources, anoncvs still makes much more of an
506: impact than ftp or sup). Such anoncvs machines should have excellent
507: network connectivity for the area they are expected to serve. A
508: <a href=anoncvs.shar>document</a>
509: which describes the setup of anoncvs servers is available.
510:
1.60 millert 511: <h3><font color=#0000e0>Final notes:</font></h3>
512: After upgrading your source tree, you should read the comments
513: at the top of <KBD>/usr/src/Makefile</KBD> before attemping
514: a build. Also, you should build a new kernel <strong>before</strong>
515: doing a <KBD>make build</KBD> if possible. In some cases it make be
516: necessary to rebuild and install the <KBD>config</KBD> utility before
517: you can build the kernel. If <KBD>config GENERIC</KBD> fails this
518: is probably the case.
519: <p>
520: It is important to note that upgrading from a release to the current tree
521: by rebuilding the sources can be rather difficult due to dependencies
522: that are often not obvious. Therefore, it is suggested that you first
523: install the latest snapshot before attemping a tree build from source.
1.1 deraadt 524:
525: <hr>
1.58 pauls 526: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.1 deraadt 527: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.83 ! millert 528: <br><small>$OpenBSD: anoncvs.html,v 1.82 1999/04/25 19:49:43 millert Exp $</small>
1.1 deraadt 529:
530: </body>
531: </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