Annotation of www/index.html, Revision 1.73
1.18 fn 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
1.1 deraadt 3: <head>
4: <title>OpenBSD</title>
1.19 fn 5: <base href=http://www.openbsd.org/>
1.18 fn 6: <link rev=made href=mailto:www@openbsd.org>
7: <meta name="resource-type" content="document">
8: <meta name="description" content="the main OpenBSD page">
9: <meta name="keywords" content="openbsd,main">
10: <meta name="distribution" content="global">
11: <meta name="copyright" content="This document copyright 1996 by OpenBSD, Inc.">
1.1 deraadt 12: </head>
1.18 fn 13:
14: <body>
15:
1.31 deraadt 16: <h1>OpenBSD</h1>
17: <br>
1.37 deraadt 18: <img src="head.gif">
1.30 deraadt 19: <br>
20: <small>The picture is Copyright (C) 1996 Shawn Mueller</small>
21: <br>
22: <h1>OpenBSD</h1>
1.1 deraadt 23:
1.18 fn 24: <p>
1.1 deraadt 25: The OpenBSD project involves continuing development of a multiplatform
26: 4.4BSD-based Unix-like operating system.
1.18 fn 27: </p>
1.1 deraadt 28:
29: <p>
1.22 deraadt 30: <ul>
31: <li><a href=#additions>Changes Relative to other *BSD's</a>
32: <li><a href=#curplat>Supported platforms</a>
33: <li><a href=#futplat>New platforms under development</a>
1.50 deraadt 34: <li><a href=#devel>How we help developers and users</a>
1.55 deraadt 35: <li><a href=#snapshots>Binary snapshots</a>
1.48 deraadt 36: <li><a href=#ftp>FTP mirrors</a>
1.50 deraadt 37: <li><a href=#maillist>Mailing Lists</a>
38: <li><a href=#gnats>Bug tracking</a>
39: <li><a href=#sup>Sup</a>
40: <li><a href=#anoncvs>AnonCVS</a>
1.22 deraadt 41: <li><a href=goals.html>OpenBSD project goals</a>
42: </ul>
43: </p>
44:
45: <h3><hr><a name=additions>Changes Relative to other *BSD's.</a></h3>
46:
47: <p>
1.1 deraadt 48: OpenBSD looks a lot like NetBSD (which it is derived from, following
49: the 4.4BSD roots), but is now being developed seperately. Good changes
50: from other free operating systems will be merged in (of course, depending
1.24 deraadt 51: on various factors like developer time for example.) OpenBSD tracks
52: NetBSD changes very closely; say anywhere between 2 days to 10 days
53: behind the state of NetBSD-current all the time. Hence you can truly
54: say that OpenBSD is NetBSD <b>PLUS MORE STUFF</b>.
1.18 fn 55: </p>
1.1 deraadt 56:
57: <p>
1.22 deraadt 58: Various additions have been made. This is only a small partial list of
1.25 deraadt 59: the major machine independent changes (ie. it is the most interesting
60: changes or what people ask about most often). Check the specific port
61: you are interested in for further details of that port -- many of them
62: have been extended too.
1.1 deraadt 63: <ul>
1.35 deraadt 64: <li>Many many NetBSD PR's fixed (which NetBSD has not yet fixed)
1.22 deraadt 65: <li>New curses library, including libform, libpanel and libmenu.
1.25 deraadt 66: <li>a termlib library which understands termcap.db, needed for new curses.
67: <li>The FreeBSD ports subsystem was integrated and is usable by you!
1.22 deraadt 68: <li>ipfilter for filtering dangerous packets
69: <li>better ELF support
1.25 deraadt 70: <li>nlist() that understands ELF, ECOFF, and a.out, allowing non-a.out ports
71: to use kvm utilies
1.22 deraadt 72: <li>Verbatim integration of the GNU tools (using a wrapper Makefile)
73: <li>All the pieces needed for cross compilation are in the source tree.
74: <li>Some LKM support in the tree.
75: <li>ATAPI support (should work on all ISA busses)
1.25 deraadt 76: <li>new scsi, md5, pkg_* commands
1.22 deraadt 77: <li>Numerous security related fixes
1.25 deraadt 78: <li>Kerberos and other crypto in the source tree that is exportable
79: <li>Solid YP master, server, and client capabilities.
1.22 deraadt 80: <li>/dev/rnd -- source of random data
1.23 deraadt 81: <li>In-kernel update(8) with an adaptive algorithm
1.25 deraadt 82: <li>Some ddb improvements and extensions
83: <li>Numerous scsi fixes
1.28 deraadt 84: <li>new system calls: rfork(), minherit(), poll().
85: <li>select() that can handle any amount of file descriptors.
1.29 deraadt 86: <li>kernfs extensions
87: <li>ATM support (support for one company's sparc & i386 cards available)
1.33 deraadt 88: <li>Boot kernels with "-c" to edit/enable/disable device configuration tables
1.38 deraadt 89: <li>pax as tar, gnutar is toast
1.42 deraadt 90: <li>using AT&T awk, gawk is toast
1.38 deraadt 91: <li>Even more security fixes.
1.47 deraadt 92: <li>Accepts FreeBSD MD5 passwords in password maps, soon will be able to
93: generate them too
1.40 deraadt 94: <li>Linux ext2fs and BSD4.4 LFS support being worked on.
1.65 deraadt 95: <li>Working ATAPI audio support for multiple architectures.
1.51 deraadt 96: <li>terminfo database support.
1.53 deraadt 97: <li>Fortran in the tree.
98: <li>The most secure rdist support anywhere.
1.63 deraadt 99: <li>randomized port allocation in bind(), bindresvport(), and rresvport() --
100: security via unpredictability.
1.53 deraadt 101: <li>Protection from the udp spamming and ftp bounce attacks.
102: <li>Significantly improved ftp daemon.
103: <li>Numerous more security policy and implimentation improvements (OpenBSD
104: defaults to installing in a very secure mode)
105: <li>zlib (non-GPL'd gzip-compatible library)
106: <li>Newest version of ppp, vi,
1.54 deraadt 107: <li>_POSIX_SAVED_IDS behaviour with permitted BSD extensions.
1.60 deraadt 108: <li>Fixed long-standing vm swap-leak.
109: <li>FreeBSD malloc() that uses mmap() and is able to free unused memory.
110: <li>Numerous FreeBSD userland fixes and improvements incorporated.
1.62 deraadt 111: <li>new rdisc Router Discovery daemon
1.63 deraadt 112: <li>generic protection against the bind() takeover problem.
113: <li>at -f security fix.
114: <li>install now supports -C, -p, and -S flags.
1.68 deraadt 115: <!-- <li>a real adduser program, which can even be used uninteractively. -->
116: <li>POSIX & C2 requirement; lose setuid/setgid bits if owner/group changed
117: by chown(). This can be turned off with sysctl.
1.66 deraadt 118: <li>partial protection against tcp SYN attacks.
1.67 deraadt 119: <li>added /etc/fbtab support to login & init.
1.72 deraadt 120: <li>RCS version 5.7
121: <li>much newer join command (4.4lite2 with other fixes)
122: <li>scsi subsystem security fix
123: <li>Kerberos is much more silent if not configured
124: <li>arc4-based random support in kernel
125: <li>ncr53cXXX scsi scripts assembler
126: <li>multihomed support in ftpd.
1.73 ! deraadt 127: <li>`lsof'-style features in fstat.
1.1 deraadt 128: </ul>
1.18 fn 129: </p>
1.1 deraadt 130:
1.18 fn 131: <h3><hr><a name=curplat>Platforms currently supported.</a></h3>
1.1 deraadt 132:
1.18 fn 133: <p>
1.1 deraadt 134: Note: for some of these platforms, the platform-independent code may
135: be identical to that found in NetBSD because there isn't a specific
136: OpenBSD developer. For other ports the differences are significant.
137: If you find an empty page that means nothing of consequence that is
138: directly port-specific has changed from NetBSD. (Of course there are
139: differences, but they just aren't in the /sys/arch/XXXX directory).
1.18 fn 140: </p>
1.1 deraadt 141:
1.18 fn 142: <p>
1.1 deraadt 143: <dl>
1.41 deraadt 144: <dt><a href=alpha.html>Alpha</a> <dd> DEC Alpha-based machines.
145: <dt><a href=amiga.html>Amiga</a> <dd> Commodore Amiga.
146: <dt><a href=arc.html>ARC</a> <dd> ARC R4000/R4400 machines (including PICA)
147: <dt><a href=arm32.html>Arm32</a> <dd> Acorn ARM6+ computers.
148: <dt><a href=atari.html>Atari</a> <dd> Atari TT and Falcon models.
149: <dt><a href=hp300.html>HP300</a> <dd> Hewlett-Packard HP300/HP400 machines.
1.1 deraadt 150: <dt><a href=i386.html>i386</a> <dd> Your standard run-of-the-mill PC.
151: <dt><a href=mac68k.html>mac68k</a> <dd> Most MC680x0-based Apple Macintosh models.
1.41 deraadt 152: <dt><a href=mvme68k.html>MVME68K</a> <dd> Motorola MVME147/16x/17x 68K VME cards.
153: <dt><a href=pc532.html>PC532</a> <dd> A rare NS32532-based computer.
154: <dt><a href=pmax.html>Pmax</a> <dd> DEC MIPS-based machines.
155: <dt><a href=sparc.html>Sparc</a> <dd> Sun's Sun4 and sun4c models (sun4m soon!).
156: <dt><a href=sun3.html>Sun3</a> <dd> Sun's sun3 models.
157: <dt><a href=vax.html>Vax</a> <dd> DEC's VAX computers.
1.1 deraadt 158: </dl>
1.18 fn 159: </p>
160:
161: <h3><hr><a name=futplat>New platforms under development.</a></h3>
1.1 deraadt 162:
1.18 fn 163: <p>
1.1 deraadt 164: <dl>
1.10 deraadt 165: <dt><a href=mvme88k.html>mvme88k</a> <dd> Motorola MVME18x/19x 88K VME cards
1.25 deraadt 166: <dt><a href=ppc.html>ppc</a> <dd> IBM/Apple/Motorola PowerPC-based machines.
1.1 deraadt 167: </dl>
1.18 fn 168: </p>
1.1 deraadt 169:
170: <p>
171: <h3>Platforms not being developed, but which should be</h3>
1.36 deraadt 172: There is enough free code available to make porting to these
173: machines relatively easy.
1.18 fn 174: </p>
175:
176: <p>
1.1 deraadt 177: <dl>
178: <dt><a href=hppa.html>hppa</a> <dd> Hewlett-Packard PA-RISC HP700/HP800 models.
179: <dt><a href=iris.html>iris</a> <dd> SGI Iris machines.
180: </dl>
1.18 fn 181: </p>
1.1 deraadt 182:
1.26 deraadt 183:
1.49 deraadt 184: <hr><hr>
185: <h3><a name=devel>How we help developers and users.</a></h3>
186:
1.50 deraadt 187: <dl>
1.55 deraadt 188: <dt><h4><a name=snapshots>BINARY SNAPSHOTS:</a></h4>
189:
190: <p>
1.59 deraadt 191: <dd>Snapshots will be made available from time to time on the ftp mirrors.
192: The snapshots are available on each of the FTP servers listed below,
1.55 deraadt 193: typically in the directory <strong>OpenBSD/snapshots</strong>.
194: You should also read the <a href=snapshots.html>general description
195: about OpenBSD snapshots</a>.
196: </p>
197:
1.59 deraadt 198: <p>
1.70 deraadt 199: <strong>
1.69 deraadt 200: NOTE: please do not fetch binaries directly from cvs.openbsd.org
201: but instead use one of the mirror sites.
202: </strong>
1.59 deraadt 203:
1.56 deraadt 204: </dl>
1.55 deraadt 205: <dl>
1.56 deraadt 206: <dt><h4><a name=ftp>FTP:</a></h4>
1.48 deraadt 207: <dd>This is a list of currently known ftp servers:<p>
208: <ul>
1.18 fn 209:
1.48 deraadt 210: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD>
211: ftp://ftp.openbsd.org/pub/OpenBSD</a><br>
212: located at Rutgers University, eastern USA.
213: <!-- deraadt@openbsd.org -->
1.18 fn 214:
1.48 deraadt 215: <li><a href=ftp://ftp.ibp.fr/pub/OpenBSD>
216: ftp://ftp.ibp.fr/pub/OpenBSD</a><br>
1.1 deraadt 217: located in France.
218: <!-- ftpmaint@ftp.ibp.fr -->
1.48 deraadt 219:
220: <li><a href=ftp://ftp.univ-evry.fr/pub/system/OpenBSD>
221: ftp://ftp.univ-evry.fr/pub/system/OpenBSD</a><br>
222: located in France.
223: <!-- mirror@ftp.univ-evry.fr -->
224:
1.52 deraadt 225: <li><a href=ftp://hal.heuris.com/pub/OpenBSD>
226: ftp://hal.heuris.com/pub/OpenBSD</a><br>
1.1 deraadt 227: located in University of Missouri-Rolla, mid-western USA.
228: <!-- johns@cs.umr.edu -->
1.48 deraadt 229:
230: <li><a href=ftp://ftp.tut.ac.jp/OpenBSD>
231: ftp://ftp.tut.ac.jp/OpenBSD</a><br>
232: located at Toyohashi University of Technology, Aichi, JAPAN
233: <!-- Keijiro Umehara ume@ftp.tut.ac.jp -->
234:
1.1 deraadt 235: </ul>
1.48 deraadt 236:
237: <p>
238: The file structure of each FTP server is as follows:
1.18 fn 239: </p>
240:
241: <p>
1.48 deraadt 242: <strong>
243: <dl>
244: <dt>OpenBSD/snapshots/
245: <dt>OpenBSD/X11/
246: <dt>OpenBSD/src/
247: </dl>
248: </strong>
1.18 fn 249: </p>
1.1 deraadt 250:
251: <p>
1.48 deraadt 252: If you add a new FTP mirror site, please contact
253: <a href=mailto:deraadt@theos.com> the FTP maintainer</a>.
254: </p>
1.50 deraadt 255: </dl>
1.48 deraadt 256:
1.50 deraadt 257: </dl>
1.1 deraadt 258: <dl>
1.50 deraadt 259: <dt><h4><a name=maillist>MAILING LISTS:</a></h4>
1.1 deraadt 260: <dd>Some mailing lists are used for the development and use of OpenBSD.
261: In each case, send mail to
262: <a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a>
263: with a message body of "<strong>subscribe mailing-list-name</strong>".
1.18 fn 264:
1.27 deraadt 265: There is a only minimal set of mailing lists intentionally; among
266: other benefits such as more communication it reduces cross-posting.
1.26 deraadt 267: There are no private mailing lists.
268: <p>
1.1 deraadt 269: These are the mailing lists:
270: <dl>
271: <dt><strong>announce</strong>
272: <dd>important announcements. Since this is a low volume list
273: it is excellent for people who just want to follow important events.
274: <dt><strong>tech</strong>
275: <dd>technical discussions
276: <dt><strong>misc</strong>
277: <dd>user questions and answers
278: <dt><strong>source-changes</strong>
279: <dd>automated mailout of CVS source tree changes
1.18 fn 280: </dl>
281:
1.1 deraadt 282: <p>
1.61 deraadt 283: For further assistance, send a message body of "<strong>help</strong>"
284: to <a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a>
1.1 deraadt 285: and you will receive a reply outlining all your options.
1.18 fn 286: </p>
1.1 deraadt 287:
1.61 deraadt 288: <p>
289: Furthermore, a
290: <a href=http://www.sigmasoft.com/~openbsd>mailing list archive</a>
291: is available.
292: </p>
293:
1.26 deraadt 294: </dl>
1.50 deraadt 295: <dl><h4><a name=gnats>BUG TRACKING:</a></h4>
296: <dd>We run GNATS for tracking bugs:
297: <a href=/cgi-bin/wwwgnats.pl>Click here to enter the bug tracking system.</a>
1.26 deraadt 298:
1.39 deraadt 299: </dl>
1.50 deraadt 300: <dl>
301: <dt><h4><a name=sup>SUP:</a></h4>
1.21 deraadt 302: <dd>Sorry, unlike other *BSD projects, the SUP service is not
303: available. We do not believe the SUP service to be a good tool for
304: source code access. But read below for the description of the
305: <a href="#anoncvs"><strong>anoncvs</strong> service!</a>
1.1 deraadt 306:
1.50 deraadt 307: <dt><h4><a name=anoncvs>CVS Access:</a></h4>
1.7 david 308: <dd>CVS is used to manage the OpenBSD source tree. This allows
309: developers to work on a local source tree and commit their changes when
310: ready. Also <strong>anyone</strong> can edit source files on their
311: local machines, and automatically track and merge in any changes made
312: in the OpenBSD CVS repository. Additionally they can easily see the
313: logs of, check out, or "diff" the source files in the OpenBSD source
314: tree.
1.57 deraadt 315: </p>
316:
317: <p>
318: Most importantly, the <strong>anoncvs</strong> service does NOT
319: delete the changes you make in your local copy of the source tree --
320: read on for more details!
321: </p>
1.18 fn 322:
1.1 deraadt 323: <p>
1.17 deraadt 324: The latest version of CVS is available at
325: <a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>.
326: Versions earlier than 1.6 are not recommended, and may not work.
1.57 deraadt 327: If you already have OpenBSD installed, CVS is included.
1.18 fn 328: </p>
329:
1.17 deraadt 330: <p>
1.18 fn 331: There are two levels of source tree access:
332: </p>
1.1 deraadt 333:
334: <dl>
1.58 deraadt 335: <dt><strong>Read-write access for developers:</strong>
1.1 deraadt 336: <dd>Developers who need to commit changes to the source tree must have
337: an account on the OpenBSD machines. Getting this access will be a
338: natural result of working on the sources with other OpenBSD developers.
1.58 deraadt 339: If someone does some good work and shows they can work with the team,
340: they will get an account.
1.18 fn 341: </dl>
342:
343: <dl>
1.58 deraadt 344: <dt><strong>Read-only access for everyone:</strong>
1.5 deraadt 345: <dd>Anyone can access the read-only CVS repositories. These copies
346: of the read-write CVS repository are mirrored often. To use one,
347: set your <strong>CVSROOT</strong> environment variable to one of
348: the following values:
1.1 deraadt 349: <ul>
1.21 deraadt 350: <p>
1.12 deraadt 351: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
352: Host also known as <strong>anoncvs.openbsd.org</strong> and
353: <strong>eap.ccrc.wustl.edu</strong>.<br>
1.4 deraadt 354: located at Washington University, St. Louis, mid-west USA.<br>
1.21 deraadt 355: maintained by <a href=mailto:chuck@maria.wustl.edu>Chuck Cranor</a>.<br>
1.5 deraadt 356: protocols: rsh, ssh, ssh port 2022.<br>
1.21 deraadt 357: updated every 4 hours.<br>
358: <p>
1.12 deraadt 359: <li><strong>CVSROOT=anoncvs@anoncvs2.usa.openbsd.org:/cvs</strong><br>
1.52 deraadt 360: Host also known as <strong>hal.heuris.com</strong>.<br>
361: located in MO, mid-west USA.<br>
362: maintained by <a href=mailto:johns@heuris.com>John Stone</a>.<br>
363: protocols: rsh, ssh, ssh port 2022.<br>
1.21 deraadt 364: updated every 12 hours.<br>
365: <p>
1.65 deraadt 366: <li><strong>CVSROOT=anoncvs@anoncvs3.usa.openbsd.org:/cvs</strong><br>
367: Host also known as <strong>freestuff.cs.colorado.edu</strong>.<br>
368: located at the University of Colorado, Boulder, western USA.<br>
369: maintained by <a href=mailto:Todd.Miller@cs.colorado.edu>Todd Miller</a>.<br>
370: protocols: ssh, ssh port 2022.<br>
371: updated every 6 hours.<br>
372: <p>
1.21 deraadt 373: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
374: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
375: located in London, UK.<br>
376: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
1.64 deraadt 377: protocols: rsh.<br>
1.21 deraadt 378: updated every 12 hours.<br>
1.43 deraadt 379: <p>
380: <li><strong>CVSROOT=anoncvs@anoncvs.tw.openbsd.org:/cvs</strong><br>
381: Host also known as <strong>hercules.secc.fju.edu.tw</strong>.<br>
382: located in Taipei, Taiwan.<br>
383: maintained by <a href=mailto:shawn@openbsd.org>Shawn Hsiao</a>.<br>
384: protocols: rsh, ssh, ssh port 2022.<br>
385: updated every 12 hours.<br>
1.71 deraadt 386: <p>
387: <li><strong>CVSROOT=anoncvs@anoncvs.no.openbsd.org:/cvs</strong><br>
388: located in Norway.<br>
389: maintained by <a href=mailto:micheals@openbsd.org>Michael Shuldman</a>.<br>
390: protocols: rsh, ssh, ssh port 2022.<br>
391: updated every 4 hours.<br>
1.1 deraadt 392: </ul>
1.21 deraadt 393: <p>
394: You may want to use `traceroute' to find out which server is nearest you.
1.1 deraadt 395: </dl>
1.18 fn 396: </p>
397:
1.1 deraadt 398: <p>
399: <strong>IMPORTANT NOTE:</strong>
400: There are a few issues relating to cryptographic software that everyone
401: should be aware of:
402: <ul>
1.20 deraadt 403: <li>The OpenBSD sources are from Canada.
404: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>It
405: is legal to export crypto software from Canada to the world.</a>
1.21 deraadt 406: <p>
1.1 deraadt 407: <li>However, if you are outside the USA or Canada, you should not
1.5 deraadt 408: fetch the cryptographic sections of the OpenBSD sources from an
409: anoncvs server located in the USA. The files in question are...
1.1 deraadt 410: <ul>
411: <li>src/kerberosIV/*
412: <li>src/lib/libc/crypt/crypt.c
413: <li>src/lib/libc/crypt/morecrypt.c
414: </ul>
415: Because of the USA ITAR munitions list,
416: crypto software may only be exported to Canada from the USA.
1.21 deraadt 417: <p>
1.58 deraadt 418: <li>The OpenBSD project is looking for more anoncvs servers -- read
419: on to find out how you can help.
1.1 deraadt 420: </ul>
1.18 fn 421: </p>
422:
1.1 deraadt 423: <p>
1.5 deraadt 424: A sample use of an anoncvs CVS server would be:
1.1 deraadt 425: <pre>
1.12 deraadt 426: % setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
1.1 deraadt 427: % cd /tmp
1.58 deraadt 428: % cvs get src/sys/arch/sparc
1.1 deraadt 429: [copies the files from the repository to your machine]
1.58 deraadt 430: % cvs log src/sys/arch/sparc/sparc/locore.s
1.1 deraadt 431: [shows the commit log for the chosen file ]
1.58 deraadt 432: % cvs diff -bc -r1.1 -r1.5 src/sys/arch/sparc/sparc/locore.s
1.1 deraadt 433: [shows the changes between revisions 1.1 and rev 1.5]
434: </pre>
1.18 fn 435: </p>
436:
437: <p>
1.44 deraadt 438: Here is how someone using anoncvs regularily would update his
439: source tree:
440: <pre>
441: # setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
442: # cd /usr
443: # cvs -q get -PA src
444: </pre>
445: or similarily later on he might try
446: <pre>
447: # cd /usr/src
448: # cvs -q up -PAd
449: </pre>
1.58 deraadt 450: Everytime you ran this it would syncronize your /usr/src tree. It would
451: not destroy any of your local changes, rather it would attempt to merge
452: changes in. If you use obj directories (not obj symbolic links) you may
453: wish to append "-I obj" to the cvs command line, this will keep cvs from
454: spitting out a warning about all the obj directories it is going to
455: encounter which are not in the repository.
1.44 deraadt 456: </p>
457:
458: <p>
1.1 deraadt 459: The CVS man page (included with the CVS sources) has much more
1.18 fn 460: information about how CVS can be used.
461: </p>
462:
1.1 deraadt 463: <p>
464: The anoncvs service gives fledgling developers a chance to learn CVS
465: operation and get thoroughly involved in the development process
466: before getting "commit" access -- as a result of showing useful
467: skills and high quality results they will naturally later be given
1.18 fn 468: developer access. As well, people providing patches can create
469: their "diff"s relative to the CVS tree, which will ease integration.
470: </p>
471:
472: <p>
473: The CVS client uses rsh to talk to the CVS server. If some local
474: security measure like a firewall (or imperfect protocol emulators
475: like slirp) prevents you from using rsh, you may be able to use
1.58 deraadt 476: <a href=http://www.cs.hut.fi/ssh>ssh</a> instead. In this case,
477: one sets the environment variable <strong>CVS_RSH</strong> to point
478: to ssh (typically <strong>/usr/local/bin/ssh</strong>). To reduce the
479: performance hit the anoncvs server would take it is recommended (and
480: requested) that you disable encryption. If your local site prevents
481: you from connecting out to port 22 (which ssh defaults to using) use
482: port 2022.
1.18 fn 483: </p>
1.5 deraadt 484:
485: <p>
1.1 deraadt 486: Do not be tempted to turn on compression since CVS already compresses.
487: Use something like the following in your <strong>$HOME/.ssh/config</strong>
488: file.
1.18 fn 489: </p>
1.1 deraadt 490: <pre>
1.12 deraadt 491: Host anoncvs.usa.openbsd.org
1.1 deraadt 492: Cipher none
493: Port 2022
494: </pre>
1.18 fn 495:
496: <p>
1.71 deraadt 497: CVS is a little noisy starting up; to quiet it a bit you may want to
498: do this:
499: <pre>
500: setenv CVS_CLIENT_PORT -1
501: </pre>
502: </p>
503:
504: <p>
1.18 fn 505: If you wish to be a new anoncvs mirror site, please contact the anoncvs
506: <a href=mailto:deraadt@theos.com>maintainer</a>.
1.16 deraadt 507: Anoncvs mirrors require about 300MB of disk, and use up to 4MB of swap
1.1 deraadt 508: per anoncvs user (assuming the user does a large operation; while smaller
509: operations use fewer resources, anoncvs still makes much more of an
1.18 fn 510: impact than ftp or sup). Such anoncvs machines should have excellent
511: network connectivity for the area they are expected to serve. A
512: <a href=anoncvs.shar>document</a>
513: which describes the setup of anoncvs servers is available.
514: </p>
1.1 deraadt 515:
516: </dl>
517:
518: <hr>
519: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.73 ! deraadt 520: <br><small>$OpenBSD: index.html,v 1.72 1996/08/12 19:52:08 deraadt Exp $</small>
1.18 fn 521:
522: </body>
523: </html>