Annotation of www/index.html, Revision 1.66
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.66 ! deraadt 115: <li>a real adduser program, which can even be used uninteractively.
! 116: <li>Like C2, lose setuid/setgid bits if owner/group changed by chown(). This is
! 117: attached to a sysctl.
! 118: <li>partial protection against tcp SYN attacks.
1.1 deraadt 119: </ul>
1.18 fn 120: </p>
1.1 deraadt 121:
1.18 fn 122: <h3><hr><a name=curplat>Platforms currently supported.</a></h3>
1.1 deraadt 123:
1.18 fn 124: <p>
1.1 deraadt 125: Note: for some of these platforms, the platform-independent code may
126: be identical to that found in NetBSD because there isn't a specific
127: OpenBSD developer. For other ports the differences are significant.
128: If you find an empty page that means nothing of consequence that is
129: directly port-specific has changed from NetBSD. (Of course there are
130: differences, but they just aren't in the /sys/arch/XXXX directory).
1.18 fn 131: </p>
1.1 deraadt 132:
1.18 fn 133: <p>
1.1 deraadt 134: <dl>
1.41 deraadt 135: <dt><a href=alpha.html>Alpha</a> <dd> DEC Alpha-based machines.
136: <dt><a href=amiga.html>Amiga</a> <dd> Commodore Amiga.
137: <dt><a href=arc.html>ARC</a> <dd> ARC R4000/R4400 machines (including PICA)
138: <dt><a href=arm32.html>Arm32</a> <dd> Acorn ARM6+ computers.
139: <dt><a href=atari.html>Atari</a> <dd> Atari TT and Falcon models.
140: <dt><a href=hp300.html>HP300</a> <dd> Hewlett-Packard HP300/HP400 machines.
1.1 deraadt 141: <dt><a href=i386.html>i386</a> <dd> Your standard run-of-the-mill PC.
142: <dt><a href=mac68k.html>mac68k</a> <dd> Most MC680x0-based Apple Macintosh models.
1.41 deraadt 143: <dt><a href=mvme68k.html>MVME68K</a> <dd> Motorola MVME147/16x/17x 68K VME cards.
144: <dt><a href=pc532.html>PC532</a> <dd> A rare NS32532-based computer.
145: <dt><a href=pmax.html>Pmax</a> <dd> DEC MIPS-based machines.
146: <dt><a href=sparc.html>Sparc</a> <dd> Sun's Sun4 and sun4c models (sun4m soon!).
147: <dt><a href=sun3.html>Sun3</a> <dd> Sun's sun3 models.
148: <dt><a href=vax.html>Vax</a> <dd> DEC's VAX computers.
1.1 deraadt 149: </dl>
1.18 fn 150: </p>
151:
152: <h3><hr><a name=futplat>New platforms under development.</a></h3>
1.1 deraadt 153:
1.18 fn 154: <p>
1.1 deraadt 155: <dl>
1.10 deraadt 156: <dt><a href=mvme88k.html>mvme88k</a> <dd> Motorola MVME18x/19x 88K VME cards
1.25 deraadt 157: <dt><a href=ppc.html>ppc</a> <dd> IBM/Apple/Motorola PowerPC-based machines.
1.1 deraadt 158: </dl>
1.18 fn 159: </p>
1.1 deraadt 160:
161: <p>
162: <h3>Platforms not being developed, but which should be</h3>
1.36 deraadt 163: There is enough free code available to make porting to these
164: machines relatively easy.
1.18 fn 165: </p>
166:
167: <p>
1.1 deraadt 168: <dl>
169: <dt><a href=hppa.html>hppa</a> <dd> Hewlett-Packard PA-RISC HP700/HP800 models.
170: <dt><a href=iris.html>iris</a> <dd> SGI Iris machines.
171: </dl>
1.18 fn 172: </p>
1.1 deraadt 173:
1.26 deraadt 174:
1.49 deraadt 175: <hr><hr>
176: <h3><a name=devel>How we help developers and users.</a></h3>
177:
1.50 deraadt 178: <dl>
1.55 deraadt 179: <dt><h4><a name=snapshots>BINARY SNAPSHOTS:</a></h4>
180:
181: <p>
1.59 deraadt 182: <dd>Snapshots will be made available from time to time on the ftp mirrors.
183: The snapshots are available on each of the FTP servers listed below,
1.55 deraadt 184: typically in the directory <strong>OpenBSD/snapshots</strong>.
185: You should also read the <a href=snapshots.html>general description
186: about OpenBSD snapshots</a>.
187: </p>
188:
1.59 deraadt 189: <p>
190: NOTE: please do not fetch binaries directly from <string>cvs.openbsd.org
191: </string> but instead use one of the mirror sites.
192:
1.56 deraadt 193: </dl>
1.55 deraadt 194: <dl>
1.56 deraadt 195: <dt><h4><a name=ftp>FTP:</a></h4>
1.48 deraadt 196: <dd>This is a list of currently known ftp servers:<p>
197: <ul>
1.18 fn 198:
1.48 deraadt 199: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD>
200: ftp://ftp.openbsd.org/pub/OpenBSD</a><br>
201: located at Rutgers University, eastern USA.
202: <!-- deraadt@openbsd.org -->
1.18 fn 203:
1.48 deraadt 204: <li><a href=ftp://ftp.ibp.fr/pub/OpenBSD>
205: ftp://ftp.ibp.fr/pub/OpenBSD</a><br>
1.1 deraadt 206: located in France.
207: <!-- ftpmaint@ftp.ibp.fr -->
1.48 deraadt 208:
209: <li><a href=ftp://ftp.univ-evry.fr/pub/system/OpenBSD>
210: ftp://ftp.univ-evry.fr/pub/system/OpenBSD</a><br>
211: located in France.
212: <!-- mirror@ftp.univ-evry.fr -->
213:
1.52 deraadt 214: <li><a href=ftp://hal.heuris.com/pub/OpenBSD>
215: ftp://hal.heuris.com/pub/OpenBSD</a><br>
1.1 deraadt 216: located in University of Missouri-Rolla, mid-western USA.
217: <!-- johns@cs.umr.edu -->
1.48 deraadt 218:
219: <li><a href=ftp://ftp.tut.ac.jp/OpenBSD>
220: ftp://ftp.tut.ac.jp/OpenBSD</a><br>
221: located at Toyohashi University of Technology, Aichi, JAPAN
222: <!-- Keijiro Umehara ume@ftp.tut.ac.jp -->
223:
1.1 deraadt 224: </ul>
1.48 deraadt 225:
226: <p>
227: The file structure of each FTP server is as follows:
1.18 fn 228: </p>
229:
230: <p>
1.48 deraadt 231: <strong>
232: <dl>
233: <dt>OpenBSD/snapshots/
234: <dt>OpenBSD/X11/
235: <dt>OpenBSD/src/
236: </dl>
237: </strong>
1.18 fn 238: </p>
1.1 deraadt 239:
240: <p>
1.48 deraadt 241: If you add a new FTP mirror site, please contact
242: <a href=mailto:deraadt@theos.com> the FTP maintainer</a>.
243: </p>
1.50 deraadt 244: </dl>
1.48 deraadt 245:
1.50 deraadt 246: </dl>
1.1 deraadt 247: <dl>
1.50 deraadt 248: <dt><h4><a name=maillist>MAILING LISTS:</a></h4>
1.1 deraadt 249: <dd>Some mailing lists are used for the development and use of OpenBSD.
250: In each case, send mail to
251: <a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a>
252: with a message body of "<strong>subscribe mailing-list-name</strong>".
1.18 fn 253:
1.27 deraadt 254: There is a only minimal set of mailing lists intentionally; among
255: other benefits such as more communication it reduces cross-posting.
1.26 deraadt 256: There are no private mailing lists.
257: <p>
1.1 deraadt 258: These are the mailing lists:
259: <dl>
260: <dt><strong>announce</strong>
261: <dd>important announcements. Since this is a low volume list
262: it is excellent for people who just want to follow important events.
263: <dt><strong>tech</strong>
264: <dd>technical discussions
265: <dt><strong>misc</strong>
266: <dd>user questions and answers
267: <dt><strong>source-changes</strong>
268: <dd>automated mailout of CVS source tree changes
1.18 fn 269: </dl>
270:
1.1 deraadt 271: <p>
1.61 deraadt 272: For further assistance, send a message body of "<strong>help</strong>"
273: to <a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a>
1.1 deraadt 274: and you will receive a reply outlining all your options.
1.18 fn 275: </p>
1.1 deraadt 276:
1.61 deraadt 277: <p>
278: Furthermore, a
279: <a href=http://www.sigmasoft.com/~openbsd>mailing list archive</a>
280: is available.
281: </p>
282:
1.26 deraadt 283: </dl>
1.50 deraadt 284: <dl><h4><a name=gnats>BUG TRACKING:</a></h4>
285: <dd>We run GNATS for tracking bugs:
286: <a href=/cgi-bin/wwwgnats.pl>Click here to enter the bug tracking system.</a>
1.26 deraadt 287:
1.39 deraadt 288: </dl>
1.50 deraadt 289: <dl>
290: <dt><h4><a name=sup>SUP:</a></h4>
1.21 deraadt 291: <dd>Sorry, unlike other *BSD projects, the SUP service is not
292: available. We do not believe the SUP service to be a good tool for
293: source code access. But read below for the description of the
294: <a href="#anoncvs"><strong>anoncvs</strong> service!</a>
1.1 deraadt 295:
1.50 deraadt 296: <dt><h4><a name=anoncvs>CVS Access:</a></h4>
1.7 david 297: <dd>CVS is used to manage the OpenBSD source tree. This allows
298: developers to work on a local source tree and commit their changes when
299: ready. Also <strong>anyone</strong> can edit source files on their
300: local machines, and automatically track and merge in any changes made
301: in the OpenBSD CVS repository. Additionally they can easily see the
302: logs of, check out, or "diff" the source files in the OpenBSD source
303: tree.
1.57 deraadt 304: </p>
305:
306: <p>
307: Most importantly, the <strong>anoncvs</strong> service does NOT
308: delete the changes you make in your local copy of the source tree --
309: read on for more details!
310: </p>
1.18 fn 311:
1.1 deraadt 312: <p>
1.17 deraadt 313: The latest version of CVS is available at
314: <a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>.
315: Versions earlier than 1.6 are not recommended, and may not work.
1.57 deraadt 316: If you already have OpenBSD installed, CVS is included.
1.18 fn 317: </p>
318:
1.17 deraadt 319: <p>
1.18 fn 320: There are two levels of source tree access:
321: </p>
1.1 deraadt 322:
323: <dl>
1.58 deraadt 324: <dt><strong>Read-write access for developers:</strong>
1.1 deraadt 325: <dd>Developers who need to commit changes to the source tree must have
326: an account on the OpenBSD machines. Getting this access will be a
327: natural result of working on the sources with other OpenBSD developers.
1.58 deraadt 328: If someone does some good work and shows they can work with the team,
329: they will get an account.
1.18 fn 330: </dl>
331:
332: <dl>
1.58 deraadt 333: <dt><strong>Read-only access for everyone:</strong>
1.5 deraadt 334: <dd>Anyone can access the read-only CVS repositories. These copies
335: of the read-write CVS repository are mirrored often. To use one,
336: set your <strong>CVSROOT</strong> environment variable to one of
337: the following values:
1.1 deraadt 338: <ul>
1.21 deraadt 339: <p>
1.12 deraadt 340: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
341: Host also known as <strong>anoncvs.openbsd.org</strong> and
342: <strong>eap.ccrc.wustl.edu</strong>.<br>
1.4 deraadt 343: located at Washington University, St. Louis, mid-west USA.<br>
1.21 deraadt 344: maintained by <a href=mailto:chuck@maria.wustl.edu>Chuck Cranor</a>.<br>
1.5 deraadt 345: protocols: rsh, ssh, ssh port 2022.<br>
1.21 deraadt 346: updated every 4 hours.<br>
347: <p>
1.12 deraadt 348: <li><strong>CVSROOT=anoncvs@anoncvs2.usa.openbsd.org:/cvs</strong><br>
1.52 deraadt 349: Host also known as <strong>hal.heuris.com</strong>.<br>
350: located in MO, mid-west USA.<br>
351: maintained by <a href=mailto:johns@heuris.com>John Stone</a>.<br>
352: protocols: rsh, ssh, ssh port 2022.<br>
1.21 deraadt 353: updated every 12 hours.<br>
354: <p>
1.65 deraadt 355: <li><strong>CVSROOT=anoncvs@anoncvs3.usa.openbsd.org:/cvs</strong><br>
356: Host also known as <strong>freestuff.cs.colorado.edu</strong>.<br>
357: located at the University of Colorado, Boulder, western USA.<br>
358: maintained by <a href=mailto:Todd.Miller@cs.colorado.edu>Todd Miller</a>.<br>
359: protocols: ssh, ssh port 2022.<br>
360: updated every 6 hours.<br>
361: <p>
1.21 deraadt 362: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
363: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
364: located in London, UK.<br>
365: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
1.64 deraadt 366: protocols: rsh.<br>
1.21 deraadt 367: updated every 12 hours.<br>
1.43 deraadt 368: <p>
369: <li><strong>CVSROOT=anoncvs@anoncvs.tw.openbsd.org:/cvs</strong><br>
370: Host also known as <strong>hercules.secc.fju.edu.tw</strong>.<br>
371: located in Taipei, Taiwan.<br>
372: maintained by <a href=mailto:shawn@openbsd.org>Shawn Hsiao</a>.<br>
373: protocols: rsh, ssh, ssh port 2022.<br>
374: updated every 12 hours.<br>
1.1 deraadt 375: </ul>
1.21 deraadt 376: <p>
377: You may want to use `traceroute' to find out which server is nearest you.
1.1 deraadt 378: </dl>
1.18 fn 379: </p>
380:
1.1 deraadt 381: <p>
382: <strong>IMPORTANT NOTE:</strong>
383: There are a few issues relating to cryptographic software that everyone
384: should be aware of:
385: <ul>
1.20 deraadt 386: <li>The OpenBSD sources are from Canada.
387: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>It
388: is legal to export crypto software from Canada to the world.</a>
1.21 deraadt 389: <p>
1.1 deraadt 390: <li>However, if you are outside the USA or Canada, you should not
1.5 deraadt 391: fetch the cryptographic sections of the OpenBSD sources from an
392: anoncvs server located in the USA. The files in question are...
1.1 deraadt 393: <ul>
394: <li>src/kerberosIV/*
395: <li>src/lib/libc/crypt/crypt.c
396: <li>src/lib/libc/crypt/morecrypt.c
397: </ul>
398: Because of the USA ITAR munitions list,
399: crypto software may only be exported to Canada from the USA.
1.21 deraadt 400: <p>
1.58 deraadt 401: <li>The OpenBSD project is looking for more anoncvs servers -- read
402: on to find out how you can help.
1.1 deraadt 403: </ul>
1.18 fn 404: </p>
405:
1.1 deraadt 406: <p>
1.5 deraadt 407: A sample use of an anoncvs CVS server would be:
1.1 deraadt 408: <pre>
1.12 deraadt 409: % setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
1.1 deraadt 410: % cd /tmp
1.58 deraadt 411: % cvs get src/sys/arch/sparc
1.1 deraadt 412: [copies the files from the repository to your machine]
1.58 deraadt 413: % cvs log src/sys/arch/sparc/sparc/locore.s
1.1 deraadt 414: [shows the commit log for the chosen file ]
1.58 deraadt 415: % cvs diff -bc -r1.1 -r1.5 src/sys/arch/sparc/sparc/locore.s
1.1 deraadt 416: [shows the changes between revisions 1.1 and rev 1.5]
417: </pre>
1.18 fn 418: </p>
419:
420: <p>
1.44 deraadt 421: Here is how someone using anoncvs regularily would update his
422: source tree:
423: <pre>
424: # setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
425: # cd /usr
426: # cvs -q get -PA src
427: </pre>
428: or similarily later on he might try
429: <pre>
430: # cd /usr/src
431: # cvs -q up -PAd
432: </pre>
1.58 deraadt 433: Everytime you ran this it would syncronize your /usr/src tree. It would
434: not destroy any of your local changes, rather it would attempt to merge
435: changes in. If you use obj directories (not obj symbolic links) you may
436: wish to append "-I obj" to the cvs command line, this will keep cvs from
437: spitting out a warning about all the obj directories it is going to
438: encounter which are not in the repository.
1.44 deraadt 439: </p>
440:
441: <p>
1.1 deraadt 442: The CVS man page (included with the CVS sources) has much more
1.18 fn 443: information about how CVS can be used.
444: </p>
445:
1.1 deraadt 446: <p>
447: The anoncvs service gives fledgling developers a chance to learn CVS
448: operation and get thoroughly involved in the development process
449: before getting "commit" access -- as a result of showing useful
450: skills and high quality results they will naturally later be given
1.18 fn 451: developer access. As well, people providing patches can create
452: their "diff"s relative to the CVS tree, which will ease integration.
453: </p>
454:
455: <p>
456: The CVS client uses rsh to talk to the CVS server. If some local
457: security measure like a firewall (or imperfect protocol emulators
458: like slirp) prevents you from using rsh, you may be able to use
1.58 deraadt 459: <a href=http://www.cs.hut.fi/ssh>ssh</a> instead. In this case,
460: one sets the environment variable <strong>CVS_RSH</strong> to point
461: to ssh (typically <strong>/usr/local/bin/ssh</strong>). To reduce the
462: performance hit the anoncvs server would take it is recommended (and
463: requested) that you disable encryption. If your local site prevents
464: you from connecting out to port 22 (which ssh defaults to using) use
465: port 2022.
1.18 fn 466: </p>
1.5 deraadt 467:
468: <p>
1.1 deraadt 469: Do not be tempted to turn on compression since CVS already compresses.
470: Use something like the following in your <strong>$HOME/.ssh/config</strong>
471: file.
1.18 fn 472: </p>
1.1 deraadt 473: <pre>
1.12 deraadt 474: Host anoncvs.usa.openbsd.org
1.1 deraadt 475: Cipher none
476: Port 2022
477: </pre>
1.18 fn 478:
479: <p>
480: If you wish to be a new anoncvs mirror site, please contact the anoncvs
481: <a href=mailto:deraadt@theos.com>maintainer</a>.
1.16 deraadt 482: Anoncvs mirrors require about 300MB of disk, and use up to 4MB of swap
1.1 deraadt 483: per anoncvs user (assuming the user does a large operation; while smaller
484: operations use fewer resources, anoncvs still makes much more of an
1.18 fn 485: impact than ftp or sup). Such anoncvs machines should have excellent
486: network connectivity for the area they are expected to serve. A
487: <a href=anoncvs.shar>document</a>
488: which describes the setup of anoncvs servers is available.
489: </p>
1.1 deraadt 490:
491: </dl>
492:
493: <hr>
494: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.66 ! deraadt 495: <br><small>$OpenBSD: index.html,v 1.65 1996/08/07 15:42:53 deraadt Exp $</small>
1.18 fn 496:
497: </body>
498: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to index.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www