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