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