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