About this Document............................................2
Dedication.....................................................2
What is NetBSD?................................................2
Upgrade path to NetBSD 1.6.2...................................3
Changes Between The NetBSD 1.6.1 and 1.6.2 Releases............3
Kernel......................................................3
Networking..................................................4
Security....................................................4
System administration and user tools........................4
Miscellaneous...............................................5
acorn32 specific............................................5
Changes Between The NetBSD 1.6 and 1.6.1 Releases..............5
Kernel......................................................5
Networking..................................................5
File system.................................................6
Security....................................................6
System administration and user tools........................6
Miscellaneous...............................................7
Changes Between The NetBSD 1.5 and 1.6 Releases................7
Kernel......................................................7
Networking..................................................8
File system.................................................8
Security....................................................9
System administration and user tools........................9
Miscellaneous...............................................9
The Future of NetBSD..........................................11
Sources of NetBSD.............................................11
NetBSD 1.6.2 Release Contents.................................11
NetBSD/acorn32 subdirectory structure......................13
Binary distribution sets...................................13
NetBSD/acorn32 System Requirements and Supported Devices......15
Supported devices..........................................15
Unsupported devices........................................16
Getting the NetBSD System on to Useful Media..................16
Preparing your System for NetBSD installation.................18
Software requirements......................................19
Preliminary steps..........................................20
Preparing your hard disk...................................20
Sharing your device........................................20
Using a whole device for NetBSD............................23
Running bb_riscbsd.........................................23
Booting....................................................23
Configuring the !BtNetBSD bootloader before installation...24
Running !BtNetBSD..........................................24
Configuring !BtNetBSD after installation...................24
Installing the NetBSD System..................................24
Running the sysinst installation program...................24
Introduction............................................24
Possible PCMCIA issues..................................24
General.................................................25
Quick install...........................................25
Booting NetBSD..........................................26
Network configuration...................................27
Installation drive selection and parameters.............27
Partitioning the disk...................................27
Preparing your hard disk................................28
Getting the distribution sets...........................28
Installation using ftp..................................28
Installation using NFS..................................28
Installation from CD-ROM................................29
Installation from an unmounted file system..............29
Installation from a local directory.....................29
Extracting the distribution sets........................29
Finalizing your installation............................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.............................34
Administrivia.................................................35
Thanks go to..................................................35
We are........................................................38
Legal Mumbo-Jumbo.............................................42
The End.......................................................44
This document describes the installation procedure for
NetBSD1.6.2
on the
acorn32
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.
The NetBSD Foundation would like to dedicate the NetBSD 1.6.2 release to the memory of Erik Reid, who went missing and is presumed dead in a sailing accident on 18 February 2004. Erik's contributions to NetBSD included work on support for SGI MIPS R4000, integrating XFree86 Direct Rendering Interface (DRI), and managing the build lab. His death came as a shock, and he will be greatly missed by all of us. May he rest in peace.
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.2 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.2 is an upgrade of NetBSD1.6.1 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.2 release provides numerous significant functional enhancements, including support for many new devices, integration of hundreds of bug fixes, patches and updates to 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 nine months of development that went into the NetBSD1.6.2 release. Some highlights include:
pciide(4)
,
make Promise controllers do DMA with large disks
requiring 48-bit LBA drives.
pciide(4)
.
mlx(4)
stability improved.
pciide(4)
.
userconf(4)
for more information.
wdc(4)
to work with pre-ATA drives.
rtk(4)
multicast problem fixed.
fxp(4)
support yet a few more chip variants.
tulip(4)
driver fixed so that the DEC Alpha PWS no longer panics.
bce(4)
driver added for Broadcom BCM4401 chipset, as seen in recent
Dell laptops.
vi(1)
triggered by an error was fixed.
scsictl(8)
now supports a few new commands.
And of course there have also been innumerable bug fixes and other miscellaneous enhancements. You can look for this trend to continue.
The NetBSD1.6.1 release provides numerous significant functional enhancements, including support for many new devices, integration of hundreds of bug fixes, patches and updates to 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 seven months of development that went into the NetBSD1.6.1 release. Some highlights include:
aac(4)
.
audio(4)
,
dpt(4)
,
eap(4)
,
emuxki(4)
,
iop(4)
,
siop(4)
and
umass(4)
.
pciide(4)
support has been extended to support Promise
Ultra133TX2, Promise Ultra133TX2v2, HighPoint HPT372, Ultra/133
on VIA VT8233A, and the VIA VT8235.
tlp(4)
and
xi(4)
drivers.
pcn(4)
driver.
rtk(4)
now supports Planex FNW-3603 cardbus ethernet card.
ex(4)
multicast handling has been fixed.
wi(4)
now supports Netgear MA401RA card.
wm(4)
now supports more chip variants.
aue(4)
now supports SMC 2206USB/ETH EZ Connect adapter.
sip(4)
now has some Tx interrupt mitigation code, and improved
support for 64-bit DP83820 cards.
fxp(4)
driver has been improved for better support of
certain i82558 revisions, and has been fixed to recognize
some more chips.
bge(4)
driver.
ftpd(8)
interoperability bugs have been fixed.
mopd(8)
fixes to make the program load correctly.
pppoe(4)
bugs have been fixed.
ffs(4)
soft dependencies handling have been incorporated.
amd(8)
.
fsck(8)
bugs have been fixed.
named(8)
and the libc resolver.
file(1)
have been fixed.
tar(1)
has been fixed.
user(8)
has seen several fixes, some of them related to MD5 and
blowfish password encryption support.
And of course there have also been innumerable bug fixes and other miscellaneous enhancements. You can look for this trend to continue.
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.2 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.2
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.
This is the fourth major release of NetBSD for the acorn32 , although it was known as NetBSD/arm32 prior to NetBSD1.6.
NetBSD1.6.2 on acorn32 is, as usual, also fully backward compatible with old NetBSD acorn32 binaries, so you don't need to recompile all your local programs provided you set the appropriate binary compatibility options in your kernel configuration.
New port-specific features include:
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.2 release is organized as follows:
.../NetBSD-1.6.2/
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.2
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.
acorn32
subdirectory of the distribution:
.../NetBSD-1.6.2/acorn32/
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/
misc/
acorn32/binary/sets
subdirectory
of the
NetBSD1.6.2
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 acorn32 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.
NetBSD/acorn32 1.6.2 runs on Acorn systems with ARM6 or later processors, with or without FPU coprocessor. The minimal configuration is said to require 8 MB of RAM and 50 MB of disk space, though we do not know of anyone running with a system quite this minimal today. To install the entire system requires much more disk space (the unpacked binary distribution, without sources, requires at least 65 MB without counting space needed for swap space, etc), and to run X or compile the system, more RAM is recommended. (8 MB of RAM will actually allow you to run X and/or compile, but it won't be speedy. Note that until you have around 16 MB of RAM, getting more RAM is more important than getting a faster CPU.)
Drivers for hardware marked with ``[*]'' are not present in installation kernels.
Support for some devices is limited to particular kernels. eg there is no SA110 support in A7000 kernels.
Drivers are planned for some of the above devices.
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.2
#
cd acorn32/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.
Please note that the
/dev
on the floppy used for upgrades only knows about
wd0
,
wd1
,
sd0
,
sd1
,
and
sd2
.
If you have more than two IDE drives or more than three SCSI drives, you
should take care not to place the sets on the high-numbered drives.
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 and foremost, before beginning the installation process, make sure you have a reliable backup of any data on your hard disk that you wish to keep. Repartitioning your hard disk is an excellent way to destroy important data.
installation/misc/gzip_ff8
(!) which is a mirror a version
that Laurent Domisse has patched to work on SA.
This is also available from:
http://www.users.dircon.co.uk/~arcangel/files/index.html.
Just set the type of the file to
`ff8'.
RiscPC/A7000(+)/NC's : INSTALL kernel
BtNetBSD.tar.gz
or
BtNetBSD.zip
as found in the
installation/misc
directory.
(This should be pre-extracted if you're installing from CD-ROM).
Settype
file in the
BtNetBSD
directory to
`Obey'
and run it.
This will make the files RISC OS typed correctly.
This is also explained in a bit more detail in the enclosed
README
file.
You will have to decide which device you wish to install NetBSD on. You will also have to decide whether you want to split the device between one or more RiscOS Discs and NetBSD or dedicate a whole Device for NetBSD.
In making this decision you should consider the possibility that if NetBSD is incorrectly configured on a shared device then your shared data is at risk.
It is still recommended that if you decide to dedicate a device to NetBSD that you set aside a small RISC OS partition at the beginning of the device. This is a useful place to store the RiscOS side of NetBSD, and will make the use of UnixFS easier to configure. If you do decide to create a minimal RiscOS partition at the beginning of the device, a size of 10-20 MB is recommended (some partitioning software has problems with partitions smaller than this).
The point is that you will have to repartition your device to make room for a separate partition after the RISC OS one for NetBSD. This means backing up your device, re-partitioning it and then copying all the data back afterwards. We recommend that you only copy the needed data back and put off installing the rest until you have NetBSD up and running. This way you will save yourself a lot of work if something goes wrong and you have to start all over again.
Use !HForm for this interface.
This is a program that is delivered with your computer and is located in the
Utilities
directory on your
hard disk.
With this software you only have the possibility of using one partition for RISC OS, so you have to set the rest aside for NetBSD.
Use this procedure to set up your device:
2.1.2 Cumana SCSI-2 card
It is recommended that you use a newer version of !SCSIMgr (newer than v1.55) since this will be easier to use when you want to leave part of the device unused by RISC OS. You should check for the latest version of this software at the following URL: http://www.cumana.demon.co.uk
You need to create one or more RISC OS partitions, and you do it in in the following way:
2.1.3 Alsystems Power-tec SCSI-2 card
You must use the !PowerMgr program to partition the device.
The RISC OS partitions should be called `RiscOs:', and the NetBSD one should be called `Empty:'.
Here is the procedure you should use:
2.1.4 Acorn SCSI card
You can only have one RISC OS partition with this card. The rest has to be set aside for NetBSD.
This card does not have a friendly WIMP-based interface on the SCSI
management program, but the command line version is very good.
You should run this in a task window (press
CTRL-F12
):
You will get the following prompt:*dir
location_of_scsidm
*scsidm
scsidm>
Include
RISCiX
partitions?
Do you really want to section device
no?
Go to the section on running bb_riscbsd.
2.1.5 Other interfaces
It may not be possible to partition devices on other interface. If you are using a different interface you have 2 options:
As a safety precaution NetBSD/acorn32 looks for a filecore bootblock at the beginning of any device it labels. If it finds one and it looks as though it is in use then NetBSD/acorn32 will not touch it.
Because of this, if you've ever used your device for RiscOS, you will need to invalidate this bootblock.
To do this you need to:
Ensure that this device is now not configured for RiscOS.
You are now ready to boot NetBSD and continue the installation.
When you run this program, you will first be asked whether you are installing to an ADFS drive or a SCSI drive. You can just press `A' or `S' respectively. (The bb_riscbsd program assumes that you are using a non-Acorn SCSI card, so if you are using an Acorn card, then you may have to edit this program and replace `SCSI_DiscOp' with `SCSIFS_DiscOp'.)
Then you will be asked which Disc you want to install NetBSD on. This must be the first Disc on the device. bb_riscbsd will now scrutinize the device and see how it has been laid out.
It will then tell you how much of the device is occupied by RiscOS in cylinders, and you will then be asked for the NetBSD starting cylinder. Normally you should just enter the number given to you since the RISC OS starting cylinder is 0 and therefore the last cylinder in use is one less than the figure given. If no figure is displayed, then your partitioning software failed to fill in the bootblock completely (it doesn't have to do this for you but most do) or you selected the wrong device. If you are convinced that this is the correct device then you must calculate a cylinder offset using the numbers noted down during partitioning (if it is not a whole number always round up, you might waste a little of the device but it'll be safer).
Make a note of this number.
bb_riscbsd will make a backup of the original bootblock, but it can be non-trivial to put it back.
Now that your device is ready for the installation you need to
unpack the bootloader archive.
Pick either
BtNetBSD.tgz
or
BtNetBSD.zip
depending on which type of archive you can extract easiest.
(If you're installing from CD-ROM then this should be unpacked already),
copy the directory to your hard disk.
In the archive you'll find the tools
mentioned in this document as well as the bootloader
!BtNetBSD
itself.
!BtNetBSD
application and edit the
fastboot
file to specify
the installation kernel location; an example is already given.
You can also set other details like tweaking with the amount of memory in
the WimpSlot of the bootloader when this is too much.
Remember however that this shouldn't be set too low for it can crash
the bootloader.
When you think you've filled in the proper details save the file again
and proceed.
Double click on the !BtNetBSD icon (or the !Run file in it) to start it up.
NetBSD should now start to boot, install NetBSD as per the NetBSD installation notes.
When you finish the installation you can restarted the computer as instructed.
Open the
!BtNetBSD
application again and edit the
fastboot
file again to fill in the normal kernel name.
Specify the device
NetBSDNetBSD
should be looking for its kernel in.
This is the
`Run
Set the kernel as
Save the file and run !BtNetBSD again (see above).
Finally, when you are happy with your
NetBSD
installation, do whatever
is necessary to restore order to the partition you took space away from.
This will most likely involve restoring files, but might involve some
other
``house-work''.
Your hard disk is now prepared to have
NetBSD
installed on it, and you should proceed with the installation instructions.
Using
sysinst,
installing
NetBSD
is a relatively easy process.
You still should read this document and have it in hand when doing the
installation process.
This document tries to be a good guideline for the installation and as such
covers many details for the sake of completeness.
Do not let this discourage you; the install program is not hard
to use.
Machines with
PCMCIA
slots may have problems during installation.
With the improvements of the
PCMCIA
code in this release, this will not happen very frequently.
If you do not have
PCMCIA
on your machine
(PCMCIA
is only really used on laptop machines),
you can skip this section, and ignore the
``[PCMCIA]''
notes.
If you do have
PCMCIA
in your machine, you can safely ignore this section and the
``[PCMCIA]''
the first time, as you are likely to not have problems.
Should troubles
occur during floppy boot, they may be
PCMCIA
specific.
You should then re-read this section and try again,
following the instructions in the
``[PCMCIA]''
notes.
This section explains how to work around the installation problem.
The kernel keeps careful track of what interrupts
and I/O ports are in use during autoconfiguration.
It then allows the
PCMCIA
devices to pick unused interrupts and I/O ports.
Unfortunately, the
For example, suppose your laptop has a
soundblaster device built in; the
As of
NetBSD1.5,
the kernel attempts to probe for available interrupts that are
usable by the
PCIC
(PCMCIA
interrupt controller).
Assuming that this functions correctly,
it should alleviate interrupt conflicts;
however, I/O port conflicts are still possible.
This problem will impact some, but not all, users of
PCMCIA.
If this problem is affecting you, watch the
``[PCMCIA]''
notes that will appear in this document.
The following is a walk-through of the steps you will take while
getting
NetBSD
installed on your hard disk.
sysinst
is a menu driven
installation system that allows for some freedom in doing the
installation.
Sometimes, questions will be asked and in many cases
the default answer will be displayed in brackets
(``[ ]'')
after the question.
If you wish to stop the installation, you may press
First, let's describe a quick install.
The other sections of this document go into the installation procedure in more
detail, but you may find that you do not need this.
If you want detailed instructions, skip to the next section.
This section describes a basic installation, using a CD-ROM install as
an example.
Boot your machine.
The boot loader will start, and will print a countdown and begin booting.
If the boot loader messages do not appear in a reasonable
amount of time, you either have a bad boot floppy or a
hardware problem.
Try writing the install floppy image to
a different disk, and using that.
It will take a while to load the kernel
from the floppy,
probably around a minute or so, then, the kernel boot messages
will be displayed.
This may take a little while also, as
NetBSD
will be probing your system to discover which hardware devices are
installed.
The most important thing to know is that
Note that once the system has finished booting, you need not
leave the floppy in the disk drive.
Once
NetBSD
has booted and printed all the boot messages,
you will be presented with a welcome message and a main menu.
It will also include instructions for using the menus.
If you will not use network operation during the installation,
but you do want your machine to be configured for networking once
it is installed, you should first go to the
Utility menu,
and select the
Configure network
option.
If you only want to temporarily
use networking during the installation, you can specify these
parameters later.
If you are not using the Domain Name System (DNS),
you can give an empty response in reply to answers relating to
this.
To start the
installation,
select
Install NetBSD to hard disk
from the main menu.
The first thing is to identify the disk on which you want to
install
NetBSD.
sysinst
will report a list of disks it finds
and ask you for your selection.
Depending on how many disks are found, you may get a different message.
You should see disk names like
You will be asked if you want to use the entire disk or
only part of the disk.
If you decide to use the entire disk for
NetBSD,
it will be checked if there are already other
systems present on the disk, and you will be asked to confirm
whether you want to overwrite these.
The partition table of the
NetBSD
part of a disk is called a
disklabel.
There are 4 layouts for the
NetBSD
part of the disk that you can pick from:
Standard, Standard with X, Custom
and
Use Existing.
The first two use a set of default values (that you can change)
suitable for a normal installation, possibly including X.
With the
Custom
option you can specify everything yourself.
The last option uses the partition info already present on the disk.
You will be presented with the current layout of the
NetBSD
disklabel, and given a chance to change it.
For each partition, you can set the type, offset and size,
block and fragment size, and the mount point.
The type that
NetBSD
uses for normal file storage is called
4.2BSD.
A swap partition has a special type called
swap.
Some partitions in the disklabel have a fixed purpose.
You will then be asked to name your disk's disklabel.
The default response is
``mydisk''.
For most purposes this will be OK.
If you choose to name it something different, make sure the name
is a single word and contains no special characters.
You don't need to remember this name.
You are now at the point of no return.
Nothing has been
written to your disk yet, but if you confirm that you want to
install
NetBSD,
your hard drive will be modified.
If you are sure you want to proceed, enter
The install program will now label your disk and make the file
systems you specified.
The file systems will be initialized to contain
NetBSD
bootstrapping binaries and configuration files.
You will see messages on your screen from the various
NetBSD
disk preparation tools that are running.
There should be no errors in this section of the installation.
If there are, restart from the beginning of the installation process.
Otherwise, you can continue the installation program
after pressing the return key.
The
NetBSD
distribution consists of a number of
sets,
that come in the form of gzipped tarfiles.
A few sets must be installed for a working system, others are optional.
At this point of the installation, you will be presented with a menu
which enables you to choose from one of the following methods
of installing the sets.
Some of these methods will first load the sets on your hard disk,
others will extract the sets directly.
For all these methods, the first step is making the sets
available for extraction, and then do the actual installation.
The sets can be made available in a few different ways.
The following sections describe each of those methods.
After reading the one about the method you will be using, you
can continue to section labeled
`Extracting the distribution sets'.
To be able to install using ftp, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
to provide some data, like IP address, hostname, etc.
If you do not have name service set up for the machine that you
are installing on, you can just press
You will also be asked to specify the host that you want
to transfer the sets from, the directory on that host,
the account name and password used to log into that
host using ftp, and optionally a proxy server to use.
If you did not set up DNS when answering
the questions to configure networking, you will need to
specify an IP address instead of a hostname for the ftp
server.
sysinst
will proceed to transfer all the default set files
from the remote site to your hard disk.
To be able to install using NFS, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
to provide some data, like IP address, hostname, etc.
If you do not have name service set up for the machine that you
are installing on, you can just press
You will also be asked to specify the host that you want
to transfer the sets from, and the directory on that host
that the files are in.
This directory should be mountable by the machine you are installing on,
i.e. correctly exported to your machine.
If you did not set up DNS when answering the questions to
configure networking, you will need to specify an IP address
instead of a hostname for the NFS server.
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM player
(usually
sysinst
will then check if the files are indeed available
in the specified location, and proceed to the actual
extraction of the sets.
In order to install from a local file system, you will
need to specify the device that the file system resides
on
(for example
This option assumes that you have already done some preparation
yourself.
The sets should be located in a directory on a
file system that is already accessible.
sysinst
will ask you
for the name of this directory.
After the install sets containing the
NetBSD
distribution
have been made available, you can either extract all the
sets (a full installation), or only extract sets that
you have selected.
In the latter case, you will be shown the currently selected sets,
and given the opportunity to select the sets you want.
Some sets always need to be installed
(kern, base)
and
etc
they will not be shown in this selection menu.
Before extraction begins, you can elect to watch the files being
extracted; the name of each file that is extracted will be shown.
This can slow down the installation process considerably, especially
on machines with slow graphics consoles or serial consoles.
After all the files have been extracted,
all the necessary device node files will be created.
If you have already configured networking, you will be asked if you want to
use this configuration for normal operation.
If so, these values will be installed in the network configuration files.
The next menu will allow you to select the time zone that you're in,
to make sure your clock has the right offset from UTC.
Finally you will be asked to select a password encryption algorithm
and can than set a password for the "root" account, to prevent
the machine coming up without access restrictions.
Congratulations, you have successfully installed
NetBSD1.6.2.
You can now reboot the machine, and boot
NetBSD
from harddisk.
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.
If you or the installation software haven't done any configuration of
and with the root file system
(
If your
If you have
Other values that need to be set in
or, if you have
myname.my.dom
in
To enable proper hostname resolution, you will also want to add an
Other files in
After reboot, you can log in as
Use the
If you have installed the X Window System, look at the files in
Don't forget to add
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.
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.
After extracting, then see the
is likely to give you more information on these files.
The upgrade to
NetBSD1.6.2
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 have the boot floppy
available.
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
(
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
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD1.6.2
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
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.
Users upgrading from previous versions of
NetBSD
may wish to bear the
following problems and compatibility issues in mind when upgrading to
NetBSD1.6.2.
Issues fixed by
postinstall:
The following issues need to be resolved manually:
Prior to
NetBSD1.5,
At system startup,
At system shutdown,
Local and third-party scripts may be installed into
Previous releases of
NetBSD
disabled a feature of
Due to
Documentation is available if you first install the manual
distribution set.
Traditionally, the
``man pages''
(documentation) are denoted by
`
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
to read the documentation for
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
Use of
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.
for their ongoing work on
BSD
systems, support, and encouragement.
for answering lots of questions, fixing bugs, and doing the various work
they've done.
(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.
UnixFS:$.netbsd
.
Installing the NetBSD System
Running the sysinst installation program
INSTALL
kernel may not detect all devices in your system.
This may be because the
INSTALL
kernel only supports the minimum set of devices to install
NetBSD
on your system, or it may be that
NetBSD
does not have support for the device causing the conflict.
INSTALL
kernel has no sound support.
The
PCMCIA
code might allocate your soundblaster's
IRQ
and I/O ports to
PCMCIA
devices, causing them not to work, or to lock up the system.
This is especially bad if one of the devices in question is your ethernet card.
CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch by running the
/sysinst
program from the command prompt.
It is not necessary to reboot.
.***********************************************.
* NetBSD-1.6 Install System *
* *
*>a: Install NetBSD to hard disk *
* b: Upgrade NetBSD on a hard disk *
* c: Re-install sets or install additional sets *
* d: Reboot the computer *
* e: Utility menu *
* x: Exit Install System *
.***********************************************.
root
,
and set a password for that account.
You are also advised to edit the file
/etc/rc.conf
to match your system needs.
/usr/X11R6/lib/X11/doc
.
Further information can be found on
http://www.xfree86.org/.
wd0
is
NetBSD's
name for your first IDE disk,
wd1
the second, etc.
sd0
is your first SCSI disk,
sd1
the second, etc.
sd0
or
sd1
.
a
/
)
b
c
d-h
e
is the partition mounted on
/usr
,
but this is historical practice and not a fixed value.
yes
at the prompt.
RETURN
in answer to these questions, and DNS will not be used.
RETURN
in answer to these questions, and DNS will not be used.
cd0
),
and the directory name on the CD-ROM where the distribution files are.
sd1e
)
the type of the file system,
and the directory on the specified file system where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
Post installation steps
/etc/rc.conf
/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.
/
)
mounted read-only.
When the system asks you to choose a shell, simply press
RETURN
to get to a
/bin/sh
prompt.
If you are asked for a terminal type, respond with
vt220
(or whatever is appropriate for your terminal type)
and press
RETURN
.
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
#
stty erase '^h'
#
stty erase '^?'
At this point, you need to configure at least
one file in the
/etc
directory.
You will need to mount your root file system read/write with:
#
/sbin/mount -u -w /
Change to the
/etc
directory and take a look at the
/etc/rc.conf
file.
Modify it to your tastes, making sure that you set
rc_configured=YES
so that your changes will be enabled and a multi-user boot can
proceed.
Default values for the various programs can be found in
/etc/defaults/rc.conf
,
where some in-line documentation may be found.
More complete documentation can be found in
rc.conf(5)
.
/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=vt220
/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.
/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_de0="inet
123.45.67.89
netmask
255.255.255.0"
/etc/hosts
:
ifconfig_de0="inet
myname.my.dom
netmask
255.255.255.0"
/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.
/etc
that may require modification or setting up include
/etc/mailer.conf
,
/etc/nsswitch.conf
,
and
/etc/wscons.conf
.
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?
[...]
.
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.
/usr/X11R6/lib/X11/doc
for information.
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
1.6.2/acorn32/All
subdir.
You can install them with the following commands:
# PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/1.6.2/acorn32/All
# export PKG_PATH
# pkg_add -v tcsh
# pkg_add -v apache
# pkg_add -v perl
...
/usr/pkgsrc
(though other locations work fine), with the commands:
#
mkdir /usr/pkgsrc
#
( cd /usr/pkgsrc ; tar -zxpf - ) < pkgsrc.tar.gz
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
Upgrading a previously-installed NetBSD System
/
)
and
/usr
partitions, you should have enough space.
/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.
/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
Compatibility Issues With Previous NetBSD Releases
Issues affecting an upgrade from NetBSD 1.5
The following issues can generally be resolved by extracting the
etc
set into a temporary directory and running
postinstall:
mkdir /tmp/upgrade
cd /tmp/upgrade
pax -zrpe -f /path/to/etc.tgz
./etc/postinstall -s `pwd` check
./etc/postinstall -s `pwd` fix
/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.
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
.
Issues affecting an upgrade from NetBSD 1.4 or prior
/etc/rc
modified to use
/etc/rc.d/*
/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/
.
/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.'
/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
.
/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.
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.
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.
Using online NetBSD documentation
name(section)
'.
Some examples of this are
intro(1)
,
man(1)
,
apropros(1)
,
passwd(1)
,
and
passwd(5)
.
#
man passwd
passwd(1)
.
To view the documentation for
passwd(5)
,
enter
#
man 5 passwd
Administrivia
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.
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.
Thanks go to
Keith Bostic
Ralph Campbell
Mike Karels
Marshall Kirk McKusick
Mike Hibler
Rick Macklem
Jan-Simon Pendry
Chris Torek
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
(If you're not on that list and should be, tell us!
We probably were not able to get in touch with you, to verify that you
wanted to be listed.)
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.
We are...
Legal Mumbo-Jumbo
The End