About this Document............................................2
What is NetBSD?................................................2
Changes Between The NetBSD 8.0 and 8.1 Releases................3
Features to be removed in a later release......................3
The NetBSD Foundation..........................................3
Sources of NetBSD..............................................3
NetBSD 8.1 Release Contents....................................3
NetBSD/sgimips subdirectory structure.......................5
Binary distribution sets....................................5
NetBSD/sgimips System Requirements and Supported Devices.......8
Supported machines..........................................8
Unsupported machines........................................8
Supported devices...........................................8
Unsupported devices.........................................9
Getting the NetBSD System on to Useful Media...................9
Preparing your System for NetBSD installation.................11
Installing the NetBSD System..................................12
Install via a bootable CD-ROM..............................13
Installation for diskless configurations...................13
Installation to local disk from the network................14
Once you've booted the diskimage...........................14
Running the sysinst installation program...................14
Introduction............................................14
General.................................................14
Quick install...........................................15
Booting NetBSD..........................................16
Network configuration...................................16
Installation drive selection and parameters.............16
Selecting which sets to install.........................16
Partitioning the disk...................................16
Preparing your hard disk................................17
Getting the distribution sets...........................17
Installation from CD-ROM................................18
Installation using FTP..................................18
Installation using NFS..................................18
Installation from an unmounted file system..............18
Installation from a local directory.....................19
Extracting the distribution sets........................19
Configure additional items..............................19
Finalizing your installation............................19
Post installation steps.......................................19
Upgrading a previously-installed NetBSD System................22
Compatibility Issues With Previous NetBSD Releases............22
Issues affecting an upgrade from NetBSD 5.x releases.......23
Issues affecting an upgrade from NetBSD 6.x releases.......23
Issues affecting an upgrade from NetBSD 7.x releases.......23
Using online NetBSD documentation.............................23
Administrivia.................................................24
Thanks go to..................................................25
We are........................................................25
Legal Mumbo-Jumbo.............................................32
The End.......................................................39
This document describes the installation procedure for
NetBSD
8.1 on the
sgimips
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 many different different system architectures (ports) across a variety of distinct CPU families, and is being ported to more. The NetBSD 8.1 release contains complete binary releases for most of these system architectures, with preliminary support for the others included in source form. Please see the NetBSD website 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, NetBSD would not exist.
The NetBSD 8.1 release is the first security/critical update of the NetBSD 8 release branch. It represents a selected subset of fixes deemed important for security or stability reasons. The complete list of changes can be found in the CHANGES-8.1: https://cdn.netbsd.org/pub/NetBSD/NetBSD-8.1/CHANGES-8.1 file in the top level directory of the NetBSD 8.1 release tree.
The release anouncements, status, updates and links to other resources can be found at https://www.netbsd.org/releases/formal-8/
dhclient(8)
in favor of
dhcpcd(8).
groff(1).
Man pages are now handled with
mandoc(1),
and
groff(1)
can still be found in pkgsrc as
textproc/groff.
rtsol(8)
and
rtsold(8).
The
NetBSD
Foundation is a tax exempt, not-for-profit 501(c)(3) corporation
that devotes itself to the traditional goals and Spirit of the
NetBSD
Project and owns the trademark of the word
``NetBSD''.
It supports the design, development, and adoption of
NetBSD
worldwide.
More information on the
NetBSD
Foundation, its composition, aims, and work can be found at:
http://www.NetBSD.org/foundation/
Refer to
http://www.NetBSD.org/mirrors/
The root directory of the NetBSD 8.1 release is organized as follows:
.../NetBSD-8.1/
CHANGESCHANGES-8.0CHANGES-8.1CHANGES.prevLAST_MINUTEREADME.filesimages/source/In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD 8.1 has a binary distribution.
The source distribution sets can be found in subdirectories of the
source
subdirectory of the distribution tree.
They contain the complete sources to the system.
The source distribution sets are as follows:
config(1)
utility.
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:
MD5SHA512The SHA512 digest is safer, but MD5 checksums are provided so that a wider range of operating systems can check the integrity of the release files.
sgimips
subdirectory of the distribution:
.../NetBSD-8.1/sgimips/.
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-GENERIC32_IP12.gznetbsd-GENERIC32_IP12.ecoff.gznetbsd-GENERIC32_IP2x.gznetbsd-GENERIC32_IP2x.ecoff.gznetbsd-GENERIC32_IP3x.gzsets/installation/netboot/sgimips/binary/sets
subdirectory
of the
NetBSD
8.1
distribution tree, and are as follows:
/usr/include)
and the various system libraries (except the shared
libraries, which are included as part of the
base
set).
This set also includes the manual pages for
all of the utilities it contains, as well as the
system call and library manual pages.
/etc
and in several other places.
This set
must
be installed if you are installing the system from scratch, but should
not
be used if you are upgrading.
GENERIC32_IP12
kernel (for R3000 Indigo, IRIS 4D/3x machines), named
/netbsd.
This set also contains an ECOFF kernel named
/netbsd.ecoff
that your system may need to boot.
GENERIC32_IP2x
kernel (for Indy, Indigo 2 and Challenge S/M machines), named
/netbsd.
This set also contains an ECOFF kernel named
/netbsd.ecoff
that your system may need to boot.
GENERIC32_IP3x
kernel (for O2), named
/netbsd.
You must install one of these distribution sets for your machine.
/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 X.Org. Binary sets for the X Window System are distributed with NetBSD. The sets are:
The sgimips 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 -xzpf
command from the root directory (
/
) of your system.
The following are included in the
sgimips/installation
directory:
diskimage/diskimage.gznetboot/diskimage.tgz
The following are included in the
sgimips/binary/kernel
directory:
netbsd-GENERIC32_IPxx.ecoff.gzGENERIC32_IPxx
kernel (gzipped). This kernel can be used when booting machines
whose PROMs do not understand the ELF binary format.
netbsd-INSTALL32_IPxx.gzINSTALL32_IPxx
kernel, which includes an embedded ramdisk with the installation tools.
netbsd-INSTALL32_IPxx.ecoff.gznetbsd-INSTALL32_IPxx kernel (also gzipped).
netbsd-INSTALL32_IPxx.symbols.gznetbsd-INSTALL32_IPxx.gz.
NetBSD/sgimips is aimed to run on MIPS-based computers manufactured by SGI.
Installation is supported from several media types, including:
The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the various media are outlined below.
binary/sets
and
sgimips/binary/sets.
(You only need to know this if you are mixing installer and installation
media from different versions - the installer will know the proper
default location for the sets it comes with).
Proceed to the instructions on installation.
Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
/etc/exports
file on the NFS server and resetting its mount daemon (mountd).
(Both of these actions will probably require superuser
privileges on the server.)
You need to know the numeric IP address of the NFS server, and, if you don't have DHCP available on your network and the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself.
Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
If you're making the tape on a UNIX-like system, the easiest way to do so is probably something like:
# tar -cf tape_device dist_sets
where
tape_device
is the name of the tape device that
represents the tape drive you're using.
This might be
/dev/rst0,
or something similar, but it will vary from system to system.
In the above example,
dist_sets
is a list of filenames corresponding to the distribution sets that you
wish to place on the tape.
For instance, to put the
kern-GENERIC, base, and etc
distributions on tape (the absolute minimum required for installation),
you would do the following:
# cd .../NetBSD-8.1
# cd sgimips/binary
# tar -cf tape_device kern-GENERIC.tgz base.tgz etc.tgz
Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
First and foremost, before beginning the installation process, make sure you have a reliable backup of any data (e.g., an old IRIX installation) you wish to preserve.
Booting NetBSD/sgimips for the first time is most commonly done from the network. You must set up DHCP, TFTP, and possibly NFS for the installation procedure to be successful. Although newer SGI bootproms can read ELF kernels directly from the network, others require that you boot an ECOFF version of the kernel. Attempting to boot an ELF kernel on a system with a PROM that only supports ECOFF binaries will result in the following message being displayed by the PROM:
Illegal f_magic number 0x7f45, expected MIPSELMAGIC or MIPSEBMAGIC.
You can convert the standard ELF
format kernel into an ECOFF kernel using the
objcopy
tool.
Note that some older bootproms have an interesting bug in reading the kernel via TFTP. They handle the port number as a signed entity, and can thus not connect to ports >32767. You can work around this problem on the TFTP server (given that it is a NetBSD host) by using ``sysctl'' to set ``net.inet.ip.anonportmin'' and ``net.inet.ip.anonportmax'' to more suitable values. For example:
# sysctl -w net.inet.ip.anonportmin=16384
# sysctl -w net.inet.ip.anonportmax=32767
# cu -l /dev/ttyXX
where XX is the serial port used on your remote machine (usually
/dev/tty00
or
/dev/tty01).
Enter the Command Monitor from the System Maintenance Menu. In
order to boot the kernel properly you also have to modify the PROM
environment with
> setenv console serial
Afterwards, just continue with the normal installation procedure.
To install or upgrade NetBSD, you need to first boot an installation program and then interact with the screen-menu program sysinst. The installation program actually consists of the NetBSD kernel plus an in-memory file system of utility programs.
The installation methods are:
You should familiarize yourself with the console PROM environment and the hardware configuration. A good place to study PROM tricks is the IRIX "prom" manual page. Be sure you know how to print the configuration of your machine, and how to boot from disk or network, as appropriate.
To boot from disk, use:
>> setenv systempartition scsi(0)disk(X)rdisk(0)partition(8)
>> setenv osloadpartition scsi(0)disk(X)rdisk(0)partition(0)
>> setenv osloadfilename netbsd
>> setenv osloadoptions auto
>> setenv osloader boot
For all drives (including all SCSI-2 drives), the kernel should correctly detect the disk geometry.
If you're installing NetBSD/sgimips for the first time it's a very good idea to pre-plan partition sizes for the disks onto which you're installing NetBSD. Changing the size of partitions after you've installed is difficult. If you do not have a spare bootable disk, it may be simpler to re-install NetBSD again from scratch.
To be able to boot from local disk an SGI Volume Header partition is required. This special partition is accessed by the PROM to load the NetBSD/sgimips boot program. The partition should be about 2 MB in size, but can be reduced somewhat. The minimum size can approach 150k, but this doesn't leave room for upgrade boot programs.
To install from a NetBSD/sgimips CD-ROM, enter the PROM command-line environment and execute one of the following commands, replacing X with the SCSI-ID of the CD-ROM:
(for most Indigo2 (IP22) and Indy (IP24) machines)
gunzip
program.
You must also decide which kernel you need to boot.
Because of differences in SGI hardware between different machines,
the kernel load addresses differ.
You will need GENERIC32_IP2x for the Indy and Indigo2,
GENERIC32_IP2x.ecoff for the Indigo (and Indy/Indigo2 machines with old PROMs),
and GENERIC32_IP3x for the O2.
server# gzip -d -c netbsd-GENERIC32_IP2x.gz > /tftpboot/netbsd-sgimips
or
server# gzip -d -c netbsd-GENERIC32_IP2x.ecoff.gz > /tftpboot/netbsd-sgimips
or
server# gzip -d -c netbsd-GENERIC32_IP2x.gz > /tftpboot/netbsd-sgimips
Note that your DHCP server must be configured to specify this file as the boot file for the client.
server# cd /export/client/mipseb
server# gzcat .../base.tgz | tar xvpf -
server# gzcat .../etc.tgz | tar xvpf -
[ repeat for all sets you wish to unpack ]
>> setenv SystemPartition bootp():
>> setenv netaddr your.ip.here.please
>> boot
The installation of your diskless NetBSD/sgimips system is now complete! You may now skip ahead to any post-installation instructions.
If the kernel has a
``.gz''
suffix, you must first uncompress it using the
gunzip
program.
As above, you must choose either the netbsd-INSTALL32_IP2x,
netbsd-INSTALL32_IP2x.ecoff, or netbsd-INSTALL32_IP3x kernel.
Note that your DHCP server must be configured to specify this file as the boot file for the client.
>> setenv SystemPartition bootp():
>> setenv netaddr your.ip.here.please
>> boot
tip(1)
or
cu(1)
connection running in an
xterm(1).
The system will then start the sysinst program.
Using sysinst, installing NetBSD is a relatively easy process. Still, you should read this document and have it available during the installation process. This document tries to be a good guide to the installation, and as such, covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use.
The following is a walk-through of the steps you will take while
installing
NetBSD
on your hard disk.
sysinst
is a menu driven program that guides you through the installation process.
Sometimes questions will be asked, and in many cases
the default answer will be displayed in brackets
(``[ ]'')
after the question.
If you wish to stop the installation, you may press
CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch by running the
/sysinst
program from the command prompt.
It is not necessary to reboot.
First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to the next section. This section describes a basic installation, using a CD / DVD as the install media.
.***********************************************.
* NetBSD-8.1 Install System *
* *
*>a: Install NetBSD to hard disk *
* b: Upgrade NetBSD on a hard disk *
* c: Re-install sets or install additional sets *
* d: Reboot the computer *
* e: Utility menu *
* f: Config menu *
* x: Exit Install System *
.***********************************************.
root
user when prompted by
sysinst,
logging in as
root
and setting a password should be your first task.
You are also advised to read
afterboot(8).
You may want to read the
boot messages, to notice your disk's name and capacity.
Its name will be something like
sd0
and the geometry will be
printed on a line that begins with its name.
As mentioned above, you may need your disk's geometry when creating
NetBSD's
partitions.
You will also need to know the name, to tell
sysinst
which disk to use.
The most important thing to know is that
sd0
is your first SCSI disk,
sd1
the second, etc.
Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus.
If you do not intend to use networking during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the Utility menu and select the Configure network option. If you only want to temporarily use networking during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response when asked to provide a server.
To start the installation, select Install NetBSD to hard disk from the main menu.
The first thing is to identify the disk on which you want to
install
NetBSD.
sysinst
will report a list of disks it finds
and ask you for your selection.
You should see disk names like
sd0
or
sd1.
The next step is to choose which distribution sets you wish to install. Options are provided for full, minimal, and custom installations. If you choose sets on your own, base, etc, and a kernel must be selected.
The partition table of the NetBSD part of a disk is called a disklabel. If your disk already has a disklabel written to it, you can choose Use existing partition sizes. Otherwise, select Set sizes of NetBSD partitions.
After you have chosen your partitions and their sizes (or if you opted to use the existing partitions), you will be presented with the layout of the NetBSD disklabel and given one more chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap partition has a special type called swap. Some partitions in the disklabel have a fixed purpose.
a/)
bcde-pe
is the partition mounted on
/usr,
but this is historical practice and not a fixed value.
You will then be asked to name your disk's disklabel. The default response will be ok for most purposes. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name.
You are now at the point of no return. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to proceed, select yes.
The install program will now label your disk and create the file systems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing the return key.
The NetBSD distribution consists of a number of sets that come in the form of gzipped tar files. At this point, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first transfer the sets to your hard disk, others will extract the sets directly.
For all these methods, the first step is to make the sets available for extraction. The sets can be made available in a few different ways. The following sections describe each of the methods. After reading about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'.
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM drive
(usually cd0)
and the directory name on the CD-ROM where the distribution files are.
sysinst will then check that the files are actually present in the specified location and proceed to the extraction of the sets.
To install using ftp, you first need to configure
your network setup if you haven't already done so.
sysinst
will help you with this, asking if you want to use DHCP.
If you do not use DHCP, you can enter network configuration
details yourself.
If you do not have DNS set up for the machine that you
are installing on, you can just press
RETURN
in answer to this question, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS, you will need to specify an IP address instead of a hostname for the ftp server.
sysinst will then transfer the set files from the remote site to your hard disk.
To install using NFS, you first need to configure
your network setup if you haven't already done so.
sysinst
will do this for you, asking you
if you want to use DHCP.
If you do not use DHCP, you can enter network configuration
details yourself.
If you do not have DNS set up for the machine that you
are installing on, you can just press
RETURN
in answer to this question, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e., correctly exported to your machine.
If you did not set up DNS, you will need to specify an IP address instead of a hostname for the NFS server.
In order to install from a local file system, you will
need to specify the device that the file system resides
on
(for example wd1e),
the type of the file system,
and the directory on the specified file system where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
If this is a CD-ROM installation, the device used will be the name for your CD-ROM player with partition letter 'a' (usually cd0a).
This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file system that is already accessible. sysinst will ask you for the name of this directory.
A progress bar will be displayed while the distribution sets are being extracted.
After all the files have been extracted, the device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files.
The next menu will allow you to select a number of additional items to configure, including the time zone that you're in, to make sure your clock has the right offset from UTC, the root user's shell, and the initial root password.
You can also enable installation of binary packages, which installs the
pkgin(1)
tool for managing binary packages for third-party software.
This will
feel familiar to users of package tools such as
apt-get
or
yum.
If you prefer to install third-party software from source, you can install
the
pkgsrc(7)
tree.
Finally, you can enable some daemons such as
sshd(8),
ntpd(8),
or
mdnsd(8).
Congratulations, you have successfully installed NetBSD 8.1. You can now reboot the machine and boot NetBSD from hard disk.
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. The most important steps are described below.
postinstall(8).
/etc/rc.conf
If you or the installation software haven't done any configuration of
/etc/rc.conf
(sysinst
normally 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).
When you have finished editing
/etc/rc.conf,
type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that may need to be set in
/etc/rc.conf
for a networked environment are
hostname
and possibly
defaultroute.
You may also need to add an
ifconfig_int
for your
<int>
network interface,
along the lines of
ifconfig_sq0="inet 192.0.2.123 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_sq0="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 networking,
DHCP can be used by setting
dhcpcd=YES
in
/etc/rc.conf.
After reboot, you can log in as
root
at the login prompt.
If you didn't set a password in
sysinst,
there
is no initial password.
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.
Use the
useradd(8)
command to add accounts to your system.
Do not
edit
/etc/passwd
directly! See
vipw(8)
and
pwd_mkdb(8)
if you want to edit the password database.
If you installed the X Window System, you may want to read the chapter about X in the NetBSD Guide: http://www.NetBSD.org/docs/guide/en/chap-x.html
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, pkgsrc. pkgsrc automatically handles any changes necessary to make the software run on NetBSD. This includes the retrieval and installation of any other packages the software may depend upon.
sgimips/8.1/All
subdir.
If you installed
pkgin(1)
in the
sysinst
post-installation configuration menu, you can use it to automatically install
binary packages over the network.
Assuming that
/usr/pkg/etc/pkgin/repositories.conf
is correctly configured, you can install them with the following commands:
# pkgin install tcsh # pkgin install bash # pkgin install perl # pkgin install apache # pkgin install kde # pkgin install firefox ...
/pub/pkgsrc
directory.
The above commands will install the Tenex-csh and Bourne Again shells, the Perl programming language, Apache web server, KDE desktop environment and the Firefox web browser as well as all the packages they depend on.
pkgsrc(7)
framework for compiling packages can be obtained by
retrieving the file
ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc.tar.gz.
It is typically extracted into
/usr/pkgsrc
(though other locations work fine) with the commands:
# cd /usr
# tar -zxpf pkgsrc.tar.gz
After extracting, see the
doc/pkgsrc.txt
file in the extraction directory (e.g.,
/usr/pkgsrc/doc/pkgsrc.txt)
for more information.
/etc/mail/aliases
to forward root mail to the right place.
Don't forget to run
newaliases(1)
afterwards.
/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 easiest way to upgrade to NetBSD 8.1 is with binaries, and that is the method documented here.
To do the upgrade, you must have one form of boot media available. You must also have at least the base and kern binary distribution sets available. Finally, you must have sufficient disk space available to install the new binaries. Since files already installed on the system are overwritten in place, you only need additional free space for files which weren't previously installed or to account for growth of the sets between releases.
Since upgrading involves replacing the kernel, boot blocks, 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 the NetBSD partition or on another operating system's partition on your disk before beginning the upgrade process.
The upgrade procedure is similar to an installation, but without the hard disk partitioning.
Fetching the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for help. File systems are checked before unpacking the sets.
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD
8.1
system.
However, that doesn't mean that you're finished with the upgrade process.
You will probably want to update the set of device nodes you have in
/dev.
If you've changed the contents of
/dev
by hand, you will need to be careful about this, but if
not, you can just cd into
/dev,
and run the command:
# sh MAKEDEV all
sysinst
will attempt to merge the settings stored in your
/etc
directory with the new version of
NetBSD
using the
postinstall(8)
utility.
However,
postinstall(8)
is only able to deal with changes that are easily automated.
It is recommended that you use the
etcupdate(8)
tool to merge any remaining configuration changes.
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 8.1.
Note that sysinst will automatically invoke
postinstall fix
See the section below on upgrading from NetBSD 6.x and 7.x as well.
The following users need to be created:
The following groups need to be created:
The implementation of SHA2-HMAC in KAME_IPSEC as used in NetBSD 5.0 and before did not comply with current standards. FAST_IPSEC does, with the result that old and new systems cannot communicate over IPSEC if one of the affected authentication algorithms (hmac_sha256, hmac_sha384, hmac_sha512) is used.
See the section on upgrading from NetBSD 7.x as well
The following user needs to be created:
The following groups need to be created:
The following user needs to be created:
The following groups need to be created:
Documentation is available if you installed the manual
distribution set.
Traditionally, the
``man pages''
(documentation) are denoted by
`name(section)'.
Some examples of this are
intro(1),
man(1),
apropos(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. See http://www.NetBSD.org/mailinglists/ for details.
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.
Bugs also can be submitted and queried with the web interface at http://www.NetBSD.org/support/send-pr.html
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 NetBSD, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-users@NetBSD.org.
As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it. 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 work on BSD systems, support, and encouragement.
(in alphabetical order)
| The NetBSD core group: | |||
| Alistair Crooks | agc@NetBSD.org | ||
| Matthew Green | mrg@NetBSD.org | ||
| Martin Husemann | martin@NetBSD.org | ||
| Chuck Silvers | chs@NetBSD.org | ||
| Matt Thomas | matt@NetBSD.org | ||
| YAMAMOTO Takashi | yamt@NetBSD.org | ||
| Christos Zoulas | christos@NetBSD.org | ||
|
| |||
| The portmasters (and their ports): | |||
| Reinoud Zandijk | reinoud | acorn32 | |
| Matt Thomas | matt | alpha | |
| Ignatios Souvatzis | is | amiga | |
| Ignatios Souvatzis | is | amigappc | |
| Noriyuki Soda | soda | arc | |
| Julian Coleman | jdc | atari | |
| Matthias Drochner | drochner | cesfic | |
| Erik Berls | cyber | cobalt | |
| Antti Kantee | pooka | emips | |
| Simon Burge | simonb | evbmips | |
| Steve Woodford | scw | evbppc | |
| Izumi Tsutsui | tsutsui | ews4800mips | |
| Izumi Tsutsui | tsutsui | hp300 | |
| Nick Hudson | skrll | hppa | |
| Valeriy E. Ushakov | uwe | hpcsh | |
| Matt Thomas | matt | ibmnws | |
| Gavan Fantom | gavan | iyonix | |
| Valeriy E. Ushakov | uwe | landisk | |
| Izumi Tsutsui | tsutsui | luna68k | |
| Scott Reynolds | scottr | mac68k | |
| Michael Lorenz | macallan | macppc | |
| Steve Woodford | scw | mvme68k | |
| Steve Woodford | scw | mvmeppc | |
| Matt Thomas | matt | netwinder | |
| Izumi Tsutsui | tsutsui | news68k | |
| Tim Rightnour | garbled | ofppc | |
| Simon Burge | simonb | pmax | |
| Tim Rightnour | garbled | prep | |
| Tim Rightnour | garbled | rs6000 | |
| Tohru Nishimura | nisimura | sandpoint | |
| Simon Burge | simonb | sbmips | |
| Søren Jørvang | soren | sgimips | |
| SAITOH Masanobu | msaitoh | sh3 | |
| Martin Husemann | martin | sparc64 | |
| Anders Magnusson | ragge | vax | |
| NISHIMURA Takeshi | nsmrtks | x68k | |
| Manuel Bouyer | bouyer | xen | |
|
| |||
| The NetBSD 8.1 Release Engineering team: | |||
| Stephen Borrill | sborrill@NetBSD.org | ||
| Manuel Bouyer | bouyer@NetBSD.org | ||
| David Brownlee | abs@NetBSD.org | ||
| Julian Coleman | jdc@NetBSD.org | ||
| Alistair G. Crooks | agc@NetBSD.org | ||
| Håvard Eidnes | he@NetBSD.org | ||
| Martin Husemann | martin@NetBSD.org | ||
| Soren Jacobsen | snj@NetBSD.org | ||
| Phil Nelson | phil@NetBSD.org | ||
| Jeremy C. Reed | reed@NetBSD.org | ||
| Jeff Rizzo | riz@NetBSD.org | ||
| SAITOH Masanobu | msaitoh@NetBSD.org | ||
|
| |||
| NetBSD Developers: | |||
| Hikaru Abe | hikaru@NetBSD.org | ||
| 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 | ||
| Zafer Aydogan | zafer@NetBSD.org | ||
| Christoph Badura | bad@NetBSD.org | ||
| Marc Balmer | mbalmer@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 | ||
| Erik Berls | cyber@NetBSD.org | ||
| Hiroyuki Bessho | bsh@NetBSD.org | ||
| John Birrell | jb@NetBSD.org | ||
| Rafal Boni | rafal@NetBSD.org | ||
| Stephen Borrill | sborrill@NetBSD.org | ||
| Sean Boudreau | seanb@NetBSD.org | ||
| Manuel Bouyer | bouyer@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 | ||
| 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 | ||
| Taylor R. Campbell | riastradh@NetBSD.org | ||
| Daniel Carosone | dan@NetBSD.org | ||
| Dave Carrel | carrel@NetBSD.org | ||
| James Chacon | jmc@NetBSD.org | ||
| Mihai Chelaru | kefren@NetBSD.org | ||
| Aleksey Cheusov | cheusov@NetBSD.org | ||
| Bill Coldwell | billc@NetBSD.org | ||
| Sean Cole | scole@NetBSD.org | ||
| Julian Coleman | jdc@NetBSD.org | ||
| Marcus Comstedt | marcus@NetBSD.org | ||
| Jeremy Cooper | jeremy@NetBSD.org | ||
| Thomas Cort | tcort@NetBSD.org | ||
| Chuck Cranor | chuck@NetBSD.org | ||
| Alistair Crooks | agc@NetBSD.org | ||
| Masatake Daimon | pho@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 | ||
| Felix Deichmann | flxd@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 | ||
| Steven Drake | sbd@NetBSD.org | ||
| Emmanuel Dreyfus | manu@NetBSD.org | ||
| Matthias Drochner | drochner@NetBSD.org | ||
| Jun Ebihara | jun@NetBSD.org | ||
| Elad Efrat | elad@NetBSD.org | ||
| Håvard Eidnes | he@NetBSD.org | ||
| Jaime A Fournier | ober@NetBSD.org | ||
| Stoned Elipot | seb@NetBSD.org | ||
| Michael van Elst | mlelstv@NetBSD.org | ||
| Robert Elz | kre@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 | ||
| Hisashi Todd Fujinaka | htodd@NetBSD.org | ||
| Makoto Fujiwara | mef@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 | ||
| Brian Ginsbach | ginsbach@NetBSD.org | ||
| Oliver V. Gould | ver@NetBSD.org | ||
| Paul Goyette | pgoyette@NetBSD.org | ||
| Michael Graff | explorer@NetBSD.org | ||
| Matthew Green | mrg@NetBSD.org | ||
| Andreas Gustafsson | gson@NetBSD.org | ||
| Ulrich Habel | rhaen@NetBSD.org | ||
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | ||
| HAMAJIMA Katsuomi | hamajima@NetBSD.org | ||
| Adam Hamsik | haad@NetBSD.org | ||
| Juergen Hannken-Illjes | hannken@NetBSD.org | ||
| Charles M. Hannum | mycroft@NetBSD.org | ||
| Yorick Hardy | yhardy@NetBSD.org | ||
| Ben Harris | bjh21@NetBSD.org | ||
| Kenichi Hashimoto | hkenken@NetBSD.org | ||
| Eric Haszlakiewicz | erh@NetBSD.org | ||
| John Hawkinson | jhawk@NetBSD.org | ||
| Emile Heitor | imil@NetBSD.org | ||
| John Heasley | heas@NetBSD.org | ||
| Lars Heidieker | para@NetBSD.org | ||
| Geert Hendrickx | ghen@NetBSD.org | ||
| Wen Heping | wen@NetBSD.org | ||
| René Hexel | rh@NetBSD.org | ||
| Iain Hibbert | plunky@NetBSD.org | ||
| Kouichirou Hiratsuka | hira@NetBSD.org | ||
| Michael L. Hitch | mhitch@NetBSD.org | ||
| Ádám Hóka | ahoka@NetBSD.org | ||
| Jachym Holecek | freza@NetBSD.org | ||
| David A. Holland | dholland@NetBSD.org | ||
| Christian E. Hopps | chopps@NetBSD.org | ||
| Daniel Horecki | morr@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 | ||
| Darran Hunt | darran@NetBSD.org | ||
| Martin Husemann | martin@NetBSD.org | ||
| Dean Huxley | dean@NetBSD.org | ||
| Love Hörnquist Åstrand | lha@NetBSD.org | ||
| Roland Illig | rillig@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 | ||
| Sevan Janiyan | sevan@NetBSD.org | ||
| Lonhyn T. Jasinskyj | lonhyn@NetBSD.org | ||
| Darrin Jewell | dbj@NetBSD.org | ||
| Nicolas Joly | njoly@NetBSD.org | ||
| Søren Jørvang | soren@NetBSD.org | ||
| Takahiro Kambe | taca@NetBSD.org | ||
| Antti Kantee | pooka@NetBSD.org | ||
| Frank Kardel | kardel@NetBSD.org | ||
| KAWAMOTO Yosihisa | kawamoto@NetBSD.org | ||
| Min Sik Kim | minskim@NetBSD.org | ||
| KIYOHARA Takashi | kiyohara@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 | ||
| Mateusz Kocielski | shm@NetBSD.org | ||
| Jonathan A. Kollasch | jakllsch@NetBSD.org | ||
| Joseph Koshy | jkoshy@NetBSD.org | ||
| Radoslaw Kujawa | rkujawa@NetBSD.org | ||
| Jochen Kunz | jkunz@NetBSD.org | ||
| Martti Kuparinen | martti@NetBSD.org | ||
| Arnaud Lacombe | alc@NetBSD.org | ||
| Kevin Lahey | kml@NetBSD.org | ||
| David Laight | dsl@NetBSD.org | ||
| Johnny C. Lam | jlam@NetBSD.org | ||
| Guillaume Lasmayous | gls@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 | ||
| Tonnerre Lombard | tonnerre@NetBSD.org | ||
| Mike Long | mikel@NetBSD.org | ||
| Sergio Lopez | slp@NetBSD.org | ||
| Michael Lorenz | macallan@NetBSD.org | ||
| Warner Losh | imp@NetBSD.org | ||
| Tomasz Luchowski | zuntum@NetBSD.org | ||
| Federico Lupi | federico@NetBSD.org | ||
| Palle Lyckegaard | palle@NetBSD.org | ||
| Brett Lymn | blymn@NetBSD.org | ||
| MAEKAWA Masahide | gehenna@NetBSD.org | ||
| Anders Magnusson | ragge@NetBSD.org | ||
| Anthony Mallet | tho@NetBSD.org | ||
| John Marino | marino@NetBSD.org | ||
| Roy Marples | roy@NetBSD.org | ||
| Pedro Martelletto | pedro@NetBSD.org | ||
| Cherry G. Mathew | cherry@NetBSD.org | ||
| David Maxwell | david@NetBSD.org | ||
| Gregory McGarry | gmcgarry@NetBSD.org | ||
| Dan McMahill | dmcmahill@NetBSD.org | ||
| Jared D. McNeill | jmcneill@NetBSD.org | ||
| Neil J. McRae | neil@NetBSD.org | ||
| Julio M. Merino Vidal | jmmv@NetBSD.org | ||
| Perry Metzger | perry@NetBSD.org | ||
| Luke Mewburn | lukem@NetBSD.org | ||
| Jean-Yves Migeon | jym@NetBSD.org | ||
| Brook Milligan | brook@NetBSD.org | ||
| Minoura Makoto | minoura@NetBSD.org | ||
| Simas Mockevicius | symka@NetBSD.org | ||
| Ryosuke Moro | szptvlfn@NetBSD.org | ||
| der Mouse | mouse@NetBSD.org | ||
| Youri Mouton | youri@NetBSD.org | ||
| Constantine A. Murenin | cnst@NetBSD.org | ||
| Joseph Myers | jsm@NetBSD.org | ||
| Tuomo Mäkinen | tjam@NetBSD.org | ||
| Zoltán Arnold NAGY | zoltan@NetBSD.org | ||
| Kengo NAKAHARA | knakahara@NetBSD.org | ||
| Ken Nakata | kenn@NetBSD.org | ||
| Takeshi Nakayama | nakayama@NetBSD.org | ||
| Alexander Nasonov | alnsn@NetBSD.org | ||
| Phil Nelson | phil@NetBSD.org | ||
| John Nemeth | jnemeth@NetBSD.org | ||
| Lourival Pereira Vieira Neto | lneto@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 | ||
| Rin Okuyama | rin@NetBSD.org | ||
| Ryo ONODERA | ryoon@NetBSD.org | ||
| Atsushi Onoe | onoe@NetBSD.org | ||
| Greg Oster | oster@NetBSD.org | ||
| Ryota Ozaki | ozaki-r@NetBSD.org | ||
| Jonathan Perkin | sketch@NetBSD.org | ||
| Fredrik Pettai | pettai@NetBSD.org | ||
| Herb Peyerl | hpeyerl@NetBSD.org | ||
| Matthias Pfaller | matthias@NetBSD.org | ||
| Chris Pinnock | cjep@NetBSD.org | ||
| Adrian Portelli | adrianp@NetBSD.org | ||
| Pierre Pronchery | khorben@NetBSD.org | ||
| Chris Provenzano | proven@NetBSD.org | ||
| Maya Rashish | maya@NetBSD.org | ||
| Mindaugas Rasiukevicius | rmind@NetBSD.org | ||
| Nils Ratusznik | nils@NetBSD.org | ||
| Michael Rauch | mrauch@NetBSD.org | ||
| Marc Recht | recht@NetBSD.org | ||
| Darren Reed | darrenr@NetBSD.org | ||
| Jeremy C. Reed | reed@NetBSD.org | ||
| Jens Rehsack | sno@NetBSD.org | ||
| Antoine Reilles | tonio@NetBSD.org | ||
| Tyler R. Retzlaff | rtr@NetBSD.org | ||
| Scott Reynolds | scottr@NetBSD.org | ||
| Tim Rightnour | garbled@NetBSD.org | ||
| Jeff Rizzo | riz@NetBSD.org | ||
| Hans Rosenfeld | hans@NetBSD.org | ||
| Steve Rumble | rumble@NetBSD.org | ||
| Rumko | rumko@NetBSD.org | ||
| Jukka Ruohonen | jruoho@NetBSD.org | ||
| Kamil Rytarowski | kamil@NetBSD.org | ||
| Blair J. Sadewitz | bjs@NetBSD.org | ||
| David Sainty | dsainty@NetBSD.org | ||
| SAITOH Masanobu | msaitoh@NetBSD.org | ||
| Kazuki Sakamoto | sakamoto@NetBSD.org | ||
| Guilherme Salazar | salazar@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 | ||
| Silke Scheler | silke@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 | ||
| Naoto Shimazaki | igy@NetBSD.org | ||
| Ryo Shimizu | ryo@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 | ||
| Nathanial Sloss | nat@NetBSD.org | ||
| Jeff Smith | jeffs@NetBSD.org | ||
| Noriyuki Soda | soda@NetBSD.org | ||
| Wolfgang Solfrank | ws@NetBSD.org | ||
| Jörg Sonnenberger | joerg@NetBSD.org | ||
| Ignatios Souvatzis | is@NetBSD.org | ||
| T K Spindler | dogcow@NetBSD.org | ||
| Matthew Sporleder | mspo@NetBSD.org | ||
| Bill Squier | groo@NetBSD.org | ||
| Adrian Steinmann | ast@NetBSD.org | ||
| Bill Studenmund | wrstuden@NetBSD.org | ||
| Hiroki Suenaga | hsuenaga@NetBSD.org | ||
| Kevin Sullivan | sullivan@NetBSD.org | ||
| Kimmo Suominen | kim@NetBSD.org | ||
| Grégoire Sutre | gsutre@NetBSD.org | ||
| Sergey Svishchev | shattered@NetBSD.org | ||
| Robert Swindells | rjs@NetBSD.org | ||
| Leonardo Taccari | leot@NetBSD.org | ||
| Shin Takemura | takemura@NetBSD.org | ||
| TAMURA Kent | kent@NetBSD.org | ||
| Shin'ichiro TAYA | taya@NetBSD.org | ||
| Hasso Tepper | hasso@NetBSD.org | ||
| Matt Thomas | matt@NetBSD.org | ||
| Jason Thorpe | thorpej@NetBSD.org | ||
| Hiroshi Tokuda | hiroshi@NetBSD.org | ||
| Christoph Toshok | toshok@NetBSD.org | ||
| Tamás Tóth | ttoth@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 | ||
| Maxime Villard | maxv@NetBSD.org | ||
| Aymeric Vincent | aymeric@NetBSD.org | ||
| Paul Vixie | vixie@NetBSD.org | ||
| Mike M. Volokhov | mishka@NetBSD.org | ||
| Krister Walfridsson | kristerw@NetBSD.org | ||
| Mark Weinem | weinem@NetBSD.org | ||
| Lex Wennmacher | wennmach@NetBSD.org | ||
| Leo Weppelman | leo@NetBSD.org | ||
| Assar Westerlund | assar@NetBSD.org | ||
| Sebastian Wiedenroth | wiedi@NetBSD.org | ||
| Frank Wille | phx@NetBSD.org | ||
| Nathan Williams | nathanw@NetBSD.org | ||
| Rob Windsor | windsor@NetBSD.org | ||
| Jim Wise | jwise@NetBSD.org | ||
| Colin Wood | ender@NetBSD.org | ||
| Steve Woodford | scw@NetBSD.org | ||
| YAMAMOTO Takashi | yamt@NetBSD.org | ||
| Abhinav Upadhyay | abhinav@NetBSD.org | ||
| Yuji Yamano | yyamano@NetBSD.org | ||
| David Young | dyoung@NetBSD.org | ||
| Arnaud Ysmal | stacktic@NetBSD.org | ||
| Reinoud Zandijk | reinoud@NetBSD.org | ||
| S.P.Zeidler | spz@NetBSD.org | ||
| Tim Zingelman | tez@NetBSD.org | ||
| Christos Zoulas | christos@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:
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.
In the following statement, "This software" refers to the parallel port driver:
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 ALLOWS FREE USE OF THIS SOFTWARE IN ITS
CONDITION. CARNEGIE MELLON DISCLAIMS 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
any improvements or extensions that they make and grant Carnegie the
rights to redistribute these changes.
Some files have the following copyright:
Author: Chris G. Demetriou
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 requests users of this software to return to
any improvements or extensions that they make and grant Carnegie the
rights to redistribute these changes.
Some files have the following copyright:
Some files have the following copyright:
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 appear in all copies. Stanford University
makes no representations about the suitability of this
software for any purpose. It is provided "as is"
without express or implied warranty.
Copyright (c) 1991,1990,1989 Carnegie Mellon University
All Rights Reserved.
Software Distribution Coordinator or Software.Distribution@CS.CMU.EDU
School of Computer Science
Carnegie Mellon University
Pittsburgh PA 15213-3890
All rights reserved.
CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND
FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
Software Distribution Coordinator or Software.Distribution@CS.CMU.EDU
School of Computer Science
Carnegie Mellon University
Pittsburgh PA 15213-3890
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.
Digital Equipment Corporation makes no representations about the
suitability of this software for any purpose. It is provided "as is"
without express or implied warranty.