[BACK]Return to index.html CVS log [TXT][DIR] Up to [local] / www

Annotation of www/index.html, Revision 1.56

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