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......................4
The NetBSD Foundation..........................................4
Sources of NetBSD..............................................4
NetBSD 5.2.3 Release Contents..................................4
NetBSD/hp300 subdirectory structure.........................5
Binary distribution sets....................................6
NetBSD/hp300 System Requirements and Supported Devices.........7
Supported hardware..........................................7
Unsupported hardware........................................9
Getting the NetBSD System on to Useful Media..................10
Preparing your System for NetBSD installation.................12
Formatting your hard drives................................13
Designing your disk's partition table......................13
Installing the bootstrap program locally...................14
Installing the miniroot file system locally................15
Configuring the netboot server.............................15
Put Series 400 systems in HP-UX Compatible Boot Mode.......19
Searching for a bootable system............................20
Selecting ethernet port on Series 400......................21
Running SYS_INST...........................................21
Choosing a kernel location.................................22
Installing the NetBSD System..................................23
Post installation steps.......................................24
Upgrading a previously-installed NetBSD System................27
Upgrading using the miniroot...............................27
Manual upgrade.............................................28
Compatibility Issues With Previous NetBSD Releases............29
Issues when running older binaries on NetBSD 5.2.3.........29
Issues affecting an upgrade from NetBSD 3.x releases.......30
Issues affecting an upgrade from NetBSD 4.x releases.......30
Using online NetBSD documentation.............................31
Administrivia.................................................32
Thanks go to..................................................32
We are........................................................33
Legal Mumbo-Jumbo.............................................39
The End.......................................................45
This document describes the installation procedure for
NetBSD
5.2.3 on the
hp300
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.
hp300
subdirectory of the distribution:
.../NetBSD-5.2.3/hp300/.
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.gznetbsd-RAMDISK.gznetbsd-RAMDISK.symbols.gznetbsd-RAMDISK.gz.
sets/installation/miniroot/misc/HP-IB.geometrySYS_INST.gzSYS_UBOOT.gzhp300/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. These sources are based on XFree86 4.5.0. Binary sets for the X Window System are distributed with NetBSD. The sets are:
The hp300 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.
NetBSD/hp300 5.2.3 will run on most HP 9000/300- and 400-series machines. The smallest amount of RAM that has been tested is 4 MB. If you wish to run X, more RAM is recommended.
Each serial interface has its own quirks, and some of them use non-standard pins. The FAQ describes how to configure and connect serial consoles to hp300 systems. http://www.NetBSD.org/ports/hp300/faq.html#serialconsole
When you try booting from a system with a framebuffer that is not supported by NetBSD/hp300, the screen will turn black, and it will try using the serial port for the console.
You should wait to decide where to put the NetBSD distribution sets until you have figured out how you are going to boot your system. Refer back to this section after you have done so.
Note that if you are installing or upgrading from writable media, it can be write-protected if you wish. These systems mount a root image from inside the kernel, and will not need to write to the media. If you booted from a floppy, the floppy disk may be removed from the drive after the system has booted.
Installation is supported from several media types, including:
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.
binary/sets
and
hp300/binary/sets.
Proceed to the instructions on installation.
split(1)
command, running e.g.
split -b 235k base.tgz base.
to split the
base.tgz
file from
hp300/binary/sets
into files named
base.aa,
base.ab,
and so on.
Repeat this for all
set_name.tgz
files, splitting them into
set_name.xx
files.
Count the number of
set_name.xx
files that make up the
distribution sets you want to install or upgrade.
You will need one sixth that number of 1.44 MB floppies.
Format all of the floppies with
MS-DOS.
Do
not
make any of them bootable
MS-DOS
floppies, i.e. don't use
format /s
to format them.
(If the floppies are bootable, then the
MS-DOS
system files that make them bootable will take up some space, and you
won't be able to fit the distribution set parts on the disks.)
If you're using floppies that are formatted for
MS-DOS
by their manufacturers, they probably aren't bootable, and you can use
them out of the box.
Place all of the
set_name.xx
files on the
MS-DOS
disks.
Once you have the files on MS-DOS disks, 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 upgrading.
204.152.190.15
and the IPv6 address is
2001:4f8:3:7:230:48ff:fec6:9aaa:21
(as of May, 2010).
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 upgrading.
/etc/exports
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 information mentioned above, 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 upgrading.
If you're making the tape on a UNIX-like system, the easiest way to do so is probably something like:
# tar -cf tape_device dist_directories
where
tape_device
is the name of the tape device that
describes the tape drive you're using; possibly
/dev/rst0,
or something similar, but it will vary from system to system.
(If you can't figure it out, ask your system administrator.)
In the above example,
dist_directories
are the
distribution sets' directories, for the distribution sets you
wish to place on the tape.
For instance, to put the
kern-GENERIC, base, and etc
distributions on tape (in
order to do the absolute minimum installation to a new disk),
you would do the following:
# cd .../NetBSD-5.2.3
# cd hp300/binary
# tar -cf tape_device kern-GENERIC base etc
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 installation, go directly to the section on upgrading.
There are two installation tools available. The traditional miniroot installer is script-based and may be netbooted or may be dumped to a disk and run locally. The ramdisk kernel with the sysinst installation utility is more flexible, but can only be netbooted and has not been extensively tested.
There are several possible installation configurations described in this document. Other configurations are possible, but less common. If you are unable to install based on the information in this document, post a message to port-hp300@NetBSD.org asking for help. The configurations described in this document are as follows:
SYS_UBOOT
from a
NetBSD
server running
rbootd(8),
or other server platforms (Linux, FreeBSD, SunOS, Solaris, HP-UX etc.) with
YAMAMORI Takenori's
sun-rbootd
package and then runs the miniroot installation tools or a purely diskless
installation from a server on the same subnet (you must have root access).
For more information, refer to the NetBSD Diskless
HOW-TO at
http://www.NetBSD.org/docs/network/netboot/
and
http://www.NetBSD.org/docs/network/netboot/rbootd/
SYS_UBOOT
from a local disk, tape, or floppy
and then runs the miniroot installation tools or a purely diskless
installation from a server as described above.
You will need
HP-UX
on your hp300 if it does not have a SCSI interface or a floppy drive.
SYS_INST
from a local disk.
You partition the drive
and then run the miniroot installation tools from that drive.
You will need
HP-UX
on your hp300 if it does not have a SCSI interface.
If you have access to a NetBSD/hp300 system, it is much easier to simply upgrade than to install from scratch. Skip down to the section on Upgrading a previously-installed NetBSD System
mediainit(1)
command.
You may need to first create the device nodes for your disk, as
HP-UX
was never very good about populating
/dev/rdsk
properly.
# mknod /dev/dsk/IDs0 b 0 0xSCID00
# mknod /dev/rdsk/IDs0 c 4 0xSCID00
# mediainit -v /dev/rdsk/IDs0
00
and
07,
but possibly up to
1F
(31 decimal) .
07
for slow (i.e. built-in) HP-IB or
0E
(14 decimal) for SCSI or fast HP-IB.
SYS_INST.
It's best to calculate it ahead of time.
If you are installing to an HP-IB disk,
you will need information about your disk's geometry, based on 512-byte sectors.
The file
installation/misc/HP-IB.geometry
in the distribution has geometry information for
several HP-IB disks, but may be incomplete.
Geometry may be calculated from an HP-UX
/etc/disktab
entry, but note that HP-UX geometry is based
on 1024 byte sectors, while
NetBSD's
is based on 512 byte sectors.
You should have all partitions start on cylinder boundaries.
If you are installing to a SCSI disk, you don't need to worry about the details of the geometry. Just create a disklabel based on the total number of sectors available on the disk.
A quick note about partitions:
Since the target disk will become the boot
disk for your new
NetBSD/hp300
installation, you will need to treat the
`a'
and
`c'
partitions in a special manner.
Due to the size of the
NetBSD/hp300
boot program (it spills into the area after the disklabel),
it is necessary to offset the beginning of the
`a'
partition.
For HP-IB disks, it is best to offset it by one cylinder from
the beginning of the disk.
For SCSI disks, just offset it by 100 KB (200 sectors).
Later, the
`c'
partition will be marked with the type
`boot'
and may not be used for a file system.
(For those unfamiliar
with historic
BSD
partition conventions, the
`c'
partition is defined as the
`entire disk',
or the
`raw partition'.)
Here is an example disklabel from a 7959B HP-IB hard drive:
# /dev/rrd0a:
type: HP-IB
disk: rd7959B
label:
flags:
bytes/sector: 512
sectors/track: 42
tracks/cylinder: 9
sectors/cylinder: 378
cylinders: 1572
total sectors: 594216
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg]
a: 37800 378 4.2BSD 1024 8192 16 #
b: 66150 38178 swap 1024 8192 16 #
c: 594216 0 boot # (Cyl. 0 - 1571)
d: 489888 104328 4.2BSD 1024 8192 16 #
installation/misc/SYS_UBOOT.
If you do not have access to a netboot server to serve the miniroot
installer, you can use a primitive bootstrap program
installation/misc/SYS_INST
to load the miniroot from a locally attached device (such as a
disk, tape or CD-R).
This is not recommended, as
SYS_INST
is difficult to use, buggy, and provides no error checking when
partitioning your disk.
If your system has SCSI, this is easy.
Just take a scratch SCSI disk (hard disk, zip disk, or CD-R)
and use any computer to dump the bootstrap program to it.
For example, to dump it to the
sd1
disk on a non-i386 platform:
# dd if=SYS_UBOOT of=/dev/sd1c
If your system has a floppy drive, you can write the bootstrap program to
it using any computer with a floppy drive.
You will need to dump it using a utility like
rawrite
or
dd(1).
Make sure to read back from the floppy to verify that the file has been
written correctly.
If your system does not have SCSI or a floppy drive, you will need a bootable operating system on your hp300 so you can write files to the HP-IB device. You should probably write the bootstrap program to the disk you will be installing NetBSD onto.
Using HP-UX to write to an HP-IB disk:
# dd if=SYS_UBOOT of=/dev/rdsk/IDs0
00
and
07,
but possibly up to
1F
(31 decimal) .
Using HP-UX to write to an HP-IB tape:
# dd if=SYS_UBOOT of=/dev/rmt/0mnb obs=20b conv=osync
installation/miniroot/miniroot.fs.gz)
instead of the bootstrap program.
The only quirk is that you should place it at the offset of the swap
partition you calculated above in the disklabel.
In the example disklabel above, the offset is 38178 sectors of 512 bytes.
Therefore, the
dd(1)
command would be something like:
# gunzip miniroot.fs.gz
# dd if=miniroot.fs of=/dev/rdsk/IDs0 seek=38178b
b'
after the offset, which specifies blocks of 512 bytes.
By dumping the miniroot to disk where the swap partition will be, you're
saving a step later where
SYS_INST
tries to download the miniroot over NFS.
Just make sure that when you enter the partition table into
SYS_INST
you use the same block offset for the swap partition as you dumped the
miniroot.
SYS_UBOOT
and the miniroot installer to your hp300.
To netboot a hp300, you must configure one or more servers to provide
information and files to your hp300 (the
`client').
If you are using
NetBSD
(any architecture) on your netboot server(s), the information
provided here should be sufficient to configure everything.
Additionally, you may wish to look at the
diskless(8)
manual page and the manual pages for each daemon you'll be configuring.
If the server(s) are another operating system, you should consult the
NetBSD Diskless HOW-TO, which will walk you through the steps necessary to
configure the netboot services on a variety of platforms.
http://www.NetBSD.org/docs/network/netboot/
You may either netboot the installer so you can install onto a locally attached disk, or you may run your system entirely over the network.
Briefly, the netboot
process involves discovery, bootstrap, kernel and file system stages.
In the first stage, the client discovers information
about where to find the bootstrap program.
Next, it downloads and executes the bootstrap program.
The bootstrap program goes through another discovery phase to determine
where the kernel is located.
The bootstrap program tries to mount the NFS share containing the kernel.
Once the kernel is loaded, it starts executing.
For RAM disk kernels, it mounts the RAM disk file system and begins
executing the installer from the RAM disk.
For normal (non-RAM disk) kernels, the
kernel tries to mount the NFS share that had the kernel and starts
executing
the installation tools or
init(8).
All supported hp300 systems use HP's proprietary RMP (the
rbootd(8)
daemon) for the first discovery stage and bootstrap download stages.
The bootstrap program uses DHCP for its discovery stage.
NFS is used in both the kernel and file system stages to download the
kernel, and to access files on the file server.
We will use
`CC:CC:CC:CC:CC:CC'
as the MAC address (ethernet hardware address) of your netboot client
machine.
You should have determined this address in an earlier stage.
In this example, we will use
`192.168.1.10'
as the IP address of your client and
`client.test.net'
as its name.
We will assume you're providing all of your netboot services
on one machine called
`server.test.net'
with the client's files exported from the directory
/export/client/root.
You should, of course, replace all of these with the names, addresses,
and paths appropriate to your environment.
You should set up each netboot stage in order (i.e., discovery, bootstrap, kernel, and then file system) so that you can test them as you proceed.
rbootd(8)
Get
SYS_UBOOT
from the
installation/misc
directory of the distribution.
# mkdir -p /usr/mdec/rbootd
# cp SYS_UBOOT /usr/mdec/rbootd
# chmod -R a+rX /usr/mdec/rbootd
Create
/etc/rbootd.conf
with the following line:
CC:CC:CC:CC:CC:CC SYS_UBOOT
You will need to start the rbootd. If it's already running, you will need to restart it to force it to re-read its configuration file. If the server is running NetBSD, you can achieve this with:
# /etc/rc.d/rbootd restart
If your netboot server is not running
NetBSD
but other OSs (like Linux, Solaris etc.), you have to use
YAMAMORI Takenori's
sun-rbootd
package instead of native
rbootd(8).
Please refer the "Setting up the rbootd server" section
in the NetBSD Diskless HOW-TO
http://www.NetBSD.org/docs/network/netboot/rbootd/
for details.
dhcpd(8)
The bootstrap program uses DHCP to discover the location of the kernel.
Put the following lines in your
/etc/dhcpd.conf
(see
dhcpd.conf(5)
and
dhcp-options(5)
for more information):
ddns-update-style none;
# Do not use any dynamic DNS features
#
allow bootp; # Allow bootp requests, thus the dhcp server
# will act as a bootp server.
#
authoritative; # master DHCP server for this subnet
#
subnet 192.168.1.0 netmask 255.255.255.0 {
# Which network interface to listen on.
# The zeros indicate the range of addresses
# that are allowed to connect.
}
group {
# Set of parameters common to all clients
# in this "group".
#
option broadcast-address 192.168.1.255;
option domain-name "test.net";
option domain-name-servers dns.test.net;
option routers router.test.net;
option subnet-mask 255.255.255.0;
#
# An individual client.
#
host client.test.net {
hardware ethernet CC:CC:CC:CC:CC:CC;
fixed-address 192.168.1.10;
#
# Name of the host (if the fixed address
# doesn't resolve to a simple name).
#
option host-name "client";
#
# The path on the NFS server.
#
option root-path "/export/client/root";
#
# If your DHCP server is not your NFS server, supply the
# address of the NFS server. Since we assume you run everything
# on one server, this is not needed.
#
# next-server server.test.net;
}
#you may paste another "host" entry here for additional
#clients on this network
}
You will need to make sure that the
dhcpd.leases
file exists.
# touch /var/db/dhcpd.leases
You will need to start the dhcpd. If it's already running, you will need to restart it to force it to re-read its configuration file. If the server is running NetBSD, you can achieve this with:
# /etc/rc.d/dhcpd restart
nfsd(8),
mountd(8),
and
rpcbind(8)
Now your system should be able to load the bootstrap program and start looking for the kernel. Let's set up the NFS server. Create the directory you are exporting for the netboot client:
# mkdir -p /export/client/root
Put the following line in
/etc/exports
to enable NFS sharing:
/export/client/root -maproot=root client.test.net
If your server is currently running an NFS server, you only need to
restart
mountd(8).
Otherwise, you need to start
rpcbind(8)
and
nfsd(8).
If the server is running
NetBSD,
you can achieve this with:
# /etc/rc.d/rpcbind start
# /etc/rc.d/nfsd start
# /etc/rc.d/mountd restart
Now, if you place a kernel named
netbsd
in
/export/client/root
your client should boot the kernel.
If you are netbooting the installer, you can use either
the traditional miniroot-based installer
installation/miniroot/miniroot.fs.gz
or the experimental RAM disk-based installer
binary/kernel/netbsd-RAMDISK.gz.
To use the miniroot-based installer, mount the miniroot file system on your netboot server. This procedure does not work on any operating system other than NetBSD. You'll also need to either set up a new NFS share point or an FTP server for the distribution files, as they won't fit inside the miniroot file system.
# gunzip miniroot.fs.gz
# vnconfig -c /dev/vnd0c /path/to/miniroot.fs
# mount -o ro /dev/vnd0c /export/client/root
# ls /export/client/root
.profile dist/ install.md mnt/ sbin/ usr/
bin/ etc/ install.sub mnt2/ tmp/ var/
dev/ install* kern/ netbsd* upgrade*
If there are no files present in your exported directory, then something is wrong.
To use the RAM disk-based installer, uncompress and rename the kernel. Also, copy the distribution files to the client's root directory.
# cp *tgz /export/client/root
# gunzip netbsd-RAMDISK.gz
# mv netbsd-RAMDISK /export/client/root/netbsd
If you are running your hp300 diskless, simply use
binary/kernel/netbsd-GENERIC.gz.
You can skip this step if you do not plan to run your client diskless after installation. Otherwise, you need to extract and set up the client's installation of NetBSD. The Diskless HOW-TO describes how to provide better security and save space on the NFS server over the procedure listed here. See http://www.NetBSD.org/docs/network/netboot/nfs.html for details.
# cd /export/client/root
# tar -xpzf /path/to/files/base.tgz
# tar -xpzf /path/to/files/etc.tgz
Continue with the other non-essential distribution sets if desired.
# mkdir /export/client/root/swap
# dd if=/dev/zero of=/export/client/swap bs=4k count=4k
# echo '/export/client/swap -maproot=root:wheel client.test.net' | cat >> /etc/exports
# /etc/rc.d/mountd restart
# cd /export/client/root/dev
# ./MAKEDEV all
This procedure only works on NetBSD hosts.
fstab(5)
Create a file in
/export/client/root/etc/fstab
with the following lines:
server:/export/client/swap none swap sw,nfsmntpt=/swap
server:/export/client/root / nfs rw 0 0
rc.conf(5)
Edit
/export/client/root/etc/rc.conf
rc_configured=YES
hostname="client"
defaultroute="192.168.1.1"
nfs_client=YES
auto_ifconfig=NO
net_interfaces=""
Make sure rc does not reconfigure the network device since it will lose its connection to the NFS server with your root file system.
hosts(5)
file.
Edit
/export/client/root/etc/hosts
::1 localhost
127.0.0.1 localhost
192.168.1.10 client.test.net client
192.168.1.5 server.test.net server
If you want
these services to start up every time you boot
your server, make sure the following lines are present in your
/etc/rc.conf:
rbootd=YES rbootd_flags=""
dhcpd=YES dhcpd_flags="-q"
nfs_server=YES # enable server daemons
mountd=YES
rpcbind=YES rpcbind_flags="-l" # -l logs libwrap
HP-UX Compatible Boot Mode'.
If, when you power on your machine, it does
not
present a menu like the following, then you need to change your
configuration.
Copyright 1990,
Hewlett-Packard Company.
All Rights Reserved.
BOOTROM Series 400 Rev. 1.1
MD12 REV 1.2 1990/08/07.14:27:08
[...]
RETURN
to get the Domain boot prompt
>).
H
to get a list of available commands.
HP-UX Compatible Boot Mode'.
> CF
Type [key] RETURN ? 2
Type [key] RETURN ? 2
Type T or P RETURN ? P
Type [key] RETURN ? E
At any time after it recognizes the keyboard, while it is doing its self
test or searching for a bootable system, you can hit reset to return it to
a cold-boot configuration.
On HIL keyboards, this is
control-shift-break,
where
break
is the key in the upper left (where
escape is on sane keyboards).
There is no equivalent over serial terminal,
you'll need to power-cycle your machine.
After it beeps (i.e. recognizes the HIL keyboard), press
RETURN
twice to get the list of bootable devices.
SEARCHING FOR A SYSTEM (RETURN To Pause)
The newer HP Boot ROM, present on Series 400 machines and some of the
later 300s (345, 375, 380, 382, 385) is capable of a little bit more.
To select which device to boot from, press
RETURN
once after it beeps twice (i.e. recognizes the HIL keyboard) to get the
list of bootable devices.
RESET To Power-Up, SPACE clears input Select System, type RETURN ?
The FAQ lists additional things you can do with the BootROM and describes the order the BootROM looks for bootable devices. http://www.NetBSD.org/ports/hp300/faq.html
A normal power-on sequence (from a 400s) looks something like this:
Copyright 1990,
Hewlett-Packard Company.
All Rights Reserved.
BOOTROM Series 400 Rev. 1.1
MD12 REV 1.2 1990/08/07.14:27:08
MC68030 Processor
MC68882 Coprocessor
Configuration EEPROM
Utility Chip at 41
HP-HIL.Keyboard
RESET To Power-Up
Loading Memory
Self-Test Mode
RESET To Power-Up, SPACE clears input
Select System, type RETURN
HP-IB
DMA-C0
Self-Test Mode
RAM 33554158 Bytes
HP98644 (RS-232) at 9
HP PARALLEL at 12
HP98265 (SCSI S 32) at 14
HP98643 (LAN) at 21, AUI, 080009115DB3
Bit Mapped Video at 133 (Console)
System Search Mode
:RODIME RO3000T, 1406, 0
1Z SYS_UBOOT
:LAN080009115DB3, 2100, 0
2Z SYS_UBOOT
:HP7959, 702, 0, 0
1H SYSHPUX
1D SYSDEBUG
1B SYSBCKUP
:HP9122, 0700, 0, 0
3Z SYS_INST
You should see your bootstrap program somewhere in this list.
If it's not here, then your hp300 can't boot it and there's a problem somewhere.
To boot from a particular device, type in the two character name for it
and press
RETURN.
In this example, you'd type
2Z
to boot from the network.
HP98643 (LAN) at 21, AUI
HP98643 (LAN) at 21, Thin
If the wrong type of network is selected, you will need to change the ethernet port. You will need to open the case (4XXt, 4XXdl, 4XXe) or remove the motherboard (4XXs) to access the jumper. Be sure to use static-prevention measures, as you could easily fry your motherboard from carelessness. If you are uncomfortable with this, ask a friend who is aware of these issues. There is a block of 8 jumpers at the rear of the motherboard, labeled AUI/Thin. You will need to put the jumpers in the position necessary for your type of ethernet.
Chose
SYS_INST
from the list of bootable devices that the BootROM found.
SYS_INST
will load and prompt you for a command.
A quick note about disk numbers:
While in the
SYS_INST
program, you may use different unit numbers for the disks than when the
NetBSD
kernel is running.
The unit number for a disk while in
SYS_INST
is calculated with the following formula:
unit = (controller * 8) + slaveID
Controllers are numbered 0, 1, ... starting with the lowest select code. SCSI controllers and HP-IB controllers are counted separately. Therefore, if you had a system with an internal HP-IB interface at select code 7, a fast HP-IB interface at select code 14, and a SCSI interface at select code 16, unit numbers might be something like the following:
| Location | Unit | |
| HP-IB at 7, slaveID 2 | 2 | (disk: rd2) |
| HP-IB at 14, slaveID 5 | 13 | (disk: rd13) |
| SCSI at 16, slaveID 0 | 0 | (disk: sd0) |
You will need to place a disklabel on the disk.
sys_inst> disklabel
Select the edit option, and answer the questions about your disk. There may be several questions which you may not be sure of the answers to. Listed below are guidelines for SCSI and HP-IB disks:
| Bad sectoring? | NO |
| Ecc? | NO |
| Interleave? | 1 |
| Trackskew? | 0 |
| Cylinderskew? | 0 |
| Headswitch? | 0 |
| Track-to-track? | 0 |
| Drivedata 0-4? | 0 (for all Drivedata values) |
Next, you will be asked to fill out the partition map.
You must provide responses for all 8 partitions.
Remember, you must have the sector offset for the
`b'
partition match the location you dumped the miniroot file system image.
Set the size and
offset of any unused partition to 0.
Note that sizes and offsets are expressed in
`n sectors',
assuming 512 byte sectors.
Care should be taken
to ensure that partitions begin and end on cylinder boundaries (i.e. size
and offset is an even multiple of the number of sectors per cylinder).
While this is not technically necessary, it is generally encouraged.
b'
partition, make sure to
specify it as an
ffs
partition so that the miniroot can be mounted (even
if this will be a swap partition).
You will be given a chance to clean
this up later in the installation process.
Once you have edited the label, select the show option to verify that it is correct. If so, select write and done. Otherwise, you may re-edit the label.
In an earlier step, we already copied the miniroot image to the target disk.
Boot from the miniroot file system.
sys_inst> boot
Enter the disk from which to boot. The kernel in the miniroot file system will be booted into single-user mode.
SYS_UBOOT
has started, it will pause and let you chose a kernel location, name, and
options:
>> NetBSD/hp300 Primary Boot, Revision 1.13
>> (gregm@mcgarry, Mon Apr 15 08:46:32 NZST 2002)
>> HP 9000/425e SPU
>> Enter "reset" to reset system.
Boot: [[[le0a:]netbsd][-a][-c][-d][-s][-v][-q]] :-
If your kernel is on a different device than
SYS_UBOOT
then you will need to type in where to find it.
This is the case, for
example, if your model is incapable of netbooting and you started
SYS_UBOOT
from a floppy, and the miniroot installer is on a netboot server.
In this case, you'd type in
`le0'
at the prompt.
If you've installed the miniroot on your disk, you can always boot from
that by using partition
`b'
when prompted by
SYS_UBOOT.
For example, to boot the miniroot from an HP-IB disk on controller 0 at
slave ID 2, you'd type:
Boot: [[[rd0a:]netbsd][-a][-c][-d][-s][-v][-q]] :- rd2b:netbsd
The miniroot's install program is very simple to use.
It will guide you through the entire process, and is well automated.
If you need to restart the installer, hit
Control-C
which will return you to a shell prompt.
From there, just start it over:
# ./install
The experimental RAM disk-based installer is not described here, but is very self-explanatory.
The miniroot's install program will:
fstype: 4.2BSD
fsize: 1024
bsize: 4096
cpg: 16
If the partition will be a swap partition, use the following:
fstype: swap
fsize: 0 (or blank)
bsize: 0 (or blank)
cpg: 0 (or blank)
You will also need to specify the number of partitions.
The number of partitions is determined by the
`index'
of
the last partition letter, where
a
=
1,
b
=
2,
etc.
Therefore, if the last filled partition is partition
`g',
there are 7 partitions.
Any partitions with size of 0 may be removed from the list.
Anything after a
`#'
is a comment.
The following is an example disklabel partition map:
7 partitions:
# size offset fstype [fsize bsize cpg]
a: 30912 448 4.2BSD 1024 8192 16 # (Cyl. 1 - 69)
b: 130816 31360 swap # (Cyl. 70 - 361)
c: 1296512 0 boot # (Cyl. 0 - 2893)
e: 81984 162176 4.2BSD 1024 8192 16 # (Cyl. 362 - 544)
f: 102592 244160 4.2BSD 1024 4096 16 # (Cyl. 545 - 773)
g: 949760 346752 4.2BSD 1024 8192 16 # (Cyl. 774 - 2893)
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
hp300h
for a local console, or whatever is appropriate for your serial console.
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 installed the X Window System, you may want to read the
chapter about X in the NetBSD Guide:
http://netbsd.org/docs/guide/en/chap-x.html
Also, you may want to read through the
NetBSD/hp300
FAQ entry on X11.
http://www.NetBSD.org/ports/hp300/faq.html#x11
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.
hp300/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/hp300/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/hp300/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/hp300/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/hp300 system using the upgrade program in the miniroot or by manually performing the same steps as the miniroot upgrade program.
In particular, make sure you have on your locally mounted file systems
base.tgz
and
miniroot.fs.gz
Follow the instructions in the section above on
Chosing a kernel location
and type
-s
at the prompt.
Make sure you install the bootstrap program distributed with this version of NetBSD/hp300.
# tar -xpvzf base.tgz ./usr/mdec
# disklabel -B -b ./usr/mdec/uboot.lif root-disk
sd0
or
rd0.
We'll assume
rd0
for now.
First make sure that your
`b'
partition has enough room for the uncompressed miniroot (otherwise it
might overwrite another partition or the end of the disk).
# gunzip miniroot.fs.gz
# dd if=miniroot.fs of=/dev/rd0b
Follow the instructions in the section above on
Chosing a kernel location
and type
rd0b:netbsd
at the prompt.
The upgrade program will:
/etc/fstab,
changing the occurrences of
ufs
to
ffs
and let you edit the resulting file.
/dev.
/).
Make sure you install the bootstrap program distributed with this version of NetBSD/hp300.
# tar -xpvzf base.tgz ./usr/mdec
# disklabel -B -b ./usr/mdec/uboot.lif root-disk
sd0
or
rd0.
# /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 /path/to/base.tgz
# 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