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