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