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