Annotation of www/index.html, Revision 1.1
1.1 ! deraadt 1: <http>
! 2: <head>
! 3: <title>OpenBSD</title>
! 4: </head>
! 5: <h2>OpenBSD</h2>
! 6:
! 7: <hr>
! 8: The OpenBSD project involves continuing development of a multiplatform
! 9: 4.4BSD-based Unix-like operating system.
! 10:
! 11: <p>
! 12: OpenBSD looks a lot like NetBSD (which it is derived from, following
! 13: the 4.4BSD roots), but is now being developed seperately. Good changes
! 14: from other free operating systems will be merged in (of course, depending
! 15: on various factors like developer time for example.)
! 16:
! 17: <p>
! 18: <ul>
! 19: <li><a href=#curplat>Supported platforms</a>
! 20: <li><a href=#futplat>New platforms under development</a>
! 21: <li><a href=#snapshots>Binary snapshots</a>
! 22: <li><a href=#devel>How we help developers and users</a>
! 23: </ul>
! 24:
! 25: <a name=curplat>
! 26: <h3><hr>Platforms currently supported.</h3>
! 27:
! 28: Note: for some of these platforms, the platform-independent code may
! 29: be identical to that found in NetBSD because there isn't a specific
! 30: OpenBSD developer. For other ports the differences are significant.
! 31: If you find an empty page that means nothing of consequence that is
! 32: directly port-specific has changed from NetBSD. (Of course there are
! 33: differences, but they just aren't in the /sys/arch/XXXX directory).
! 34:
! 35: <dl>
! 36: <dt><a href=alpha.html>alpha</a> <dd> DEC Alpha-based machines.
! 37: <dt><a href=amiga.html>amiga</a> <dd> Commodore Amiga.
! 38: <dt><a href=atari.html>atari</a> <dd> Atari TT and Falcon models.
! 39: <dt><a href=hp300.html>hp300</a> <dd> Hewlett-Packard HP300/HP400 machines.
! 40: <dt><a href=i386.html>i386</a> <dd> Your standard run-of-the-mill PC.
! 41: <dt><a href=mac68k.html>mac68k</a> <dd> Most MC680x0-based Apple Macintosh models.
! 42: <dt><a href=mvme68k.html>mvme68k</a> <dd> Motorola MVME147/16x/17x MC680[346]0-based VME cards.
! 43: <dt><a href=pc532.html>pc532</a> <dd> A rare NS32532-based computer.
! 44: <dt><a href=pmax.html>pmax</a> <dd> DEC MIPS-based machines.
! 45: <dt><a href=sparc.html>sparc</a> <dd> Sun's Sun4 and sun4c models (sun4m soon!).
! 46: <dt><a href=sun3.html>sun3</a> <dd> Sun's sun3 models.
! 47: <dt><a href=vax.html>vax</a> <dd> DEC's VAX computers.
! 48: </dl>
! 49:
! 50: <a name=futplat>
! 51: <h3><hr>New platforms under development.</h3>
! 52: <dl>
! 53: <dt><a href=arm32.html>arm32</a> <dd> Acorn ARM6+ computers.
! 54: <dt><a href=mvme88k.html>mvme88k</a> <dd> Motorola MVME18x/19x MC88xxx-based VME cards
! 55: <dt><a href=pica.html>pica</a> <dd> Acer PICA R4400
! 56: </dl>
! 57:
! 58: <p>
! 59: <h3>Platforms not being developed, but which should be</h3>
! 60: Either there is enough free code available to make porting to these
! 61: machines relatively easy, or it's a port which should be done.
! 62: <dl>
! 63: <dt><a href=hppa.html>hppa</a> <dd> Hewlett-Packard PA-RISC HP700/HP800 models.
! 64: <dt><a href=iris.html>iris</a> <dd> SGI Iris machines.
! 65: <dt><a href=ppc.html>ppc</a> <dd> various IBM, Apple, and Motorola PowerPC-based machines.
! 66: </dl>
! 67:
! 68: <a name=snapshots>
! 69: <h3><hr>Binary Snapshots.</h3>
! 70: Snapshots will be made available from time to time in the following
! 71: directories:<p>
! 72: <ul>
! 73: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD/snapshots>
! 74: ftp://ftp.openbsd.org/pub/OpenBSD/snapshots</a><br>
! 75: located at Rutgers University, eastern USA.
! 76: <!-- davem@openbsd.org -->
! 77: <li><a href=ftp://ftp.ibp.fr/pub/OpenBSD/snapshots>
! 78: ftp://ftp.ibp.fr/pub/OpenBSD/snapshots/</a><br>
! 79: located in France.
! 80: <!-- ftpmaint@ftp.ibp.fr -->
! 81: <li><a href=ftp://hal.cs.umr.edu/pub/OpenBSD/snapshots>
! 82: ftp://hal.cs.umr.edu/pub/OpenBSD/snapshots/</a><br>
! 83: located in University of Missouri-Rolla, mid-western USA.
! 84: <!-- johns@cs.umr.edu -->
! 85: </ul>
! 86: You should also read the <a href=snapshots.html>
! 87: general description about OpenBSD snapshots</a>.
! 88:
! 89: <p>
! 90: The page for each platform (listed above) provides a link to the
! 91: specific snapshot ftp area, as well as other information you might
! 92: find neccessary or handy.
! 93:
! 94: <a name=devel>
! 95: <h3><hr>How we help developers and users.</h3>
! 96: We are moving quickly to setup `infrastructure'... as things get working
! 97: this section will be updated.
! 98:
! 99: <dl>
! 100: <dt><h4>Mailing Lists:</h4>
! 101: <dd>Some mailing lists are used for the development and use of OpenBSD.
! 102: In each case, send mail to
! 103: <a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a>
! 104: with a message body of "<strong>subscribe mailing-list-name</strong>".
! 105: <p>
! 106: These are the mailing lists:
! 107: <dl>
! 108: <dt><strong>announce</strong>
! 109: <dd>important announcements. Since this is a low volume list
! 110: it is excellent for people who just want to follow important events.
! 111: <dt><strong>tech</strong>
! 112: <dd>technical discussions
! 113: <dt><strong>misc</strong>
! 114: <dd>user questions and answers
! 115: <dt><strong>source-changes</strong>
! 116: <dd>automated mailout of CVS source tree changes
! 117: </ul>
! 118: <p>
! 119: For further assistance, send a message body of "<strong>help</strong>",
! 120: and you will receive a reply outlining all your options.
! 121:
! 122: <dt><h4>FTP:</h4>
! 123: <dd>This is a list of currently known ftp servers:<p>
! 124: <ul>
! 125: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD>
! 126: ftp://ftp.openbsd.org/pub/OpenBSD</a><br>
! 127: located at Rutgers University, eastern USA.
! 128: <!-- davem@openbsd.org -->
! 129: <li><a href=ftp://ftp.ibp.fr/pub/OpenBSD>
! 130: ftp://ftp.ibp.fr/pub/OpenBSD</a><br>
! 131: located in France.
! 132: <!-- ftpmaint@ftp.ibp.fr -->
! 133: <li><a href=ftp://hal.cs.umr.edu/pub/OpenBSD>
! 134: ftp://hal.cs.umr.edu/pub/OpenBSD</a><br>
! 135: located in University of Missouri-Rolla, mid-western USA.
! 136: <!-- johns@cs.umr.edu -->
! 137: </ul>
! 138: <p>
! 139:
! 140: The file structure of the FTP servers is as follows:
! 141: <p>
! 142: <strong><dl>
! 143: <dt>pub/OpenBSD/snapshots/
! 144: <dt>pub/OpenBSD/src/
! 145: </dl>
! 146: </strong>
! 147: <p>
! 148:
! 149: If you add a new FTP mirror site, please contact
! 150: <a href=mailto:deraadt@theos.com> the FTP maintainer</a>.
! 151:
! 152: <dt><h4>SUP:</h4>
! 153: <dd>Sorry, SUP is not ready for use yet.
! 154:
! 155: <dt><h4>CVS Access:</h4>
! 156: <dd>CVS is used to manage the OpenBSD source tree. This allows developers
! 157: to edit source files on their local machines, but have the OpenBSD CVS
! 158: repository track the changes. It is also easy for <strong>anyone</strong>
! 159: to see the logs of, check out, or "diff" the source files in the OpenBSD
! 160: source tree.
! 161: <p>
! 162:
! 163: CVS is available at <a href=ftp://prep.ai.mit.edu/pub/gnu/cvs-1.6.tar.gz>
! 164: ftp://prep.ai.mit.edu/pub/gnu/cvs-1.6.tar.gz</a>. Versions earlier
! 165: than 1.6 are not recommended, and may not work.<p>
! 166:
! 167: There are two levels of source tree access:<p>
! 168:
! 169: <dl>
! 170: <dt><strong>Read-write access for developers</strong>
! 171: <dd>Developers who need to commit changes to the source tree must have
! 172: an account on the OpenBSD machines. Getting this access will be a
! 173: natural result of working on the sources with other OpenBSD developers.
! 174: <p>
! 175: The OpenBSD cvs server is in Calgary, Alberta, Canada.
! 176: <p>
! 177: <dt><strong>Read-only access for everyone</strong>
! 178: <dd>Anyone can access the read-only CVS repository. This copy of the
! 179: read-write CVS repository is mirrored twice daily. To use it, set
! 180: your <strong>CVSROOT</strong> environment variable to one of the
! 181: following values:
! 182: <p>
! 183: <ul>
! 184: <li><strong>CVSROOT=anoncvs@anoncvs.openbsd.org:/cvs</strong><br>
! 185: located at Washington University, St. Louis, mid-west USA.
! 186: </ul>
! 187: </dl>
! 188: <p>
! 189: <strong>IMPORTANT NOTE:</strong>
! 190: There are a few issues relating to cryptographic software that everyone
! 191: should be aware of:
! 192: <ul>
! 193: <li>The OpenBSD sources are from Canada. It is legal to export crypto
! 194: software from Canada to the world.
! 195: <li>However, if you are outside the USA or Canada, you should not
! 196: fetch the cryptographic sections of the OpenBSD sources from a cvs
! 197: or anoncvs server located in the USA. The files in question are...
! 198: <ul>
! 199: <li>src/kerberosIV/*
! 200: <li>src/lib/libc/crypt/crypt.c
! 201: <li>src/lib/libc/crypt/morecrypt.c
! 202: </ul>
! 203: Because of the USA ITAR munitions list,
! 204: crypto software may only be exported to Canada from the USA.
! 205: <li><strong>At the moment the only anoncvs server is in the USA.
! 206: OpenBSD is looking for people willing to run an anoncvs server in Europe!</strong>
! 207: </ul>
! 208: <p>
! 209: A sample use of the anoncvs CVS server would be:
! 210: <pre>
! 211: % setenv CVSROOT anoncvs@anoncvs.openbsd.org:/cvs
! 212: % cd /tmp
! 213: % cvs get sparc
! 214: [copies the files from the repository to your machine]
! 215: % cvs log sparc/sparc/locore.s
! 216: [shows the commit log for the chosen file ]
! 217: % cvs diff -bc -r1.1 -r1.5 sparc/sparc/locore.s
! 218: [shows the changes between revisions 1.1 and rev 1.5]
! 219: </pre>
! 220: The CVS man page (included with the CVS sources) has much more
! 221: information about how CVS can be used.<p>
! 222: <p>
! 223: The anoncvs service gives fledgling developers a chance to learn CVS
! 224: operation and get thoroughly involved in the development process
! 225: before getting "commit" access -- as a result of showing useful
! 226: skills and high quality results they will naturally later be given
! 227: developer access.
! 228: As well, people providing patches can create their "diff"s relative
! 229: to the CVS tree, which will ease integration.<p>
! 230:
! 231: <p>
! 232: The CVS client uses rsh to talk to the CVS server.
! 233: If some local security measure like a firewall (or imperfect protocol
! 234: emulators like slirp) prevents you from using rsh, you may be able
! 235: to use <a href=http://www.cs.hut.fi/ssh>ssh</a> instead. In this
! 236: case, one sets the environment variable <strong>CVS_RSH</strong>
! 237: to point to ssh (typically <strong>/usr/local/bin/ssh</strong>).
! 238: To reduce the performance hit the anoncvs server would take it is
! 239: recommended (and requested) that you disable encryption. If your local
! 240: site prevents you from connecting out to port 22 (which ssh defaults to
! 241: using) use port 2022.
! 242: Do not be tempted to turn on compression since CVS already compresses.
! 243: Use something like the following in your <strong>$HOME/.ssh/config</strong>
! 244: file.
! 245: <pre>
! 246: Host anoncvs.openbsd.org
! 247: Cipher none
! 248: Port 2022
! 249: </pre>
! 250: If you wish to be a new anoncvs mirror site, please contact
! 251: <a href=mailto:deraadt@theos.com>the anoncvs maintainer</a>.
! 252: Anoncvs mirrors require about 250MB of disk, and use up to 8MB of swap
! 253: per anoncvs user (assuming the user does a large operation; while smaller
! 254: operations use fewer resources, anoncvs still makes much more of an
! 255: impact than ftp or sup). Such anoncvs machines should have excellent
! 256: network connectivity for the area they are expected to serve.<p>
! 257:
! 258: </dl>
! 259:
! 260: <hr>
! 261: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
![[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