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