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