About this Document............................................2
What is NetBSD?................................................2
Changes Between The NetBSD 3.0 and 4.0 Releases................2
Networking..................................................3
File systems................................................3
Drivers.....................................................4
Platforms...................................................6
Kernel subsystems...........................................7
Security....................................................8
Userland....................................................8
Components removed from NetBSD..............................9
The Future of NetBSD..........................................10
Sources of NetBSD.............................................11
NetBSD 4.0 Release Contents...................................11
NetBSD/hp700 subdirectory structure........................12
Binary distribution sets...................................12
NetBSD/hp700 System Requirements and Supported Devices........14
Supported hardware.........................................14
Unsupported hardware.......................................14
Getting the NetBSD System on to Useful Media..................14
Preparing your System for NetBSD installation.................14
Get to the Boot Administration prompt......................14
Change the configuration parameters to netboot.............15
Determine netboot method...................................15
Installing the NetBSD System..................................16
Post installation steps.......................................20
Upgrading a previously-installed NetBSD System................22
Compatibility Issues With Previous NetBSD Releases............22
Issues affecting an upgrade from NetBSD 2.1 and older......23
Issues affecting an upgrade from NetBSD 3.x releases.......23
Issues with GDB 6.5...........................................24
Using online NetBSD documentation.............................24
Administrivia.................................................25
Thanks go to..................................................25
We are........................................................26
Dedication....................................................32
Legal Mumbo-Jumbo.............................................32
The End.......................................................38
This document describes the installation procedure for
NetBSD
4.0 on the
hp700
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 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 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 release is organized as follows:
.../NetBSD-4.0/
CHANGESCHANGES-4.0CHANGES.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 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.
hp700
subdirectory of the distribution:
.../NetBSD-4.0/hp700/.
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/misc/hp700/binary/sets
subdirectory
of the
NetBSD
4.0
distribution tree, and are as follows:
/usr/include)
and the various system libraries (except the shared
libraries, which are included as part of the
base
set).
This set also includes the manual pages for
all of the utilities it contains, as well as the
system call and library manual pages.
/etc
and in several other places.
This set
must
be installed if you are installing the system from scratch, but should
not
be used if you are upgrading.
GENERIC
kernel, named
/netbsd.
You
must
install this distribution set.
/usr/share.
groff(1),
all related programs, and their manual pages.
NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. NetBSD/hp700 currently does not ship with an X server or X clients. Binary sets for the X Window System are distributed with NetBSD. The sets are:
The hp700 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.
Since NetBSD/hp700 is an experimental port, the hardware support is in a constant state of flux. Check the port-hp700@NetBSD.org mailing list and the NetBSD/hp700 port homepage for an up-to-date list of known supported hardware. http://www.NetBSD.org/ports/hp700/
NetBSD/hp700 4.0 does not have any local disk support, so you must netboot and run diskless.
Because NetBSD/hp700 must run diskless, the distribution must be installed to a remote machine that NFS exports to the hp700 machine. As a result, there is no automated install procedure. Begin by retrieving the NetBSD set files onto the serving machine. These can be found at ftp.NetBSD.org. You may want to keep the following information handy:
IP Address: ftp.NetBSD.org
Login: anonymous
Password: <your e-mail address>
Server path: /pub/NetBSD/NetBSD-4.0/hp700/binary/sets
To get to the
BOOT_ADMIN>
prompt, you must press the
ESCAPE
key before it tries to boot an OS. Since these machines often take a
long time between powering on and the brief window of time where you can
hit the
ESCAPE
key, you must pay attention. Depending on how much RAM your system has, it
may take over a minute after pressing the power button before anything
will show up on screen.
Once you have escaped out of the
Selecting a system to boot
and
Searching for Potential Boot Devices
you need to type the
`a'
key to get to the
BOOT_ADMIN>
prompt. Now, use the online help with the
help
command.
Write down the ethernet address. You will need this later to configure the netboot server for your NetBSD/hp700 system.
Selecting a system to boot.
To stop selection process, press and hold the ESCAPE key.
<ESC>
Booting from: scsi.6.0 SEAGATE ST3600N
Selection process stopped.
Searching for Potential Boot Devices.
To terminate search, press and hold the ESCAPE key.
Device Selection Device Path Device Type
----------------------------------------------------------------------------
P0 scsi.6.0 SEAGATE ST3600N
<ESC>
Search terminated.
b) Boot from specified device
s) Search for bootable devices
a) Enter Boot Administration mode
x) Exit and continue boot sequence
?) Help
Select from menu: a
BOOT_ADMIN> lan_addr
LAN Station Address: 080009-123456
BOOT_ADMIN> help
BOOT_ADMIN> path primary lan
BOOT_ADMIN> autoselect on
BOOT_ADMIN> reset
The first command sets the primary boot device to be the network interface, and the second command sets the system to always try booting from the primary boot path when it is reset or powered on. The last command stores the new settings and resets the machine.
To return to using the SCSI disk at ID 6 as your primary boot device, you would use something like the following command:
BOOT_ADMIN> path primary scsi.6.0
rbootd(8)
server. The following list of RMP-only Series 700 workstations is
probably complete, but has not been tested:
Newer Series 700 workstations retrieve their boot program from a server
running
dhcpd(8)
in
bootpd(8)
compatible mode and
tftpd(8).
The following list of BOOTP-only Series 700 workstations is
probably complete, but has not been tested:
To netboot a hp700, you must configure one or more servers to provide
information and files to your hp700 (the
`client').
If you are using
NetBSD
(any architecture) on your netboot server(s), the information
provided here should be sufficient to configure everything.
Additionally, you may wish to look at the
diskless(8)
manual page and the manual pages for each daemon you'll be configuring.
If the server(s) are another operating system, you should consult the
NetBSD Diskless HOW-TO, which will walk you through the steps necessary to
configure the netboot services on a variety of platforms.
http://www.NetBSD.org/docs/network/netboot/
Briefly, the netboot
process involves discovery, bootstrap, kernel and file system stages.
In the first stage, the client discovers information
about where to find the bootstrap program.
Next, it downloads and executes the bootstrap program.
The server contains one large file (a LIF file system) with the bootloader
and the kernel. The bootstrap program simply loads the kernel from the
LIF image.
Once the kernel is loaded, it starts executing.
The
kernel tries to mount the NFS share that had the kernel and starts
executing
init(8).
Early hp700 systems use HP's proprietary RMP (the
rbootd(8)
daemon) for the discovery stage, bootstrap download, and kernel download
stages. Later hp700 systems use BOOTP for the discovery stage and TFTP for
the bootstrap and kernel download.
We will use
`CC:CC:CC:CC:CC:CC'
as the MAC address (ethernet hardware address) of your netboot client
machine.
You should have determined this address in an earlier stage.
In this example, we will use
`192.168.1.10'
as the IP address of your client and
`client.test.net'
as its name.
We will assume you're providing all of your netboot services
on one machine called
`server.test.net'
with the client's files exported from the directory
/export/client/root.
You should, of course, replace all of these with the names, addresses,
and paths appropriate to your environment.
You should set up each netboot stage in order (i.e. discovery, bootstrap, kernel, and then file system) so that you can test them as you proceed.
If your system uses RMP to netboot, you must set up
rbootd(8)
but can skip
dhcpd(8)
and
tftpd(8).
If your system uses BOOTP to netboot, then you must set up
dhcpd(8)
and
tftpd(8)
but can skip
rbootd(8).
rbootd(8)
Get
SYSNBSD
from the
installation/misc
directory of the distribution.
# mkdir -p /usr/mdec/rbootd
# cp SYSNBSD /usr/mdec/rbootd
# chmod -R a+rX /usr/mdec/rbootd
Create
/etc/rbootd.conf
with the following line:
CC:CC:CC:CC:CC:CC SYSNBSD
You will need to start the rbootd. If it's already running, you will need to restart it to force it to re-read its configuration file. If the server is running NetBSD, you can achieve this with:
# /etc/rc.d/rbootd restart
If your netboot server is not running
NetBSD
but other OSs (like Linux, Solaris etc.), you have to use
YAMAMORI Takenori's
sun-rbootd
package instead of native
rbootd(8).
Please refer the "Setting up the rbootd server" section
in the NetBSD Diskless HOW-TO
http://www.NetBSD.org/docs/network/netboot/rbootd/
for details.
dhcpd(8)
in
bootpd(8)
compatible mode
Put the following lines in your
/etc/dhcpd.conf
(see
dhcpd.conf(5)
and
dhcp-options(5)
for more information):
ddns-update-style none;
# Do not use any dynamic DNS features
#
allow bootp; # Allow bootp requests, thus the dhcp server
# will act as a bootp server.
#
authoritative; # master DHCP server for this subnet
#
subnet 192.168.1.0 netmask 255.255.255.0 {
# Which network interface to listen on.
# The zeros indicate the range of addresses
# that are allowed to connect.
}
group {
# Set of parameters common to all clients
# in this "group".
#
option broadcast-address 192.168.1.255;
option domain-name "test.net";
option domain-name-servers dns.test.net;
option routers router.test.net;
option subnet-mask 255.255.255.0;
#
# An individual client.
#
host client.test.net {
hardware ethernet CC:CC:CC:CC:CC:CC;
fixed-address 192.168.1.10;
#
# Name of the host (if the fixed address
# doesn't resolve to a simple name).
#
option host-name "client";
#
# Name of the bootloader or kernel
# to download via tftp.
#
filename "SYSNBSD";
#
# The path on the NFS server.
#
option root-path "/export/client/root";
#
# If your DHCP server is not your NFS server, supply the
# address of the NFS server. Since we assume you run everything
# on one server, this is not needed.
#
# next-server server.test.net;
}
#you may paste another "host" entry here for additional
#clients on this network
}
You will need to make sure that the
dhcpd.leases
file exists.
# touch /var/db/dhcpd.leases
You will need to start the dhcpd. If it's already running, you will need to restart it to force it to re-read its configuration file. If the server is running NetBSD, you can achieve this with:
# /etc/rc.d/dhcpd restart
tftpd(8)
The default configuration of the TFTP server is to run in a
chroot(8)
environment in the
/tftpboot
directory.
Thus, the first order of business is to create this directory:
# mkdir -p /tftpboot
Next, edit
/etc/inetd.conf
and uncomment the line with the TFTP daemon:
tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot
Now, restart
inetd(8).
If the server is running
NetBSD,
you can achieve this with:
# /etc/rc.d/inetd restart
Now, you need to copy the
bootloader
for your hp700 machine to
/tftpboot.
Get
SYSNBSD
from the
installation
directory of the distribution.
# cp SYSNBSD /tftpboot
# chmod -R a+rX /tftpboot
Sometimes, the
arp(8)
table gets messed up, and the TFTP server can't communicate with the
client.
In this case, it will write a log message (via
syslogd(8))
to
/var/log/messages
saying:
`tftpd: write: Host is down'.
If this is the case, you may need to force the server to map your client's
ethernet address to its IP address:
# arp -s client CC:CC:CC:CC:CC:CC
nfsd(8),
mountd(8),
and
rpcbind(8)
Now your system should be able to load the bootstrap program and start looking for the kernel. Let's set up the NFS server. Create the directory you are exporting for the netboot client:
# mkdir -p /export/client/root
Put the following line in
/etc/exports
to enable NFS sharing:
/export/client/root -maproot=root client.test.net
If your server is currently running an NFS server, you only need to
restart
mountd(8).
Otherwise, you need to start
rpcbind(8)
and
nfsd(8).
If the server is running
NetBSD,
you can achieve this with:
# /etc/rc.d/rpcbind start
# /etc/rc.d/nfsd start
# /etc/rc.d/mountd restart
You do not need to place a kernel in
/export/client/root
since the kernel is contained inside
SYSNBSD.
You need to extract and set up the client's installation of NetBSD. The Diskless HOW-TO describes how to provide better security and save space on the NFS server over the procedure listed here. http://www.NetBSD.org/docs/network/netboot/nfs.html
# cd /export/client/root
# tar -xpzf /path/to/files/base.tgz
# tar -xpzf /path/to/files/etc.tgz
Continue with the other non-essential distribution sets if desired.
# mkdir /export/client/root/swap
# dd if=/dev/zero of=/export/client/swap bs=4k count=4k
# echo '/export/client/swap -maproot=root:wheel client.test.net' | cat >> /etc/exports
# /etc/rc.d/mountd restart
# cd /export/client/root/dev
# ./MAKEDEV all
This procedure only works on NetBSD hosts.
fstab(5)
Create a file in
/export/client/root/etc/fstab
with the following lines:
server:/export/client/swap none swap sw,nfsmntpt=/swap
server:/export/client/root / nfs rw 0 0
rc.conf(5)
Edit
/export/client/root/etc/rc.conf
rc_configured=YES
hostname="client"
defaultroute="192.168.1.1"
nfs_client=YES
auto_ifconfig=NO
net_interfaces=""
Make sure rc does not reconfigure the network device since it will lose its connection to the NFS server with your root file system.
hosts(5)
file.
Edit
/export/client/root/etc/hosts
::1 localhost
127.0.0.1 localhost
192.168.1.10 client.test.net client
192.168.1.5 server.test.net server
You need
these services to start up every time you boot
your server, make sure the following lines are present in your
/etc/rc.conf:
rbootd=YES rbootd_flags=""
dhcpd=YES dhcpd_flags="-q"
nfs_server=YES # enable server daemons
mountd=YES
rpcbind=YES rpcbind_flags="-l" # -l logs libwrap
Also, you'll need to make sure the
tftpd
line in
/etc/inetd.conf
remains uncommented.
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_ie0="inet 123.45.67.89 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_ie0="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.
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.
4.0/hp700/All
subdir.
You can install them with the following commands under
sh(1):
# PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/4.0/hp700/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/NetBSD/packages/4.0/hp700/All ...
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.
/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.
NetBSD/hp700
does not currently support an upgrade procedure.
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 .
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-help@NetBSD.org.
As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it.
Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick
for their ongoing work on BSD systems, support, and encouragement.
(in alphabetical order)
| The NetBSD core group: | |||
| Alistair Crooks | agc@NetBSD.org | ||
| Quentin Garnier | cube@NetBSD.org | ||
| YAMAMOTO Takashi | yamt@NetBSD.org | ||
| Matt Thomas | matt@NetBSD.org | ||
| Christos Zoulas | christos@NetBSD.org | ||
|
| |||
| The portmasters (and their ports): | |||
| Anders Magnusson | ragge | vax | |
| Andrew Doran | ad | amd64 | |
| Andrew Doran | ad | i386 | |
| Andrey Petrov | petrov | sparc64 | |
| Ben Harris | bjh21 | acorn26 | |
| Cherry G. Mathew | cherry | ia64 | |
| Chris Gilbert | chris | cats | |
| Darrin Jewell | dbj | next68k | |
| Erik Berls | cyber | cobalt | |
| Gavan Fantom | gavan | iyonix | |
| IWAMOTO Toshihiro | toshii | hpcarm | |
| Ichiro FUKUHARA | ichiro | hpcarm | |
| Ignatios Souvatzis | is | amiga | |
| Izumi Tsutsui | tsutsui | ews4800mips | |
| Izumi Tsutsui | tsutsui | hp300 | |
| Izumi Tsutsui | tsutsui | news68k | |
| Jaime A Fournier | ober | bebox | |
| Jaime A Fournier | ober | zaurus | |
| Jason Thorpe | thorpej | algor | |
| Jason Thorpe | thorpej | evbarm | |
| Jason Thorpe | thorpej | shark | |
| Jonathan Stone | jonathan | pmax | |
| Julian Coleman | jdc | atari | |
| Manuel Bouyer | bouyer | xen | |
| Marcus Comstedt | marcus | dreamcast | |
| Martin Husemann | martin | sparc64 | |
| Matt Fredette | fredette | sun2 | |
| Matt Thomas | matt | alpha | |
| Matt Thomas | matt | netwinder | |
| Matthias Drochner | drochner | cesfic | |
| Michael Lorenz | macallan | macppc | |
| NISHIMURA Takeshi | nsmrtks | x68k | |
| Nathan Williams | nathanw | sun3 | |
| Nick Hudson | skrll | hp700 | |
| Noriyuki Soda | soda | arc | |
| Paul Kranenburg | pk | sparc | |
| Phil Nelson | phil | pc532 | |
| Reinoud Zandijk | reinoud | acorn32 | |
| Ross Harvey | ross | alpha | |
| Søren Jørvang | soren | sgimips | |
| Scott Reynolds | scottr | mac68k | |
| Shin Takemura | takemura | hpcmips | |
| Simon Burge | simonb | evbmips | |
| Simon Burge | simonb | pmax | |
| Simon Burge | simonb | sbmips | |
| Steve Woodford | scw | evbppc | |
| Steve Woodford | scw | mvme68k | |
| Steve Woodford | scw | mvmeppc | |
| Takayoshi Kochi | kochi | ia64 | |
| Tim Rightnour | garbled | prep | |
| Tohru Nishimura | nisimura | luna68k | |
| Tohru Nishimura | nisimura | sandpoint | |
| Wayne Knowles | wdk | mipsco | |
| Wolfgang Solfrank | ws | ofppc
| |
| The NetBSD 4.0 Release Engineering team: | |||
| Grant Beattie | grant@NetBSD.org | ||
| Manuel Bouyer | bouyer@NetBSD.org | ||
| David Brownlee | abs@NetBSD.org | ||
| Pavel Cahyna | pavel@NetBSD.org | ||
| James Chacon | jmc@NetBSD.org | ||
| Julian Coleman | jdc@NetBSD.org | ||
| Håvard Eidnes | he@NetBSD.org | ||
| Liam J. Foy | liamjfoy@NetBSD.org | ||
| John Heasley | heas@NetBSD.org | ||
| Geert Hendrickx | ghen@NetBSD.org | ||
| Soren Jacobsen | snj@NetBSD.org | ||
| Daniel de Kok | daniel@NetBSD.org | ||
| Phil Nelson | phil@NetBSD.org | ||
| Jeff Rizzo | riz@NetBSD.org | ||
|
| |||
| NetBSD Developers: | |||
| Nathan Ahlstrom | nra@NetBSD.org | ||
| Steve Allen | wormey@NetBSD.org | ||
| Jukka Andberg | jandberg@NetBSD.org | ||
| Julian Assange | proff@NetBSD.org | ||
| Lennart Augustsson | augustss@NetBSD.org | ||
| Christoph Badura | bad@NetBSD.org | ||
| Bang Jun-Young | junyoung@NetBSD.org | ||
| Dieter Baron | dillo@NetBSD.org | ||
| Robert V. Baron | rvb@NetBSD.org | ||
| Alan Barrett | apb@NetBSD.org | ||
| Grant Beattie | grant@NetBSD.org | ||
| Jason Beegan | jtb@NetBSD.org | ||
| Erik Berls | cyber@NetBSD.org | ||
| Hiroyuki Bessho | bsh@NetBSD.org | ||
| John Birrell | jb@NetBSD.org | ||
| Mason Loring Bliss | mason@NetBSD.org | ||
| Charles Blundell | cb@NetBSD.org | ||
| Rafal Boni | rafal@NetBSD.org | ||
| Stephen Borrill | sborrill@NetBSD.org | ||
| Sean Boudreau | seanb@NetBSD.org | ||
| Manuel Bouyer | bouyer@NetBSD.org | ||
| John Brezak | brezak@NetBSD.org | ||
| Allen Briggs | briggs@NetBSD.org | ||
| Mark Brinicombe | mark@NetBSD.org | ||
| Aaron Brown | abrown@NetBSD.org | ||
| Andrew Brown | atatat@NetBSD.org | ||
| David Brownlee | abs@NetBSD.org | ||
| Frederick Bruckman | fredb@NetBSD.org | ||
| Jon Buller | jonb@NetBSD.org | ||
| Simon Burge | simonb@NetBSD.org | ||
| Robert Byrnes | byrnes@NetBSD.org | ||
| Pavel Cahyna | pavel@NetBSD.org | ||
| D'Arcy J.M. Cain | darcy@NetBSD.org | ||
| Dave Carrel | carrel@NetBSD.org | ||
| Daniel Carosone | dan@NetBSD.org | ||
| James Chacon | jmc@NetBSD.org | ||
| Bill Coldwell | billc@NetBSD.org | ||
| Julian Coleman | jdc@NetBSD.org | ||
| Ben Collver | ben@NetBSD.org | ||
| Jeremy Cooper | jeremy@NetBSD.org | ||
| Chuck Cranor | chuck@NetBSD.org | ||
| Alistair Crooks | agc@NetBSD.org | ||
| Aidan Cully | aidan@NetBSD.org | ||
| Garrett D'Amore | gdamore@NetBSD.org | ||
| Johan Danielsson | joda@NetBSD.org | ||
| John Darrow | jdarrow@NetBSD.org | ||
| Jed Davis | jld@NetBSD.org | ||
| Matt DeBergalis | deberg@NetBSD.org | ||
| Arnaud Degroote | degroote@NetBSD.org | ||
| Rob Deker | deker@NetBSD.org | ||
| Chris G. Demetriou | cgd@NetBSD.org | ||
| Tracy Di Marco White | gendalia@NetBSD.org | ||
| Jaromír Dolecek | jdolecek@NetBSD.org | ||
| Andy Doran | ad@NetBSD.org | ||
| Roland Dowdeswell | elric@NetBSD.org | ||
| Emmanuel Dreyfus | manu@NetBSD.org | ||
| Matthias Drochner | drochner@NetBSD.org | ||
| Jun Ebihara | jun@NetBSD.org | ||
| Håvard Eidnes | he@NetBSD.org | ||
| Stoned Elipot | seb@NetBSD.org | ||
| Michael van Elst | mlelstv@NetBSD.org | ||
| Enami Tsugutomo | enami@NetBSD.org | ||
| Bernd Ernesti | veego@NetBSD.org | ||
| Erik Fair | fair@NetBSD.org | ||
| Gavan Fantom | gavan@NetBSD.org | ||
| Hauke Fath | hauke@NetBSD.org | ||
| Hubert Feyrer | hubertf@NetBSD.org | ||
| Jason R. Fink | jrf@NetBSD.org | ||
| Matt J. Fleming | mjf@NetBSD.org | ||
| Marty Fouts | marty@NetBSD.org | ||
| Liam J. Foy | liamjfoy@NetBSD.org | ||
| Matt Fredette | fredette@NetBSD.org | ||
| Thorsten Frueauf | frueauf@NetBSD.org | ||
| Castor Fu | castor@NetBSD.org | ||
| Ichiro Fukuhara | ichiro@NetBSD.org | ||
| Quentin Garnier | cube@NetBSD.org | ||
| Thomas Gerner | thomas@NetBSD.org | ||
| Simon J. Gerraty | sjg@NetBSD.org | ||
| Justin Gibbs | gibbs@NetBSD.org | ||
| Chris Gilbert | chris@NetBSD.org | ||
| Eric Gillespie | epg@NetBSD.org | ||
| Michael Graff | explorer@NetBSD.org | ||
| Brian C. Grayson | bgrayson@NetBSD.org | ||
| Matthew Green | mrg@NetBSD.org | ||
| Andreas Gustafsson | gson@NetBSD.org | ||
| Ulrich Habel | rhaen@NetBSD.org | ||
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | ||
| Adam Hamsik | haad@NetBSD.org | ||
| Juergen Hannken-Illjes | hannken@NetBSD.org | ||
| Charles M. Hannum | mycroft@NetBSD.org | ||
| Ben Harris | bjh21@NetBSD.org | ||
| Ross Harvey | ross@NetBSD.org | ||
| Eric Haszlakiewicz | erh@NetBSD.org | ||
| John Hawkinson | jhawk@NetBSD.org | ||
| HAMAJIMA Katsuomi | hamajima@NetBSD.org | ||
| HAYAKAWA Koichi | haya@NetBSD.org | ||
| John Heasley | heas@NetBSD.org | ||
| Geert Hendrickx | ghen@NetBSD.org | ||
| René Hexel | rh@NetBSD.org | ||
| Iain Hibbert | plunky@NetBSD.org | ||
| Kouichirou Hiratsuka | hira@NetBSD.org | ||
| Michael L. Hitch | mhitch@NetBSD.org | ||
| Jachym Holecek | freza@NetBSD.org | ||
| Christian E. Hopps | chopps@NetBSD.org | ||
| Ken Hornstein | kenh@NetBSD.org | ||
| Marc Horowitz | marc@NetBSD.org | ||
| Eduardo Horvath | eeh@NetBSD.org | ||
| Nick Hudson | skrll@NetBSD.org | ||
| Shell Hung | shell@NetBSD.org | ||
| Martin Husemann | martin@NetBSD.org | ||
| Dean Huxley | dean@NetBSD.org | ||
| Love Hörnquist Åstrand | lha@NetBSD.org | ||
| Bernardo Innocenti | bernie@NetBSD.org | ||
| Tetsuya Isaki | isaki@NetBSD.org | ||
| ITOH Yasufumi | itohy@NetBSD.org | ||
| IWAMOTO Toshihiro | toshii@NetBSD.org | ||
| Matthew Jacob | mjacob@NetBSD.org | ||
| Soren Jacobsen | snj@NetBSD.org | ||
| Lonhyn T. Jasinskyj | lonhyn@NetBSD.org | ||
| Darrin Jewell | dbj@NetBSD.org | ||
| Nicolas Joly | njoly@NetBSD.org | ||
| Chris Jones | cjones@NetBSD.org | ||
| Søren Jørvang | soren@NetBSD.org | ||
| Takahiro Kambe | taca@NetBSD.org | ||
| Antti Kantee | pooka@NetBSD.org | ||
| Masanori Kanaoka | kanaoka@NetBSD.org | ||
| Frank Kardel | kardel@NetBSD.org | ||
| Mattias Karlsson | keihan@NetBSD.org | ||
| KAWAMOTO Yosihisa | kawamoto@NetBSD.org | ||
| Mario Kemper | magick@NetBSD.org | ||
| Min Sik Kim | minskim@NetBSD.org | ||
| Thomas Klausner | wiz@NetBSD.org | ||
| Klaus Klein | kleink@NetBSD.org | ||
| John Klos | jklos@NetBSD.org | ||
| Wayne Knowles | wdk@NetBSD.org | ||
| Takayoshi Kochi | kochi@NetBSD.org | ||
| John Kohl | jtk@NetBSD.org | ||
| Daniel de Kok | daniel@NetBSD.org | ||
| Paul Kranenburg | pk@NetBSD.org | ||
| Lubomir Kundrak | lkundrak@NetBSD.org | ||
| Martti Kuparinen | martti@NetBSD.org | ||
| Kentaro A. Kurahone | kurahone@NetBSD.org | ||
| Kevin Lahey | kml@NetBSD.org | ||
| David Laight | dsl@NetBSD.org | ||
| Johnny C. Lam | jlam@NetBSD.org | ||
| Martin J. Laubach | mjl@NetBSD.org | ||
| Greg Lehey | grog@NetBSD.org | ||
| Ted Lemon | mellon@NetBSD.org | ||
| Christian Limpach | cl@NetBSD.org | ||
| Frank van der Linden | fvdl@NetBSD.org | ||
| Joel Lindholm | joel@NetBSD.org | ||
| Mike Long | mikel@NetBSD.org | ||
| Michael Lorenz | macallan@NetBSD.org | ||
| Warner Losh | imp@NetBSD.org | ||
| Tomasz Luchowski | zuntum@NetBSD.org | ||
| Federico Lupi | federico@NetBSD.org | ||
| Brett Lymn | blymn@NetBSD.org | ||
| Paul Mackerras | paulus@NetBSD.org | ||
| Anders Magnusson | ragge@NetBSD.org | ||
| MAEKAWA Masahide | gehenna@NetBSD.org | ||
| David Maxwell | david@NetBSD.org | ||
| Dan McMahill | dmcmahill@NetBSD.org | ||
| Gregory McGarry | gmcgarry@NetBSD.org | ||
| Jared D. McNeill | jmcneill@NetBSD.org | ||
| Neil J. McRae | neil@NetBSD.org | ||
| Perry Metzger | perry@NetBSD.org | ||
| Simas Mockevicius | symka@NetBSD.org | ||
| Juan Romero Pardines | xtraeme@NetBSD.org | ||
| Julio M. Merino Vidal | jmmv@NetBSD.org | ||
| Minoura Makoto | minoura@NetBSD.org | ||
| Luke Mewburn | lukem@NetBSD.org | ||
| der Mouse | mouse@NetBSD.org | ||
| Joseph Myers | jsm@NetBSD.org | ||
| Ken Nakata | kenn@NetBSD.org | ||
| Takeshi Nakayama | nakayama@NetBSD.org | ||
| Phil Nelson | phil@NetBSD.org | ||
| John Nemeth | jnemeth@NetBSD.org | ||
| Bob Nestor | rnestor@NetBSD.org | ||
| NISHIMURA Takeshi | nsmrtks@NetBSD.org | ||
| Tohru Nishimura | nisimura@NetBSD.org | ||
| NONAKA Kimihiro | nonaka@NetBSD.org | ||
| Takehiko NOZAKI | tnozaki@NetBSD.org | ||
| Tobias Nygren | tnn@NetBSD.org | ||
| OBATA Akio | obache@NetBSD.org | ||
| Jesse Off | joff@NetBSD.org | ||
| Tatoku Ogaito | tacha@NetBSD.org | ||
| OKANO Takayoshi | kano@NetBSD.org | ||
| Masaru Oki | oki@NetBSD.org | ||
| Atsushi Onoe | onoe@NetBSD.org | ||
| Greg Oster | oster@NetBSD.org | ||
| Jonathan Perkin | sketch@NetBSD.org | ||
| Herb Peyerl | hpeyerl@NetBSD.org | ||
| Matthias Pfaller | matthias@NetBSD.org | ||
| Chris Pinnock | cjep@NetBSD.org | ||
| Adrian Portelli | adrianp@NetBSD.org | ||
| Rui Paulo | rpaulo@NetBSD.org | ||
| Peter Postma | peter@NetBSD.org | ||
| Dante Profeta | dante@NetBSD.org | ||
| Chris Provenzano | proven@NetBSD.org | ||
| Niels Provos | provos@NetBSD.org | ||
| Mindaugas Rasiukevicius | rmind@NetBSD.org | ||
| Michael Rauch | mrauch@NetBSD.org | ||
| Marc Recht | recht@NetBSD.org | ||
| Darren Reed | darrenr@NetBSD.org | ||
| Jeremy C. Reed | reed@NetBSD.org | ||
| Antoine Reilles | tonio@NetBSD.org | ||
| Tyler R. Retzlaff | rtr@NetBSD.org | ||
| Scott Reynolds | scottr@NetBSD.org | ||
| Michael Richardson | mcr@NetBSD.org | ||
| Tim Rightnour | garbled@NetBSD.org | ||
| Alan Ritter | rittera@NetBSD.org | ||
| Jeff Rizzo | riz@NetBSD.org | ||
| Gordon Ross | gwr@NetBSD.org | ||
| Steve Rumble | rumble@NetBSD.org | ||
| Ilpo Ruotsalainen | lonewolf@NetBSD.org | ||
| Heiko W. Rupp | hwr@NetBSD.org | ||
| David Sainty | dsainty@NetBSD.org | ||
| SAITOH Masanobu | msaitoh@NetBSD.org | ||
| Kazuki Sakamoto | sakamoto@NetBSD.org | ||
| Curt Sampson | cjs@NetBSD.org | ||
| Wilfredo Sanchez | wsanchez@NetBSD.org | ||
| Ty Sarna | tsarna@NetBSD.org | ||
| SATO Kazumi | sato@NetBSD.org | ||
| Jan Schaumann | jschauma@NetBSD.org | ||
| Matthias Scheler | tron@NetBSD.org | ||
| Karl Schilke (rAT) | rat@NetBSD.org | ||
| Amitai Schlair | schmonz@NetBSD.org | ||
| Konrad Schroder | perseant@NetBSD.org | ||
| Georg Schwarz | schwarz@NetBSD.org | ||
| Lubomir Sedlacik | salo@NetBSD.org | ||
| Christopher SEKIYA | sekiya@NetBSD.org | ||
| Reed Shadgett | dent@NetBSD.org | ||
| John Shannon | shannonjr@NetBSD.org | ||
| Tim Shepard | shep@NetBSD.org | ||
| Takeshi Shibagaki | shiba@NetBSD.org | ||
| Naoto Shimazaki | igy@NetBSD.org | ||
| Takao Shinohara | shin@NetBSD.org | ||
| Takuya SHIOZAKI | tshiozak@NetBSD.org | ||
| Daniel Sieger | dsieger@NetBSD.org | ||
| Chuck Silvers | chs@NetBSD.org | ||
| Thor Lancelot Simon | tls@NetBSD.org | ||
| Jeff Smith | jeffs@NetBSD.org | ||
| Noriyuki Soda | soda@NetBSD.org | ||
| Wolfgang Solfrank | ws@NetBSD.org | ||
| T K Spindler | dogcow@NetBSD.org | ||
| SOMEYA Yoshihiko | someya@NetBSD.org | ||
| Bill Sommerfeld | sommerfeld@NetBSD.org | ||
| Jörg Sonnenberger | joerg@NetBSD.org | ||
| Ignatios Souvatzis | is@NetBSD.org | ||
| Bill Squier | groo@NetBSD.org | ||
| Jonathan Stone | jonathan@NetBSD.org | ||
| Bill Studenmund | wrstuden@NetBSD.org | ||
| Kevin Sullivan | sullivan@NetBSD.org | ||
| SUNAGAWA Keiki | kei@NetBSD.org | ||
| Kimmo Suominen | kim@NetBSD.org | ||
| Shin Takemura | takemura@NetBSD.org | ||
| TAMURA Kent | kent@NetBSD.org | ||
| Shin'ichiro TAYA | taya@NetBSD.org | ||
| Ian Lance Taylor | ian@NetBSD.org | ||
| Matt Thomas | matt@NetBSD.org | ||
| Jason Thorpe | thorpej@NetBSD.org | ||
| Christoph Toshok | toshok@NetBSD.org | ||
| Greg Troxel | gdt@NetBSD.org | ||
| Tsubai Masanari | tsubai@NetBSD.org | ||
| Izumi Tsutsui | tsutsui@NetBSD.org | ||
| UCHIYAMA Yasushi | uch@NetBSD.org | ||
| Masao Uebayashi | uebayasi@NetBSD.org | ||
| Shuichiro URATA | ur@NetBSD.org | ||
| Valeriy E. Ushakov | uwe@NetBSD.org | ||
| Todd Vierling | tv@NetBSD.org | ||
| Aymeric Vincent | aymeric@NetBSD.org | ||
| Paul Vixie | vixie@NetBSD.org | ||
| Mike M. Volokhov | mishka@NetBSD.org | ||
| Krister Walfridsson | kristerw@NetBSD.org | ||
| Lex Wennmacher | wennmach@NetBSD.org | ||
| Leo Weppelman | leo@NetBSD.org | ||
| Assar Westerlund | assar@NetBSD.org | ||
| Todd Whitesel | toddpw@NetBSD.org | ||
| Frank Wille | phx@NetBSD.org | ||
| Nathan Williams | nathanw@NetBSD.org | ||
| Rob Windsor | windsor@NetBSD.org | ||
| Dan Winship | danw@NetBSD.org | ||
| Arnaud Lacombe | alc@NetBSD.org | ||
| Jim Wise | jwise@NetBSD.org | ||
| Michael Wolfson | mbw@NetBSD.org | ||
| Steve Woodford | scw@NetBSD.org | ||
| Colin Wood | ender@NetBSD.org | ||
| YAMAMOTO Takashi | yamt@NetBSD.org | ||
| Yuji Yamano | yyamano@NetBSD.org | ||
| Reinoud Zandijk | reinoud@NetBSD.org | ||
| S.P.Zeidler | spz@NetBSD.org | ||
| Maria Zevenhoven | maria7@NetBSD.org | ||
| Christos Zoulas | christos@NetBSD.org | ||
|
| |||
| Other contributors: | |||
| Dave Burgess | burgess@cynjut.infonet.net | ||
| Brian R. Gaeke | brg@dgate.org | ||
| Brad Grantham | grantham@tenon.com | ||
| Lawrence Kesteloot | kesteloo@cs.unc.edu | ||
| Waldi Ravens | waldi@moacs.indiv.nl.net |
NetBSD 4.0 is dedicated to the memory of Jun-Ichiro "itojun" Hagino, who died in October 2007. Itojun was a member of the KAME project, which provided IPv6 and IPsec support; he was also a member of the NetBSD core team (the technical management for the project), and one of the Security Officers. Due to Itojun's efforts, NetBSD was the first open source operating system with a production ready IPv6 networking stack, which was included in the base system before many people knew what IPv6 was. We are grateful to have known and worked with Itojun, and we know that he will be missed. This release is therefore dedicated, with thanks, to his memory.
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