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