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