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

Annotation of www/index.html, Revision 1.41

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>
                     34: <li><a href=#snapshots>Binary snapshots</a>
                     35: <li><a href=#devel>How we help developers and users</a>
                     36: <li><a href=goals.html>OpenBSD project goals</a>
                     37: </ul>
                     38: </p>
                     39:
                     40: <h3><hr><a name=additions>Changes Relative to other *BSD's.</a></h3>
                     41:
                     42: <p>
1.1       deraadt    43: OpenBSD looks a lot like NetBSD (which it is derived from, following
                     44: the 4.4BSD roots), but is now being developed seperately.  Good changes
                     45: from other free operating systems will be merged in (of course, depending
1.24      deraadt    46: on various factors like developer time for example.)  OpenBSD tracks
                     47: NetBSD changes very closely; say anywhere between 2 days to 10 days
                     48: behind the state of NetBSD-current all the time.  Hence you can truly
                     49: say that OpenBSD is NetBSD <b>PLUS MORE STUFF</b>.
1.18      fn         50: </p>
1.1       deraadt    51:
                     52: <p>
1.22      deraadt    53: Various additions have been made. This is only a small partial list of
1.25      deraadt    54: the major machine independent changes (ie. it is the most interesting
                     55: changes or what people ask about most often). Check the specific port
                     56: you are interested in for further details of that port -- many of them
                     57: have been extended too.
1.1       deraadt    58: <ul>
1.35      deraadt    59: <li>Many many NetBSD PR's fixed (which NetBSD has not yet fixed)
1.22      deraadt    60: <li>New curses library, including libform, libpanel and libmenu.
1.25      deraadt    61: <li>a termlib library which understands termcap.db, needed for new curses.
                     62: <li>The FreeBSD ports subsystem was integrated and is usable by you!
1.22      deraadt    63: <li>ipfilter for filtering dangerous packets
                     64: <li>better ELF support
1.25      deraadt    65: <li>nlist() that understands ELF, ECOFF, and a.out, allowing non-a.out ports
                     66:        to use kvm utilies
1.22      deraadt    67: <li>Verbatim integration of the GNU tools (using a wrapper Makefile)
                     68: <li>All the pieces needed for cross compilation are in the source tree.
                     69: <li>Some LKM support in the tree.
                     70: <li>ATAPI support (should work on all ISA busses)
1.25      deraadt    71: <li>new scsi, md5, pkg_* commands
1.22      deraadt    72: <li>Numerous security related fixes
1.25      deraadt    73: <li>Kerberos and other crypto in the source tree that is exportable
                     74: <li>Solid YP master, server, and client capabilities.
1.22      deraadt    75: <li>/dev/rnd -- source of random data
1.23      deraadt    76: <li>In-kernel update(8) with an adaptive algorithm
1.25      deraadt    77: <li>Some ddb improvements and extensions
                     78: <li>Numerous scsi fixes
1.28      deraadt    79: <li>new system calls: rfork(), minherit(), poll().
                     80: <li>select() that can handle any amount of file descriptors.
