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