INSTALL(8) NetBSD System Manager's Manual INSTALL(8)

NNAAMMEE
IINNSSTTAALLLL -- Installation procedure for NetBSD/vax.

CCOONNTTEENNTTSS
About this Document
What is NetBSD?
Changes Between The NetBSD 9 and 10 Releases
Features to be removed in a later release
The NetBSD Foundation
Sources of NetBSD
NetBSD 10.1 Release Contents
NetBSD/vax subdirectory structure
Binary distribution sets
NetBSD/vax System Requirements and Supported Devices
Supported hardware
Getting the NetBSD System on to Useful Media
Creating boot tapes
Creating boot floppies
Booting from NFS server
Preparing your System for NetBSD installation
Installing the NetBSD System
Running the sysinst installation program
Introduction
Possible hardware problems
General
Quick install
Booting NetBSD
Network configuration
Installation drive selection and parameters
Selecting which sets to install
Partitioning the disk
Preparing your hard disk
Getting the distribution sets
Installation from CD-ROM
Installation using FTP
Installation using NFS
Installation from an unmounted file system
Installation from a local directory
Extracting the distribution sets
Configure additional items
Finalizing your installation
Post installation steps
Upgrading a previously-installed NetBSD System
Compatibility Issues With Previous NetBSD Releases
Using online NetBSD documentation
Administrivia
Thanks go to
Legal Mumbo-Jumbo
The End

DDEESSCCRRIIPPTTIIOONN
AAbboouutt tthhiiss DDooccuummeenntt
This document describes the installation procedure for
NetBSD 10.1 on the _v_a_x platform. It is available in four
different formats titled _I_N_S_T_A_L_L_._e_x_t, where _._e_x_t is one of
_._p_s, _._h_t_m_l, _._m_o_r_e, or _._t_x_t:

_._p_s PostScript.

_._h_t_m_l Standard Internet HTML.

_._m_o_r_e The enhanced text format used on UNIX-like
systems by the more(1) and less(1) pager util-
ity programs. This is the format in which the
on-line _m_a_n pages are generally presented.

_._t_x_t Plain old ASCII.

You are reading the _m_o_r_e version.

WWhhaatt iiss NNeettBBSSDD??
The NetBSD Operating System is a fully functional open-
source operating system derived from the University of Cali-
fornia, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite,
and 4.4BSD-Lite2 sources. NetBSD runs on many different
different system architectures (ports) across a variety of
distinct CPU families, and is being ported to more. The
NetBSD 10.1 release contains complete binary releases for
most of these system architectures, with preliminary support
for the others included in source form. For more informa-
tion please visit hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//.

NetBSD is a completely integrated system. In addition to
its highly portable, high performance kernel, NetBSD fea-
tures a complete set of user utilities, compilers for sev-
eral languages, the X Window System, firewall software and
numerous other tools, all accompanied by full source code.

NetBSD is a creation of the members of the Internet commu-
nity. Without the unique cooperation and coordination the
net makes possible, NetBSD would not exist.

CChhaannggeess BBeettwweeeenn TThhee NNeettBBSSDD 99 aanndd 1100 RReelleeaasseess
The NetBSD 10.1 release provides many significant changes,
including support for many new devices, hundreds of bug
fixes, new and updated kernel subsystems, and numerous user-
land enhancements. The result of these improvements is a
stable operating system fit for production use that rivals
most commercially available systems.

One important new feature in this release is the support for
extended attributes and access control lists on FFS file
systems.

For new installations the installer will by default disable
these features, so the file system is compatible with older
NetBSD releases (before 10), and allow other operating sys-
tems to mount this file systems at least in read-only mode.

If you want a new installed file system to support extended
attributes, change the file system type from ``FFSv2'' to
``FFSv2ea'' in the partitioning menu. You can also convert
file systems later, using the fsck_ffs(8) utility. More
details are available in _t_h_i_s _g_u_i_d_e_:
hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ttuuttoorriiaallss//aaccllss__aanndd__eexxtteennddeedd__aattttrriibbuutteess__oonn__ffffss.

If you are upgrading from a version of NetBSD -current
please also check the _C_o_m_p_a_t_i_b_i_l_i_t_y _I_s_s_u_e_s _W_i_t_h _P_r_e_v_i_o_u_s
_N_e_t_B_S_D _R_e_l_e_a_s_e_s. It is impossible to completely summarize
the massive development that went into the NetBSD 10.1
release. The complete list of changes can be found in
_C_H_A_N_G_E_S_:
hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD--1100..11//CCHHAANNGGEESS
_C_H_A_N_G_E_S_-_1_0_._1_:
hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD--1100..11//CCHHAANNGGEESS--1100..11
which are also present in the top level directory of the
NetBSD 10.1 release tree.

FFeeaattuurreess ttoo bbee rreemmoovveedd iinn aa llaatteerr rreelleeaassee
The following features are to be removed from NetBSD in the
future:

++oo groff(1). Man pages are now handled with
mandoc(1), and groff(1) can still be found in
pkgsrc as _t_e_x_t_p_r_o_c_/_g_r_o_f_f.

++oo pf(4). This packet filter is obsolete and unmain-
tained in NetBSD. It will be eventually removed
due to possible long-standing security issues and
lack of multiprocessor support. New installations
should use npf(7).

TThhee NNeettBBSSDD FFoouunnddaattiioonn
The NetBSD Foundation is a tax exempt, not-for-profit
501(c)(3) corporation that devotes itself to the traditional
goals and spirit of the NetBSD Project and owns the trade-
mark of the word ``NetBSD''. It supports the design, devel-
opment, and adoption of NetBSD worldwide. More information
on the NetBSD Foundation, its composition, aims, and work
can be found at:
hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ffoouunnddaattiioonn//

SSoouurrcceess ooff NNeettBBSSDD
Refer to _m_i_r_r_o_r_s_:
hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//mmiirrrroorrss//

NNeettBBSSDD 1100..11 RReelleeaassee CCoonntteennttss
The root directory of the NetBSD 10.1 release is organized
as follows:

_._._._/_N_e_t_B_S_D_-_1_0_._1_/

CHANGES Changes between the 9.0 and 10.0 releases.

CHANGES-10.0 Changes between the initial 10.0 branch and
final release of 10.0.

CHANGES-10.1 Changes between the 10.0 and the 10.1 release.

CHANGES.prev Changes in previous NetBSD releases.

LAST_MINUTE Last minute changes and notes about the
release.

README.files README describing the distribution's contents.

_i_m_a_g_e_s_/ Images (ISO 9660 or USB) for installing
NetBSD. Depending on your system, these may
be bootable.

_s_o_u_r_c_e_/ Source distribution sets; see below.

In addition to the files and directories listed above, there
is one directory per architecture, for each of the architec-
tures for which NetBSD 10.1 has a binary distribution.

The source distribution sets can be found in subdirectories
of the _s_o_u_r_c_e subdirectory of the distribution tree. They
contain the complete sources to the system. The source dis-
tribution sets are as follows:

ggnnuussrrcc This set contains the ``gnu'' sources, including
the source for the compiler, assembler, groff, and
the other GNU utilities in the binary distribution
sets.

sshhaarreessrrcc This set contains the ``share'' sources, which
include the sources for the man pages not associ-
ated with any particular program; the sources for
the typesettable document set; the dictionaries;
and more.

ssrrcc This set contains all of the base NetBSD 10.1
sources which are not in ggnnuussrrcc, sshhaarreessrrcc, or
ssyyssssrrcc.

ssyyssssrrcc This set contains the sources to the NetBSD 10.1
kernel for all architectures as well as the
config(1) utility.

xxssrrcc This set contains the sources to the X Window Sys-
tem.

All the above source sets are located in the _s_o_u_r_c_e_/_s_e_t_s
subdirectory of the distribution tree.

The source sets are distributed as compressed tar files.
Except for the ppkkggssrrcc set, which is traditionally unpacked
into _/_u_s_r_/_p_k_g_s_r_c, all sets may be unpacked into _/_u_s_r_/_s_r_c
with the command:
# ccdd // ;; ttaarr --zzxxppff sseett__nnaammee..ttggzz

In each of the source distribution set directories, there
are files which contain the checksums of the files in the
directory:

MD5 MD5 digests in the format produced by the com-
mand:
cckkssuumm --aa MMDD55 _f_i_l_e.

SHA512 SHA512 digests in the format produced by the
command:
cckkssuumm --aa SSHHAA551122 _f_i_l_e.

The SHA512 digest is safer, but MD5 checksums are provided
so that a wider range of operating systems can check the
integrity of the release files.

_N_e_t_B_S_D_/_v_a_x _s_u_b_d_i_r_e_c_t_o_r_y _s_t_r_u_c_t_u_r_e

