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