Annotation of www/26.html, Revision 1.2
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
4: <title>OpenBSD 2.6 Release</title>
5: <link rev=made href=mailto:www@openbsd.org>
6: <meta name="resource-type" content="document">
7: <meta name="description" content="the main OpenBSD page">
8: <meta name="keywords" content="openbsd,main">
9: <meta name="distribution" content="global">
10: <meta name="copyright" content="This document copyright 1999 by OpenBSD.">
11: </head>
12:
13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#24248E">
14:
15: <img alt="[OpenBSD]" height=30 width=141 src="images/smalltitle.gif">
16: <hr>
17:
1.2 ! louis 18: <a name=top></a>
! 19:
1.1 deraadt 20: <p>
21: <a href=images/fishbowl_sm.jpg><img align=left src=images/fishbowl_sm.jpg></a>
22: <h2><font color=#0000e0>The OpenBSD 2.6 Release:</font></h2>
23: <p>
24:
25: Released December 1, 1999.<br>
26: Copyright 1997-1999, Theo de Raadt.
27: <p>
28:
1.2 ! louis 29: <a href=#new>What's New</a>
! 30:
! 31: <p>
1.1 deraadt 32: <a href=orders.html>To order a 2.6 CDROM, click here.</a>
33:
34: <h3><font color=#0000e0>
35: To get the files for this release:
36: <ul>
37: <li><strong>Order a CDROM from our ordering system.</strong>
38: If you want to try to get a bookstore local to you to carry it,
39: have them order<br>
40: <font color=#e00000>ISBN 0-9683637-4-1</font>.
41: <li>See the information on <a href=ftp.html>The FTP page</a> for
42: a list of mirror machines
43: <li>Go to the <font color=#e00000>pub/OpenBSD/2.6/</font> directory on
44: one of the mirror sites
45: <li>Briefly read the rest of this document.
46: <li>Have a look at <a href=errata.html>The 2.6 Errata page</a> for a list
47: of bugs and workarounds.
48: </ul>
49: </font></h3>
50: <br clear=all>
51: <br>
52: <p>
53:
54: All applicable copyrights and credits can be found in the applicable
55: file sources found in the files src.tar.gz and srcsys.tar.gz.
56: <p>
57: Following this are the instructions which you would have on a piece of
58: paper if you had purchased a CDROM set
59: from <a href=orders.html>http://www.OpenBSD.org/orders.html</a>,
60: instead of doing an alternate form of install. The instructions for
61: doing an ftp (or other style of) install are very similar; the CDROM
62: instructions are left intact so that you can see how much easier it
63: would have been if you had purchased a CDROM instead.
64: <p>
65: <hr>
66: Please refer to the following files on the two CDROM's for extensive
67: details on how to install OpenBSD 2.6 on your machine:
68: <p>
69: <dl>
70: <li> CD1:2.6/i386/INSTALL.i386
71: <li> CD1:2.6/sparc/INSTALL.sparc
72: <p>
73: <li> CD2:2.6/alpha/INSTALL.alpha
74: <li> CD2:2.6/amiga/INSTALL.amiga
75: <li> CD2:2.6/mac68k/INSTALL.mac68k
76: <li> CD2:2.6/hp300/INSTALL.hp300
77: <p>
78: <li>A pmax release is available on the ftp sites, but not on the CDs.
79: </dl>
80: <hr>
81: <p>
82: Quick installer information for people familiar with OpenBSD, and the
83: use of the new "disklabel -E" command. If you are at all confused when
84: installing OpenBSD, read the relevant INSTALL.* file as listed above!
85: <p>
86: <h3><font color=#e00000>i386:</font></h3>
87: <p>
88: Play with your BIOS options, and see if you can enable booting off a
89: CD; try using CD1. If not, write CD1:2.6/i386/floppy26.fs to a
90: floppy, then boot that. If you are mixing OpenBSD with another
91: operating system, you will surely need to read the INSTALL.i386
92: document.
93: <p>
94: To make a floppy under MS-DOS, use /2.6/tools/rawrite.exe. Under
95: Unix, use "dd if=<file> of=/dev/<device> bs=32k" (where device could
96: be "floppy" or "rfd0c" or "rfd0a"). Use properly formatted perfect
97: floppies with NO BAD BLOCKS or you will lose.
98: <p>
99: <h3><font color=#e00000>sparc:</font></h3>
100: <p>
101: To boot off CD1, type "boot cdrom 2.6/sparc/bsd.rd", or
102: "b sd(0,6,0)2.6/sparc/bsd.rd" depending on your ROM version.
103: Alternatively, write CD1:2.6/sparc/floppy26.fs to a floppy and boot it
104: using "boot fd()" or "boot floppy" depending on your ROM version.
105: Finally, a third alternative is to write CD1:2.6/sparc/kc.fs and
106: CD1:2.6/sparc/inst.fs to two separate floppies. Then insert "kc.fs",
107: and boot as described above. As soon as the floppy drive ejects a
108: floppy, insert "inst.fs". Answer a bunch of questions. Reboot from
109: the "kc.fs" floppy. This time, when the floppy is ejected simply
110: re-insert "kc.fs" again and answer a different set of questions.
111: <p>
112: <h3><font color=#e00000>amiga:</font></h3>
113: <p>
114: Create BSD partitions according to INSTALL.amiga's preparation section.
115: Mount the CD2 under AmigaOS as device CD0: Next, execute the following
116: CLI command: "CD0:2.6/amiga/utils/loadbsd CD0:2.6/amiga/bsd.rd".
117: <p>
118: <h3><font color=#e00000>hp300:</font></h3>
119: <p>
120: You can boot over the network by following the instructions in
121: INSTALL.hp300.
122: <p>
123: <h3><font color=#e00000>alpha:</font></h3>
124: <p>
125: Your alpha must use SRM firmware (not ARC). If you have a CDROM, you
126: can try "boot -fi 2.6/alpha/bsd.rd dkaX" (use "show device" to find your
127: CDROM drive identifier). Otherwise, write CD2:2.6/alpha/floppy.fs to a
128: floppy and boot that by typing "boot dva0". If this fails, you can place
129: bsd.rd on some other device and boot it, or use the provided simpleroot.
130: <p>
131: <h3><font color=#e00000>mac68k:</font></h3>
132: <p>
133: Boot MacOS as normal and partition your disk with the appropriate A/UX
134: configurations. Then, extract the Macside utilities from
135: CD1:2.6/mac68k/utils onto your hard disk. Run Mkfs to create your
136: filesystems on the A/UX partitions you just made. Then, use the
137: BSD/Mac68k Installer to copy all the sets in CD1:2.6/mac68k/ onto your
138: partitions. Finally, you will be ready to configure the BSD/Mac68k
139: Booter with the location of your kernel and boot the system.
140: <p>
141: <h3><font color=#e00000>Notes about the source code:</font></h3>
142: <p>
143: src.tar.gz contains a source archive starting at /usr/src. This file
144: contains everything you need except for the kernel sources, which are
145: in a separate archive. To extract:
146: <p>
147: <pre>
148: # mkdir -p /usr/src
149: # cd /usr/src
150: # tar xvfz /tmp/src.tar.gz
151: </pre>
152: <p>
153: srcsys.tar.gz contains a source archive starting at /usr/src/sys.
154: This file contains all the kernel sources you need to rebuild kernels.
155: To extract:
156: <p>
157: <pre>
158: # mkdir -p /usr/src/sys
159: # cd /usr/src
160: # tar xvfz /tmp/srcsys.tar.gz
161: </pre>
162: <p>
163: Both of these trees are a regular CVS checkout. Using these trees it
164: is possible to get a head-start on using the anoncvs servers as
165: described at <a href=anoncvs.html>http://www.OpenBSD.org/anoncvs.html</a>.
166: Using these files
167: results in a much faster initial CVS update than you could expect from
168: a fresh checkout of the full OpenBSD source tree.
169: <p>
170: <hr>
171: <p>
172: <h3><font color=#e00000>PORTS TREE</font></h3>
173: <p>
174: A ports tree archive is also provided. To extract:
175: <p>
176: <pre>
177: # cd /usr
178: # tar xvfz /tmp/ports.tar.gz
179: # cd ports
180: # ls
181: ...
182: </pre>
183: <p>
184: The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go
185: read <a href=ports.html>http://www.OpenBSD.org/ports.html</a>
186: if you know nothing about ports
187: at this point. This text is not a manual of how to use ports.
188: Rather, it is a set of notes meant to kickstart the user on the
189: OpenBSD ports system.
190: <p>
191: Certainly, the OpenBSD ports system is not complete. This is because
192: the full integration of ports into the OpenBSD environment is still a
193: young project as of this release. We believe the ports that are
194: provided here are stable, but it is most important to realize that
195: ports will continue to grow a great deal in functionality in the
196: future.
197: <p>
198: As we said, ports will be growing a lot in the future. The ports/
199: directory represents a CVS (see the manpage for cvs(1) if you aren't
200: familiar with CVS) checkout of our ports. As with our complete source
201: tree, our ports tree is available via anoncvs. So, in
202: order to keep current with it, you must make the ports/ tree
203: available on a read-write medium and update the tree with a command
204: like:
205: <p>
206: <pre>
207: # cd [portsdir]/; cvs -d anoncvsserver.openbsd.org:/cvs update -PAd
208: </pre>
209: <p>
210: [Of course, you must replace the local directory and server name here
211: with the location of your ports collection and a nearby anoncvs
212: server.]
213: <p>
214: Again, it is important to see the webpage for specific instructions as
215: this is a new service which hasn't yet been ironed out
216: completely.
217: <p>
218: Finally, despite ports' youth, help is never far. If you're
219: interested in seeing a port added, would like to help out, or just
220: would like to know more, the mailing list ports@openbsd.org is a good
221: place to know.
1.2 ! louis 222:
! 223: <hr>
! 224: <a name=new></a>
! 225: <p>
! 226: <h3><font color=#e00000>WHAT'S NEW</font></h3>
! 227: <p>
! 228: This is a partial list of new features and systems included in OpenBSD 2.6.
! 229: For a comprehensive list, see the <a href=plus26.html>changelog</a> leading
! 230: to 2.6.
! 231: <p>
! 232:
! 233: <ul>
! 234: <li>The most interesting addition is OpenSSH (http://www.OpenSSH.com/).
! 235: This is a free and reusable SSH suite based on an early release by Tatu
! 236: Ylonen (1.2.12). That release was the last with a free license. OpenSSH
! 237: was brought up to current standards and uses the OpenSSL library. It is
! 238: free for all except USA commercial users (RSA patent in USA). OpenSSH was
! 239: developed by OpenBSD and has been ported to FreeBSD and Linux.
! 240:
! 241: <li>A clever trick allows us to distribute the same CD-ROM (USA and the
! 242: rest of the world) and maintain full strength crypto without violating the
! 243: RSA patent in the USA.
! 244:
! 245: <li>Extensive changes to the documentation, notably the man pages and the
! 246: Web FAQ. The manual pages now include useful examples to supplement the
! 247: explanations. By keeping the documentation set concise and in two
! 248: well-known locations, we hope to avoid the explosion of "How-To" docs that
! 249: forces users to search endlessly for information.
! 250:
! 251: <li>More complete collection of "ports". Ports is the method to use when
! 252: importing and building freeware applications from the network
! 253: (applications, mailers, browsers, etc.). The user needs only to cd to the
! 254: relevant directory and type "make install" to start a process that will
! 255: fetch the sources, patch them for OpenBSD, compile and install the
! 256: package. Most ports are also available as pre-built packages.
! 257:
! 258: <li>Includes:
! 259: <ul>
! 260: <li>XFree86 3.3.5
! 261: <li>gcc 2.95
! 262: <li>Apache 1.3.9 + Mod_ssl 2.4.5 + OpenSSL 0.9.4
! 263: </ul>
! 264:
! 265: <li>Many improvements for security and reliability (look for the red
! 266: print in the complete list).
! 267:
! 268: <li>New hardware devices supported, notably in the PC (i386) architecture.
! 269:
! 270: </ul>
! 271:
! 272: <p>
! 273: <a href=#top>Back to top</a>
! 274:
! 275: <hr>
! 276: <br>
! 277: <small>$OpenBSD$</small>
! 278:
! 279: </body>
! 280: </html>
! 281:
![[BACK]](/icons/back.gif){kind=icon}
Return to 26.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www