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