INSTALLATION NOTES for OpenBSD/pmax 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. Tools like ipf, ipnat, and nc have
been added to the tree because security conscious people often need
them.
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 and modern
UN*X-like environment. Tools like perl and ksh are standard, as are
numerous other useful tools.
OpenBSD 2.1 is the first public release of OpenBSD for the DECstation
and DECsystem family of computers. This release includes kernel
support for ELF shared libraries and uses them througout the
userland.
Sources of OpenBSD:
-------------------
This is a list of currently known ftp servers:
Germany:
ftp://ftp.fu-berlin.de/pub/unix/openbsd/mirrors/OpenBSD ==
ftp://ftp.de.openbsd.org/pub/unix/openbsd/mirrors/OpenBSD
Japan:
ftp://ftp.tut.ac.jp/OpenBSD == ftp://ftp.jp.openbsd.org/OpenBSD
ftp://ftp.dti.ad.jp/pub/OpenBSD
Switzerland:
ftp://ftp.openbsd.org/pub/OpenBSD ==
ftp://ftp.eu.openbsd.org/pub/OpenBSD
USA:
ftp://hydra.heuris.com/pub/OpenBSD ==
ftp://ftp1.usa.openbsd.org/pub/OpenBSD
ftp://freestuff.cs.colorado.edu/pub/OpenBSD ==
ftp://ftp2.usa.openbsd.org/pub/OpenBSD
ftp://ftp.ctaz.com/pub/OpenBSD ==
ftp://ftp5.usa.openbsd.org/pub/OpenBSD
ftp://pub.seastrom.com/pub/OpenBSD ==
ftp://ftp1.usa.openbsd.org/pub/OpenBSD
As well, the file ftp://ftp.openbsd.org/pub/OpenBSD/2.1/ftplist
contains a list which is continually updated. If you wish to become a
distribution site for OpenBSD, contact deraadt@cvs.openbsd.org.
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).
The pmax-specific portion of the OpenBSD 2.1 release is found in the
"pmax" subdirectory of the distribution. That subdirectory is laid
out as follows:
.../2.1/pmax/
INSTALL.pmax Installation notes; this file.
*.gz pmax binary distribution sets;
see below.
simpleroot* pmax boot and installation
simpleroot files; see below.
There is a pmax simpleroot image named simpleroot21.fs (it is usually
compressed using gzip - simpleroot21.fs.gz - so you need gunzip first
to uncompress it) subdirectory of the OpenBSD 2.1 distribution. This
file you can dump onto a disk and boot from it to start the installation
of OpenBSD/pmax. Also there is a simpleroot21.tar.gz file there. It
can be used as root area on the NFS server if you plan to install via
network.
The OpenBSD/pmax binary distribution sets contain the binaries which
comprise the OpenBSD 2.1 release for the pmax. There are seven binary
distribution sets. The binary distribution sets can be found in
subdirectories of the "pmax/bins" subdirectory of the OpenBSD 2.1
distribution tree, and are as follows:
base21 The OpenBSD/pmax 2.1 base binary distribution. You
MUST install this distribution set. It contains the
base OpenBSD utilities that are necessary for the
system to run and be minimally functional. It
includes shared library support, and excludes
everything described below.
[ 15.0M gzipped, 50.8M uncompressed ]
comp21 The OpenBSD/pmax Compiler tools. All of the tools
relating to C, C++, and FORTRAN (yes, there are two!).
This set includes the system include files
(/usr/include), the linker, the compiler tool chain,
and the various system libraries (except the shared
libraries, which are included as part of the base
set). This set also includes the manual pages for all
of the utilities it contains, as well as the system
call and library manual pages.
[ 16.2M gzipped, 61.1M uncompressed ]
etc21 This distribution set contains the system
configuration files that reside in /etc and in several
other places. This set MUST be installed if you are
installing the system from scratch, but should NOT be
used if you are upgrading. (If you are upgrading,
it's recommended that you get a copy of this set and
CAREFULLY upgrade your configuration files by hand.)
[ 93K gzipped, 450K uncompressed ]
game21 This set includes the games and their manual pages.
[ 2.9M gzipped, 7.5M uncompressed ]
man21 This set includes all of the manual pages for the
binaries and other software contained in the base set.
Note that it does not include any of the manual pages
that are included in the other sets.
[ 2.5M gzipped, 9.4M uncompressed ]
misc21 This set includes the system dictionaries (which are
rather large), the typesettable document set, and
man pages for other architectures which happen to be
installed from the source tree by default.
[ 1.8M gzipped, 6.2M uncompressed ]
text21 This set includes OpenBSD's text processing tools,
including groff, all related programs, and their
manual pages.
[ 1.0M gzipped, 4.2M uncompressed ]
OpenBSD System Requirements and Supported Devices:
--------------------------------------------------
OpenBSD/pmax 2.1 runs on the following classes of machines:
- Decstation 2100 and 3100, also known as "pmin" and "pmax"
- Personal Decstations (5000/20, and /25) also knonw as "MAXINE"
- Decstation 5000/120, /125, and /133, also knonw as "3MIN"
- Decstation 5000/200, also knonw as "3MAX"
- Decstation 5000/240, als knonw as "3MAXPLUS"
OpenBSD/pmax 2.1 does *not* (yet) run on these machines:
- Decstation 5100 (an r2000-based cousin of the Decstation 3100)
- Decsystem 5400 and 5500 (Qbus-based systems, similar to a
Vax 'Mayfair' and 'Mayfair II', but with an r2000a or r3000
cpu instead of a CVAX cpu.)
- Decsystem 5800 (xbi-based multiprocessor, a Vax 8800 with
Vax CPU boards replaced with Mips cpu boards)
The minimal configuration requires 8M of RAM and ~60M of disk space.
To install the entire system requires much more disk space, and to run
X or compile the system, more RAM is recommended. (OpenBSD with 8M of
RAM feels like Ultrix with 8M of RAM.) Note that until you have
around 16M of RAM, getting more RAM is more important than getting a
faster CPU.
Supported devices include:
Decstation 2100 and 3100 baseboard video:
pm one-bit mono or 8-bit pseudocolour fraem buffers.
Decstation 5000 series TurboChannel video:
PMAG-DV Personal Decstation baseboard 1024x768 frame buffer.
PMAG-BA 1024x768 8-bit colour frame buffer.
PMAGB-BA 1024x768 8-bit colour frame buffer.
PMAG-AA 1280x1024 four-bit greyscale frame buffer.
NOTE: All supported DECstation vide produces sync-on-green.
Be sure to use either a DEC-compatible fixed-sync monitor
or a multisync monitor that supports sync-on-green.
serial ports:
ttya and ttyb (can be used as console if needed)
ethernet:
on-board AMD Lance ethernet ("le0"),
TURBOchannel AMD Lance ethernet cards.
SCSI:
on-board DEC "sii" SCSI controller (2100 and 3100)
on-board "asc" SCSI controller (5000 series machines)
TurboChannel "asc" SCSI controller,
DEC (LK-201 or compatible) keyboard
DEC ("hockey puck" or compatible) mouse.
Hardware the we do NOT currently support:
Q-bus Decsystem machines
Decstation 5100 machines
PrestoServe NVRAM on Decstation 5100 machines
audio drivers for Personal Decstation machines
floppy driver for Personal Decstation machines
TurboChannel audio hardware (LoFi)
PMAG-C 2-D accelerated framebuffers with onboard i860 processors
Getting the OpenBSD System onto Useful Media:
---------------------------------------------
Installation is supported from several media types, including:
NFS partitions
FTP
Tape
The steps necessary to prepare the distribution sets
for installation depend on which method of installation
you choose. The various methods are explained below.
Those are only the preparationis required before you start
the installation.
To prepare for installing via an NFS partition:
Place the OpenBSD software you wish to install into
a directory on an NFS server, and make that directory
mountable by the machine which you will be installing
OpenBSD on. This will probably require modifying the
/etc/exports file of the NFS server and resetting
mountd, acts which will require superuser privileges.
Note the numeric IP address of the NFS server and of
the router closest to the the new OpenBSD machine,
if the NFS server is not on a network which is
directly attached to the OpenBSD machine.
If you are using a diskless setup to install OpenBSD on
your machine, you can take advantage of the fact that
the above has already been done on your machine's server.
So, you can conveniently put the OpenBSD filesets in your
machine's root filesystem on the server where the install
program can find them.
Once you have done this, you can proceed to the next
step in the installation process, preparing your
system for OpenBSD installation.
To prepare for installing via FTP:
The preparations for this method of installation
are easy: all you have to do is make sure that
there's some FTP site from which you can retrieve
the OpenBSD installation when it's time to do
the install. You should know the numeric IP
address of that site, the numeric IP address of
your nearest router if one is necessary
Once you have done this, you can proceed to the next
step in the installation process, preparing your
system for OpenBSD installation.
To prepare for installing via a tape:
To install OpenBSD from a tape, you need to somehow
get the OpenBSD filesets you wish to install on
your system on to the appropriate kind of tape,
in tar format.
If you're making the tape on a UN*X system, the easiest
way to do so is:
tar cvf
where "" is the name of the tape device
that describes the tape drive you're using (possibly
something like /dev/nrst0, but we make no guarantees 8-).
Under SunOS 5.x, this would be something like /dev/rmt/0mbn.
Again, your mileage may vary. If you can't figure it out,
ask your system administrator. "" are the names
of the "set_name.nnn" files which you want to be placed
on the tape.
Once you have done this, you can proceed to the next
step in the installation process, preparing your
system for OpenBSD installation.
Preparing your System for OpenBSD Installation:
-----------------------------------------------
Before you start you should familiarize yourself with the boot PROM
of your machine. The older Decstation 2100 and 3100 cannot select
a kernel from the command line. You need to set the bootpath
environment variable to point to the disk and kernel you intend to boot.
You should also examine the guide on the OpenBSD/pmax web site, which
will hopefully soon have more complete and more up-to-date
instructions than are given in the install document. I will try to
put there all the corrections to this document in the future.
If you're installing OpenBSD/pmax for the first time it's a very good idea
to look at the partition sizes of disk you intend installing OpenBSD on.
Changing the size of partitions after you've installed is difficult.
If you do not have a spare bootable disk, it may be simpler to re-install
OpenBSD again from scratch.
But if you don't have a second disk or plan to do an installation via
netbooting you don't have any choice about the partition sizes (at
least not for the root and the swap partitions) because they are set
in the simpleroot image to to 32M for root and 64M for swap. About the
rest of your disk you can still decide yourself.
Asumming a classic partition scheme with root (`/') and /usr filesystems,
a comfortable size for the OpenBSD root filesystem partition is about 32M;
a good initial size for the swap partition is twice the amount of physical
memory in your machine (though, unlike Ultrix, there are no restrictions on
the size of the swap partition that would render part of your memory
unusable). A full binary installation, without X11 or other additional
software, takes about 130MB in `/usr'.
Installing the OpenBSD System:
------------------------------
Installing OpenBSD is a relatively complex process, but if you have
this document in hand it shouldn't be too much trouble.
Also i wanted to note that the installation procedure via install
script is new for the pmax and i had only the chance of limited
testing for it - so if you run into any problems with it or if this
documentation is somehow unclear - please send me a mail and i'll try
to help you or to fix the problem.
There are several ways to install OpenBSD onto a disk. The easiest way
in terms of preliminary setup is to use the OpenBSD simpleroot that can
be booted off your local disk. Alternatively, if your Decstation is
hooked up in a network you can find a server and arrange for a diskless
setup which is another convenient way to install OpenBSD/pmax.
Installing using the OpenBSD simpleroot.
The simpleroot is a self-contained OpenBSD filesystem holding a complete
OpenBSD/pmax rootfilesystem plus all utilities necessary to install
OpenBSD on a local disk. It is distributed as a plain file designed to
be transferred to a raw disk from which it can be booted using the
appropriate PROM command.
Loading the simpleroot onto your raw partition is simple. You can do
this on any machine you can hang on the disk which you plan to put
onto the pmax which allows you to write to the raw disk - i.e. on all
UN*X like operatingsystems it should work using "dd". On OpenBSD
as well as SunOS you use a command like:
# dd if=simpleroot21.fs of=/dev/rsd0c bs=20b conv=sync
Especially on OpenBSD/pmax you'll have to use /dev/rrz0c or something
like that instead of /dev/rsd0c.
Keep in mind that this will overwrite the contents of that disk!
After transferring the simpleroot to disk, bring the system down by:
# halt
and hang the disk onto the pmax you want to install OpenBSD/pmax on.
Then boot the simpleroot by typing the appropriate command at the PROM:
>> boot rz(0,0,0)/bsd # for Decstation 2100/3100
or
>> boot 5/rz0a/bsd # for Decstation 5000's
If you've loaded the simpleroot onto some other disk than `rz0' adapt
the boot specifier accordingly.
This will cause the kernel contained in the simpleroot to be booted.
After the initial probe messages you'll asked to choose a shell with
sh as default. Simply type Return here and you are in single user
mode. For further instructions please read on in the "Continuing the
installation from single user mode" below.
Note: if booting the kernel in the miniroot should not work - there are
two kernels part of the distribution - look at the place you got
the distribution from - the kernels are there also - so you can
see which kernels there are - usually there should be 3 of them
* bsd - a generic kernel which should ask for the root device
* bsd.rz0 - generic kernel with root and swap fixed to rz0
don't ask me why - but this should be usable then
installing from a simpleroot on a zip disk (which
is usually rz5 or rz6 - bsd crashes here :-)
* bsd.nfs - a generic kernel with root and swap configured
to be on nfs (also this kernel is in ecoff and not
in a.out format so that it can be netbooted with a
pmax)
Installing using a diskless setup.
First, you must setup a diskless client configuration on a server. If
you are using a OpenBSD system as the boot-server, have a look at the
diskless(8) manual page for guidelines on how to proceed with this.
If the server runs another operating system, you'll have to consult
documentation that came with it (on SunOS systems, add_client(8) is a
good start).
One part of the distribution of OpenBSD/pmax is a file called
simpleroot21.tar.gz which is a good start for the rootfilesystem area on
the NFS server then you want to install via network.
A few configuration files need to be edited:
/etc/hosts
Add the IP addresses of both server and client.
/etc/myname
This file contains the client's hostname; use the same
name as in /etc/hosts.
/etc/fstab
Enter the entries for the remotely mounted filesystems.
For example:
server:/export/root/client / nfs rw 0 0
Now you must populate the the `/dev' directory for your client. If you
have an intelligent tar command on the NFS server the /dev directory
inside the simpleroot21.tar.gz should be usable (i.e. containing
special devices and not only files) - else you'll have to remake the
devices on the server using
cd /export/root/client/dev
mv MAKEDEV* ..
rm -rf *
mkdir fd
mv ../MAKEDEV* .
./MAKEDEV all
This may not not work correctly on some operatingsystems.
Ok here is in shortform what you have to do on the Server to prepare a
diskless installation of OpenBSD/pmax assuming the Server is an
OpenBSD machine (for instance a PC running OpenBSD/1). As said
above for other systems you'll have to look into the supplied
documentation for that systems. All the following should apply also
without any major changes to an FreeBSD or NetBSD server.
If the following instructions are not enough - you may look at the
manpages for the following commands:
* tftpd
* rarpd
* bootpd
* rpc.bootparamd
Ok - now let's see what to do to set up the server:
* set up a file /etc/ethers containing the ethernet hardware address
of the pmax you want to boot via net and it's hostname (the hardware
address you should get via PROM commands)
example:
--- snip ---
08:00:2b:1a:4b:41 summer
--- snip ---
* add an entry to /etc/bootptab which looks like the following:
--- snip ---
.ris.dec:hn:vm=rfc1048
summer:ht=ethernet:ha=08002b1c4d51:ip=10.0.0.5:bf=/bsd
--- snip ---
* make shure that the following line in /etc/inetd.conf is not
commented out:
--- snip ---
tftp dgram udp wait root /usr/libexec/tftpd tftpd -s /tftpboot
--- snip ---
if it is commented out (which is the default on OpenBSD for security
reasons) - uncomment it and send the inetd process and HUP signal
kill -HUP `cat /var/run/inetd.pid`
so that it rereads the /etc/inetd.conf file
* untar the simpleroot.tar.gz on the server in an nfs exported
directory - for instance /export/root - so /etc/exports should
contain a line like (OpenBSD syntax !)
--- snip ---
/export -alldirs -root=0:0 summer
--- snip ---
for the example above - on OpenBSD the tar should be intelligent
enough to unpack the /dev directory correctly - on other systems you
may look at the comment about /dev above. So what you have to do in
this example you have to do:
mkdir /export/root
cd /export/root
tar xvpzf /some_path/simpleroot21.tar.gz
vi /etc/exports (to add the above line)
kill -HUP `cat /var/run/mountd.pid` (so that mountd rereads exports)
Note: also make shure that the server is configured as nfs server -
i.e. for OpenBSD "option NFSSERVER" for the kernel and the
following set in /etc/netstart:
--- snip ---
nfs_server="YES"
nfs_client="YES"
--- snip ---
* create an swapfile using (example 16 mbytes):
cd /exports
dd if=/dev/zero of=swap bs=1024k count=16
* copy the kernel from the /export/root area to the tftp area:
mkdir /tftpboot
cp /export/root/bsd_nfs /tftpboot
* create a /etc/bootparams file - for example:
--- snip ---
summer root=prospero:/export/root swap=prospero:/export/swap
--- snip ---
prospero is the hostname of the server in this example
* start the rquired daemons on the server:
/usr/sbin/rpc.bootparamd
/usr/sbin/rarpd -a
and bootpd - either by uncommenting the entry in /etc/inetd.conf and
sending inetd an HUP signal like above or by starting it explicitely
/usr/sbin/bootpd
* now you should be able to boot the pmax using:
>> boot -f tftp()/bsd_nfs
for 2100/3100 systems or
>> boot 6/tftp
for a 5000/200 - look into the manual of your pmax for details how
to boot via tftp
If you plan to use OpenBSD/pmax on a diskless system in the future -
keep in mind that the Decstations can only boot ecoff format kernels
via net - so you have to convert them explicitely after the kernel
compilation to ecoff - therefor in the kernel compile dir you can do
the following after the kernel compile has finished
elf2ecoff bsd.elf bsd.ecoff
then you can use the bsd.ecoff for netbooting - as a startingpoint for
the kernel config file you may choose GENERIC_NFS.
After you have set up everything correctly you can boot your system
over the network into singleuser mode and continue the installation.
Continuing the installation from single user mode
If you have reached single user mode either via booting the
simpleroot image or via booting over the network you will have to
relabel/label your disk and put filesystems on the patitions.
So here's what you have to do after going into single user mode:
- simpleroot image (assuming you have the simpleroot on rz0 and want
to install on that disk too - everytinh behind the ";" is comment)
# fsck /dev/rrz0a ; check the filesystem
# mount /dev/rz0a / ; mount / read write
# ./install
- network boot
# ./install
This script should bring you to a completely installed OpenBSD/pmax
system (in theory :-) - if you should run into any problems while
installing - please first look at
http://www.OpenBSD.org/pmax.html
I'll try to collect there any hints, fixes and so on. If your problem
can't be solved that way just send me a mail to graichen@OpenBSD.org
and i'll try to help you fixing it.
If you should somehow fail using the install script and want to
restart - you may have to umount any filesystems mounted while running
the install script (so all except /) and clean /tmp using:
rm /tmp/.??* /tmp/??*
then it should be possible to rerun it again.
Now some more notes about labeling the disk - which you will hjave to
do in the process of running the install script.
Here follows an example of what you'll see while in the dislabel editor.
Do not touch any of the parameters except for the `label: ' entry and
the actual partition size information at the bottom (the lines starting
with `a:', `b:', ...).
If you are using the simpleroot image and wan't to install onto the
same disk you put the simpleroot on you'll also have to change the
sector, track, cylinder, etc. entries to match the values for your
disk. The Problem is to get those values for your disk :-) - you can
either look into the /etc/disktab file for an matching entry or boot
another verbose system like OpenBSD/1 with your disk attached an
see what it prints out about the geometry of the disk. Also you can
get the total size of your disk from the bootup output of the
Decstation - look for lines like:
rz0 at sii0 drive 0 slave 0 SEAGATE ST1480 rev 7336, 832527 512 byte blocks
here 832527 is the number of total sectors on that disk.
The size and offset fields are given in sector units. Partitions on
which you intend to have a mountable filesystem, should be given
fstype `4.2BSD'. Remember, the `c' partition should describe the whole
disk. The `(Cyl. x - y)' info that appears after the hash (`#')
character is treated as a comment and need not be filled in when
altering partitions.
Special note: the line containing `8 partitions:' is best left alone,
even if you define less then eight partitions. If this line displays
a different number and the program complains about it (after you leave
the editor), then try setting it to `8 partitions:'.
Ok - now lets see how the default disklabel of the simpleroot image
looks like:
OpenBSD# disklabel rz0
# /dev/rrz0c:
type: SCSI
disk: simpleroot
label:
flags:
bytes/sector: 512
sectors/track: 32
tracks/cylinder: 64
sectors/cylinder: 2048
cylinders: 96
total sectors: 196608
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
#size offset fstype [fsize bsize cpg]
a: 65536 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 32*)
b: 131072 65536 swap # (Cyl. 32*- 96*)
c: 196608 0 unused 1024 8192 # (Cyl. 0 - 96*)
ok - and now let's see how it looks like if it is adapted for the rz0
disk above (SEAGATE ST1480).
OpenBSD# disklabel rz0
# /dev/rrz0c:
type: SCSI
disk: SEAGATE ST1480 r
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 11
sectors/cylinder: 693
cylinders: 832527
total sectors: 832527
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
#size offset fstype [fsize bsize cpg]
a: 65536 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 94*)
b: 131072 65536 swap # (Cyl. 94*- 283*)
c: 832527 0 unused 1024 8192 # (Cyl. 0 - 1201*)
d: 635919 196608 4.2BSD 1024 8192 16 # (Cyl. 283*- 1201*)
I hope you got the idea now - maybe it'll take some experiments until
you get it right :-). One thing to note here is that you can't change
the a and b partitions if you are relabeling the disk you are running
the simpleroot on - you'll have to accept the simpleroot values here
for those 2 partitions.
Note: if you have finished the disklabeling and exited the editor for
editing the label in the process of the installation and if you then
get a message like: "no disklabel on disk - use the -r option to write
one" you should ignore it and answer no to the question if you want to
reedit the disklabel - this is due to a problem with the pmax
disklabel code and it should be worked around by the install script.
So what does the install script explicitely do ?
These script will do most of the work of transferring the system from the
tar files onto your disk. You will frequently be asked for confirmation
before the script proceeds with each phase of the installation process.
Occasionally, you'll have to provide a piece of information such as the
name of the disk you want to install on or IP addresses and domain names
you want to assign.
The installation script goes through the following phases:
- determination of the disk to install OpenBSD on
- checking of the partition information on the disk
- creating and mounting the OpenBSD filesystems
- setup of IP configuration
- extraction of the distribution tar files
- installation of boot programs
If the installation worked fine we can go on.
Now try a reboot. (If needed, swap your scsi id's first). Initially
I'd suggest you "boot" (Decstation 2100/3100) or "boot/rz0a/bsd", then
try multiuser after that. if you boot single-user the OpenBSD
incarnation to make the root filesystem writable is
OpenBSD# fsck -p
OpenBSD# mount -u /dev/rz0a /
assuming your rootdisk is rz0.
Congratulations, you have successfully installed OpenBSD 2.1. When you
reboot into OpenBSD, you should log in as "root" at the login prompt.
There is no initial password, but if you're using the machine in a
networked environment, you should create yourself an account and
protect it and the "root" account with good passwords.
Some of the files in the OpenBSD 2.1 distribution might need to be
tailored for your site. In particular, the /etc/sendmail.cf file will
almost definitely need to be adjusted, and other files in /etc will
probably need to be modified. If you are unfamiliar with UN*X-like
system administration, it's recommended that you buy a book that
discusses it.
I am very interested in reports of how the installation worked - so if
you got OpenBSD/pmax installed (or if you have problems doing this)
please send a mail to me: graichen@OpenBSD.org - thanks.
Upgrading a previously-installed OpenBSD System:
------------------------------------------------
Because this is the first release of OpenBSD for the pmax - there is no
upgrade option in this release.
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
ANONCVS, CTM or FTP. For more information, see
http://www.openbsd.org/anoncvs.html
http://www.openbsd.org/ctm.html
http://www.openbsd.org/ftp.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),
apropos(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 . To get help on using the mailing
list server, send mail to that address with an empty body, and it will
reply with instructions. There are also two OpenBSD Usenet newsgroups,
comp.unix.bsd.openbsd.announce for important announcements and
comp.unix.bsd.openbsd.misc for general OpenBSD discussion.
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.