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