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
|
INSTALLATION NOTES for OpenBSD/MACHINE 2.1
What is OpenBSD?
----------------
OpenBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite
-derived Operating System. It is a fully functional UN*X-like system
which runs on many architectures and is being ported to more.
Continuing the multi-platform tradition, OpenBSD has added ports to
mvme68k, powerpc and arc machines. Kernel interfaces have continued to
be refined, and now several subsystems and device drivers are shared
among the different ports. You can look for this trend to continue.
Security of the system as a whole has been significantly
improved. Source code for all critical system components has been
checked for remote-access, local-access, denial-of-service, data
destruction, or information-gathering problems.
OpenBSD 2.1 has significantly enhanced the binary emulation subsystem
(which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix
compatibility) and several kernel subsystems have been generalized
to support this more readily. The binary emulation strategy is
aimed at making the emulation as accurate as possible.
Cryptography components are part of OpenBSD. OpenBSD is from Canada,
and export of these pieces (such as kerberosIV) to the world is not
restricted. Note that it can not be re-exported from the US once it
has entered US. Because of this, take care NOT to get the distrib-
ution from an FTP server in the US if you are outside of Canada and
the US.
Many new user programs have been added in OpenBSD 2.1, as well,
bringing it closer to our goal of supplying a complete UN*X-like
environment. Tools like perl and ksh are standard, as are numerous
other useful tools.
#include "whatis"
Sources of OpenBSD:
-------------------
#include "mirrors"
OpenBSD 2.1 Release Contents:
-----------------------------
The OpenBSD 2.1 release is organized in the following way. In the
.../2.1 directory, there is one sub-directory per architecture, for
each of the architectures that OpenBSD 2.1 has a binary distribution
for. That is described further along in this document).
#include "contents"
OpenBSD System Requirements and Supported Devices:
--------------------------------------------------
#include "hardware"
Getting the OpenBSD System on to Useful Media:
----------------------------------------------
#include "xfer"
Preparing your System for OpenBSD Installation:
-----------------------------------------------
#include "prep"
Installing the OpenBSD System:
------------------------------
#include "install"
Upgrading a previously-installed OpenBSD System:
------------------------------------------------
#include "upgrade"
Getting source code for your OpenBSD System:
--------------------------------------------
Now that your OpenBSD system is up and running, you probably want to get
access to source code so that you can recompile pieces of the system.
A few methods are provided. If you have an OpenBSD CD, the source code
is provided. Otherwise, you can get the pieces over the Internet using
either ANONCVS or CTM. For more information, see
http://www.openbsd.org/anoncvs.html
http://www.openbsd.org/ctm.html
Using online OpenBSD documentation:
-----------------------------------
Documentation is available if you first install the manual
distribution set. Traditionally, the UN*X "man pages" (documentation)
are denoted by 'name(section)'. Some examples of this are
intro(1),
man(1),
apropros(1),
passwd(1), and
passwd(5).
The section numbers group the topics into several categories, but three
are of primary interest: user commands are in section 1, file formats
are in section 5, and administrative information is in section 8.
The 'man' command is used to view the documentation on a topic, and is
started by entering 'man [section] topic'. The brackets [] around the
section should not be entered, but rather indicate that the section is
optional. If you don't ask for a particular section, the topic with the
least-numbered section name will be displayed. For instance, after
logging in, enter
man passwd
to read the documentation for passwd(1). To view the documentation for
passwd(5), enter
man 5 passwd
instead.
If you are unsure of what man page you are looking for, enter
apropos subject-word
where "subject-word" is your topic of interest; a list of possibly
related man pages will be displayed.
Administrivia:
--------------
There are various mailing lists available via the mailing list
server at <majordomo@OpenBSD.ORG>. To get help on using the mailing
list server, send mail to that address with an empty body, and it will
reply with instructions.
To report bugs, use the 'sendbug' command shipped with OpenBSD,
and fill in as much information about the problem as you can. Good
bug reports include lots of details. Additionally, bug reports can
be sent by mail to:
bugs@OpenBSD.ORG
Use of 'sendbug' is encouraged, however, because bugs reported with it
are entered into the OpenBSD bugs database, and thus can't slip through
the cracks.
As a favor, please avoid mailing huge documents or files to the
mailing lists. Instead, put the material you would have sent up
for FTP somewhere, then mail the appropriate list about it, or, if
you'd rather not do that, mail the list saying you'll send the data
to those who want it.
|
