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