Give the common install notes components their own subdirectory.

Also, alpha and i386 now use a single merged common/sysinst,
and arm32 and sparc have a single merged common/xfer.
This commit is contained in:
ross 1999-01-13 08:18:44 +00:00
parent 12d2afa11a
commit b207e38c8b
11 changed files with 3953 additions and 0 deletions

View File

@ -0,0 +1,55 @@
# $NetBSD: Makefile.inc,v 1.1 1999/01/13 08:18:44 ross Exp $
# Ross Harvey <ross@netbsd.org>
NOPROG= notreally
M?= ${.CURDIR:T}
V!= /bin/sh ${.CURDIR}/../../../sys/conf/osrelease.sh
V_S!= /bin/sh ${.CURDIR}/../../../sys/conf/osrelease.sh -s
MAIN= ${.CURDIR}/../common/main ${EXTRA}
TARG= INSTALL
TARGS= ${TARG}.ps ${TARG}.txt ${TARG}.html
SRCS= ${MAIN} mirrors whatis contents hardware xfer prep install\
upgrade donations legal.common legal postinstall ../Makefile.inc\
${MERGED_SRCS}
PRESET= ${GFLAGS} -dV=$V -dV_S=${V_S} -dMACHINE=$M -d.CURDIR=${.CURDIR} -r$M=1
POST_PLAIN= -P-b -P-u -P-o -Tascii
ARGS_PS= ${PRESET} -dformat=PostScript
ARGS_TXT= ${PRESET} -dformat=ASCII ${POST_PLAIN}
ARGS_HTML= ${PRESET} -dformat=HTML ${POST_PLAIN} -ww
ARGS_MORE= ${PRESET} -dformat=more -P-h -Tascii
#
# For example...
#
# .if ri386 ...stuff...
# .Ss "Install notes for NetBSD/\*[MACHINE]"
#
CLEANFILES+=${TARGS}
.for i in ps txt html more
all: ${TARG}.$i
.endfor
${TARG}.ps: ${SRCS}
groff ${ARGS_PS} -mdoc ${MAIN} > $@
${TARG}.txt: ${SRCS}
groff ${ARGS_TXT} -mdoc ${MAIN} > $@
${TARG}.html: ${SRCS}
groff ${ARGS_HTML} -mdoc2html ${MAIN} > $@
${TARG}.more: ${SRCS}
groff ${ARGS_MORE} -mdoc ${MAIN} > $@
echosrcs! ${SRCS}
@echo ${.ALLSRC}
.PATH: ${.CURDIR}/../common

View File

