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