Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

_ copyright crank 

- whitespace cleanup
- formatting cleanup (start sentences on new lines)
This commit is contained in:
lukem 2002-06-29 08:32:30 +00:00
parent c8ef0c6235
commit cb50ccb853
6 changed files with 578 additions and 459 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

303
distrib/notes/common/contents
View File

@ -1,6 +1,6 @@
.\" $NetBSD: contents,v 1.62 2002/06/28 15:26:38 skrll Exp $
.\" $NetBSD: contents,v 1.63 2002/06/29 08:32:30 lukem Exp $
.\"
.\" Copyright (c) 1999-2001 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -76,20 +76,21 @@ four megabytes of RAM.
.if r_amiga \{\
. It Pa netbsd.INSTALL.gz
A somewhat smaller kernel, which you can use to boot the system
using loadbsd for installation on memory-tight systems. This is the
same kernel as present on the miniroot.
using loadbsd for installation on memory-tight systems.
This is the same kernel as present on the miniroot.
.\}
.
.if r_atari \{\
. It Pa netbsd-ATARITT.gz
A kernel specifically tuned for the Atari TT030.
. It Pa netbsd-BOOT.gz
A kernel for both the Falcon and TT030. It is kept pretty small, so you
A kernel for both the Falcon and TT030.
It is kept pretty small, so you
can use it to boot the system for installation on memory-tight systems.
This is the kernel supplied on the boot.fs floppy.
. It Pa netbsd-BOOTX.gz
Same as the BOOT kernel, but it has slightly more features. You can run X11
with it.
Same as the BOOT kernel, but it has slightly more features.
You can run X11 with it.
. It Pa netbsd-FALCON.gz
A kernel specifically tuned for the Atari Falcon.
. It Pa netbsd-HADES.gz
@ -107,7 +108,7 @@ A kernel for TX3912 machines.
.
.if r_i386 \{\
. It Pa netbsd.GENERIC_LAPTOP.gz
A version of
A version of
.Li GENERIC
that has USB, PCMCIA and CardBus enabled to allow
installing on laptop machines.
@ -130,28 +131,29 @@ A version of
.Li INSTALL
intended to fit on a 5.25"/1.2 MB diskette.
. It Pa netbsd.INSTALL_LAPTOP.gz
A version of
A version of
.Li INSTALL
that has USB, PCMCIA and CardBus enabled to allow
installing on laptop machines.
. It Pa netbsd.INSTALL_PS2.gz
A version of
A version of
.Li INSTALL
that has MCA stuff enabled to allow installing on IBM PS/2 machines.
.\}
.if r_macppc \{\
. It Pa netbsd.GENERIC_MD.gz
A gzipped
A gzipped
.Nx
kernel containing code for everything supported in this release. It also
has a RAM-disk installer. This is the kernel you should use when you want
to install via from an HFS partition on Open Firmware 3 systems, netboot,
or from a CD-R.
kernel containing code for everything supported in this release.
It also has a RAM-disk installer.
This is the kernel you should use when you want to install via from an
HFS partition on Open Firmware 3 systems, netboot, or from a CD-R.
. It Pa netbsd.INSTALL.gz
A gzipped
.Nx kernel containing code only for Open Firmware 1.0.5, 1.1.22, 2.0.x,
and 2.4 systems (i.e. those that have floppy drives). It has a RAM-disk
installer. This is the kernel you should use when you want to install on
and 2.4 systems (i.e. those that have floppy drives).
It has a RAM-disk installer.
This is the kernel you should use when you want to install on
one of these systems from a floppy disk.
.\}
.
@ -184,10 +186,11 @@ in this release.
. It Pa netbsd.img-WALNUT.gz
Same as the above, but in the format expected by the firmware.
. It Pa netbsd.INSTALL.gz
A gzipped
A gzipped
.Nx
kernel (ELF format) containing code for everything supported in this
release. It also includes a RAM-disk installer with sysinst.
release.
It also includes a RAM-disk installer with sysinst.
. It Pa netbsd.INSTALL.img.gz
Same as the above, but in the format expected by the firmware.
.\}
@ -244,8 +247,8 @@ contains
.Pa GENERIC.fs ,
a
.Li GENERIC
kernel in a bootable file system image. This is used in some unusual
installations as described in the next section.
kernel in a bootable file system image.
This is used in some unusual installations as described in the next section.
.\}
.ie r_sparc \{\
Statically-linked versions of
@ -262,8 +265,9 @@ installation section, below.
.
.if r_macppc \{\
. It Pa floppy/boot.fs
\*M boot and installation floppy image. Only usable on models that
ship with a floppy drive (pre-Open Firmware 3); see below.
\*M boot and installation floppy image.
Only usable on models that ship with a floppy drive (pre-Open Firmware 3);
see below.
. It Pa ofwboot.xcf
\*M bootloader; see below.
.\}
@ -312,21 +316,22 @@ There are three bootable images in the
\*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
but intended to be written to a CD, tape, or hard drive.
The third image is a
.Li GENERIC
kernel intended for production use in unusual cases.
This can be useful at some sites when:
.(bullet
You want to run diskless but SRM bugs prevent the firmware from
netbooting. You can work around this problem by always booting the generic
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
does.
This happens more frequently than you might think.
SRM will usually only boot from
.Xr ncr 4
or
.Xr isp 4
@ -343,8 +348,9 @@ a kernel or always boot from floppy.
.if r_amiga \{\
.Ss2 Miniroot file system
The Amiga now uses a single miniroot file system for both an initial
installation and for an upgrade. A gzipped version is available, for easier
downloading. (The gzipped version has the
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.)
@ -362,10 +368,11 @@ This includes formatting and mounting your
(root) and
.Pa /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
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
.Tn AmigaDOS
partitions.
.tag)
@ -379,7 +386,8 @@ The
binary distribution sets contain the binaries which
comprise the
.Nx \*V
release for the \*M. There are eight binary distribution sets.
release for the \*M.
There are eight binary distribution sets.
The binary distribution sets can be found in the
.Pa \*M/binary/sets
subdirectory
@ -391,13 +399,15 @@ distribution tree, and are as follows:
.It Sy base
The
.Nx \*V
.No \*M Sy base No binary distribution. You
.No \*M Sy base No binary distribution.
You
.Em must
install this distribution set. It contains the base
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
system to run and be minimally functional.
It includes shared library support, and excludes
everything described below.
.br
.if r_acorn26 .Em 20.2 MB gzipped, ? MB uncompressed
@ -427,13 +437,14 @@ everything described below.
.if r_x68k .Em 12.5 MB gzipped, 34.0 MB uncompressed
.
.It Sy comp
Things needed for compiling programs. This set
includes the system include files
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
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
@ -467,7 +478,8 @@ system call and library manual pages.
This distribution set contains the system
configuration files that reside in
.Pa /etc
and in several other places. This set
and in several other places.
This set
.Em must
be installed if you are installing the system from scratch, but should
.Em not
@ -615,8 +627,8 @@ The sets are:
.(tag xcontrib
.It Sy xbase
The basic files needed for a complete X
client environment. This does not include
the X servers.
client environment.
This does not include the X servers.
.br
.\" Shareable within MACHINE_ARCH, except atari
.if r_alpha .Em 3.6 MB gzipped, 13.7 MB uncompressed
@ -709,9 +721,9 @@ The Xarm32VIDC and Xprt servers.
.
.if r_atari \{\
.It Sy xserver
The Xservers and some programs not shared with the other m68k ports. Please
consult the X specific section in the atari FAQ as to which server you should
use.
The Xservers and some programs not shared with the other m68k ports.
Please consult the X specific section in the atari FAQ as to which server
you should use.
.br
.Em 5.7 MB gzipped, 14.1 MB uncompressed
.\}
@ -725,11 +737,11 @@ The Xhpc server which supports 256 and 65536 colors, with man pages.
.
.if r_i386 \{\
.It Sy xserver
All XFree86 X servers. Because all of them are
included, this set is large. However, you will
only need one of the servers provided in this
set. (Typically,
.Ic XF86_SVGA . )
All XFree86 X servers.
Because all of them are included, this set is large.
However, you will only need one of the servers provided in this set.
(Typically,
.Ic XF86_SVGA ) .
.br
.Em 14.9 MB gzipped, 35.2 MB uncompressed
.\}
@ -768,8 +780,8 @@ servers with man pages.
.if r_sparc64 \{\
.It Sy xserver
The Xsun, Xsun24, XsunMono and Xprt
servers with man pages. The 64-bit X server current has problems with
pixmaps.
servers with man pages.
The 64-bit X server current has problems with pixmaps.
.br
.Em 3.4 MB gzipped, 8.9 MB uncompressed
.\}
@ -812,8 +824,8 @@ method, the files are
.Pa / Ns No -relative
and therefore are extracted
.Em below
the current directory. That
is, if you want to extract the binaries into your system, i.e.
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 -xpf"
command from
@ -831,7 +843,8 @@ bootloader,
.Ic boot26 ,
in the
.Pa installation/misc
subdirectory. This is a RISC OS relocatable module, and should have its file
subdirectory.
This is a RISC OS relocatable module, and should have its file
type set to ffa (Module) once it's been copied to a RISC OS system.
.\}
.
@ -843,19 +856,22 @@ in the
.Pa atari/binary/kernel
subdirectory of the
.Nx \*V
distribution tree. These kernels are generally named something like
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.
or some other suitable name.
Please note that these kernels are simply gzipped and are not in tar archives.
.Pp
There are six atari floppy images to be found in the
.Pa atari/installation/floppies
subdirectory of the
.Nx \*V
distribution. three of them are bootable
distribution.
Three of them are bootable
.Tn TOS
kernel floppies and the other
three are installation floppies. They are described in more detail below.
three 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
@ -864,13 +880,14 @@ extension added to their names.)
.It Em Bootable\ Kernel\ floppies
These
.Tn TOS
disks contains the
disks contains the
.Tn TOS
support programs (like
.Ic loadbsd.ttp
and
.Ic chg_pid.ttp
- see below) and a kernel. They are setup such that you can insert them'into
\(em see below) and a kernel.
They are setup such that you can insert them'into
your floppy drive, and start the programs from GEM.
.Pp
For the TT030 and Falcon, the (720 KB) floppy is named
@ -881,7 +898,7 @@ the kernel supplied is
For the Hades, you need the
.Pa hades-boot.fs
floppy (1.44 MB), the kernel is
.Li HADES .
.Li HADES .
For the Milan, you need the
.Pa milan-boot.fs
floppy (1.44 MB), the kernel is MILAN-PCIIDE.
@ -898,10 +915,12 @@ and mounting your
.Pa /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
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
file system or ftp.
You can also load distribution sets from a SCSI tape or from one of
your existing
.Tn GEMDOS
partitions.
.Pp
@ -938,7 +957,8 @@ The
program reads the partition tables present on a
given disk and tries to interpret then the same way the
.Nx
kernel does. If you have a disk on which
kernel does.
If you have a disk on which
.Tn GEMDOS
and
.Nx
@ -947,13 +967,13 @@ are to co-exist, It is a good idea to run this before you begin the
installation just to check that the kernel's view
of the partition tables agree with
.Tn GEMDOS Ns 's
view. If you have
more than 3 partitions defined on a disk you will notice that
the
view.
If you have more than 3 partitions defined on a disk you will notice that the
.Nx*M
partition starts one sector after the
.Tn GEMDOS
partition. This is to allow space for the auxiliary root for
partition.
This is to allow space for the auxiliary root for
the 4th and subsequent partitions.
.It
The
@ -971,7 +991,8 @@ The
.Ic chg_pid.ttp
program can be used to change the id of an
.Tn AHDI
compatible partition. This allows you to reserve a partition for use by
compatible partition.
This allows you to reserve a partition for use by
.Nx*M
(id: NBD), or for use as a swap (id: SWP) partition.
.It
@ -979,9 +1000,10 @@ The
.Ic file2swp.ttp
program can be used to transfer an installation filesystem image, like
.Pa sysinst.fs
to a partition with id SWP. In this way, you can run the installation from
the swap partition instead of a memory disk. This is a necessity for small
memory systems.
to a partition with id SWP.
In this way, you can run the installation from the swap partition
instead of a memory disk.
This is a necessity for small memory systems.
.bullet)
.\}
.
@ -1004,16 +1026,18 @@ 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
A gzipped copy of the universal boot block.
Supports Network, tape and disk booting.
This is useful if you are installing a diskless
.Nx*M
system.
. It Pa rbootd.tgz
Source code for the rbootd program included with
.Nx .
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.
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.
. tag)
.tag)
.
@ -1043,10 +1067,11 @@ in the
.Pa hpcmips/binary/kernels
subdirectory of the
.Nx \*V
distribution tree. These kernels are generally named something like
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.
or some other suitable name.
Please note that these kernels are simply gzipped and are not in tar archives.
.Pp
The
.Tn "Windows CE" Ns No -based utilities
@ -1057,26 +1082,28 @@ be found in the
.Pa hpcmips/installation/
subdirectory of the
.Nx \*V
distribution tree. The important files in this directory are as
follows:
distribution tree.
The important files in this directory are as follows:
.
.
.(tag pbsdboot1.exe
.It Pa netbsd.gz
.Nx*M
kernel with system installer (sysinst). This kernel runs on Vr41xx and
TX3922 CPU only.
kernel with system installer (sysinst).
This kernel runs on Vr41xx and TX3922 CPU only.
.br
.Em 1.98 MB gzipped, 6.7 MB uncompressed
.It Pa netbsd.TX3912.gz
.Nx*M
kernel with system installer (sysinst). This kernel runs on TX3912 CPU only.
kernel with system installer (sysinst).
This kernel runs on TX3912 CPU only.
.br
.Em 1.98 MB gzipped, 6.7 MB uncompressed
.It Pa hpcboot.exe
The
.Nx*M
boot loader utility. This program is used to boot the
boot loader utility.
This program is used to boot the
.Nx
kernel from within
.Tn "Windows CE"
@ -1086,7 +1113,8 @@ kernel from within
.It Pa pbsdboot.exe
The
.Nx*M
boot loader utility. This program is used to boot the
boot loader utility.
This program is used to boot the
.Nx
kernel from within
.Tn "Windows CE"
@ -1096,7 +1124,8 @@ kernel from within
.It Pa pbsdboot1.exe
The
.Nx*M
boot loader utility. This program is used to boot the
boot loader utility.
This program is used to boot the
.Nx
kernel from within
.Tn "Windows CE"
@ -1105,11 +1134,12 @@ kernel from within
.Em 191 KB
.tag)
.Pp
These
These
.Pa *.exe
files are
.Tn "Windows CE
binaries. If you need them,
binaries.
If you need them,
the sources for these utilities are in the
.Pa src/arch/hpc/stand/
and the
@ -1125,10 +1155,11 @@ in the
.Pa mac68k/binary/kernels
subdirectory of the
.Nx \*V
distribution tree. These kernels are generally named something like
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.
or some other suitable name.
Please note that these kernels are simply gzipped and are not in tar archives.
.Pp
The
.Tn MacOS
@ -1139,14 +1170,15 @@ be found in the
.Pa mac68k/installation/misc
subdirectory of the
.Nx \*V
distribution tree. The important files in this directory are as
follows:
distribution tree.
The important files in this directory are as follows:
.
.(tag Installer.sea.hqx
.It Pa Booter.sea.hqx
The
.Nx*M
Booter utility. This program is used to boot the
Booter utility.
This program is used to boot the
.Nx
kernel from within
.Tn MacOS .
@ -1155,24 +1187,25 @@ kernel from within
.It Pa Installer.sea.hqx
The
.Nx*M
Installer utility. This
program is used to install the distribution sets onto your
Installer utility.
This program is used to install the distribution sets onto your
.Nx
partition(s).
.br
.Em 147 KB archived
.It Pa Mkfs.sea.hqx
The Mkfs utility. This program is used to
format your chosen partitions so that they
The Mkfs utility.
This program is used to format your chosen partitions so that they
can be used with
.Nx .
.br
.Em 76 KB archived
.tag)
.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.
These files are all binhexed, self-extracting archives.
If you need them, the sources for these utilities are in the
.Pa src
subdirectory.
.\}
.
.if r_mvme68k \{\
@ -1188,7 +1221,8 @@ A copy of the miniroot file system.
This filesystem image is copied into the swap partition of the disk which
you intend to boot
.Nx
from. Normally, this step will be performed manually from the ramdisk boot
from.
Normally, this step will be performed manually from the ramdisk boot
environment.
. tag)
.tag)
@ -1197,15 +1231,15 @@ environment.
.It Pa netboot/
. (tag sboot
. It Pa sboot
An MVME147 bootstrap program in Motorola S-Record format. This is
required when you wish to boot an MVME147 over the network since
the ROM has no built-in network support. Instructions for getting
this program into memory are discussed later.
An MVME147 bootstrap program in Motorola S-Record format.
This is required when you wish to boot an MVME147 over the network since
the ROM has no built-in network support.
Instructions for getting this program into memory are discussed later.
. tag)
. (tag netboot
. It Pa netboot
A standalone 2nd stage bootstrap program loaded over the network
via TFTP. This is responsible for fetching and starting the
A standalone 2nd stage bootstrap program loaded over the network via TFTP.
This is responsible for fetching and starting the
.Nx
\*M
kernel from an NFS server.
@ -1216,27 +1250,29 @@ kernel from an NFS server.
.It Pa tapeimage/
. (tag stboot
. It Pa stboot
This file contains a boot sector for Motorola MVME boards. It must
be the first file written to a tape in order to make the tape bootable.
This file contains a boot sector for Motorola MVME boards.
It must be the first file written to a tape in order to make the tape bootable.
. tag)
. (tag bootst
. It Pa bootst
This file contains a bootstrap program which knows how to load the
.Nx
\*M
ramdisk image from tape. This must be the second file written to the tape.
ramdisk image from tape.
This must be the second file written to the tape.
. tag)
. (tag netbsd.RAMDISK.gz
. It Pa netbsd.RAMDISK.gz
This is the
.Nx
\*M
ramdisk image. It contains a
ramdisk image.
It contains a
.Li GENERIC
kernel and a built in RAMDISK
with just enough tools to partition a disk, dump the miniroot kernel
to it and make the disk bootable. This must be the third file written
to the tape.
to it and make the disk bootable.
This must be the third file written to the tape.
. tag)
.tag)
.\}
@ -1259,7 +1295,8 @@ into memory via the pc532
.tag)
.Pp
The upgrade process is supported by having a copy of a \*V kernel
available. This file is:
available.
This file is:
.(tag kern.tgz
.It Pa kern.tgz
Contains a kernel produced from the
@ -1293,16 +1330,18 @@ There is a collection of Sun2 kernels in the
.Pa \*M/binary/kernel
subdirectory of the
.Nx \*V
distribution. The one named
distribution.
The one named
.Pa netbsd.RAMDISK.gz
contain a root file system image and should only be used for the
initial installation. The others are included for convenience.
initial installation.
The others are included for convenience.
(Most people will want to use
.Pa netbsd-GENERIC.gz
or
.Pa netbsd-FOURMEG.gz
as appropriate.) Please note that these kernels are simply gzipped
and are not tar archives.
as appropriate.)
Please note that these kernels are simply gzipped and are not tar archives.
.\}
.
.if r_sun3 \{\
@ -1311,14 +1350,16 @@ There is a collection of Sun3 and Sun3X kernels in the
.Pa \*M/binary/kernels
subdirectory of the
.Nx \*V
distribution. The ones named
distribution.
The ones named
.Pa netbsd-ramdisk*.gz
contain a root file system image and should only be used for the
initial installation. The others are included for convenience.
initial installation.
The others are included for convenience.
(Most people will want to use
.Pa netbsd-generic.gz
or
.Pa netbsd-generic3x.gz
as appropriate.) Please note that these kernels are simply gzipped
and are not tar archives.
as appropriate.)
Please note that these kernels are simply gzipped and are not tar archives.
.\}

