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