Annotation of www/index.html, Revision 1.49
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>
1.48 deraadt 34: <li><a href=#ftp>FTP mirrors</a>
1.22 deraadt 35: <li><a href=#snapshots>Binary snapshots</a>
36: <li><a href=#devel>How we help developers and users</a>
37: <li><a href=goals.html>OpenBSD project goals</a>
38: </ul>
39: </p>
40:
41: <h3><hr><a name=additions>Changes Relative to other *BSD's.</a></h3>
42:
43: <p>
1.1 deraadt 44: OpenBSD looks a lot like NetBSD (which it is derived from, following
45: the 4.4BSD roots), but is now being developed seperately. Good changes
46: from other free operating systems will be merged in (of course, depending
1.24 deraadt 47: on various factors like developer time for example.) OpenBSD tracks
48: NetBSD changes very closely; say anywhere between 2 days to 10 days
49: behind the state of NetBSD-current all the time. Hence you can truly
50: say that OpenBSD is NetBSD <b>PLUS MORE STUFF</b>.
1.18 fn 51: </p>
1.1 deraadt 52:
53: <p>
1.22 deraadt 54: Various additions have been made. This is only a small partial list of
1.25 deraadt 55: the major machine independent changes (ie. it is the most interesting
56: changes or what people ask about most often). Check the specific port
57: you are interested in for further details of that port -- many of them
58: have been extended too.
1.1 deraadt 59: <ul>
1.35 deraadt 60: <li>Many many NetBSD PR's fixed (which NetBSD has not yet fixed)
1.22 deraadt 61: <li>New curses library, including libform, libpanel and libmenu.
1.25 deraadt 62: <li>a termlib library which understands termcap.db, needed for new curses.
63: <li>The FreeBSD ports subsystem was integrated and is usable by you!
1.22 deraadt 64: <li>ipfilter for filtering dangerous packets
65: <li>better ELF support
1.25 deraadt 66: <li>nlist() that understands ELF, ECOFF, and a.out, allowing non-a.out ports
67: to use kvm utilies
1.22 deraadt 68: <li>Verbatim integration of the GNU tools (using a wrapper Makefile)
69: <li>All the pieces needed for cross compilation are in the source tree.
70: <li>Some LKM support in the tree.
71: <li>ATAPI support (should work on all ISA busses)
1.25 deraadt 72: <li>new scsi, md5, pkg_* commands
1.22 deraadt 73: <li>Numerous security related fixes
1.25 deraadt 74: <li>Kerberos and other crypto in the source tree that is exportable
75: <li>Solid YP master, server, and client capabilities.
1.22 deraadt 76: <li>/dev/rnd -- source of random data
1.23 deraadt 77: <li>In-kernel update(8) with an adaptive algorithm
1.25 deraadt 78: <li>Some ddb improvements and extensions
79: <li>Numerous scsi fixes
1.28 deraadt 80: <li>new system calls: rfork(), minherit(), poll().
81: <li>select() that can handle any amount of file descriptors.
1.29 deraadt 82: <li>kernfs extensions
83: <li>ATM support (support for one company's sparc & i386 cards available)
1.33 deraadt 84: <li>Boot kernels with "-c" to edit/enable/disable device configuration tables
1.38 deraadt 85: <li>pax as tar, gnutar is toast
1.42 deraadt 86: <li>using AT&T awk, gawk is toast
1.38 deraadt 87: <li>Even more security fixes.
1.47 deraadt 88: <li>Accepts FreeBSD MD5 passwords in password maps, soon will be able to
89: generate them too
1.40 deraadt 90: <li>Linux ext2fs and BSD4.4 LFS support being worked on.
1.47 deraadt 91: <li>Working ATAPI audio support.
1.1 deraadt 92: </ul>
1.18 fn 93: </p>
1.1 deraadt 94:
1.18 fn 95: <h3><hr><a name=curplat>Platforms currently supported.</a></h3>
1.1 deraadt 96:
1.18 fn 97: <p>
1.1 deraadt 98: Note: for some of these platforms, the platform-independent code may
99: be identical to that found in NetBSD because there isn't a specific
100: OpenBSD developer. For other ports the differences are significant.
101: If you find an empty page that means nothing of consequence that is
102: directly port-specific has changed from NetBSD. (Of course there are
103: differences, but they just aren't in the /sys/arch/XXXX directory).
1.18 fn 104: </p>
1.1 deraadt 105:
1.18 fn 106: <p>
1.1 deraadt 107: <dl>
1.41 deraadt 108: <dt><a href=alpha.html>Alpha</a> <dd> DEC Alpha-based machines.
109: <dt><a href=amiga.html>Amiga</a> <dd> Commodore Amiga.
110: <dt><a href=arc.html>ARC</a> <dd> ARC R4000/R4400 machines (including PICA)
111: <dt><a href=arm32.html>Arm32</a> <dd> Acorn ARM6+ computers.
112: <dt><a href=atari.html>Atari</a> <dd> Atari TT and Falcon models.
113: <dt><a href=hp300.html>HP300</a> <dd> Hewlett-Packard HP300/HP400 machines.
1.1 deraadt 114: <dt><a href=i386.html>i386</a> <dd> Your standard run-of-the-mill PC.
115: <dt><a href=mac68k.html>mac68k</a> <dd> Most MC680x0-based Apple Macintosh models.
1.41 deraadt 116: <dt><a href=mvme68k.html>MVME68K</a> <dd> Motorola MVME147/16x/17x 68K VME cards.
117: <dt><a href=pc532.html>PC532</a> <dd> A rare NS32532-based computer.
118: <dt><a href=pmax.html>Pmax</a> <dd> DEC MIPS-based machines.
119: <dt><a href=sparc.html>Sparc</a> <dd> Sun's Sun4 and sun4c models (sun4m soon!).
120: <dt><a href=sun3.html>Sun3</a> <dd> Sun's sun3 models.
121: <dt><a href=vax.html>Vax</a> <dd> DEC's VAX computers.
1.1 deraadt 122: </dl>
1.18 fn 123: </p>
124:
125: <h3><hr><a name=futplat>New platforms under development.</a></h3>
1.1 deraadt 126:
1.18 fn 127: <p>
1.1 deraadt 128: <dl>
1.10 deraadt 129: <dt><a href=mvme88k.html>mvme88k</a> <dd> Motorola MVME18x/19x 88K VME cards
1.25 deraadt 130: <dt><a href=ppc.html>ppc</a> <dd> IBM/Apple/Motorola PowerPC-based machines.
1.1 deraadt 131: </dl>
1.18 fn 132: </p>
1.1 deraadt 133:
134: <p>
135: <h3>Platforms not being developed, but which should be</h3>
1.36 deraadt 136: There is enough free code available to make porting to these
137: machines relatively easy.
1.18 fn 138: </p>
139:
140: <p>
1.1 deraadt 141: <dl>
142: <dt><a href=hppa.html>hppa</a> <dd> Hewlett-Packard PA-RISC HP700/HP800 models.
143: <dt><a href=iris.html>iris</a> <dd> SGI Iris machines.
144: </dl>
1.18 fn 145: </p>
1.1 deraadt 146:
1.26 deraadt 147:
1.49 ! deraadt 148: <hr><hr>
! 149: <h3><a name=devel>How we help developers and users.</a></h3>
! 150:
! 151: <h3><a name=ftp>FTP:</a></h4>
1.48 deraadt 152: <dd>This is a list of currently known ftp servers:<p>
153: <ul>
1.18 fn 154:
1.48 deraadt 155: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD>
156: ftp://ftp.openbsd.org/pub/OpenBSD</a><br>
157: located at Rutgers University, eastern USA.
158: <!-- deraadt@openbsd.org -->
1.18 fn 159:
1.48 deraadt 160: <li><a href=ftp://ftp.ibp.fr/pub/OpenBSD>
161: ftp://ftp.ibp.fr/pub/OpenBSD</a><br>
1.1 deraadt 162: located in France.
163: <!-- ftpmaint@ftp.ibp.fr -->
1.48 deraadt 164:
165: <li><a href=ftp://ftp.univ-evry.fr/pub/system/OpenBSD>
166: ftp://ftp.univ-evry.fr/pub/system/OpenBSD</a><br>
167: located in France.
168: <!-- mirror@ftp.univ-evry.fr -->
169:
170: <li><a href=ftp://hal.cs.umr.edu/pub/OpenBSD>
171: ftp://hal.cs.umr.edu/pub/OpenBSD</a><br>
1.1 deraadt 172: located in University of Missouri-Rolla, mid-western USA.
173: <!-- johns@cs.umr.edu -->
1.48 deraadt 174:
175: <li><a href=ftp://ftp.tut.ac.jp/OpenBSD>
176: ftp://ftp.tut.ac.jp/OpenBSD</a><br>
177: located at Toyohashi University of Technology, Aichi, JAPAN
178: <!-- Keijiro Umehara ume@ftp.tut.ac.jp -->
179:
1.1 deraadt 180: </ul>
1.48 deraadt 181:
182: <p>
183: The file structure of each FTP server is as follows:
1.18 fn 184: </p>
185:
186: <p>
1.48 deraadt 187: <strong>
188: <dl>
189: <dt>OpenBSD/snapshots/
190: <dt>OpenBSD/X11/
191: <dt>OpenBSD/src/
192: </dl>
193: </strong>
1.18 fn 194: </p>
1.1 deraadt 195:
196: <p>
1.48 deraadt 197: If you add a new FTP mirror site, please contact
198: <a href=mailto:deraadt@theos.com> the FTP maintainer</a>.
199: </p>
200:
1.49 ! deraadt 201: <h3><a name=snapshots>Binary Snapshots.</a></h3>
1.48 deraadt 202:
203: <p>
204: Snapshots will be made available from time to time in the following
205: directories. Please do not fetch binaries directly from
206: <string>cvs.openbsd.org</string>, but instead use one of these
207: mirrors.
208: </p>
209: <p>
210: The snapshots are available on each of the FTP servers listed above,
211: typically in the directory <strong>OpenBSD/snapshots</strong>.
212: You should also read the <a href=snapshots.html>general description
213: about OpenBSD snapshots</a>.
1.18 fn 214: </p>
1.1 deraadt 215:
1.18 fn 216: <p>
1.1 deraadt 217: <dl>
218: <dt><h4>Mailing Lists:</h4>
219: <dd>Some mailing lists are used for the development and use of OpenBSD.
220: In each case, send mail to
221: <a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a>
222: with a message body of "<strong>subscribe mailing-list-name</strong>".
1.18 fn 223:
1.27 deraadt 224: There is a only minimal set of mailing lists intentionally; among
225: other benefits such as more communication it reduces cross-posting.
1.26 deraadt 226: There are no private mailing lists.
227: <p>
1.1 deraadt 228: These are the mailing lists:
229: <dl>
230: <dt><strong>announce</strong>
231: <dd>important announcements. Since this is a low volume list
232: it is excellent for people who just want to follow important events.
233: <dt><strong>tech</strong>
234: <dd>technical discussions
235: <dt><strong>misc</strong>
236: <dd>user questions and answers
237: <dt><strong>source-changes</strong>
238: <dd>automated mailout of CVS source tree changes
1.18 fn 239: </dl>
240:
1.1 deraadt 241: <p>
242: For further assistance, send a message body of "<strong>help</strong>",
243: and you will receive a reply outlining all your options.
1.18 fn 244: </p>
1.1 deraadt 245:
1.26 deraadt 246: </dl>
247:
1.39 deraadt 248: <dl><h4>Bug tracking:</h4>
249: We run GNATS for tracking bugs:
250: <a href=/cgi-bin/wwwgnats.pl>Click here to enter the bug tracking system.</a>
251: </dl>
252:
1.1 deraadt 253: <dt><h4>SUP:</h4>
1.21 deraadt 254: <dd>Sorry, unlike other *BSD projects, the SUP service is not
255: available. We do not believe the SUP service to be a good tool for
256: source code access. But read below for the description of the
257: <a href="#anoncvs"><strong>anoncvs</strong> service!</a>
1.1 deraadt 258:
259: <dt><h4>CVS Access:</h4>
1.7 david 260: <dd>CVS is used to manage the OpenBSD source tree. This allows
261: developers to work on a local source tree and commit their changes when
262: ready. Also <strong>anyone</strong> can edit source files on their
263: local machines, and automatically track and merge in any changes made
264: in the OpenBSD CVS repository. Additionally they can easily see the
265: logs of, check out, or "diff" the source files in the OpenBSD source
266: tree.
1.18 fn 267:
1.1 deraadt 268: <p>
1.17 deraadt 269: The latest version of CVS is available at
270: <a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>.
271: Versions earlier than 1.6 are not recommended, and may not work.
1.18 fn 272: </p>
273:
1.17 deraadt 274: <p>
1.18 fn 275: There are two levels of source tree access:
276: </p>
1.1 deraadt 277:
278: <dl>
279: <dt><strong>Read-write access for developers</strong>
280: <dd>Developers who need to commit changes to the source tree must have
281: an account on the OpenBSD machines. Getting this access will be a
282: natural result of working on the sources with other OpenBSD developers.
1.18 fn 283: </dl>
284: </p>
1.1 deraadt 285: The OpenBSD cvs server is in Calgary, Alberta, Canada.
286: <p>
1.18 fn 287:
288: <dl>
1.21 deraadt 289: <a name="anoncvs">
1.1 deraadt 290: <dt><strong>Read-only access for everyone</strong>
1.5 deraadt 291: <dd>Anyone can access the read-only CVS repositories. These copies
292: of the read-write CVS repository are mirrored often. To use one,
293: set your <strong>CVSROOT</strong> environment variable to one of
294: the following values:
1.1 deraadt 295: <ul>
1.21 deraadt 296: <p>
1.12 deraadt 297: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
298: Host also known as <strong>anoncvs.openbsd.org</strong> and
299: <strong>eap.ccrc.wustl.edu</strong>.<br>
1.4 deraadt 300: located at Washington University, St. Louis, mid-west USA.<br>
1.21 deraadt 301: maintained by <a href=mailto:chuck@maria.wustl.edu>Chuck Cranor</a>.<br>
1.5 deraadt 302: protocols: rsh, ssh, ssh port 2022.<br>
1.21 deraadt 303: updated every 4 hours.<br>
304: <p>
1.12 deraadt 305: <li><strong>CVSROOT=anoncvs@anoncvs2.usa.openbsd.org:/cvs</strong><br>
306: Host also known as <strong>hal.cs.umr.edu</strong>.<br>
1.4 deraadt 307: located at University of Missouri-Rolla, Rolla, MO, mid-west USA.<br>
1.21 deraadt 308: maintained by <a href=mailto:johns@cs.umr.edu>John Stone</a>.<br>
1.12 deraadt 309: protocols: ssh, ssh port 2022 (<strong>NO rsh</strong>).<br>
1.21 deraadt 310: updated every 12 hours.<br>
311: <p>
312: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
313: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
314: located in London, UK.<br>
315: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
316: protocols: rsh, ssh, ssh port 2022.<br>
317: updated every 12 hours.<br>
1.43 deraadt 318: <p>
319: <li><strong>CVSROOT=anoncvs@anoncvs.tw.openbsd.org:/cvs</strong><br>
320: Host also known as <strong>hercules.secc.fju.edu.tw</strong>.<br>
321: located in Taipei, Taiwan.<br>
322: maintained by <a href=mailto:shawn@openbsd.org>Shawn Hsiao</a>.<br>
323: protocols: rsh, ssh, ssh port 2022.<br>
324: updated every 12 hours.<br>
1.1 deraadt 325: </ul>
1.21 deraadt 326: <p>
327: You may want to use `traceroute' to find out which server is nearest you.
1.1 deraadt 328: </dl>
1.18 fn 329: </p>
330:
1.1 deraadt 331: <p>
332: <strong>IMPORTANT NOTE:</strong>
333: There are a few issues relating to cryptographic software that everyone
334: should be aware of:
335: <ul>
1.20 deraadt 336: <li>The OpenBSD sources are from Canada.
337: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>It
338: is legal to export crypto software from Canada to the world.</a>
1.21 deraadt 339: <p>
1.1 deraadt 340: <li>However, if you are outside the USA or Canada, you should not
1.5 deraadt 341: fetch the cryptographic sections of the OpenBSD sources from an
342: anoncvs server located in the USA. The files in question are...
1.1 deraadt 343: <ul>
344: <li>src/kerberosIV/*
345: <li>src/lib/libc/crypt/crypt.c
346: <li>src/lib/libc/crypt/morecrypt.c
347: </ul>
348: Because of the USA ITAR munitions list,
349: crypto software may only be exported to Canada from the USA.
1.21 deraadt 350: <p>
351: <li><strong>At the moment most of the anoncvs servers are in the USA.
352: OpenBSD is looking for people willing to run an anoncvs servers in
353: Europe and other places in the world!</strong>
1.1 deraadt 354: </ul>
1.18 fn 355: </p>
356:
1.1 deraadt 357: <p>
1.5 deraadt 358: A sample use of an anoncvs CVS server would be:
1.1 deraadt 359: <pre>
1.12 deraadt 360: % setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
1.1 deraadt 361: % cd /tmp
362: % cvs get sparc
363: [copies the files from the repository to your machine]
364: % cvs log sparc/sparc/locore.s
365: [shows the commit log for the chosen file ]
366: % cvs diff -bc -r1.1 -r1.5 sparc/sparc/locore.s
367: [shows the changes between revisions 1.1 and rev 1.5]
368: </pre>
1.18 fn 369: </p>
370:
371: <p>
1.44 deraadt 372: Here is how someone using anoncvs regularily would update his
373: source tree:
374: <pre>
375: # setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
376: # cd /usr
377: # cvs -q get -PA src
378: </pre>
379: or similarily later on he might try
380: <pre>
381: # cd /usr/src
382: # cvs -q up -PAd
383: </pre>
384: Everytime you ran this it would syncronize your /usr/src tree; it would
1.46 deraadt 385: also not destroy any of your local changes. If you use obj directories
386: (not obj symbolic links) you may wish to append "-I obj" to the cvs
387: command line, this will keep cvs from spitting out a warning about all
388: the obj directories it is going to encounter which are not in the
389: repository.
1.44 deraadt 390: </p>
391:
392: <p>
1.1 deraadt 393: The CVS man page (included with the CVS sources) has much more
1.18 fn 394: information about how CVS can be used.
395: </p>
396:
1.1 deraadt 397: <p>
398: The anoncvs service gives fledgling developers a chance to learn CVS
399: operation and get thoroughly involved in the development process
400: before getting "commit" access -- as a result of showing useful
401: skills and high quality results they will naturally later be given
1.18 fn 402: developer access. As well, people providing patches can create
403: their "diff"s relative to the CVS tree, which will ease integration.
404: </p>
405:
406: <p>
407: The CVS client uses rsh to talk to the CVS server. If some local
408: security measure like a firewall (or imperfect protocol emulators
409: like slirp) prevents you from using rsh, you may be able to use
410: <a href=http://www.cs.hut.fi/ssh>ssh</a>
411: instead (if you are running Solaris, there is a kernel bug which
412: causes problems -- contact
413: <a href=mailto:johns@cs.umr.edu>johns@cs.umr.edu</a>
414: for further details). In this case, one sets the environment
415: variable <strong>CVS_RSH</strong> to point to ssh (typically
416: <strong>/usr/local/bin/ssh</strong>). To reduce the performance
417: hit the anoncvs server would take it is recommended (and requested)
418: that you disable encryption. If your local site prevents you from
419: connecting out to port 22 (which ssh defaults to using) use port 2022.
420: </p>
1.5 deraadt 421:
422: <p>
1.1 deraadt 423: Do not be tempted to turn on compression since CVS already compresses.
424: Use something like the following in your <strong>$HOME/.ssh/config</strong>
425: file.
1.18 fn 426: </p>
1.1 deraadt 427: <pre>
1.12 deraadt 428: Host anoncvs.usa.openbsd.org
1.1 deraadt 429: Cipher none
430: Port 2022
431: </pre>
1.18 fn 432:
433: <p>
434: If you wish to be a new anoncvs mirror site, please contact the anoncvs
435: <a href=mailto:deraadt@theos.com>maintainer</a>.
1.16 deraadt 436: Anoncvs mirrors require about 300MB of disk, and use up to 4MB of swap
1.1 deraadt 437: per anoncvs user (assuming the user does a large operation; while smaller
438: operations use fewer resources, anoncvs still makes much more of an
1.18 fn 439: impact than ftp or sup). Such anoncvs machines should have excellent
440: network connectivity for the area they are expected to serve. A
441: <a href=anoncvs.shar>document</a>
442: which describes the setup of anoncvs servers is available.
443: </p>
1.1 deraadt 444:
445: </dl>
446:
447: <hr>
448: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.49 ! deraadt 449: <br><small>$OpenBSD: index.html,v 1.48 1996/07/24 01:15:53 deraadt Exp $</small>
1.18 fn 450:
451: </body>
452: </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