@ -0,0 +1,881 @@
.\" $NetBSD: contents,v 1.1 1999/01/13 08:18:45 ross Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.ds m \*[MACHINE]
.Ss2 NetBSD/\*m Subdirectory Structure
The \*m-specific portion of the
.Nx \*V
release is found in the
.Pa \*m
subdirectory of the distribution:
.ie \n[_FOR_RELEASE] .Pa \&.../NetBSD-\*V/\*m/
.el .Pa Pf \&.../arch/\*m/snapshot/ Ar yyyymmdd/
.Bl -tag -compact -width INSTALL.html
. It Pa INSTALL.html
. It Pa INSTALL.ps
. It Pa INSTALL.txt
. It Pa INSTALL.more
Installation notes; this file. The
.Pa \&.more No file contains underlined text using the
.Xr more 1
conventions for indicating italic and bold display.
. It Pa binary/
. Bl -tag -compact -width diskimage/
. It Pa sets/
\*m binary distribution sets;
see below.
.if \n[amiga] \{\
. Bl -tag -compact -width diskimage/
. It Pa Split/
\&.tgz files split for loading onto floppies.
. El
.\}
. It Pa security/
\*m security distribution; see below.
.if \n[amiga] \{\
. It Pa kernel/
.No The Tn GENERIC No kernel.
.\}
.if \n[sparc] \{\
. It Pa kernel/
.No Base Tn GENERIC No kernels.
.\}
. El
. It Pa installation/
.\" BTW, .Bl ... .El is not allowed unless there is at least one .It.
.
.\"============================================ ALPHA INSTALLATION SUBTREE
.
.if \n[alpha] \{\
. Bl -tag -compact -width diskimage/
. It Pa floppy/
\*m boot and installation floppies; see below.
. It Pa tapeimage/
. It Pa diskimage/
.No An image file Pa cdhdtape
is included for the case where the installer is written to
a CD, hard drive, or tape.
This image file is the same for the CD, HD, and tape cases,
.No but a separate Pa tapeimage/
directory exists to hold a copy of the
.Tn README No file and to meet the
.Nx
.Xr release 7
standard.
. El
.\}
.
.\"============================================ AMIGA INSTALLATION SUBTREE
.
.if \n[amiga] \{\
. Bl -tag -compact -width diskimage/
. It Pa miniroot/
\*[MACHINE] miniroot file system image; see below.
. It Pa misc/
Miscellaneous \*[MACHINE] installation utilities; see
installation section, below.
. El
.\}
.
.\"============================================ ARM32 INSTALLATION SUBTREE
.
.if \n[arm32] \{\
. Bl -tag -compact -width diskimage/
. It Pa kernels/
\*m installation and other kernels; see below.
. It Ar platform/
Miscellaneous arm32 installation utilities and
supplementary documentation for
.Ar platform ; No see installation section, below.
. El
.\}
.
.\"============================================ HP300 INSTALLATION SUBTREE
.
.if \n[hp300] \{\
. Bl -tag -compact -width diskimage/
. It Pa miniroot/
hp300 miniroot images; see below.
. It Pa misc/
Miscellaneous hp300 installation helper utilities;
see installation section below.
. El
.\}
.
.\"============================================ I386 INSTALLATION SUBTREE
.
.if \n[i386] \{\
. Bl -tag -compact -width diskimage/
. It Pa floppy/
\*m boot and installation floppies; see below.
. It Pa misc/
Miscellaneous \*[MACHINE] installation utilities; see
installation section, below.
. El
.\}
.
.
.
.\"============================================ MVME68K INSTALLATION SUBTREE
.
.if \n[mvme68k] \{\
. Bl -tag -compact -width diskimage/
. It Pa miniroot/
The miniroot filesystem image.
. It Pa netboot/
Two programs needed to boot a VME147 kernel over the network.
. It Pa tapeimage/
Tape boot programs, and a RAMDISK kernel.
. El
.\}
.
.\"============================================ PC532 INSTALLATION SUBTREE
.
.if \n[pc532] \{\
. Bl -tag -compact -width floppy
. It Pa floppy/
. Bl -tag -compact -width floppy-144.fs.gz
. It Pa floppy-144.fs.gz
Installation file system obtained via SCSI floppy or download to RAM.
. El
. It Pa misc/
. Bl -tag -compact -width floppy-144.fs.gz
. It Pa download.c.gz
Source for the program to download inst-11.fs into memory via the
pc532 ROM monitor.
. El
. El
.\}
.
.\"============================================ PMAX INSTALLATION SUBTREE
.
.if \n[pmax] \{\
.\}
.
.\"============================================ SPARC INSTALLATION SUBTREE
.
.if \n[sparc] \{\
. Bl -tag -compact -width miniroot/
. It Pa miniroot/
Sparc miniroot boot-image.
. It Pa netboot/
Server boot-file image for diskless machines.
. It Pa misc/
Statically-linked versions of gzip (GNU gzip) and gtar (GNU tar).
. El
.\}
.
.\"============================================ SUN3 INSTALLATION SUBTREE
.
.if \n[sun3] \{\
.\}
.
.\"============================================ SUN3X INSTALLATION SUBTREE
.
.if \n[sun3x] \{\
.\}
.
.\"============================================ VAX INSTALLATION SUBTREE
.
.if \n[vax] \{\
.\}
.
.\"============================================ X68K INSTALLATION SUBTREE
.
.if \n[x68k] \{\
.\}
.
.
.
.
.El
.
.
.
.if r_alpha \{\
.Ss2 Bootable installation/upgrade floppies:
.Pp
There are three bootable images in the
.Nx
\*m distribution.
One is for a dual-floppy boot and is split into two separate files.
The other is a single-file image containing the same install kernel,
but intended to be written to a CD, tape, or hard drive. The third
image is a
.Tn GENERIC
kernel intended for production use in unusual cases.
This can be useful at some sites when:
.Bl -bullet
.It
You want to run diskless but SRM bugs prevent the firmware from
netbooting. You can work around this problem by always booting the generic
kernel from the floppy.
.It
SRM doesn't recognize your (hard) disk controller but
.Nx
does. This
happens more frequently than you might think. SRM will usually only boot
from
.Xr ncr 4
or
.Xr isp 4
SCSI devices, and on most platforms will not
boot from an IDE drive.
.Nx
will happily operate
with almost any SCSI root or an IDE root; the solution here is to netboot
a kernel or always boot from floppy.
.El
.\}
.
.if r_amiga \{\
.Ss2 Miniroot file system
The Amiga now uses a single miniroot filesystem for both an initial
installation and for an upgrade. A gzipped version is available, for easier
downloading. (The gzipped version has the
.Sy \&.gz
extension added to
their names.)
.(tag Pa miniroot.fs
This file contains a BSD root file system setup to help you
install the rest of
.Nx
or to upgrade a previous version of
.Nx .
This includes formatting and mounting your root and
/usr partitions and getting ready to extract (and possibly first
fetching) the distribution sets. There is enough on this file
system to allow you to make a SLIP or PPP connection, configure
an Ethernet, mount an NFS file system or ftp. You can also load
distribution sets from a SCSI tape or from one of your existing
AmigaDOS partitions.
.tag)
.\}
.
.if r_arm32 \{\
There are a collection of arm32 kernels in the "arm32/kernels"
subdirectory of the
.Nx \*V
distribution. Some of these kernels
contain a root file system image and should only be used for the
initial installation. Some of the kernels only support a particular
subset of the platforms that arm32 supports (See
"arm32/kernels/README" for more details.)
.\}
.
.if r_mvme68k \{\
.Pp
The NetBSD/mvme68k install distribution contains files that can be
used to install NetBSD onto a completely "bare" VME147. The files
in the "mvme68k/installation/*" directories are described below.
.Bl -tag -width netbsd-rd.gz
.It Pa miniroot.gz
A gzipped copy of the miniroot filesystem.
This image is to be un-gzipped and copied
into the swap area of a disk.
.It Pa netbsd-rd.gz
A gzipped copy of the
.Em RAMDISK kernel
for installing the miniroot filesystem.
.It Pa stboot
A tape boot-block, in the form required to
allow 147-Bug to boot from tape. This is the
first segment of a boot tape.
.It Pa bootst
A copy of the tape boot program, used
as the second segment of a boot tape.
.It Pa sboot
A copy of the serial boot program. This is
necessary if you don't have a tape drive,
but you _do_ have another system which can
act as a boot and NFS server. This is also
useful if you are installing a diskless
NetBSD/mvme68k system.
.It Pa netboot
A copy of the network boot program. Used
in conjunction with sboot to get your system
booted over a network.
.El
.Pp
These files can be used to make a boot tape suitable for installing
NetBSD/mvme68k. These files can also be used to configure an NFS server
to support installation "over the network". See the section
.Sx Getting the NetBSD System onto Useful Media
for instructions on either method.
.\}
.
.
.Ss2 Binary Distribution Sets
The
.Nx
\*m
binary distribution sets contain the binaries which
comprise the
.Nx \*V
release for the \*m. There are eight binary distribution
.ie r_pc532 sets.
.el .No sets and the Em security No distribution set.
The binary distribution sets can be found in the
.Pa \*m/binary/sets
subdirectory
of the
.Nx \*V
distribution tree, and are as follows:
.Bl -tag -width mmmmmmmmmmm -compact
.Pp
.It Sy base
The
.Nx \*V
.No \*m Sy base No binary distribution. You
.Em must
install this distribution set. It contains the base
.Nx
utilities that are necessary for the
system to run and be minimally functional. It
includes shared library support, and excludes
everything described below.
.br
.if r_alpha .Em 13M gzipped, 41M uncompressed
.if r_arm32 .Em 11M gzipped, 28M uncompressed
.if r_mac68k .Em 8.6M gzipped, 25.1M uncompressed
.Pp
.It Sy comp
Things needed for compiling programs. This set
includes the system include files
.Pq Pa /usr/include
and the various system libraries (except the shared
libraries, which are included as part of the
.Sy 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.
.br
.if r_alpha .Em 6M gzipped, 31M uncompressed
.if r_arm32 .Em 7.5M gzipped, 25M uncompressed
.if r_mac68k .Em 6.2M gzipped, 21.6M uncompressed
.Pp
.It Sy etc
This distribution set contains the system
configuration files that reside in
.Pa /etc
and in several other places. This set
.Em must
be installed if you are installing the system from scratch, but should
.Em not
be used if you are upgrading. (If you are upgrading,
it's recommended that you get a copy of this set and
.Em carefully
upgrade your configuration files by hand.)
.br
.if r_alpha .Em 50K gzipped, 320K uncompressed
.if r_arm32 .Em 52K gzipped, 310K uncompressed
.if r_mac68k .Em 49K gzipped, 288K uncompressed
.Pp
.It Sy games
This set includes the games and their manual pages.
.br
.if r_alpha .Em 3M gzipped, 8M uncompressed
.if r_arm32 .Em 3M gzipped, 7.4M uncompressed
.if r_mac68k .Em 2.8M gzipped, 7.2M uncompressed
.
.\" garden variety kern set description
.
.if !\n[arm32]:\n[atari]:\n[mac68k] \{\
.Pp
.It Sy kern
This set contains a NetBSD/\*m \*V
.Tn GENERIC No kernel, named Pa /netbsd .
.No You Em must
install this distribution set.
.br
.if r_alpha .Em 1M gzipped, 2M uncompressed
.\}
.if \n[atari] \{\
.Pp
.It Sy kern
.It Sy kern_hades
.It Sy kern_x
The NetBSD/\*m \*V kernel binary. You should
install the appropriate kernel for your system.
.Em 472K gzipped, 1.01M uncompressed
.\}
.if \n[mac68k] \{\
.Pp
.It Sy kern
.It Sy kern_sbc
This set contains a NetBSD/\*m \*V
.Tn GENERIC No kernel, named Pa /netbsd .
.No You Em must
install this distribution set.
It is the kernel that you need to boot the system.
If you experience SCSI-related difficulties with your 68030-based system, you
might want to try kern_sbc.tgz instead.
.br
.Em 606K gzipped, 1.32M uncompressed
.\}
.Pp
.It Sy man
This set includes all of the manual pages for the
binaries and other software contained in the
.Sy base
set.
Note that it does not include any of the manual pages
that are included in the other sets.
.br
.Em 2.5M gzipped, 10M uncompressed
.Pp
.It Sy misc
This set includes the (rather large) system dictionaries,
the typesettable document set, and other files from
.Pa /usr/share .
.br
.
.\" Umm, shouldn't this be the same for all platforms?!
.
.if r_alpha .Em 2M gzipped, 9M uncompressed
.if r_arm32 .Em 2M gzipped, 8M uncompressed
.if r_mac68k .Em 2.1M gzipped, 7.6M uncompressed
.Pp
.It Sy text
This set includes NetBSD's text processing tools,
including
.Xr groff 1 ,
all related programs, and their manual pages.
.br
.if r_alpha .Em 1M gzipped, 4M uncompressed
.if r_arm32 .Em 1M gzipped, 4M uncompressed
.if r_mac68k .Em 1.0M gzipped, 3.7M uncompressed
.El
.if r_atari \{\
.(tag Note:
An X server distribution set is currently not available.
.tag)
.\}
.
.
.ie \n[pc532] \{\
.Pp
The pc532 distribution set does not include a security distribution.
If you are in the US and want the security distribution you must
get the security source distribution and recompile libcrypt.a and
recompile the following programs:
.Xr ed 1 ,
.Xr ftpd 8 ,
.Xr makekey 8 ,
.Xr rexecd 8 ,
.Xr uucpd 8 ,
.Xr init 8 ,
.Xr lock 1 ,
.Xr login 1 ,
.Xr passwd 1 ,
.Xr skeyinit 1 ,
.Xr su 1 ,
.Xr tn3270 1 ,
and
.Xr pppd 8 .
.\}
.el \{\
.Pp
The \*m security distribution set is named
.Sy secr No and can be found in the
.D1 Pa \*m/binary/security
subdirectory of the
.Nx \*V
distribution tree. It contains security-related binaries
which depend on cryptographic source code. You do not need this
distribution set to use encrypted passwords in your password file; the
.Sy base
distribution includes a crypt library which can perform
only the one-way encryption function. The security distribution
includes a version of the Kerberos IV network security system, and
a Kerberized version of
.Xr telnet 1
.No program. The Sy secr
distribution set can be found only on those sites which carry the complete
.Nx
distribution and which can legally obtain it. Because
of United States law, it may not be legal to distribute this set
to locations outside of the United States and Canada.
.br
.if r_alpha .Em 1M gzipped, 3M uncompressed
.if r_i386 . Em 798K gzipped, 2.4M uncompressed
.\}
.
.
.Pp
Starting with release 1.3, binary sets for the X Window system are
distributed with
.Nx .
The binaries are based on X11R6.3.
.if r_hp300 \{\
Unfortunately there is no R6.3 Xserver for NetBSD/hp300 yet,
so we can only distribute the X clients this time.
.\}
You can not yet install them using the new automated install system.
However, they are gzipped tarfiles, just like the other sets, so you
can always simply extract them once you have your
.Nx
system installed and running. The sets are:
.Bl -tag -width xcontribmmm
.It Sy xbase
The basic files needed for a complete X
client environment. This does not include
the X servers.
.br
.if r_hp300 .Em 2.5M gzipped, 7.6M uncompressed
.if r_mac68k .Em 2.34 M gzipped, 7.46M uncompressed
.It Sy xcomp
The extra libraries and include files needed to compile X source code.
.br
.if r_hp300 .Em 1.7M gzipped, 7.1M uncompressed
.if r_mac68k .Em 1.57M gzipped, 6.38M uncompressed
.It Sy xcontrib
Programs that were contributed to X.
.br
.if r_hp300 .Em 183k gzipped, 686k uncompressed
.if r_mac68k .Em 178K gzipped, 661K uncompressed
.It Sy xfont
Fonts needed by X.
.br
.Em 5.9M gzipped, 7.3M uncompressed
.
.if r_mac68k \{\
.Pp
.It Sy xserver
.No The Xmac68k Em monochrome
server with man pages.
.br
.Em 1.32M gzipped, 3.25M uncompressed
.\}
.
.El
.
.\"============================ MI DISCUSSION OF BINARY SETS
.
.Pp
The \*m binary distribution sets are distributed as gzipped tar files
named with the extension
.Sy .tgz , No e.g.
.Pa base.tgz .
.
.
.\" contrary to most old INSTALL docs, only i386 has Split/ sets
.
.
.if r_i386 \{\
They are also
available in split form \- catted together, the members of a split set
form a gzipped tar file.
.\}
.
.
.Pp
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
.Em 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
.Ic tar xfp
command from /. Also note that if you upgrade or install this way, those
programs that you are using at the time will
.Em not
be replaced unless you run
.Xr tar 1
with the
.Cm --unlink
option. If you follow the normal
installation or upgrade procedures, this will be taken care of for you.
.
.
.
.
.if r_atari \{\
.Pp
Additional kernels to those included in the distribution sets may be found
in the
.Pa atari/binary/kernel
subdirectory of the
.Nx \*V
distribution tree. These kernels are generally named something like
.Pa netbsd.BOOT.gz
or some other suitable name. Please note that these kernels are simply
gzipped and are not in tar archives.
.Pp
There are three atari floppy images to be found in the
.Pa atari/installation/floppies
subdirectory of the
.Nx \*V
distribution. One of them is a bootable TOS kernel floppy and the other
two are installation floppies. They are described in more detail below.
There are gzipped versions of each available, for easier downloading.
(The gzipped versions have the
.Pa \&.gz
extension added to their names.)
.Bl -tag -width indent
.It Em Bootable\ Kernel\ floppy
This TOS disk contains the loadbsd and chg_pid programs
and a kernel. It is setup so that you can insert it
int your floppy drive, and start the programs from GEM.
.Pp
For the TT030 and Falcon, the floppy is named boot-_SVER_S.fs and
the kernel supplied is 'BOOT'. For the Hades, you need the
hades-boot-_SVER_S.fs floppy. The kernel is 'HADES'.
.It Em Installation\ floppy:
This disk contains a BSD root file system setup to help
you install the rest of NetBSD. This includes formatting
and mounting your root and /usr partitions and getting
ready to extract (and possibly first fetching) the distribution
sets. There is enough on this file system to allow you to
make a slip connection, configure an ethernet, mount an NFS
file system or ftp. You can also load distribution sets from
a SCSI tape or from one of your existing GEMDOS partitions.
.Pp
These floppies are named
.Pa miniroot.fs.1 No and Pa miniroot.fs.2 .
.El
.Pp
There are also TOS utilities in the
.Pa atari/installation/misc
subdirectory, which you will need to get NetBSD/Atari 'up-and-running'.
.Bl -bullet
.It
The
.Dq gzip.ttp
program allows you to uncompress .gz images. The
usage is "gzip.ttp -d filename.gz".
.It
The
.Dq rawwrite.ttp
program allows you to create the installation
floppy disks from the files in the
.Pa atari/floppies
directory.
.It
The "aptck.ttp" program reads the partition tables present on a
given disk and tries to interpret then the same way the NetBSD
kernel does. If you have a disk on which GEMDOS and
.Nx
are to co-exist, It is a good idea to run this before you begin the
NetBSD/Atari installation just to check that the kernel's view
of the partition tables agree with GEMDOS's view. If you have
more than 3 partitions defined on a disk you will notice that
the NetBSD/\*m partition starts one sector after the GEMDOS
partition. This is to allow space for the auxilliary root for
the 4th and subsequent partitions.
.It
The "loadbsd.ttp" program loads the NetBSD/\*m kernel from TOS
(or MiNT, MultiTOS, etc.).
.El
.\}
.
.
.
.if r_hp300 \{\
.
.Pp
The following are included in the
.Pa hp300/installation No directory:
.
.
.Bl -tag -width miniroot/xx
.It Pa miniroot/
. Bl -tag -width miniroot.fs.gz
. It miniroot.fs.gz
A copy of the miniroot filesystem.
. El
.It Pa misc/
. Bl -tag -width miniroot.fs.gz
. It Pa HP-IB.geometry
A file containing geometry for some
HB-IB disk drives.
. It Pa SYS_INST.gz
A gzipped copy of the SYS_INST
miniroot installation program.
. It Pa SYS_UBOOT.gz
A gzipped copy of the universal boot
block. Supports Network, tape and
disk booting. This is useful if you
are installing a diskless NetBSD/hp300
system.
. It Pa rbootd.tgz
Source code for the rbootd program
included with NetBSD. It requires that
the server has a Berkeley Packet
Filter (bpf). You will need to
compile this version of rbootd if
server system does not have this
utility already.
. El
.El
.
.
The following are included in the
.Pa hp300/binary/kernel No directory:
.
.Bl -tag -width netbsd.gdb.gzmmmmm
.It Pa netbsd.gdb.gz
A gzipped GENERIC kernel with debugging symbols.
.It Pa netbsd.gz
A gzipped GENERIC kernel.
.El
.
.\}
.
.if r_mac68k \{\
.Pp
Additional kernels to those included in the distribution sets may be found
in the
.Pa mac68k/binary/kernels
subdirectory of the
.Nx \*V
distribution tree. These kernels are generally named something like
.Pa netbsd-GENERIC.gz
or some other suitable name. Please note that these kernels are simply
gzipped and are not in tar archives.
.Pp
The MacOS-based utilities necessary for installing and running
.Nx
can
be found in the
.Pa mac68k/installation/misc
subdirectory of the
.Nx \*V
distribution tree. The important files in this directory are as
follows:
.
.
.Bl -tag -width Installer.sea.hqx
.It Pa Booter.sea.hqx
The NetBSD/Mac68k Booter utility. This program is used to boot the
.Nx
kernel from within MacOS.
.br
.Em 141 K archived
.It Pa Installer.sea.hqx
The NetBSD/Mac68k Installer utility. This
program is used to install the distribution sets onto your
.Nx
partition(s).
.br
.Em 147 K archived
.It Pa Mkfs.sea.hqx
The Mkfs utility. This program is used to
format your chosen partitions so that they
can be used with NetBSD.
.br
.Em 76 K archived
.El
.Pp
These files are all binhexed, self-extracting archives. If you need them,
the sources for these utilities are in the
.Pa src No subdirectory.
.
.
.\}
.
.
.if r_pc532 \{\
.Pp
The initial installation process on a pc532 without a previous
.Nx
installation is supported by the following files:
.Bl -tag -width floppy-144.fs
.It Pa floppy-144.fs
A file system containing the boot loader and install kernel with
a 2MB root.
.It Pa download.c
The source for a program to download
.Pa inst-11.fs
into memory via the pc532
.Tn ROM No monitor .
.El
.Pp
The upgrade process is supported by having a copy of a \*V kernel
available. This file is:
.(tag Pa kern.tgz
Contains a kernel produced from the
.Pa DEFAULT
configuration file in
.Pa pc532/conf .
.tag)
.\}
.
.
.if r_sparc \{\
. (Note
The distribution cannot be extracted using the SunOS
. Pa tar
program so statically-linked SunOS versions of gzip (GNU gzip) and
gtar (GNU tar) are provided in
. Pa sparc/installation/misc .
. Note)
.\}
.
.
.(Note
Each directory in the \*m binary distribution also has its
own checksum files, just as the source distribution does:
.Pp
.No All Tn BSDSUM
files are historic
.Tn BSD No checksums for the various files
in that directory, in the format produced by the command:
.Ic cksum -o 1 Ar file
.Pp
.No All Tn CKSUM No files are
.Tn POSIX
checksums for the various files in that
directory, in the format produced by the command:
.Ic cksum Ar file .
.Pp
.No All Tn MD5 No files are
.Tn MD5
digests for the various files in that
directory, in the format produced by the command:
.Ic cksum Fl m Ar file .
.Pp
.No All Tn SYSVSUM
files are historic AT\*&T System V
.Ux
checksums for the various files in that directory, in the format produced by
the command:
.Ic cksum Fl o 2 Ar file .
.Pp
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.
.Note)

View File

@ -0,0 +1,71 @@
.\" $NetBSD: donations,v 1.1 1999/01/13 08:18:45 ross Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.Bd -unfilled -offset indent
Avalon Computer Systems
Bay Area Internet Solutions
Jason Brazile
David Brownlee
Simon Burge
Dave Burgess
Ralph Campbell
Canada Connect Corporation
Brian Carlstrom
James Chacon
Bill Coldwell
Charles Conn
Tom Coulter
Charles D. Cranor
Christopher G. Demetriou
Ross Harvey
Demon Internet, UK
Easynet, UK
Scott Ellis
Free Hardware Foundation
Greg Gingerich
Michael L. Hitch
Innovation Development Enterprises of America
Scott Kaplan
Chris Legrow
Neil J. McRae
Perry E. Metzger
MS Macro System GmbH, Germany
Numerical Aerospace Simulation Facility, NASA Ames Research Center
Herb Peyerl
Mike Price
Thor Lancelot Simon
Bill Sommerfeld
Paul Southworth
Jason R. Thorpe
Steve Wadlow
.Ed

View File

@ -0,0 +1,219 @@
.\" $NetBSD: legal.common,v 1.1 1999/01/13 08:18:45 ross Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.
.
.
.ig
WARNING: Don't insert markup into this file without making AT LEAST one of
the following checks:
1. The command is a raw troff command other than .ps or \s
2. The command is a -mdoc macro that doesn't change the point size.
3. You restore the lowered point size after marked-up input changes it.
..
.
.
.
.
This product includes software developed by the University of
California, Berkeley and its contributors.
This product includes software developed by the Computer
Systems Engineering Group at Lawrence Berkeley Laboratory.
This product includes software developed by the NetBSD
Foundation, Inc. and its contributors.
This product includes software developed by Adam Glass
and Charles Hannum.
This product includes software developed by Adam Glass.
This product includes software developed by Berkeley Software
Design, Inc.
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 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 Herb Peyerl.
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 Mark Brinicombe.
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 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 Scott Bartram.
This product includes software developed by SigmaSoft, Th. Lockert.
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 TooLs GmbH.
This product includes software developed by Winning Strategies, Inc.
This product includes software developed by the Center for
Software Science 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.

144
distrib/notes/common/macros Normal file
View File

@ -0,0 +1,144 @@
.\" $NetBSD: macros,v 1.1 1999/01/13 08:18:45 ross Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" This code is derived from software contributed to The NetBSD Foundation
.\" by Ross Harvey.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.\" -------------------- MACROS --------------------
.
.
.\" Define a .CURDIR-relative include, with entertainment
.
.rn so so-real
.de so
. tm ...reading \\$1
. Pp
. so-real \*[.CURDIR]/\\$1
.\" tm ...back to INSTALL
..
.als source so
.
.\" -mdoc only has only two section levels (Sh & Ss)
.
.\" second-level subsection macro (third-level section)
.
.de Ss2
. ie rHTML <h3>\\$*</h3>
. el \{\
. br
. ne 7P
. Pp
. Em "\\$*"
. Pp
. \}
..
.
.
.\" standard display, with nice showmatch parens in the name
.
.
.de (disp
. Bd -literal -offset indent
..
.
.de disp)
. Ed
..
.
.
.de br_ne
. br
. ne \\$1
..
.
.
.
.\" Degenerate case of tagged list: a single tagged paragraph, possibly
.\" followed by more (.Pp) paragraphs at the same indent level. Uses the
.\" last parameter specified for the width, so things like .(tag Em tagfun
.\" will DTRT. End the sequence with ``.tag)''.
.\"
.
.
.de (tag
. Bl -tag -width x\\$\\n[.$]
. It \\$@
.
..
.de tag)
. El
..
.
.de (Note
. (tag Em Note
..
.
.de Note)
. tag)
..
.
.de Bdlit
. Bd -literal -offset indent
..
.
.de D2
. Pp
. Dl Ic $@
..
.
.\" -------------------- MISC --------------------
.
.\" set the unused target number registers to 0, so that we can turn on all
.\" the warnings but still do things like .if \n[amiga]:\n[alpha] \&stuff
.\" (The Makefile defines the target as 1, leaving the others undefined.)
.
.de define_all
. while \\n[.$] \{\
. if !r\\$1 .nr \\$1 0
. shift
. \}
..
.
.define_all \*[MACHINE_LIST]
.
.\" Define _ versions, sometimes these look better as with .if r_xxx
.
.nr _FOR_RELEASE \n[FOR_RELEASE]
.nr _\*[MACHINE] 1
.
.de (note
. (Note
..
.de note)
. Note)
..

983
distrib/notes/common/main Normal file
View File

@ -0,0 +1,983 @@
.\" $NetBSD: main,v 1.1 1999/01/13 08:18:45 ross Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.ig
The notes that describe the improvements over the last release
aren't appropriate for a snapshot, so these are conditional on
FOR_RELEASE. 0 == snapshot; 1 == release
..
.
.tm Processing INSTALL
.
.\" -------------------- CONFIGURATION --------------------
.
.nr FOR_RELEASE 0
.ds MACHINE_LIST alpha amiga arm32 atari hp300 i386 mac68k mvme68k
.as MACHINE_LIST " pc532 pmax sparc sun3 sun3x vax x68k
.so ../common/macros
.Dd 13 October 1998
.Dt INSTALL 8
.Os NetBSD
.Sh NAME
.Nm INSTALL
.Nd Installation procedure for NetBSD/\*[MACHINE]
.Sh DESCRIPTION
.Pp
.
.Ss About this Document
.
This document describes the installation procedure for
.Nx \*V
on the
.Em \*[MACHINE] No platform .
It is available in four different formats titled
.Pa INSTALL. Ns Ar ext ,
.No where Ar ext
is one of
.Pa .ps , .html , .more ,
.No or Pa txt .
.Bl -tag -width \&.morex -offset indent
.It Pa \&.ps
PostScript.
.It Pa \&.html
.No Standard internet Tn HTML .
.It Pa \&.more
The enhanced text format used on Unix-like systems by the
.Xr more 1
and
.Xr less 1
pager utility programs. This is the format in which the on-line
.Em man
pages are generally presented.
.It Pa \&.txt
Plain old
.Tn ASCII .
.El
.Pp
You are reading the
.Em \*[format] No version .
.
.Ss "What is NetBSD?"
.
The
.Nx
Operating System is a fully functional UN*X-like system
derived from the Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite,
and 4.4BSD-Lite2 sources.
.Nx
runs on many architectures and is
being ported to more.
.Pp
.Nx
is a creation of the members of the Internet community.
Without the unique cooperation and coordination the net makes
possible, it's likely that this release wouldn't have come about.
.if \n[_FOR_RELEASE] \{\
.Pp
The
.Nx \*V
release is a landmark. Building upon the successful
.Nx
1.2 release, we have provided numerous and significant
functional enhancements, including support for many new devices,
integration of many bug fixes, new and updated kernel subsystems, and
many userland enhancements. The results of these improvements is a
stable operating system fit for production use that rivals most
commercially available systems.
.Pp
It is impossible to summarize the 18 months of development that went
into the
.Nx \*V
release. Some of the significant changes include:
.Bl -bullet
.It
Support for machine independent device drivers has been
radically improved with the addition of the "bus.h" interface,
providing a high quality abstraction for machine and
architecture independent device access.
.It
The bus_dma interface has also been integrated, providing a
machine-independent abstraction for DMA mapping. This permits many
good things, including (among many) clean multi-platform
bounce buffer support.
.It
Framework support for ISA "Plug and Play" has been added, as
well as support for numerous "Plug and Play" devices.
.It
APM support has been added to NetBSD/i386.
.It
An initial cut of multi-platform PCMCIA support has been added.
.It
Support for ATAPI devices (initially just ATAPI CD-ROM drives)
has been added.
.It
Support for Sun 3/80s (sun3x architecture) has been added.
.It
Support for R4000 DECstations has been added.
.It
Integration/merger of 4.4BSD Lite-2 sources into userland
programs has nearly been completed.
.It
Most of userland now compiles with high levels of gcc warnings
turned on, which has lead to the discovery and elimination of
many bugs.
.It
The i386 boot blocks have been completely replaced with a new,
libsa based two stage boot system. This has permitted
integration of compressed boot support (see below).
.It
Many ports now support booting of compressed kernels, and
feature new "Single Floppy" install systems that boot
compressed install kernels and ramdisks. We intend to do
substantial work on improving ease of installation in the
future.
.It
"ypserv" has been added, thus completing our support for the
"yp" network information system suite.
.It
Support for the Linux "ext2fs" filesystem and for FAT32 "msdosfs"
filesystems has been added.
.It
TCP now has a SYN "compressed state engine" which provides
increased robustness under high levels of received SYNs (as in
the case of "SYN flood" attacks.) (Much of this code was
derived from sources provided by BSDI.)
.It
An initial implementation of Path MTU discovery has been
integrated (though it is not turned on by default).
.It
An initial kernel based random number generator pseudodevice has
been added.
.It
Several major fixes have been integrated for the VM subsystem,
including the fix of a notorious VM leak, improved
synchronization between mmap()ed and open()ed files, and
massively improved performance in low real memory conditions.
.It
A new swap subsystem has radically improved configuration and
management of swap devices and adds swapping to files.
.It
Userland ntp support, including xntpd, has been integrated.
.It
The audio subsystems have been substantially debugged and
improved, and now offer substantial emulation of the OSS audio
interface, thus providing the ability to cleanly run emulated
Linux and FreeBSD versions of sound intensive programs.
.It
A "packages" system has been adapted from FreeBSD and will
provide binary package installations for third party
applications.
.It
The XFree86 X source tree has been made a supported part of
the
.Nx
distribution, and X servers (if built for this
port), libraries and utilities are now shipped with our releases.
.It
The ftp(1) program has been made astoundingly overfunctional.
It supports command line editing, tab completion, status bars,
automatic download of URLs specified on the command line,
firewall support and many other features.
.It
All ports now use "new" config. Old config has been laid to rest.
.It
The ARP subsystem and API has been rewritten to make it less
ethernet-centric.
.It
A new if_media subsystem has been added which allows network
interfaces to be configured using media type names rather than
device-specific mode bits.
.It
Many kernel interface manual pages have been added to manual
section 9.
.It
Several ports support much more hardware.
.It
Many updates to bring
.Nx
closer to standards compliance.
.It
Most third party packages have been updated to the latest stable
release.
.El
As has been noted, there have also been innumerable bug fixes.
.Pp
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.
.Pp
.Nx \*V also includes some refinement to the
.Nx
binary emulation
system (which includes FreeBSD, HP-UX, iBCS2, Linux, OSF/1, SunOS, SVR4,
Solaris and Ultrix compatibility), bringing
.Nx
closer to the goal of
making the emulation as accurate as possible.
.Pp
In the near future, we hope to integrate a fully rewritten Virtual
Memory subsystem, kernel threads, and SMP support.
.Pp
.so whatis -----------------------------------------------
.\}
.
.Ss "The Future of NetBSD"
.
The
.Nx
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
.Nx
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
.Nx
Project.
.Pp
The
.Nx
Foundation will help improve the quality of
.Nx
by:
.Bl -bullet
.It
providing better organization to keep track of development
efforts, including co-ordination with groups working in
related fields.
.It
providing a framework to receive donations of goods and
services and to own the resources necessary to run the
.Nx
Project.
.It
providing a better position from which to undertake
promotional activities.
.It
periodically organizing workshops for developers and other
interested people to discuss ongoing work.
.El
We hope to have regular releases of the full binary and source trees,
but these are difficult to coordinate, especially with all of the
architectures which we now support!
.Pp
We hope to support even
.Em more
hardware in the future, and we have a
rather large number of other ideas about what can be done to improve
.Nx .
.Pp
We intend to continue our current practice of making the
NetBSD-current development source available on a daily basis.
.Pp
We intend to integrate free, positive changes from whatever sources
will provide them, providing that they are well thought-out and
increase the usability of the system.
.Pp
Above all, we hope to create a stable and accessible system, and to be
responsive to the needs and desires of
.Nx
users, because it is for
and because of them that
.Nx
exists.
.br_ne 10P
.
.Ss "Sources of NetBSD"
.
.so ../common/mirrors -----------------------------------------------
.br_ne 10P
.
.Ss "NetBSD \*V Release Contents
.
The root directory of the
.Nx \*V
release is organized as follows:
.ie \n[_FOR_RELEASE] \{\
.Pp
.Pa .../NetBSD-\*V/
.Bl -tag -width LAST_MINUTE
.It Li BUGS
Known bugs list (somewhat incomplete and out of date).
.It Li CHANGES
Changes since earlier
.Nx
releases.
.It Li LAST_MINUTE
Last minute changes.
.It Li MIRRORS
A list of sites that mirror the
.Nx \*V
distribution.
.It Li README.files
README describing the distribution's contents.
.It Li TODO
NetBSD's todo list (also somewhat incomplete and out of date).
.It Li patches/
Post-release source code patches.
.It Li source/
Source distribution sets; see below.
.El
.Pp
In addition to the files and directories listed above, there is one
directory per architecture, for each of the architectures for which
.Nx \*V
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 (i.e. the `domestic' portion) that may be subject to
export regulations of the United States. It is your responsibility
to determine whether or not it is legal for you to export these portions
and to act accordingly.
.Pp
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:
.Bl -tag -width sharesrc.tgz...
.It secrsrc.tgz:
This set contains the "domestic" sources. These
sources may be subject to United States export
regulations.
.br
.Em 412K gzipped, 1.8M uncompressed
.It gnusrc.tgz:
This set contains the "gnu" sources, including
the source for the compiler, assembler, groff,
and the other GNU utilities in the binary distribution
sets.
.br
.Em 15.6M gzipped, 66.4M uncompressed
.It syssrc.tgz:
This set contains the sources to the
.Nx \*V
kernel, config(8), and dbsym(8).
.br
.Em 10.7M gzipped, 50.0M uncompressed
.It sharesrc.tgz:
This set contains the "share" sources, which include
the sources for the man pages not associated with
any particular program, the sources for the
typesettable document set, the dictionaries, and more.
.br
.Em 2.9M gzipped, 11.1M uncompressed
.It src.tgz:
This set contains all of the
.Nx \*V
sources which
are not mentioned above.
.br
.Em 13.9M gzipped, 60.7M uncompressed
.El
.Pp
Most of the above source sets are located in the
.Pa source/sets
subdirectory of the distribution tree. The secrsrc.tgz set is
contained in the
.Pa source/security
subdirectory. This set, which is
available only to users in the United States and Canada, contains the
sources normally found in
.Pa /usr/src/domestic
\- primarily kerberos and
other cryptographic security related software. (Remember, because of
United States law, it may not be legal to distribute this set to
locations outside of the United States and Canada.)
.Pp
The source sets are distributed as compressed tar files. They may be
unpacked into
.Pa /usr/src
with the command:
.D1 Ic "cat set_name.tgz | gunzip | (cd /; tar xpf - )
.No The Pa sets/Split/
.No and Pa security/Split/
subdirectories contain 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 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.)
.Pp
The split distributions may be reassembled and extracted with
.Ic cat No as follows:
.D1 Ic "cat set_name.?? | gunzip | (cd /; tar xpf - )
.Pp
In each of the source distribution set directories, there is a file
named
.Pa CKSUMS
which contains the checksums of the files in that
directory, as generated by the
.Xr cksum 1
utility. You can use cksum to
check the integrity of the archives, if you suspect that one of the
files is corrupt and have access to a cksum binary. Checksums based on
other algorithms may also be present \*- see the
.Xr release 7
man page for details.
.\}
.el \{\
.Pp
.Pa \&.../NetBSD-current/tar_files/
.Dl doc.tar.gz
.Dl pkgsrc.tar.gz
.Dl src/*.tar.gz
.Dl xsrc.tar.gz
.Pp
Other directories provide unpacked source trees for distribution via
the source update protocol, for more information see:
.Lk http://www.netbsd.org/Sites/net.html#sup
.\}
.so ../common/contents -----------------------------------------------
.br_ne 7P
.
.Ss "NetBSD/\*[MACHINE] System Requirements and Supported Devices"
.
.so hardware -----------------------------------------------
.br_ne 7P
.
.Ss "Getting the NetBSD System on to Useful Media"
.
.so xfer -----------------------------------------------
.br_ne 7P
.
.Ss "Preparing your System for NetBSD Installation"
.
.so prep -----------------------------------------------
.br_ne 7P
.
.Ss "Installing the NetBSD System"
.
.so install -----------------------------------------------
.br_ne 7P
.
.Ss "Post installation steps"
.
.so ../common/postinstall -----------------------------------------------
.br_ne 7P
.
.Ss "Upgrading a previously-installed NetBSD System"
.
.so upgrade -----------------------------------------------
.br_ne 7P
.
.Ss "Compatibility Issues With Previous NetBSD Releases"
.
Users upgrading from previous versions of
.Nx
may wish to bear the
following problems and compatibility issues in mind when upgrading to
.Nx \*V
.
.
.Bl -bullet
.It
Swap configuration
.
.
.Bl -tag -width 3n
.It Description
All swap partitions are now configured by the swapctl(8)
program. The kernel no longer configures a default swap
partition. Because of this, all swap partitions
.No must be listed in Pa /etc/fstab .
.Pp
Many users of previous releases relied on the kernel
configuring a "default" swap partition and did not list any swap space in
.Pa /etc/fstab
at all -- such users will now have no
swap space configured unless they list swap partitions in
.Pa /etc/fstab !
.Pp
Common symptoms of of this problem include machine crashes
during builds, and similar memory intensive activities.
.It Fix
The most common position for a swap partition is the `b'
partition of the drive the root file system is on. For
diskless systems, check the new swapctl(8) manual for more
detail on how this is done. Example fstab entries:
.
.Bl -column /dev/sd0bxx nonexx swapxx sw,priority=0xx
.It /dev/sd0b Ta none Ta swap Ta sw,priority=0
.It /dev/sd1b Ta none Ta swap Ta sw,priority=5
.El
.
.El
.
.It
NFS now uses reserved ports
.
.Bl -tag -width 3n
.It Description
Earlier versions of
.Nx
did not use a reserved (\*(<= 1023)
port when making NFS client requests. When acting as a server
NetBSD now requires reserved ports by default.
.Pp
Old clients mounting a new server will receive a 'permission
denied' response when the directory is accessed. New clients
should work fine with old servers.
.It Fix
Add '-P' to the mount options in the old client's
.Pa /etc/fstab ,
or (less preferred), add
.Li \&-noresvport,noresvmnt
to the options on the new server's
.Pa /etc/exports .
.El
.
.It
NFS daemons and other programs in /sbin moved
.
.Bl -tag -width 3n
.It Description
The NFS daemons (nfsd, nfsiod, mountd) have been moved from
the
.Pa /sbin
to the
.Pa /usr/sbin directory .
When new binaries are
loaded over old ones during upgrade, most programs get
overlaid and replaced, but unless these binaries are
explicitly removed they will not disappear. The installation
subsystems on some
.Nx
architectures will not properly
remove these binaries.
.Pp
Due to changes in the NFS subsystem, the old NFS daemon
binaries will not work correctly, and will cause serious
problems. Unfortunately, the default startup script
.Pq Pa /etc/rc
will run the old binaries in
.Pa /sbin
if they are present instead of the new ones in
.Pa /usr/sbin .
.Pp
Some other programs (dumpfs, dumplfs and quotacheck) have also
been moved from
.Pa /sbin
to
.Pa /usr/sbin ,
and old versions may be
left behind by accident. They, too, may cause difficulties.
.It Fix
Remove the old daemon binaries
.Pp Pa (/sbin/nfsiod ,
.Pa /sbin/nfsd ,
.Pa /sbin/mountd ,
.Pq etc.
after your upgrade has finished. You may
wish to do an
.D1 Ic "ls -lt /sbin | more
to help determine which
binaries were not replaced/removed during your upgrade.
.El
.
.It
.Tn AMANDA
(The Advanced Maryland Automatic Network Disk Archiver, from
.Lk http://www.amanda.org)
.
.Bl -tag -width 3n
.It Description
Due to a change in the output of dump(8) to ensure
consistency in the messages, AMANDA's dump output
parser breaks.
.Pp
Error messages such as the following may be an
indication that this problem is present:
.
.Bd -unfilled
FAILURE AND STRANGE DUMP SUMMARY:
hostname wd0e lev 1 FAILED [no backup size line]
.Ed
.
.It Versions affected
2.3.0.4, and most likely earlier versions
.It Workaround/Fix
One of:
.
.Bl -bullet
.It
Apply
.Lk ftp://ftp.netbsd.org/pub/NetBSD/misc/patches/amanda-pre-2.4.patch \
this\~patch
.It
Upgrade to AMANDA 2.4.0 or newer. The side effect of this is
that the network protocol is incompatible with earlier
versions.
.El
.
.El
.
.El
.
.
.Ss "Using online NetBSD documentation"
.Pp
Documentation is available if you first install the manual
distribution set. Traditionally, the
.Dq man pages
(documentation) are denoted by
.Dq Li name(section) .
Some examples of this are
.Pp
.Bl -bullet -compact -offset indent
.It
.Xr intro 1 ,
.It
.Xr man 1 ,
.It
.Xr apropros 1 ,
.It
.Xr passwd 1 ,
and
.It
.Xr passwd 5 .
.El
.Pp
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.
.Pp
.No The Em man
command is used to view the documentation on a topic, and is
started by entering
.Ic man Op Ar section
.Ar topic .
The brackets
.Op \&
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
.D1 Ic "man passwd
to read the documentation for
.Xr passwd 1 .
To view the documentation for
.Xr passwd 5 m
enter
.D1 Ic man 5 passwd
instead.
.Pp
If you are unsure of what man page you are looking for, enter
.Ic apropos Ar subject-word
.Pp
where
.Ar subject-word
is your topic of interest; a list of possibly
related man pages will be displayed.
.
.Ss Administrivia
.
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
.Mt 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.
.Pp
There are various mailing lists set up to deal with comments and
questions about this release. Please send comments to:
.Mt netbsd-comments@NetBSD.ORG .
.Pp
To report bugs, use the
.Xr send-pr 1
command shipped with
.Nx ,
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:
.Mt netbsd-bugs@NetBSD.ORG .
.Pp
Use of
.Xr send-pr 1
is encouraged, however, because bugs reported with it
are entered into the
.Nx
bugs database, and thus can't slip through
the cracks.
.Pp
There are also port-specific mailing lists, to discuss aspects of
each port of
.Nx .
Use majordomo to find their addresses. 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).
.Pp
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:
.Mt netbsd-help@NetBSD.ORG .
.Pp
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 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.
.
.Ss Thanks go to
.
.Bl -bullet
.It
The former members of UCB's Computer Systems Research Group,
including (but not limited to):
.Bd -unfilled -offset indent
Keith Bostic
Ralph Campbell
Mike Karels
Marshall Kirk McKusick
.Ed
.Pp
for their ongoing work on BSD systems, support, and encouragement.
.It
Also, our thanks go to:
.Bd -unfilled -offset indent
Mike Hibler
Rick Macklem
Jan-Simon Pendry
Chris Torek
.Ed
.Pp
for answering lots of questions, fixing bugs, and doing the various work
they've done.
.It
UC Berkeley's Experimental Computing Facility provided a home for
sun-lamp in the past, people to look after it, and a sense of humor.
Rob Robertson, too, has added his unique sense of humor to things, and
for a long time provided the primary FTP site for
.Nx .
.It
Best Internet Communications for hosting the
.Nx
FTP and SUP server.
.It
Cygnus Support for hosting the
.Nx
Mail server.
.It
Without CVS, this project would be impossible to manage, so our hats
go off to Brian Berliner, Jeff Polk, and the various other people
who've had a hand in making CVS a useful tool.
.It
Dave Burgess
.Mt burgess@cynjut.infonet.net
has been maintaining the
386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be
recognized for it.
.It
The following people (in alphabetical order) have made donations or
loans of hardware and/or money, to support
.Nx
development, and
deserve credit for it:
.so ../common/donations -----------------------------------------------
(If you're not on that list and should be, tell us! We probably were
not able to get in touch with you, to verify that you wanted to be
listed.)
.It
Finally, we thank all of the people who've put sweat and tears into
developing
.Nx
since its inception in January, 1993. (Obviously,
there are a lot more people who deserve thanks here. If you're one of
them, and would like to mentioned, tell us!)
.El
.
.Ss "We are..."
.
.Pp
(in alphabetical order)
.Pp
.
.
.Bl -column XXxxx Frank\ van\ der\ Lindenxx sakamoto@NetBSD.ORGxx newsmips
.
.br_ne 1i
.It-span Em "The NetBSD core group:"
.It Ta Ta
.It Ta Paul Kranenburg Ta Mt pk@NetBSD.ORG
.It Ta Herb Peyerl Ta Mt hpeyerl@NetBSD.ORG
.It Ta Scott Reynolds Ta Mt scottr@NetBSD.ORG
.It Ta Jason Thorpe Ta Mt thorpej@NetBSD.ORG
.It Ta Christos Zoulas Ta Mt christos@NetBSD.ORG
.It Ta Ta
.br_ne 2i
.It-span Em "The portmasters (and their ports):"
.It Ta Ta
.It Ta Mark Brinicombe Ta Mt mark@NetBSD.ORG Ta Sy arm32
.It Ta Jeremy Cooper Ta Mt jeremy@NetBSD.ORG Ta Sy sun3x
.It Ta Chuck Cranor Ta Mt chuck@NetBSD.ORG Ta Sy mvme68k
.It Ta Ross Harvey Ta Mt ross@NetBSD.ORG Ta Sy alpha
.It Ta Chris Hopps Ta Mt chopps@NetBSD.ORG Ta Sy amiga
.It Ta Eduardo Horvath Ta Mt eeh@NetBSD.ORG Ta Sy sparc64
.It Ta Paul Kranenburg Ta Mt pk@NetBSD.ORG Ta Sy sparc
.It Ta Anders Magnusson Ta Mt ragge@NetBSD.ORG Ta Sy vax
.It Ta Tsubai Masanari Ta Mt tsubai@NetBSD.ORG Ta Sy macppc
.It Ta Tsubai Masanari Ta Mt tsubai@NetBSD.ORG Ta Sy newsmips
.It Ta Phil Nelson Ta Mt phil@NetBSD.ORG Ta Sy pc532
.It Ta Masaru Oki Ta Mt oki@NetBSD.ORG Ta Sy x68k
.It Ta Scott Reynolds Ta Mt scottr@NetBSD.ORG Ta Sy mac68k
.It Ta Gordon Ross Ta Mt gwr@NetBSD.ORG Ta Sy sun3,\ sun3x
.It Ta Kazuki Sakamoto Ta Mt sakamoto@NetBSD.ORG Ta Sy bebox
.It Ta Wolfgang Solfrank Ta Mt ws@NetBSD.ORG Ta Sy powerpc
.It Ta Jonathan Stone Ta Mt jonathan@NetBSD.ORG Ta Sy pmax
.It Ta Jason Thorpe Ta Mt thorpej@NetBSD.ORG Ta Sy hp300
.It Ta "Frank van der Linden" Ta Mt fvdl@NetBSD.ORG Ta Sy i386
.It Ta Leo Weppelman Ta Mt leo@NetBSD.ORG Ta Sy atari
.It Ta Ta
.br_ne 1i
.It-span Em "The NetBSD \*V Release Engineering team:"
.It Ta Ta
.It Ta Chris G. Demetriou Ta Mt cgd@NetBSD.ORG
.It Ta Ted Lemon Ta Mt mellon@NetBSD.ORG
.It Ta Perry Metzger Ta Mt perry@NetBSD.ORG
.It Ta Jason Thorpe Ta Mt thorpej@NetBSD.ORG
.It Ta Ta
.br_ne 2i
.It-span Em "Developers and other contributors:"
.It Ta Ta
.It Ta Steve Allen Ta Mt wormey@NetBSD.ORG
.It Ta Lennart Augustsson Ta Mt augustss@NetBSD.ORG
.It Ta Christoph Badura Ta Mt bad@NetBSD.ORG
.It Ta Manuel Bouyer Ta Mt bouyer@NetBSD.ORG
.It Ta Robert V. Baron Ta Mt rvb@NetBSD.ORG
.It Ta John Brezak Ta Mt brezak@NetBSD.ORG
.It Ta Allen Briggs Ta Mt briggs@NetBSD.ORG
.It Ta Aaron Brown Ta Mt abrown@NetBSD.ORG
.It Ta David Brownlee Ta Mt abs@NetBSD.ORG
.It Ta Simon Burge Ta Mt simonb@NetBSD.ORG
.It Ta Dave Burgess Ta Mt burgess@cynjut.infonet.net
.It Ta Dave Carrel Ta Mt carrel@NetBSD.ORG
.It Ta Bill Coldwell Ta Mt billc@NetBSD.ORG
.It Ta Alistair Crooks Ta Mt agc@NetBSD.ORG
.It Ta Aidan Cully Ta Mt aidan@NetBSD.ORG
.It Ta Rob Deker Ta Mt deker@NetBSD.ORG
.It Ta Chris G. Demetriou Ta Mt cgd@NetBSD.ORG
.It Ta Matthias Drochner Ta Mt drochner@NetBSD.ORG
.It Ta Enami Tsugutomo Ta Mt enami@NetBSD.ORG
.It Ta Bernd Ernesti Ta Mt veego@NetBSD.ORG
.It Ta Erik Fair Ta Mt fair@NetBSD.ORG
.It Ta Hubert Feyrer Ta Mt hubertf@NetBSD.ORG
.It Ta Thorsten Frueauf Ta Mt frueauf@NetBSD.ORG
.It Ta Brian R. Gaeke Ta Mt brg@dgate.org
.It Ta Thomas Gerner Ta Mt thomas@NetBSD.ORG
.It Ta Justin Gibbs Ta Mt gibbs@NetBSD.ORG
.It Ta Adam Glass Ta Mt glass@NetBSD.ORG
.It Ta Michael Graff Ta Mt explorer@NetBSD.ORG
.It Ta Brad Grantham Ta Mt grantham@tenon.com
.It Ta Matthew Green Ta Mt mrg@NetBSD.ORG
.It Ta Juergen Hannken-Illjes Ta Mt hannken@NetBSD.ORG
.It Ta Charles M. Hannum Ta Mt mycroft@NetBSD.ORG
.It Ta Eric Haszlakiewicz Ta Mt erh@NetBSD.ORG
.It Ta Michael L. Hitch Ta Mt osymh@NetBSD.ORG
.It Ta Ken Hornstein Ta Mt kenh@NetBSD.ORG
.It Ta Marc Horowitz Ta Mt marc@NetBSD.ORG
.It Ta ITOH Yasufumi Ta Mt itohy@NetBSD.ORG
.It Ta Matthew Jacob Ta Mt mjacob@NetBSD.ORG
.It Ta Lonhyn T. Jasinskyj Ta Mt lonhyn@NetBSD.ORG
.It Ta Darrin Jewell Ta Mt dbj@NetBSD.ORG
.It Ta Lawrence Kesteloot Ta Mt kesteloo@cs.unc.edu
.It Ta Klaus Klein Ta Mt kleink@NetBSD.ORG
.It Ta John Kohl Ta Mt jtk@NetBSD.ORG
.It Ta Kevin Lahey Ta Mt kml@NetBSD.ORG
.It Ta Ted Lemon Ta Mt mellon@NetBSD.ORG
.It Ta Mike Long Ta Mt mikel@NetBSD.ORG
.It Ta Paul Mackerras Ta Mt paulus@NetBSD.ORG
.It Ta Neil J. McRae Ta Mt neil@NetBSD.ORG
.It Ta Perry Metzger Ta Mt perry@NetBSD.ORG
.It Ta Luke Mewburn Ta Mt lukem@NetBSD.ORG
.It Ta Minoura Makoto Ta Mt minoura@NetBSD.ORG
.It Ta der Mouse Ta Mt mouse@NetBSD.ORG
.It Ta Tohru Nishimura Ta Mt nisimura@NetBSD.ORG
.It Ta Greg Oster Ta Mt oster@NetBSD.ORG
.It Ta Matthias Pfaller Ta Mt matthias@NetBSD.ORG
.It Ta Dante Profeta Ta Mt dante@NetBSD.ORG
.It Ta Chris Provenzano Ta Mt proven@NetBSD.ORG
.It Ta Waldi Ravens Ta Mt waldi@moacs.indiv.nl.net
.It Ta Darren Reed Ta Mt darrenr@NetBSD.ORG
.It Ta Tim Rightnour Ta Mt garbled@NetBSD.ORG
.It Ta Heiko W. Rupp Ta Mt hwr@NetBSD.ORG
.It Ta SAITOH Masanobu Ta Mt msaitoh@NetBSD.ORG
.It Ta Kazuki Sakamoto Ta Mt sakamoto@NetBSD.ORG
.It Ta Curt Sampson Ta Mt cjs@NetBSD.ORG
.It Ta Wilfredo Sanchez Ta Mt wsanchez@NetBSD.ORG
.It Ta Ty Sarna Ta Mt tsarna@NetBSD.ORG
.It Ta Matthias Scheler Ta Mt tron@NetBSD.ORG
.It Ta Karl Schilke (rAT) Ta Mt rat@NetBSD.ORG
.It Ta Tim Shepard Ta Mt shep@NetBSD.ORG
.It Ta Chuck Silvers Ta Mt chs@NetBSD.ORG
.It Ta Thor Lancelot Simon Ta Mt tls@NetBSD.ORG
.It Ta Noriyuki Soda Ta Mt soda@NetBSD.ORG
.It Ta Wolfgang Solfrank Ta Mt ws@NetBSD.ORG
.It Ta Bill Sommerfeld Ta Mt sommerfeld@NetBSD.ORG
.It Ta Ignatios Souvatzis Ta Mt is@NetBSD.ORG
.It Ta Bill Studenmund Ta Mt wrstuden@NetBSD.ORG
.It Ta Kevin Sullivan Ta Mt sullivan@NetBSD.ORG
.It Ta Kimmo Suominen Ta Mt kim@NetBSD.ORG
.It Ta Matt Thomas Ta Mt matt@NetBSD.ORG
.It Ta Christoph Toshok Ta Mt toshok@NetBSD.ORG
.It Ta Todd Vierling Ta Mt tv@NetBSD.ORG
.It Ta Paul Vixie Ta Mt vixie@NetBSD.ORG
.It Ta Krister Walfridsson Ta Mt kristerw@NetBSD.ORG
.It Ta Nathan Williams Ta Mt nathanw@NetBSD.ORG
.It Ta Colin Wood Ta Mt ender@NetBSD.ORG
.It Ta Steve Woodford Ta Mt scw@NetBSD.ORG
.
.El
.
.Ss "Legal Mumbo-Jumbo"
.
The following notices are required to satisfy the license terms of
the software that we have mentioned in this document:
.Pp
.nr save_size \n[.s]
.nr save_vs \n[.v]
.ps 8
.vs 9
.Ht <font size=-1>
.so ../common/legal.common -----------------------------------------------
.so legal -----------------------------------------------
.Ht </font>
.ps
.vs

View File

@ -0,0 +1,274 @@
.\" $NetBSD: mirrors,v 1.1 1999/01/13 08:18:45 ross Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.Ss2 "NetBSD Mirror Site List"
The following sites mirror NetBSD as of December 01, 1998.
.Pp
If you wish to become a distribution site for NetBSD, contact
.Mt mirrors@netbsd.org .
.Bl -tag -width 3n
.It "FTP Mirrors"
.de Country
.It \\$1
..
.de mirror
.Pp
\&\\$1
.br
\&\\$2
.br
\&\\$3
..
.Bl -tag -width 3n
.
.Country Australia
.mirror "ftp.au.netbsd.org" \
"RMIT University, Melbourne" \
"ftp://ftp.au.netbsd.org/pub/NetBSD"
.mirror "ftp2.au.netbsd.org" \
"University of Queensland, Brisbane" \
"ftp://ftp2.au.netbsd.org/pub/NetBSD"
.
.Country "Austria"
.mirror "ftp.at.netbsd.org" \
"University of Technology, Vienna" \
"ftp://ftp.at.netbsd.org/pub/NetBSD"
.
.Country "Brazil"
.mirror "ftp.ravel.ufrj.br" \
"Cidade Universitaria" \
"ftp://ftp.ravel.ufrj.br/pub/NetBSD"
.
.Country "Denmark"
.mirror "ftp.dk.netbsd.org" \
"Aalborg University" \
"ftp://ftp.dk.netbsd.org/pub/NetBSD"
.
.Country "Finland"
.mirror "ftp.fi.netbsd.org" \
"The Finnish University and Research Network, Espoo" \
"ftp://ftp.fi.netbsd.org/pub/NetBSD"
.
.Country "France"
.mirror "ftp.fr.netbsd.org" \
"Paris University" \
"ftp://ftp.fr.netbsd.org/pub/NetBSD"
.
.Country "Germany"
.mirror "ftp.de.netbsd.org" \
"University of Trier" \
"ftp://ftp.de.netbsd.org/pub/NetBSD"
.mirror "ftp2.de.netbsd.org" \
"University of Erlangen-Nuremberg" \
"ftp://ftp2.de.netbsd.org/pub/NetBSD"
.mirror "ftp.uni-regensburg.de" \
"University of Regensburg" \
"ftp://ftp.uni-regensburg.de/pub/comp/os/NetBSD"
.
.Country "Japan"
.mirror ftp.jp.netbsd.org "Internet Research Institute Inc., Tokyo" \
ftp://ftp.jp.netbsd.org/pub/NetBSD
.mirror "ftp.dti.ad.jp" \
"ftp://ftp.dti.ad.jp/pub/NetBSD/"
.mirror "mirror.nucba.ac.jp" \
"Nagoya University of Commerce and Business" \
"ftp://mirror.nucba.ac.jp/mirror/NetBSD"
.mirror "netbsd.tohoku.ac.jp" \
"Tohoku University" \
"ftp://netbsd.tohoku.ac.jp/NetBSD"
.
.Country "Korea"
.mirror "sunsite.kren.ne.kr" \
"Seoul National University" \
"ftp://sunsite.kren.ne.kr/pub/OS/NetBSD"
.
.Country "Netherlands"
.mirror "ftp.nl.netbsd.org" \
"University of Amsterdam" \
"ftp://ftp.nl.netbsd.org/pub/NetBSD"
.
.Country "Norway"
.mirror "ftp.no.netbsd.org" \
"ftp://ftp.no.netbsd.org/pub/NetBSD"
.mirror "ftp.ntnu.no" \
"Norwegian University of Science and Technology" \
"ftp://ftp.ntnu.no/pub/NetBSD"
.mirror "skarven.itea.ntnu.no" \
"Norwegian University of Science and Technology" \
"ftp://skarven.itea.ntnu.no/pub/NetBSD"
.
.Country Russia
.mirror ftp.ru.netbsd.org\
"Landau Institute for Theoretical Physics, Chernogolovka"\
ftp://ftp.ru.netbsd.org/pub/NetBSD
.
.Country "Sweden"
.mirror "ftp.stacken.kth.se" \
"Royal Institute of Technology, Stockholm" \
"ftp://ftp.stacken.kth.se/pub/OS/NetBSD"
.mirror "ftp.sunet.se" \
"Swedish University NETwork, Uppsala" \
"ftp://ftp.sunet.se/pub/os/NetBSD"
.
.Country "UK"
.mirror "ftp.uk.netbsd.org" \
"Domino, London" \
"ftp://ftp.uk.netbsd.org/pub/NetBSD"
.mirror "sunsite.org.uk" \
"ftp://sunsite.org.uk/packages/netbsd"
.
.Country "USA"
.mirror "ftp.netbsd.org" \
"Silicon Valley, California" \
"ftp://ftp.netbsd.org/pub/NetBSD"
.mirror "ftp.cs.umn.edu" \
"University of Minnesota" \
"ftp://ftp.cs.umn.edu/pub/NetBSD"
.mirror "ftp.eecs.umich.edu" \
"University of Michigan, Ann Arbor" \
"ftp://ftp.eecs.umich.edu/pub/NetBSD"
.mirror "ftp.iastate.edu" \
"Iowa State University" \
"ftp://ftp.iastate.edu/pub/netbsd"
.mirror "ftp.op.net" \
"ftp://ftp.op.net/pub/NetBSD"
.El
.It "AFS Mirrors"
.Bl -tag -width 3n
.
.Country "Sweden"
.mirror "ftp.stacken.kth.se" \
"Royal Institute of Technology, Stockholm" \
"AFS path: /afs/stacken.kth.se/ftp/pub/OS/NetBSD"
.
.Country "USA"
.mirror "ftp.iastate.edu" \
"Iowa State University" \
"AFS path: /afs/iastate.edu/public/ftp/pub/netbsd"
.El
.It "NFS Mirrors"
.Bl -tag -width 3n
.
.Country "UK"
.mirror "sunsite.org.uk" \
"Instructions: mount -o ro sunsite.org.uk:/public/packages/netbsd /mnt"
.El
.It "SUP Mirrors"
.Bl -tag -width 3n
.
.Country "Australia"
.mirror "sup.au.netbsd.org" \
"RMIT University, Melbourne" \
"Instructions: ftp://sup.au.netbsd.org/pub/NetBSD/sup/README.sup"
.
.Country "France"
.mirror "sup.fr.netbsd.org" \
"Paris University" \
"Instructions: Similar to sup.netbsd.org"
.
.Country "Germany"
.mirror "sup.de.netbsd.org" \
"University of Trier" \
"Instructions: ftp://sup.de.netbsd.org/pub/NetBSD/sup/supfile.example"
.mirror "sup.owl.de" \
"Instructions: ftp://sup.owl.de/pub/sup/supfile.example"
.
.Country Japan
.mirror "Internet Research Institute Inc., Tokyo"\
"Instructions: ftp://sup.jp.netbsd.org/pub/NetBSD/sup/README.sup"
.
.Country "Norway"
.mirror "skarven.itea.ntnu.no" \
"Norwegian University of Science and Technology" \
"Instructions: Use this line as your sup file to get /usr/README.supinfo-"
"skarven:current release=supinfo host=skarven.itea.ntnu.no use-rel-suffix"
"backup delete old base=/usr prefix=/usr hostbase=/supmirror"
.
.Country "UK"
.mirror "sup.uk.netbsd.org" \
"Domino, London" \
"Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup"
.
.Country "USA"
.mirror "sup.netbsd.org" \
"Silicon Valley, California" \
"Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup"
.mirror "ftp.cs.umn.edu" \
"University of Minnesota" \
"Instructions: hostbase=/ftp/ftp/packages/NetBSD, collections are the same"
"as on sup.NetBSD.ORG"
.El
.It "WWW Mirrors"
.Bl -tag -width 3n
.
.Country "Australia"
.mirror "www.au.netbsd.org" \
"RMIT University, Melbourne" \
"http://www.au.netbsd.org/"
.
.Country "Austria"
.mirror "www.at.netbsd.org" \
"University of Technology, Vienna" \
"http://www.at.netbsd.org/"
.
.Country "Finland"
.mirror "www.fi.netbsd.org" \
"Global Wire Oy, Lappeenranta" \
"http://www.fi.netbsd.org/"
.
.Country "France"
.mirror "www.fr.netbsd.org" \
"Paris University" \
"http://www.fr.netbsd.org/"
.
.Country "Germany"
.mirror "www.de.netbsd.org" \
"http://www.de.netbsd.org/"
.
.Country Japan
.mirror www.jp.netbsd.org\
"Internet Research Institute Inc., Tokyo" http://www.jp.netbsd.org/
.
.Country "Norway"
.mirror "www.no.netbsd.org" \
"http://www.no.netbsd.org/"
.
.Country "USA"
.mirror "www.netbsd.org" \
"Western Washington State University" \
"http://www.netbsd.org/"
.mirror "www2.us.netbsd.org" \
"New York" \
"http://www.us.netbsd.org/"
.El
.El

View File

@ -0,0 +1,215 @@
.\" $NetBSD: postinstall,v 1.1 1999/01/13 08:18:45 ross Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
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 propperly
configured state, with the most important ones described below.
.Bl -enum
.It
Configuring
.Pa /etc/rc.conf
.Pp
If you haven't done any configuration of
.Pa /etc/rc.conf ,
the system will drop you into single user mode on first reboot with the
message
.Dl /etc/rc.conf is not configured. Multiuser boot aborted.
and with the root filesystem mounted read-write. When the system
asks you to choose a shell, simply hit return to get to a
prompt. If you are asked for a terminal type, respond with
.Ic vt220
(or whatever is appropriate for your terminal type)
and hit return. At this point, you need to configure at least
one file in the
.Pa /etc No directory. Change to the
.Pa /etc
directory and take a look at the
.Pa /etc/rc.conf
file. Modify it to your tastes, making sure that you set
.Li rc_configured=YES
so that your changes will be enabled and a multi-user boot can
proceed. If your
.Pa /usr No directory is on a separate partition
and you do not know how to use 'ed' or 'ex', you will have to mount your
.Pa /usr
partition to gain access to 'vi'. Do the following:
.D1 Ic "mount /usr
.D1 Ic "export TERM=vt220
If you have
.Pa /var
on a seperate partition, you need to repeat
that step for it. After that, you can edit
.Pa /etc/rc.conf
with
.Xr vi 1 .
When you have finished, type
.Ic exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
.Pp
Other values that need to be set in
.Pa /etc/rc.conf
for a networked environment are
.Ar hostname No and possibly
.Ar defaultroute ,
furthermore add an
.Ar ifconfig_int
for your interface
.Aq int ,
along the lines of
.Dl ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0"
or, if you have
.Ar myname.my.dom No in Pa /etc/hosts :
.Dl ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
To enable proper hostname resolution, you will also want to add an
.Pa /etc/resolv.conf
file or (if you are feeling a little more adventurous) run
.Xr named 8 .
See
.Xr resolv.conf 5
or
.Xr named 8
for more information.
.It
Logging in
.Pp
After reboot, you can log in as
.Li root
at the login prompt. There
is no initial password, but 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.
.It
Adding accounts
.Pp
Use the
.Xr vipw 8
command to add accounts to your system,
.Em do not No edit Pa /etc/passwd
directly. See
.Xr adduser 8
for more information on the process of how to add a new user to the system.
.It
The X Window System
.Pp
If you have installed the X window system, look at the files in
.Pa /usr/X11R6/lib/X11/doc
for information.
.Pp
On NetBSD/i386 and NetBSD/arm32, you will need to set up a
configuration file, see
.Pa /usr/X11R6/lib/X11/XF86Config.eg
for an example. See
.Lk http://www.xfree86.org/
and the XFree86 manual page for more information.
.if r_pmax \{\
.Pp
NetBSD/pmax \*V uses an X11R5 X server. These servers cannot read
the compressed fonts which are shipped with standard X11R6
configurations. You must take post-installation steps to make the
X11R5 server work with the fonts that are standard for X11R6.3.
The distribution file
.Pa /usr/X11R6/bin/README.pmax
contains
information on how to choose an Xserver and how to access
compressed fonts via a font server or to decompress the X fonts
after installation. Please follow the directions there.
.\}
.Pp
Don't forget to add
.Pa /usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
.It
Installing 3rd party packages
.Pp
There is a lot of software freely available for Unix-based systems,
almost all of which can run on
.Nx .
Modifications are usually needed to
when transferring programs between different Unix-like systems, so
the
.Nx
packages collection incorporates any such
changes necessary to make that software run on
.Nx ,
and makes
the installation (and deinstallation) of the software packages
easy. There's also the option of building a package from source, in
case there's no precompiled binary available.
.Pp
Precompiled binaries can be found at
.Lk ftp://ftp.netbsd.org/pub/NetBSD/packages/
Package sources for compiling packages can be obtained by
retrieving the file
.Lk ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/pkgsrc.tar.gz
and extracting it into
.Pa /usr/pkgsrc .
See
.Pa /usr/pkgsrc/README
then for more information.
.It
Misc
.Bl -bullet
.It
To adjust the system to your local timezone, point the
.Pa /etc/localtime
symlink to the appropriate file under
.Pa /usr/share/zoneinfo .
.It
Edit
.Pa /etc/aliases
to forward root mail to the right place (run
.Xr newaliases 1
afterwards.)
.It
The
.Pa /etc/sendmail.cf
file will almost definitely need to be adjusted;
files aiding in this can be found in
.Pa /usr/share/sendmail .
See the
.Li Tn README
file there for more information.
.It
Edit
.Pa /etc/rc.local
to run any local daemons you use.
.It
Many of the
.Pa /etc
files are documented in section 5 of the manual; so just invoking
.D1 Ic man Ar filename
is likely to give you more information on these files.
.El
.El

View File

@ -0,0 +1,768 @@
.\" $NetBSD: sysinst,v 1.1 1999/01/13 08:18:45 ross Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.
.
.de (pcmcia
. Bl -tag -width x[PCMCIA]x
.It [ Tn PCMCIA ]
..
.de pcmcia)
. El
..
.
.de It_need
.br
.ne 6P
\\*[It]\\
..
.
.
.Ss2 "Running the Sysinst Installation Program"
.Bl -enum
.It_need
.Em Introduction
.Pp
Using
.Ic sysinst ,
installing
.Nx
is a relatively easy process. You
still should read this document and have it in hand when doing the
installation process. This document tries to be a good guideline
for the installation and as such covers many details to be completed.
Do not let this discourage you, the install program is not hard
to use.
.
.It_need
.Em Possible Tn PCMCIA Em issues
.Pp
There is a serious bug that may make installation of
.Nx
on
.Tn PCMCIA
machines difficult. This bug does not make
.Em use
of
.Tn PCMCIA
difficult once a machine is installed. If you do not have
.Tn PCMCIA
on your
machine
.Op Tn PCMCIA
is only really used on laptop machines), you
can skip this section, and ignore the
.Dq Bq Tn PCMCIA
notes.
.Pp
This will explains how to work around the installation problem.
It is anticipated that this bug will be fixed by
.Nx
1.4
.Pp
What is the bug: The kernel keeps careful track of what interrupts
and i/o ports are in use during autoconfiguration. It then allows
the
.Tn PCMCIA
devices to pick unused interrupts and ports.
Unfortunately, not all devices are included in the
.Tn Li INSTALL
kernels in order to save space. Let's say your laptop has a
soundblaster device built in. The
.Tn Li INSTALL
kernel has no sound support. The
.Tn PCMCIA No code might allocate your soundblaster's
.Tn IRQ No and I/O ports to
.Tn PCMCIA
devices, causing them not to work. This
is especially bad if one of the devices in question is your
ethernet card.
.Pp
This problem will impact some, but not all, users of
.Tn PCMCIA .
If this bug is affecting you, watch the
.Bq Tn PCMCIA
notes that will appear in this document.
.It_need
.Em General
.Pp
The following is a walk-through of the steps you will take while
getting
.Nx
installed on your hard disk.
.Ic sysinst
is a menu driven
installation system that allows for some freedom in doing the
installation. Sometimes, questions will be asked and in many cases
the default answer will be displayed in brackets
.Pq Dq \&[\ ]
after the question. If you wish to stop the installation, you may hit Control-C
at any time, but if you do, you'll have to begin the installation
process again from scratch.
.It_need
.Em Quick install
.Pp
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 section 3. This section
describes a basic installation, using a CD-ROM install as
an example.
.Pp
.Bl -bullet
.It_need
What you need.
.Bl -hyphen
.It_need
The distribution sets (in this example, they are on CD).
.It_need
.ie r_alpha Two floppy disks.
.el One 1.44M 3.5\" floppy.
.It_need
.if r_i386 A PC with a 386 or newer processor.
A CD-ROM drive (SCSI or ATAPI), a harddisk and a minimum of
.if r_i386 4Mb
.if r_alpha 32Mb
of memory installed.
.It_need
The harddisk should have at least
.if r_i386 70
.if r_alpha 200
+
.Em n
megabytes of
space free, where
.Em n
is the number of megabytes of
main memory in your system. If you wish to install
the X window system as well, you will need at least
60Mb more.
.El
.if r_i386 \{\
.It_need
Creating a Bootfloppy.
You can create the floppy needed for installation
under DOS or Windows. Supposing your 1.44M floppy
drive is drive A:, and your CD is drive E: do the
following from an MS-DOS command prompt:
.D1 Ic "\&e:
.D1 Ic "\&cd \eNetBSD-\*V\einstallation\emisc
.D1 Ic "\&rawrite
When asked for a source filename, answer
.if r_i386 .D1 Ic \&..\efloppy\eboot.fs
.if r_alpha .D1 Em \&(...alpha installation root) Ns Ic \efloppy\edisk1of2
When asked for a destination drive answer
.D1 Ic a
.It_need
To create the bootfloppy under
.Nx
or other UNIX-like system, you
would type something like:
.D1 Ic "dd if=.../boot.fs bs=18k of=/dev/rfd0a
.\}
.It_need
The Quick Installation
.Bl -hyphen
.It_need
Insert the boot floppy you just created.
.ie r_i386 Restart
.el Boot
the computer.
.if r_alpha Type
.if r_alpha .Dl \&\*>\*>\*> Ic "B DVA0
The main menu will be displayed.
.It_need
If you wish, you can configure some network settings
immediately by choosing the
.Me utilities
menu and then
.Me configure network .
It isn't actually required at this point, but
it may be more convenient. Go back to the main menu.
.It_need
Choose
.Me install
.It_need
You will be guided through some steps regarding the
setup of your disk, and the selection of distributed components
to install. When in doubt, refer to the rest of this document for details.
.It_need
After your disk has been prepared, choose
.Me CD-ROM
as the medium. The default values for the path and device should be ok.
.It_need
After all the files have been unpacked, go back to
the main menu and select
.Me reboot ,
after you have removed the bootfloppy from the drive.
.It_need
.Nx
will now boot. You should log in as
.Li root ,
and set a password for that account. You are also
advised to edit the file
.Pa /etc/rc.conf No to match your system needs.
.It_need
Your installation is now complete.
.It_need
For configuring the X window system, if installed, see the files in
.Dl /usr/X11R6/lib/X11/doc .
Further information can be found on
.Lk http://www.xfree86.org/
.El
.El
.It_need
.Em Booting
.Nx
.
.
.(pcmcia
Unplug your
.Tn PCMCIA
devices, so that they won't be found by
.Nx .
.pcmcia)
.
.
.Pp
Boot your machine using the boot floppy. The boot loader will
start, and will print a countdown and begin booting. You will
likely see one
.Li file not found
warning from the boot loader.
Ignore this, it merely indicates that the boot loader
did not find a normal kernel to boot before trying to boot a
compressed kernel.
.Pp
If the boot loader messages do not appear in a reasonable
amount of time, you either have a bad boot floppy or a
hardware problem. Try writing the install floppy image to
a different disk, and using that.
.if r_i386 \{\
.Pp
If that doesn't work, try booting after disabling your CPU's
internal and external caches (if any). If it still doesn't
work,
.Nx
probably can't be run on your hardware. This can
probably be considered a bug, so you might want to report it.
If you do, please include as many details about your system
configuration as you can.
.\}
.Pp
It will take a while to load the kernel from the floppy,
probably around a minute or so, then, the kernel boot messages
will be displayed. This may take a little while also, as
.Nx
will be probing your system to discover which hardware devices are
installed.
.if r_i386 \{\
You may want to read the
boot messages, to notice your disk's name and geometry. Its name
will be something like
.Li sd0
or
.Li wd0
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
.Ic sysinst
on which disk
to install.
.\}
The most important thing to know is that
.Li wd0
is NetBSD's name for your first IDE disk,
.Li wd1
the second, etc.
.Li sd0
is your first SCSI disk,
.Li sd1
the second, etc.
.Pp
Note that, once the system has finished booting, you need not
leave the floppy in the disk drive.
.if r_i386 \{\
Earlier version of
the
.Nx
install floppies mounted the floppy as the system's
root partition, but the new installation floppies use a
ramdisk file system and are no longer dependent on the floppy
once it has booted.
.\}
.Pp
Once
.Nx
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.
.It_need
.Em Network configuration
.(pcmcia
You can skip this section, as you will only get data
from floppy in the first part of the install.
.pcmcia)
.Pp
If you will not use network operation during the installation,
but you do want your machine to be configured for networking once
it is installed, you should first go to the utilities menu, and select
.Ic 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 Domain Name Service (DNS),
you can give an empty response in reply to answers relating to
this.
.It_need
.Em Installation drive selection and parameters
.Pp
To start the installation, select the menu option to install
.Nx
from the main menu.
.Pp
The first thing is to identify the disk on which you want to
install
.Nx .
.Ic sysinst
will report a list of disks it finds
and ask you for your selection. Depending on how many disks
are found, you may get a different message. You should see
disk names like
.Li wd0 ,
.Li wd1 ,
.Li sd0 ,
or
.Li sd1 .
.if r_i386 \{\
.Pp
.Ic sysinst
next tries to figure out the real and BIOS geometry
of your disk. It will present you with the values it found,
if any, and will give you a chance to change them.
Please note that if you change the values,
.Ic sysinst
.Em will also reinitialize your MBR .
.\}
.Pp
You will also be asked if you want to use the last cylinder of
the disk. Originally, the last cylinder of the disk was used for
diagnostic purposes, but this is usually not a concern anymore
these days. You will be able to specify whether you want to
skip the last cylinder anyway.
.Pp
Next, depending on whether you are using a
.Li Pf wd Em x
or
.Li Pf wd Em x
disk,
you will either be asked for the type of disk
.Pq Li Pf wd Em x
you are
using or you will be asked if you want to specify a fake geometry
for your SCSI disk
.Pq Li Pf sd Em x .
The types of disk are be
.Tn IDE, ST-506
or
.Tn ESDI .
If you're installing on an
.Tn ST-506
or
.Tn ESDI
drive, you'll be asked if your disk supports automatic sector forwarding.
If you are
.Em sure
that it does, reply affirmatively. Otherwise, the install
program will automatically reserve space for bad144 tables.
.It_need
.Em Partitioning the disk.
.Bl -bullet
.It_need
Which portion of the disk to use.
.Pp
You will be asked if you want to use the entire disk or
only part of the disk. If you decide to use the entire disk
for
.Nx ,
it will be checked if there are already other
systems present on the disk, and you will be asked to confirm
whether you want to overwrite these.
.Pp
If you want to use the entire disk for
.Nx ,
you can skip
the following section and go to
.Em Editing the
.Nx
.Em disklabel .
.if r_i386 \{\
.It_need
Editing the Master Boot Record.
.Pp
First, you will be prompted to specify the units of size
that you want to express the sizes of the partitions in.
You can either pick megabytes, cylinders or sectors.
.Pp
After this, you will be presented with the current values
stored in the MBR, and will be given the opportunity to
change, create or delete partitions. For each partition
you can set the type, the start and the size. Setting the type to
.Ic unused
will delete a partition. You can
also mark a partition as active, meaning that this is
the one that the BIOS will start from at boot time.
.Pp
Be sure to mark the partition you want to boot from as active!
.Pp
After you are done editing the MBR, a sanity check
will be done, checking for partitions that overlap.
If everything is ok, you can go on to the next step,
editing the
.Nx
disklabel.
.Pp
.\}
.It_need
.Em Editing the
.Nx
.Em disklabel .
.Pp
The partition table of the
.Nx
part of a disk is called a
.Em disklabel .
There are 3 layouts for the
.Nx
part of the disk that you can pick from:
.Ic Standard, Standard with X
and
.Ic Custom .
The first two use a set of default
values (that you can change) suitable for a normal
installation, possibly including X. The last option
lets you specify everything yourself.
.Pp
You will be presented with the current layout of the
.Nx
disklabel, and given a chance to change it.
For each partition, you can set the type, offset and size,
block and fragment size, and the mount point. The type
that
.Nx
uses for normal file storage is called
.Sy 4.2BSD .
A swap partition has a special type called
.Sy swap .
.
.
.ie r_i386 \{\
.
.
You can also specify a partition as type
.Sy msdos .
This is useful if you share the disk with
.Tn MS-DOS
or Windows95;
.Nx
is able to access the files on these partitions.
You can use the values from the MBR for the MS-DOS part
of the disk to specify the partition of type
.Sy msdos
(you don't have to do this now, you can always re-edit
the disklabel to add this once you have installed NetBSD).
.Pp
Some partitions in the disklabel have a fixed purpose.
Partition
.Sy \&a
is always the root partition,
.Sy \&b
is the swap partition,
.Sy \&c
is the entire
.Nx
part of the disk, and
.Sy \&d
is the whole disk. Partitions
.Sy \&e-h
are available
for other use. Traditionally,
.Sy \&e
is the partition mounted on the
.Pa /usr
directory, but this is historical practice, not a fixed value.
.
.
.\}
.el \{\
.
.
.Pp
Some partitions in the disklabel have a fixed purpose. Partition
.Sy a No is always the root partition,
.Sy b No is the swap partition, and
.Sy c No is the whole disk. Partitions
.Sy \&e-h
are available for other use. Traditionally,
.Sy \&d
is the partition mounted on the
.Pa /usr
directory, but this is historical practice, not a fixed value.
.
.
.\}
.
.
.Pp
You will then be asked to name your disk's disklabel. The
default response is
.Sy mydisk .
For most purposes this will be OK.
If you choose to name it something different, make sure the name
is a single word and contains no special characters. You don't
need to remember this name.
.El
.Pp
.It_need
.Em Preparing your hard disk
.Pp
.Em 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
.Nx ,
your hard drive will be modified. If you are
sure you want to proceed, enter
.Li yes
at the prompt.
.Pp
The install program will now label your disk and make the file
systems you specified. The filesystems will be initialized to
contain
.Nx
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.
.if r_i386 \{\
.Pp
NOTE: In previous versions of
.Nx ,
the kernel from the
install floppy was copied onto the hard drive in a special
step. In the new install system, the kernel on the floppy is
unsuited to being copied onto the hard drive. Instead, a new set,
.Sy kern ,
has been added which contains a generic kernel to
be unloaded onto the drive. So, you can not boot from your
hard drive yet at this point.
.\}
.It_need
.Em Getting the distribution sets.
.if r_i386 \{\
.(pcmcia
.
Load a kernel tar file (i.e. the kern.tgz set file)
on to your hard disk, for example by mounting the
hard disk first, copying the kern.tgz file from
floppy and unpacking it. Example:
.(disp
mount /dev/wd0a /mnt
cd /mnt
\*<repeat following 3 steps until all kern.* files are there\*>
mount -t msdos /dev/fd0a /mnt2
cp /mnt2/kern.* .
umount /mnt2
cat kern.* | tar vxzf -
.disp)
.Pp
Then halt the machine using the 'halt' command. Power
the machine down, and re-insert all the
.Tn PCMCIA
devices.
Remove any floppy from the floppy drive.
Start the machine up. After booting
.Nx ,
you will
be presented with the main
.Ic sysinst
menu. Choose the
option to re-install sets. Wait for the filesystem
checks that it will do to finish, and then proceed
as described below.
.pcmcia)
.\}
.Pp
The
.Nx
distribution consists of a number of
.Em sets ,
that come in the form of gzipped tarfiles. A few sets must be
installed for a working system, others are optional. At this
point of the installation, you will be presented with a menu
which enables you to choose from one of the following methods
of installing the sets. Some of these methods will first
load the sets on your hard disk, others will extract the sets
directly.
.Pp
For all these methods, the first step is making the sets
available for extraction, and then do the actual installation.
The sets can be made available in a few different ways. The
following sections describe each of those methods. After
reading the one about the method you will be using, you
can continue to section 9
.It_need
.Em Installation using ftp
.Pp
To be able to install using ftp, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
.Ic sysinst
will do this for you, asking you
to provide some data, like IP number, hostname, etc. If you
do not have name service set up for the machine that you
are installing on, you can just press return in answer
to these questions, and DNS will not be used.
.Pp
You will also be asked to specify the host that you want
to transfer the sets from, the directory on that host,
and the account name and password used to log into that
host using ftp. If you did not set up DNS when answering
the questions to configure networking, you will need to
specify an IP number instead of a hostname for the ftp
server.
.Pp
.Ic sysinst
will proceed to transfer all the default set files
from the remote site to your hard disk.
.It_need
.Em Installation using NFS
.Pp
To be able to install using NFS, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
.Ic sysinst
will do this for you, asking you
to provide some data, like IP number, hostname, etc. If you
do not have name service set up for the machine that you
are installing on, you can just press return in answer
to these questions, and DNS will not be used.
.Pp
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.
.Pp
If you did not set up DNS when answering the questions to
configure networking, you will need to specify an IP number
instead of a hostname for the NFS server.
.It_need
.Em Installation from CD-ROM
.Pp
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM player
.Pq usually Li cd0 ,
and the directory name on the CD-ROM where the distribution files are.
.Pp
.Ic sysinst
will then check if the files are indeed available
in the specified location, and proceed to the actual
extraction of the sets.
.if !ralpha \{\
.It_need
.Em Installation from a floppy set
.Pp
Because the installation sets are too big to fit on one floppy,
the floppies are expected to be filled with the split set
files. The floppies are expected to be in MS-DOS
format. You will be asked for a directory where the sets
should be reassembled. Then you will be prompted to insert
the floppies containing the split sets. This process
will continue until all the sets have been loaded from floppy.
.\}
.It_need
.Em Installation from an unmounted filesystem
.Pp
In order to install from a local filesystem, you will
need to specify the device that the filesystem resides
on
.Pq for example Li wd1e ,
the type of the filesystem,
and the directory on the specified filesystem where the sets are located.
.Ic sysinst
will then check if it
can indeed access the sets at that location.
.It_need
.Em Installation from a local directory
.Pp
This option assumes that you have already done some preparation
yourself. The sets should be located in a directory on a
filesystem that is already accessible.
.Ic sysinst
will ask you
for the name of this directory.
.It_need
.Em Extracting the distribution sets
.Pp
After the install sets containing the
.Nx
distribution
have been made available, you can either extract all the
sets (a full installation), or only extract sets that
you have selected. In the latter case you will be shown the
currently selected sets, and given the opportunity to select
the sets you want. Some sets always need to be installed
.Pq Ic kern, base No and Ic etc
they will not be shown in this selection menu.
.Pp
Before extraction begins, you can elect to watch the files
being extracted; the name of each file that is extracted will
be shown.
.Pp
After all the files have been extracted, all the necessary
device node files will be created. If you have already
configured networking, you will be asked if you want to
use this configuration for normal operation. If so, these
values will be installed in the network configuration files.
.It_need
.Em Finalizing your installation.
.Pp
Congratulations, you have successfully installed
.Nx \*V .
You can now reboot the machine, and boot from harddisk.
.El

View File

@ -0,0 +1,127 @@
.\" $NetBSD: upgrade,v 1.1 1999/01/13 08:18:45 ross Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.
.
.ie r_arm32 \{\
.
.
Upgrading from a previous version of
.Nx
isn't currently supported by
NetBSD/arm32. If you are currently running NetBSD/arm32 then make a
FULL BACKUP of your current installation, and install
.Nx \*V
from scratch. Obviously some of the steps can be skipped (in particular,
hard disk partitioning) as they will already be done.
.
.
.\}
.el \{\
.
.
.Pp
The upgrade to
.Nx \*V
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.
.Pp
To do the upgrade, you must have the boot floppy
.if r_alpha set
available. You must also have at least the
.Ic base No and Ic kern
binary distribution sets available, so that you can upgrade with them,
using one of the upgrade methods described above. Finally, you must
have sufficient disk space available to install the new binaries.
Since the old binaries are being overwritten in place, you only need
space for the new binaries, which weren't previously on the system.
If you have a few megabytes free on each of your root and
.Pa /usr
partitions, you should have enough space.
.Pp
Since upgrading involves replacing the boot blocks on your
.Nx
partition, the kernel, and most of the system binaries, it has the
potential to cause data loss. You are strongly advised to
.Em back up any important data on your disk ,
whether on the
.Nx
partition or on
another operating system's partition, before beginning the upgrade
process.
.Pp
The upgrade procedure using the
.Ic sysinst No tool is similar to
an installation, but without the hard disk partitioning.
Another difference is that existing configuration files in
.Pa /etc
are backed up and merged with the new files. Getting the binary
sets is done in the same manner as the installation procedure;
refer to the installation part of the document
for how to do this. Also, some sanity checks are done, i.e.
filesystems are checked before unpacking the sets.
.Pp
After a new kernel has been copied to your hard disk, your
machine is a complete
.Nx \*V
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
.Pa /dev .
If you've changed the contents of
.Pa /dev
by hand, you will need to be careful about this, but if
not, you can just cd into
.Pa /dev No , and run the command
.Dl sh MAKEDEV all
.Pp
You must also deal with certain changes in the formats of
some of the configuration files. The most notable change is
that the options given to many of the file systems in
.Pa /etc/fstab
have changed, and some of the file
systems have changed names. To find out what the new options
are, it's suggested that you read the manual page
for the file systems' mount commands, for example
.Xr mount_nfs 8
for NFS.
.Pp
Finally, you will want to delete old binaries that were part
of the version of
.Nx
that you upgraded from and have since been removed from the
.Nx
distribution.
.\}

216
distrib/notes/common/xfer Normal file
View File

@ -0,0 +1,216 @@
.\" $NetBSD: xfer,v 1.1 1999/01/13 08:18:45 ross Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
Installation is supported from several media types, including:
.Pp
.Bl -bullet -compact
.It
CDROM
.It
DOS Floppy
.It
Tape
.It
Remote NFS partition
.It
FTP
.El
.if r_arm32 \{\
. Pp
No matter which installation medium you choose, you'll need to have an
installation kernel and possibly a boot application, see
. Li arm32/ Ns Ar platform Ns Li /prep
for details.
.\}
.Pp
Note that, if you are installing or upgrading from a writable media,
the media can be write-protected if you wish. These systems mount a
root image from inside the kernel, and will not need to write to the
media.
.Pp
The distribution sets for
installation or upgrade depend on which installation medium you
choose. The steps for the various media are outlined below.
.Bl -bullet
.It
To install or upgrade NetBSD using CDROM, you need to do the
following:
.Pp
Find out where the distribution set files are on the CDROM.
.Pp
Proceed to the instruction on installation.
.It
To install or upgrade NetBSD using DOS floppies, you need to do the
following:
.Pp
Count the number of "set_name.xx" files that make up the
distribution sets you want to install or upgrade. You will
need that number of 1.44M floppies.
.Pp
Format all of the floppies with DOS. DO NOT make any of them
bootable DOS floppies. (If the floppies are bootable, then
the DOS system files that make them bootable will take up
some space, and you won't be able to fit the distribution set
parts on the disks.) If you're using floppies that are
formatted for DOS by their manufacturers, they probably
aren't bootable, and you can use them out of the box.
.Pp
Place all of the "set_name.xx" files on the DOS disks.
.Pp
Once you have the files on DOS disks, you can proceed to the
next step in the installation or upgrade process. If you're
installing NetBSD from scratch, go to the section on preparing
your hard disk, below. If you're upgrading an existing
installation, go directly to the section on upgrading.
.It
To install or upgrade NetBSD using a tape, you need to do the
following:
.Pp
To install NetBSD from a tape, you need to make a tape that
contains the distribution set files, in "tar" format. If
you're making the tape on a UN*X-like system, the easiest way
to do so is probably something like:
.Li tar cf Ar tape_device dist_directories
.No where Ar tape_device
is the name of the tape device that
describes the tape drive you're using (possibly
.Pa /dev/rst0 ,
or something similar, but it will vary from system to system.
(If you can't figure it out, ask your system administrator.)
In the above example,
.Ar dist_directories
are the
distribution sets' directories, for the distribution sets you
wish to place on the tape. For instance, to put the
.Sy misc, base, No and Sy etc
distributions on tape (in
order to do the absolute minimum installation to a new disk),
you would do the following:
.D1 Ic "cd \&.../NetBSD-\*V # the top of the tree
.D1 Ic "cd \*[MACHINE]/binary
And then:\ \~
.D1 tar \&cf Ar tape_device Ic misc etc kern
.Pp
.(Note
You still need to fill in
.Ar tape_device No in the example.
.Note)
.Pp
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.
.It
To install or upgrade NetBSD using a remote partition, mounted via
NFS, you must do the following:
.(Note
This method of installation is recommended only for
those already familiar with using BSD network
configuration and management commands. If you aren't,
this documentation should help, but is not intended to
be all-encompassing.
.Note)
.Pp
Place the NetBSD distribution sets you wish to install into a
directory on an NFS server, and make that directory mountable
by the machine on which you are installing or upgrading NetBSD.
This will probably require modifying the /etc/exports file on
of the NFS server and resetting its mount daemon (mountd).
(Both of these actions will probably require superuser
privileges on the server.)
.Pp
You need to know the the numeric IP address of the NFS server,
and, if the server is not on a network directly connected to
the machine on which you're installing or upgrading NetBSD,
you need to know the numeric IP address of the router closest
to the NetBSD machine. Finally, you need to know the numeric
IP address of the NetBSD machine itself.
.Pp
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.
.It
To install or upgrade NetBSD by using FTP to get the installation
sets, you must do the following:
.Pp
.(Note
This method of installation is recommended only for
those already familiar with using BSD network
configuration and management commands. If you aren't,
this documentation should help, but is not intended to
be all-encompassing.
.Note)
.Pp
The preparations for this installation/upgrade method are
easy; all you make sure that there's some FTP site from which
you can retrieve the NetBSD distribution when you're about to
install or upgrade. You need to know the numeric IP address
of that site, and, if it's 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.
.Pp
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.
.It
If you are upgrading NetBSD, you also have the option of installing
NetBSD by putting the new distribution sets somewhere in your existing
file system, and using them from there. To do that, you must do the
following:
.Pp
Place the distribution sets you wish to upgrade somewhere in
your current file system tree. Please note that the /dev on
the floppy used for upgrades only knows about wd0, wd1, sd0,
sd1 and sd2. If you have more than two IDE drives or more than
three SCSI drives, you should take care not to place the sets
on the high numbered drives.
.Pp
At a bare minimum, you must upgrade the "base" binary
distribution, and so must put the "base13" set somewhere in
your file system. If you wish, you can do the other sets, as
well, but you should NOT upgrade the "etc" distribution; the
"etc" distribution contains system configuration files that
you should review and update by hand.
.Pp
Once you have done this, you can proceed to the next step in
the upgrade process, actually upgrading your system.
.El