Annotation of www/anoncvs.html, Revision 1.73
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>
139: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
1.10 millert 140: Host also known as <strong>anoncvs.openbsd.org</strong>,
141: <strong>anoncvs@anoncvs1.usa.openbsd.org</strong>,
142: <strong>anoncvs@anoncvs4.usa.openbsd.org</strong> and
143: <strong>anoncvs2.isc.org</strong>.<br>
144: located in California, western USA.<br>
1.46 millert 145: maintained by <a href=mailto:millert@openbsd.org>Todd Miller</a>.<br>
1.10 millert 146: protocols: ssh only.<br>
1.1 deraadt 147: updated every 4 hours.<br>
1.66 millert 148: Currently DOWN!<br>
1.1 deraadt 149: <p>
150: <li><strong>CVSROOT=anoncvs@anoncvs3.usa.openbsd.org:/cvs</strong><br>
1.55 millert 151: Host also known as <strong>openbsd.cs.colorado.edu</strong>.<br>
1.1 deraadt 152: located at the University of Colorado, Boulder, western USA.<br>
153: maintained by <a href=mailto:Todd.Miller@cs.colorado.edu>Todd Miller</a>.<br>
1.71 millert 154: protocols: ssh, ssh port 2022, pserver.<br>
1.1 deraadt 155: updated every 6 hours.<br>
156: <p>
1.31 deraadt 157: <li><strong>CVSROOT=anoncvs@anoncvs6.usa.openbsd.org:/cvs</strong><br>
158: Host also known as <strong>openbsd.citi.umich.edu</strong>.<br>
159: located at the University of Michigan, central USA.<br>
160: maintained by <a href=mailto:rees@umich.edu>Jim Rees</a>.<br>
161: protocols: ssh, ssh port 2022.<br>
162: updated every 12 hours.<br>
163: <p>
1.24 deraadt 164: <li><strong>CVSROOT=anoncvs@anoncvs1.ca.openbsd.org:/cvs</strong><br>
1.40 beck 165: Host also known as <strong>anoncvs.ca.openbsd.org</strong>,
166: <strong>panopticon.ucs.ualberta.ca</strong><br>
1.24 deraadt 167: located in Edmonton, Alberta, Canada.<br>
168: maintained by <A HREF="mailto:beck@panopticon.ucs.ualberta.ca">Bob Beck</A><br>
1.53 beck 169: protocols: ssh, rsh, ssh port 2022, pserver<br>
1.45 beck 170: updated every 2 hours.<br>
1.24 deraadt 171: <p>
1.1 deraadt 172: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
173: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
174: located in London, UK.<br>
175: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
176: protocols: rsh.<br>
177: updated every 12 hours.<br>
178: <p>
179: <li><strong>CVSROOT=anoncvs@anoncvs.tw.openbsd.org:/cvs</strong><br>
1.64 deraadt 180: Host also known as <strong>OpenBSD.csie.NCTU.edu.tw</strong>.<br>
1.1 deraadt 181: located in Taipei, Taiwan.<br>
1.63 deraadt 182: maintained by <a href=mailto:lkchu@OpenBSD.csie.NCTU.edu.tw>Liang-Kai Chu</a>.<br>
1.1 deraadt 183: protocols: rsh, ssh, ssh port 2022.<br>
184: updated every 12 hours.<br>
185: <p>
186: <li><strong>CVSROOT=anoncvs@anoncvs.no.openbsd.org:/cvs</strong><br>
1.64 deraadt 187: Host also known as <strong>cvs.inet.no</strong>.<br>
1.1 deraadt 188: located in Norway.<br>
1.64 deraadt 189: maintained by <a href=mailto:cvsadmin@inet.no>Michael Shuldman</a>.<br>
1.1 deraadt 190: protocols: rsh, ssh, ssh port 2022.<br>
191: updated every 4 hours.<br>
192: <p>
1.33 deraadt 193: <li><strong>CVSROOT=anoncvs@anoncvs.se.openbsd.org:/cvs</strong><br>
1.54 art 194: Host also known as <strong>anoncvs.stacken.kth.se</strong>.<br>
1.33 deraadt 195: located in Sweden.<br>
196: maintained by <a href=mailto:anoncvs@stacken.kth.se>Magnus Holmberg</a>.<br>
197: protocols: rsh, ssh, ssh port 2022.<br>
1.57 art 198: updated every 3 hours.<br>
1.68 wvdputte 199: <p>
200: <li><strong>CVSROOT=anoncvs@anoncvs.be.openbsd.org:/cvs</strong><br>
201: Host also known as <strong>badlands.rug.ac.be</strong>.<br>
202: located in Belgium.<br>
203: maintained by <a href=mailto:wvdputte@reptile.rug.ac.be>Wim Vandeputte</a>.<br>
204: protocols: ssh, ssh port 2022.<br>
205: updated every 3 hours.<br>
1.69 deraadt 206: <p>
207: <li><strong>CVSROOT=anoncvs@anoncvs.jp.openbsd.org:/cvs</strong><br>
208: Host also known as <strong>kankoromochi.econ.nagasaki-u.ac.jp</strong>.<br>
209: located at Nagasaki Univ. Faculty of Economics, JAPAN.<br>
210: maintained by <a href=mailto:sigh@net.nagasaki-u.ac.jp>SUZUKI Hitoshi</a>.<br>
211: protocols: ssh.<br>
212: updated every 12 hours.<br>
1.33 deraadt 213: </ul>
214: <p>
1.73 ! deraadt 215: <li><strong>CVSROOT=anoncvs@anoncvs.cz.openbsd.org:/cvs</strong><br>
! 216: Host also known as <strong>com-os2.ms.mff.cuni.cz</strong>.<br>
! 217: located at Faculty Math & Physics, Charles University, Prague, Czech republic.<br>
! 218: maintained by <a href=mailto:galambos@com-os2.ms.mff.cuni.cz>Leo Galambos</a>.<br>
! 219: protocols: ssh, ssh port 2022.<br>
! 220: updated every 3 hours.<br>
! 221: </ul>
! 222: <p>
1.1 deraadt 223: You may want to use `traceroute' to find out which server is nearest you.
1.11 michaels 224: Problems with a server should be reported to the <b>maintainer</b> of the
225: server in question.
1.1 deraadt 226: </dl>
227: <p>
228: <strong>IMPORTANT NOTE:</strong>
229: There are a few issues relating to cryptographic software that everyone
230: should be aware of:
231: <ul>
232: <li>The OpenBSD sources are from Canada.
1.9 deraadt 233: As
234: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>
235: researched by a Canadian individual</a>
236: and as
237: <a href=http://axion.physics.ubc.ca/ECL.html>
238: described in the Export Control list of Canada</a>
239: is legal to export crypto software from Canada to the world.
1.1 deraadt 240: <p>
241: <li>However, if you are outside the USA or Canada, you should not
242: fetch the cryptographic sections of the OpenBSD sources from an
243: anoncvs server located in the USA. The files in question are...
244: <ul>
245: <li>src/kerberosIV/*
1.57 art 246: <li>src/lib/libdes/*
1.1 deraadt 247: <li>src/lib/libc/crypt/crypt.c
248: <li>src/lib/libc/crypt/morecrypt.c
1.36 deraadt 249: <li>src/sys/netinet
1.67 art 250: <li>src/usr.sbin/afs/src/rxkad/*
1.56 matthieu 251: <li>X11/xc/lib/Xdmcp/Wraphelp.c
1.1 deraadt 252: </ul>
253: Because of the USA ITAR munitions list,
254: crypto software may only be exported to Canada from the USA.
255: <p>
256: <li>The OpenBSD project is looking for more anoncvs servers -- read
257: on to find out how you can help.
258: </ul>
259:
260: <p>
261: A sample use of an anoncvs CVS server would be:
1.27 todd 262: <ul>
1.1 deraadt 263: <pre>
1.59 beck 264: % setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs
1.1 deraadt 265: % cd /tmp
266: % cvs get src/sys/arch/sparc
1.12 grr 267: [copies the files from the repository to your machine]
1.1 deraadt 268: % cvs log src/sys/arch/sparc/sparc/locore.s
1.12 grr 269: [shows the commit log for the chosen file ]
1.1 deraadt 270: % cvs diff -bc -r1.1 -r1.5 src/sys/arch/sparc/sparc/locore.s
1.12 grr 271: [shows the changes between revisions 1.1 and rev 1.5]
1.1 deraadt 272: </pre>
1.27 todd 273: </ul>
1.1 deraadt 274:
275: <p>
1.18 todd 276: <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>
277: <pre>
278: [ *NOTE* You must be using cvs version 1.8 or higher to do this ]
1.59 beck 279: % setenv CVSROOT :pserver:anoncvs@anoncvs.ca.openbsd.org:/cvs
1.18 todd 280: % cvs login
1.59 beck 281: (Logging in to anoncvs@anoncvs1.ca.openbsd.org)
1.71 millert 282: CVS password: anoncvs
1.18 todd 283: [this writes a line to ~/.cvspass (filename over-ridden by CVS_PASSFILE).]
284: [An example line from my ~/.cvspass after typing 'blah' for the above ]
285: [password is: ]
286: [:pserver:anoncvs@anoncvs5.usa.openbsd.org:/cvs Au'yc ]
287: [...after logging in ONCE every other use of the above CVSROOT will work ]
288: % cvs -z9 get ksrc-i386 ksrc-common
289: [allows you to retrieve ONLY that necessary to rebuild an i386 kernel ]
290: [ -z9 allows gzip -9 compression, GOOD medicine for slow links ]
291: </pre>
292:
293: <p>
1.39 todd 294: Here is how someone using anoncvs regularly would update his
1.1 deraadt 295: source tree:
1.60 millert 296: <ul><li>First, start out by `get'-ing an initial tree:
1.27 todd 297:
1.1 deraadt 298: <pre>
1.59 beck 299: # setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs
1.1 deraadt 300: # cd /usr
301: # cvs -q get -PA src
302: </pre>
1.27 todd 303: </li>
1.37 todd 304:
1.27 todd 305: <li> Anytime afterwards, to `update' this tree:
1.1 deraadt 306: <pre>
1.41 deraadt 307: # cd /usr/src
308: # cvs -q up -PAd
1.1 deraadt 309: </pre>
1.27 todd 310:
1.39 todd 311: Everytime you ran this it would synchronize your /usr/src tree. It would
1.1 deraadt 312: not destroy any of your local changes, rather it would attempt to merge
313: changes in. If you use obj directories (not obj symbolic links) you may
314: wish to append "-I obj" to the cvs command line, this will keep cvs from
315: spitting out a warning about all the obj directories it is going to
316: encounter which are not in the repository.
1.72 millert 317:
318: <p>
319: <li> NOTE: if you are updating a source tree that you initially fetched
320: from a different server, or from a CD, you <strong>must</strong>
321: add the <em>-d $CVSROOT</em> options to cvs. You must also set the
322: <em>CVS_IGNORE_REMOTE_ROOT</em> environment variable.
323:
324: <pre>
325: # cd /usr/src
326: # cvs -d $CVSROOT -q up -PAd
327: </pre>
328:
1.27 todd 329: </li>
330: </ul>
331:
1.37 todd 332: <p>
333: To <a name=ports>use</a> <a href=ports.html>ports</a>, it is similar to src:
334: <ul><li>
335: <pre>
1.59 beck 336: # setenv CVSROOT anoncvs@anoncvs.ca.openbsd.org:/cvs
1.37 todd 337: # cd /usr
338: # cvs -q get -PA ports
1.38 deraadt 339: </pre>
1.37 todd 340: </li>
341: <li> Anytime afterwards, to `update' this tree:
342: <pre>
343: # cd /usr
344: # cvs -q up -PAd ports
345: </pre>
346: </li>
347: </p>
348: </ul>
349:
1.27 todd 350: In the above example, '-q' is optional, only intended to minimize
351: cvs's output. For those who like to see screenfulls of output, it
352: can be omitted.
1.1 deraadt 353:
354: <p>
1.12 grr 355: or to make a diff of a locally patched module (here cd.c) to include with
356: a bug report:
357: <pre>
358: # cd /usr
359: # cvs diff -u src/sys/scsi/cd.c > /tmp/patch
360: </pre>
1.37 todd 361: </p>
1.12 grr 362:
363: <p>
1.1 deraadt 364: The CVS man page (included with the CVS sources) has much more
365: information about how CVS can be used.
366:
367: <p>
1.12 grr 368: <strong>Warning:</strong>
369: When using cvs you should take care that your current directory is either
370: the root of the tree you're referencing or in a separate place such as /tmp.
371: Some commands such as "get" can create an arbitrary sub-tree in the current
372: directory, and a subsequent update will recursively flesh out this sub-tree.
373:
374: <p>
1.1 deraadt 375: The anoncvs service gives fledgling developers a chance to learn CVS
376: operation and get thoroughly involved in the development process
377: before getting "commit" access -- as a result of showing useful
378: skills and high quality results they will naturally later be given
379: developer access. As well, people providing patches can create
380: their "diff"s relative to the CVS tree, which will ease integration.
381:
382: <p>
1.15 grr 383: <strong>Anoncvs: rsh vs. ssh</strong>
1.12 grr 384: <br>
385: By default, the CVS client uses rsh to talk to the CVS server. Many
1.39 todd 386: of the CVS sites no longer support rsh for security reasons or a local
1.12 grr 387: problem like a firewall or imperfect protocol emulator such as slirp
388: may prevent you from using rsh.
389: The alternative is a to use a "secure shell" connection using
1.48 ryker 390: <a href=http://www.cs.hut.fi/ssh/>ssh</a>. This is a commercial product
1.12 grr 391: offered by <a href=http://www.ssh.fi>SSH Communications Security Ltd</a>,
392: however they make a free unix version available that can be easily
1.68 wvdputte 393: installed under OpenBSD. Make sure you read the LICENSING doc! If you have
394: installed the OpenBSD <A HREF="ports.html">ports tree</A> you can download,
395: compile, and install the free UNIX version just by changing directory into the
396: directory /usr/ports/security/ssh and typing <KBD>make install</KBD>.
397: If you installed "ports" from the OpenBSD 2.4 CD-ROM, you get ssh
398: version 1.2.26 and should eventually "cvs update ports" and rebuild it as above
1.49 ian 399: after you get ssh and anoncvs working, to get the latest version.
1.68 wvdputte 400: Alternately, you can manually download the latest 1.2.* Unix version from
401: <a href= "ftp://ftp.funet.fi/pub/unix/security/login/ssh/">
402: ftp://ftp.funet.fi/pub/unix/security/login/ssh/</a> or
403: <a href= "http://www.datafellows.com/f-secure/fnetsys.htm">
404: http://www.datafellows.com/f-secure/fnetsys.htm</a>,
405: compile, and install it yourself.
406:
407: <p>
408: The OpenBSD anoncvs repositries support the SSH1 protocol, not the SSH2 protocol
409: due to the use of a "strict non-commercial use licensing policy".
1.28 beck 410:
1.50 ian 411: <p> One ssh is installed, one sets the environment variable
1.28 beck 412: <strong>CVS_RSH</strong> to point to ssh (typically
413: <strong>/usr/local/bin/ssh</strong>). If your local site prevents you
414: from connecting out to port 22 (which ssh defaults to using) use port
415: 2022.
1.1 deraadt 416:
417: <p>
418: Do not be tempted to turn on compression since CVS already compresses.
419: Use something like the following in your <strong>$HOME/.ssh/config</strong>
1.10 millert 420: file. Note that not all anoncvs servers allow ssh connections on
1.21 millert 421: port 2022. Also note that most anoncvs servers no longer accept
422: the <strong>none</strong> cipher as it is disabled in recent
423: versions of ssh for security reasons.
1.1 deraadt 424: <pre>
1.59 beck 425: Host anoncvs.ca.openbsd.org
1.1 deraadt 426: Port 2022
427: </pre>
428:
429: <p>
430: CVS is a little noisy starting up; to quiet it a bit you may want to
431: do this:
432: <pre>
433: setenv CVS_CLIENT_PORT -1
434: </pre>
435:
436: <p>
1.8 deraadt 437: If you wish to change from one CVS server to another (say your normal one is
438: down, or for any other reason), the environment variable which will let you
439: do this is
440: <pre>
441: setenv CVS_IGNORE_REMOTE_ROOT
442: </pre>
1.72 millert 443: Note that you will also need to use the <strong>-d</strong> flag
444: as mentioned above.
1.8 deraadt 445:
1.65 matthieu 446: <p><strong>X11 Source tree</strong>
447: <br>
448: Anoncvs mirrors also carry the OpenBSD X11 source tree. You can adapt
449: the recipe above to update your X11 source tree from the second CD.
450: Either copy or use a union mount to get the X11 sources in /usr/X11:
451: <ul>
452: <li>copy the tree off it (assuming the 2nd CD is mounted on /mnt):
453: <pre>
454: <b>#</b> cd /mnt; cp -Rp X11 /usr
455: </pre>
456: <li>use a union mount with the CD below a writable directory.
457: <pre>
458: <b>#</b> mount -t union -o -b /mnt/X11 /usr/X11
459: </pre>
460: </ul>
461: After this, /usr/X11 will be ready to be used by cvs. You can for
462: example update it to -current source (assuming you've already set
463: the <b>CVSROOT</b> environment variable):
464: <pre>
465: <b>#</b> cd /usr/X11
466: <b>#</b> cvs -q update -PAd
467: </pre>
468:
469: <p><strong>Setting up a new anoncvs mirror</strong>
470: <br>
1.1 deraadt 471: If you wish to be a new anoncvs mirror site, please contact the anoncvs
472: <a href=mailto:deraadt@theos.com>maintainer</a>.
1.30 beck 473: Anoncvs mirrors require about 500MB of disk, and use up to 4MB of swap
1.1 deraadt 474: per anoncvs user (assuming the user does a large operation; while smaller
475: operations use fewer resources, anoncvs still makes much more of an
476: impact than ftp or sup). Such anoncvs machines should have excellent
477: network connectivity for the area they are expected to serve. A
478: <a href=anoncvs.shar>document</a>
479: which describes the setup of anoncvs servers is available.
480:
1.60 millert 481: <h3><font color=#0000e0>Final notes:</font></h3>
482: After upgrading your source tree, you should read the comments
483: at the top of <KBD>/usr/src/Makefile</KBD> before attemping
484: a build. Also, you should build a new kernel <strong>before</strong>
485: doing a <KBD>make build</KBD> if possible. In some cases it make be
486: necessary to rebuild and install the <KBD>config</KBD> utility before
487: you can build the kernel. If <KBD>config GENERIC</KBD> fails this
488: is probably the case.
489: <p>
490: It is important to note that upgrading from a release to the current tree
491: by rebuilding the sources can be rather difficult due to dependencies
492: that are often not obvious. Therefore, it is suggested that you first
493: install the latest snapshot before attemping a tree build from source.
1.1 deraadt 494:
495: <hr>
1.58 pauls 496: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.1 deraadt 497: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.73 ! deraadt 498: <br><small>$OpenBSD: anoncvs.html,v 1.72 1998/12/03 04:17:56 millert Exp $</small>
1.1 deraadt 499:
500: </body>
501: </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