Annotation of www/33.html, Revision 1.2
1.1 miod 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <title>OpenBSD 3.3 Release</title>
5: <link rev=made href="mailto:www@openbsd.org">
6: <meta name="resource-type" content="document">
7: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
8: <meta name="description" content="OpenBSD 3.3">
9: <meta name="keywords" content="openbsd,main">
10: <meta name="distribution" content="global">
11: <meta name="copyright" content="This document copyright 2003 by OpenBSD.">
12: </head>
13:
14: <body bgcolor="#ffffff" text="#000000" link="#24248E">
15:
16: <a href="index.html">
17: <img alt="[OpenBSD]" height="30" width="141" hspace="24" src="images/smalltitle.gif" border="0"></a>
18: <hr>
19:
20: <p>
21: <a href="images/BePatientAndDontAngerTheFishGuys.gif">
22: <img align="left" width="255" height="323" hspace="24"
23: src="images/BePatientAndDontAngerTheFishGuys.gif" alt="OpenBSD 3.3 logo"></a>
24: <h2><font color="#0000e0">The OpenBSD 3.3 Release:</font></h2>
25: <p>
26:
27: Released May 1, 2003<br>
28: Copyright 1997-2003, Theo de Raadt.<br>
29: <font color="#e00000">ISBN 0-9731791-1-2</font>
30: <p>
31:
32: <a href="#new">What's New</a><br>
33: <a href="#install">How to install</a><br>
34: <a href="#ports">How to use the ports tree</a><br>
35: <a href="orders.html">Ordering a CD set</a><br>
36:
37: <p>
38: <h3><font color="#0000e0">
39: To get the files for this release:
40: <ul>
41: <li>Order a CDROM from our <a href="orders.html">ordering system</a>.
42: <li>See the information on <a href="ftp.html">The FTP page</a> for
43: a list of mirror machines.
44: <li>Go to the <font color="#e00000">pub/OpenBSD/3.3/</font> directory on
45: one of the mirror sites.
46: <li>Briefly read the rest of this document.
47: <!-- change to errata33.html when available -->
48: <li>Have a look at <a href="errata.html">The 3.3 Errata page</a> for a list
49: of bugs and workarounds.
50: <!-- change ALL refs to plus.html to plus33.html when available -->
51: <li>See a <a href="plus.html">detailed log of changes</a> between the
52: 3.2 and 3.3 releases.
53: </ul>
54: </font></h3>
55: <br clear=all>
56: <br>
57: <p>
58:
59: <strong>Note:</strong> All applicable copyrights and credits can be found
60: in the applicable file sources found in the files src.tar.gz, srcsys.tar.gz,
61: XF4.tar.gz, or in the files fetched via ports.tar.gz. The distribution
62: files used to build packages from the ports.tar.gz file are not included on
63: the CDROM because of lack of space.
64: <p>
65:
66: <a name="new"></a>
67: <hr>
68: <p>
69: <h3><font color="#0000e0">What's New</font></h3>
70: <p>
71: This is a partial list of new features and systems included in OpenBSD 3.3.
72: For a comprehensive list, see the <a href="plus.html">changelog</a> leading
73: to 3.3.
74: <p>
75:
76: <ul>
77: <li>Integration of the
78: <a href="http://www.trl.ibm.com/projects/security/ssp">ProPolice</a>
79: stack protection technology into the system compiler. This protection is
80: enabled by default.
1.2 ! deraadt 81: <p>
1.1 miod 82:
83: <li>W^X (pronounced: "W or X") binaries on ELF architectures. This is
84: a fine-grained memory permissions layout, ensuring that memory which can be
85: written to by application programs can not be executable at the same time.
86: This raises the bar on potential buffer overflows and other attacks.
87: <p>
88:
1.2 ! deraadt 89: <li>Still more reduction in setuid and setgid binaries, and more chroot
! 90: use throughout the system.
1.1 miod 91: <p>
92:
93: <li>The X window system uses privilege separation, for better security.
94: <p>
95:
96: <li>As usual, improvements to the documentation, notably the man pages and
97: the Web FAQ. An always larger part of the website is available in several
98: languages.
99: <p>
100:
101: <li>More complete collection and better tested set of "ports".
102: setuid/setgid ports have been significantly reduced as well. Many of the
103: ones that remain setuid have been modified to revoke privileges as early
104: as possible.
105: <p>
106:
107: <li>Over 2000 pre-built and tested packages.
108: <p>
109:
110: <li>Significant improvements to the pthread library.
111: <p>
112:
113: <!-- PF Twins! Please fill this! -->
114: <li>An incredible amount of enhancements and stability improvements to
115: our packet filter, <a
116: href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&sektion=4">pf</a>,
117: which will be detailed here shortly.
118: <!--
119: <ul>
120: <li>anchors
121: <li>spamd
122: <li>etc
123: </ul>
124: -->
125: <p>
126:
127: <li>The system includes the following major components from outside suppliers:
128: <p>
129: <ul>
130: <li>XFree86 4.2.1 (and i386 contains 3.3.X servers also, thus providing support for all chipsets)
131: <li>gcc 2.95.3 (+ patches)
132: <li>perl 5.8.0 (+ patches)
133: <li>Apache 1.3.27, mod_ssl 2.8.11, DSO support
134: <li>OpenSSL 0.9.7beta3 (+ patches)
135: <li>groff 1.15
136: <li>sendmail 8.12.8
137: <li>lynx 2.8.2rel.1 with HTTPS support added
138: <li>sudo 1.6.7
139: <li>ncurses 5.2
140: <li>Latest KAME IPv6
141: <li>KTH Kerberos 1.0.8
142: <li>Heimdal 0.4e (+ patches)
143: <li>OpenSSH 3.6
144: </ul>
145: <p>
146:
147: <li>Many improvements for security and reliability (look for the red
148: print in the <a href="plus.html">complete changelog</a>).
149: <p>
150: </ul>
151:
152: <a name="install"></a>
153: <hr>
154: <p>
155: <h3><font color="#0000e0">How to install</font></h3>
156: <p>
157: Following this are the instructions which you would have on a piece of
158: paper if you had purchased a CDROM set instead of doing an alternate
159: form of install. The instructions for doing an ftp (or other style
160: of) install are very similar; the CDROM instructions are left intact
161: so that you can see how much easier it would have been if you had
162: purchased a CDROM instead.
163: <p>
164:
165: <hr>
166: Please refer to the following files on the three CDROMs for extensive
167: details on how to install OpenBSD 3.3 on your machine:
168: <p>
169: <ul>
170: <li> CD1:3.3/i386/INSTALL.i386
171: <p>
172: <li> CD2:3.3/macppc/INSTALL.macppc
173: <li> CD2:3.3/vax/INSTALL.vax
174: <p>
175: <li> CD3:3.3/sparc/INSTALL.sparc
176: <li> CD3:3.3/sparc64/INSTALL.sparc64
177: </ul>
178: <hr>
179:
180: <p>
181: Quick installer information for people familiar with OpenBSD, and the
182: use of the "disklabel -E" command. If you are at all confused when
183: installing OpenBSD, read the relevant INSTALL.* file as listed above!
184: <p>
185:
186: <h3><font color="#e00000">OpenBSD/i386:</font></h3>
187: <ul>
188: Play with your BIOS options to enable booting from a CD. The OpenBSD/i386
189: release is on CD1. If your BIOS does not support booting from CD, you will need
190: to create a boot floppy to install from. To create a boot floppy write
191: <i>CD1:3.3/i386/floppy33.fs</i> to a floppy and boot via the floppy drive.
192:
193: <p>
194: Use <i>CD1:3.3/i386/floppyB33.fs</i> instead for greater scsi controller
195: support, or <i>CD1:3.3/i386/floppyC33.fs</i> for better laptop support.
196:
197: <p>
198: If you are planning on dual booting OpenBSD with another OS, you will need to read the included INSTALL.i386 document.
199:
200: <p>
201: To make a boot floppy under MS-DOS, use the "rawrite" utility located
202: at <i>CD:/3.3/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS, use the <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dd&sektion=1">dd(1)</a> utility. The following is an example usage of <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dd&sektion=1">dd(1)</a>, where the device could be "floppy", "rfd0c", or "rfd0a".
203:
204: <ul><pre>
205: # <strong>dd if=<file> of=/dev/<device> bs=32k</strong>
206: </pre></ul>
207:
208: <p>
209: Make sure you use properly formatted perfect floppies with NO BAD BLOCKS or your install will most likely fail. For more information on creating a boot floppy and installing OpenBSD/i386 please refer to <a href="faq/faq4.html#4.1">FAQ4.1</a>.
210: </ul>
211:
212: <p>
213: <h3><font color="#e00000">OpenBSD/macppc:</font></h3>
214: <ul>
215: Put the CD2 in your CDROM drive and poweron your machine while holding down the
216: <i>C</i> key until the display turns on and shows <i>OpenBSD/macppc boot</i>.
217:
218: <p>
219: Alternatively, at the Open Firmware prompt, enter <i>boot cd:,ofwboot
220: /3.3/macppc/bsd.rd</i>
221: </ul>
222:
223: <p>
224: <h3><font color="#e00000">OpenBSD/vax:</font></h3>
225: <ul>
226: Boot over the network via mopbooting as described in INSTALL.vax.
227: </ul>
228:
229: <p>
230: <h3><font color="#e00000">OpenBSD/sparc:</font></h3>
231: <ul>
232: The 3.3 release of OpenBSD/sparc is located on CD3. To boot off of this CD you can use one of the two commands listed below, depending on the version of your ROM.
233:
234: <ul><pre>
235: > <strong>boot cdrom 3.3/sparc/bsd.rd</strong>
236: or
237: > <strong>b sd(0,6,0)3.3/sparc/bsd.rd</strong>
238: </pre></ul>
239:
240: <p>
241: If your sparc does not have a CD drive, you can alternatively boot from floppy.
242: To do so you need to write "CD3:3.3/sparc/floppy33.fs" to a floppy. For more information see <a href="faq/faq4.html#4.1">FAQ4.1</a>. To boot from the floppy use one of the two commands listed below, depending on the version of your ROM.
243:
244: <ul><pre>
245: > <strong>boot floppy</strong>
246: or
247: > <strong>boot fd()</strong>
248: </pre></ul>
249:
250: <p>
251: Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail.
252:
253: <p>
254: If your sparc doesn't have a floppy drive nor a CD drive, you can either
255: setup a bootable tape, or install via network, as told in the
256: INSTALL.sparc file.
257: </ul>
258:
259: <p>
260: <h3><font color="#e00000">OpenBSD/sparc64:</font></h3>
261: <ul>
262: Put the CD3 in your CDROM drive and type <i>boot cdrom</i>.
263:
264: <p>
265: If this doesn't work, or if you don't have a CDROM drive, you can write
266: <i>CD3:3.3/sparc64/floppy33.fs</i> to a floppy and boot it with <i>boot
267: floppy</i>.<br>
268: Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail.
269:
270: <p>
271: You can also write <i>CD3:3.3/sparc64/miniroot33.fs</i> to the swap partition on
272: the disk and boot with <i>boot disk:b</i>.
273:
274: <p>
275: If nothing works, you can boot over the network as described in INSTALL.sparc64
276: </ul>
277:
278: <p>
279: <h3><font color="#e00000">Notes about the source code:</font></h3>
280: <ul>
281: src.tar.gz contains a source archive starting at /usr/src. This file
282: contains everything you need except for the kernel sources, which are
283: in a separate archive. To extract:
284: <p>
285: <ul><pre>
286: # <strong>mkdir -p /usr/src</strong>
287: # <strong>cd /usr/src</strong>
288: # <strong>tar xvfz /tmp/src.tar.gz</strong>
289: </pre></ul>
290: <p>
291: srcsys.tar.gz contains a source archive starting at /usr/src/sys.
292: This file contains all the kernel sources you need to rebuild kernels.
293: To extract:
294: <p>
295: <ul><pre>
296: # <strong>mkdir -p /usr/src/sys</strong>
297: # <strong>cd /usr/src</strong>
298: # <strong>tar xvfz /tmp/srcsys.tar.gz</strong>
299: </pre></ul>
300: <p>
301: Both of these trees are a regular CVS checkout. Using these trees it
302: is possible to get a head-start on using the anoncvs servers as
303: described at <a href="anoncvs.html">http://www.OpenBSD.org/anoncvs.html</a>.
304: Using these files
305: results in a much faster initial CVS update than you could expect from
306: a fresh checkout of the full OpenBSD source tree.
307: <p>
308: </ul>
309: <a name="ports"></a>
310: <hr>
311: <p>
312: <h3><font color="#0000e0">Ports Tree</font></h3>
313: <p>
314: A ports tree archive is also provided. To extract:
315: <p>
316: <ul><pre>
317: # <strong>cd /usr</strong>
318: # <strong>tar xvfz /tmp/ports.tar.gz</strong>
319: # <strong>cd ports</strong>
320: </pre></ul>
321: <p>
322: The <i>ports/</i> subdirectory is a checkout of the OpenBSD ports tree. Go
323: read <a href="ports.html">http://www.OpenBSD.org/ports.html</a>
324: if you know nothing about ports
325: at this point. This text is not a manual of how to use ports.
326: Rather, it is a set of notes meant to kickstart the user on the
327: OpenBSD ports system.
328: <p>
329: Certainly, the OpenBSD ports system is not complete. It is doubtful it
330: will ever be. However, it is growing very fast and getting more stable.
331: Almost all ports provided with this release should build without problems
332: on most architectures (over 2000 packages build on i386, for instance).
333: <p>
334: The <i>ports/</i> directory represents a CVS (see the manpage for
335: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&apropos=0&sektion=1&manpath=OpenBSD+Current&arch=i386&format=html">
336: cvs(1)</a> if
337: you aren't familiar with CVS) checkout of our ports. As with our complete
338: source tree, our ports tree is available via anoncvs. So, in
339: order to keep current with it, you must make the <i>ports/</i> tree
340: available on a read-write medium and update the tree with a command
341: like:
342: <p>
343: <ul><pre>
344: # <strong>cd [portsdir]/; cvs -d anoncvsserver.openbsd.org:/cvs update -Pd -rOPENBSD_3.3</strong>
345: </pre></ul>
346: <p>
347: [Of course, you must replace the local directory and server name here
348: with the location of your ports collection and a nearby anoncvs
349: server.]
350: <p>
351: Note that most ports are available as packages through ftp. Updated
352: packages for the 3.3 release will be made available if problems arise.
353: <p>
354: If you're interested in seeing a port added, would like to help out, or just
355: would like to know more, the mailing list ports@openbsd.org is a good
356: place to know.
357: <p>
358:
359: <hr>
360: <a href="index.html"><img height="24" width="24" src="back.gif" border="0"
361: alt="OpenBSD"></a>
362: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
363: <br><small>
1.2 ! deraadt 364: $OpenBSD: 33.html,v 1.1 2003/03/25 21:50:10 miod Exp $
1.1 miod 365: </small>
366:
367: </body>
368: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to 33.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www