1.29      deraadt    81: <li>kernfs extensions
                     82: <li>ATM support (support for one company's sparc & i386 cards available)
1.33      deraadt    83: <li>Boot kernels with "-c" to edit/enable/disable device configuration tables
1.38      deraadt    84: <li>pax as tar, gnutar is toast
                     85: <li>Even more security fixes.
1.40      deraadt    86: <li>Accepts FreeBSD MD5 passwords in password maps, soon will be able of
                     87:        generating them too
                     88: <li>Linux ext2fs and BSD4.4 LFS support being worked on.
1.1       deraadt    89: </ul>
1.18      fn         90: </p>
1.1       deraadt    91:
1.18      fn         92: <h3><hr><a name=curplat>Platforms currently supported.</a></h3>
1.1       deraadt    93:
1.18      fn         94: <p>
1.1       deraadt    95: Note: for some of these platforms, the platform-independent code may
                     96: be identical to that found in NetBSD because there isn't a specific
                     97: OpenBSD developer. For other ports the differences are significant.
                     98: If you find an empty page that means nothing of consequence that is
                     99: directly port-specific has changed from NetBSD. (Of course there are
                    100: differences, but they just aren't in the /sys/arch/XXXX directory).
1.18      fn        101: </p>
1.1       deraadt   102:
1.18      fn        103: <p>
1.1       deraadt   104: <dl>
1.41    ! deraadt   105: <dt><a href=alpha.html>Alpha</a>       <dd> DEC Alpha-based machines.
        !           106: <dt><a href=amiga.html>Amiga</a>       <dd> Commodore Amiga.
        !           107: <dt><a href=arc.html>ARC</a>           <dd> ARC R4000/R4400 machines (including PICA)
        !           108: <dt><a href=arm32.html>Arm32</a>       <dd> Acorn ARM6+ computers.
        !           109: <dt><a href=atari.html>Atari</a>       <dd> Atari TT and Falcon models.
        !           110: <dt><a href=hp300.html>HP300</a>       <dd> Hewlett-Packard HP300/HP400 machines.
1.1       deraadt   111: <dt><a href=i386.html>i386</a>         <dd> Your standard run-of-the-mill PC.
                    112: <dt><a href=mac68k.html>mac68k</a>     <dd> Most MC680x0-based Apple Macintosh models.
1.41    ! deraadt   113: <dt><a href=mvme68k.html>MVME68K</a>   <dd> Motorola MVME147/16x/17x 68K VME cards.
        !           114: <dt><a href=pc532.html>PC532</a>       <dd> A rare NS32532-based computer.
        !           115: <dt><a href=pmax.html>Pmax</a>         <dd> DEC MIPS-based machines.
        !           116: <dt><a href=sparc.html>Sparc</a>       <dd> Sun's Sun4 and sun4c models (sun4m soon!).
        !           117: <dt><a href=sun3.html>Sun3</a>         <dd> Sun's sun3 models.
        !           118: <dt><a href=vax.html>Vax</a>           <dd> DEC's VAX computers.
1.1       deraadt   119: </dl>
1.18      fn        120: </p>
                    121:
                    122: <h3><hr><a name=futplat>New platforms under development.</a></h3>
1.1       deraadt   123:
1.18      fn        124: <p>
1.1       deraadt   125: <dl>
1.10      deraadt   126: <dt><a href=mvme88k.html>mvme88k</a>   <dd> Motorola MVME18x/19x 88K VME cards
1.25      deraadt   127: <dt><a href=ppc.html>ppc</a>           <dd> IBM/Apple/Motorola PowerPC-based machines.
1.1       deraadt   128: </dl>
1.18      fn        129: </p>
1.1       deraadt   130:
                    131: <p>
                    132: <h3>Platforms not being developed, but which should be</h3>
1.36      deraadt   133: There is enough free code available to make porting to these
                    134: machines relatively easy.
1.18      fn        135: </p>
                    136:
                    137: <p>
1.1       deraadt   138: <dl>
                    139: <dt><a href=hppa.html>hppa</a>         <dd> Hewlett-Packard PA-RISC HP700/HP800 models.
                    140: <dt><a href=iris.html>iris</a>         <dd> SGI Iris machines.
                    141: </dl>
1.18      fn        142: </p>
1.1       deraadt   143:
1.26      deraadt   144:
                    145: <h3><hr><hr><a name=snapshots>Binary Snapshots.</a></h3>
1.18      fn        146:
                    147: <p>
1.1       deraadt   148: Snapshots will be made available from time to time in the following
1.34      deraadt   149: directories.  Please do not fetch binaries directly from
                    150: <string>cvs.openbsd.org</string>, but instead use one of these
                    151: mirrors.
1.18      fn        152: </p>
                    153:
                    154: <p>
1.1       deraadt   155: <ul>
                    156: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD/snapshots>
                    157: ftp://ftp.openbsd.org/pub/OpenBSD/snapshots</a><br>
                    158: located at Rutgers University, eastern USA.
                    159: <!-- davem@openbsd.org -->
                    160: <li><a href=ftp://ftp.ibp.fr/pub/OpenBSD/snapshots>
                    161: ftp://ftp.ibp.fr/pub/OpenBSD/snapshots/</a><br>
                    162: located in France.
                    163: <!-- ftpmaint@ftp.ibp.fr -->
                    164: <li><a href=ftp://hal.cs.umr.edu/pub/OpenBSD/snapshots>
                    165: ftp://hal.cs.umr.edu/pub/OpenBSD/snapshots/</a><br>
                    166: located in University of Missouri-Rolla, mid-western USA.
                    167: <!-- johns@cs.umr.edu -->
                    168: </ul>
1.18      fn        169: </p>
                    170:
                    171: <p>
1.1       deraadt   172: You should also read the <a href=snapshots.html>
                    173: general description about OpenBSD snapshots</a>.
1.18      fn        174: </p>
1.1       deraadt   175:
                    176: <p>
                    177: The page for each platform (listed above) provides a link to the
                    178: specific snapshot ftp area, as well as other information you might
                    179: find neccessary or handy.
1.18      fn        180: </p>
1.1       deraadt   181:
1.18      fn        182: <hr>
                    183: <h3><a name=devel>How we help developers and users.</a></h3>
                    184:
                    185: <p>
1.1       deraadt   186: <dl>
                    187: <dt><h4>Mailing Lists:</h4>
                    188: <dd>Some mailing lists are used for the development and use of OpenBSD.
                    189: In each case, send mail to
                    190: <a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a>
                    191: with a message body of "<strong>subscribe mailing-list-name</strong>".
1.18      fn        192:
1.27      deraadt   193: There is a only minimal set of mailing lists intentionally; among
                    194: other benefits such as more communication it reduces cross-posting.
1.26      deraadt   195: There are no private mailing lists.
                    196: <p>
1.1       deraadt   197: These are the mailing lists:
                    198: <dl>
                    199: <dt><strong>announce</strong>
                    200: <dd>important announcements. Since this is a low volume list
                    201: it is excellent for people who just want to follow important events.
                    202: <dt><strong>tech</strong>
                    203: <dd>technical discussions
                    204: <dt><strong>misc</strong>
                    205: <dd>user questions and answers
                    206: <dt><strong>source-changes</strong>
                    207: <dd>automated mailout of CVS source tree changes
1.18      fn        208: </dl>
                    209:
1.1       deraadt   210: <p>
                    211: For further assistance, send a message body of "<strong>help</strong>",
                    212: and you will receive a reply outlining all your options.
1.18      fn        213: </p>
1.1       deraadt   214:
1.26      deraadt   215: </dl>
                    216:
1.39      deraadt   217: <dl><h4>Bug tracking:</h4>
                    218: We run GNATS for tracking bugs:
                    219: <a href=/cgi-bin/wwwgnats.pl>Click here to enter the bug tracking system.</a>
                    220: </dl>
                    221:
1.18      fn        222: <dl><h4>FTP:</h4>
1.1       deraadt   223: <dd>This is a list of currently known ftp servers:<p>
                    224: <ul>
                    225: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD>
                    226: ftp://ftp.openbsd.org/pub/OpenBSD</a><br>
                    227: located at Rutgers University, eastern USA.
                    228: <!-- davem@openbsd.org -->
                    229: <li><a href=ftp://ftp.ibp.fr/pub/OpenBSD>
                    230: ftp://ftp.ibp.fr/pub/OpenBSD</a><br>
                    231: located in France.
                    232: <!-- ftpmaint@ftp.ibp.fr -->
                    233: <li><a href=ftp://hal.cs.umr.edu/pub/OpenBSD>
                    234: ftp://hal.cs.umr.edu/pub/OpenBSD</a><br>
                    235: located in University of Missouri-Rolla, mid-western USA.
                    236: <!-- johns@cs.umr.edu -->
                    237: </ul>
1.18      fn        238:
1.1       deraadt   239: <p>
1.18      fn        240: The file structure of the FTP servers is as follows:
                    241: </p>
1.1       deraadt   242:
                    243: <p>
1.18      fn        244: <strong>
                    245: <dl>
1.1       deraadt   246: <dt>pub/OpenBSD/snapshots/
                    247: <dt>pub/OpenBSD/src/
                    248: </dl>
                    249: </strong>
1.18      fn        250: </p>
                    251:
1.1       deraadt   252: <p>
                    253: If you add a new FTP mirror site, please contact
                    254: <a href=mailto:deraadt@theos.com> the FTP maintainer</a>.
1.18      fn        255: </p>
1.1       deraadt   256:
                    257: <dt><h4>SUP:</h4>
1.21      deraadt   258: <dd>Sorry, unlike other *BSD projects, the SUP service is not
                    259: available.  We do not believe the SUP service to be a good tool for
                    260: source code access. But read below for the description of the
                    261: <a href="#anoncvs"><strong>anoncvs</strong> service!</a>
1.1       deraadt   262:
                    263: <dt><h4>CVS Access:</h4>
1.7       david     264: <dd>CVS is used to manage the OpenBSD source tree. This allows
                    265: developers to work on a local source tree and commit their changes when
                    266: ready.  Also <strong>anyone</strong> can edit source files on their
                    267: local machines, and automatically track and merge in any changes made
                    268: in the OpenBSD CVS repository. Additionally they can easily see the
                    269: logs of, check out, or "diff" the source files in the OpenBSD source
                    270: tree.
1.18      fn        271:
1.1       deraadt   272: <p>
1.17      deraadt   273: The latest version of CVS is available at
                    274: <a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>.
                    275: Versions earlier than 1.6 are not recommended, and may not work.
1.18      fn        276: </p>
                    277:
1.17      deraadt   278: <p>
1.18      fn        279: There are two levels of source tree access:
                    280: </p>
1.1       deraadt   281:
                    282: <dl>
                    283: <dt><strong>Read-write access for developers</strong>
                    284: <dd>Developers who need to commit changes to the source tree must have
                    285: an account on the OpenBSD machines.  Getting this access will be a
                    286: natural result of working on the sources with other OpenBSD developers.
1.18      fn        287: </dl>
                    288: </p>
1.1       deraadt   289: The OpenBSD cvs server is in Calgary, Alberta, Canada.
                    290: <p>
1.18      fn        291:
                    292: <dl>
1.21      deraadt   293: <a name="anoncvs">
1.1       deraadt   294: <dt><strong>Read-only access for everyone</strong>
1.5       deraadt   295: <dd>Anyone can access the read-only CVS repositories. These copies
                    296: of the read-write CVS repository are mirrored often. To use one,
                    297: set your <strong>CVSROOT</strong> environment variable to one of
                    298: the following values:
1.1       deraadt   299: <ul>
1.21      deraadt   300: <p>
1.12      deraadt   301: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
                    302: Host also known as <strong>anoncvs.openbsd.org</strong> and
                    303: <strong>eap.ccrc.wustl.edu</strong>.<br>
1.4       deraadt   304: located at Washington University, St. Louis, mid-west USA.<br>
1.21      deraadt   305: maintained by <a href=mailto:chuck@maria.wustl.edu>Chuck Cranor</a>.<br>
1.5       deraadt   306: protocols: rsh, ssh, ssh port 2022.<br>
1.21      deraadt   307: updated every 4 hours.<br>
                    308: <p>
1.12      deraadt   309: <li><strong>CVSROOT=anoncvs@anoncvs2.usa.openbsd.org:/cvs</strong><br>
                    310: Host also known as <strong>hal.cs.umr.edu</strong>.<br>
1.4       deraadt   311: located at University of Missouri-Rolla, Rolla, MO, mid-west USA.<br>
1.21      deraadt   312: maintained by <a href=mailto:johns@cs.umr.edu>John Stone</a>.<br>
1.12      deraadt   313: protocols: ssh, ssh port 2022 (<strong>NO rsh</strong>).<br>
1.21      deraadt   314: updated every 12 hours.<br>
                    315: <p>
                    316: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
                    317: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
                    318: located in London, UK.<br>
                    319: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
                    320: protocols: rsh, ssh, ssh port 2022.<br>
                    321: updated every 12 hours.<br>
1.1       deraadt   322: </ul>
1.21      deraadt   323: <p>
                    324: You may want to use `traceroute' to find out which server is nearest you.
1.1       deraadt   325: </dl>
1.18      fn        326: </p>
                    327:
1.1       deraadt   328: <p>
                    329: <strong>IMPORTANT NOTE:</strong>
                    330: There are a few issues relating to cryptographic software that everyone
                    331: should be aware of:
                    332: <ul>
1.20      deraadt   333: <li>The OpenBSD sources are from Canada.
                    334: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>It
                    335: is legal to export crypto software from Canada to the world.</a>
1.21      deraadt   336: <p>
1.1       deraadt   337: <li>However, if you are outside the USA or Canada, you should not
1.5       deraadt   338: fetch the cryptographic sections of the OpenBSD sources from an
                    339: anoncvs server located in the USA. The files in question are...
1.1       deraadt   340: <ul>
                    341: <li>src/kerberosIV/*
                    342: <li>src/lib/libc/crypt/crypt.c
                    343: <li>src/lib/libc/crypt/morecrypt.c
                    344: </ul>
                    345: Because of the USA ITAR munitions list,
                    346: crypto software may only be exported to Canada from the USA.
1.21      deraadt   347: <p>
                    348: <li><strong>At the moment most of the anoncvs servers are in the USA.
                    349: OpenBSD is looking for people willing to run an anoncvs servers in
                    350: Europe and other places in the world!</strong>
1.1       deraadt   351: </ul>
1.18      fn        352: </p>
                    353:
1.1       deraadt   354: <p>
1.5       deraadt   355: A sample use of an anoncvs CVS server would be:
1.1       deraadt   356: <pre>
1.12      deraadt   357: % setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
1.1       deraadt   358: % cd /tmp
                    359: % cvs get sparc
                    360: [copies the files from the repository to your machine]
                    361: % cvs log sparc/sparc/locore.s
                    362: [shows the commit log for the chosen file ]
                    363: % cvs diff -bc -r1.1 -r1.5 sparc/sparc/locore.s
                    364: [shows the changes between revisions 1.1 and rev 1.5]
                    365: </pre>
1.18      fn        366: </p>
                    367:
                    368: <p>
1.1       deraadt   369: The CVS man page (included with the CVS sources) has much more
1.18      fn        370: information about how CVS can be used.
                    371: </p>
                    372:
1.1       deraadt   373: <p>
                    374: The anoncvs service gives fledgling developers a chance to learn CVS
                    375: operation and get thoroughly involved in the development process
                    376: before getting "commit" access -- as a result of showing useful
                    377: skills and high quality results they will naturally later be given
1.18      fn        378: developer access.  As well, people providing patches can create
                    379: their "diff"s relative to the CVS tree, which will ease integration.
                    380: </p>
                    381:
                    382: <p>
                    383: The CVS client uses rsh to talk to the CVS server.  If some local
                    384: security measure like a firewall (or imperfect protocol emulators
                    385: like slirp) prevents you from using rsh, you may be able to use
                    386: <a href=http://www.cs.hut.fi/ssh>ssh</a>
                    387: instead (if you are running Solaris, there is a kernel bug which
                    388: causes problems -- contact
                    389: <a href=mailto:johns@cs.umr.edu>johns@cs.umr.edu</a>
                    390: for further details).  In this case, one sets the environment
                    391: variable <strong>CVS_RSH</strong> to point to ssh (typically
                    392: <strong>/usr/local/bin/ssh</strong>). To reduce the performance
                    393: hit the anoncvs server would take it is recommended (and requested)
                    394: that you disable encryption.  If your local site prevents you from
                    395: connecting out to port 22 (which ssh defaults to using) use port 2022.
                    396: </p>
1.5       deraadt   397:
                    398: <p>
1.1       deraadt   399: Do not be tempted to turn on compression since CVS already compresses.
                    400: Use something like the following in your <strong>$HOME/.ssh/config</strong>
                    401: file.
1.18      fn        402: </p>
1.1       deraadt   403: <pre>
1.12      deraadt   404:        Host anoncvs.usa.openbsd.org
1.1       deraadt   405:            Cipher none
                    406:            Port 2022
                    407: </pre>
1.18      fn        408:
                    409: <p>
                    410: If you wish to be a new anoncvs mirror site, please contact the anoncvs
                    411: <a href=mailto:deraadt@theos.com>maintainer</a>.
1.16      deraadt   412: Anoncvs mirrors require about 300MB of disk, and use up to 4MB of swap
1.1       deraadt   413: per anoncvs user (assuming the user does a large operation; while smaller
                    414: operations use fewer resources, anoncvs still makes much more of an
1.18      fn        415: impact than ftp or sup).  Such anoncvs machines should have excellent
                    416: network connectivity for the area they are expected to serve.  A
                    417: <a href=anoncvs.shar>document</a>
                    418: which describes the setup of anoncvs servers is available.
                    419: </p>
1.1       deraadt   420:
                    421: </dl>
                    422:
                    423: <hr>
                    424: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.41    ! deraadt   425: <br><small>$OpenBSD: index.html,v 1.40 1996/07/03 07:18:21 deraadt Exp $</small>
1.18      fn        426:
                    427: </body>
                    428: </html>