forked from openbsd/www
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path27.html
370 lines (350 loc) · 12.9 KB
/
27.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
<html>
<head>
<title>OpenBSD 2.7</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="description" content="OpenBSD 2.7">
<meta name="copyright" content="This document copyright 1999-2001 by OpenBSD.">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="https://www.openbsd.org/27.html">
</head>
<body bgcolor="#ffffff" text="#000000" link="#24248e">
<h2>
<a href="index.html">
<font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
<font color="#e00000">2.7</font>
</h2>
<a href=images/spacefish.jpg>
<img align=left hspace="24" src=images/spacefish.jpg></a>
<p>
Released June 15, 2000.<br>
Copyright 1997-2000, Theo de Raadt.<br>
<font color=#e00000>ISBN 0-9683637-5-X</font>
<p>
<ul>
<li>Order a CDROM from our <a href="https://openbsdstore.com">ordering system</a>.
<li>See the information on <a href=ftp.html>The FTP page</a> for
a list of mirror machines
<li>Go to the <font color=#e00000>pub/OpenBSD/2.7/</font> directory on
one of the mirror sites
<li>Have a look at <a href=errata27.html>The 2.7 Errata page</a> for a list
of bugs and workarounds.
<li>See a <a href=plus27.html>detailed log of changes</a> between the
2.6 and 2.7 releases.
</ul>
<p>
All applicable copyrights and credits are in the src.tar.gz,
sys.tar.gz, xenocara.tar.gz, ports.tar.gz files, or in the
files fetched via ports.tar.gz.
<br clear="all">
<hr>
<a name="new"></a>
<p>
<h3><font color=#0000e0>What's New</font></h3>
<p>
This is a partial list of new features and systems included in OpenBSD 2.7.
For a comprehensive list, see the <a href=plus27.html>changelog</a> leading
to 2.7.
<p>
<ul>
<li><a href="https://www.OpenSSH.com">OpenSSH</a> now supports both the
SSH1 and SSH2 protocols. The SSH2 protocol is slowly gaining
acceptance. Up until recently, SSH2 was just available in various
commercial offerings. The benefit with SSH2 is that it avoids the RSA
cipher and uses DSA instead, which is freely reusable. The downside
is that DSA is not nearly as fast on old slow machines. But since
OpenSSH still supports SSH1 protocol (if the RSA libraries are
installed) our users get the best of both worlds.
<p>
<li>The clever trick used in 2.6 remains, allowing us to distribute
the same CD-ROM worldwide containing full strength crypto without
violating the RSA patent in the USA. The next OpenBSD release will
ship with RSA support in the operating system by default, since the
patent expires on September 21, 2000.
<p>
<li>Extensive changes to the documentation, notably the man pages and
the Web FAQ. The manual pages now include useful examples to
supplement the explanations.
<p>
<li>More complete collection and better tested set of "ports".
<p>
<li>Over 500 pre-built and tested packages.
<p>
<li>The system includes the following major components from outside suppliers:
<p>
<ul>
<li>XFree86 3.3.6
<li>gcc 2.95.2
<li>perl 5.6.0 plus a few fixes.
<li>Apache 1.3.12 + Mod_ssl 2.6.2 + OpenSSL 0.9.5a, DSO
<li>ipf 3.3.14
<li>groff 1.15
<li>sendmail 8.10.1
<li>lynx 2.8.2 with HTTPS support added
<li>sudo 1.6.3
<li>Recent ncurses release
<li>Latest KAME IPv6 as of mid-May 2000.
<li>KTH Kerberos 1.0
<li>OpenSSH 2.1
</ul>
<p>
<li>Much improved device driver support
<p>
<ul>
<li>Support for crypto hardware to accelerate IPSEC performance, ie.
<a href=http://www.powercrypt.com>PowerCrypt</a>.
<li>Support for all new
<a href="https://man.openbsd.org/?query=ahc&sektion=4">Adaptec</a>,
<a href="https://man.openbsd.org/?query=ncr&sektion=4">NCR</a>,
<a href="https://man.openbsd.org/?query=isp&sektion=4">Qlogic</a>,
and
<a href="https://man.openbsd.org/?query=adw&sektion=4">Advansys</a>
scsi controllers.
<li>Many new ethernet devices supported, including
<a href="https://man.openbsd.org/?query=sis&sektion=4">
SiS900/7016</a>,
<a href="https://man.openbsd.org/?query=sf&sektion=4">
Adaptec Starfire</a>,
<a href="https://man.openbsd.org/?query=dc&sektion=4">
21143</a>,
<a href="https://man.openbsd.org/?query=ste&sektion=4">
Sundance ST201 (DEC DFE-550TX)</a>, etc.
<li>New USB ethernet devices supported, including
<a href="https://man.openbsd.org/?query=aue&sektion=4">ADMtek USB</a>,
<a href="https://man.openbsd.org/?query=cue&sektion=4">CATC USB</a>,
and
<a href="https://man.openbsd.org/?query=kue&sektion=4">
Kawasaki USB</a>.
<li>A good start at
<a href="https://man.openbsd.org/?query=cardbus&sektion=4">
cardbus</a> support.
<li>Significant improvements to
<a href="https://man.openbsd.org/?query=pcmcia&sektion=4">
pcmcia</a>.
<li>Support for many more wireless networking cards, ie.
<a href="https://man.openbsd.org/?query=wi&sektion=4">WaveLAN</a>,
<a href="https://man.openbsd.org/?query=an&sektion=4">Aironet</a>,
<a href="https://man.openbsd.org/?query=ray&sektion=4">Aviator</a>,
etc.
<li>Many improvements in
<a href="https://man.openbsd.org/?query=usb&sektion=4">USB</a>
support.
<li>Hypersparc support for the sparc port.
<li>Support for most of the gigabit ethernet cards on the market, ie.
<a href="https://man.openbsd.org/?query=sk&sektion=4">SysKonnect</a>,
<a href="https://man.openbsd.org/?query=wx&sektion=4">Intel</a>, and
<a href="https://man.openbsd.org/?query=ti&sektion=4">Alteon</a>.
<li>Support for the
<a href="https://man.openbsd.org/?query=gdt&sektion=4">
ICP Vortex RAID controller</a>.
<li>Support for large PC's using multiple PCI busses based on the Intel 451 or
RCC ServerWorks chipsets.
<li>New audio drivers, including
<a href="https://man.openbsd.org/?query=neo&sektion=4">Neomagic</a>,
<a href="https://man.openbsd.org/?query=cmpci&sektion=4">
C-Media CMI8x38</a>, and
<a href="https://man.openbsd.org/?query=uaudio&sektion=4">
USB audio</a>.
<li>Improvements in
<a href="https://man.openbsd.org/?query=pciide&sektion=4">
PCI IDE subsystem</a>, including new support for AMD 756.
</ul>
<p>
<li>Many improvements for security and reliability (look for the red
print in the <a href=plus27.html>complete changelog</a>).
<p>
<li>Many other new features, including:
<p>
<ul>
<li>Support for encrypting swap space.
<li>Improved
<a href="https://man.openbsd.org/?query=compat_linux&sektion=8">
Linux emulation</a>
<li>Support for large
<a href="https://man.openbsd.org/?query=mount_msdos&sektion=8">
FAT32 filesystems</a>.
<li>Significant improvements to the
<a href="https://man.openbsd.org/?query=bridge&sektion=4">
network bridging</a> code.
<li>Improved
<a href="https://man.openbsd.org/?query=pthreads&sektion=3">
pthreads</a> support.
<li>Support for
<a href="https://man.openbsd.org/?query=vlan&sektion=4">
vlan</a> networking.
</ul>
<p>
</ul>
<p>
<a name=install></a>
<hr>
<p>
<h3><font color=#0000e0>How to install</font></h3>
<p>
Following this are the instructions which you would have on a piece of
paper if you had purchased a CDROM set instead of doing an alternate
form of install. The instructions for doing an ftp (or other style
of) install are very similar; the CDROM instructions are left intact
so that you can see how much easier it would have been if you had
purchased a CDROM instead.
<p>
<hr>
Please refer to the following files on the two CDROMs for extensive
details on how to install OpenBSD 2.7 on your machine:
<p>
<dl>
<li> CD1:2.7/i386/INSTALL.i386
<p>
<li> CD2:2.7/sparc/INSTALL.sparc
<li> CD2:2.7/mvme68k/INSTALL.mvme68k
<li> CD2:2.7/amiga/INSTALL.amiga
<li> CD2:2.7/mac68k/INSTALL.mac68k
<li> CD2:2.7/hp300/INSTALL.hp300
<p>
<li>The pmax & sun3 releases are available on the ftp sites, but not
on the CDs.
</dl>
<hr>
<p>
Quick installer information for people familiar with OpenBSD, and the
use of the new "disklabel -E" command. If you are at all confused when
installing OpenBSD, read the relevant INSTALL.* file as listed above!
<p>
<h3><font color=#e00000>i386:</font></h3>
<p>
Play with your BIOS options, and see if you can enable booting off a
CD; try using CD1. If not, write CD1:2.7/i386/floppy27.fs to a
floppy, then boot that. If you are mixing OpenBSD with another
operating system, you will surely need to read the INSTALL.i386
document.
<p>
To make a floppy under MS-DOS, use /2.7/tools/rawrite.exe. Under
Unix, use "dd if=<file> of=/dev/<device> bs=32k" (where device could
be "floppy" or "rfd0c" or "rfd0a"). Use properly formatted perfect
floppies with NO BAD BLOCKS or you will lose.
<p>
<h3><font color=#e00000>sparc:</font></h3>
<p>
To boot off CD2, type "boot cdrom 2.7/sparc/bsd.rd", or
"b sd(0,6,0)2.7/sparc/bsd.rd" depending on your ROM version.
Alternatively, write CD2:2.7/sparc/floppy27.fs to a floppy and boot it
using "boot floppy" or "boot fd()" depending on your ROM version.
Finally, a third alternative is to write CD2:2.7/sparc/kc.fs and
CD2:2.7/sparc/inst.fs to two separate floppies. Then insert "kc.fs",
and boot as described above. As soon as the floppy drive ejects a
floppy, insert "inst.fs". Answer a bunch of questions. Reboot from
the "kc.fs" floppy. This time, when the floppy is ejected simply
re-insert "kc.fs" again and answer a different set of questions.
<p>
<h3><font color=#e00000>amiga:</font></h3>
<p>
Create BSD partitions according to INSTALL.amiga's preparation section.
Mount the CD2 under AmigaOS as device CD0: Next, execute the following
CLI command: "CD0:2.7/amiga/utils/loadbsd CD0:2.7/amiga/bsd.rd".
<p>
<h3><font color=#e00000>hp300:</font></h3>
<p>
You can boot over the network by following the instructions in
INSTALL.hp300.
<p>
<h3><font color=#e00000>mac68k:</font></h3>
<p>
Boot MacOS as normal and partition your disk with the appropriate A/UX
configurations. Then, extract the Macside utilities from
CD1:2.7/mac68k/utils onto your hard disk. Run Mkfs to create your
filesystems on the A/UX partitions you just made. Then, use the
BSD/Mac68k Installer to copy all the sets in CD1:2.7/mac68k/ onto your
partitions. Finally, you will be ready to configure the BSD/Mac68k
Booter with the location of your kernel and boot the system.
<p>
<h3><font color=#e00000>sun3:</font></h3>
<p>
Get the release via ftp. Then, you can either setup a diskless boot or
create an installation tape, as described in INSTALL.sun3.
<p>
<h3><font color=#e00000>Notes about the source code:</font></h3>
<p>
src.tar.gz contains a source archive starting at /usr/src. This file
contains everything you need except for the kernel sources, which are
in a separate archive. To extract:
<p>
<pre>
# mkdir -p /usr/src
# cd /usr/src
# tar xvfz /tmp/src.tar.gz
</pre>
<p>
srcsys.tar.gz contains a source archive starting at /usr/src/sys.
This file contains all the kernel sources you need to rebuild kernels.
To extract:
<p>
<pre>
# mkdir -p /usr/src/sys
# cd /usr/src
# tar xvfz /tmp/srcsys.tar.gz
</pre>
<p>
Both of these trees are a regular CVS checkout. Using these trees it
is possible to get a head-start on using the anoncvs servers as
described at <a href=anoncvs.html>http://www.OpenBSD.org/anoncvs.html</a>.
Using these files
results in a much faster initial CVS update than you could expect from
a fresh checkout of the full OpenBSD source tree.
<p>
<a name=ports></a>
<hr>
<p>
<h3><font color=#0000e0>Ports Tree</font></h3>
<p>
A ports tree archive is also provided. To extract:
<p>
<pre>
# cd /usr
# tar xvfz /tmp/ports.tar.gz
# cd ports
# ls
...
</pre>
<p>
The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go
read <a href=faq/faq15.html>http://www.OpenBSD.org/faq/faq15.html</a>
if you know nothing about ports
at this point. This text is not a manual of how to use ports.
Rather, it is a set of notes meant to kickstart the user on the
OpenBSD ports system.
<p>
Certainly, the OpenBSD ports system is not complete. This is because
the full integration of ports into the OpenBSD environment is still a
young project as of this release. We believe the ports that are
provided here are stable, but it is most important to realize that
ports will continue to grow a great deal in functionality in the
future.
<p>
As we said, ports will be growing a lot in the future. The ports/
directory represents a CVS (see the manpage for cvs(1) if you aren't
familiar with CVS) checkout of our ports. As with our complete source
tree, our ports tree is available via anoncvs. So, in
order to keep current with it, you must make the ports/ tree
available on a read-write medium and update the tree with a command
like:
<p>
<pre>
# cd [portsdir]/; cvs -d [email protected]:/cvs update -Pd
</pre>
<p>
[Of course, you must replace the local directory and server name here
with the location of your ports collection and a nearby anoncvs
server.]
<p>
Again, it is important to see the webpage for specific instructions as
this is a new service which hasn't yet been ironed out
completely.
<p>
Finally, despite ports' youth, help is never far. If you're
interested in seeing a port added, would like to help out, or just
would like to know more, the mailing list [email protected] is a good
place to know.
<p>
</body>
</html>