130
distrib/notes/common/netboot
View File

@ -1,6 +1,6 @@
.\" $NetBSD: netboot,v 1.9 2002/06/23 01:27:52 gmcgarry Exp $
.\" $NetBSD: netboot,v 1.10 2002/06/29 08:32:31 lukem Exp $
.\"
.\" Copyright (c) 1999-2001 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -36,18 +36,18 @@
Introduction
.Pp
To netboot a \*M, you must configure one or more servers to provide
information and files to your \*M (the
information and files to your \*M (the
.Sq client ).
If you are using
.Nx
(any architecture) on your netboot server(s), the information
provided here should be sufficient to configure everything. Additionally,
you may wish to look at the
.Xr diskless 8
provided here should be sufficient to configure everything.
Additionally, you may wish to look at the
.Xr diskless 8
manual page and the manual pages for each daemon you'll be configuring.
If the server(s) are another operating system, you should consult the
NetBSD Diskless HOW-TO, which will walk you through the steps necessary to
configure the netboot services on a variety of platforms.
configure the netboot services on a variety of platforms.
.Lk http://www.netbsd.org/Documentation/network/netboot/
.if !\n[next68k] \{\
.Pp
@ -75,19 +75,19 @@ Once the kernel is loaded, it starts executing.
.\}
.ie !\n[next68k] \{\
For RAM disk kernels, it mounts the RAM disk filesystem and begins
executing the installer from the RAM disk. For normal
(non-RAM disk) kernels, the
executing the installer from the RAM disk.
For normal (non-RAM disk) kernels, the
.\}
.el The
kernel tries to mount the NFS share that had the kernel and starts
executing
executing
.if !\n[next68k] the installation tools or
.Xr init 8 .
.ie \n[hp300] \{\
All supported \*M systems use HP's proprietary RMP (the
All supported \*M systems use HP's proprietary RMP (the
.Xr rbootd 8
daemon) for the first discovery stage and bootstrap download stages. The
bootstrap program uses DHCP for its discovery stage.
daemon) for the first discovery stage and bootstrap download stages.
The bootstrap program uses DHCP for its discovery stage.
.\}
.el .ie \n[macppc]:\n[next68k]:\n[walnut] \{\
All \*M systems use BOOTP for the discovery stage.
@ -130,15 +130,17 @@ NFS is used in both the kernel and filesystem stages to download the
kernel, and to access files on the file server.
.\} \" !\n[walnut]
.Pp
We will use
We will use
.Sq Li "CC:CC:CC:CC:CC:CC"
as the MAC address (ethernet hardware address) of your netboot client
machine. You should have determined this address in an earlier stage. In
this example, we will use
machine.
You should have determined this address in an earlier stage.
In this example, we will use
.Sq Li 192.168.1.10
as the IP address of your client and
.Sq Li client.test.net
as its name. We will assume you're providing all of your netboot services
as its name.
We will assume you're providing all of your netboot services
on one machine called
.Sq Li server.test.net
with the client's files exported from the directory
@ -166,7 +168,7 @@ directory of the distribution.
.No # Ic "chmod -R a+rX /usr/mdec/rbootd"
.disp)
.Pp
Create
Create
.Pa /etc/rbootd.conf
with the following line:
.(disp
@ -175,7 +177,7 @@ CC:CC:CC:CC:CC:CC SYS_UBOOT
.Pp
You will need to start the
.Ic rbootd .
If it's already running, you will need to
If it's already running, you will need to
restart it to force it to re-read its configuration file.
If the server is running
.Nx 1.5
@ -189,18 +191,18 @@ or later, you can achieve this with:
.\} \" ! \n[hp300]
.if \n[hp300]:\n[macppc]:\n[next68k]:\n[sparc]:\n[walnut] \{\
.ie !\n[hp300] \{\
.Xr dhcpd 8
in
.Xr dhcpd 8
in
.Xr bootpd 8
compatible mode
.Pp
.\}
.el \{\
.Xr dhcpd 8
.Xr dhcpd 8
.Pp
The bootstrap program uses DHCP to discover the location of the kernel.
.\}
Put the following lines in your
Put the following lines in your
.Pa /etc/dhcpd.conf
(see
.Xr dhcpd.conf 5
@ -217,9 +219,9 @@ allow bootp; # Allow bootp requests, thus the dhcp server
authoritative; # This is the authoritative DHCP server for this subnet
#
subnet 192.168.1.0 netmask 255.255.255.0 {
# Which network interface the server will
# listen on. The zeros indicate which
# range of addresses are allowed to connect.
# Which network interface the server will listen on.
# The zeros indicate which range of addresses are
# allowed to connect.
}
group {
# Set of parameters common to all clients
@ -251,17 +253,17 @@ group {
#
filename "netbsd.INSTALL.img"
.\}
.el .if !\n[sparc] \{\
.el .if !\n[sparc] \{\
#
# Name of the bootloader or kernel
# to download via tftp.
#
.\}
.ie \n[macppc] \{\
.ie \n[macppc] \{\
filename "ofwboot.xcf";
.\}
.el .if \n[next68k] \{\
.el .if \n[next68k] \{\
filename "boot";
.\} \" \n[next68k]
.\} \" !\n[hp300]
@ -269,7 +271,7 @@ group {
# The path on the NFS server.
#
option root-path "/export/client/root";
.if \n[next68k] \{\
.if \n[next68k] \{\
#
#next68k machines require non-RFC1048 BOOTP
@ -291,7 +293,7 @@ file exists.
.Pp
You will need to start the
.Ic dhcpd .
If it's already running, you will need to
If it's already running, you will need to
restart it to force it to re-read its configuration file.
If the server is running
.Nx 1.5
@ -325,7 +327,7 @@ file:
.Pp
You will need to start the
.Ic rarpd .
If it's already running, you will need to
If it's already running, you will need to
restart it to force it to re-read its configuration file.
If the server is running
.Nx 1.5
@ -341,11 +343,12 @@ or later, you can achieve this with:
.It
.Xr tftpd 8
.Pp
The default configuration of the TFTP server is to run in a
The default configuration of the TFTP server is to run in a
.Xr chroot 8
environment in the
.Pa /tftpboot
directory. Thus, the first order of business is to create this directory:
directory.
Thus, the first order of business is to create this directory:
.(disp
.No # Ic "mkdir -p /tftpboot"
.disp)
@ -357,18 +360,18 @@ and uncomment the line with the TFTP daemon:
tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot
.disp)
.Pp
Now, restart
Now, restart
.Xr inetd 8 .
If the server is running
.Nx 1.5
or later, you can achieve this with:
.Pp
.(disp
.No # Ic "/etc/rc.d/inetd restart"
.(disp
.No # Ic "/etc/rc.d/inetd restart"
.disp)
.Pp
.ie \n[walnut] Now, you need to copy the kernel for your \*M machine to
.el Now, you need to copy the bootloader for your \*M machine to
.ie \n[walnut] Now, you need to copy the kernel for your \*M machine to
.el Now, you need to copy the bootloader for your \*M machine to
.Pa /tftpboot .
.ie \n[macppc] \{\
Get
@ -383,9 +386,9 @@ directory of the distribution.
.el .ie \n[next68k] \{\
Get
.Pa base.tgz
from the
from the
.Pa binary/sets
directory of the distribution and extract
directory of the distribution and extract
.Pa boot
from it.
.(disp
@ -405,10 +408,12 @@ directory of the distribution.
.Pp
Now, you need to link
.Pa boot.net
to the filename that your \*M will look for. It will look for a filename
composed of the machine's IP address (in hexadecimal) followed by the machine's
architecture, separated by a period. For example, a sun4c machine which
has been assigned IP address 192.168.1.10, will make a TFTP request for
to the filename that your \*M will look for.
It will look for a filename composed of the machine's IP address
(in hexadecimal) followed by the machine's architecture,
separated by a period.
For example, a sun4c machine which has been assigned IP address
192.168.1.10, will make a TFTP request for
.Pa C0A8010A.SUN4C .
.Pp
You can use
@ -436,10 +441,11 @@ Just to be sure, let's make everything readable.
.No # Ic "chmod -R a+rX /tftpboot"
.disp)
.Pp
Sometimes, the
Sometimes, the
.Xr arp 8
table gets messed up, and the TFTP server can't communicate with the
client. In this case, it will write a log message (via
client.
In this case, it will write a log message (via
.Xr syslogd 8 )
to
.Pa /var/log/messages
@ -468,8 +474,8 @@ You can either boot a kernel, or the RAM disk-based installer
.Pa binary/kernel/netbsd.INSTALL.img.gz .
In the first case you'll also need an NFS-mounted userland.
.\}
Let's set up the NFS server. Create the
directory you are exporting for the netboot client:
Let's set up the NFS server.
Create the directory you are exporting for the netboot client:
.Pp
.(disp
.No # Ic "mkdir -p /export/client/root"
@ -486,15 +492,15 @@ to enable NFS sharing:
If your server is currently running an NFS server, you only need to
restart
.Xr mountd 8 .
Otherwise, you need to start
Otherwise, you need to start
.Xr rpcbind 8
and
and
.Xr nfsd 8 .
If the server is running
.Nx 1.5
or later, you can achieve this with:
.Pp
.(disp
.(disp
.No # Ic "/etc/rc.d/rpcbind start"
.No # Ic "/etc/rc.d/nfsd start"
.No # Ic "/etc/rc.d/mountd restart"
@ -513,14 +519,15 @@ in
your client should boot the kernel.
.\} \" !\n[walnut]
.ie \n[hp300] \{\
If you are netbooting the installer, you can use either
If you are netbooting the installer, you can use either
the traditional miniroot-based installer
.Pa installation/miniroot/miniroot.fs.gz
or the experimental RAM disk-based installer
.Pa binary/kernel/netbsd.RAMDISK.gz .
.Pp
To use the miniroot-based installer, mount the miniroot filesystem on your
netboot server. This procedure does
netboot server.
This procedure does
.Em not
work on any operating system other than
.Nx .
@ -555,7 +562,7 @@ If you are running your \*M diskless, simply use
.\}
.el .ie \n[macppc] \{\
If you are netbooting the installer, use
.Pa binary/kernel/netbsd.GENERIC_MD.gz
.Pa binary/kernel/netbsd.GENERIC_MD.gz
(this has the installation tools in a RAM disk).
Also, copy the distribution files to the client's root directory.
.Pp
@ -586,7 +593,7 @@ Use
.No # Ic "mv netbsd-GENERIC /export/client/root/netbsd"
.disp)
.Pp
If you are netbooting the installer, copy the distribution files to
If you are netbooting the installer, copy the distribution files to
the client's root directory and extract the tools from
.Pa installation/netboot/rootfs.tgz .
.Pp
@ -598,7 +605,7 @@ the client's root directory and extract the tools from
.\}
.el .if \n[walnut] \{\
If you are netbooting the installer, use
.Pa binary/kernel/netbsd.INSTALL.img.gz
.Pa binary/kernel/netbsd.INSTALL.img.gz
(this has the installation tools in a RAM disk).
Also, copy the distribution files to the client's root directory.
.Pp
@ -616,10 +623,11 @@ Client filesystem
.Pp
.ie !\n[next68k] \{\
You can skip this step if you do not plan to run your client
diskless after installation. Otherwise, you
diskless after installation.
Otherwise, you
.\}
.el You
need to extract and set up the client's installation of
need to extract and set up the client's installation of
.Nx .
The Diskless HOW-TO describes how to provide better security and save
space on the NFS server over the procedure listed here.
@ -662,7 +670,7 @@ hosts.
Set up the client's
.Xr fstab 5
.Pp
Create a file in
Create a file in
.Pa /export/client/root/etc/fstab
with the following lines:
.Pp
@ -708,7 +716,7 @@ Edit
.It
Setting up the server daemons
.Pp
.ie !\n[next68k] If you want
.ie !\n[next68k] If you want
.el You need
these services to start up every time you boot
your server, make sure the following lines are present in your

70
distrib/notes/common/postinstall
View File

@ -1,6 +1,6 @@
.\" $NetBSD: postinstall,v 1.34 2002/06/13 14:55:39 leo Exp $
.\" $NetBSD: postinstall,v 1.35 2002/06/29 08:32:31 lukem Exp $
.\"
.\" Copyright (c) 1999-2001 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -39,7 +39,7 @@ Configuring
.Pa /etc/rc.conf
.Pp
If you or the installation software haven't done any configuration of
.Pa /etc/rc.conf
.Pa /etc/rc.conf
.Ic ( sysinst
usually will),
the system will drop you into single user mode on first reboot with the
@ -49,12 +49,13 @@ message
.Pp
and with the root file system
.Pq Pa /
mounted read-write. When the system
asks you to choose a shell, simply press
mounted read-write.
When the system asks you to choose a shell, simply press
.Key RETURN
to get to a
to get to a
.Pa /bin/sh
prompt. If you are asked for a terminal type, respond with
prompt.
If you are asked for a terminal type, respond with
.ie r_hp300 \{\
.Ic hp300h
for a local console, or whatever is appropriate for your serial console.
@ -89,13 +90,15 @@ to work properly, depending on your keyboard:
At this point, you need to configure at least
one file in the
.Pa /etc
directory. You will need to mount your root filesystem read/write with:
directory.
You will need to mount your root filesystem read/write with:
.Dl # Ic "/sbin/mount -u -w /"
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
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.
@ -126,8 +129,8 @@ Do the following:
.Pp
If you have
.Pa /var
on a separate partition, you need to repeat
that step for it. After that, you can edit
on a separate partition, you need to repeat that step for it.
After that, you can edit
.Pa /etc/rc.conf
with
.Xr vi 1 .
@ -145,7 +148,7 @@ furthermore add an
.Ar ifconfig_int
for your
.Aq int
network interface,
network interface,
.ie r_macppc \{\
where your on-board interfaces may be one of
.Li mc0 , bm0 , de0 No or Li gm0 .
@ -205,23 +208,27 @@ Select the proper terminal devices
.Pp
You will have to edit the
.Pa /etc/ttys
file. If you don't have a Milan, you must disable the
file.
If you don't have a Milan, you must disable the
.Pa ttyEx
devices. For the Milan, you will have to disable the
devices.
For the Milan, you will have to disable the
.Pa ttyex
devices. This is easy, just change 'on' to 'off' on the corresponding lines.
devices.
This is easy, just change 'on' to 'off' on the corresponding lines.
.\}
.It
Logging in
.Pp
After reboot, you can log in as
.Li root
at the login prompt. Unless you've set a password in
at the login prompt.
Unless you've set a password in
.Ic sysinst ,
there
is no initial password. If you're using the machine in a
networked environment, you should create an account for yourself
(see below) and protect it and the
is no initial password.
If you're using the machine in a networked environment,
you should create an account for yourself (see below) and protect it and the
.Dq root
account with good passwords.
Unless you have connected an unusual terminal device as the console
@ -238,7 +245,8 @@ command to add accounts to your system,
.Em do not
edit
.Pa /etc/passwd
directly. See
directly.
See
.Xr useradd 8
for more information on how to add a new user to the system.
.if !\n[next68k] \{\
@ -249,7 +257,7 @@ If you have installed the X Window System, look at the files in
.Pa /usr/X11R6/lib/X11/doc
for information.
.if \n[hp300] \{\
Also, you may want to read through the
Also, you may want to read through the
.Nx*M
FAQ entry on X11.
.br
@ -257,7 +265,7 @@ FAQ entry on X11.
http://www.netbsd.org/Ports/faq.html#x11
.\}
.if \n[macppc] \{\
Also, you may want to read through the
Also, you may want to read through the
.Nx*M
X11R6 FAQ.
.br
@ -268,10 +276,12 @@ X11R6 FAQ.
.Pp
You will need to set up a configuration file, see
.Pa /usr/X11R6/lib/X11/XF86Config.eg
for an example. The
for an example.
The
.Xr xf86config 1
utility can interactively create a first version of such a configuration
file for you. See
file for you.
See
.Lk http://www.xfree86.org/
and the XFree86 manual page for more information.
.\}
@ -287,8 +297,8 @@ If you wish to install any of the software freely available for
systems
you are strongly advised to first check the
.Nx
package system. This automatically handles any changes necessary to
make the software run on
package system.
This automatically handles any changes necessary to make the software run on
.Nx ,
retrieval and installation of any other packages on which the software
may depend, and simplifies installation (and deinstallation), both
@ -305,7 +315,8 @@ Precompiled binaries can be found at
.Lk ftp://ftp.netbsd.org/pub/NetBSD/packages ,
usually in the
.Pa \*V/\*M/All
subdir. You can install them with the following commands:
subdir.
You can install them with the following commands:
.Pp
.Bd -unfilled
.Ic # PKG_PATH=ftp://ftp.netbsd.org/pub/NetBSD/packages/\*V/\*M/All
@ -319,7 +330,7 @@ subdir. You can install them with the following commands:
The above commands will install the tcsh shell,
the Apache web server and
the perl programming language as well as all the packages they
depend on.
depend on.
.It
Package sources for compiling packages on your own can be obtained by
retrieving the file
@ -342,7 +353,8 @@ Misc
.(bullet
Edit
.Pa /etc/mail/aliases
to forward root mail to the right place. Don't forget to run
to forward root mail to the right place.
Don't forget to run
.Xr newaliases 1
afterwards.
.It

432
distrib/notes/common/sysinst
View File

@ -1,6 +1,6 @@
.\" $NetBSD: sysinst,v 1.42 2002/06/28 15:26:38 skrll Exp $
.\" $NetBSD: sysinst,v 1.43 2002/06/29 08:32:31 lukem Exp $
.\"
.\" Copyright (c) 1999-2001 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -51,10 +51,11 @@ 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.
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.
.
@ -65,8 +66,8 @@ to use.
.Pp
Machines with
.Tn PCMCIA
slots may have problems during installation. With the improvements of
the
slots may have problems during installation.
With the improvements of the
.Tn PCMCIA
code in this release, this will not happen very frequently.
If you do not have
@ -76,14 +77,17 @@ on your machine
is only really used on laptop machines),
you can skip this section, and ignore the
.Dq Bq Tn PCMCIA
notes. If you do have
notes.
If you do have
.Tn PCMCIA
in your machine, you can safely ignore this section and the
.Dq Bq Tn PCMCIA
the first time, as you are likely to not have problems. Should troubles
the first time, as you are likely to not have problems.
Should troubles
occur during floppy boot, they may be
.Tn PCMCIA
specific. You should then re-read this section and try again,
specific.
You should then re-read this section and try again,
following the instructions in the
.Dq Bq Tn PCMCIA
notes.
@ -91,14 +95,14 @@ notes.
This section explains how to work around the installation problem.
.Pp
The kernel keeps careful track of what interrupts
and I/O ports are in use during autoconfiguration. It then allows
the
and I/O ports are in use during autoconfiguration.
It then allows the
.Tn PCMCIA
devices to pick unused interrupts and I/O ports.
Unfortunately, the
.Tn Li INSTALL
kernel may not detect all devices in your system. This may
be because the
kernel may not detect all devices in your system.
This may be because the
.Tn Li INSTALL
kernel only supports the minimum set of devices to install
.Nx
@ -109,13 +113,14 @@ does not have support for the device causing the conflict.
For example, suppose 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
kernel has no sound support.
The
.Tn PCMCIA
code might allocate your soundblaster's
.Tn IRQ No and I/O ports to
.Tn PCMCIA
devices, causing them not to work, or to lock up the system. This is
especially bad if one of the devices in question is your ethernet
card.
devices, causing them not to work, or to lock up the system.
This is especially bad if one of the devices in question is your ethernet card.
.Pp
As of
.Nx 1.5 ,
@ -123,9 +128,10 @@ the kernel attempts to probe for available interrupts that are
usable by the
.Tn PCIC
.Tn ( PCMCIA
interrupt controller). Assuming that this functions correctly, it
should alleviate interrupt conflicts; however, I/O port conflicts are
still possible.
interrupt controller).
Assuming that this functions correctly,
it should alleviate interrupt conflicts;
however, I/O port conflicts are still possible.
.Pp
This problem will impact some, but not all, users of
.Tn PCMCIA .
@ -135,7 +141,8 @@ notes that will appear in this document.
.if r_i386 \{\
.Pp
It can be difficult to distinguish an interrupt conflict from
an I/O space conflict. There are no hard-and-fast rules, but
an I/O space conflict.
There are no hard-and-fast rules, but
interrupt conflicts are more likely to lock up the machine,
and I/O space conflicts are more likely to result in misbehavior
(e.g. a network card that cannot send or receive packets).
@ -152,25 +159,28 @@ IRQ Val IRQ Val IRQ Val IRQ Val
3 0x0008 7 0x0080 11 0x0800 15 0x8000
.disp)
.Pp
For example, 0x0a00 allows both IRQ 9 and IRQ 11. By default,
the
For example, 0x0a00 allows both IRQ 9 and IRQ 11.
By default, the
.Tn Li INSTALL
kernel permits all IRQs other than IRQs 5 and 7, so the corresponding
mask is 0xff5f. The
mask is 0xff5f.
The
.Tn Li GENERIC
kernel, however, allows all IRQs. (The presumption here
is that IRQ 10 may be assigned to a device that the
kernel, however, allows all IRQs.
(The presumption here is that IRQ 10 may be assigned to a device that the
.Tn Li GENERIC
kernel
supports, but that the
.Tn Li INSTALL
does not.) Because of support for interrupt probing, it is no
does not.)
Because of support for interrupt probing, it is no
longer necessary to exclude IRQs 3 and 5 explicitly; if they are
in use, they should not be assigned to
.Tn PCMCIA .
.Pp
The kernel selects IO space by assigning cards IO space within a
predefined range. The range is specified as a base and size,
predefined range.
The range is specified as a base and size,
specified by the kernel global variables
.Va pcic_isa_alloc_iobase
and
@ -180,8 +190,8 @@ base of 0x400 and a size of 0xbff (a range of 0x400-0xfff).
For systems with 10-bit addressing, the kernel defaults to a
base of 0x300 and a size of 0xff (range of 0x300-0x3ff).
.Pp
Unfortunately, these ranges may conflict with some devices. In the
event of a conflict, try a base of 0x330 with a size of 0x0bf (range
Unfortunately, these ranges may conflict with some devices.
In the event of a conflict, try a base of 0x330 with a size of 0x0bf (range
of 0x330-0x3ff).
.Pp
In order to work around this at installation time, you may
@ -208,7 +218,8 @@ the kernel, you may have to consult the matching
.Pa .symbols
file in the
.Pa binary/kernel
directory in the installation tree. Find the pcic_ symbols used above,
directory in the installation tree.
Find the pcic_ symbols used above,
look at the hexadecimal value in the first column, and write, for
example (if
.Va pcic_isa_intr_alloc_mask
@ -258,24 +269,26 @@ 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
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 press
after the question.
If you wish to stop the installation, you may press
.Key CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch, by running the
process again from scratch, by running the
.Pa /sysinst
program from the command prompt, you do not need to reboot.
.It
.To 2 "Quick install"
.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
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
.(bullet
@ -291,7 +304,8 @@ Some form of bootable media, described above.
.\}
.el .ie r_atari \{\
A floppy disk containing a suitable boot.fs and a floppy with the
sysinst.fs image. See the "prepare" section about obtaining those.
sysinst.fs image.
See the "prepare" section about obtaining those.
.\} .el One 1.44 MB 3.5" floppy.
.\} \" !\n[pmax]:\n[sgimips]
.if r_i386 \{\
@ -336,8 +350,8 @@ 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
main memory in your system.
If you wish to install the X Window System as well, you will need at least
60 MB more.
.bullet)
.if \n[alpha]:\n[i386]:\n[news68k]:\n[newsmips] \{\
@ -385,8 +399,8 @@ system, you would type something like:
The Quick Installation
.(bullet
.ie \n[acorn26]:\n[atari]:\n[cats]:\n[macppc]:\n[pmax]:\n[sgimips]:\n[sparc]:\n[walnut] \{\
Boot the system as described above. You
should be at the
Boot the system as described above.
You should be at the
.Ic sysinst
main menu.
.\}
@ -445,14 +459,16 @@ immediately by choosing the
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 may be more convenient.
Go back to the main menu.
.It
Choose
.Me install .
.It
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.
to install.
When in doubt, refer to the rest of this document for details.
.if r_atari \{\
WARNING: If you want your disk to retain an AHDI compatible partitioning,
make sure to use the 'existing' disk layout.
@ -461,12 +477,15 @@ make sure to use the 'existing' disk layout.
After your disk has been prepared, choose
.if r_sgimips \{\
.Me Unmounted filesystem
as the medium. The CD-ROM device is usually cd0 and the partition 'a'
as the medium.
The CD-ROM device is usually cd0 and the partition
.Sq a
.Pq i.e. cd0a .
.\}
.el \{\
.Me CD-ROM
as the medium. The default values for the path and device should be ok.
as the medium.
The default values for the path and device should be ok.
.\}
.It
After all the files have been unpacked, go back to
@ -493,12 +512,13 @@ PROM environment settings for SystemPartition, OSLoadPartition, OSLoader
and OSLoadFilename and then boot the hard drive.
.\}
.Nx
will now boot. If you haven't already done so in
will now boot.
If you haven't already done so in
.Ic sysinst ,
you should log in as
.Li root ,
and set a password for that account. You are also
advised to edit the file
and set a password for that account.
You are also advised to edit the file
.Pa /etc/rc.conf
to match your system needs.
.It
@ -533,16 +553,16 @@ devices, so that they won't be found by
Boot the system as described in the previous section.
.Pp
You may want to read the
boot messages, to notice your disk's name and capacity. Its name
will be something like
boot messages, to notice your disk's name and capacity.
Its name will be something like
.Li sd0
.if \n[acorn26]:\n[cats]:\n[macppc]:\n[walnut] \{\
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
printed on a line that begins with its name.
As mentioned above, you may need your disk's geometry when creating
.Nx 's
partitions.
You will also need to know the name, to tell
@ -571,42 +591,44 @@ the second, etc.
Boot the system as described in the "Booting the installer" section above.
.\}
.el \{\
Boot your machine. The boot loader will
start, and will print a countdown and begin booting.
Boot your machine.
The boot loader will start, and will print a countdown and begin booting.
.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
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,
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.
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
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 \n[atari]:\n[i386] \{\
You may want to read the
boot messages, to notice your disk's name and geometry. Its name
will be something like
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
printed on a line that begins with its name.
As mentioned above, you may need your disk's geometry when creating
.Nx 's
partitions.
You will also need to know the name, to tell
@ -660,14 +682,15 @@ from floppy in the first part of the install.
.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
it is installed, you should first go to the
.Me Utility menu ,
and select the
.Me Configure network
.Me Configure network
option.
If you only want to temporarily
use networking during the installation, you can specify these
parameters later. If you are not using the Domain Name System (DNS),
parameters later.
If you are not using the Domain Name System (DNS),
you can give an empty response in reply to answers relating to
this.
.if r_macppc \{\
@ -683,17 +706,18 @@ onto a dedicated drive.
.Pp
Go to the
.Me "Utility Menu" No Ns ,
and select the
and select the
.Me "Run /bin/sh"
option which will give you a shell prompt. From this shell prompt, you
will do some of the steps that the normal install procedure
runs automatically. Unfortunately, at the moment, our install tools
aren't smart enough to deal with drives shared with
option which will give you a shell prompt.
From this shell prompt, you will do some of the steps that the normal
install procedure runs automatically.
Unfortunately, at the moment, our install tools
aren't smart enough to deal with drives shared with
.Tn MacOS
and will overwrite important information describing your partitions.
.Pp
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
to work properly, depending on your keyboard:
.Dl # Ic "stty erase '^h'"
.Dl # Ic "stty erase '^?'"
.Pp
@ -702,10 +726,10 @@ Type the following command (replacing
with the name of your destination hard drive):
.Dl # Ic "disklabel wd0"
.Pp
This will print out the partition info that was generated by Drive
Setup. Note that, as discussed above in the
This will print out the partition info that was generated by Drive Setup.
Note that, as discussed above in the
.Sx Partitioning your hard drive for NetBSD
section, your
section, your
.Em "A/UX Root"
typically is the first partition
.No ( Ns Em a No Ns )
@ -733,7 +757,7 @@ disklabel: boot block size 0
disklabel: super block size 0
.disp)
.Pp
Now, you need to create filesystems on the partitions that
Now, you need to create filesystems on the partitions that
.Nx
will be using.
.Pp
@ -765,8 +789,8 @@ super-block backups (for fsck -b #) at:
newfs: ioctl (WDINFO): Invalid argument
newfs: /dev/sd1a: can't rewrite disk label
.disp)
You can ignore the
.Pa Sq "not a character-special device" ,
You can ignore the
.Pa Sq "not a character-special device" ,
.Pa Sq "sector(s) in last cylinder unallocated" ,
.Pa Sq "ioctl (WDINFO): Invalid argument" ,
and
@ -776,12 +800,12 @@ warnings.
Now you need to mount your destination root partition:
.Dl # Ic "mount /dev/wd0a /mnt"
.Pp
Make an
Make an
.Pa fstab
file for your new system (right now, you only really need to include
.Pa / No ,
.Pa /usr No ,
and
.Pa /usr No ,
and
.Pa swap No ),
for example:
.Dl # Ic "mkdir /mnt/etc"
@ -800,7 +824,7 @@ Great, now create the mountpoints for the filesystems you listed in the
.Pa fstab No Ns :
.Dl # Ic "mkdir /mnt/usr"
.Pp
Clean up and return to
Clean up and return to
.Ic sysinst :
.Dl # Ic "cd /;umount /mnt"
.Dl # Ic exit
@ -833,9 +857,9 @@ 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
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
.ie r_pmax \{\
.Li rz0
or
@ -853,7 +877,8 @@ or
.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,
of your disk.
It will present you with the values it found,
if any, and will give you a chance to change them.
.\}
.Pp
@ -880,17 +905,18 @@ or
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.
that it does, reply affirmatively.
Otherwise, the install program will automatically reserve space for
bad144 tables.
.\}
.if r_macppc \{\
If
.Ic sysinst
reports
If
.Ic sysinst
reports
.Dl "I can not find any hard disk for use by NetBSD"
or the drive you wish to install onto is missing, then you should look at
or the drive you wish to install onto is missing, then you should look at
the FAQ entry
.Lk http://www.netbsd.org/Ports/macppc/faq.html#nodisk
.Lk http://www.netbsd.org/Ports/macppc/faq.html#nodisk
.\}
.\}
.It
@ -910,17 +936,22 @@ on a dedicated drive, just answer 'no' and skip to the next section.
.Pp
If you answer 'yes', the
.Ic ahdilabel
program is started. You can now change the AHDI partition ID's on your root
disk. Because NetBSD imposes a special ordering in disk partitions it uses
for / (root) and swap. And because it wants to guard you against an unwanted
program is started.
You can now change the AHDI partition ID's on your root disk.
Because NetBSD imposes a special ordering in disk partitions it uses
for / (root) and swap.
Also, because it wants to guard you against an unwanted
demolition of partitions used by other systems, you have to tell it what
partitions it is allowed to use. You have to mark the partition you want
to use as swap SWP or (depricated!) NBS and the other partitions as NBD.
partitions it is allowed to use.
You have to mark the partition you want to use as swap SWP or
(depricated!) NBS and the other partitions as NBD.
Note that all the changes you make to the ID's are reversable as long as
you remember the original value. As of NetBSD 1.5 ahdilabel is capable of
creating or changing an AHDI compatible partioning on the disk! In the
partition-ID editor, the partitions are shown in the order that AHDI
created them. When you leave this editor and continue with
you remember the original value.
As of NetBSD 1.5, ahdilabel is capable of creating or changing an
AHDI compatible partioning on the disk!
In the partition-ID editor, the partitions are shown in the order that AHDI
created them.
When you leave this editor and continue with
.Ic sysinst,
your changes to the ID's do have consequences to the partition order!
They will show up as follows:
@ -936,7 +967,7 @@ the rest of the partitions in AHDI order
.\} \" r_atari
.if r_macppc \{\
.Pp
You can skip a few steps, down to
You can skip a few steps, down to
.Em Sq "Getting the distribution sets" ,
if you are installing onto a drive that will be used with
.Tn MacOS
@ -949,8 +980,8 @@ from the main menu).
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
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
@ -971,11 +1002,12 @@ 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
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
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!
@ -986,8 +1018,8 @@ Depending on the BIOS capabilities of your machine and the
parameters of the
.Nx
partition you have specified, you
may also be asked if you want to install newer bootcode in
your MBR. If you have multiple operating systems on the
may also be asked if you want to install newer bootcode in your MBR.
If you have multiple operating systems on the
disk that you are installing on, you will also be given
the option to install a bootselector, that will allow you
to pick the operating system to start up when your computer
@ -1008,9 +1040,10 @@ The partition table of the
part of a disk is called a
.Em disklabel .
.if r_macppc \{\
In actuality,
In actuality,
.Nx*M
uses an Apple Partition Map. The installer creates something like a real
uses an Apple Partition Map.
The installer creates something like a real
Apple Partition Map, but it is not compatible with
.Tn MacOS ,
which is one of the reasons why you cannot use this installer to partition
@ -1020,7 +1053,7 @@ a disk that can be used with
.\}
.if r_sparc \{\
.Nx
disklabels on \*M are compatible with the boot ROMs, and with
disklabels on \*M are compatible with the boot ROMs, and with
.Tn SunOS
and
.Tn Solaris .
@ -1031,12 +1064,12 @@ part of the disk that you can pick from:
.Ic Standard, Standard with X, Custom
and
.Ic Use Existing .
The first two use a set of default
values (that you can change) suitable for a normal
installation, possibly including X. With the
The first two use a set of default values (that you can change)
suitable for a normal installation, possibly including X.
With the
.Ic Custom
option you can specify everything yourself. The last option uses
the partition info already present on the disk.
option you can specify everything yourself.
The last option uses the partition info already present on the disk.
.Pp
.if r_atari \{\
If you want to use
@ -1049,8 +1082,8 @@ 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
block and fragment size, and the mount point.
The type that
.Nx
uses for normal file storage is called
.Sy 4.2BSD .
@ -1117,13 +1150,13 @@ but this is historical practice and not a fixed value.
.tag)
.
.Pp
You will then be asked to name your disk's disklabel. The
default response is
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.
is a single word and contains no special characters.
You don't need to remember this name.
.bullet)
.Pp
.It
@ -1134,8 +1167,8 @@ need to remember this name.
.if r_atari \{\
Apart from the changes you made with
.Ic ahdilabel
nothing has been modified on your disk yet. If you confirm that you want to
install
nothing has been modified on your disk yet.
If you confirm that you want to install
.Nx ,
the partitions now assigned to
.Nx
@ -1153,15 +1186,15 @@ If you are sure you want to proceed, enter
at the prompt.
.Pp
The install program will now label your disk and make the file
systems you specified. The file systems will be initialized to
contain
systems you specified.
The file systems will be initialized to contain
.Nx
bootstrapping binaries and configuration files.
You will see messages on your screen from the various
.Nx
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.
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 \{\
@ -1170,13 +1203,14 @@ after pressing the return key.
In previous versions of
.Nx ,
the kernel from the
install floppy was copied onto the hard drive in a special
step. In the current install system, the kernel on the floppy is
unsuited to being copied onto the hard drive. Instead, a new set,
install floppy was copied onto the hard drive in a special step.
In the current 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.
be unloaded onto the drive.
So, you can not boot from your hard drive yet at this point.
.Note)
.\}
.if r_macppc \{\
@ -1184,7 +1218,8 @@ hard drive yet at this point.
.(Note
The bootstrapping code installed in this step will
.Em not
boot a machine with Open Firmware 3. You will still need to have
boot a machine with Open Firmware 3.
You will still need to have
.Pa ofwboot.xcf
on an HFS or HFS+ partition.
.Note)
@ -1201,7 +1236,8 @@ set file)
on to your hard disk, for example by mounting the
hard disk first, copying the
.Pa kern-GENERIC.tgz
file from floppy and unpacking it. Example:
file from floppy and unpacking it.
Example:
.Pp
.Dl # Ic "mount /dev/wd0a /mnt"
.Dl # Ic "cd /mnt"
@ -1214,19 +1250,20 @@ file from floppy and unpacking it. Example:
.Pp
Then halt the machine using the
.Ic halt
command. Power
the machine down, and re-insert all the
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
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 file system
checks that it will do to finish, and then proceed
menu.
Choose the option to re-install sets.
Wait for the file system checks that it will do to finish, and then proceed
as described below.
.pcmcia)
.\}
@ -1235,19 +1272,19 @@ 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
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.
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
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 labeled
.Sq Extracting the distribution sets .
.It
@ -1259,8 +1296,8 @@ 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 address, hostname, etc. If you
do not have name service set up for the machine that you
to provide some data, like IP address, hostname, etc.
If you do not have name service set up for the machine that you
are installing on, you can just press
.Key RETURN
in answer to these questions, and DNS will not be used.
@ -1286,17 +1323,17 @@ 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 address, hostname, etc. If you
do not have name service set up for the machine that you
to provide some data, like IP address, hostname, etc.
If you do not have name service set up for the machine that you
are installing on, you can just press
.Key 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.
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 address
@ -1309,7 +1346,8 @@ instead of a hostname for the NFS server.
The bootable CD-ROM distribution for
.Nx*M
is not ISO-9660 formatted.
This function cannot be used for installation. Use the
This function cannot be used for installation.
Use the
"Installation from an unmounted file system" selection.
.\}
.el \{\
@ -1330,12 +1368,13 @@ extraction of the sets.
.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
files.
The floppies are expected to be in
.Tn 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.
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
.To 2 "Installation from an unmounted file system"
@ -1358,7 +1397,7 @@ CD-ROM player with partition letter 'a'
.Pq usually cd0a .
.\}
.if r_macppc \{\
Remember,
Remember,
.Nx*M
doesn't grok HFS or HFS+ partitions
.\}
@ -1367,7 +1406,8 @@ doesn't grok HFS or HFS+ partitions
.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
yourself.
The sets should be located in a directory on a
file system that is already accessible.
.Ic sysinst
will ask you
@ -1381,10 +1421,13 @@ After the install sets containing the
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 Sy kern, base No and Sy etc
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 Sy kern, base
and
.Sy etc
they will not be shown in this selection menu.
.Pp
Before extraction begins, you can elect to watch the files being
@ -1393,31 +1436,32 @@ This can slow down the installation process considerably, especially
on machines with slow graphics consoles or serial consoles.
.Pp
.ie r_macppc \{\
If you are installing using the
If you are installing using the
.Me "Re-install sets or install additional sets"
option, then you will need to create the device nodes in
.Pa /dev ,
otherwise,
otherwise,
.\}
.el 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.
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.
The next menu will allow you to select the time zone that you're in,
to make sure your clock has the right offset from UTC.
Finally you can set a password for the "root" account, to prevent
the machine coming up without access restrictions.
to make sure your clock has the right offset from UTC.
Finally you can set a password for the "root" account, to prevent
the machine coming up without access restrictions.
.if r_macppc \{\
.It
.To 2 "Making the device nodes"
.Em Making the device nodes
.Pp
If you are installing using the
If you are installing using the
.Me "Re-install sets or install additional sets"
option, then you will need to create the device nodes in
.Pa /dev
now. Otherwise, skip this step.
.Pa /dev
now.
Otherwise, skip this step.
.Pp
Go to the main installation menu, and select
.Me "Utility menu"
@ -1425,7 +1469,7 @@ and then select the
.Me "Run /bin/sh"
option, which will give you a shell prompt.
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
to work properly, depending on your keyboard:
.Dl # Ic "stty erase '^h'"
.Dl # Ic "stty erase '^?'"
.Pp
@ -1446,7 +1490,7 @@ Now you need to mount your destination root partition:
Congratulations, you have successfully installed
.Nx \*V .
.if !r_macppc \{\
You can now reboot the machine, and boot
You can now reboot the machine, and boot
.Nx
from harddisk.
.\} \" !r_macppc

34
distrib/notes/common/upgrade
View File

@ -1,6 +1,6 @@
.\" $NetBSD: upgrade,v 1.14 2002/06/20 10:44:07 leo Exp $
.\" $NetBSD: upgrade,v 1.15 2002/06/29 08:32:32 lukem Exp $
.\"
.\" Copyright (c) 1999-2001 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -76,8 +76,9 @@ You must also have at least the
and
.Sy 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.
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
@ -89,8 +90,8 @@ partitions, you should have enough space.
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 ,
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
@ -100,8 +101,8 @@ process.
Since installation of the bootloader will prevent
.Tn MacOS
from using the disk and will prevent Open Firmware 3 machines from
booting, there is an option to bypass this step. Make sure you know
whether or not to install the bootloader.
booting, there is an option to bypass this step.
Make sure you know whether or not to install the bootloader.
.\}
.Pp
The upgrade procedure using the
@ -118,14 +119,15 @@ file is copied into the new configuration.
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.
for how to do this.
Also, some sanity checks are done, i.e.
file systems 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.
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 .
@ -139,12 +141,14 @@ and run the command:
.Dl # Ic "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
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
systems have changed names.
To find out what the new options are,
it's suggested that you read the manual page
for the file system's mount commands, for example
.Xr mount_nfs 8
for NFS.

68
distrib/notes/common/xfer
View File

@ -1,6 +1,6 @@
.\" $NetBSD: xfer,v 1.28 2002/06/28 15:26:39 skrll Exp $
.\" $NetBSD: xfer,v 1.29 2002/06/29 08:32:32 lukem Exp $
.\"
.\" Copyright (c) 1999-2001 The NetBSD Foundation, Inc.
.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -65,8 +65,9 @@ floppy images.
For older machines with little RAM, use
.Pa boot-tiny.fs .
This image is tailored towards old, small-memory systems, and thus does
not contain any PCI or SCSI support. It should work on systems with
4M of RAM. Note that this means 4M available to NetBSD; systems that
not contain any PCI or SCSI support.
It should work on systems with 4M of RAM.
Note that this means 4M available to NetBSD; systems that
are said to have 4M may have 640k of base memory and 3072k of extended
memory, which currently will not work, as this is a total of 3712k.
.Pp
@ -84,8 +85,9 @@ and
.
.Pp
For the 2-floppy sets (and the CD boot image), utilities to repair
a badly crashed systems are included. The -small and -tiny images
have separate rescue floppy images because of lack of space.
a badly crashed systems are included.
The -small and -tiny images have separate rescue floppy images because
of lack of space.
.Pp
If you are using a
.Ul
@ -122,7 +124,8 @@ is also available that runs under
You should wait to decide where to put the
.Nx
distribution sets until you have figured out how you are going to boot
your system. Refer back to this section after you have done so.
your system.
Refer back to this section after you have done so.
.Pp
.\}
.if r_macppc \{\
@ -132,9 +135,11 @@ Some
.Ic ftp
clients default to downloading files in
.Sq ASCII
mode. This will render the
mode.
This will render the
.Nx
files useless. Make sure to set your ftp program to download in
files useless.
Make sure to set your ftp program to download in
.Sq binary
mode.
.Note)
@ -181,7 +186,7 @@ utility, provided in the
directory of the
.Nx
distribution.
It will write a file system image (.fs file) to a floppy disk.
It will write a file system image (.fs file) to a floppy disk.
A
.Ic rawrite32
is also available that runs under
@ -261,7 +266,7 @@ utility, provided in the
directory of the
.Nx
distribution.
It will write a file system image (.fs file) to a floppy disk.
It will write a file system image (.fs file) to a floppy disk.
A
.Ic rawrite32
is also available that runs under
@ -279,8 +284,8 @@ even after
.Nx*M
has been installed.
.Pp
SCSI devices on NWS-3xxx and NWS-5000 machines are supported. But they
also can run
SCSI devices on NWS-3xxx and NWS-5000 machines are supported.
But they also can run
.Nx*M
diskless.
No file transfer is needed, and all you have to do is to prepare files on
@ -366,7 +371,8 @@ When you chose the first method, you have to put the installation kernel
.Pa netbsd
and the
.Pa loadbsd.x
utility to a disk accessible from Human68k. These files can be found in
utility to a disk accessible from Human68k.
These files can be found in
.Pa installation/misc
directory of the
.Nx
@ -395,7 +401,8 @@ system to write the floppy image to
disks, you should use the
.Pa dd
command to copy the file system images (.fs files) directly to the raw
floppy disks. It is suggested that you read the
floppy disks.
It is suggested that you read the
.Xr dd 1
manual page or
ask your system administrator to determine the correct set of
@ -411,25 +418,27 @@ utility, provided in the
.Pa installation/misc
directory of the
.Nx
distribution. It will write the file system
images (.fs files) to disks.
distribution.
It will write the file system images (.fs files) to disks.
.Pp
To use the boot floppy, insert the floppy to your floppy drive 0,
and reboot your computer with OPT.1 key pressed.
.Pp
If you have less than 5MB of memory, you have to use the
`floppy-root' installation system instead of the above
`ramdisk-root' installation system. `Floppy-root' installation
system is composed of two floppies, `kern' and `inst'. They are
made from the floppy images
.Pa kern.fs
`ramdisk-root' installation system.
`Floppy-root' installation
system is composed of two floppies, `kern' and `inst'.
They are made from the floppy images
.Pa kern.fs
and
.Pa inst.fs
respectively, both of which are found in
.Pa installation/floppy
directory of the
.Nx
distribution. See above how to write the images to floppies.
distribution.
See above how to write the images to floppies.
.Pp
To start the `floppy-root' installation system, insert the `kern' floppy
to your floppy drive 0, and reboot your computer with OPT.1 key pressed.
@ -438,11 +447,11 @@ replace the `kern' floppy with `inst' floppy and press return key.
.Pp
Once booted, the `floppy-root' installation system is identical with
the `ramdisk-root' installation system, except that the former constantly
accesses the floppy disk. Floppy disks are relatively unreliable
media and cause some warning messages to report access errors, most of
which are corrected and can be ignored. With the latter installation
system the floppy disk is not used once the system has booted off and can
be removed from the drive.
accesses the floppy disk.
Floppy disks are relatively unreliable media and cause some warning messages
to report access errors, most of which are corrected and can be ignored.
With the latter installation system the floppy disk is not used once the
system has booted off and can be removed from the drive.
.Pp
.\} \" r_x68k
.
@ -731,8 +740,9 @@ the tape devices with which
.Nx*M
is believed to work is the
.Tn DEC
TK-50. This is a very slow device. Installation via disk or network is
recommended if at all possible.
TK-50.
This is a very slow device.
Installation via disk or network is recommended if at all possible.
.Note)
.\} \" \n[pmax]:\n[vax]
.Pp