About this Document............................................1
Quick install notes for the impatient..........................2
What is NetBSD?................................................2
Upgrade path to NetBSD 1.6.....................................3
Changes Between The NetBSD 1.5 and 1.6 Releases................3
Kernel......................................................3
Networking..................................................4
File system.................................................4
Security....................................................5
System administration and user tools........................5
Miscellaneous...............................................6
sparc specific..............................................7
The Future of NetBSD...........................................7
Sources of NetBSD..............................................7
NetBSD 1.6 Release Contents....................................7
NetBSD/sparc subdirectory structure.........................9
Binary distribution sets...................................10
NetBSD/sparc System Requirements and Supported Devices........11
Supported machines.........................................11
Machines not supported by NetBSD/sparc.....................12
Supported devices..........................................12
Unsupported devices........................................14
Getting the NetBSD System on to Useful Media..................14
Preparing your System for NetBSD installation.................16
Configuring your PROM......................................17
Determining how to access your SCSI disk from the..........18
Determining how to boot from an SBUS card..................19
Deciding on partition sizes................................20
Configuration of network interfaces........................21
Installing the NetBSD System..................................21
Installing NetBSD by placing a bootable file system on.....21
Installing NetBSD by using a bootable CD-ROM...............22
Installing NetBSD by using the bootable floppies...........22
Installing NetBSD by using a netboot setup.................23
Installing NetBSD by using a bootable tape.................28
Running the installation scripts...........................29
Post installation steps.......................................30
Upgrading a previously-installed NetBSD System................32
Compatibility Issues With Previous NetBSD Releases............33
Issues affecting an upgrade from NetBSD 1.5................33
Issues affecting an upgrade from NetBSD 1.4 or prior.......34
Using online NetBSD documentation.............................35
Administrivia.................................................35
Thanks go to..................................................36
We are........................................................38
Legal Mumbo-Jumbo.............................................42
The End.......................................................45
This document describes the installation procedure for
NetBSD1.6
on the
sparc
platform.
It is available in four different formats titled
INSTALL.
ext,
where
.ext
is one of
.ps
, .html
, .more
,
or .txt
:
.ps
.html
.more
more(1)
and
less(1)
pager utility programs.
This is the format in which the on-line
man
pages are generally presented.
.txt
You are reading the HTML version.
This section contains some brief notes describing what you need to install NetBSD1.6 on a machine of the sparc architecture.
sparc_bootable.iso
or the floppy disk images,
install/floppy/disk1.gz
and
install/floppy/disk2
.
You need either the pair of floppies or the CD to boot your system.
Alternatively, you may netboot the installation kernel, which requires
several local netboot services.
The details are not covered here, as setting up a netboot server is hardly
``quick''.
binary/sets/
directory.
When you boot the install
floppies or CD-ROM,
the installation program
can fetch these files for you (using e.g. ftp),
if you have a network connection.
There are several other methods to get the binary sets onto
your machine.
You will at a minimum need
the following sets:
kern-GENERIC.tgz
,
base.tgz
and
etc.tgz
.
In a typical workstation installation you will probably want
all the installation sets.
The disk(s) you just prepared will be used to boot the installation kernel, which contains all the tools required to install NetBSD.
STOP-A
keys.
At the
``ok''
prompt, type the command to boot your system into
NetBSD.
The command to boot from CD is one of the following commands (depending on
your model):
``b sd(,30,)'',
``boot sd(,30,)'',
or
``boot cdrom''.
The command to boot from floppy is either ``boot fd(,,1)'' or ``boot floppy''. The installer will prompt you to insert the second floppy when it is ready for it.
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 fifty three different system architectures (ports), featuring seventeen machine architectures across eleven distinct CPU families, and is being ported to more. The NetBSD1.6 release contains complete binary releases for thirty eight different system architectures. (The fifteen remaining are not fully supported at this time and are thus not part of the binary distribution. For information on them, please see the NetBSD web site at http://www.netbsd.org/.)
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.
NetBSD1.6 is an upgrade of NetBSD1.5.3 and earlier major and patch releases of NetBSD.
The intermediate development versions of code available on the main trunk in our CVS repository (also known as ``NetBSD-current'') from after the point where the release cycle for 1.6 was started are designated by version identifiers such as 1.6A, 1.6B, etc. These identifiers do not designate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.6 can not be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD 1.6 kernel on such a system will probably result in problems.
Please also note that it is not possible to do a direct ``version'' comparison between any of the intermediate development versions mentioned above and 1.6 to determine if a given feature is present or absent in 1.6. The development of 1.6 and the subsequent ``point'' releases is done on a separate branch in the CVS repository. The branch was created when the release cycle for 1.6 was started, and during the release cycle of 1.6 and its patch releases selected fixes and enhancements have been imported from the main development trunk.
The NetBSD1.6 release provides numerous significant functional enhancements, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many user-land enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems.
It is impossible to completely summarize over eighteen months of development that went into the NetBSD1.6 release. Some highlights include:
scsipi(9)
.
userconf(4)
,
activated with the
-c
boot loader flag.
ehci(4)
host controller.
irframe(4)
IrDA frame level driver.
Serial dongles and the
oboe(4)
driver are currently supported.
INCLUDE_CONFIG_FILE
in
options(4)
for more information.
sysctl(8)
.
).
vlan(4)
.
ndbootd(8)
added;
used to netboot
NetBSD/sun2
machines.
racoon(8)
added;
IKE key management daemon for IPsec key negotiation, from the KAME project.
ifconfig(8)
and
awi(4)
driver.
wi(4)
and
wiconfig(8)
now support scanning for access points,
and defaults to BSS instead of ad-hoc mode.
bridge(4)
.
pppoe(4)
.
ifwatchd(8)
added;
invokes up-script and down-script when a network interface goes up and down.
Used by
pppoe(4)
.
dump(8)
,
dumpfs(8)
,
fsck_ffs(8)
,
fsirand(8)
,
newfs(8)
,
and
tunefs(8)
support a
-F
option to manipulate file system images in regular files.
makefs(8)
added;
creates file system images from a directory tree.
(Currently ffs only.)
)
by Grigoriy Orlov, which noticeably improves performance on FFS file systems
when creating directories, and subsequently manipulating them.
newfs(8)
calculates default block size from the file system size,
and uses the largest possible cylinders/group (cpg) value if
-c
isn't given.
dpti(4)
driver added;
an implementation of the DPT/Adaptec SCSI/I2O RAID management interface.
Allows the use of the Linux versions of
dptmgr,
raidutil,
dptelog,
(etc).
chroot(8)
hierarchy for services including
named(8)
,
ntpd(8)
,
and
sshd(8)
.
passwd(5)
ciphers:
MD5, and
DES with more encryption rounds.
See
passwd.conf(5)
.
/etc/security
performs many more checks and is far more flexible in how it monitors
changes.
See
security.conf(5)
.
sushi(8)
added;
a menu based system administration tool.
pgrep(1)
and
pkill(1)
added;
find or signal processes by name or other attributes.
etcupdate(8)
script which helps updating the
/etc
config files interactively, and the
/etc/postinstall
script which is provided to check for or fix configuration changes
that have occurred in
NetBSD.
stat(1)
added;
a user interface to the information returned by the
stat(2)
system call.
sort(1)
replaces
GNU
sort(1)
.
rc.d(8)
scripts waits until the service terminates before returning.
This improves the reliability of
``restart''
operations as well.
swapoff
in
rc.conf(5)
.
rc.shutdown(8)
after the number of seconds provided in
rcshutdown_timeout
from
rc.conf(5)
.
src/build.sh
is available for doing arbitrary cross-builds; see
src/BUILDING
for more information.
At least 38 ports for the
NetBSD1.6
release were cross-built on a
NetBSD/i386
system using this mechanism.
agp(4)
for faster access to graphics boards.
init(8)
will create an mfs (memory based file system)
/dev
if
/dev/console
is missing.
vmstat(8)
displays kernel hash statistics with
-H
and
-h hash.
wscons(4)
supports blanking of VGA consoles.
Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue.
NetBSD1.6 is the seventh major release for the sparc.
Some (but not all!) notable sparc-specific improvements include:
NetBSD1.6 on sparc is, as usual, also fully backward compatible with old NetBSD/sparc binaries, so you don't need to recompile all your local programs provided you set the appropriate binary compatibility options in your kernel configuration.
The NetBSD Foundation has been incorporated as a non-profit organization. Its purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project.
The NetBSD Foundation will help improve the quality of NetBSD by:
We intend to begin narrowing the time delay between releases. Our ambition is to provide a full release every six to eight months.
We hope to support even more hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD.
We intend to continue our current practice of making the NetBSD-current development source available on a daily basis.
We intend to integrate free, positive changes from whatever sources submit them, providing that they are well thought-out and increase the usability of the system.
Above all, we hope to create a stable and accessible system, and to be
responsive to the needs and desires of
NetBSD
users, because it is for
and because of them that
NetBSD
exists.
Refer to
http://www.netbsd.org/Sites/net.html.
The root directory of the NetBSD1.6 release is organized as follows:
.../NetBSD-1.6/
CHANGES
LAST_MINUTE
MIRRORS
README.files
TODO
patches/
source/
In addition to the files and directories listed above, there is one
directory per architecture, for each of the architectures for which
NetBSD1.6
has a binary distribution.
There are also
README.export-control
files sprinkled liberally throughout the
distribution tree, which point out that there are some portions of the
distribution that may be subject to
export regulations of the United States, e.g.
code under
src/crypto
and
src/sys/crypto
.
It is your responsibility
to determine whether or not it is legal for you to export these portions
and to act accordingly.
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(8)
;
and
dbsym(8)
.
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
The
sets/Split/
subdirectory contains split
versions of the source sets for those users who need to load the
source sets from floppy or otherwise need a split distribution.
The split sets are named
set_name.
xx
where
set_name
is the distribution set name, and
xx
is the sequence number of the file,
starting with
``aa''
for the first file in the distribution set, then
``ab''
for the next, and so on.
All of these files except the last one of each set should be exactly
240,640 bytes long.
(The last file is just long enough to contain the remainder of the data
for that distribution set.)
The split distributions may be reassembled and extracted with cat as follows:
#
cat set_name.?? | ( cd / ; tar -zxpf - )
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
BSDSUM
CKSUM
MD5
SYSVSUM
The MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of system can check the integrity of the release files.
sparc
subdirectory of the distribution:
.../NetBSD-1.6/sparc/
INSTALL.html
INSTALL.ps
INSTALL.txt
INSTALL.more
.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/
kernel/
netbsd-GENERIC.gz
sets/
installation/
miniroot/
misc/
netboot/
sparc/binary/sets
subdirectory
of the
NetBSD1.6
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, and tightly track XFree86 releases. They are currently equivalent to XFree86 3.3.6. Binary sets for the X Window System are distributed with NetBSD. The sets are:
The sparc 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 -xpf
command from the root directory (
/
) of your system.
This utility is used only in a Traditional method installation.
sparc/installation/misc
.
GENERIC_SUN4U
kernel.
UltraSPARC based machines in 32-bit or 64-bit mode are supported by the NetBSD/sparc64 port. Refer to http://www.netbsd.org/Ports/sparc64/index.html
The minimal configuration requires 4 MB of RAM and ~60 MB of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended, as NetBSD with 4 MB of RAM feels like Solaris with 4 MB of RAM - slow. Note that until you have around 16 MB of RAM, getting more RAM is more important than getting a faster CPU.
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.
Proceed to the instruction on installation.
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.184.75
(as of June, 2002).
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 of 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 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
misc, 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-1.6
#
cd sparc/binary
#
tar -cf tape_device misc etc kern
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.
Place the distribution sets you wish to upgrade somewhere in your current file system tree.
At a bare minimum, you must upgrade the base and kern binary distributions, and so must put the base and kern sets somewhere in your file system. If you wish, you can do the other sets, as well, but you should not upgrade the etc distribution; it contains contains system configuration files that you should review and update by hand.
Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system.
First, you need to stop your system from automatically booting when
powered on. Pressing the
STOP
key (sometimes called the
L1
key, found on the left side of your keyboard) and the
a
key will halt your system and give you a PROM prompt. If you are using a
Tadpole SPARCbook, you press the
Pause
and
a
keys. If you are using a serial console, send a
``BREAK''
signal from your terminal (the method of sending
``BREAK''
varies from terminal to terminal).
If the ethernet address of your sparc system is
ff:ff:ff:ff:ff:ff
,
then your NVRAM battery is dead and you will have trouble using
ethernet (among other problems). Read the Sun NVRAM/Hostid FAQ.
http://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html
If you have a valid ethernet address and you plan to netboot, write down your system's ethernet address.
Next, you should set your system to always use the OpenBoot PROM (sometimes called ``new command mode'') if it defaults to sunmon. The NetBSD kernel relies on some of the functionality provided by the OpenBoot PROM. If your machine gives you a `>' prompt instead of an `ok' prompt, type:
> n
ok setenv sunmon-compat? false
ok
Next, if you are using any security features of OpenBoot PROM, you should turn them off -- NetBSD can't deal well with this.
ok setenv security-mode none
The OpenBoot PROM 1 machines (SPARCstation/server 1, SPARCstation/server 1+, IPC, and SLC) have an odd SCSI quirk you should be aware of. There are three SCSI addressing schemes used by your system: SCSI target ID (set by physical jumpers on the device), PROM `unit' number (set by OpenBoot PROM 1, based on its SCSI target ID), and the name you reference within an operating system (set by the kernel, based on the PROM `unit' number).
Sun shipped these systems with the internal drives set to SCSI target IDs
3 and 1. The default value of the OpenBoot PROM variable
`sd-targets
'
is
`31204567.
'
This variable maps how the OpenBoot PROM 1 assigns
`unit'
numbers based on the SCSI target ID.
Thus the device at SCSI target ID 3 is considered
`unit'
0, and the SCSI device at target ID 0 is
`unit'
3. When you type
``boot scsi(0,0,0)'',
the OpenBoot PROM will boot from
`unit'
0 (which is SCSI target ID 3, the internal hard drive). The
SunOS
kernel is hard-wired to map
sd0
to SCSI target 3, and
sd3
to SCSI target 0.
PROM Unit# SCSI Target | SunOS name
| 0 | 3 | sd0
| 1 | 1 | sd1
| 2 | 2 | sd2
| 3 | 0 | sd3
| 4 | 4 | st0
| 5 | 5 | st1
| 6 | 6 | cdrom
| |
The
NetBSD/sparc
GENERIC
kernel does not wire things down as does
SunOS.
It names the disks in the order
that the SCSI targets are probed (01234567). If you only have one disk,
it is always
sd0
regardless of its SCSI target ID or its PROM
`unit'
number, and there are no problems. If you have two disks, one at
SCSI ID 2 (
`unit'
2) and SCSI ID 3 (
`unit'
0), then they are recognized as
sd0
and
sd1
respectively. This can be a problem if you are not
aware of it, particularly when creating an fstab.
There are two approaches to fixing this problem: changing the mapping that OpenBoot PROM 1 does, and changing the NetBSD kernel configuration. To get OpenBoot PROM 1 to number the SCSI `unit' numbers the same as the SCSI target IDs, you need to run this command:
ok setenv sd-targets 01234567
This may, however, cause problems if you were to later attempt to use SunOS on this machine or if you reset the OpenBoot PROM variables.
The other approach is to use a
NetBSD
kernel that matches the PROM's odd target mapping by treating
`unit'
0 (i.e. SCSI target ID 3) as
sd0
and
`unit'
3 (i.e. SCSI target ID 0) as
sd3
.
The
GENERIC_SCSI3
kernel performs this target mapping, but the
GENERIC
and
INSTALL
kernels do not.
The machines with OpenBoot PROM 2 (SPARCstation/server 2, ELC, IPX, and all sun4m models) have a similar SCSI target mapping in the form of a devalias entry. That is, the device alias disk is shorthand for the disk at SCSI ID 3 on the internal SCSI controller. Normally, the disk device alias is what the PROM uses as the default boot device, i.e. in the absence of a device argument to the boot command. Note that there are also pre-configured device alias entries for disk0, disk1, disk2 and disk3, which are in fact a one-to-one mapping to the SCSI targets 0 to 3 (all on the internal SCSI controller).
Again, it may be advantageous to use a fixed
``SCSI target''
to
``NetBSD disk unit''
mapping in your kernel configuration file (such as is done in the
GENERIC_SCSI3
kernel) to ensure that your disks remain showing up at the same
NetBSD
device unit numbers even if you add disks to your system at a later time.
sd(
c,u,p)
syntax to address SCSI devices. OpenBoot PROM 2 uses a more intuitive
syntax using device aliases.
To calculate the parameters for sunmon and OpenBoot PROM 1:
a
',
`
1
'
=
`
b
',
etc.
(`
0
')
Therefore, to boot from the swap partition on the internal hard drive (first SCSI bus, target 0, lun 0, partition 1), one would use:
ok boot sd(0,0,1)
To boot from a CD-ROM (first SCSI bus, target 6, lun 0, partition dynamically determined), one would use:
ok boot sd(0,30,)
And, to boot from a kernel named
netbsd-GENERIC
on the fourth partition (
`d
',
often the
/usr
partition) on an external hard drive (first SCSI bus, target 2, lun 0,
partition 3), one would use:
ok boot sd(0,10,3)netbsd-GENERIC
Now, for OpenBoot PROM 2, SCSI devices are specified by an OpenBOOT devalias which provides simple mnemonics for the full path to the device. Type devalias in OpenBoot PROM 2 to get a list of all of the available aliases. Just the alias and partition are necessary when booting.
Therefore, to boot from the swap partition on the internal hard drive (OpenBoot PROM 2 assumes the internal hard drive is at target 3), one would use:
ok boot disk:b
To boot from a CD-ROM (OpenBoot PROM 2 assumes the CD-ROM is at target 6), one would use:
ok boot cdrom
And, to boot from a kernel named
netbsd-GENERIC
on the fourth partition (
`d
',
often the
/usr
partition) on an external hard drive (target 2, partition 3), one would use:
ok boot disk2:d netbsd-GENERIC
The full device path specifier for OpenBoot PROM 2 depends on how OpenBoot
PROM 2 recognizes
your SCSI controller. Typically, one would use something like:
/sbus/esp/sd@
t,p
where t is the SCSI target and p is the partition number.
ok cd /
ok ls
ffd3b790 TI,TMS390S10@0,f8fffffc
ffd2d254 virtual-memory@0,0
ffd2d198 memory@0,0
ffd2b65c obio
ffd2b310 iommu@0,10000000
ffd2b2a0 openprom
ffd24af0 aliases
ffd24abc options
ffd24a88 packages
ok cd iommu
ok ls
ffd2b454 sbus@0,10001000
ok cd sbus
ok ls
ffd467e8 cgthree@3,0
ffd42a1c SUNW,hme@1,8c00000
ffd4297c le@0,c00000
ffd40d28 ledma@4,8400010
ffd40c9c SUNW,bpp@4,c800000
ffd40c00 audio@4,1300000
ffd3dc68 espdma@4,8400000
ok cd SUNW,hme
ok ls
ok pwd
/iommu@0,10000000/sbus@0,10001000/SUNW,hme@1,8c00000
ok words
reset seek load open close
watch-net selftest obp-selftest write read
preamble-32 enable-link-pulse disable-link-pulse
force-speeds reset-transceiver use-bit-bang-mode
use-frame-mode dump-phys transfer-speed=10
transfer-speed=100 mii-write mii-read
create-rev-id
ok .attributes
hm-rev 00000022
version 1.18
model SUNW,501-2919
device_type network
intr 00000037 00000000
interrupts 00000004
address-bits 00000030
max-frame-size 00004000
reg 00000001 08c00000 00000108
00000001 08c02000 00002000
00000001 08c04000 00002000
00000001 08c06000 00002000
00000001 08c07000 00000020
name SUNW,hme
ok
ok boot /iommu/sbus/SUNW,hme
root on sd0a dumps on sd0b
no file system for sd0 (dev 0x700)
cannot mount root, error = 79
root device (default sd0a): ?
use one of: fd0[a-h] le0 le1 hme0 sd0[a-h] halt
root device (default sd0a): hme0
dump device: hme0
file system (default generic): nfs
root on hme0
Assuming a classic partition scheme with
/
(root) and
/usr
file systems, a comfortable size for the
NetBSD
root file system partition is
about 20 MB; a good initial size for the swap partition is twice the amount
of physical memory in your machine (though, unlike
SunOS 4.x,
there are no restrictions on the size of the swap partition that would render
part of your memory unusable). A full binary installation takes about 60 MB
in
/usr
.
Most sparc systems have trouble booting if the root partition extends beyond the first 2 GB of your disk.
If automatic detection is not available or not working properly in your
environment, you may have to specify the type connection using the
media
parameter of
ifconfig(8)
.
During installation, you'll get the opportunity to specify the appropriate
medium. Use
10base5
or
AUI
to select the AUI connector, or
10baseT
or
UTP
to select the UTP connector.
Fast ethernet interfaces default to
auto
,
which usually does not detect properly and runs at
`10BaseT'
speed.
The options are
10baseT
,
10baseTX
,
and
auto
.
The
hme
and
qfe
interfaces also allow
10baseT-FDX
and
100baseT-FDX
.
Installing NetBSD is a relatively complex process, but if you have this document in hand it shouldn't be too much trouble.
There are several ways to install
NetBSD
onto your system.
The easiest way is to use the
miniroot.fs
image copied to your local disk's swap partition or a scratch drive.
If your Sparc is hooked up in a network, you may configure another
UNIX-like
machine as a netboot server for your Sparc.
Alternatively, there is a pair
of floppy images that will boot your system and run the installer.
For more information on the commands and variables available in the OpenBoot PROM (present in all sun4c and sun4m machines), go to http://docs.sun.com and search for ``openboot reference'' (without quotes).
installation/miniroot/miniroot.fs.gz
is a compressed, self-contained
NetBSD
file system holding all utilities necessary to install
NetBSD
onto a disk attached to your system.
It is distributed as a compressed plain
file you will transfer to a raw disk partition.
You will then boot this installer using the appropriate PROM command.
The simplest case is where you place the
miniroot.fs
file system on the swap partition of your disk.
Alternatively, you can place
it on any other unused partition on any disk (such as a Zip disk).
Be forewarned that you will not be able to install
NetBSD
onto the partition that contains the
miniroot.fs
as this partition is needed during the install process.
Loading the file system onto a raw partition is straightforward.
First, download
miniroot.fs
to your system.
Next, reboot in single-user mode (i.e.
boot -s)
to ensure that your system will not be swapping.
Finally, place the
miniroot.fs
on your partition of choice.
On
NetBSD
or SunOS the commands are:
# gunzip miniroot.fs.gz
# dd if=miniroot.fs of=/dev/rsd0b bs=4k conv=sync
Here,
/dev/rsd0b
is assumed to be your swap partition.
If you decide to place
miniroot.fs
on a non-swap partition, it will overwrite all of the contents of that
partition, but you will not need to reboot into single-user mode to write it.
After transferring the file system to disk, bring the system down by:
# halt
Then boot the installer by typing the appropriate command at the PROM prompt (this example is for the swap partition):
> b sd(,,1)netbsd -s
ok boot sd(,,1)netbsd -s
ok boot disk:b netbsd -s
The monitor boot command will load the NetBSD kernel contained in the file system image. After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section Running the installation scripts. below.
installation/cdrom/netbsd-sparc.iso
or create your own.
If you wish to create your own, you should follow the directions on the
NetBSD
Bootable CD-ROM HOW-TO at:
http://www.netbsd.org/Documentation/bootcd.html#sparcimage
Once you have downloaded
netbsd-sparc.iso
or created your own disk image, then you need to burn it to a CD-R.
The CD-ROM attached to your Sparc must support 512 byte sectors to be bootable. All Sun brand CD-ROMs will work, as well as many other manufacturers. See the Sun CD-ROM FAQ: http://saturn.tlug.org/suncdfaq/
Sun sets their CD-ROM drives to SCSI ID 6. We recommend you do the same.
Boot the installer by typing the appropriate command at the PROM prompt:
> b sd(,30,)
ok boot sd(,30,)
ok boot cdrom
After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section Running the installation scripts. below.
NetBSD
and SunOS use the same commands.
First, get two 1.44 MB floppy disks and format them either using the
fdformat(8)
command or a PC.
# fdformat
Be sure that the `fdformat' command completes successfully before proceeding;
on
NetBSD
success is a string of all
`V
's
',
and on
SunOS
success is a string of
`.
's
'.
Next, transfer the two floppy images
(installation/floppy/disk1.gz
and installation/floppy/disk2
)
to the disks you just formatted.
You can do this step from
NetBSD,
SunOS,
or a
Windows
machine using
rawrite.exe
(available in the
NetBSD/i386
distribution).
Insert the first floppy and run the following commands:
# gunzip disk1.gz
# dd if=disk1 of=/dev/rfd0a bs=36k
# eject floppy
Insert the second floppy and run the following commands:
# dd if=disk2 of=/dev/rfd0a bs=36k conv=sync
# eject floppy
Note that disk2 may be a symlink to .tgz file; do not uncompress it, just follow the instructions above, verbatim. After writing the two floppies, be sure to label them so you can later identify them.
Insert the floppy made from
disk1
into your Sparc.
From the OpenBoot prompt, boot the floppy with the following command:
ok boot fd(,,1)
ok boot /fd
ok boot floppy
After the initial probe messages you'll be asked to insert the floppy labeled ``NetBSD disk2''. If the floppy is not automatically ejected, you can either use a straightened paperclip to eject the disk or do the following:
Press the
STOP
key (sometimes called the
L1
key, found on the left side of your keyboard) and the
a
key, which will halt your system and give you a PROM prompt.
ok eject
ok go
Now, insert the floppy labeled
disk2
.
After the installation tools have been loaded,
you'll be asked to start the install or upgrade procedure.
Proceed to the section
Running the installation scripts.
below.
To netboot a sparc, you must configure one or more servers to provide
information and files to your sparc (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/Documentation/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 sparc systems use a combination of RARP and BOOTP for the discovery stage.
In the past, these systems used RARP and BOOTPARAMS.
TFTP is used in the bootstrap phase to download
the bootstrap program,
boot.net
,
which has been linked to a file name appropriate to the client's
architecture and IP address as described in the TFTP section below.
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.
dhcpd(8)
in
bootpd(8)
compatible mode
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; # This is the authoritative DHCP server for this subnet
#
subnet 192.168.1.0 netmask 255.255.255.0 {
# Which network interface the server will listen on.
# The zeros indicate which range of addresses 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";
}
#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 NetBSD1.5 or later, you can achieve this with:
# /etc/rc.d/dhcpd restart
rarpd(8)
Create an
/etc/ethers
file with the following line:
CC:CC:CC:CC:CC:CC client
Add your client to the server's
/etc/hosts
file:
192.168.1.10 client
You will need to start the rarpd. 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 NetBSD1.5 or later, you can achieve this with:
# /etc/rc.d/rarpd restart
tftpd(8)
The default configuration of the TFTP server is to run in a
chroot(8)
environment in the
/tftpboot
directory.
Thus, the first order of business is to create this directory:
# mkdir -p /tftpboot
Next, edit
/etc/inetd.conf
and uncomment the line with the TFTP daemon:
tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot
Now, restart
inetd(8)
.
If the server is running
NetBSD1.5
or later, you can achieve this with:
# /etc/rc.d/inetd restart
Now, you need to copy the bootloader for your sparc machine to
/tftpboot
.
Get
boot.net
from the
installation/netboot
directory of the distribution.
# cp boot.net /tftpboot
Now, you need to link
boot.net
to the filename that your sparc will look for.
It will look for a filename composed of the machine's IP address
(in hexadecimal) followed by the machine's architecture,
separated by a period.
For example, a sun4c machine which has been assigned IP address
192.168.1.10, will make a TFTP request for
C0A8010A.SUN4C
.
You can use
bc(1)
to help calculate the filename:
# bc
obase=16
192
C0
168
A8
1
1
10
A
quit
# cd /tftpboot
# ln -s boot.net C0A8010A.SUN4C
Just to be sure, let's make everything readable.
# chmod -R a+rX /tftpboot
Sometimes, the
arp(8)
table gets messed up, and the TFTP server can't communicate with the
client.
In this case, it will write a log message (via
syslogd(8)
)
to
/var/log/messages
saying:
`tftpd: write: Host is down
'.
If this is the case, you may need to force the server to map your client's
ethernet address to its IP address:
# arp -s client CC:CC:CC:CC:CC:CC
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
NetBSD1.5
or later, 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.
Use
binary/kernel/netbsd-GENERIC.gz
).
# gunzip netbsd-GENERIC.gz
# mv netbsd-GENERIC /export/client/root/netbsd
If you are netbooting the installer, copy the distribution files to
the client's root directory and extract the tools from
installation/netboot/rootfs.tgz
.
# cp *tgz /export/client/root
# cd /export/client/root
# tar -xpzf rootfs.tgz
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. http://www.netbsd.org/Documentation/network/netboot/nfs.html
# 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
:
dhcpd=YES dhcpd_flags="-q"
rarpd=YES rarpd_flags="-a"
nfs_server=YES # enable server daemons
mountd=YES
rpcbind=YES rpcbind_flags="-l" # -l logs libwrap
Also, you'll need to make sure the
tftpd
line in
/etc/inetd.conf
remains uncommented.
Now, netboot your Sparc from the server by entering the appropriate boot command at the monitor prompt. Depending on the PROM version in your machine, this command takes one of the following forms:
> b le()netbsd
ok b le()netbsd
ok boot net netbsd
After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section Running the installation scripts. below.
Get the tape images
(installation/tape/tapefile1.gz
and installation/tape/tapefile2
)
and transfer them to a tape.
Make sure you use the
`no rewind scsi tape'
device.
Run the following commands:
# gunzip tapefile1.gz
# mt -f /dev/nrst0 rew
# dd if=tapefile1 of=/dev/nrst0 bs=4k
# dd if=tapefile2 of=/dev/nrst0 bs=4k
Now you can transfer the
NetBSD1.6.
distribution sets from
(binary/sets
)
to the tape by using a series of additional
# dd if=<aset>.tgz of=/dev/nrst0 bs=4k
Insert the tape into your Sparc's tapestation. Boot the installer by typing the appropriate command at the PROM prompt:
> b st()
ok boot st()
ok boot tape
After the initial probe messages you'll be asked to confirm the tape device and tape file number containing the installation tools. Then, proceed to the section Running the installation scripts. below.
If you're using a terminal device connected to a serial port, choose a terminal type appropriate for that device, e.g. vt100 or vt200.
Next, you will be presented with a choice of two installation methods: a new full-screen sysinst program, or the traditional script-based miniroot program. The sysinst program is easier to use, but the miniroot program is more flexible. Both of these installation methods will follow the same set of procedures and will fully install NetBSD on your Sparc.
You will frequently be asked for confirmation before the system proceeds with each phase of the installation process.
Occasionally, you will have to provide a piece of information such as the
name of the disk you want to install on, partitioning information,
or IP addresses and domain names you want to assign.
If your system has
more than one disk, you may want to look at the output of the
dmesg(8)
command to see how your disks have been identified by the kernel.
The installation script goes through the following phases:
Now try a reboot. Initially we'd suggest you boot sd()netbsd -bs, then try multiuser after that. If you boot single-user the NetBSD incantation to make the root file system writable is
# mount -u /dev/sd0a /
Your PROM might have been setup to instruct the boot program to load
a file called
vmunix
.
On OpenBoot PROM systems you can change it to load
netbsd
instead using the following commands:
ok setenv boot-from sd(0,0,0)netbsd
ok setenv boot-file netbsd
ok setenv boot-device disk:a
Congratulations,
you have successfully installed
NetBSD1.6.
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, with the most important ones 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
sun
for a local console, or whatever is appropriate for your serial
console (some systems display garbage with a
sun
terminal type, you may need to use
sun-ss5)
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)
.
If your
/usr
directory is on a separate partition and you do not know how to use
ed,
you will have to mount your
/usr
partition to gain access to
ex
or
vi.
Do the following:
#
mount /usr
#
export TERM=sun
If you have
/var
on a separate partition, you need to repeat that step for it.
After that, you can edit
/etc/rc.conf
with
vi(1)
.
When you have finished, type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that need to be set in
/etc/rc.conf
for a networked environment are
hostname
and possibly
defaultroute,
furthermore add an
ifconfig_int
for your
<int>
network interface,
along the lines of
ifconfig_le0="inet
123.45.67.89
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.
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.
If you're using the machine in a networked environment,
you should create an account for yourself (see below) and protect it and the
``root''
account with good passwords.
Unless you have connected an unusual terminal device as the console
you can just press
RETURN
when it prompts for
Terminal
type?
[...]
.
Use the
useradd(8)
command to add accounts to your system;
do not
edit
/etc/passwd
directly.
See
useradd(8)
for more information on how to add a new user to the system.
If you have installed the X Window System, look at the files in
/usr/X11R6/lib/X11/doc
for information.
Don't forget to add
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
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. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstallation), both from source and precompiled binaries.
1.6/sparc/All
subdir.
You can install them with the following commands:
# PKG_PATH=ftp://ftp.netbsd.org/pub/NetBSD/packages/1.6/sparc/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v apache # pkg_add -v perl ...
The above commands will install the tcsh shell, the Apache web server and the perl programming language as well as all the packages they depend on.
/usr/pkgsrc
(though other locations work fine), with the commands:
#
mkdir /usr/pkgsrc
#
( cd /usr/pkgsrc ; tar -zxpf - ) < pkgsrc.tar.gz
After extracting, then see the
README
file in the extraction directory (e.g.
/usr/pkgsrc/README
)
for more information.
/etc/mail/aliases
to forward root mail to the right place.
Don't forget to run
newaliases(1)
afterwards.
/etc/mail/sendmail.cf
file will almost definitely need to be adjusted;
files aiding in this can be found in
/usr/share/sendmail
.
See the
README
file there for more information.
/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.
The upgrade to NetBSD1.6 is a binary upgrade; it can be quite difficult to update the system from an earlier version by recompiling from source, primarily due to interdependencies in the various components.
To do the upgrade, you must boot from the installer kernel using one of
the methods described above.
You must also have at least the
base
and
kern
binary distribution sets available, so that you can upgrade with them,
using one of the upgrade methods described above.
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.
If you have a few megabytes free on each of your root
(/
)
and
/usr
partitions, you should have enough space.
Since upgrading involves replacing the boot blocks on your NetBSD partition, the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to back up any important data on your disk, whether on the NetBSD partition or on another operating system's partition, before beginning the upgrade process.
The upgrade procedure using the
sysinst
tool is similar to an installation, but without the hard disk partitioning.
The original
/etc
directory is renamed to
/etc.old
,
and no attempt is made to merge any of the previous configuration into
the new system except that the previous
/etc/fstab
file is copied into the new configuration.
Getting the binary
sets is done in the same manner as the installation procedure;
refer to the installation part of the document
for how to do this.
Also, some sanity checks are done, i.e.
file systems are checked before unpacking the sets.
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD1.6
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
/dev
.
If you've changed the contents of
/dev
by hand, you will need to be careful about this, but if
not, you can just cd into
/dev
,
and run the command:
#
sh MAKEDEV all
Finally, you will want to delete old binaries that were part of the version of NetBSD that you upgraded from and have since been removed from the NetBSD distribution.
NetBSD/sparc
has switched its executable format from the old a.out format
to ELF, the now more commonly used and supported format.
Your old binaries will continue to work just fine.
The installation procedure
will try to take the necessary steps to accomplish this.
The most important step is to move the old a.out shared libraries in
/usr/lib
and
/usr/X11R6/lib
(if X was installed) to
/emul/aout
,
where they will be automatically found if an older a.out binary
is executed.
sysinst
will use an existing
/emul
and / or
/emul/aout
directory if available, and will create it (as a symbolic link to
/usr/aout
)
if necessary.
If you already had a
/emul
directory, or a symbolic link by that name,
sysinst
should rename it and tell you about it.
The network bootstrap
/usr/mdec/boot.net
and GENERIC and INSTALL kernels now try DHCP/BOOTP before falling back
to bootparams.
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD1.6.
mkdir /tmp/upgrade
cd /tmp/upgrade
pax -zrpe -f /path/to/etc.tgz
./etc/postinstall -s `pwd` check
./etc/postinstall -s `pwd` 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/rc.d/NETWORK
and
/etc/rc.d/gated
.
rc.conf(5)
entries are now obsolete:
amd_master
,
ip6forwarding
,
defcorename
,
and
nfsiod_flags
.
critical_filesystems_beforenet
has been replaced by
critical_filesystems_local
.
critical_filesystems
has been replaced by
critical_filesystems_remote
.
ssh(1)
and
sshd(8)
were moved from
/etc
to
/etc/ssh
,
including
ssh_known_hosts*
files and the
host key files
ssh_host*_key*
.
/etc/ssh.conf
was renamed to
/etc/ssh/ssh_config
,
and
/etc/sshd.conf
was renamed to
/etc/ssh/sshd_config
.
wscons.conf(5)
are now obsolete.
The following issues need to be resolved manually:
postfix(8)
configuration files require upgrading.
cd /usr/share/examples/postfix
cp post-install postfix-files postfix-script /etc/postfix
postfix check
/etc/ifconfig.de*
to
/etc/ifconfig.tlp*
,
renaming of
rc.conf(5)
entries
ifconfig_de*
to
ifconfig_tlp*
,
and the reconfiguration of files such as
/etc/dhclient.conf
and
/etc/ipf.conf
.
/etc/rc
modified to use
/etc/rc.d/*
Prior to
NetBSD1.5,
/etc/rc
was a traditional
BSD
style monolithic file; each discrete program or substem from
/etc/rc
and
/etc/netstart
has been moved into separate scripts in
/etc/rc.d/
.
At system startup,
/etc/rc
uses
rcorder(8)
to build a dependency list of the files in
/etc/rc.d
and then executes each script in turn with an argument of
`start'.
Many
rc.d
scripts won't start unless the appropriate
rc.conf(5)
entry in
/etc/rc.conf
is set to
`YES.'
At system shutdown,
/etc/rc.shutdown
uses
rcorder(8)
to build a dependency list of the files in
/etc/rc.d
that have a
``KEYWORD: shutdown''
line, reverses the resulting list, and then executes each script in turn
with an argument of
`stop'.
The following scripts support a specific shutdown method:
cron
,
inetd
,
local
,
and
xdm
.
Local and third-party scripts may be installed into
/etc/rc.d
as necessary.
Refer to the other scripts in that directory and
rc(8)
for more information on implementing
rc.d
scripts.
named(8)
leaks version information.
Previous releases of
NetBSD
disabled a feature of
named(8)
where the version number of the server could be determined by remote clients.
This feature has not been disabled in
NetBSD1.5,
because there is a
named.conf(5)
option to change the version string:
option {
version "newstring";
};
sysctl(8)
was moved from
/usr/sbin/sysctl
to
/sbin/sysctl
.
If you have hardcoded references to the full pathname
(in shell scripts, for example)
please be sure to update those.
sendmail(8)
configuration file pathname changed.
Due to
sendmail(8)
upgrade from 8.9.x to 8.10.x,
/etc/sendmail.cf
is moved to
/etc/mail/sendmail.cf
.
Also, the default
sendmail.cf(5)
refers different pathnames than before.
For example,
/etc/aliases
is now located at
/etc/mail/aliases
,
/etc/sendmail.cw
is now called
/etc/mail/local-host-names
,
and so forth.
If you have customized
sendmail.cf(5)
and friends, you will need to move the files to the new locations.
See
/usr/share/sendmail/README
for more information.
Documentation is available if you first install the manual
distribution set.
Traditionally, the
``man pages''
(documentation) are denoted by
`name(section)
'.
Some examples of this are
intro(1)
,
man(1)
,
apropros(1)
,
passwd(1)
,
and
passwd(5)
.
The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8.
The man command is used to view the documentation on a topic, and is started by entering man[ section] topic. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the 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.
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.
Additionally, bug reports can be sent by mail to:
netbsd-bugs@netbsd.org.
Use of
send-pr(1)
is encouraged, however, because bugs reported with it
are entered into the
NetBSD
bugs database, and thus can't slip through
the cracks.
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-help@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 ongoing work on BSD systems, support, and encouragement.
Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek
for answering lots of questions, fixing bugs, and doing the various work they've done.
Steve Allen Jason Birnschein Mason Loring Bliss Jason Brazile Mark Brinicombe David Brownlee Simon Burge Dave Burgess Ralph Campbell Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Scott Ellis Hubert Feyrer Castor Fu Greg Gingerich William Gnadt Michael Graff Guenther Grau Ross Harvey Charles M. Hannum Michael L. Hitch Kenneth Alan Hornstein Jordan K. Hubbard Søren Jørvang Scott Kaplan Noah M. Keiserman Harald Koerfgen John Kohl Chris Legrow Ted Lemon Norman R. McBride Neil J. McRae Perry E. Metzger Luke Mewburn Toru Nishimura Herb Peyerl Mike Price Dave Rand Michael Richardson Heiko W. Rupp Brad Salai Chuck Silvers Thor Lancelot Simon Bill Sommerfeld Paul Southworth Eric and Rosemary Spahr Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow Krister Walfridsson Rob Windsor Jim Wise Reinoud Zandijk Christos Zoulas
AboveNet Communications, Inc. Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Brains Corporation, Japan Canada Connect Corporation Co-operative Research Centre for Enterprise Distributed Systems Technology Demon Internet, UK Digital Equipment Corporation Distributed Processing Technology Easynet, UK Free Hardware Foundation Innovation Development Enterprises of America Internet Software Consortium MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center Piermont Information Systems Inc. Precedence Technologies Ltd Salient Systems Inc. VMC Harald Frank, Germany Warped Communications, Inc. Whitecross Database Systems Ltd.
(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:
This product includes software developed by the University of
California, Berkeley and its contributors.