Annotation of www/index.html, Revision 1.33
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.18 fn 144: directories:
145: </p>
146:
147: <p>
1.1 deraadt 148: <ul>
149: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD/snapshots>
150: ftp://ftp.openbsd.org/pub/OpenBSD/snapshots</a><br>
151: located at Rutgers University, eastern USA.
152: <!-- davem@openbsd.org -->
153: <li><a href=ftp://ftp.ibp.fr/pub/OpenBSD/snapshots>
154: ftp://ftp.ibp.fr/pub/OpenBSD/snapshots/</a><br>
155: located in France.
156: <!-- ftpmaint@ftp.ibp.fr -->
157: <li><a href=ftp://hal.cs.umr.edu/pub/OpenBSD/snapshots>
158: ftp://hal.cs.umr.edu/pub/OpenBSD/snapshots/</a><br>
159: located in University of Missouri-Rolla, mid-western USA.
160: <!-- johns@cs.umr.edu -->
161: </ul>
1.18 fn 162: </p>
163:
164: <p>
1.1 deraadt 165: You should also read the <a href=snapshots.html>
166: general description about OpenBSD snapshots</a>.
1.18 fn 167: </p>
1.1 deraadt 168:
169: <p>
170: The page for each platform (listed above) provides a link to the
171: specific snapshot ftp area, as well as other information you might
172: find neccessary or handy.
1.18 fn 173: </p>
1.1 deraadt 174:
1.18 fn 175: <hr>
176: <h3><a name=devel>How we help developers and users.</a></h3>
177:
178: <p>
1.1 deraadt 179: <dl>
180: <dt><h4>Mailing Lists:</h4>
181: <dd>Some mailing lists are used for the development and use of OpenBSD.
182: In each case, send mail to
183: <a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a>
184: with a message body of "<strong>subscribe mailing-list-name</strong>".
1.18 fn 185:
1.27 deraadt 186: There is a only minimal set of mailing lists intentionally; among
187: other benefits such as more communication it reduces cross-posting.
1.26 deraadt 188: There are no private mailing lists.
189: <p>
1.1 deraadt 190: These are the mailing lists:
191: <dl>
192: <dt><strong>announce</strong>
193: <dd>important announcements. Since this is a low volume list
194: it is excellent for people who just want to follow important events.
195: <dt><strong>tech</strong>
196: <dd>technical discussions
197: <dt><strong>misc</strong>
198: <dd>user questions and answers
199: <dt><strong>source-changes</strong>
200: <dd>automated mailout of CVS source tree changes
1.18 fn 201: </dl>
202:
1.1 deraadt 203: <p>
204: For further assistance, send a message body of "<strong>help</strong>",
205: and you will receive a reply outlining all your options.
1.18 fn 206: </p>
1.1 deraadt 207:
1.26 deraadt 208: </dl>
209:
1.18 fn 210: <dl><h4>FTP:</h4>
1.1 deraadt 211: <dd>This is a list of currently known ftp servers:<p>
212: <ul>
213: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD>
214: ftp://ftp.openbsd.org/pub/OpenBSD</a><br>
215: located at Rutgers University, eastern USA.
216: <!-- davem@openbsd.org -->
217: <li><a href=ftp://ftp.ibp.fr/pub/OpenBSD>
218: ftp://ftp.ibp.fr/pub/OpenBSD</a><br>
219: located in France.
220: <!-- ftpmaint@ftp.ibp.fr -->
221: <li><a href=ftp://hal.cs.umr.edu/pub/OpenBSD>
222: ftp://hal.cs.umr.edu/pub/OpenBSD</a><br>
223: located in University of Missouri-Rolla, mid-western USA.
224: <!-- johns@cs.umr.edu -->
225: </ul>
1.18 fn 226:
1.1 deraadt 227: <p>
1.18 fn 228: The file structure of the FTP servers is as follows:
229: </p>
1.1 deraadt 230:
231: <p>
1.18 fn 232: <strong>
233: <dl>
1.1 deraadt 234: <dt>pub/OpenBSD/snapshots/
235: <dt>pub/OpenBSD/src/
236: </dl>
237: </strong>
1.18 fn 238: </p>
239:
1.1 deraadt 240: <p>
241: If you add a new FTP mirror site, please contact
242: <a href=mailto:deraadt@theos.com> the FTP maintainer</a>.
1.18 fn 243: </p>
1.1 deraadt 244:
245: <dt><h4>SUP:</h4>
1.21 deraadt 246: <dd>Sorry, unlike other *BSD projects, the SUP service is not
247: available. We do not believe the SUP service to be a good tool for
248: source code access. But read below for the description of the
249: <a href="#anoncvs"><strong>anoncvs</strong> service!</a>
1.1 deraadt 250:
251: <dt><h4>CVS Access:</h4>
1.7 david 252: <dd>CVS is used to manage the OpenBSD source tree. This allows
253: developers to work on a local source tree and commit their changes when
254: ready. Also <strong>anyone</strong> can edit source files on their
255: local machines, and automatically track and merge in any changes made
256: in the OpenBSD CVS repository. Additionally they can easily see the
257: logs of, check out, or "diff" the source files in the OpenBSD source
258: tree.
1.18 fn 259:
1.1 deraadt 260: <p>
1.17 deraadt 261: The latest version of CVS is available at
262: <a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>.
263: Versions earlier than 1.6 are not recommended, and may not work.
1.18 fn 264: </p>
265:
1.17 deraadt 266: <p>
1.18 fn 267: There are two levels of source tree access:
268: </p>
1.1 deraadt 269:
270: <dl>
271: <dt><strong>Read-write access for developers</strong>
272: <dd>Developers who need to commit changes to the source tree must have
273: an account on the OpenBSD machines. Getting this access will be a
274: natural result of working on the sources with other OpenBSD developers.
1.18 fn 275: </dl>
276: </p>
1.1 deraadt 277: The OpenBSD cvs server is in Calgary, Alberta, Canada.
278: <p>
1.18 fn 279:
280: <dl>
1.21 deraadt 281: <a name="anoncvs">
1.1 deraadt 282: <dt><strong>Read-only access for everyone</strong>
1.5 deraadt 283: <dd>Anyone can access the read-only CVS repositories. These copies
284: of the read-write CVS repository are mirrored often. To use one,
285: set your <strong>CVSROOT</strong> environment variable to one of
286: the following values:
1.1 deraadt 287: <ul>
1.21 deraadt 288: <p>
1.12 deraadt 289: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
290: Host also known as <strong>anoncvs.openbsd.org</strong> and
291: <strong>eap.ccrc.wustl.edu</strong>.<br>
1.4 deraadt 292: located at Washington University, St. Louis, mid-west USA.<br>
1.21 deraadt 293: maintained by <a href=mailto:chuck@maria.wustl.edu>Chuck Cranor</a>.<br>
1.5 deraadt 294: protocols: rsh, ssh, ssh port 2022.<br>
1.21 deraadt 295: updated every 4 hours.<br>
296: <p>
1.12 deraadt 297: <li><strong>CVSROOT=anoncvs@anoncvs2.usa.openbsd.org:/cvs</strong><br>
298: Host also known as <strong>hal.cs.umr.edu</strong>.<br>
1.4 deraadt 299: located at University of Missouri-Rolla, Rolla, MO, mid-west USA.<br>
1.21 deraadt 300: maintained by <a href=mailto:johns@cs.umr.edu>John Stone</a>.<br>
1.12 deraadt 301: protocols: ssh, ssh port 2022 (<strong>NO rsh</strong>).<br>
1.21 deraadt 302: updated every 12 hours.<br>
303: <p>
304: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
305: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
306: located in London, UK.<br>
307: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
308: protocols: rsh, ssh, ssh port 2022.<br>
309: updated every 12 hours.<br>
1.1 deraadt 310: </ul>
1.21 deraadt 311: <p>
312: You may want to use `traceroute' to find out which server is nearest you.
1.1 deraadt 313: </dl>
1.18 fn 314: </p>
315:
1.1 deraadt 316: <p>
317: <strong>IMPORTANT NOTE:</strong>
318: There are a few issues relating to cryptographic software that everyone
319: should be aware of:
320: <ul>
1.20 deraadt 321: <li>The OpenBSD sources are from Canada.
322: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>It
323: is legal to export crypto software from Canada to the world.</a>
1.21 deraadt 324: <p>
1.1 deraadt 325: <li>However, if you are outside the USA or Canada, you should not
1.5 deraadt 326: fetch the cryptographic sections of the OpenBSD sources from an
327: anoncvs server located in the USA. The files in question are...
1.1 deraadt 328: <ul>
329: <li>src/kerberosIV/*
330: <li>src/lib/libc/crypt/crypt.c
331: <li>src/lib/libc/crypt/morecrypt.c
332: </ul>
333: Because of the USA ITAR munitions list,
334: crypto software may only be exported to Canada from the USA.
1.21 deraadt 335: <p>
336: <li><strong>At the moment most of the anoncvs servers are in the USA.
337: OpenBSD is looking for people willing to run an anoncvs servers in
338: Europe and other places in the world!</strong>
1.1 deraadt 339: </ul>
1.18 fn 340: </p>
341:
1.1 deraadt 342: <p>
1.5 deraadt 343: A sample use of an anoncvs CVS server would be:
1.1 deraadt 344: <pre>
1.12 deraadt 345: % setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
1.1 deraadt 346: % cd /tmp
347: % cvs get sparc
348: [copies the files from the repository to your machine]
349: % cvs log sparc/sparc/locore.s
350: [shows the commit log for the chosen file ]
351: % cvs diff -bc -r1.1 -r1.5 sparc/sparc/locore.s
352: [shows the changes between revisions 1.1 and rev 1.5]
353: </pre>
1.18 fn 354: </p>
355:
356: <p>
1.1 deraadt 357: The CVS man page (included with the CVS sources) has much more
1.18 fn 358: information about how CVS can be used.
359: </p>
360:
1.1 deraadt 361: <p>
362: The anoncvs service gives fledgling developers a chance to learn CVS
363: operation and get thoroughly involved in the development process
364: before getting "commit" access -- as a result of showing useful
365: skills and high quality results they will naturally later be given
1.18 fn 366: developer access. As well, people providing patches can create
367: their "diff"s relative to the CVS tree, which will ease integration.
368: </p>
369:
370: <p>
371: The CVS client uses rsh to talk to the CVS server. If some local
372: security measure like a firewall (or imperfect protocol emulators
373: like slirp) prevents you from using rsh, you may be able to use
374: <a href=http://www.cs.hut.fi/ssh>ssh</a>
375: instead (if you are running Solaris, there is a kernel bug which
376: causes problems -- contact
377: <a href=mailto:johns@cs.umr.edu>johns@cs.umr.edu</a>
378: for further details). In this case, one sets the environment
379: variable <strong>CVS_RSH</strong> to point to ssh (typically
380: <strong>/usr/local/bin/ssh</strong>). To reduce the performance
381: hit the anoncvs server would take it is recommended (and requested)
382: that you disable encryption. If your local site prevents you from
383: connecting out to port 22 (which ssh defaults to using) use port 2022.
384: </p>
1.5 deraadt 385:
386: <p>
1.1 deraadt 387: Do not be tempted to turn on compression since CVS already compresses.
388: Use something like the following in your <strong>$HOME/.ssh/config</strong>
389: file.
1.18 fn 390: </p>
1.1 deraadt 391: <pre>
1.12 deraadt 392: Host anoncvs.usa.openbsd.org
1.1 deraadt 393: Cipher none
394: Port 2022
395: </pre>
1.18 fn 396:
397: <p>
398: If you wish to be a new anoncvs mirror site, please contact the anoncvs
399: <a href=mailto:deraadt@theos.com>maintainer</a>.
1.16 deraadt 400: Anoncvs mirrors require about 300MB of disk, and use up to 4MB of swap
1.1 deraadt 401: per anoncvs user (assuming the user does a large operation; while smaller
402: operations use fewer resources, anoncvs still makes much more of an
1.18 fn 403: impact than ftp or sup). Such anoncvs machines should have excellent
404: network connectivity for the area they are expected to serve. A
405: <a href=anoncvs.shar>document</a>
406: which describes the setup of anoncvs servers is available.
407: </p>
1.1 deraadt 408:
409: </dl>
410:
411: <hr>
412: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.33 ! deraadt 413: <br><small>$OpenBSD: index.html,v 1.32 1996/06/24 20:30:36 deraadt Exp $</small>
1.18 fn 414:
415: </body>
416: </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