About this Document............................................2
What is NetBSD?................................................2
Changes Between The NetBSD 5.2.2 and 5.2.3 Releases............2
Security Advisory Fixes.....................................3
Kernel......................................................3
Miscellaneous...............................................3
Features to be removed in a later release......................3
The NetBSD Foundation..........................................4
Sources of NetBSD..............................................4
NetBSD 5.2.3 Release Contents..................................4
NetBSD/sun2 subdirectory structure..........................5
Binary distribution sets....................................6
NetBSD/sun2 System Requirements and Supported Devices..........7
Supported hardware..........................................7
Getting the NetBSD System on to Useful Media...................7
Creating boot/install tapes.................................8
Boot/Install from NFS server................................8
Install/Upgrade from CD-ROM.................................9
Install/Upgrade via FTP.....................................9
Preparing your System for NetBSD installation..................9
Installing the NetBSD System...................................9
Installing from tape.......................................10
Installing from NFS........................................10
Installing from SunOS......................................11
Booting the Miniroot.......................................12
Miniroot install program...................................12
Post installation steps.......................................13
Upgrading a previously-installed NetBSD System................15
Compatibility Issues With Previous NetBSD Releases............16
Issues when running older binaries on NetBSD 5.2.3.........17
Issues affecting an upgrade from NetBSD 3.x releases.......17
Issues affecting an upgrade from NetBSD 4.x releases.......18
Using online NetBSD documentation.............................19
Administrivia.................................................19
Thanks go to..................................................20
We are........................................................21
Legal Mumbo-Jumbo.............................................27
The End.......................................................33
This document describes the installation procedure for
NetBSD
5.2.3 on the
sun2
platform.
It is available in four different formats titled
INSTALL.ext,
where
.ext
is one of
.ps, .html, .more,
or .txt:
.ps.html.moremore(1)
and
less(1)
pager utility programs.
This is the format in which the on-line
man
pages are generally presented.
.txtYou are reading the HTML version.
The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the University of California, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on 57 different system architectures (ports) across 15 distinct CPU families, and is being ported to more. The NetBSD 5.2.3 release contains complete binary releases for many different system architectures. (A few ports are not fully supported at this time and are thus not part of the binary distribution. Please see the NetBSD web site at http://www.NetBSD.org/ for information on them.)
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several 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 community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.
NetBSD 5.2.3 is the third critical/security update of the NetBSD 5.2 release branch. It represents a selected subset of fixes deemed critical for security or stability reasons.
The complete list of changes can be found in the CHANGES-5.2.3: http://ftp.NetBSD.org/pub/NetBSD/NetBSD-5.2.3/CHANGES-5.2.3 file in the top level directory of the NetBSD 5.2.3 release tree. An abbreviated list is as follows:
modctl(2)
system call
setsockopt(2)
system call
ftp(1)
can be made to execute arbitrary commands
mount(2)
system call
Advisories prior to NetBSD-SA2014-005 do not affect NetBSD 5.2.3: http://www.NetBSD.org/support/security/patches-5.2.3.html.
NetBSD-<version>-<machine>.iso
and placed under the
images
directory instead of
iso.
mount(8))
will be removed in the next major release.
NetBSD
5.2.3
includes a preview of WAPBL
(Write Ahead Physical Block Logging),
which will replace soft dependencies in the next major release.
See
wapbl(4)
and
http://mail-index.netbsd.org/netbsd-announce/2008/12/14/msg000051.html
for details.
It should be considered as deprecated. Users are expected to not rely on it any more beyond this major release.
Further, at least version 3.1 of Xen will be required to run NetBSD as Dom0 or DomU.
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 trademark of the word
``NetBSD''.
It supports the design, development, and adoption of
NetBSD
worldwide.
More information on the
NetBSD
Foundation, its composition, aims, and work can be found at:
http://www.NetBSD.org/foundation/
Refer to
http://www.NetBSD.org/mirrors/
The root directory of the NetBSD 5.2.3 release is organized as follows:
.../NetBSD-5.2.3/
CHANGESCHANGES-5.0CHANGES-5.1CHANGES-5.2CHANGES-5.2.1CHANGES-5.2.2CHANGES-5.2.3CHANGES.prevLAST_MINUTEREADME.filessource/In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD 5.2.3 has a binary distribution.
The source distribution sets can be found in subdirectories of the
source
subdirectory of the distribution tree.
They contain the complete sources to the system.
The source distribution sets are as follows:
config(1)
utility.
All the above source sets are located in the
source/sets
subdirectory of the distribution tree.
The source sets are distributed as compressed tar files.
Except for the
pkgsrc
set, which is traditionally unpacked into
/usr/pkgsrc,
all sets may be unpacked into
/usr/src
with the command:
# cd / ; tar -zxpf set_name.tgz
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
MD5SHA512The 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.
sun2
subdirectory of the distribution:
.../NetBSD-5.2.3/sun2/.
It contains the following files and directories:
INSTALL.htmlINSTALL.psINSTALL.txtINSTALL.more.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/kernel/netbsd-GENERIC.gzsets/installation/miniroot/misc/netboot/tapeimage/sun2/binary/sets
subdirectory
of the
NetBSD
5.2.3
distribution tree, and are as follows:
/usr/include)
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.
/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.
GENERIC
kernel, named
/netbsd.
You
must
install this distribution set.
/usr/share.
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 compatibility. NetBSD/sun2 currently does not ship with an X server or X clients.
The sun2 binary distribution sets are distributed as gzipped tar files
named with the extension
.tgz,
e.g.
base.tgz.
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
below the current directory.
Therefore, if you want to extract the binaries into your system, i.e.
replace the system binaries with them, you have to run the
tar -xzpf
command from the root directory (
/
) of your system.
There is a collection of Sun2 kernels in the
sun2/binary/kernel
subdirectory of the
NetBSD
5.2.3 distribution.
The one named
netbsd-RAMDISK.gz
contain a root file system image and should only be used for the
initial installation.
The others are included for convenience.
(Most people will want to use
netbsd-GENERIC.gz
or
netbsd-FOURMEG.gz
as appropriate.)
Please note that these kernels are simply gzipped and are not tar archives.
NetBSD/sun2 5.2.3 runs on Multibus Sun2 machines, including:
| 2/120 | 2/170 | 2/100U |
The minimal configuration requires 4 MB of RAM and about 130 MB of disk
space.
To install the entire system requires much more disk space.
To compile the system, more RAM is recommended.
Good performance requires 7 MB of RAM.
A good rule of thumb is to have a swap partition twice the size of the
amount of RAM in your machine.
You will probably want to compile your own kernel, as
GENERIC
is large and bulky to accommodate all people.
Note that the sun2 installation procedure uses a miniroot image which is placed into the swap area of the disk. The swap partition must be at least as large as the miniroot image (12 MB).
If it's not on this list, there is no support for it in this release.
Installation is supported from several media types, including:
The procedure for transferring the distribution sets onto installation media depends on the type of media. Instructions for each type of media are given below.
In order to create installation media, you will need all the files in the directory
.../NetBSD-5.2.3/sun2/
The boot tape is created as follows:
# cd .../NetBSD-5.2.3/sun2/installation/tapeimage
# sh MakeBootTape /dev/nrst0
The install tape is created as follows:
# cd .../NetBSD-5.2.3/sun2/installation/tapeimage
# sh MakeInstallTape /dev/nrst0
If the tapes do not work as expected, you may need to explicitly
set the EOF mark at the end of each tape segment.
It may also be necessary to use the
conv=osync
argument to
dd(1).
Note that
this argument is incompatible with the
bs=
argument.
Consult the tape-related manual pages on the system where the tapes are
created for more details.
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 (i.e.
add_client(8)
on
SunOS).
When instructed to boot over the network, your sun2 expects to be
able to download first and second stage bootstrap programs via
ND,
the Network Disk protocol.
The
ndbootd(8)
program will attempt to serve a second-stage bootstrap file using
a name derived from the machine's recently acquired IP
address and an extension which corresponds to the
machine architecture.
(It may be handy to have a hexadecimal
calculator for this next step.)
The filename prefix is created by converting the machine's assigned
IP address into hexadecimal, most-significant octet first,
using uppercase characters for the non-decimal (A-F) digits.
The filename suffix used by all sun2 machines is
SUN2.
For example, a sun2 which has been assigned IP address 130.115.144.11
will be served a second-stage bootstrap file named
8273900B.SUN2.
Normally, this file
is a symbolic link to the
NetBSD/sun2
netboot
program, which should
be located in a place where the
ndbootd(8)
daemon can find it.
The
netboot
program may be found in the
installation/netboot
directory of this distribution.
The netboot program will query a bootparamd server to find the
NFS server address and path name for its root, and then load a
kernel from that location.
The server should have a copy of the
netbsd-RAMDISK
kernel in the root area for your client, hard-linked
under the names
netbsd
and
vmunix
(no other files are needed in the client root) and
/etc/bootparams
on the server
should have an entry for your client and its root directory.
The client will need access to the miniroot image, which can be
provided using NFS or remote shell.
If you will be installing
NetBSD
on several clients, it may be useful
to know that you can use a single NFS root for all the clients as long
as they only use the
netbsd-RAMDISK
kernel.
There will be no conflict
between clients because the RAM-disk kernel will not use the NFS root.
No swap file is needed; the RAM-disk kernel does not use that either.
installation/tapeimage
and
binary/kernel
(which you get via FTP).
Once you have booted
netbsd-RAMDISK
(the RAM-disk kernel)
and loaded the miniroot, you can load any of the distribution sets
over the net using FTP.
The
install
program in the miniroot
automates the work required to configure the network interface and
transfer the files.
The preparations for this installation/upgrade method are easy; all
you make sure that there's some FTP site from which you can retrieve
the
NetBSD
distribution when you're about to install or upgrade.
You 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.
Sun2 machines usually need little or no preparation before installing NetBSD, other than the usual, well advised precaution of backing up all data on any attached storage devices.
You will need to know the SCSI target ID of the drive on which you will install NetBSD.
sd2,
target 2 is
sd4,
etc.
Installing NetBSD is a relatively complex process, but if you have this document in hand it should not be too difficult.
There are several ways to install NetBSD onto your disk. If your machine has a tape drive the easiest way is Installing from tape (details below). If your machine is on a network with a suitable NFS server, then Installing from NFS is the next best method. Otherwise, if you have another Sun machine running SunOS you can initialize the disk on that machine and then move the disk. (Installing from SunOS is not recommended.)
>b st()
>b st(0,8,0)
The first example will use the tape on SCSI target 4, where the
second will use SCSI target 5.
The
>
is the monitor prompt.
After the tape loads, you should see many lines of configuration messages, and then the following `welcome' screen:
Welcome to the NetBSD/sun2 RAMDISK root!
This environment is designed to do only three things:
1: Partition your disk (use the command: edlabel /dev/rsd0c)
2: Copy a miniroot image into the swap partition (/dev/rsd0b)
3: Reboot (using the swap partition, i.e. /dev/sd?b).
Note that the sun2 firmware cannot boot from a partition located
more than 1 GB from the beginning of the disk, so the swap partition
should be completely below the 1 GB boundary.
Copying the miniroot can be done several ways, allowing
the source of the miniroot image to be on any of these:
boot tape, NFS server, TFTP server, rsh server
The easiest is loading from tape, which is done as follows:
mt -f /dev/nrst0 rewind
mt -f /dev/nrst0 fsf 2
dd if=/dev/nrst0 of=/dev/rsd0b bs=32k conv=sync
(For help with other methods, please see the install notes.)
To reboot using the swap partition, first use "halt",
then at the PROM monitor prompt use a command like:
b sd(,,1) -s
To view this message again, type: cat /.welcome
Copy the miniroot as described in the welcome message, and reboot from that just installed miniroot. See the section entitled Booting the miniroot for details.
First, at the Sun PROM monitor prompt, enter a boot command using the network interface as the boot device. If your machine has Intel Ethernet, this is ie, and if it has 3Com Ethernet, this is ec. Examples:
>b ie() -s
>b ec() -s
After the boot program loads the RAMDISK kernel, you should see the welcome screen as shown in the Installing from tape section above. You must configure the network interface before you can use any network resources. For example the command:
ssh> ifconfig ie0 inet 192.233.20.198 up
will bring up the network interface with that address. The next step is to copy the miniroot from your server. This can be done using either NFS or remote shell. (In the examples that follow, the server has IP address 192.233.20.195.) You may then need to add a default route if the server is on a different subnet:
ssh> route add default 192.233.20.255 1
You can look at the route table using:
ssh> route show
Now mount the NFS file system containing the miniroot image:
ssh> mount -o rdonly,-r=1024 192.233.20.195:/server/path /mnt
The procedure is simpler and much faster if you have space for an expanded (not compressed) copy of the miniroot image. In that case:
ssh> dd if=/mnt/miniroot.fs of=/dev/rsd0b bs=8k
Otherwise, you will need to use
zcat
to expand the miniroot image while copying.
This is tricky because the
ssh
program
(small shell) does not handle
sh(1)
pipeline syntax.
Instead,
you first run the reader in the background with its input set
to
/dev/pipe
and then run the other program in the foreground with its output to
/dev/pipe.
The result looks like this:
ssh> run -bg dd if=/dev/pipe of=/dev/rsd0b obs=8k
ssh> run -o /dev/pipe zcat /mnt/install/miniroot.fs.gz
To load the miniroot using rsh to the server, you would use a pair of commands similar to the above. Here is another example:
ssh> run -b dd if=/dev/pipe of=/dev/rsd0b obs=8k
ssh> run -o /dev/pipe rsh 192.233.20.195 zcat miniroot.fs.gz
Note that decompression on a sun2 is extremely slow, be prepared to wait. For this reason, expanding the miniroot image on the NFS server is highly recommended.
Once the miniroot has been copied using one of the above methods, you reboot from that just installed miniroot. See the section entitled Booting the miniroot for details.
First, boot SunOS and place the miniroot file onto the hard drive. If you do not have gzip for SunOS, you will need to decompress the image elsewhere before you can use it.
Next, bring SunOS down to single user mode to insure that nothing will be using the swap space on your drive. To be extra safe, reboot the machine into single-user mode rather than using the shutdown command.
Now copy the miniroot image onto your swap device (here
/dev/rsd0b)
with the command
gzip -dc miniroot.fs.gz | dd of=/dev/rsd0b obs=32k
or if you have already decompressed the miniroot
dd if=miniroot.fs of=/dev/rsd0b obs=32k
Finally, reboot the machine and instruct the PROM to boot from the swap device as described in the next section.
halt
command.
If the miniroot was installed on partition
`b'
of the disk with
SCSI target ID=0 then the PROM boot command would be:
>b sd(0,0,1) -s
With SCSI target ID=2, the PROM is:
>b sd(0,10,1) -s
The numbers in parentheses above are:
The miniroot's install program will:
foo
instead of
foo.bar.org.
If, during the process of configuring
the network interfaces, you make a mistake, you will
be able to re-configure that interface by simply selecting
it for configuration again.
/etc/fstab.
/).
/dev.
/).
First-time installation on a system through a method other than the
installation program is possible, but strongly discouraged.
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.
/etc/rc.conf
If you or the installation software haven't done any configuration of
/etc/rc.conf
(sysinst
usually 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
/bin/sh
prompt.
If you are asked for a terminal type, respond with
vt220
(or whatever is appropriate for your terminal type)
and press
RETURN.
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
# stty erase '^h'
# stty erase '^?'
At this point, you need to configure at least
one file in the
/etc
directory.
You will need to mount your root file system read/write with:
# /sbin/mount -u -w /
Change to the
/etc
directory and take a look at the
/etc/rc.conf
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
proceed.
Default values for the various programs can be found in
/etc/defaults/rc.conf,
where some in-line documentation may be found.
More complete documentation can be found in
rc.conf(5).
When you have finished editing
/etc/rc.conf,
type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that may need to be set in
/etc/rc.conf
for a networked environment are
hostname
and possibly
defaultroute.
You may also need to add an
ifconfig_int
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
myname.my.dom
in
/etc/hosts:
ifconfig_le0="inet myname.my.dom netmask 255.255.255.0"
To enable proper hostname resolution, you will also want to add an
/etc/resolv.conf
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 network and naming service,
DHCP can be used by setting
dhclient=YES
in
/etc/rc.conf.
Other files in
/etc
that may require modification or setting up include
/etc/mailer.conf,
/etc/nsswitch.conf,
and
/etc/wscons.conf.
After reboot, you can log in as
root
at the login prompt.
Unless you've set a password in
sysinst,
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.
Use the
useradd(8)
command to add accounts to your system.
Do not
edit
/etc/passwd
directly! See
vipw(8)
and
pwd_mkdb(8)
if you want to edit the password database.
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 necessary to make the software run on NetBSD. This includes the retrieval and installation of any other packages on which the software may depend.
sun2/5.2.3/All
subdir.
You can install them with the following commands under
sh(1):
# PKG_PATH=ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/sun2/5.2.3/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v bash # pkg_add -v perl # pkg_add -v apache # pkg_add -v kde # pkg_add -v firefox ...
If you are using
csh(1)
then replace the first two lines with the following:
# setenv PKG_PATH ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/sun2/5.2.3/All
/pub/pkgsrc
directory.
If you would like to use such mirrors, you could also try the
/pub/NetBSD/packages/current-packages/NetBSD/sun2/5.2.3/All
directory, which may have the same contents.
The above commands will install the Tenex-csh and Bourne Again shells, the Perl programming language, Apache web server, KDE desktop environment and the Firefox web browser as well as all the packages they depend on.
pkg_add(1)
command will complain about a version mismatch of packages with a message
like the following:
Warning: package `foo' was built for a different version of the OS:
NetBSD/i386 M.N (pkg) vs. NetBSD/i386 5.2.3 (this host),
/usr/pkgsrc
(though other locations work fine) with the commands:
# cd /usr
# tar -zxpf pkgsrc.tar.gz
After extracting, see the
doc/pkgsrc.txt
file in the extraction directory (e.g.,
/usr/pkgsrc/doc/pkgsrc.txt)
for more information.
/etc/mail/aliases
to forward root mail to the right place.
Don't forget to run
newaliases(1)
afterwards.
/etc/postfix/main.cf
file will almost definitely need to be adjusted.
If you prefer a different MTA, then install it using
pkgsrc or by hand and adjust
/etc/mailer.conf.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
# man 5 filename
is likely to give you more information on these files.
It is possible to easily upgrade your existing NetBSD/sun2 system using the upgrade program in the miniroot. If you wish to upgrade your system by this method, simply select the upgrade option once the miniroot has booted. The upgrade program with then guide you through the procedure. The upgrade program will:
/dev.
/).
Using the miniroot's upgrade program is the preferred method of upgrading your system.
However, it is possible to upgrade your system manually. To do this, follow the following procedure:
/).
# /sbin/fsck -pf
# /sbin/mount -a -t nonfs
/usr
or
/usr/share
on an NFS server, you
will want to mount those file systems as well.
To do this, you will need to enable the network:
# sh /etc/rc.d/network start
/ and extract the)
base
binary set:
# cd /
# pax -zrvpe -f Ar /path/to/base.tgz
/dev/rsd0a)
# cd /usr/mdec
# cp -p ./ufsboot /mnt/ufsboot
#sync ; sleep 1 ; sync
# /usr/sbin/installboot -v /dev/rsd0a bootxx /ufsboot
sync
# cd /
# pax -zrvpe -f path_to_set
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 5.2.3.
If your port uses X.Org and you see messages from the X server indicating that no devices were found, you may need to run X -configure and update your existing xorg.conf to use the BusID line from the newly-generated config file.
Dual-head support for PC systems has become broken for many configurations with the update to xorg-server 1.6.x, which has removed the userland PCI configuration mechanism, and needs to rely upon the OS. We hope to correct this for future releases. Workaround: The only workaround is non-trivial and requires programming several PCI BAR registers as they previously were in NetBSD 5.0.
If you are updating to
NetBSD
5.2.3
without the aid of sysinst or postinstall and your port uses X.Org, be sure
to remove
/usr/X11R7/lib/X11/xkb/symbols/pc
before extracting the xbase set.
In the version of X.Org shipped with 5.0, this was a directory, but in more
recent X.Org versions it is a file.
pkg_install now depends on the pkgdb cache for automatic conflict detection. It is recommended to rebuild the cache with
# pkg_admin rebuild
audit-packages.conf(5)
has been superseded by
pkg_install.conf(5).
The default configuration is the same.
Support for
pkg_view(1)
has been retired.
The functionality of
audit-packages(1)
and
download-vulnerability-list(1)
has moved into
pkg_admin(1).
However, wrapper scripts that handle the common use cases are provided.
The pthread libraries from previous versions of
NetBSD
require that the
sysctl(3)
node
kern.no_sa_support
be set to
0.
This affects the following environments:
The 5.x kernel defaults to
0
for
kern.no_sa_support,
which covers the first case.
However, please note that a full installation of 5.x
(either from scratch or through an upgrade)
will set
kern.no_sa_support
to 1 during the boot process.
This means that for the last two cases, you will have to manually set
kern.no_sa_support
to
0,
using either the
sysctl(8)
command or through
sysctl.conf(5).
Note that sysinst will automatically invoke
postinstall fix
The following issues can generally be resolved by running postinstall with the etc set:
postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix
Issues fixed by postinstall:
/etc
need upgrading.
These include:
/etc/defaults/*
/etc/mtree/*
/etc/daily
/etc/weekly
/etc/monthly
/etc/security
/etc/rc.subr
/etc/rc
/etc/rc.shutdown
/etc/rc.d/*
/etc/envsys.conf
The following issues need to be resolved manually:
postinstall -s /path/to/etc.tgz fix mailerconf
/etc/mailer.conf
file to use Postfix as the MTA. When using
sysinst
to upgrade the system, it will ask if you want this to be done.
Note that if you have a customized Sendmail setup, you need to set up Postfix in an equivalent way; there is no tool for automatic conversion of Sendmail configuration to a Postfix one.
Postfix will be started automatically when the system boots.
You may see messages like "$sendmail is not set properly" at boot.
You can suppress them by removing
/etc/rc.d/sendmail
and
/etc/rc.d/smmsp.
Those files and other parts of sendmail configuration like files under
/usr/share/sendmail
are not removed by default
while upgrading for those who want to continue using sendmail from
outside the base system.
If you want to delete them,
postinstall
can be used:
postinstall -s /path/to/etc.tgz fix sendmail
The following issues can generally be resolved by running postinstall with the etc set:
postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix
Issues fixed by postinstall:
/etc
need upgrading.
These include:
/etc/defaults/*
/etc/mtree/*
/etc/daily
/etc/weekly
/etc/monthly
/etc/security
/etc/rc.subr
/etc/rc
/etc/rc.shutdown
/etc/rc.d/*
/etc/envsys.conf
The following issues need to be resolved manually:
mount(8)
command now requires the
nosuid
and
nodev
options to be explicitly specified.
Previously, these options were automatically enforced even if they
were not explicitly specified.
Documentation is available if you installed the manual
distribution set.
Traditionally, the
``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 lowest 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.
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 majordomo@NetBSD.org. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. See http://www.NetBSD.org/mailinglists/ for a web interface.
There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.org.
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 interface at http://www.NetBSD.org/support/send-pr.html
There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit http://www.NetBSD.org/mailinglists/
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 this effort, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-users@NetBSD.org.
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 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.
Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick
for their work on BSD systems, support, and encouragement.
(in alphabetical order)
All product names mentioned herein are trademarks or registered trademarks of their respective owners.
The following notices are required to satisfy the license terms of the software that we have mentioned in this document:
NetBSD is a registered trademark of The NetBSD Foundation, Inc.
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