The vax-specific portion of the NetBSD 10.1 release is found
in the _v_a_x subdirectory of the distribution:
_._._._/_N_e_t_B_S_D_-_1_0_._1_/_v_a_x_/. It contains the following files and
directories:

_I_N_S_T_A_L_L_._h_t_m_l
_I_N_S_T_A_L_L_._p_s
_I_N_S_T_A_L_L_._t_x_t
_I_N_S_T_A_L_L_._m_o_r_e Installation notes in various file formats,
including this file. The _._m_o_r_e file contains
underlined text using the more(1) conventions
for indicating italic and bold display.
_b_i_n_a_r_y_/
_k_e_r_n_e_l_/
_n_e_t_b_s_d_-_G_E_N_E_R_I_C_._g_z
A gzipped NetBSD kernel
containing code for every-
thing supported in this
release.
_n_e_t_b_s_d_-_G_E_N_E_R_I_C_._M_P_._g_z
A gzipped NetBSD kernel
containing code for every-
thing supported in this
release. This kernel sup-
ports SMP on systems with
more than one CPU.
_s_e_t_s_/ vax binary distribution sets; see
below.
_i_n_s_t_a_l_l_a_t_i_o_n_/
_m_i_s_c_/ Miscellaneous vax installation
utilities; see installation section
below.

_B_i_n_a_r_y _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s

The NetBSD vax binary distribution sets contain the binaries
which comprise the NetBSD 10.1 release for vax. The binary
distribution sets can be found in the _v_a_x_/_b_i_n_a_r_y_/_s_e_t_s subdi-
rectory of the NetBSD 10.1 distribution tree, and are as
follows:

bbaassee The NetBSD 10.1 vax bbaassee binary distribution. You
_m_u_s_t install this distribution set. It contains
the base NetBSD utilities that are necessary for
the system to run and be minimally functional.

