About this Document............................................2
What is NetBSD?................................................2
Changes Between The NetBSD 4.0 release and 4.0.1 update........3
Security Advisories Fixes...................................3
Other Security Fixes........................................3
Networking..................................................4
Libraries...................................................4
Drivers.....................................................4
Miscellaneous...............................................4
Platforms specific..........................................5
Changes Between The NetBSD 3.0 and 4.0 Releases................5
Networking..................................................5
File systems................................................6
Drivers.....................................................6
Platforms...................................................8
Kernel subsystems...........................................9
Security...................................................10
Userland...................................................10
Components removed from NetBSD.............................12
The Future of NetBSD..........................................13
Sources of NetBSD.............................................13
NetBSD 4.0.1 Release Contents.................................13
NetBSD/amiga subdirectory structure........................15
Miniroot file system.......................................15
Binary distribution sets...................................15
NetBSD/amiga System Requirements and Supported Devices........17
Supported devices..........................................17
Getting the NetBSD System on to Useful Media..................19
Preparing your System for NetBSD installation.................21
Preparing your hard disk with HDToolBox....................21
Transferring the miniroot file system......................23
Installing the NetBSD System..................................24
Booting....................................................24
Once your kernel boots.....................................24
Post installation steps.......................................27
Upgrading a previously-installed NetBSD System................29
Once your kernel boots.....................................30
Compatibility Issues With Previous NetBSD Releases............31
Issues affecting an upgrade from NetBSD 2.1 and older......31
Issues affecting an upgrade from NetBSD 3.x releases.......32
Issues with GDB 6.5...........................................33
Using online NetBSD documentation.............................33
Administrivia.................................................34
Thanks go to..................................................34
We are........................................................35
Legal Mumbo-Jumbo.............................................41
The End.......................................................47
This document describes the installation procedure for
NetBSD
4.0.1 on the
amiga
platform.
It is available in four different formats titled
INSTALL.ext,
where
.ext
is one of
.ps, .html, .more,
or .txt:
.ps.html.moremore(1)
and
less(1)
pager utility programs.
This is the format in which the on-line
man
pages are generally presented.
.txtYou are reading the HTML version.
The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the University of California, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on fifty four different system architectures (ports), featuring seventeen machine architectures across fifteen distinct CPU families, and is being ported to more. The NetBSD 4.0.1 release contains complete binary releases for many different system architectures. (A few ports are not fully supported at this time and are thus not part of the binary distribution. Please see the NetBSD web site at http://www.NetBSD.org/ for information on them.)
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code.
NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.
The NetBSD 4.0.1 update is the first security/critical update of the NetBSD 4.0 release branch. This represents a selected subset of fixes deemed critical in nature for stability or security reasons.
These fixes will also appear in future releases (NetBSD 4.1), together with other less-critical fixes and feature enhancements.
The complete list of changes can be found in the CHANGES-4.0.1: ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-4.0.1/CHANGES-4.0.1 file in the top level directory of the NetBSD 4.0.1 release tree.
bzip2(1)
Multiple issues (CVE-2008-1372 and CVE-2005-0953),
has been fixed by upgrading bzip2 to 1.0.5.
strfmon(3)
function (CVE-2008-1391),
has been fixed.
query-source'
statement, which could allow the BIND cache poisoning attack,
has been commented out in the default
named.conf(5)
file.
racoon(8)
(CVE-2008-3652), has been fixed by upgrading ipsec-tools to release 0.7.1.
Note this also fixes CVE-2008-3651.
ftpd(8)
(CVE-2008-4247), has been fixed.
tcpdump(8):
Fix CVE-2007-1218, CVE-2007-3798 and CAN-2005-1278 in base-tcpdump.
machfb(4),
voodoofb(4):
Introduce two missing KAUTH_GENERIC_ISSUSER check in the
mmap(2)
code.
rc.d(8)
script for
amd(8)
not to shutdown gracefully since it seems to cause problems for more people
than the old (also broken) behavior.
ftpd(8):
Fix and reorganize PAM support.
fxp(4):
Fix random pool corruption and hangup problems.
wd(4):
Handle more LBA48 bug quirks on some Hitachi's SATA/IDE drives.
awk(1):
Bring back an accidentally removed fix to allow escape of a newline
in string literals.
gcc(1):
zgrep(1):
Make
`-h'
option
(suppress filenames on output when multiple files are searched)
actually work.
copyinstr(9)
and
copyoutstr(9).
locore.s
which causes unexpected behavior.
copyin(9)
function on parsing syscall args.
The NetBSD 4.0 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 more than a year of development that went into the NetBSD 4.0 release. The complete list of changes can be found in the CHANGES: ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-4.0/CHANGES and CHANGES-4.0: ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-4.0/CHANGES-4.0 files in the top level directory of the NetBSD 4.0 release tree. Some highlights include:
agr(4):
new pseudo-device driver for link level aggregation.
gre(4)
tunnels and the
tun(4)
device.
ndiscvt(8).
options(4)
and
in_getifa(9).
wpa_supplicant(8)
and
wpa_cli(8).
Utilities to connect and handle aspects of 802.11 WPA networks.
hostapd(8).
An authenticator for IEEE 802.11 networks.
carp(4):
imported Common Address Redundancy Protocol to allow multiple hosts to share a set of IP addresses for high availability / redundancy, from OpenBSD.
etherip(4):
new EtherIP tunneling device. It's able to tunnel Ethernet traffic over IPv4 and IPv6 using the EtherIP protocol specified in RFC 3378.
ftpd(8)
can now run in standalone mode, instead of from
inetd(8).
tftp(1)
now has support for multicast TFTP operation in open-loop mode, server is in progress.
tcp(4):
added support for RFC 3465 Appropriate Byte Counting (ABC) and Explicit Congestion Notification as defined in RFC 3168.
scan_ffs(8),
scan_lfs(8):
utilities to find FFSv1/v2 and LFS partitions to recover lost disklabels on disks and image files.
mount_tmpfs(8).
mount_udf(8).
Read-only for now.
vnd(4):
the vnode disk driver can be used on filesystems such as smbfs and tmpfs.
newfs_sysvbfs(8)
and
mount_sysvbfs(8).
auich(4):
added support to handle the AC'97 modem as audio device, enabled with the kernel option
``AUICH_ATTACH_MODEM''
azalia(4):
added support for S/PDIF.
amdpm(4):
added support for the i2c bus on the AMD-8111 used on many Opteron motherboards and for the Analog Devices ADT7464 hardware monitor chip.
adt7467c(4):
new driver for Analog Devices ADT7467 and ADM1030 hardware monitor chips.
ipmi(4):
new driver for motherboards implementing the Intelligent Platform Management Interface 1.5 or 2.0, from OpenBSD.
it(4):
new driver for iTE 8705F/8712F and SiS 950 hardware monitors.
lm(4)
driver was rewritten and support for more chips was added, for example for Winbond W83627HF, W83627THF, W83627DHG and Asus AS99127F.
owtemp(4):
new driver for the 1-Wire temperature sensors.
tmp121temp(4):
new driver for the Texas Instruments TMP121 temperature sensor.
ug(4):
new driver for Abit uGuru hardware monitor found on newer Abit motherboards.
geodewdog(4):
new AMD Geode SC1100 Watchdog Timer driver.
gscpcib(4):
new AMD Geode SC1100 PCI-ISA bridge that provides support for the GPIO interface.
ath(4):
updated HALs with support for WiSOC (AR531x) and 32bit SPARC.
bge(4):
added support for the following chips: BCM5753, BCM5753M, BCM5715, BCM5754, BCM5755 and BCM5787. Numerous improvements and bugfixes were made too.
kse(4):
new driver for Micrel KSZ8842/8841 PCI network cards.
msk(4):
new driver for Marvell Yukon 2 GigE PCI network cards, from OpenBSD.
nfe(4):
new driver for NVIDIA nForce Ethernet network cards, from OpenBSD.
ral(4):
new 802.11 driver for PCI/Cardbus Ralink RT2500, RT2501, RT2600, RT2661 and RT2500 USB chipsets, from OpenBSD.
rum(4):
new 802.11 driver for USB Ralink RT2501 and RT2601 chipsets, from OpenBSD.
sip(4):
now works on sparc64.
tlp(4):
added support for ASIX AX88140A and AX88141.
vr(4):
added support for the VIA Rhine III.
wm(4):
added support for i8003, ICH8, ICH9 and others. Support for IPv6 Rx TCP/UDP Checksum Offloading and more.
wpi(4):
new driver for Intel PRO/Wireless 3945ABG PCI 802.11 network cards, from OpenBSD.
glxsb(4):
new driver for the AMD Geode LX AES Security Block that provides random numbers and AES acceleration, from OpenBSD.
options(4)
for more information.
options(4)
for more information.
ahcisata(4):
new driver for AHCI 1.0 and 1.1 compliant SATA controllers.
ataraid(4):
added support to handle Adaptec HostRAID and VIA V-Tech software RAID.
ciss(4):
new driver for HP/Compaq 5th+ generation Smart ARRAY controllers, from OpenBSD.
fdc(4):
added support for SBus based sparc64 machines and fixed formatting on sparc.
gcscide(4):
new driver for the AMD Geode CS5535 Companion Device IDE controller.
jmide(4):
new driver for JMicron Technology JMB36x PCIe to SATA II/PATA controllers.
mfi(4):
new driver for LSI Logic and Dell MegaRAID SAS controllers, from OpenBSD.
mpt(4):
added support for newer SAS and similar devices.
njata(4):
new driver for Workbit NinjaATA-32 CardBus IDE controller.
pdcsata(4):
added support for the Promise PDC20775, PDC20771, PDC40518, PDC40718 and some bugfixes.
piixide(4):
added support for some ICH8/ICH8-M/ICH9 IDE and SATA controllers.
svwsata(4):
new driver for Serverworks K2 SATA controllers, from OpenBSD.
viaide(4)
added support for the VIA VT8237A SATA controller and AMD CS5536 Companion Device IDE Controller.
ucycom(4):
new driver for Cypress microcontroller based serial devices.
uipaq(4):
new driver for the iPAQ devices.
uslsa(4):
new driver for Silicon Labs CP210x series serial adapters.
utoppy(4):
new driver for the Topfield TF5000PVR range of digital video recorders.
vesafb(4):
added new framebuffer driver that supports VESA BIOS (VBE) 2.0 extensions and up.
teliosio(4)
driver for the Sharp Telios LCD screen and Battery unit.
midi(4)
framework got a complete overhaul for better support of Active Sensing and improved handling of tempo and timebase changes.
ubt(4)
for USB controllers, and
bt3c(4)
for the 3Com Bluetooth PC-Card.
See
bluetooth(4),
bthset(1)
and
btpin(1).
bio(4)
framework from OpenBSD, to query/control block hardware RAID device controllers. Currently supporting the
mfi(4)
driver.
dkctl(8)
can be used to switch buffer queuing strategies on the fly on
wd(4)
disks, see also
bufq(9).
fileassoc(9)
is used by Veriexec, it adds in-kernel and file-system independent file meta-data association interface.
firmload(9):
an API for loading firmware images used by various hardware devices.
gpio(4):
imported General Purpose I/O framework from OpenBSD.
onewire(4):
imported Dallas Semiconductor 1-wire bus framework from OpenBSD.
proplib(3)
protocol was added for sending property lists to/from the kernel using ioctls.
spi(4):
new SPI (Serial Peripherial Interface) framework.
timecounter(9)
adds a new time-keeping infrastructure along with NTP API 4 nanokernel implementation. Almost all platforms were changed to support this API.
wscons(4)
console driver supports splash screens, scrolling, progress bar for kernel and boot messages.
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.
fast_ipsec(4)
for more information.
mprotect(2)
got restrictions to enforce W^X policies, from PaX. See
options(4),
sysctl(3),
and
paxctl(1).
security(8).
kauth(9)
was added, replacing the traditional BSD credential management and privileged operation access control with an abstract layer, allowing the implementation of various security models either as part of the NetBSD distribution or as third-party LKMs.
NetBSD's kernel authorization is a hybrid clean-room implementation of a similar interface developed by Apple, extending its capabilities and combining concepts of credential inheritance control.
cdplay(1):
added digital transfer mode support.
cksum(1)
can now verify checksums.
csplit(1):
new utility that splits a file into pieces. From FreeBSD/OpenBSD.
identd(1):
added support for forwarding ident queries and receiving of proxied ident queries.
getent(1):
added support for the ethers database.
gkermit(1):
new program for transferring files using the Kermit protocol.
mail(1):
added support for Mime and multi-character set handling, command line editing and completion.
utoppya(1):
new utility to interface to the
utoppy(4)
driver.
init(8):
added support for running multi-user in a chroot() environment. Allows / file system on e.g.,
cgd(4),
vnd(4)
or
ccd(4)
volumes.
gpt(8):
new GUID partition table maintenance utility, from FreeBSD.
iscsi-target(8);
Initiator (client) code is underway.
lockstat(8):
new command to display a summary of kernel locking events recorded over the lifetime of a called program.
ofctl(8):
new command to display the OpenPROM or OpenFirmware device tree for the macppc, shark and sparc64.
btconfig(8)
for controller configuration.
btdevctl(8)
to manage pseudo devices relating to remote services.
bthcid(8)
and
btpin(1)
for authenticating radio connections.
sdpd(8)
for providing service discovery to remote devices.
sdpquery(1)
for querying services on remote devices.
rfcomm_sppd(1)
to access remote services over RFCOMM via stdio or pty.
bthset(1)
for making connections to Bluetooth headsets.
Besides this list, there have also been innumerable bug fixes and other miscellaneous enhancements of course.
In this release of NetBSD, some software components known from previous releases were removed from the system. In some cases those were components that are not useful anymore or their utility does not justify maintenance overhead. Other components were not working properly and there was lack of interest in fixing them.
raid(4),
raidctl(8),
and the
NetBSD Guide:
http://www.NetBSD.org/docs/guide/en/chap-rf.html.
sendmail(1)
command line tool. Postfix has been included with NetBSD since NetBSD 1.5 was released in December 2005. Details about Postfix can be found in the
NetBSD Guide:
http://www.NetBSD.org/docs/guide/en/chap-mail.html.
For those who need Sendmail, it is available from pkgsrc in the
mail/sendmail
and
mail/sendmail813
packages.
net/uucp
package. The
cu(1)
command is available as a frontend to
tip(1).
lang/gcc3-f77
package.
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 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/mirrors/.
The root directory of the NetBSD 4.0.1 release is organized as follows:
.../NetBSD-4.0.1/
CHANGESCHANGES-4.0CHANGES-4.0.1CHANGES.prevLAST_MINUTEMIRRORSREADME.filesTODOpatches/source/In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD 4.0.1 has a binary distribution.
The source distribution sets can be found in subdirectories of the
source
subdirectory of the distribution tree.
They contain the complete sources to the system.
The source distribution sets are as follows:
config(1);
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
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
BSDSUMCKSUMMD5SHA512SYSVSUMThe SHA512 digest is the safest checksum, followed by the MD5 digest, and finally the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of systems can check the integrity of the release files.
amiga
subdirectory of the distribution:
.../NetBSD-4.0.1/amiga/.
It contains the following files and directories:
INSTALL.htmlINSTALL.psINSTALL.txtINSTALL.more.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/kernel/netbsd-GENERIC.gzsets/installation/floppy/miniroot/misc/miniroot.fs/
(root) and
/usr
partitions and getting ready to extract (and possibly first
fetching) the distribution sets.
There is enough on this file system to allow you to make a SLIP or
PPP connection, configure an Ethernet, mount an NFS file system or ftp.
You can also load distribution sets from a SCSI tape or from one of
your existing
AmigaDOS
partitions.
amiga/binary/sets
subdirectory
of the
NetBSD
4.0.1
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 4.5.0. Binary sets for the X Window System are distributed with NetBSD. The sets are:
The amiga 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.
NetBSD4.0.1 runs on any Amiga that has a 68020 or better CPU with some form of MMU, and on 68060 DraCos.
NetBSD does not, and will never, run on run on A1000, A500, A600, A1200, A2000, A4000/EC030, CDTV and CD32 systems that are not enhanced by a CPU board.
For 68020 and 68030 systems, a FPU is recommended but not required for the system utilities. 68LC040, 68040V and 68LC060 systems don't work correctly at the moment.
The minimal configuration requires 6 MB of RAM (not including CHIPMEM!) and about 75 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. (6 MB of RAM will actually allow you to compile, however it won't be speedy. X really isn't usable on a 6 MB system.)
Here is a table of recommended HD partition sizes for a full install:
| Partition | Suggested | + X | Needed | + X |
| / (root) | 25 MB | 25 MB | 20 MB | 20 MB |
| /usr | 245 MB | 270 MB | 120 MB | 145 MB |
| /var | 20 MB | 20 MB | 5 MB | 5 MB |
| swap | 2*RAM below 32 MB, then up to you |
As you may note the recommended size of
/usr
is 125 MB greater than needed.
This is to leave room for a kernel source and compile tree as
you will probably want to compile your own kernel.
GENERIC
is large and bulky to accommodate all people.
For example, most people's machines have an FPU, so you do not need the
bulky FPU_EMULATE option.
Preconfigured or precompiled packages are installed below
/usr/pkg
by default.
You should either make
/usr
larger (if you intend to install a lot of them), make
/usr/pkg
an additional partition, use the
-p
option to
pkg_add
to install them in a different place, or link
/usr/pkg
to a different place.
If you only have less than 8 MB of fast memory, you should make your swap partition larger, as your system will be doing much more swapping. Especially: do not place it onto a old small (and normally slow) disk!
If its not on the above lists, there is no support for it in this release.
Especially (but this is an incomplete list), there are no
drivers for: Blizzard III SCSI option,
Ferret SCSI, Oktagon SCSI.
Note that if you are installing or upgrading from a writable media, the media can be write-protected if you wish. These systems mount a root image from inside the kernel, and will not need to write to the media. If you booted from a floppy, the floppy disk may be removed from the drive after the system has booted.
Installation is supported from several media types, including:
The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the various media are outlined below.
Note where you place the files as you will need this later.
Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk.
If your SCSI CD-ROM is connected to a supported SCSI host adapter, or it is an ATAPI cd-rom connected to the A1200/A4000 internal IDE connector, simply put the CD into the drive before installation.
Find out where the distribution set files are on the CD-ROM or DVD.
Likely locations are
binary/sets
and
amiga/binary/sets.
Proceed to the instruction on installation.
split(1)
command, running e.g.
split -b 235k base.tgz base.
to split the
base.tgz
file from
amiga/binary/sets
into files named
base.aa,
base.ab,
and so on.
Repeat this for all
set_name.tgz
files, splitting them into
set_name.xx
files.
Count the number of
set_name.xx
files that make up the
distribution sets you want to install or upgrade.
You will need one sixth that number of 1.44 MB floppies.
Format all of the floppies with
MS-DOS.
Do
not
make any of them bootable
MS-DOS
floppies, i.e. don't use
format /s
to format them.
(If the floppies are bootable, then the
MS-DOS
system files that make them bootable will take up some space, and you
won't be able to fit the distribution set parts on the disks.)
If you're using floppies that are formatted for
MS-DOS
by their manufacturers, they probably aren't bootable, and you can use
them out of the box.
Place all of the
set_name.xx
files on the
MS-DOS
disks.
Once you have the files on MS-DOS disks, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
204.152.190.13
and the IPv6 address is
2001:4f8:4:7:230:48ff:fe31:43f2
(as of December, 2007).
Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
/etc/exports
file on the NFS server and resetting its mount daemon (mountd).
(Both of these actions will probably require superuser
privileges on the server.)
You need to know the numeric IP address of the NFS server, and, if you don't have DHCP available on your network and the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself.
Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
If you're making the tape on a UNIX-like system, the easiest way to do so is probably something like:
# tar -cf tape_device dist_directories
where
tape_device
is the name of the tape device that
describes the tape drive you're using; possibly
/dev/rst0,
or something similar, but it will vary from system to system.
(If you can't figure it out, ask your system administrator.)
In the above example,
dist_directories
are the
distribution sets' directories, for the distribution sets you
wish to place on the tape.
For instance, to put the
kern-GENERIC, base, and etc
distributions on tape (in
order to do the absolute minimum installation to a new disk),
you would do the following:
# cd .../NetBSD-4.0.1
# cd amiga/binary
# tar -cf tape_device kern-GENERIC base etc
Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
You will need an AmigaDOS hard drive prep tool to prepare your hard drives for use with NetBSD/amiga. HDToolBox is provided with the system software and on floppy installation disks since Release 2.0 of AmigaDOS, so we will provide instructions for its use.
Note that NetBSD can't currently be installed on disks with a sector size other than 512 bytes (e.g., ``640 MB'' 90mm M-O media). You can, however, mount ADOSFS partitions on such M-O's.
A full explanation of HDToolBox can be found with your AmigaDOS manuals and is beyond the scope of this document.
The first time you partition a drive, you need to set its drive type so that you have working geometry parameters. To do this you enter the ``Change drive type'' menu, and either use ``read parameters from drive'' or set them manually.
Note you will be modifying your HD's. If you mess something up here you could lose everything on all the drives that you configure. It is therefore advised that you:
What you need to do is partition your drives; creating at least
root, swap and
/usr
partitions and possibly at least one more for
/usr/local
if you have the space.
This should be done as the HDToolBox manual describes. One thing to note is that if you are not using a Commodore controller you will need to specify the device your SCSI controller uses, e.g. if you have a Warp Engine you would:
SCSI_DEVICE_NAME=warpdrive.device
The important things you need to do above and beyond normal partitioning includes (from Partition Drive section):
/),
if you want to boot
NetBSD
directly, or the swap partition, if you want
to boot the installation miniroot directly.
To make the needed changes:
root partition : 0x4e425207 (NBR\007)
swap partition : 0x4e425301 (NBS\001)
other partitions: 0x4e425507 (NBU\007)
Here
`other'
refers to other partitions you will
format for reading and writing under
NetBSD
(e.g.
/usr)
Make sure you press
RETURN
to enter this value as some versions of HDToolBox will forget your entry
if you don't.
On the root
(/)
(and, for installation, swap) partition,
set instead this:
Mask and maxtransfer are not used with NetBSD.
Once this is done NetBSD/amiga will be able to recognize your disks and which partitions it should use.
Once the hard disk has been prepared for
NetBSD,
the miniroot file system
(miniroot.fs)
is transferred to the swap
partition configured during the hard disk prep (or the existing
swap partition in the case of an upgrade).
The xstreamtodev utility provided in the
amiga/installation/misc
directory can
be used on
AmigaDOS
to transfer the file system for either a new
installation or an upgrade.
The file system can also be transferred on an existing
NetBSD
system for an update by using dd.
This should only be done after booting
NetBSD
into single-user state.
It may also be possible to shutdown to single-user, providing that
the single-user state processes are not using the swap partition.
On AmigaDOS, the command:
xstreamtodev --input=miniroot.fs --rdb-name=<swap partition>
where <swap partition> is the name you gave to the NetBSD partition to be used for swapping. If xstreamtodev is unable to determine the SCSI driver device name or the unit number of the specified partition, you may also need to include the option
--device=<driver.name>
and/or
--unit=<SCSI unit number>
To transfer the miniroot using NetBSD, you should be booted up in single user state on the current NetBSD system, or use the shutdown now command to shutdown to single-user state. Then copy the miniroot using dd:
dd if=miniroot.fs of=/dev/rsd0b
where
/dev/rsd0b
should be the device path of the swap partition
your system is configured to use.
Once the file is copied, reboot back to
AmigaDOS
to boot the upgrade kernel.
miniroot.fs
on the swap partition.
Installing NetBSD is a relatively complex process, but, if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble.
Before you begin, you must have already prepared your hard disk as detailed in the section on preparing your system for install.
The following is a walk-through of the steps necessary to get
NetBSD
installed on your hard disk.
If you wish to stop the installation, you may press
CONTROL-C
at any prompt, but if you do, you'll have to
begin again from scratch.
Transfer the miniroot file system onto the hard disk partition used by NetBSD for swapping, as described in the "Preparing your System for NetBSD Installation" section above.
[This description is for V40 (OS 3.1) ROMs. For older ROMs, there might be small differences. Check your AmigaDOS documentation to learn about the exact procedure.] Using bootblocks may not work on some systems, and may require a mountable file system on others.
Reboot your machine, holding down both mouse buttons if you have a 2-button mouse, the outer mouse buttons if you have a 3-button mouse. On the DraCo, press the left mouse button instead, when the boot screen prompts you for it.
From the boot menu, select Boot Options. Select the swap partition with the miniroot, and then ok. Select Boot now. The machine will boot the bootblock, which will prompt your for a command line. You have a few seconds time to change the default. Entering an empty line will accept the default.
The bootblock uses command lines of the form:
file[ options]
where file
is the kernel file name on the partition where the
boot block is on, and
[options]
may contain the following:
If you have an AGA machine, and your monitor will handle the dblNTSC mode, you may include the -A option to enable the dblNTSC display mode.
If your machine has a fragmented physical memory space, as, e.g., DraCo machines, you should add the -n2 option to enable the use of all memory segments.
sd0 sd1, etc.)
Then you will be prompted for a root device.
At this time type
sd0b,
where
sd0
is the device which contains the swap
partition you created during the hard disk preparation.
When prompted for a dump device, answer
`none'
for the install
(normally, you would tell it one of the swap devices).
When prompted for the root file system type, confirm
`generic',
which will auto-detect it.
If the system should hang after entering the root device, try again with
netbsd -I ff -b
This disables synchronous transfer on all SCSI devices on the first bus.
The system should continue to boot.
For now ignore
``WARNING''
messages about bad dates in clocks, and a warning about
/etc/rc
not existing.
Eventually you will be be asked to enter the pathname of the shell, just press
RETURN.
After a short while, you will be asked to select the type of your keyboard.
After
you have entered a valid response here, the system asks you if
you want to install or upgrade your system.
Since you are reading the
install
section,
`i'
would be the proper response here...
The installer starts with a nice welcome messages. Read this message carefully, it also informs you of the risks involved in continuing! If you still want to go on, type `y'. The installer now continues by trying to figure out your disk configuration. When it is done, you will be prompted to select a root device from the list of disks it has found.
You should know at this point that the disks are
not
numbered according to their SCSI-ID!
The
NetBSD
kernel numbers the SCSI
drives (and other devices on the SCSI bus) sequentially as it finds them.
The drive with the lowest SCSI-ID will be called
sd0,
the next one
sd1,
etc.
Also, any ATAPI disk drives (e.g. ZIP)
will be configured as
``SCSI''
drives, too, and will be configured
before any
`real'
SCSI drives if connected to the Amiga internal port on A4000/A1200
(if any are present). Real IDE drives will be configured as
wd0,
wd1,
etc.
The installer will offer you to look at the NetBSD disk label of the disks at this point. You should do this, to find out what partition letters the NetBSD kernel assigned to the partitions you created, and as a check whether the disk number you are going to use is right.
you are now at the point of no return.
If you confirm that
you want to install
NetBSD,
your hard drive will be modified,
and perhaps its contents scrambled at the whim of the install
program.
Type
Control-C
now
if you don't want this.
At this time, you will need to tell the installer which partition
will be associated with the different file systems.
Normally, you'll want to add a partition for
/usr,
at least.
rsdNc
or
sdNc
partitions for anything!
They are for access to the whole disk only and do
not
correspond to any Amiga partition!
The install program will now make the file systems you specified. There should be only one error per file system in this section of the installation. It will look like this:
newfs: ioctl (WDINFO): Invalid argument
newfs: /dev/rsd0a: can't rewrite disk label
If there are any others, restart from the beginning of the installation process. This error is ok as the Amiga does not write disklabels currently. You should expect this error whenever using newfs.
The install will now ask you want to configure any network information. It ill ask for the machine's host name, domain name, and other network configuration information.
Since the network configuration might have lead to additional (nfs) file system entries, you get another chance to modify your fstab.
You are finally at the point where some real data will be put on your freshly made file systems. Select the device type you wish to install from and off you go....
Some notes:
nrst0).
Try
nrst0h,
nrst0m,
or
nrst0l
instead.
.'.
Next you will be asked to specify the timezone.
Just select the timezone you are in.
The installer will make the correct setup on your root file system
(/).
After the timezone-link is installed,
the installer will proceed by creating the device nodes on your
root file system under
/dev.
Be patient, this will take a while...
Next, the installer will copy your keymap settings to the new system. After this, it will copy the kernel from the installation miniroot to the newly installed / upgraded system. If the installed system already has a kernel, it will ask you for confirmation.
kern.tgz distribution set, this is an old kernel, and you should answer "y" to install a working (although restricted) INSTALL kernel.
If you did install the kern.tgz kernel, you normally should answer "n".
Finally, the installer ask you if you want to install the bootblock
code on your root disk.
This is a matter of personal choice and can also be done from a running
NetBSD
system.
See the
installboot(8)
manual page about how to do this.
Once the installer is done, halt the system with the
halt
command
(wait for
halted
to be displayed) and reboot.
Then again boot
NetBSD
this time selecting the root partition
(/)
from the boot menu, and tell it to boot
netbsd -s
You need to do your final tweaks now. First mount your file systems like so:
mount -av
Your system is now complete but not completely configured; you
should adjust the
/etc/sendmail.cf
file as necessary to suit your site.
You should also examine and adjust the settings in
/etc/rc.conf.
You can use
vi(1)
or
ed(1)
to edit the files.
If you installed the man pages you can type
man vi or man ed
for instructions on how to use these somewhat non-intuitive editors.
Once you are done with the rest of configuration unmount your file systems and halt your system, then reboot:
# cd /
# umount -av
# halt
Finally you can now boot your system and it will be completely functional:
netbsd
When it boots off of the hard drive, you will have a complete
NetBSD
system!
Congratulations!
(You really deserve them!!!)
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
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).
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=vt220
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_de0="inet 123.45.67.89 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
To enable proper hostname resolution, you will also want to add an
/etc/resolv.conf
file or (if you are feeling a little more adventurous) run
named(8).
See
resolv.conf(5)
or
named(8)
for more information.
Instead of manually configuring network and naming service,
DHCP can be used by setting
dhclient=YES
in
/etc/rc.conf.
Other files in
/etc
that may require modification or setting up include
/etc/mailer.conf,
/etc/nsswitch.conf,
and
/etc/wscons.conf.
After reboot, you can log in as
root
at the login prompt.
Unless you've set a password in
sysinst,
there
is no initial password.
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.
By default, root login from the network is disabled (even via
ssh(1)).
One way to become root over the network is to log in as a different
user that belongs to group
``wheel''
(see
group(5))
and use
su(1)
to become root.
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
vipw(8)
and
pwd_mkdb(8)
if you want to edit the password database.
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.
amiga/4.0/All
subdir.
You can install them with the following commands under
sh(1):
# PKG_PATH=ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/amiga/4.0/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v bash # pkg_add -v perl # pkg_add -v apache # pkg_add -v kde # pkg_add -v firefox ...
If you are using
csh(1)
then replace the first two lines with the following:
# setenv PKG_PATH ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/amiga/4.0/All ...
/pub/pkgsrc
directory.
If you would like to use such mirrors, you could also try the
/pub/NetBSD/packages/current-packages/NetBSD/amiga/4.0/All
directory which may have the same contents.
The above commands will install the Tenex-csh and Bourne Again shell, the Perl programming language, Apache web server, KDE desktop environment and the Firefox web browser as well as all the packages they depend on.
pkg_add(1)
command will complain about a version mismatch of packages with a message
like the following:
Warning: package `foo' was built for a different version of the OS:
NetBSD/i386 4.0 (pkg) vs. NetBSD/i386 4.0.1 (this host),
/usr/pkgsrc
(though other locations work fine), with the commands:
# mkdir /usr/pkgsrc
# cd /usr/pkgsrc
# tar -zxpf pkgsrc.tar.gz
After extracting, see the
README
and
doc/pkgsrc.txt
files 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/postfix/main.cf
file will almost definitely need to be adjusted.
If you prefer a different MTA, then install it using the
NetBSD
package system or by hand and adjust
/etc/mailer.conf.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
# man 5 filename
is likely to give you more information on these files.
The upgrade to NetBSD4.0.1 is a binary upgrade; it can be quite difficult to advance to a later version by recompiling from source due primarily to interdependencies in the various components.
To do the upgrade, you must have the
NetBSD
kernel on
AmigaDOS
and you must transfer the miniroot file system
miniroot.fs
onto the swap partition of the
NetBSD
hard disk.
You must also have at least the
base
binary distribution set available, so that you can upgrade
with it, using one of the upgrade methods described above.
Finally, you must have sufficient disk space available to install the new
binaries.
Since the old binaries are being overwritten in place, you only need
space for the new binaries, which weren't previously on the system.
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 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.
To upgrade your system, follow the following instructions:
Transfer the miniroot file system onto the hard disk partition used by NetBSD for swapping, as described in the "Preparing your System for NetBSD Installation" section above.
Now boot up NetBSD, with boot blocks installed
Reboot your machine, holding down both mouse buttons if you have a 2-button mouse, the outer mouse buttons if you have a 3-button mouse. On the DraCo, press the left mouse button instead, when the boot screen prompts you for it.
From the boot menu, select Boot Options. Select the swap partition with the miniroot, and then ok. Select Boot now. The machine will boot the bootblock, which will prompt your for a command line. You have a few seconds time to change the default. Entering an empty line will accept the default.
The bootblock uses command lines of the form:
file[ options]
where
file
is the kernel file name on the partition where the
boot block is on, and
options
may contain the same as described in the INSTALL section.
For installing, use
netbsd -b
If you machine has a split memory space, like, e.g., DraCo machines, use this instead:
netbsd -bn2
/)
and swap partitions.
When prompted for the root device, type
sd0b
(replacing
`0'
with the disk number that
NetBSD
used for
your root/swap device).
When prompted for a dump device, answer
`none'
for the upgrade.
(For a normal boot, you would tell it one of the swap devices).
When prompted for the root file system type, confirm
`generic',
which will auto-detect it.
You will be presented with some information about the upgrade
process and a warning message, and will be asked if you wish
to proceed with the upgrade process.
If you answer negatively, the upgrade process will stop, and your disk will
not be modified.
If you answer affirmatively, the upgrade process will begin,
and your disk will be modified.
You may press
CONTROL-C
to stop the upgrade process at any time.
However, if you press it at an inopportune moment, your system
may be left in an inconsistent (and possibly unusable) state.
You will now be greeted and reminded of the fact that this is a potential dangerous procedure and that you should not upgrade the etc set.
When you decide to proceed, you will be prompted to enter your root disk. After you've done this, it will be checked automatically to make sure that the file system is in a sane state before making any modifications. After this is done, you will be asked if you want to configure your network.
You are now allowed to edit your fstab. Normally you don't have to. Note that the upgrade-kit uses its own copy of the fstab. Whatever you do here won't affect your actual fstab. After you are satisfied with your fstab, the upgrade-kit will check all file systems mentioned in it. When they're ok, they will be mounted.
You will now be asked if your sets are stored on a normally mounted file system. You should answer `y' to this question if you have the sets stored on a file system that was present in the fstab. The actions you should take for the set extraction are pretty logical (we think).
After you have extracted the sets, the upgrade kit will proceed with setting the timezone and installing the kernel and bootcode. This is all exactly the same as described in the installation section.
Your system has now been upgraded to NetBSD4.0.1.
After a new kernel has been copied to your hard disk, your machine is a complete NetBSD4.0.1 system. However, that doesn't mean that you're finished with the upgrade process. There are several things that you should do, or might have to do, to insure that the system works properly.
You will probably want to get the
etc
distribution,
extract it, and compare its contents with those in your
/etc
directory.
You will probably want to replace some of your
system configuration files, or incorporate some of the changes
in the new versions into yours.
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.
If upgrading from a
NetBSD
version older than 1.0, you might also want to
recompile any locally-built binaries, to take advantage of the
shared libraries.
(Note that any new binaries that you build
will be dynamically linked, and therefore take advantage of
the shared libraries, by default.
For information on how to make statically linked binaries, see the
cc(1)
and
ld(1)
manual pages.)
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 4.0.1.
N.B. when using sysinst for upgrading, it will automatically invoke
postinstall fix
It is
very important
that you populate the directory
/etc/pam.d
with appropriate configuration files for Pluggable Authentication Modules
(PAM) because you will not be able to login any more otherwise. Using
postinstall
as described below will take care of this. Please refer to
http://www.NetBSD.org/docs/guide/en/chap-pam.html
for documentation about PAM.
The following issues can generally be resolved by running postinstall with the etc set :
postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix
Issues fixed by postinstall:
/etc
need upgrading.
These include:
/etc/defaults/*
/etc/mtree/*
/etc/pam.d/*
/etc/daily
/etc/weekly
/etc/monthly
/etc/security
/etc/rc.subr
/etc/rc
/etc/rc.shutdown
/etc/rc.d/*
The following issues need to be resolved manually:
The following issues can generally be resolved by running postinstall with the etc set :
postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix
Issues fixed by postinstall:
/etc
need upgrading.
These include:
/etc/defaults/*
/etc/mtree/*
/etc/daily
/etc/weekly
/etc/monthly
/etc/security
/etc/rc.subr
/etc/rc
/etc/rc.shutdown
/etc/rc.d/*
/etc/envsys.conf
The following issues need to be resolved manually:
postinstall -s /path/to/etc.tgz fix mailerconf
/etc/mailer.conf
file to use Postfix as the MTA. When using
sysinst
to upgrade the system, it will ask if you want this to be done.
Note that if you have a customized Sendmail setup, you need to set up Postfix in an equivalent way; there is no tool for automatic conversion of Sendmail configuration to a Postfix one.
Postfix will be started up automatically when the system boots.
You may see messages like "$sendmail is not set properly" at boot.
You can suppress them by removing
/etc/rc.d/sendmail
and
/etc/rc.d/smmsp.
Those files and other parts of sendmail configuration like files under
/usr/share/sendmail
are not removed by default
while upgrading for those who want to continue using sendmail from
outside the base system.
If you want to delete them,
postinstall
can be used:
postinstall -s /path/to/etc.tgz fix sendmail
Both issues have been addressed on the wrstuden-fixsa branch, but did not make it into the NetBSD release. Both will be fixed in the next patch release.
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-users@NetBSD.org.
As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it.
Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick
for their ongoing work on BSD systems, support, and encouragement.
(in alphabetical order)
All product names mentioned herein are trademarks or registered trademarks of their respective owners.
The following notices are required to satisfy the license terms of the software that we have mentioned in this document:
NetBSD is a registered trademark of The NetBSD Foundation, Inc.
In the following statement, the phrase ``this text'' refers to portions
of the system documentation.
Portions of this text are reprinted and reproduced in electronic form in
NetBSD, from IEEE Std 1003.1, 2004 Edition, Standard for
Information Technology -- Portable Operating System Interface (POSIX),
The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the
Institute of Electrical and Electronics Engineers, Inc and The Open Group.
In the event of any discrepancy between these versions and the original
IEEE and The Open Group Standard, the original IEEE and The Open Group
Standard is the referee document.
The original Standard can be obtained online at
http://www.opengroup.org/unix/online.html.
This notice shall appear on any product containing this material