Annotation of www/anoncvs.html, Revision 1.14
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
1.2 deraadt 4: <title>OpenBSD AnonCVS</title>
1.1 deraadt 5: <link rev=made href=mailto:www@openbsd.org>
6: <meta name="resource-type" content="document">
7: <meta name="description" content="the main OpenBSD page">
8: <meta name="keywords" content="openbsd,main">
9: <meta name="distribution" content="global">
1.13 deraadt 10: <meta name="copyright" content="This document copyright 1996 by OpenBSD.">
1.1 deraadt 11: </head>
12:
1.14 ! downsj 13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
1.1 deraadt 14:
1.14 ! downsj 15: <img alt="[OpenBSD]" SRC="images/smalltitle.gif">
! 16:
! 17: <p>
1.1 deraadt 18: <h3>CVS Access:</h3>
19: CVS is used to manage the OpenBSD source tree. This allows
20: developers to work on a local source tree and commit their changes when
21: ready. Also <strong>anyone</strong> can edit source files on their
22: local machines, and automatically track and merge in any changes made
23: in the OpenBSD CVS repository. Additionally they can easily see the
24: logs of, check out, or "diff" the source files in the OpenBSD source
25: tree.
26: </p>
27:
28: <p>
29: Most importantly, the <strong>anoncvs</strong> service does NOT
30: delete the changes you make in your local copy of the source tree --
31: read on for more details!
32: </p>
33:
34: <p>
35: The latest version of CVS is available at
36: <a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>.
37: Versions earlier than 1.6 are not recommended, and may not work.
38: If you already have OpenBSD installed, CVS is included.
39: </p>
40:
41: <p>
42: There are two levels of source tree access:
43: </p>
44:
45: <dl>
46: <dt><strong>Read-write access for developers:</strong>
47: <dd>Developers who need to commit changes to the source tree must have
48: an account on the OpenBSD machines. Getting this access will be a
49: natural result of working on the sources with other OpenBSD developers.
50: If someone does some good work and shows they can work with the team,
51: they will get an account.
52: </dl>
53:
54: <dl>
55: <dt><strong>Read-only access for everyone:</strong>
56: <dd>Anyone can access the read-only CVS repositories. These copies
57: of the read-write CVS repository are mirrored often. To use one,
58: set your <strong>CVSROOT</strong> environment variable to one of
59: the following values:
1.12 grr 60: <p>
61: <strong>Please see the note about using ssh vs. rsh below!</strong>
62: <p>
1.1 deraadt 63: <ul>
64: <p>
65: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
1.10 millert 66: Host also known as <strong>anoncvs.openbsd.org</strong>,
67: <strong>anoncvs@anoncvs1.usa.openbsd.org</strong>,
68: <strong>anoncvs@anoncvs4.usa.openbsd.org</strong> and
69: <strong>anoncvs2.isc.org</strong>.<br>
70: located in California, western USA.<br>
71: maintained by <a href=mailto:niklas@openbsd.org>Niklas Hallqvist</a>.<br>
72: protocols: ssh only.<br>
1.1 deraadt 73: updated every 4 hours.<br>
74: <p>
75: <li><strong>CVSROOT=anoncvs@anoncvs2.usa.openbsd.org:/cvs</strong><br>
1.5 johns 76: Host also known as <strong>hydra.heuris.com</strong>.<br>
1.4 deraadt 77: located in St. Louis, Missouri, mid-western USA.<br>
1.1 deraadt 78: maintained by <a href=mailto:johns@heuris.com>John Stone</a>.<br>
79: protocols: rsh, ssh, ssh port 2022.<br>
80: updated every 12 hours.<br>
81: <p>
82: <li><strong>CVSROOT=anoncvs@anoncvs3.usa.openbsd.org:/cvs</strong><br>
83: Host also known as <strong>freestuff.cs.colorado.edu</strong>.<br>
84: located at the University of Colorado, Boulder, western USA.<br>
85: maintained by <a href=mailto:Todd.Miller@cs.colorado.edu>Todd Miller</a>.<br>
86: protocols: ssh, ssh port 2022.<br>
87: updated every 6 hours.<br>
88: <p>
89: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
90: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
91: located in London, UK.<br>
92: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
93: protocols: rsh.<br>
94: updated every 12 hours.<br>
95: <p>
96: <li><strong>CVSROOT=anoncvs@anoncvs.tw.openbsd.org:/cvs</strong><br>
97: Host also known as <strong>hercules.secc.fju.edu.tw</strong>.<br>
98: located in Taipei, Taiwan.<br>
99: maintained by <a href=mailto:shawn@openbsd.org>Shawn Hsiao</a>.<br>
100: protocols: rsh, ssh, ssh port 2022.<br>
101: updated every 12 hours.<br>
102: <p>
103: <li><strong>CVSROOT=anoncvs@anoncvs.no.openbsd.org:/cvs</strong><br>
104: located in Norway.<br>
105: maintained by <a href=mailto:micheals@openbsd.org>Michael Shuldman</a>.<br>
106: protocols: rsh, ssh, ssh port 2022.<br>
107: updated every 4 hours.<br>
108: </ul>
109: <p>
110: You may want to use `traceroute' to find out which server is nearest you.
1.11 michaels 111: Problems with a server should be reported to the <b>maintainer</b> of the
112: server in question.
1.1 deraadt 113: </dl>
114: </p>
115: <p>
116: <strong>IMPORTANT NOTE:</strong>
117: There are a few issues relating to cryptographic software that everyone
118: should be aware of:
119: <ul>
120: <li>The OpenBSD sources are from Canada.
1.9 deraadt 121: As
122: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>
123: researched by a Canadian individual</a>
124: and as
125: <a href=http://axion.physics.ubc.ca/ECL.html>
126: described in the Export Control list of Canada</a>
127: is legal to export crypto software from Canada to the world.
1.1 deraadt 128: <p>
129: <li>However, if you are outside the USA or Canada, you should not
130: fetch the cryptographic sections of the OpenBSD sources from an
131: anoncvs server located in the USA. The files in question are...
132: <ul>
133: <li>src/kerberosIV/*
134: <li>src/lib/libc/crypt/crypt.c
135: <li>src/lib/libc/crypt/morecrypt.c
136: </ul>
137: Because of the USA ITAR munitions list,
138: crypto software may only be exported to Canada from the USA.
139: <p>
140: <li>The OpenBSD project is looking for more anoncvs servers -- read
141: on to find out how you can help.
142: </ul>
143: </p>
144:
145: <p>
146: A sample use of an anoncvs CVS server would be:
147: <pre>
148: % setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
149: % cd /tmp
150: % cvs get src/sys/arch/sparc
1.12 grr 151: [copies the files from the repository to your machine]
1.1 deraadt 152: % cvs log src/sys/arch/sparc/sparc/locore.s
1.12 grr 153: [shows the commit log for the chosen file ]
1.1 deraadt 154: % cvs diff -bc -r1.1 -r1.5 src/sys/arch/sparc/sparc/locore.s
1.12 grr 155: [shows the changes between revisions 1.1 and rev 1.5]
1.1 deraadt 156: </pre>
157: </p>
158:
159: <p>
160: Here is how someone using anoncvs regularily would update his
161: source tree:
162: <pre>
163: # setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
164: # cd /usr
165: # cvs -q get -PA src
166: </pre>
1.12 grr 167: or similarily later on he might try:
1.1 deraadt 168: <pre>
1.12 grr 169: # cd /usr
170: # cvs -q up -PAd src
1.1 deraadt 171: </pre>
172: Everytime you ran this it would syncronize your /usr/src tree. It would
173: not destroy any of your local changes, rather it would attempt to merge
174: changes in. If you use obj directories (not obj symbolic links) you may
175: wish to append "-I obj" to the cvs command line, this will keep cvs from
176: spitting out a warning about all the obj directories it is going to
177: encounter which are not in the repository.
178: </p>
179:
180: <p>
1.12 grr 181: or to make a diff of a locally patched module (here cd.c) to include with
182: a bug report:
183: <pre>
184: # cd /usr
185: # cvs diff -u src/sys/scsi/cd.c > /tmp/patch
186: </pre>
187: </p>
188:
189: <p>
1.1 deraadt 190: The CVS man page (included with the CVS sources) has much more
191: information about how CVS can be used.
192: </p>
193:
194: <p>
1.12 grr 195: <strong>Warning:</strong>
196: When using cvs you should take care that your current directory is either
197: the root of the tree you're referencing or in a separate place such as /tmp.
198: Some commands such as "get" can create an arbitrary sub-tree in the current
199: directory, and a subsequent update will recursively flesh out this sub-tree.
200: </p>
201:
202: <p>
1.1 deraadt 203: The anoncvs service gives fledgling developers a chance to learn CVS
204: operation and get thoroughly involved in the development process
205: before getting "commit" access -- as a result of showing useful
206: skills and high quality results they will naturally later be given
207: developer access. As well, people providing patches can create
208: their "diff"s relative to the CVS tree, which will ease integration.
209: </p>
210:
211: <p>
1.12 grr 212: <strong>Anoncvs rsh vs. ssh</strong>
213: <br>
214: By default, the CVS client uses rsh to talk to the CVS server. Many
215: of the CVS sites no longer supprt rsh for security reasons or a local
216: problem like a firewall or imperfect protocol emulator such as slirp
217: may prevent you from using rsh.
218: The alternative is a to use a "secure shell" connection using
219: <a href=http://www.cs.hut.fi/ssh>ssh</a>. This is a commerical product
220: offered by <a href=http://www.ssh.fi>SSH Communications Security Ltd</a>,
221: however they make a free unix version available that can be easily
222: installed under OpenBSD. You can download the unix version from
223: <a href=http://www.cs.hut.fi/ssh>http://www.cs.hut.fi/ssh</a> or one of
224: the mirrors listed there.
225: </p>
226: <p>
227: In this case,
1.1 deraadt 228: one sets the environment variable <strong>CVS_RSH</strong> to point
229: to ssh (typically <strong>/usr/local/bin/ssh</strong>). To reduce the
230: performance hit the anoncvs server would take it is recommended (and
231: requested) that you disable encryption. If your local site prevents
232: you from connecting out to port 22 (which ssh defaults to using) use
233: port 2022.
234: </p>
235:
236: <p>
237: Do not be tempted to turn on compression since CVS already compresses.
238: Use something like the following in your <strong>$HOME/.ssh/config</strong>
1.10 millert 239: file. Note that not all anoncvs servers allow ssh connections on
240: port 2022.
1.1 deraadt 241: </p>
242: <pre>
243: Host anoncvs.usa.openbsd.org
244: Cipher none
245: Port 2022
246: </pre>
247:
248: <p>
249: CVS is a little noisy starting up; to quiet it a bit you may want to
250: do this:
251: <pre>
252: setenv CVS_CLIENT_PORT -1
253: </pre>
254: </p>
255:
256: <p>
1.8 deraadt 257: If you wish to change from one CVS server to another (say your normal one is
258: down, or for any other reason), the environment variable which will let you
259: do this is
260: <pre>
261: setenv CVS_IGNORE_REMOTE_ROOT
262: </pre>
263: </p>
264:
265: <p>
1.1 deraadt 266: If you wish to be a new anoncvs mirror site, please contact the anoncvs
267: <a href=mailto:deraadt@theos.com>maintainer</a>.
268: Anoncvs mirrors require about 300MB of disk, and use up to 4MB of swap
269: per anoncvs user (assuming the user does a large operation; while smaller
270: operations use fewer resources, anoncvs still makes much more of an
271: impact than ftp or sup). Such anoncvs machines should have excellent
272: network connectivity for the area they are expected to serve. A
273: <a href=anoncvs.shar>document</a>
274: which describes the setup of anoncvs servers is available.
275: </p>
276:
277: </dl>
278:
279: <hr>
1.3 deraadt 280: <a href=index.html><img src=back.gif border=0 alt=OpenBSD></a>
1.1 deraadt 281: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.14 ! downsj 282: <br><small>$OpenBSD: anoncvs.html,v 1.13 1997/04/30 22:18:01 deraadt Exp $</small>
1.1 deraadt 283:
284: </body>
285: </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