ccoommpp Things needed for compiling programs. This set
includes the system include files (_/_u_s_r_/_i_n_c_l_u_d_e)
and the various system libraries (except the shared
libraries, which are included as part of the bbaassee
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.

ddeebbuugg This distribution set contains debug information
for all base system utilities. It is useful when
reporting issues with binaries or during develop-
ment. This set is huge, if the target disk is
small, do not install it.

eettcc This distribution set contains the system configu-
ration files that reside in _/_e_t_c and in several
other places. This set _m_u_s_t be installed if you
are installing the system from scratch, but should
_n_o_t be used if you are upgrading.

ggaammeess This set includes the games and their manual pages.

kkeerrnn--GGEENNEERRIICC
This set contains a NetBSD/vax 10.1 GENERIC kernel,
named _/_n_e_t_b_s_d. You _m_u_s_t install either this dis-
tribution set, kern-GENERIC.MP or kern-GENERIC_USB.

kkeerrnn--GGEENNEERRIICC__UUSSBB
This set contains a NetBSD/vax 10.1 GENERIC_USB
kernel, named _/_n_e_t_b_s_d. This kernel supports vsbus
USB host controllers and some USB devices. You
_m_u_s_t install either this distribution set, kern-
GENERIC.MP or kern-GENERIC.

kkeerrnn--GGEENNEERRIICC..MMPP
This set contains a NetBSD/vax 10.1 GENERIC.MP ker-
nel, named _/_n_e_t_b_s_d. This kernel supports multiple
CPUs (if available). You _m_u_s_t install either this
distribution set, kern-GENERIC or kern-GENERIC_USB.

mmaann This set includes all of the manual pages for the
binaries and other software contained in the bbaassee
set. Note that it does not include any of the man-
ual pages that are included in the other sets.

mmiisscc This set includes the system dictionaries, the
typesettable document set, and other files from
_/_u_s_r_/_s_h_a_r_e.

mmoodduulleess This set includes kernel modules to add functional-
ity to a running system.

rreessccuuee This set includes the statically linked emergency
recovery binaries installed in _/_r_e_s_c_u_e.

tteexxtt This set includes NetBSD's text processing tools,
including groff(1), all related programs, and their
manual pages.

NetBSD maintains its own set of sources for the X Window
System in order to assure tight integration and compatibil-
ity. These sources are based on X.Org. Binary sets for the
X Window System are distributed with NetBSD. The sets are:

xxbbaassee The basic files needed for a complete X client
environment. This does not include the X servers.

xxccoommpp The extra libraries and include files needed to
compile X source code.

xxddeebbuugg This distribution set contains debug information
for all X11 binaries. It is useful when reporting
issues with these binaries or during development.
This set is huge, if the target disk is small, do
not install it.

xxffoonntt Fonts needed by the X server and by X clients.

xxeettcc Configuration files for X which could be locally
modified.

xxsseerrvveerr The X server.

The vax binary distribution sets are distributed as gzipped
tar files named with the extension ..ttggzz, e.g. _b_a_s_e_._t_g_z.

The instructions given for extracting the source sets work
equally well for the binary sets, but it is worth noting
that if you use that method, the filenames stored in the
sets are relative and therefore the files are extracted
_b_e_l_o_w _t_h_e _c_u_r_r_e_n_t _d_i_r_e_c_t_o_r_y. Therefore, if you want to
extract the binaries into your system, i.e. replace the
system binaries with them, you have to run the ttaarr --xxzzppff
command from the root directory ( _/ ) of your system.

_N_o_t_e_: Each directory in the vax binary distribution also
has its own checksum files, just as the source dis-
tribution does.

NNeettBBSSDD//vvaaxx SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess
_S_u_p_p_o_r_t_e_d _h_a_r_d_w_a_r_e

++oo CPU types
-- VAX 11/750
-- VAX 11/78{0,5}
-- VAX 4000 model
100(A),105A,106A,108,200,300,400,500(A),505A,600(A),700
-- VAX 8200/8250/8300/8350
-- VAX 8600/8650
-- MicroVAX/VAXstation II
-- MicroVAX III
-- MicroVAX 3100 model
10,10e,20,20e,30,40,80,85,90,95
-- MicroVAX 3300/3400
-- MicroVAX 3500/3600
-- MicroVAX 3800/3900
-- MicroVAX 2000/VAXstation 2000
-- VAXstation 3100 model 30,38,40,48,76
-- VAXserver 3100 KA41-B and KA41-E
-- VAXserver 3600
-- VAXserver 3900
-- VAXstation 3200/3500
-- VAXstation 4000 models 60,90,90A,96 and VLC

++oo Networking
-- DEUNA/DELUA Unibus ethernet
-- DEQNA/DELQA Q22 bus ethernet
-- LANCE chip (where available)
-- SGEC chip (where available)

++oo Serial lines
-- DHU11/DHV11/DL11/DLV11/DZ11/DZQ11/DZV11
Unibus/Q22 bus asynchronous lines
-- DZ11-compatible lines on VAXstations.

++oo Disks
-- UDA50 Unibus MSCP controller
-- KDA50/RQDX1/2/3 Q22 bus
-- MSCP controller
-- KDB50 BI-bus MSCP controller
-- MFM and SCSI controllers on VAXstations
-- RP04/05/06/07 and RM02/03/05/80 Massbus disks
-- Console RL02 on VAX 8600.

Some third-party controllers are also known to
work, others do not.

++oo Tapes
-- TMSCP on Q22 bus (TK50/70, TU81)
-- TMSCP on BI bus
-- SCSI tapes on VAXstations.

++oo Floppy
-- RX33/RX50 on RQDX controllers
-- RX50 on VAX 8200

The minimal configuration requires 2 MB of RAM and ~130 MB
of disk space, but the installation really requires 6 MB RAM
unless you plan on using Jedi powers.

Here is a table of recommended HD partition sizes for a full
install:

Partition Suggested Needed
/ (root) 32 MB 16 MB
/usr 110 MB 45 MB
/var 20 MB 5 MB
swap _2_-_3 _*_R_A_M

Anything else is up to you!

GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn ttoo UUsseeffuull MMeeddiiaa
Installing on a `bare' machine requires some bootable
device; either a tape, CD-ROM or floppy drive or a NFS
server together with a machine that can act as a MOP loader,
such as another machine running NetBSD. NetBSD/vax can use
both BOOTP/DHCP and BOOTPARAMS for netboot installations.

Installation is supported from several media types, includ-
ing:

++oo CD-ROM / DVD / USB stick
++oo FTP
++oo Remote NFS partition
++oo Tape
++oo Existing NetBSD partitions, if performing an
upgrade

The steps necessary to prepare the distribution sets for
installation depend upon which installation medium you
choose. The steps for the various media are outlined below.

_C_D_-_R_O_M _/ _D_V_D _/ _U_S_B _s_t_i_c_k Find out where the distribution
set files are on the CD-ROM, DVD
or USB stick. Likely locations
are _b_i_n_a_r_y_/_s_e_t_s and
_v_a_x_/_b_i_n_a_r_y_/_s_e_t_s. (You only need
to know this if you are mixing
installer and installation media
from different versions - the
installer will know the proper
default location for the sets it
comes with).

Proceed to the instructions on
installation.

_F_T_P The preparations for this instal-
lation/upgrade method are easy;
all you need to do is make sure
that there's an FTP site from
which you can retrieve the NetBSD
distribution when you're about to
install or upgrade. If you don't
have DHCP available on your net-
work, you will need to know the
numeric IP address of that site,
and, if it's not on a network
directly connected to the machine
on which you're installing or
upgrading NetBSD, you need to know
the numeric IP address of the
router closest to the NetBSD
machine. Finally, you need to
know the numeric IP address of the
NetBSD machine itself.

Once you have this information,
you can proceed to the next step
in the installation or upgrade
process. If you're installing
NetBSD from scratch, go to the
section on preparing your hard
disk, below. If you're upgrading
an existing installation, go
directly to the section on upgrad-
ing.

_N_F_S Place the NetBSD distribution sets
you wish to install into a direc-
tory on an NFS server, and make
that directory mountable by the
machine on which you are
installing or upgrading NetBSD.
This will probably require modify-
ing the _/_e_t_c_/_e_x_p_o_r_t_s file on the
NFS server and resetting its mount
daemon (mountd). (Both of these
actions will probably require
superuser privileges on the
server.)

You need to know the numeric IP
address of the NFS server, and, if
you don't have DHCP available on
your network and the server is not
on a network directly connected to
the machine on which you're
installing or upgrading NetBSD,
you need to know the numeric IP
address of the router closest to
the NetBSD machine. Finally, you
need to know the numeric IP
address of the NetBSD machine
itself.

Once the NFS server is set up
properly and you have the informa-
tion mentioned above, you can pro-
ceed to the next step in the
installation or upgrade process.
If you're installing NetBSD from
scratch, go to the section on pre-
paring your hard disk, below. If
you're upgrading an existing
installation, go directly to the
section on upgrading.

_T_a_p_e To install NetBSD from a tape, you
need to make a tape that contains
the distribution set files, in
`tar' format.

_N_o_t_e_: the tape devices with which
NetBSD/vax is believed to
work is the DEC TK-50.
This is a very slow device.
Installation via disk or
network is recommended if
possible.

If you're making the tape on a
UNIX-like system, the easiest way
to do so is probably something
like:

# ttaarr --ccff _t_a_p_e___d_e_v_i_c_e
_d_i_s_t___s_e_t_s

where _t_a_p_e___d_e_v_i_c_e is the name of
the tape device that represents
the tape drive you're using. This
might be _/_d_e_v_/_r_s_t_0, or something
similar, but it will vary from
system to system. In the above
example, _d_i_s_t___s_e_t_s is a list of
filenames corresponding to the
distribution sets that you wish to
place on the tape. For instance,
to put the kkeerrnn--GGEENNEERRIICC,, bbaassee,, and
eettcc distributions on tape (the
absolute minimum required for
installation), you would do the
following:

# ccdd ......//NNeettBBSSDD--1100..11
# ccdd vvaaxx//bbiinnaarryy
# ttaarr --ccff _t_a_p_e___d_e_v_i_c_e
kkeerrnn--GGEENNEERRIICC..ttggzz bbaassee..ttggzz
eettcc..ttggzz

_N_o_t_e_: You still need to fill in
_t_a_p_e___d_e_v_i_c_e in the example.

Once you have the files on the
tape, you can proceed to the next
step in the installation or
upgrade process. If you're
installing NetBSD from scratch, go
to the section on preparing your
hard disk, below. If you're
upgrading an existing installa-
tion, go directly to the section
on upgrading.

_C_r_e_a_t_i_n_g _b_o_o_t _t_a_p_e_s

Fetch the bootable bootfs image from

_._._._/_N_e_t_B_S_D_-_1_0_._1_/_v_a_x_/_i_n_s_t_a_l_l_a_t_i_o_n_/_b_o_o_t_f_s_/_b_o_o_t_._f_s

and write it on the beginning of the tape. Under NetBSD
this is done (for MSCP tape, with SCSI tape the name is
nrst0) via:

# mmtt --ff //ddeevv//nnrrmmtt00 rreewwiinndd
# dddd iiff==bboooott..ffss ooff==//ddeevv//nnrrmmtt00 ccoonnvv==oossyynncc
# mmtt --ff //ddeevv//nnrrmmtt00 rreewwooffffll

Under Ultrix the tape name is different:

# mmtt --ff //ddeevv//rrmmtt00hh rreewwiinndd
# dddd iiff==bboooott..ffss ooff==//ddeevv//rrmmtt00hh ccoonnvv==oossyynncc
# mmtt --ff //ddeevv//rrmmtt00hh rreewwooffffll

Of course, if you have a tape unit other than unit 0 you
have to use the corresponding unit number.

If you wish to install the sets from tape you will need to
download the *.tgz files from

_._._._/_N_e_t_B_S_D_-_1_0_._1_/_v_a_x_/_b_i_n_a_r_y_/_s_e_t_s_{_5_0_,_3_3_}

(if your disk is less than 200 MB you will probably want to
exclude the X sets) and then before the mmtt ...... rreewwooffffll run

# ttaarr --ccvvff //ddeevv//nnrrmmtt00 **..ttggzz

When you have booted the bootfs and completed the disk par-
titioning you will be prompted to sseelleecctt mmeeddiiuumm for install.
At this point you will need to press CONTROL-Z to suspend
the install tool, then

# ccdd //mmnntt
# mmtt --ff //ddeevv//nnrrmmtt00 rreewwiinndd
# mmtt --ff //ddeevv//nnrrmmtt00 ffssff
# ttaarr --xxvvff //ddeevv//nnrrmmtt00
# ffgg

then select ``install from local dir'' and give _/_m_n_t.

_N_o_t_e_: If your disk is small you will need to be careful
about filling it up.

If you are using any other OS to create bootable tapes,
remember that the blocksize _m_u_s_t be 512 for the file to be
bootable! Otherwise it just won't work.

_C_r_e_a_t_i_n_g _b_o_o_t _f_l_o_p_p_i_e_s

Fetch the bootable bootfs image from

_._._._/_N_e_t_B_S_D_-_1_0_._1_/_v_a_x_/_i_n_s_t_a_l_l_a_t_i_o_n_/_b_o_o_t_f_s_/_b_o_o_t_._f_s

and gguunnzziipp it. It is a 1.2MB bootable image that will boot
from any floppy of size 1.2MB and bigger. Note that you
_c_a_n_n_o_t install from RX50 floppies due to the small size.
This may change in the future.

All floppies except RX50 use a standardized format for stor-
ing data so writing the bootfs to the floppy can be done on
any PC. From MS-DOS the preferred way to do this is using
rraawwrriittee..eexxee.

_B_o_o_t_i_n_g _f_r_o_m _N_F_S _s_e_r_v_e_r

All VAXen that can boot over network use MOP, a DEC proto-
col. To be able to use MOP, a MOP daemon must be present on
one of the machines on the local network. The boot princi-
ple is:
++oo The VAX broadcasts a request to load an image.
++oo A mopd answers and sends the boot program to the
VAX.
++oo The boot program does rarp/bootp requests, mounts
the root file system and loads the kernel.
++oo The kernel is loaded and starts executing.

If your machine has a disk and network connection, it may be
convenient for you to install NetBSD over the network. This
involves temporarily booting your machine over NFS, just
long enough so you can initialize its disk. This method
requires that you have access to an NFS server on your net-
work which you can configure to support diskless boot for
your machine. Configuring the NFS server is normally a task
for a system administrator, and is not trivial.

If you are using a NetBSD 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, consult the documentation that came with it. (For
example add_client(8) on SunOS.)

There is also very useful documentation at
hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//nneettwwoorrkk//nneettbboooott//

You also must install a MOP loader. If you are booting from
another NetBSD machine, the MOP daemons are included in the
distribution, otherwise you may have to install a MOP
loader. A loader can be found at
ffttpp..ssttaacckkeenn..kktthh..ssee:://ppuubb//OOSS//NNeettBBSSDD//mmooppdd
Fetch the latest and read the installation instructions.

The file that should be loaded is called boot and is located
in

_._._._/_N_e_t_B_S_D_-_1_0_._1_/_v_a_x_/_i_n_s_t_a_l_l_a_t_i_o_n_/_n_e_t_b_o_o_t_/_b_o_o_t

The kernel to load is the same kernel as the bootfs uses and
can be found in

_._._._/_N_e_t_B_S_D_-_1_0_._1_/_v_a_x_/_i_n_s_t_a_l_l_a_t_i_o_n_/_n_e_t_b_o_o_t_/_n_e_t_b_s_d_._r_a_m_._g_z

From the install program started in the kernel the rest of
the system can be installed. There is also a very good (if
somewhat out of date) FAQ for netbooting VAXen at
hhttttpp::////wwoorrlldd..ssttdd..ccoomm//~~bbddcc//pprroojjeeccttss//vvaaxxeenn//VVAAXX--nneettbboooott--HHOOWWTTOO..hhttmmll
that describes netbooting of VAXen from many different OSes.

PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD iinnssttaallllaattiioonn
VAX machines usually need little or no preparation before
installing NetBSD, other than the usual well advised precau-
tion of BACKING UP ALL DATA on any attached storage devices.

If you are on a Q-bus or Unibus system the disk con-
troller(s) need be at the standard CSR addresses for DUA
(772150) or DUB (760334) to be recognized by the kernel and
boot programs.

If you are installing on a VAXstation you _m_a_y require a
serial console.

IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm
Installation of NetBSD/vax is now easier than ever! For the
latest news, problem reports, and discussion, join the port-
vax maillist by mailing a line saying

subscribe port-vax

to _m_a_j_o_r_d_o_m_o_@_N_e_t_B_S_D_._o_r_g. Also, see hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//
for more information.

If you encounter any problems, please report them via the
mailing list or the send-pr(1) program so that they can be
fixed for the next release.

To install or upgrade NetBSD, you need to first boot the
installation program and then interact with the screen-menu
program ssyyssiinnsstt. The installation program actually consists
of the NetBSD kernel plus an in-memory file system of util-
ity programs.

The usual procedure is to write the installation system to
the install media, as described earlier.

Booting from install media

The built-in console monitor understands a bunch of com-
mands, dependent on which VAX you have. To just boot from a
device, type `BB' at the >>> prompt. Device naming in the
console monitor differs a lot from the UNIX counterparts. A
device looks like ddcu, where `dd' is the device type, `c'
is the controller number and `u' is the device unit. Many
console monitors also support the SSHHOOWW DDEEVV command, which
shows available units to boot from.

A summary of the most common boot devices and their name:

BB DDUUAA00 first MSCP controller, unit 0.

BB MMUUAA00 first TMSCP tape controller, unit 0.

BB DDKKBB00 second SCSI bus, unit 0.

BB XXQQAA00 first Q22 bus Ethernet controller.

BB EESSAA00 first LANCE Ethernet controller on VAXstations.

BB EEZZAA00 first SGEC Ethernet controller on VAXstations.
Other devices may be appropriate for your configuration.

Then just proceed with the program ssyyssiinnsstt. The procedure
that is described below can be easily adapted to VAX.

_R_u_n_n_i_n_g _t_h_e _s_y_s_i_n_s_t _i_n_s_t_a_l_l_a_t_i_o_n _p_r_o_g_r_a_m

1. _I_n_t_r_o_d_u_c_t_i_o_n

Using ssyyssiinnsstt, installing NetBSD is a relatively easy
process. Still, you should read this document and have
it available during the installation process. This
document tries to be a good guide to the installation,
and as such, covers many details for the sake of com-
pleteness. Do not let this discourage you; the install
program is not hard to use.

2. _P_o_s_s_i_b_l_e _h_a_r_d_w_a_r_e _p_r_o_b_l_e_m_s

Should you encounter hardware problems during installa-
tion, try rebooting after unplugging removable devices
you don't need for installation. Non-removable devices
can be disabled with uusseerrccoonnff (use bboooott --cc to enter
it).

3. _G_e_n_e_r_a_l

The following is a walk-through of the steps you will
take while installing NetBSD on your hard disk.
ssyyssiinnsstt is a menu-driven program that guides you
through the installation process. Sometimes questions
will be asked, and in many cases the default answer
will be displayed in brackets (``[ ]'') after the ques-
tion. If you wish to stop the installation, you may
press CONTROL-C at any time, but if you do, you'll have
to begin the installation process again from scratch by
running the _/_s_y_s_i_n_s_t program from the command prompt.
It is not necessary to reboot.

4. _Q_u_i_c_k _i_n_s_t_a_l_l

First, let's describe a quick install. The other sec-
tions of this document go into the installation proce-
dure in more detail, but you may find that you do not
need this. If you want detailed instructions, skip to
the next section. This section describes a basic
installation, using a CD / DVD as the install medium.

++oo What you need.

-- The distribution sets (in this example, they
are on the CD or DVD).

-- One 1.44 MB 3.5" floppy.

-- A minimum of of memory installed.

-- An optical drive.

-- A hard drive with at least 500 MB of free space
for a complete base install, not including room
for swap. If you wish to install the X Window
System as well, you will need at least 225 MB
more.

++oo The Quick Installation

-- Insert the first boot floppy you just created
and boot the computer. After language selec-
tion, the main menu will be displayed.

.***********************************************.
* NetBSD-10.1 Install System *
* *
*>a: Install NetBSD to hard disk *
* b: Upgrade NetBSD on a hard disk *
* c: Re-install sets or install additional sets *
* d: Reboot the computer *
* e: Utility menu *
* f: Config menu *
* x: Exit Install System *
.***********************************************.

-- If you wish, you can configure some network
settings immediately by choosing the UUttiilliittyy
mmeennuu and then CCoonnffiigguurree nneettwwoorrkk. It isn't
actually required at this point, but it may be
more convenient. Go back to the main menu.

-- Choose IInnssttaallll.

-- You will be guided through the setup of your
disk.

-- You will be asked to choose which distribution
sets to install.

-- When prompted, choose CCDD--RROOMM as the install
medium if booted from CD-ROM. The default val-
ues for the path and device should be OK.

-- After the installation process has completed,
you will be brought back to the main menu,
where you should select RReebboooott, after you have
removed the bootfloppy from the drive.

-- NetBSD will now boot. If you didn't set a
password for the root user when prompted by
ssyyssiinnsstt, logging in as root and setting a pass-
word should be your first task. You are also
advised to read afterboot(8).

5. _B_o_o_t_i_n_g _N_e_t_B_S_D

Boot your machine. The boot loader will start, which
will print a countdown and begin booting.

If the boot loader messages do not appear in a reason-
able amount of time, you either have a bad boot floppy
or a hardware problem. Try writing the install floppy
image to a different disk, and using that.

It will take a while to load the kernel from the
floppy, probably around a minute or so; then the kernel
boot messages will be displayed. This may take a lit-
tle while also, as NetBSD will be probing your system
to discover which hardware devices are installed. The
most important thing to know is that wd0 is NetBSD's
name for your first SATA/PATA disk, wd1 the second,
etc. sd0 is your first SCSI disk, sd1 the second, etc.

Note that once the system has finished booting, you
need not leave the floppy in the disk drive.

Once NetBSD has booted and printed all the boot mes-
sages, you will be presented with a welcome message and
a main menu. It will also include instructions for
using the menus.

6. _N_e_t_w_o_r_k _c_o_n_f_i_g_u_r_a_t_i_o_n

If you do not intend to use networking during the
installation, but you do want your machine to be con-
figured for networking once the system is installed,
you should first go to the UUttiilliittyy mmeennuu and select the
CCoonnffiigguurree nneettwwoorrkk option. If you only want to tempo-
rarily use networking during the installation, you can
specify these parameters later. If you are not using
the Domain Name System (DNS), you can give an empty
response when asked to provide a server.

7. _I_n_s_t_a_l_l_a_t_i_o_n _d_r_i_v_e _s_e_l_e_c_t_i_o_n _a_n_d _p_a_r_a_m_e_t_e_r_s

To start the installation, select IInnssttaallll NNeettBBSSDD ttoo
hhaarrdd ddiisskk from the main menu.

The first thing is to identify the disk on which you
want to install NetBSD. ssyyssiinnsstt will report a list of
disks it finds and ask you for your selection. You
should see disk names like sd0 or sd1.

8. _S_e_l_e_c_t_i_n_g _w_h_i_c_h _s_e_t_s _t_o _i_n_s_t_a_l_l

The next step is to choose which distribution sets you
wish to install. Options are provided for full, mini-
mal, and custom installations. If you choose sets on
your own, bbaassee, eettcc, and a kernel must be selected.

9. _P_a_r_t_i_t_i_o_n_i_n_g _t_h_e _d_i_s_k

++oo Choosing which portion of the disk to use.

You will be asked if you want to use the entire
disk or only part of the disk. If you decide to
use the entire disk for NetBSD, ssyyssiinnsstt will check
for the presence of other operating systems and you
will be asked to confirm that you want to overwrite
these.

10. _E_d_i_t_i_n_g _t_h_e _N_e_t_B_S_D _d_i_s_k_l_a_b_e_l

The partition table of the NetBSD part of a disk is
called a _d_i_s_k_l_a_b_e_l. If your disk already has a diskla-
bel written to it, you can choose UUssee eexxiissttiinngg
ppaarrttiittiioonn ssiizzeess. Otherwise, select SSeett ssiizzeess ooff NNeettBBSSDD
ppaarrttiittiioonnss.

After you have chosen your partitions and their sizes
(or if you opted to use the existing partitions), you
will be presented with the layout of the NetBSD diskla-
bel and given one more chance to change it. For each
partition, you can set the type, offset and size, block
and fragment size, and the mount point. The type that
NetBSD uses for normal file storage is called 44..22BBSSDD.
A swap partition has a special type called sswwaapp. Some
partitions in the disklabel have a fixed purpose.

a Root partition (_/)

b Swap partition.

c The entire disk.

d-h Available for other use. Traditionally,
d is the partition mounted on _/_u_s_r, but
this is historical practice and not a
fixed value.

You will then be asked to name your disk's disklabel.
The default response will be OK for most purposes. If
you choose to name it something different, make sure
the name is a single word and contains no special char-
acters. You don't need to remember this name.

11. _P_r_e_p_a_r_i_n_g _y_o_u_r _h_a_r_d _d_i_s_k

_Y_o_u _a_r_e _n_o_w _a_t _t_h_e _p_o_i_n_t _o_f _n_o _r_e_t_u_r_n. Nothing has
been written to your disk yet, but if you confirm that
you want to install NetBSD, your hard drive will be
modified. If you are sure you want to proceed, select
yyeess.

The install program will now label your disk and create
the file systems you specified. The file systems will
be initialized to contain NetBSD bootstrapping binaries
and configuration files. You will see messages on your
screen from the various NetBSD disk preparation tools
that are running. There should be no errors in this
section of the installation. If there are, restart
from the beginning of the installation process. Other-
wise, you can continue the installation program after
pressing the return key.

12. _G_e_t_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s

The NetBSD distribution consists of a number of _s_e_t_s
that come in the form of gzipped tar files. At this
point, you will be presented with a menu which enables
you to choose from one of the following methods of
installing the sets. Some of these methods will first
transfer the sets to your hard disk, others will
extract the sets directly.

For all these methods, the first step is to make the
sets available for extraction. The sets can be made
available in a few different ways. The following sec-
tions describe each of the methods. After reading
about the method you will be using, you can continue to
the section labeled `Extracting the distribution sets'.

13. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _C_D_-_R_O_M

When installing from a CD-ROM, you will be asked to
specify the device name for your CD-ROM drive (usually
cd0) and the directory name on the CD-ROM where the
distribution files are.

ssyyssiinnsstt will then check that the files are actually
present in the specified location and proceed to the
extraction of the sets.

14. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _F_T_P

To install using FTP, you first need to configure your
network setup if you haven't already done so. ssyyssiinnsstt
will help you with this, asking if you want to use
DHCP. If you do not use DHCP, you can enter network
configuration details yourself. If you do not have DNS
set up for the machine that you are installing on, you
can just press RETURN in answer to this question, and
DNS will not be used.

You will also be asked to specify the host that you
want to transfer the sets from, the directory on that
host, the account name and password used to log into
that host using FTP, and optionally a proxy server to
use. If you did not set up DNS, you will need to spec-
ify an IP address instead of a hostname for the FTP
server.

ssyyssiinnsstt will then transfer the set files from the
remote site to your hard disk.

15. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _N_F_S

To install using NFS, you first need to configure your
network setup if you haven't already done so. ssyyssiinnsstt
will do this for you, asking you if you want to use
DHCP. If you do not use DHCP, you can enter network
configuration details yourself. If you do not have DNS
set up for the machine that you are installing on, you
can just press RETURN in answer to this question, and
DNS will not be used.

You will also be asked to specify the host that you
want to transfer the sets from and the directory on
that host that the files are in. This directory should
be mountable by the machine you are installing on,
i.e., correctly exported to your machine.

If you did not set up DNS, you will need to specify an
IP address instead of a hostname for the NFS server.

16. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a_n _u_n_m_o_u_n_t_e_d _f_i_l_e _s_y_s_t_e_m

In order to install from a local file system, you will
need to specify the device that the file system resides
on (for example wd1e), the type of the file system, and
the directory on the specified file system where the
sets are located. ssyyssiinnsstt will then check if it can
indeed access the sets at that location.

17. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a _l_o_c_a_l _d_i_r_e_c_t_o_r_y

This option assumes that you have already done some
preparation yourself. The sets should be located in a
directory on a file system that is already accessible.
ssyyssiinnsstt will ask you for the name of this directory.

18. _E_x_t_r_a_c_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s

A progress bar will be displayed while the distribution
sets are being extracted.

After all the files have been extracted, the device
node files will be created. If you have already con-
figured networking, you will be asked if you want to
use this configuration for normal operation. If so,
these values will be installed in the network configu-
ration files.

19. _C_o_n_f_i_g_u_r_e _a_d_d_i_t_i_o_n_a_l _i_t_e_m_s

The next menu will allow you to select a number of
additional items to configure, including the time zone
that you're in, to make sure your clock has the right
offset from UTC, the root user's shell, and the initial
root password.

You can also enable installation of binary packages,
which installs the pkgin(1) tool for managing binary
packages for third-party software. This will feel
familiar to users of package tools such as aapptt--ggeett or
yyuumm. If you prefer to install third-party software
from source, you can install the pkgsrc(7) tree.

Finally, you can enable some daemons such as sshd(8),
ntpd(8), or mdnsd(8).

20. _F_i_n_a_l_i_z_i_n_g _y_o_u_r _i_n_s_t_a_l_l_a_t_i_o_n

Congratulations, you have successfully installed NetBSD
10.1. You can now reboot the machine and boot NetBSD
from hard disk.

PPoosstt iinnssttaallllaattiioonn sstteeppss
Once you've got the operating system running, there are a
few things you need to do in order to bring the system into
a properly configured state. The most important steps are
described below.

1. Before all else, read postinstall(8).

2. Configuring _/_e_t_c_/_r_c_._c_o_n_f

If you or the installation software haven't done any
configuration of _/_e_t_c_/_r_c_._c_o_n_f (ssyyssiinnsstt normally will),
the system will drop you into single user mode on first
reboot with the message

/etc/rc.conf is not configured. Multiuser boot
aborted.

and with the root file system (_/) mounted read-only.
When the system asks you to choose a shell, simply
press RETURN to get to a _/_b_i_n_/_s_h prompt. If you are
asked for a terminal type, respond with vvtt222200 (or what-
ever is appropriate for your terminal type) and press
RETURN. You may need to type one of the following com-
mands to get your delete key to work properly, depend-
ing on your keyboard:
# ssttttyy eerraassee ''^^hh''
# ssttttyy eerraassee ''^^??''
At this point, you need to configure at least one file
in the _/_e_t_c directory. You will need to mount your
root file system read/write with:
# //ssbbiinn//mmoouunntt --uu --ww //
Change to the _/_e_t_c directory and take a look at the
_/_e_t_c_/_r_c_._c_o_n_f file. Modify it to your tastes, making
sure that you set rc_configured=YES so that your
changes will be enabled and a multi-user boot can pro-
ceed. Default values for the various programs can be
found in _/_e_t_c_/_d_e_f_a_u_l_t_s_/_r_c_._c_o_n_f, where some in-line doc-
umentation may be found. More complete documentation
can be found in rc.conf(5).

When you have finished editing _/_e_t_c_/_r_c_._c_o_n_f, type eexxiitt
at the prompt to leave the single-user shell and con-
tinue with the multi-user boot.

Other values that may need to be set in _/_e_t_c_/_r_c_._c_o_n_f
for a networked environment are _h_o_s_t_n_a_m_e and possibly
_d_e_f_a_u_l_t_r_o_u_t_e. You may also need to add an _i_f_c_o_n_f_i_g___i_n_t
for your <int> network interface, along the lines of

ifconfig_le0="inet 192.0.2.123 netmask
255.255.255.0"

or, if you have _m_y_n_a_m_e_._m_y_._d_o_m in _/_e_t_c_/_h_o_s_t_s:

ifconfig_le0="inet myname.my.dom netmask
255.255.255.0"

To enable proper hostname resolution, you will also
want to add an _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f file or (if you are
feeling a little more adventurous) run named(8). See
resolv.conf(5) or named(8) for more information.

Instead of manually configuring networking, DHCP can be
used by setting dhcpcd=YES in _/_e_t_c_/_r_c_._c_o_n_f.

3. Logging in

After reboot, you can log in as root at the login
prompt. If you didn't set a password in ssyyssiinnsstt, there
is no initial password. You should create an account
for yourself (see below) and protect it and the
``root'' account with good passwords. By default, root
login from the network is disabled (even via ssh(1)).
One way to become root over the network is to log in as
a different user that belongs to group ``wheel'' (see
group(5)) and use su(1) to become root.

4. Adding accounts

Use the useradd(8) command to add accounts to your sys-
tem. Do not edit _/_e_t_c_/_p_a_s_s_w_d directly! See vipw(8) and
pwd_mkdb(8) if you want to edit the password database.

5. The X Window System

If you installed the X Window System, you may want to
read the chapter about X in the _N_e_t_B_S_D _G_u_i_d_e_:
hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//gguuiiddee//eenn//cchhaapp--xx..hhttmmll:

6. Installing third-party packages

If you wish to install any of the software freely
available for UNIX-like systems you are strongly
advised to first check the NetBSD package system,
pkgsrc. pkgsrc automatically handles any changes nec-
essary to make the software run on NetBSD. This
includes the retrieval and installation of any other
packages the software may depend upon.

++oo More information on the package system is available
at
hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//ssooffttwwaarree//ppaacckkaaggeess..hhttmmll

++oo A list of available packages suitable for browsing
is at
hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ccuurrrreenntt//ppkkggssrrcc//RREEAADDMMEE..hhttmmll

++oo Precompiled binaries can be found at
hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ppaacckkaaggeess//NNeettBBSSDD//
usually in the _v_a_x_/_1_0_._1_/_A_l_l subdir. If you
installed pkgin(1) in the ssyyssiinnsstt post-installation
configuration menu, you can use it to automatically
install binary packages over the network. Assuming
that _/_u_s_r_/_p_k_g_/_e_t_c_/_p_k_g_i_n_/_r_e_p_o_s_i_t_o_r_i_e_s_._c_o_n_f is cor-
rectly configured, you can install them with the
following commands:

## ppkkggiinn iinnssttaallll ttccsshh bbaasshh ppeerrll aappaacchhee xxffccee44 ffiirreeffooxx
...

The above command will install the Tenex-csh and
Bourne Again shells, the Perl programming language,
Apache web server, Xfce desktop environment and the
Firefox web browser as well as all the packages
they depend on.

If it was not automatically installed, pkgin(1) can
be installed on a fresh NetBSD system with
pkg_add(1):

eexxppoorrtt PPKKGG__PPAATTHH==hhttttppss::////ccddnn..nneettbbssdd..oorrgg//ppuubb//ppkkggssrrcc//ppaacckkaaggeess//NNeettBBSSDD//$$((uunnaammee --pp))//$$((uunnaammee --rr | ccuutt --dd__ --ff11))//AAllll
ppkkgg__aadddd ppkkggiinn

++oo If you wish to use the pkgsrc(7) framework for com-
piling packages and did not install it from the
sysinst(8) post-installation configuration menu,
you can obtain it by retrieving the file
hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ssttaabbllee//ppkkggssrrcc..ttaarr..ggzz.
It is typically extracted into _/_u_s_r_/_p_k_g_s_r_c (though
other locations work fine) with the commands:

# ccdd //uussrr
# ttaarr --zzxxppff ppkkggssrrcc..ttaarr..ggzz

After extracting, see the _d_o_c_/_p_k_g_s_r_c_._t_x_t file in
the extraction directory (e.g.,
_/_u_s_r_/_p_k_g_s_r_c_/_d_o_c_/_p_k_g_s_r_c_._t_x_t) for more information.

7. Misc

++oo Edit _/_e_t_c_/_m_a_i_l_/_a_l_i_a_s_e_s to forward root mail to the
right place. Don't forget to run newaliases(1)
afterwards.

++oo Edit _/_e_t_c_/_r_c_._l_o_c_a_l to run any local daemons you
use.

++oo Many of the _/_e_t_c files are documented in section 5
of the manual; so just invoking

# mmaann 55 _f_i_l_e_n_a_m_e

is likely to give you more information on these
files.

UUppggrraaddiinngg aa pprreevviioouussllyy--iinnssttaalllleedd NNeettBBSSDD SSyysstteemm
The easiest way to upgrade to NetBSD 10.1 is with binaries,
and that is the method documented here.

To do the upgrade, you must have one form of boot media
available. You must also have at least the bbaassee and kkeerrnn
binary distribution sets available. Finally, you must have
sufficient disk space available to install the new binaries.
Since files already installed on the system are overwritten
in place, you only need additional free space for files
which weren't previously installed or to account for growth
of the sets between releases.

Since upgrading involves replacing the kernel, boot blocks,
and most of the system binaries, it has the potential to
cause data loss. You are strongly advised to _b_a_c_k _u_p any
important data on the NetBSD partition or on another operat-
ing system's partition on your disk before beginning the
upgrade process.

The upgrade procedure is similar to an installation, but
without the hard disk partitioning.

Fetching the binary sets is done in the same manner as the
installation procedure; refer to the installation part of
the document for help. File systems are checked before
unpacking the sets.

After a new kernel has been copied to your hard disk, your
machine is a complete NetBSD 10.1 system. However, that
doesn't mean that you're finished with the upgrade process.
You will probably want to update the set of device nodes you
have in _/_d_e_v. If you've changed the contents of _/_d_e_v by
hand, you will need to be careful about this, but if not,
you can just cd into _/_d_e_v, and run the command:

# sshh MMAAKKEEDDEEVV aallll

ssyyssiinnsstt will attempt to merge the settings stored in your
_/_e_t_c directory with the new version of NetBSD using the
postinstall(8) utility. However, postinstall(8) is only
able to deal with changes that are easily automated. It is
recommended that you use the etcupdate(8) tool to merge any
remaining configuration changes.

CCoommppaattiibbiilliittyy IIssssuueess WWiitthh PPrreevviioouuss NNeettBBSSDD RReelleeaasseess
Users upgrading from previous versions of NetBSD may wish to
bear the following problems and compatibility issues in mind
when upgrading to NetBSD 10.1.

Note that ssyyssiinnsstt will automatically invoke

postinstall fix
and thus all issues that are fixed by ppoossttiinnssttaallll by default
will be handled.

In NetBSD 9 and earlier, filesystems listed in _/_e_t_c_/_f_s_t_a_b
would be mounted before non-legacy zzffss filesystems. Starting
from NetBSD 10 this order has been reversed.

If you have ever run a version of NetBSD -current between
April 18, 2020 and September 23, 2022 (the version numbers
used in the affected time range are between 9.99.56 and
9.99.106) your FFS file systems might have broken extended
attributes stored.

You should follow this _g_u_i_d_e_:
hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ffeeaattuurreess//UUFFSS22eeaa//
before booting the updated system multi-user for the first
time.

_N_o_t_e _t_h_a_t _y_o_u _d_o _n_o_t _n_e_e_d _t_o _d_o _a_n_y_t_h_i_n_g _s_p_e_c_i_a_l _i_f _y_o_u
_n_e_v_e_r _d_i_d _r_u_n _a_n_y _a_f_f_e_c_t_e_d _k_e_r_n_e_l_, especially if you have
never run NetBSD -current.

The display drivers used for modern GPUs and the whole sub-
system supporting it (DRM/KMS) have been updated to a newer
version. Unfortunately not all issues with this have been
resolved before the NetBSD 10.0 release. You can find a list
of issues in the _O_p_e_n _i_s_s_u_e_s _w_i_t_h _n_e_w _D_R_M_/_K_M_S_:
hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//rreelleenngg//nneettbbssdd--1100//
section of the release engineering wiki page.

A number of things have been removed from the NetBSD 10.1
release. See the ``Components removed from NetBSD'' section
near the beginning of this document for a list.

UUssiinngg oonnlliinnee NNeettBBSSDD ddooccuummeennttaattiioonn
Documentation is available if you installed the manual dis-
tribution set. Traditionally, the ``man pages'' (documenta-
tion) are denoted by `name(section)'. Some examples of this
are

++oo intro(1),
++oo man(1),
++oo apropos(1),
++oo passwd(1), and
++oo passwd(5).

The section numbers group the topics into several cate-
gories, but three are of primary interest: user commands are
in section 1, file formats are in section 5, and administra-
tive information is in section 8.

The _m_a_n command is used to view the documentation on a
topic, and is started by entering mmaann [_s_e_c_t_i_o_n] _t_o_p_i_c. 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 lowest num-
bered section name will be displayed. For instance, after
logging in, enter

# mmaann ppaasssswwdd

to read the documentation for passwd(1). To view the docu-
mentation for passwd(5), enter

# mmaann 55 ppaasssswwdd

instead.

If you are unsure of what man page you are looking for,
enter

# aapprrooppooss _s_u_b_j_e_c_t_-_w_o_r_d

where _s_u_b_j_e_c_t_-_w_o_r_d is your topic of interest; a list of pos-
sibly related man pages will be displayed.

AAddmmiinniissttrriivviiaa
If you've got something to say, do so! We'd like your
input. There are various mailing lists available via the
mailing list server at _m_a_j_o_r_d_o_m_o_@_N_e_t_B_S_D_._o_r_g. See
hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//mmaaiilliinngglliissttss//
for details.

There are various mailing lists set up to deal with comments
and questions about this release. Please send comments to:
_n_e_t_b_s_d_-_c_o_m_m_e_n_t_s_@_N_e_t_B_S_D_._o_r_g.

To report bugs, use the send-pr(1) command shipped with
NetBSD, and fill in as much information about the problem as
you can. Good bug reports include lots of details.

Bugs also can be submitted and queried with the web inter-
face at
hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ssuuppppoorrtt//sseenndd--pprr..hhttmmll

There are also port-specific mailing lists, to discuss
aspects of each port of NetBSD. Use majordomo to find their
addresses, or visit
hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//mmaaiilliinngglliissttss//

If you're interested in doing a serious amount of work on a
specific port, you probably should contact the `owner' of
that port (listed below).

If you'd like to help with NetBSD, and have an idea as to
how you could be useful, send us mail or subscribe to:
_n_e_t_b_s_d_-_u_s_e_r_s_@_N_e_t_B_S_D_._o_r_g.

As a favor, please avoid mailing huge documents or files to
these mailing lists. Instead, put the material you would
have sent up for FTP or WWW somewhere, then mail the appro-
priate list about it. If you'd rather not do that, mail the
list saying you'll send the data to those who want it.

TThhaannkkss ggoo ttoo
++oo The former members of UCB's Computer Systems Research
Group, including (but not limited to):

Keith Bostic
Ralph Campbell
Mike Karels
Marshall Kirk McKusick

for their work on BSD systems, support, and encourage-
ment.

++oo The Internet Systems Consortium, Inc. for hosting the
NetBSD FTP, CVS, AnonCVS, mail, mail archive, GNATS,
SUP, Rsync and WWW servers.

++oo The Internet Research Institute in Japan for hosting the
server which runs the CVSweb interface to the NetBSD
source tree.

++oo The Columbia University Computer Science Department for
hosting the build cluster.

++oo The many organizations that provide NetBSD mirror sites.

++oo Without CVS, this project would be impossible to manage,
so our hats go off to Brian Berliner, Jeff Polk, and the
various other people who've had a hand in making CVS a
useful tool.

++oo We list the individuals and organizations that have made
donations or loans of hardware and/or money, to support
NetBSD development, and deserve credit for it at
hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddoonnaattiioonnss//
(If you're not on that list and should be, tell us! We
probably were not able to get in touch with you, to ver-
ify that you wanted to be listed.)

++oo Finally, we thank all of the people who've put sweat and
tears into developing NetBSD since its inception in Jan-
uary, 1993. (Obviously, there are a lot more people who
deserve thanks here. If you're one of them, and would
like to be mentioned, tell us!)

LLeeggaall MMuummbboo--JJuummbboo
All product names mentioned herein are trademarks or regis-
tered trademarks of their respective owners.

The following notices are required to satisfy the license
terms of the software that we have mentioned in this docu-
ment:

NetBSD is a registered trademark of The NetBSD Foundation,
Inc.
This product includes software developed by the University
of California, Berkeley and its contributors.
This product includes software developed by the NetBSD Foun-
dation.
This product includes software developed by The NetBSD Foun-
dation, Inc. and its contributors.
This product includes software developed for the NetBSD
Project. See https://www.NetBSD.org/ for information about
NetBSD.
This product includes cryptographic software written by Eric
Young (eay@cryptsoft.com)
This product includes cryptographic software written by Eric
Young (eay@mincom.oz.au)
This product includes software designed by William Allen
Simpson.
This product includes software developed at Ludd, University
of Luleoa.
This product includes software developed at Ludd, University
of Luleoa, Sweden and its contributors.
This product includes software developed at the Information
Technology Division, US Naval Research Laboratory.
This product includes software developed by Aaron Brown and
Harvard University.
This product includes software developed by Adam Ciarcinski
for the NetBSD project.
This product includes software developed by Adam Glass.
This product includes software developed by Adam Glass and
Charles M. Hannum.
This product includes software developed by Alex Zepeda.
This product includes software developed by Alex Zepeda, and
Colin Wood for the NetBSD Project.
This product includes software developed by Allen Briggs.
This product includes software developed by Amancio Hasty
and Roger Hardiman
This product includes software developed by Ben Gray.
This product includes software developed by Berkeley Soft-
ware Design, Inc.
This product includes software developed by Bill Paul.
This product includes software developed by Bodo Moeller.
This product includes software developed by Boris Popov.
This product includes software developed by Brini.
This product includes software developed by Bruce M. Simp-
son.
This product includes software developed by Causality Lim-
ited.
This product includes software developed by Charles Hannum.
This product includes software developed by Charles M. Han-
num.
This product includes software developed by Charles M. Han-
num, by the University of Vermont and State Agricultural
College and Garrett A. Wollman, by William F. Jolitz, and
by the University of California, Berkeley, Lawrence Berkeley
Laboratory, and its contributors.
This product includes software developed by Christian E.
Hopps.
This product includes software developed by Christian E.
Hopps, Ezra Story, Kari Mettinen, Markus Wild, Lutz Vieweg
and Michael Teske.
This product includes software developed by Christopher G.
Demetriou.
This product includes software developed by Christopher G.
Demetriou for the NetBSD Project.
This product includes software developed by Chuck Silvers.
This product includes software developed by Cisco Systems,
Inc.
This product includes software developed by Colin Wood.
This product includes software developed by Colin Wood for
the NetBSD Project.
This product includes software developed by Computing Ser-
vices at Carnegie Mellon University (http://www.cmu.edu/com-
puting/).
This product includes software developed by Daan Vreeken.
This product includes software developed by Daishi Kato
This product includes software developed by Daniel Widenfalk
and Michael L. Hitch.
This product includes software developed by Daniel Widenfalk
for the NetBSD Project.
This product includes software developed by David Jones and
Gordon Ross
This product includes software developed by David Miller.
This product includes software developed by Dean Huxley.
This product includes software developed by Emmanuel Dreyfus
This product includes software developed by Eric S. Hvozda.
This product includes software developed by Eric S. Raymond
This product includes software developed by Eric Young
(eay@cryptsoft.com)
This product includes software developed by Eric Young
(eay@mincom.oz.au)
This product includes software developed by Ezra Story.
This product includes software developed by Ezra Story and
by Kari Mettinen.
This product includes software developed by Ezra Story, by
Kari Mettinen and by Bernd Ernesti.
This product includes software developed by Ezra Story, by
Kari Mettinen, and Michael Teske.
This product includes software developed by Ezra Story, by
Kari Mettinen, Michael Teske and by Bernd Ernesti.
This product includes software developed by Frank van der
Linden for the NetBSD Project.
This product includes software developed by Gardner
Buchanan.
This product includes software developed by Garrett D'Amore.
This product includes software developed by Gary Thomas.
This product includes software developed by Gordon Ross
This product includes software developed by Harvard Univer-
sity.
This product includes software developed by Harvard Univer-
sity and its contributors.
This product includes software developed by Hellmuth
Michaelis and Joerg Wunsch
This product includes software developed by Henrik Vester-
gaard Draboel.
This product includes software developed by Herb Peyerl.
This product includes software developed by Hidetoshi
Shimokawa.
This product includes software developed by Hubert Feyrer
for the NetBSD Project.
This product includes software developed by Ian W. Dall.
This product includes software developed by Intel Corpora-
tion and its contributors.
This product includes software developed by Internet Initia-
tive Japan Inc.
This product includes software developed by Internet
Research Institute, Inc.
This product includes software developed by James R. Maynard
III.
This product includes software developed by Jared D.
McNeill.
This product includes software developed by Jason L. Wright
This product includes software developed by Jason R. Thorpe
for And Communications, http://www.and.com/
This product includes software developed by Joachim Koenig-
Baltes.
This product includes software developed by Jochen Pohl for
The NetBSD Project.
This product includes software developed by Joerg Wunsch
This product includes software developed by John Birrell.
This product includes software developed by John P. Wit-
tkoski.
This product includes software developed by John Polstra.
This product includes software developed by Jonathan R.
Stone for the NetBSD Project.
This product includes software developed by Jonathan Stone.
This product includes software developed by Jonathan Stone
and Jason R. Thorpe for the NetBSD Project.
This product includes software developed by Jonathan Stone
for the NetBSD Project.
This product includes software developed by Julian High-
field.
This product includes software developed by K. Kobayashi
This product includes software developed by K. Kobayashi and
H. Shimokawa
This product includes software developed by Kazuhisa
Shimizu.
This product includes software developed by Kazuki Sakamoto.
This product includes software developed by Kenneth Stailey.
This product includes software developed by Kiyoshi Ikehara.
This product includes software developed by Klaus Burkert,by
Bernd Ernesti, by Michael van Elst, and by the University of
California, Berkeley and its contributors.
This product includes software developed by Kyma Systems.
This product includes software developed by Leo Weppelman
and Waldi Ravens.
This product includes software developed by Lloyd Parkes.
This product includes software developed by Lutz Vieweg.
This product includes software developed by Marc Horowitz.
This product includes software developed by Marcus Comstedt.
This product includes software developed by Mark Brinicombe.
This product includes software developed by Mark Brinicombe
for the NetBSD Project.
This product includes software developed by Mark Tinguely
and Jim Lowe
This product includes software developed by Markus Wild.
This product includes software developed by Marshall M. Mid-
den.
This product includes software developed by Masanobu Saitoh.
This product includes software developed by Masaru Oki.
This product includes software developed by Matt DeBergalis
This product includes software developed by Matthew Fre-
dette.
This product includes software developed by Michael Smith.
This product includes software developed by Microsoft
This product includes software developed by Mika Kortelainen
This product includes software developed by Mike Pritchard.
This product includes software developed by Mike Pritchard
and contributors.
This product includes software developed by Minoura Makoto.
This product includes software developed by MINOURA Makoto,
Takuya Harakawa.
This product includes software developed by Niels Provos.
This product includes software developed by Niklas Hal-
lqvist.
This product includes software developed by Niklas Hal-
lqvist, Brandon Creighton and Job de Haas.
This product includes software developed by Paolo Abeni.
This product includes software developed by Paul Kranenburg.
This product includes software developed by Paul Mackerras.
This product includes software developed by Paul Mackerras
<paulus@samba.org>.
This product includes software developed by Pedro Roque Mar-
ques <pedro_m@yahoo.com>
This product includes software developed by Per Fogelstrom.
This product includes software developed by Peter Galbavy.
This product includes software developed by Phase One, Inc.
This product includes software developed by Philip A. Nel-
son.
This product includes software developed by QUALCOMM Incor-
porated.
This product includes software developed by Ravikanth.
This product includes software developed by RiscBSD.
This product includes software developed by Roar Thronaes.
This product includes software developed by Rodney W.
Grimes.
This product includes software developed by Roger Hardiman
This product includes software developed by Rolf Grossmann.
This product includes software developed by Ross Harvey.
This product includes software developed by Ross Harvey for
the NetBSD Project.
This product includes software developed by Scott Bartram.
This product includes software developed by Scott Stevens.
This product includes software developed by Shingo WATANABE.
This product includes software developed by Softweyr LLC,
the University of California, Berkeley, and its contribu-
tors.
This product includes software developed by Stephan Thesing.
This product includes software developed by Steven M.
Bellovin
This product includes software developed by Takashi Hamada.
This product includes software developed by Takumi Nakamura.
This product includes software developed by Tatoku Ogaito
for the NetBSD Project.
This product includes software developed by Tommi Komulainen
<Tommi.Komulainen@iki.fi>.
This product includes software developed by TooLs GmbH.
This product includes software developed by Trimble Naviga-
tion, Ltd.
This product includes software developed by Waldi Ravens.
This product includes software developed by WIDE Project and
its contributors.
This product includes software developed by Winning Strate-
gies, Inc.
This product includes software developed by Yen Yen Lim and
North Dakota State University
This product includes software developed by Zembu Labs, Inc.
This product includes software developed by the Alice Group.
This product includes software developed by the Computer
Systems Engineering Group at Lawrence Berkeley Laboratory.
This product includes software developed by the Computer
Systems Laboratory at the University of Utah.
This product includes software developed by the Harvard Uni-
versity and its contributors.
This product includes software developed by the Kungliga
Tekniska Hoegskolan and its contributors.
This product includes software developed by the Network
Research Group at Lawrence Berkeley Laboratory.
This product includes software developed by the OpenSSL
Project for use in the OpenSSL Toolkit.
(http://www.OpenSSL.org/)
This product includes software developed by the PocketBSD
project and its contributors.
This product includes software developed by the RiscBSD ker-
nel team
This product includes software developed by the RiscBSD
team.
This product includes software developed by the SMCC Tech-
nology Development Group at Sun Microsystems, Inc.
This product includes software developed by the University
of California, Lawrence Berkeley Laboratories.
This product includes software developed by the University
of California, Lawrence Berkeley Laboratory.
This product includes software developed by the University
of California, Lawrence Berkeley Laboratory and its contrib-
utors.
This product includes software developed by the University
of Vermont and State Agricultural College and Garrett A.
Wollman.
This product includes software developed by the University
of Vermont and State Agricultural College and Garrett A.
Wollman, by William F. Jolitz, and by the University of
California, Berkeley, Lawrence Berkeley Laboratory, and its
contributors.
This product includes software developed by the Urbana-Cham-
paign Independent Media Center.
This product includes software developed for the FreeBSD
project
This product includes software developed for the NetBSD
Project by Allegro Networks, Inc., and Wasabi Systems, Inc.
This product includes software developed for the NetBSD
Project by Bernd Ernesti.
This product includes software developed for the NetBSD
Project by Christopher G. Demetriou.
This product includes software developed for the NetBSD
Project by Eiji Kawauchi.
This product includes software developed for the NetBSD
Project by Frank van der Linden
This product includes software developed for the NetBSD
Project by Genetec Corporation.
This product includes software developed for the NetBSD
Project by Jason R. Thorpe.
This product includes software developed for the NetBSD
Project by John M. Vinopal.
This product includes software developed for the NetBSD
Project by Jonathan Stone.
This product includes software developed for the NetBSD
Project by Kyma Systems LLC.
This product includes software developed for the NetBSD
Project by Matthias Drochner.
This product includes software developed for the NetBSD
Project by Perry E. Metzger.
This product includes software developed for the NetBSD
Project by Piermont Information Systems Inc.
This product includes software developed for the NetBSD
Project by Shigeyuki Fukushima.
This product includes software developed for the NetBSD
Project by SUNET, Swedish University Computer Network.
This product includes software developed for the NetBSD
Project by Wasabi Systems, Inc.
This product includes software developed or owned by Caldera
International, Inc.
This product includes software developed under OpenBSD by
Per Fogelstrom.
This product includes software developed under OpenBSD by
Per Fogelstrom Opsycon AB for RTMX Inc, North Carolina, USA.
This software was developed by Holger Veit and Brian Moore
for use with "386BSD" and similar operating systems. "Simi-
lar operating systems" includes mainly non-profit oriented
systems for research and education, including but not
restricted to "NetBSD", "FreeBSD", "Mach" (by CMU).
The Institute of Electrical and Electronics Engineers and
The Open Group, have given us permission to reprint portions
of their documentation.

In the following statement, the phrase ``this text'' refers
to portions of the system documentation.

Portions of this text are reprinted and reproduced in
electronic form in NetBSD, from IEEE Std 1003.1, 2004
Edition, Standard for Information Technology -- Portable
Operating System Interface (POSIX), The Open Group Base
Specifications Issue 6, Copyright (C) 2001-2004 by the
Institute of Electrical and Electronics Engineers, Inc and
The Open Group. In the event of any discrepancy between
these versions and the original IEEE and The Open Group
Standard, the original IEEE and The Open Group Standard is
the referee document.

The original Standard can be obtained online at
http://www.opengroup.org/unix/online.html.

This notice shall appear on any product containing this
material.

In the following statement, "This software" refers to the
parallel port driver:
This software is a component of "386BSD" developed by
William F. Jolitz, TeleMuse.

CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN
ITS CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABIL-
ITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING
FROM THE USE OF THIS SOFTWARE.

Carnegie Mellon requests users of this software to
return to
Software Distribution Coordinator or Software.Dis-
tribution@CS.CMU.EDU
School of Computer Science
Carnegie Mellon University
Pittsburgh PA 15213-3890

any improvements or extensions that they make and
grant Carnegie the rights to redistribute these
changes.

Author: Chris G. Demetriou

Permission to use, copy, modify and distribute this
software and its documentation is hereby granted, pro-
vided that both the copyright notice and this permis-
sion notice appear in all copies of the software, de-
rivative works or modified versions, and any portions
thereof, and that both notices appear in supporting
documentation.
CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN
ITS "AS IS" CONDITION. CARNEGIE MELLON DISCLAIMS ANY
LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER
RESULTING FROM THE USE OF THIS SOFTWARE.

any improvements or extensions that they make and
grant Carnegie the rights to redistribute these
changes.

Permission to use, copy, modify, and distribute this
software and its documentation for any purpose and
without fee is hereby granted, provided that the above
copyright notice appear in all copies. Stanford Uni-
versity makes no representations about the suitability
of this software for any purpose. It is provided "as
is" without express or implied warranty.

TThhee EEnndd
NetBSD/vax 10.1 Dec 17, 2024 NetBSD/vax 10.1