About this Document............................................1
What is NetBSD?................................................1
Upgrade path to NetBSD 1.5.3...................................2
Major Changes Between 1.5.2 and 1.5.3..........................2
Known Caveats with 1.5.3.......................................3
Major Changes Between 1.5.1 and 1.5.2..........................3
Major Changes Between 1.5 and 1.5.1............................4
Changes Between The NetBSD 1.4 and 1.5 Releases................6
Kernel......................................................6
Networking..................................................7
File system.................................................7
Security....................................................7
System administration and user tools........................8
Miscellaneous...............................................8
The Future of NetBSD...........................................9
Sources of NetBSD..............................................9
NetBSD 1.5.3 Release Contents..................................9
NetBSD/pc532 subdirectory structure........................11
Binary distribution sets...................................11
NetBSD/pc532 System Requirements and Supported Devices........13
Getting the NetBSD System on to Useful Media..................13
Preparing your System for NetBSD installation.................14
Installing the NetBSD System..................................14
The install procedure......................................14
Post installation steps.......................................17
Upgrading a previously-installed NetBSD System................19
Compatibility Issues With Previous NetBSD Releases............20
General issues.............................................20
Issues affecting an upgrade from NetBSD 1.4 or prior.......20
Using online NetBSD documentation.............................21
Administrivia.................................................21
Thanks go to..................................................22
We are........................................................24
Legal Mumbo-Jumbo.............................................28
The End.......................................................31
This document describes the installation procedure for
NetBSD1.5.3
on the
pc532
platform. It is available in four different formats titled
INSTALL.
ext,
where
.ext
is one of
.ps
, .html
, .more
,
or .txt
:
.ps
.html
.more
more(1)
and
less(1)
pager utility programs. This is the format in which the on-line
man
pages are generally presented.
.txt
You are reading the HTML version.
The NetBSD 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 thirty-one different system architectures featuring twelve distinct families of CPUs, and is being ported to more. The NetBSD1.5.3 release contains complete binary releases for fifteen different machine types. (The sixteen remaining are not fully supported at this time and are thus not part of the binary distribution. For information on them, please see the NetBSD web site at http://www.netbsd.org/.)
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code.
NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.
NetBSD 1.5.3 is an upgrade of NetBSD 1.5, 1.5.1, 1.5.2, and earlier major and maintenance releases of NetBSD.
The intermediate development versions of code available on the main trunk in our CVS repository (also known as ``NetBSD-current'') from after the point where the release cycle for 1.5 was started are designated by version identifiers such as 1.5A, 1.5B, etc. These identifiers do not designate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.5.3 can not be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD 1.5.3 kernel on such a system will probably result in problems.
Please also note that it is not possible to do a direct ``version'' comparison between any of the intermediate development versions mentioned above and 1.5.3 to determine if a given feature is present or absent in 1.5.3. The development of 1.5 and the subsequent maintenance releases is done on a separate branch in the CVS repository. The branch was created when the release cycle for 1.5 was started, and during the release cycle of 1.5 and its maintenance releases, selected fixes and enhancements have been imported from the main development trunk. So, there are features in 1.5.3 which were not in, e.g. 1.5B, and vice versa.
lpd(8)
has been fixed to deal with a security issue (SA2001-018).
ca(4)
to be replaced by
ld(4)
.
Drivers for the Mylex DAC960 management interface
and DPT/Adaptec I2O RAID management interface has also been added.
See
dpti(4)
and
mlxctl(8)
.
twe(4)
.
ep(4)
,
ex(4)
,
rtk(4)
,
sip(4)
,
ti(4)
,
tl(4)
,
and
wi(4)
.
rtk(4)
on CardBus has been added.
ne(4)
driver has been extended to support some more pcmcia cards.
pciide(4)
controllers added: HPT-370A, Acard ATP-850/860, and AMD-768.
Ultra-DMA 100 support added for CMD 0649.
emuxki(4)
.
esa(4)
.
siop(4)
driver.
sendmail(8)
has been upgraded to version 8.11.6.
In addition, many bugs have been fixed--more than 70 problems reported through our problem tracking system have been fixed, and several other non-reported problems have also been found and fixed. See the CHANGES-1.5.3 file for the complete list.
telnetd(8)
has been fixed to deal with a security issue (SA2001-012).
mount(8)
.
dump(8)
has been fixed to deal with a local security issue (SA2001-014).
Additionally, a few more bugs have been fixed. See the CHANGES-1.5.2 file for the complete list of changes.
an(4)
.
siop(4)
driver has improved in performance and robustness.
ifconfig(8)
.
vlan(4)
.
isp(4)
driver has been upgraded to (among other things) work on MacPPC.
lfs(4)
file system has again been substantially updated, but is still
experimental.
pciide(4)
driver.
Support for Intel 82801BAM controllers has also been added, and
handling of Ali controllers has been improved.
ex(4)
driver has added support for 3Com 3c555, 3c556 and 3c556B MiniPCI Ethernet
cards.
awacs(4)
.
sip(4)
driver has been fixed to properly support the dp83815, as found in
current Netgear FA311 10/100 cards.
ftpd(8)
has been updated to deal with two security issues (SA2000-018 and
SA2001-005).
ntpd(8)
has been updated to deal with a security issue (SA2001-004).
telnetd(8)
has been updated to deal with a security issue (SA2000-017).
ne(4)
.
dhclient(8)
,
among other things. Please note that the new
dhcpd(8)
forces you to configure a "ddns-update-style" of either
"ad-hoc", "interim" or "none".
kerberos(8)
implementation has been upgraded to version 0.3e.
tlp(4)
driver.
yds(4)
.
esm(4)
),
NeoMagic 256 (see
neo(4)
),
and Cirrus Logic CrystalClear PCI Audio CS4281 (see
clct(4)
)have been added.
In addition, many bugs have been fixed--more than 95 problems reported through our problem tracking system have been fixed, and some other non-reported problems have also been found and fixed. See the CHANGES-1.5.1 file for the complete list.
The NetBSD Packages Collection (pkgsrc) which is used to maintain, build, track dependencies, and maintain NetBSD-specific fixes to third-party programs, has received a major overhaul for NetBSD 1.5.1. Some highlights are:
Please note that at the moment, sysinst will not assist you in installing pre-built third-party binary packages or the pkgsrc system itself, so you will have to manually install packages using pkg_install or fetch and extract the pkgsrc.tgz tar file to get started.
Lastly, it should be noted that the X11 binaries shipped in NetBSD 1.5.3 is still based on XFree86 version 3.3.6. Several newer graphics cards are inadequately supported by that code base, but on the other hand support for several older graphics cards is not available in newer XFree86 code. NetBSD is in the process of moving to XFree86 version 4, and is currently maintaining both the XFree86 3.3.6 and the XFree86 version 4 code in the xsrc source set, and you may at compile time pick which sources to build and install. To ease installation, testing and use of the XFree86 version 4 code, a binary snapshot based on XFree86 version 4.0.3 will be made available for at least the i386 architecture shortly after the release of NetBSD 1.5.3.
The NetBSD1.5 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 userland enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems.
It is impossible to completely summarize over one year of development that went into the NetBSD1.5.3 release. Some highlights include:
ktruss(1)
.
swapctl(8)
.
pcap(3)
is incremented and you may need to recompile userland tools.
The KAME IPv6 part includes results from the unified-IPv6 effort.
/
)
on a RAID set.
rpc.lockd(8)
)
now works.
sysctl(3)
interfaces to various elements of process and system information,
allowing programs such as
ps(1)
,
dmesg(1)
and the like to operate without recompilation after kernel upgrades,
and remove the necessity to run setgid kmem (thus improving system
security).
sshd(8)
and
ssh(1)
now require
rnd(4)
kernel random number devices.
rc(8)
system startup and shutdown scripts to an
`rc.d'
mechanism, with separate control scripts for each service, and
appropriate dependency ordering provided by
rcorder(8)
.
postfix(1)
provided as alternative mail transport agent to
sendmail(8)
.
useradd(8)
,
usermod(8)
,
userdel(8)
,
groupadd(8)
,
groupmod(8)
,
and
groupdel(8)
added to the system.
/etc/login.conf
)
from
BSD/OS.
at(1)
and
w(1)
.
ftpd(8)
providing features found in larger and less secure FTP daemons,
such as user classes, connection limits, improved support for
virtual hosting, transfer statistics, transfer rate throttling,
and support for various IETF ftpext working group extensions.
ftp(1)
client has been improved even further, including
transfer rate throttling, improved URL support, command line uploads.
See the man page for details.
/usr/share/misc/style
)
to use ANSI C only (instead of K&R) and reflect current (best) practice,
and begin migrating the
NetBSD
source code to follow it.
curses(3)
library, including support for color.
file(1)
,
ipfilter(4)
,
ppp(4)
,
and
sendmail(8)
to the latest stable release.
Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue.
This is the sixth major release of NetBSD/pc532.
There are a few known problems in the pc532 port. They include:
The NetBSD Foundation has been incorporated as a non-profit organization. Its purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project.
The NetBSD Foundation will help improve the quality of NetBSD by:
We intend to begin narrowing the time delay between releases. Our ambition is to provide a full release every six to eight months.
We hope to support even more hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD.
We intend to continue our current practice of making the NetBSD-current development source available on a daily basis.
We intend to integrate free, positive changes from whatever sources submit them, providing that they are well thought-out and increase the usability of the system.
Above all, we hope to create a stable and accessible system, and to be
responsive to the needs and desires of
NetBSD
users, because it is for
and because of them that
NetBSD
exists.
Refer to
http://www.netbsd.org/Sites/net.html.
The root directory of the NetBSD1.5.3 release is organized as follows:
.../NetBSD-1.5.3/
CHANGES
LAST_MINUTE
MIRRORS
README.files
TODO
patches/
source/
In addition to the files and directories listed above, there is one
directory per architecture, for each of the architectures for which
NetBSD1.5.3
has a binary distribution.
There are also
README.export-control
files sprinkled liberally throughout the
distribution tree, which point out that there are some portions of the
distribution that may be subject to
export regulations of the United States, e.g.
code under
src/crypto
and
src/sys/crypto
.
It is your responsibility
to determine whether or not it is legal for you to export these portions
and to act accordingly.
The source distribution sets can be found in subdirectories of the
source
subdirectory of the distribution tree. They contain the
complete sources to the system. The source distribution sets
are as follows:
config(8)
;
and
dbsym(8)
.
All the above source sets are located in the
source/sets
subdirectory of the distribution tree.
The source sets are distributed as compressed tar files. They may be
unpacked into
/usr/src
with the command:
#
( cd / ; tar -zxpf - ) < set_name.tgz
The
sets/Split/
subdirectory contains split
versions of the source sets for those users who need to load the
source sets from floppy or otherwise need a split distribution. The
split sets are named
set_name.
xx
where
set_name
is the distribution set name, and
xx
is the sequence number of the file,
starting with
``aa''
for the first file in the distribution set, then
``ab''
for the next, and so on. All of these files except the last one
of each set should be exactly 240,640 bytes long. (The last file is
just long enough to contain the remainder of the data for that
distribution set.)
The split distributions may be reassembled and extracted with cat as follows:
#
cat set_name.?? | ( cd / ; tar -zxpf - )
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
BSDSUM
CKSUM
MD5
SYSVSUM
The MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of system can check the integrity of the release files.
pc532
subdirectory of the distribution:
.../NetBSD-1.5.3/pc532/
INSTALL.html
INSTALL.ps
INSTALL.txt
INSTALL.more
.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/
kernel/
netbsd.GENERIC.gz
sets/
installation/
floppy/
misc/
pc532/binary/sets
subdirectory
of the
NetBSD1.5.3
distribution tree, and are as follows:
/usr/include
)
and the various system libraries (except the shared
libraries, which are included as part of the
base
set). This set also includes the manual pages for
all of the utilities it contains, as well as the
system call and library manual pages.
/etc
and in several other places. This set
must
be installed if you are installing the system from scratch, but should
not
be used if you are upgrading.
GENERIC
kernel, named
/netbsd
.
You must
install this distribution set.
/usr/share
.
groff(1)
,
all related programs, and their manual pages.
NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. The binaries shipped with NetBSD 1.5.3 are based on XFree86 version 3.3.6. NetBSD is in the process of moving to XFree86 version 4, and the X source set actually contains source for both XFree86 3.3.6 and XFree86 4, and the ability to decide at compile-time which one to build and install. The X Window System binary sets distributed with NetBSD are:
The pc532 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 files are
/
-relative
and therefore are extracted
below
the current directory. That
is, 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 initial installation process on a pc532 without a previous NetBSD installation is supported by the following files:
floppy-144.fs
download.c
inst-11.fs
into memory via the pc532
ROM monitor.
The upgrade process is supported by having a copy of a 1.5.3 kernel available. This file is:
kern.tgz
DEFAULT
configuration file in
pc532/conf
.
NetBSD/pc532 1.5.3 runs on a PC532 computer. It supports a subset of the ``standard'' hardware to date. This is defined as:
NetBSD/pc532 currently expects the ROM monitor to be the ``autoboot monitor'' of Oct/Nov 1991. It includes support to set up auto booting of NetBSD, including a secondary boot program that the autoboot monitor will load that in turn loads the NetBSD kernel from a NetBSD file system. Source and ROM images of the autoboot monitor are located at ftp://ftp.cs.wwu.edu/pub/pc532/mon.auto.tar.gz
Most of the pc532 specific development of
NetBSD/pc532
was done on a
machine with 8 MB of memory. It should run with 4 MB of memory
although it may be slower.
The `standard' method of getting NetBSD/pc532 onto your pc532 is via the console terminal and using the downloading parts of the ROM monitor. As such, usually another computer has the distribution on disk and is connected via a serial line to your pc532's console port. A terminal connected to the attached host computer is used to access the pc532 console via a terminal program. The source for a program called download is part of this distribution. Download sends data to the ROM monitor over the serial line.
You may need to find and read the documentation about the ROM monitor download command and other low level comands.
Other methods of getting NetBSD/pc532 on your pc532 may include SCSI tape or SCSI floppy disk or cloning a disk on a system already running NetBSD/pc532.
If you have some operating system already running on your pc532,
you can use that OS to get
NetBSD/pc532
on a hard disk much easier than
with the ROM monitor.
NetBSD/pc532
was developed from Minix/pc532
until it was self hosting. You can run
NetBSD
and Minix or other OS
off the same disk.
The major preparation needed is to make sure you can recover any
current bits stored on your pc532. If you don't care about your
data on the disk, you don't need to do anything.
(If you already have NetBSD/pc532 installed and you only want to update your system, see the next section.)
To install
NetBSD/pc532,
there are several things you need to know.
First,
NetBSD
``autoconfig 's''
the SCSI devices.
floppy-144.fs
has only
support for disks configured into the kernel. Starting the search at
SCSI address 0, lun 0 and increasing, the first disk found will be
sd0
regardless of the address, the second will be sd1.
KLONDIKE
for example has the following devices installed:
sd0
sd1
sd2
sd3
cd0
st0
Only
sd0
-
sd3
are supported by the
floppy-144.fs
kernel.
Next you need to know what the install script wants to do. This install is script on the ram disk root that can do most of the work of configuring your disk.
sdXa:/netbsd
Replace X with your drive number. For KLONDIKE, X would be 2.
floppy-144.fs
into RAM.
floppy-144.fs
at
0x260000
0x3BE020
The boot program will ask you now for a kernel to load. Answer
md0a:/netbsd.gz
download.c
).
This program when used as
``download file''
will read the contents of the file and
output to standard output a byte sequence used by the pc532
ROM monitor to download a binary file into RAM. Using this
program on a computer connected to the pc532, one can
load a copy of
floppy-144.fs
into RAM at
0x260000
.
The boot sequence is now the same as with tape.
floppy-144.fs
will run the new
sysinst
utility as the standard
setup. It assumes a VT100 compatible terminal. If you don't want
to try using
sysinst
or you don't have a VT100, type f followed by
the return. Then following these instructions for installation.
If you want to use
sysinst,
read the i386 INSTALL instructions to
learn about
sysinst.
To help in this process, there is a program
factor
that is on the
floppy-144.fs
.
The usage is
factor number
and it lists the prime factors of number.
For example, with the 2053880 sector disk we got:
$
factor 2053880
2053880:
2
2
2
5
51347
Not many to choose from, so we tried ...
$
factor 2053820
2053820:
2
2
5
103
997
Now we'd like to get about a megabyte per track:
$
echo 2 * 997"|bc"
1994
Now we need the number of tracks (or cylinders):
$
echo 2 * 5 * 103"|bc"
1030
So we ended up choosing 1030 cylinders, 1 head, 1994 sectors/track. We ``lost'' only 60 sectors, but got a ``reasonable'' geometry.
/
),
your swap partition,
and then any other partitions you may want. For the
`other'
partitions, it will ask for a mount point. The mount point will
be
``relative to /''
and should not include the leading
`/'.
Also, if you do not want the partition to have newfs run on it (that is
it might be the last one and have a copy of
floppy-144.fs
)
enter
`NO'
to the mount point and it will not run
newfs
on the partition.
It will enter the partition into the disklabel.
/netbsd
.
You can get it to do it faster by pressing return.
If you are not using the autoboot monitor, you will have to figure out the starting sector of the boot images partition and manually load the NetBSD boot loader from the disk using the read command. If you would rather use the autoboot monitor you can get source and ROM images from the URL ftp://ftp.cs.wwu.edu/pub/pc532/mon.auto.tar.gz
/etc/resolv.conf
, ...
)
mount -rt cd9660 /dev/cd0a /mnt
Get the .tgz files from the cd-rom
/gz.files
and put them there. If you are
``short on space,''
you might want to load them and extract them one
at a time. A minimum installation is
base
and
etc.
It takes about 32 Megs installed + 20 Megs for the
base.tgz
.
/
.
For example, if your
*.tgz
files were in a directory
/gz.files
,
to extract
base.tgz
you would:
cd /
tar --unlink -zxpf /gz.files/base.tgz
Add v to the flags if you want a verbose extract. The --unlink is to make sure that the install versions of sh, init, ... are replaced by their proper versons in base.tgz. We think it is wise to include the --unlink for other things.
/etc
to
/etc.old
and then extract
etc.
You should extract
etc
for upgrades. For
``full''
installations, extract all files.
/etc
rc.conf
hosts
resolv.conf
ttys
gettytab
fstab
Now you can adjust the kernel's default baud rate to match your monitor's default baud rate. Do the following:
#
gdb -w /netbsd
(gdb)
set scndefaultrate = your_baud_rate
(gdb)
quit
where your_baud_rate is the actual value, 19200, 38400 or something slower than 9600. If you set scndefaultrate to something bogus, you'll probably not be able to reboot... So be carefull!
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-write. 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 filesystem 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.
Other files in
/etc
that may require modification or setting up include
/etc/mailer.conf
,
/etc/nsswitch.conf
,
and
/etc/wscons.conf
.
After reboot, you can log in as
root
at the login prompt. Unless you've set a password in
sysinst,
there
is no initial password. If you're using the machine in a
networked environment, you should create an account for yourself
(see below) and protect it and the
``root''
account with good passwords.
Unless you have connected an unusual terminal device as the console
you can just press
RETURN
when it prompts for
Terminal
type?
[...]
.
Use the
useradd(8)
command to add accounts to your system,
do not
edit
/etc/passwd
directly. See
useradd(8)
for more information on how to add a new user to the system.
If you have installed the X Window System, look at the files in
/usr/X11R6/lib/X11/doc
for information.
Don't forget to add
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstallation), both from source and precompiled binaries.
1.5.3/pc532/All
subdir. You can install them with the following commands:
# export PKG_PATH=\ ftp://ftp.netbsd.org/pub/NetBSD/packages/1.5.3/pc532/All\;\ ftp://ftp.netbsd.org/pub/NetBSD/packages/1.5/pc532/All # pkg_add -v tcsh # pkg_add -v cvs # pkg_add -v apache # pkg_add -v perl ...
The above commands will install the tcsh shell, the CVS source code management system, the Apache web server and the perl programming language as well as all the packages they depend on.
/usr/pkgsrc
(though other locations work fine), with the commands:
#
mkdir /usr/pkgsrc
#
( cd /usr/pkgsrc ; tar -zxpf - ) < pkgsrc.tar.gz
After extracting, then see the
README
file in the extraction directory (e.g.
/usr/pkgsrc/README
)
for more information.
/etc/mail/aliases
to forward root mail to the right place. Don't forget to run
newaliases(1)
afterwards.
/etc/mail/sendmail.cf
file will almost definitely need to be adjusted;
files aiding in this can be found in
/usr/share/sendmail
.
See the
README
file there for more information.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
#
man 5 filename
is likely to give you more information on these files.
The upgrade to NetBSD 1.5.3 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 at least base.tgz on disk and a copy of the proper netbsd.default. It will require quite a bit of disk space to do the upgrade.
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:
base.tgz
:
#
cd /
#
pax -zrvpe -f /gz.files/base.tgz
/etc
.
There may be changes to file formats depending on what version of
NetBSD/pc532
you are running.
netbsd.default
in
/
as the file
netbsd
.
netbsd.default
is a 9600 console line kernel. Read the last part of the new installation
part of these notes to find out how to change your default speed.)
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD1.5.3.
/etc/rc
modified to use
/etc/rc.d/*
Prior to
NetBSD1.5,
/etc/rc
was a traditional
BSD
style monolithic file; each discrete program or substem from
/etc/rc
and
/etc/netstart
has been moved into separate scripts in
/etc/rc.d/
.
At system startup,
/etc/rc
uses
rcorder(8)
to build a dependency list of the files in
/etc/rc.d
and then executes each script in turn with an argument of
`start'.
Many
rc.d
scripts won't start unless the appropriate
rc.conf(5)
entry in
/etc/rc.conf
is set to
`YES.'
At system shutdown,
/etc/rc.shutdown
uses
rcorder(8)
to build a dependency list of the files in
/etc/rc.d
that have a
``KEYWORD: shutdown''
line, reverses the resulting list, and then executes each script in turn
with an argument of
`stop'.
The following scripts support a specific shutdown method:
cron
,
inetd
,
local
,
and
xdm
.
Local and third-party scripts may be installed into
/etc/rc.d
as necessary.
Refer to the other scripts in that directory and
rc(8)
for more information on implementing
rc.d
scripts.
named(8)
leaks version information
Previous releases of
NetBSD
disabled a feature of
named(8)
where the version number of the server could be determined by remote clients.
This feature has not been disabled in
NetBSD1.5,
because there is a
named.conf(5)
option to change the version string:
option {
version "newstring";
};
sysctl(8)
pathname changed
sysctl(8)
is moved from
/usr/sbin/sysctl
to
/sbin/sysctl
.
If you have hardcoded references to the full pathname
(in shell scripts, for example)
please be sure to update those.
sendmail(8)
configuration file pathname changed
Due to
sendmail(8)
upgrade from 8.9.x to 8.10.x,
/etc/sendmail.cf
is moved to
/etc/mail/sendmail.cf
.
Also, the default
sendmail.cf(5)
refers different pathnames than before.
For example,
/etc/aliases
is now located at
/etc/mail/aliases
,
/etc/sendmail.cw
is now called
/etc/mail/local-host-names
,
and so forth.
If you have customized
sendmail.cf(5)
and friends, you will need to move the files to the new locations.
See
/usr/share/sendmail/README
for more information.
Documentation is available if you first install the manual
distribution set. Traditionally, the
``man pages''
(documentation) are denoted by
`name(section)
'.
Some examples of this are
intro(1)
,
man(1)
,
apropros(1)
,
passwd(1)
,
and
passwd(5)
.
The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8.
The man command is used to view the documentation on a topic, and is started by entering man[ section] topic. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the lowest numbered section name will be displayed. For instance, after logging in, enter
#
man passwd
to read the documentation for
passwd(1)
.
To view the documentation for
passwd(5)
,
enter
#
man 5 passwd
instead.
If you are unsure of what man page you are looking for, enter apropos subject-word
where subject-word is your topic of interest; a list of possibly related man pages will be displayed.
If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at majordomo@netbsd.org. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions.
There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@netbsd.org.
To report bugs, use the
send-pr(1)
command shipped with
NetBSD,
and fill in as much information about the problem as you can. Good
bug reports include lots of details. Additionally, bug reports can
be sent by mail to:
netbsd-bugs@netbsd.org.
Use of
send-pr(1)
is encouraged, however, because bugs reported with it
are entered into the
NetBSD
bugs database, and thus can't slip through
the cracks.
There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit http://www.netbsd.org/MailingLists/. If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed below).
If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-help@netbsd.org.
As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it.
Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick
for their ongoing work on BSD systems, support, and encouragement.
Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek
for answering lots of questions, fixing bugs, and doing the various work they've done.
Steve Allen Jason Birnschein Mason Loring Bliss Jason Brazile Mark Brinicombe David Brownlee Simon Burge Dave Burgess Ralph Campbell Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Scott Ellis Hubert Feyrer Castor Fu Greg Gingerich William Gnadt Michael Graff Guenther Grau Ross Harvey Charles M. Hannum Michael L. Hitch Kenneth Alan Hornstein Jordan K. Hubbard Søren Jørvang Scott Kaplan Noah M. Keiserman Harald Koerfgen John Kohl Chris Legrow Ted Lemon Norman R. McBride Neil J. McRae Perry E. Metzger Toru Nishimura Herb Peyerl Mike Price Dave Rand Michael Richardson Heiko W. Rupp Brad Salai Chuck Silvers Thor Lancelot Simon Bill Sommerfeld Paul Southworth Eric and Rosemary Spahr Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow Krister Walfridsson Jim Wise Reinoud Zandijk Christos Zoulas
AboveNet Communications, Inc. Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Brains Corporation, Japan Canada Connect Corporation Co-operative Research Centre for Enterprise Distributed Systems Technology Demon Internet, UK Digital Equipment Corporation Distributed Processing Technology Easynet, UK Free Hardware Foundation Innovation Development Enterprises of America Internet Software Consortium MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center Piermont Information Systems Inc. Precedence Technologies Ltd Salient Systems Inc. VMC Harald Frank, Germany Warped Communications, Inc. Whitecross Database Systems Ltd.
(in alphabetical order)
The NetBSD core group: | ||||||||
Jun-ichiro itojun Hagino | itojun@netbsd.org | |||||||
Frank van der Linden | fvdl@netbsd.org | |||||||
Luke Mewburn | lukem@netbsd.org | |||||||
Christos Zoulas | christos@netbsd.org | |||||||
| ||||||||
The portmasters (and their ports): | ||||||||
Mark Brinicombe | mark@netbsd.org | arm32 | ||||||
Simon Burge | simonb@netbsd.org | pmax | ||||||
Jeremy Cooper | jeremy@netbsd.org | sun3x | ||||||
Matt Fredette | fredette@netbsd.org | sun2 | ||||||
Ross Harvey | ross@netbsd.org | alpha | ||||||
Jun-ichiro itojun Hagino | itojun@netbsd.org | sh3 | ||||||
Ben Harris | bjh21@netbsd.org | arm26 | ||||||
Eduardo Horvath | eeh@netbsd.org | sparc64 | ||||||
Darrin Jewell | dbj@netbsd.org | next68k | ||||||
Søren Jørvang | soren@netbsd.org | cobalt | ||||||
Søren Jørvang | soren@netbsd.org | sgimips | ||||||
Wayne Knowles | wdk@netbsd.org | mipsco | ||||||
Paul Kranenburg | pk@netbsd.org | sparc | ||||||
Anders Magnusson | ragge@netbsd.org | vax | ||||||
Minoura Makoto | minoura@netbsd.org | x68k | ||||||
Phil Nelson | phil@netbsd.org | pc532 | ||||||
Tohru Nishimura | nisimura@netbsd.org | luna68k | ||||||
NONAKA Kimihiro | nonaka@netbsd.org | prep | ||||||
Scott Reynolds | scottr@netbsd.org | mac68k | ||||||
Kazuki Sakamoto | sakamoto@netbsd.org | bebox | ||||||
Noriyuki Soda | soda@netbsd.org | arc | ||||||
Wolfgang Solfrank | ws@netbsd.org | ofppc | ||||||
Ignatios Souvatzis | is@netbsd.org | amiga | ||||||
Jonathan Stone | jonathan@netbsd.org | pmax | ||||||
Shin Takemura | takemura@netbsd.org | hpcmips | ||||||
Jason Thorpe | thorpej@netbsd.org | alpha | ||||||
Jason Thorpe | thorpej@netbsd.org | hp300 | ||||||
Tsubai Masanari | tsubai@netbsd.org | macppc | ||||||
Tsubai Masanari | tsubai@netbsd.org | newsmips | ||||||
Izumi Tsutsui | tsutsui@netbsd.org | news68k | ||||||
Frank van der Linden | fvdl@netbsd.org | i386 | ||||||
Leo Weppelman | leo@netbsd.org | atari | ||||||
Nathan Williams | nathanw@netbsd.org | sun3 | ||||||
Steve Woodford | scw@netbsd.org | mvme68k | ||||||
| ||||||||
The NetBSD 1.5.3 Release Engineering team: | ||||||||
Chris G. Demetriou | cgd@netbsd.org | |||||||
Håvard Eidnes | he@netbsd.org | |||||||
Ted Lemon | mellon@netbsd.org | |||||||
Perry Metzger | perry@netbsd.org | |||||||
Curt Sampson | cjs@netbsd.org | |||||||
Jason Thorpe | thorpej@netbsd.org | |||||||
Todd Vierling | tv@netbsd.org | |||||||
| ||||||||
Developers and other contributors: | ||||||||
Nathan Ahlstrom | nra@NetBSD.org | |||||||
Steve Allen | wormey@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 | |||||||
Jason Beegan | jtb@netbsd.org | |||||||
Erik Berls | cyber@netbsd.org | |||||||
John Birrell | jb@netbsd.org | |||||||
Mason Loring Bliss | mason@netbsd.org | |||||||
Rafal Boni | rafal@netbsd.org | |||||||
Manuel Bouyer | bouyer@netbsd.org | |||||||
John Brezak | brezak@netbsd.org | |||||||
Allen Briggs | briggs@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 | |||||||
Dave Burgess | burgess@cynjut.infonet.net | |||||||
Robert Byrnes | byrnes@netbsd.org | |||||||
D'Arcy J.M. Cain | darcy@netbsd.org | |||||||
Dave Carrel | carrel@netbsd.org | |||||||
James Chacon | jmc@netbsd.org | |||||||
Bill Coldwell | billc@netbsd.org | |||||||
Julian Coleman | jdc@netbsd.org | |||||||
Chuck Cranor | chuck@netbsd.org | |||||||
Alistair Crooks | agc@netbsd.org | |||||||
Aidan Cully | aidan@netbsd.org | |||||||
Johan Danielsson | joda@netbsd.org | |||||||
Matt DeBergalis | deberg@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 | |||||||
Enami Tsugutomo | enami@netbsd.org | |||||||
Bernd Ernesti | veego@netbsd.org | |||||||
Erik Fair | fair@netbsd.org | |||||||
Hubert Feyrer | hubertf@netbsd.org | |||||||
Jason R. Fink | jrf@netbsd.org | |||||||
Thorsten Frueauf | frueauf@netbsd.org | |||||||
Castor Fu | castor@netbsd.org | |||||||
Ichiro Fukuhara | ichiro@netbsd.org | |||||||
Brian R. Gaeke | brg@dgate.org | |||||||
Thomas Gerner | thomas@netbsd.org | |||||||
Simon J. Gerraty | sjg@netbsd.org | |||||||
Justin Gibbs | gibbs@netbsd.org | |||||||
Adam Glass | glass@netbsd.org | |||||||
Michael Graff | explorer@netbsd.org | |||||||
Brad Grantham | grantham@tenon.com | |||||||
Brian C. Grayson | bgrayson@netbsd.org | |||||||
Matthew Green | mrg@netbsd.org | |||||||
Juergen Hannken-Illjes | hannken@netbsd.org | |||||||
Charles M. Hannum | mycroft@netbsd.org | |||||||
Eric Haszlakiewicz | erh@netbsd.org | |||||||
John Hawkinson | jhawk@netbsd.org | |||||||
HAYAKAWA Koichi | haya@netbsd.org | |||||||
René Hexel | rh@netbsd.org | |||||||
Michael L. Hitch | mhitch@netbsd.org | |||||||
Christian E. Hopps | chopps@netbsd.org | |||||||
Ken Hornstein | kenh@netbsd.org | |||||||
Marc Horowitz | marc@netbsd.org | |||||||
Nick Hudson | skrll@netbsd.org | |||||||
Martin Husemann | martin@netbsd.org | |||||||
Dean Huxley | dean@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 | |||||||
Lonhyn T. Jasinskyj | lonhyn@netbsd.org | |||||||
Chris Jones | cjones@netbsd.org | |||||||
Takahiro Kambe | taca@netbsd.org | |||||||
Antti Kantee | pooka@netbsd.org | |||||||
Masanori Kanaoka | kanaoka@netbsd.org | |||||||
KAWAMOTO Yosihisa | kawamoto@netbsd.org | |||||||
Mario Kemper | magick@netbsd.org | |||||||
Lawrence Kesteloot | kesteloo@cs.unc.edu | |||||||
Thomas Klausner | wiz@netbsd.org | |||||||
Klaus Klein | kleink@netbsd.org | |||||||
Wayne Knowles | wdk@netbsd.org | |||||||
John Kohl | jtk@netbsd.org | |||||||
Martti Kuparinen | martti@netbsd.org | |||||||
Kevin Lahey | kml@netbsd.org | |||||||
Johnny C. Lam | jlam@netbsd.org | |||||||
Martin J. Laubach | mjl@netbsd.org | |||||||
Ted Lemon | mellon@netbsd.org | |||||||
Joel Lindholm | joel@netbsd.org | |||||||
Mike Long | mikel@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 | |||||||
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 | |||||||
der Mouse | mouse@netbsd.org | |||||||
Joseph Myers | jsm@netbsd.org | |||||||
Ken Nakata | kenn@netbsd.org | |||||||
Bob Nestor | rnestor@netbsd.org | |||||||
NISHIMURA Takeshi | nsmrtks@netbsd.org | |||||||
NONAKA Kimihiro | nonaka@netbsd.org | |||||||
Jesse Off | joff@netbsd.org | |||||||
Tatoku Ogaito | tacha@netbsd.org | |||||||
Masaru Oki | oki@netbsd.org | |||||||
Atsushi Onoe | onoe@netbsd.org | |||||||
Greg Oster | oster@netbsd.org | |||||||
Herb Peyerl | hpeyerl@netbsd.org | |||||||
Matthias Pfaller | matthias@netbsd.org | |||||||
Chris Pinnock | cjep@netbsd.org | |||||||
Dante Profeta | dante@netbsd.org | |||||||
Chris Provenzano | proven@netbsd.org | |||||||
Michael Rauch | mrauch@netbsd.org | |||||||
Waldi Ravens | waldi@moacs.indiv.nl.net | |||||||
Darren Reed | darrenr@netbsd.org | |||||||
Michael Richardson | mcr@netbsd.org | |||||||
Tim Rightnour | garbled@netbsd.org | |||||||
Gordon Ross | gwr@netbsd.org | |||||||
Heiko W. Rupp | hwr@netbsd.org | |||||||
SAITOH Masanobu | msaitoh@netbsd.org | |||||||
Curt Sampson | cjs@netbsd.org | |||||||
Wilfredo Sanchez | wsanchez@netbsd.org | |||||||
Ty Sarna | tsarna@netbsd.org | |||||||
SATO Kazumi | sato@netbsd.org | |||||||
Matthias Scheler | tron@netbsd.org | |||||||
Karl Schilke (rAT) | rat@netbsd.org | |||||||
Konrad Schroder | perseant@netbsd.org | |||||||
Reed Shadgett | dent@netbsd.org | |||||||
Tim Shepard | shep@netbsd.org | |||||||
Takao Shinohara | shin@netbsd.org | |||||||
Takuya SHIOZAKI | tshiozak@netbsd.org | |||||||
Chuck Silvers | chs@netbsd.org | |||||||
Thor Lancelot Simon | tls@netbsd.org | |||||||
Jeff Smith | jeffs@netbsd.org | |||||||
SOMEYA Yoshihiko | someya@netbsd.org | |||||||
Bill Sommerfeld | sommerfeld@netbsd.org | |||||||
Bill Squier | groo@netbsd.org | |||||||
Bill Studenmund | wrstuden@netbsd.org | |||||||
Kevin Sullivan | sullivan@netbsd.org | |||||||
SUNAGAWA Keiki | kei@netbsd.org | |||||||
Kimmo Suominen | kim@netbsd.org | |||||||
TAMURA Kent | kent@netbsd.org | |||||||
Shin'ichiro TAYA | taya@netbsd.org | |||||||
Matt Thomas | matt@netbsd.org | |||||||
Christoph Toshok | toshok@netbsd.org | |||||||
UCHIYAMA Yasushi | uch@netbsd.org | |||||||
Shuichiro URATA | ur@netbsd.org | |||||||
Todd Vierling | tv@netbsd.org | |||||||
Aymeric Vincent | aymeric@netbsd.org | |||||||
Paul Vixie | vixie@netbsd.org | |||||||
Krister Walfridsson | kristerw@netbsd.org | |||||||
Lex Wennmacher | wennmach@netbsd.org | |||||||
Assar Westerlund | assar@netbsd.org | |||||||
Todd Whitesel | toddpw@netbsd.org | |||||||
Rob Windsor | windsor@netbsd.org | |||||||
Dan Winship | danw@netbsd.org | |||||||
Jim Wise | jwise@netbsd.org | |||||||
Michael Wolfson | mbw@netbsd.org | |||||||
Colin Wood | ender@netbsd.org | |||||||
YAMAMOTO Takashi | yamt@netbsd.org | |||||||
Yuji Yamano | yyamano@netbsd.org | |||||||
Reinoud Zandijk | reinoud@netbsd.org |
All product names mentioned herein are trademarks or registered trademarks of their respective owners.
The following notices are required to satisfy the license terms of the software that we have mentioned in this document:
This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by The NetBSD Foundation, Inc. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. This product includes software developed by the Computer Systems Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by Adam Glass and Charles Hannum. This product includes software developed by Adam Glass and Charles M. Hannum. This product includes software developed by Adam Glass. This product includes software developed by Alistair G. Crooks. This product includes software developed by Amancio Hasty and Roger Hardiman. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Bill Paul. This product includes software developed by Charles D. Cranor and Washington University. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum, by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Chris Provenzano. This product includes software developed by Christian E. Hopps. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christos Zoulas. This product includes software developed by David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes software developed by Eric S. Hvozda. This product includes software developed by Ezra Story. This product includes software developed by Gardner Buchanan. This product includes software developed by Gordon Ross. This product includes software developed by Gordon W. Ross and Leo Weppelman. This product includes software developed by Gordon W. Ross. This product includes software developed by Hauke Fath. This product includes software developed by HAYAKAWA Koichi. This product includes software developed by Hellmuth Michaelis and Joerg Wunsch. This product includes software developed by Herb Peyerl. This product includes software developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. This product includes software developed by Hubert Feyrer for the NetBSD Project. This product includes software developed by Iain Hibbert. This product includes software developed by Ian W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com/. This product includes software developed by Joachim Koenig-Baltes. This product includes software developed by Jochen Pohl for The NetBSD Project. This product includes software developed by John Polstra. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This product includes software developed by Kenneth Stailey. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Manuel Bouyer. This product includes software developed by Marc Horowitz. This product includes software developed by Mark Brinicombe. This product includes software developed by Mark Tinguely and Jim Lowe. This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This product includes software developed by Michael L. Hitch. This product includes software developed by Niels Provos. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Peter Galbavy. This product includes software developed by Philip A. Nelson. This product includes software developed by Rodney W. Grimes. This product includes software developed by Roland C. Dowdeswell. This product includes software developed by Rolf Grossmann. This product includes software developed by Scott Bartram. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed by Tatoku Ogaito for the NetBSD Project. This product includes software developed by Terrence R. Lambert. This product includes software developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software developed by Tohru Nishimura for the NetBSD Project. This product includes software developed by TooLs GmbH. This product includes software developed by Winning Strategies, Inc. This product includes software developed by Zembu Labs, Inc. This product includes software developed by the Center for Software Science at the University of Utah. This product includes software developed by the Computer Systems Laboratory at the University of Utah. This product includes software developed by the University of Calgary Department of Computer Science and its contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed for the FreeBSD project. This product includes software developed for the Internet Software Consortium by Ted Lemon. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Matthieu Herrb. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Piermont Information Systems Inc. This product includes software developed for the NetBSD Project by Ted Lemon. This product includes software developed by LAN Media Corporation and its contributors. This product includes software developed by Michael Graff for the NetBSD Project. This product includes software developed by Niklas Hallqvist, C Stone and Job de Haas. This product includes software developed by Eric Young (eay@mincom.oz.au). This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes software developed by the University of Oregon. This product includes software developed by the University of Southern California and/or Information Sciences Institute. This product includes software developed by Internet Initiative Japan Inc. This product includes software developed by Reinoud Zandijk.
This product includes software developed by the Alice Group.
This product includes software developed by Philip L. Budne.
This product includes software at the Helsinki University of Technology.
Some files have the following copyright:
Permission to use, copy, modify and distribute this software and its documentation is hereby granted, provided that both the copyright notice and this permission notice appear in all copies of the software, derivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation.
HELSINKI UNIVERSITY OF TECHNOLOGY ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS" CONDITION. HELSINKI UNIVERSITY OF TECHNOLOGY DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
At least one file contains:
All Rights Reserved
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both the copyright notice and this permission notice appear in supporting documentation, and that the name of OSF or Open Software Foundation not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
OSF DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL OSF BE LIABLE FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN ACTION OF CONTRACT, NEGLIGENCE, OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Some files have the following copyright:
Permission to use, copy, modify and distribute this software and its documentation is hereby granted, provided that both the copyright notice and this permission notice appear in all copies of the software, derivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation.
CARNEGIE MELLON AND HELSINKI UNIVERSITY OF TECHNOLOGY ALLOW FREE USE OF THIS SOFTWARE IN ITS "AS IS" CONDITION. CARNEGIE MELLON AND HELSINKI UNIVERSITY OF TECHNOLOGY DISCLAIM ANY LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
Carnegie Mellon requests users of this software to return to
Software Distribution Coordinator or Software.Distribution@CS.CMU.EDU School of Computer Science Carnegie Mellon University Pittsburgh PA 15213-3890
any improvements or extensions that they make and grant Carnegie Mellon the rights to redistribute these changes.
The IEEE floating point support in
/usr/src/sys/arch/pc532/fpu
has the following copyright:
Permission to use, copy, modify and distribute this software and its documentation is hereby granted, provided that both the copyright notice and this permission notice appear in all copies of the software, derivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation.
IAN DALL ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS" CONDITION. IAN DALL DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.