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