more cleanups

- use .Ic, .Pa, .Key, .Ul, .Tn, .Sq, .Dq as appropriate
- use .Dl instead of .(disp when formatting changes are required (the latter
  doesn't cope too well when font change macros are used)
- wrap .Dl blocks with .Pp
- consistently use `file system' instead of `filesystem'
- migrate macppc to common/xfer
This commit is contained in:
lukem 2000-10-29 12:32:23 +00:00
parent 00f86cf2f4
commit 26f3b13e17
4 changed files with 350 additions and 249 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: postinstall,v 1.13 2000/10/11 12:59:22 simonb Exp $
.\" $NetBSD: postinstall,v 1.14 2000/10/29 12:32:23 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -42,10 +42,15 @@ If you or the installation software 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
.Pp
.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 press return to get to a
prompt. If you are asked for a terminal type, respond with
.Pp
and with the root file system
.Pq Pa /
mounted read-write. When the system
asks you to choose a shell, simply press
.Key RETURN
to get to a prompt. If you are asked for a terminal type, respond with
.ie r_pmax \{\
the correct terminal type as discussed in the
.Sx Once you've booted the diskimage
@ -55,9 +60,12 @@ section.
.Ic vt220
(or whatever is appropriate for your terminal type)
.\}
and press return. At this point, you need to configure at least
and press
.Key RETURN
. At this point, you need to configure at least
one file in the
.Pa /etc No directory. Change to the
.Pa /etc
directory. Change to the
.Pa /etc
directory and take a look at the
.Pa /etc/rc.conf
@ -71,18 +79,21 @@ More complete documentation can be found in
.Xr rc.conf 5 .
.Pp
If your
.Pa /usr No directory is on a separate partition
and you do not know how to use 'ed', you will have to mount your
.Pa /usr
partition to gain access to 'ex' or 'vi'. Do the following:
.ie r_pmax \{\
.D1 Ic "mount /usr
.D1 Ic "export TERM=termtype
.\}
.el \{\
.D1 Ic "mount /usr
.D1 Ic "export TERM=vt220
.\}
directory is on a separate partition and you do not know how to use
.Ic ed ,
you will have to mount your
.Pa /usr
partition to gain access to
.Ic ex
or
.Ic vi .
Do the following:
.Pp
.Dl # Ic "mount /usr"
.ie r_pmax .Dl # Ic "export TERM=termtype"
.el .Dl # Ic "export TERM=vt220"
.Pp
If you have
.Pa /var
on a separate partition, you need to repeat
@ -105,12 +116,18 @@ furthermore add an
for your interface
.Aq int ,
along the lines of
.Pp
.ie r_pmax .Dl ifconfig_le0="inet 123.45.67.89 netmask 255.255.255.0"
.el .Dl ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0"
.el .Dl ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0"
.Pp
or, if you have
.Ar myname.my.dom No in Pa /etc/hosts :
.Ar myname.my.dom
in
.Pa /etc/hosts :
.Pp
.ie r_pmax .Dl ifconfig_le0="inet myname.my.dom netmask 255.255.255.0"
.el .Dl ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
.el .Dl ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
.Pp
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
@ -136,10 +153,13 @@ After reboot, you can log in as
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.
(see below) and protect it and the
.Dq root
account with good passwords.
Unless you have connected an unusual terminal device as the console
you can just press RETURN when it prompts for
you can just press
.Key RETURN
when it prompts for
.Li Terminal type? [...]
.
.It
@ -148,7 +168,9 @@ Adding accounts
Use the
.Xr useradd 8
command to add accounts to your system,
.Em do not No edit Pa /etc/passwd
.Em do not
edit
.Pa /etc/passwd
directly. See
.Xr useradd 8
for more information on the process of how to add a new user to the system.
@ -173,7 +195,9 @@ to your path in your shell's dot file so that you have access to the X binaries.
.It
Installing third party packages
.Pp
If you wish to install any of the software freely available for unix systems
If you wish to install any of the software freely available for
.Ul
systems
you are strongly advised to first check the
.Nx
package system. This automatically handles any changes necessary to
@ -198,7 +222,9 @@ retrieving the file
They are typically extracted into
.Pa /usr/pkgsrc
(though other locations work fine), as with the command:
.D1 Ic "mkdir /usr/pkgsrc; tar -C /usr/pkgsrc -zxpf pkgsrc.tar.gz"
.Pp
.Dl # Ic "mkdir /usr/pkgsrc; tar -C /usr/pkgsrc -zxpf pkgsrc.tar.gz"
.Pp
After extracting, then see the
.Pa README
file in the extraction directory (e.g.
@ -230,7 +256,9 @@ to run any local daemons you use.
Many of the
.Pa /etc
files are documented in section 5 of the manual; so just invoking
.D1 Ic man Ar filename
.Pp
.Dl # Ic man 5 Ar filename
.Pp
is likely to give you more information on these files.
.bullet)
.enum)

View File

@ -1,4 +1,4 @@
.\" $NetBSD: sysinst,v 1.11 2000/10/11 11:46:02 tsutsui Exp $
.\" $NetBSD: sysinst,v 1.12 2000/10/29 12:32:23 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -183,28 +183,25 @@ in order to enter
(the in-kernel debugger), and then use the
.Ic write
command to alter the variable values:
.(disp
db> write pcic_isa_intr_alloc_mask 0x0a00
pcic_isa_intr_alloc_mask 0xff5f = 0xa00
db> write pcic_isa_alloc_iobase 0x330
pcic_isa_alloc_iobase 0x400 = 0x330
db> write pcic_isa_alloc_iosize 0x0bf
pcic_isa_alloc_iosize 0xbff = 0xbf
db> continue
.disp)
.Pp
.Dl db> Ic "write pcic_isa_intr_alloc_mask 0x0a00"
.Dl pcic_isa_intr_alloc_mask 0xff5f = 0xa00
.Dl db> Ic "write pcic_isa_alloc_iobase 0x330"
.Dl pcic_isa_alloc_iobase 0x400 = 0x330
.Dl db> Ic "write pcic_isa_alloc_iosize 0x0bf"
.Dl pcic_isa_alloc_iosize 0xbff = 0xbf
.Dl db> Ic "continue"
.Pp
After installation, this value can be permanently written to the kernel image
directly with:
.Pp
.(disp
# cp /netbsd /netbsd.bak
# gdb --write /netbsd
(gdb) set pcic_isa_intr_alloc_mask=0x0a00
(gdb) set pcic_isa_alloc_iobase=0x330
(gdb) set pcic_isa_alloc_iosize=0x0bf
(gdb) quit
#
.disp)
.Dl # Ic "cp /netbsd /netbsd.bak"
.Dl # Ic "gdb --write /netbsd"
.Dl (gdb) Ic "set pcic_isa_intr_alloc_mask=0x0a00"
.Dl (gdb) Ic "set pcic_isa_alloc_iobase=0x330"
.Dl (gdb) Ic "set pcic_isa_alloc_iosize=0x0bf"
.Dl (gdb) Ic "quit"
.Dl #
.Pp
or you could specify these value when configuring your kernel, e.g.:
.(disp
@ -239,7 +236,8 @@ 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
Control-C at any time, but if you do, you'll have to begin the installation
.Key CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch.
.It
.Em Quick install
@ -295,25 +293,42 @@ the X window system as well, you will need at least
.It
Creating the boot floppies.
You can create the floppies needed for installation
under DOS or Windows. Supposing your 1.44 MB floppy
under
.Tn MS-DOS
or
.Tn Windows .
Supposing your 1.44 MB 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\ei386\einstallation\emisc
.D1 Ic "\&rawrite
following from an
.Tn MS-DOS
command prompt:
.Pp
.Dl Ic "e:"
.Dl Ic "cd \eNetBSD-\*V\ei386\einstallation\emisc"
.Dl Ic "rawrite"
.Pp
When asked for a source filename, answer
.if r_i386 .D1 Ic \&..\efloppy\eboot1.fs for the first diskette and
.if r_i386 .D1 Ic \&..\efloppy\eboot2.fs for the second diskette
.if r_alpha .D1 Em \&(...alpha installation root) Ns Ic \efloppy\edisk1of2
.if r_news68k .D1 Ic \eNetBSD-\*V\e\*M\einstallation\efloppy\eboot.fs
.Pp
.if r_i386 \{\
.Dl Pa \&..\efloppy\eboot1.fs
for the first diskette and
.Dl Pa \&..\efloppy\eboot2.fs
for the second diskette.
.\}
.if r_alpha .Dl Em \&(...alpha installation root) Ns Pa \efloppy\edisk1of2
.if r_news68k .Dl Pa \eNetBSD-\*V\e\*M\einstallation\efloppy\eboot.fs
.Pp
When asked for a destination drive answer
.D1 Ic a
.Sq Ic a .
.It
To create a bootfloppy under
.Nx
or other UNIX-like system, you
would type something like:
.D1 Ic "dd if=.../boot1.fs bs=18k of=/dev/rfd0a
or other
.Ul
system, you would type something like:
.Pp
.Dl # Ic "dd if=.../boot1.fs bs=18k of=/dev/rfd0a"
.Pp
.\} \" \n[alpha]:\n[i386]:\[news68k]
.It
The Quick Installation
@ -332,11 +347,19 @@ boot floppy you just created.
.ie r_i386 Restart
.el Boot
the computer.
.if r_alpha Type
.if r_alpha .Dl \&\*>\*>\*> Ic "B DVA0
.if r_alpha \{\
Type
.Pp
.Dl \&\*>\*>\*> Ic "B DVA0"
.Pp
.\}
.if r_i386 When prompted, insert the second boot floppy.
.if r_news68k Type
.if r_news68k .Dl \&NEWS\*> Ic "bo fh
.if r_news68k \{\
Type
.Pp
.Dl \&NEWS\*> Ic "bo fh"
.Pp
.\}
The main menu will be displayed.
.\} \" ! r_pmax
.It
@ -369,19 +392,19 @@ 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.
.Pa /etc/rc.conf
to match your system needs.
.It
Your installation is now complete.
.It
For configuring the X window system, if installed, see the files in
.Dl /usr/X11R6/lib/X11/doc .
.Pa /usr/X11R6/lib/X11/doc .
Further information can be found on
.Lk http://www.xfree86.org/
.bullet)
.bullet)
.It
.Em Booting
.Nx
.Em Booting NetBSD
.
.
.ie r_pmax \{\
@ -461,7 +484,9 @@ Earlier version of
the
.Nx
install floppies mounted the floppy as the system's
root partition, but the new installation floppies use a
root partition
.Pq Pa / ,
but the new installation floppies use a
ramdisk file system and are no longer dependent on the floppy
once it has booted.
.\}
@ -527,16 +552,16 @@ if any, and will give you a chance to change them.
.\}
.Pp
Next, depending on whether you are using a
.Li Pf wd Em x
.Li wd Ns Ar X
or
.Li Pf sd Em x
.Li sd Ns Ar X
disk,
you will either be asked for the type of disk
.Pq Li Pf wd Em x
.Pq Li wd Ns Ar 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 .
.Pq Li sd Ns Ar X .
The types of disk are be
.Tn IDE, ST-506
or
@ -552,7 +577,7 @@ that it does, reply affirmatively. Otherwise, the install
program will automatically reserve space for bad144 tables.
.\}
.It
.Em Partitioning the disk.
.Em Partitioning the disk
.(bullet
Which portion of the disk to use.
.Pp
@ -568,12 +593,10 @@ 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 .
.Em "Editing the NetBSD disklabel" .
.if r_i386 \{\
.It
Editing the Master Boot Record.
.Em "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.
@ -610,9 +633,7 @@ disklabel.
.Pp
.\}
.It
.Em Editing the
.Nx
.Em disklabel .
.Em Editing the NetBSD disklabel
.Pp
The partition table of the
.Nx
@ -644,61 +665,50 @@ A swap partition has a special type called
.
.ie r_i386 \{\
.
.
You can also specify a partition as type
.Sy msdos .
.Sy MSDOS .
This is useful if you share the disk with
.Tn MS-DOS
or Windows95;
or
.Tn Windows ;
.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 can use the values from the MBR for the
.Tn 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
.Nx ).
.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.
.
.
.ds usrpart e
.\}
.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.
.
.
.ds usrpart d
.\}
.
Some partitions in the disklabel have a fixed purpose.
.(tag 6n -offset indent
.It Li a
Root partition.
.Pq Pa / ,
.It Li b
Swap partition.
.It Li c
.if r_i386 \{\
The
.Nx
portion of the disk.
.It Li d
.\}
The entire disk.
.It Li \*[usrpart]-h
Available for other use.
Traditionally,
.Li \*[usrpart]
is the partition mounted on
.Pa /usr ,
but this is historical practice and not a fixed value.
.tag)
.
.Pp
You will then be asked to name your disk's disklabel. The
@ -713,7 +723,7 @@ need to remember this name.
.It
.Em Preparing your hard disk
.Pp
.Em You\ are\ now\ at\ the\ point\ of\ no\ return .
.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
@ -724,7 +734,7 @@ 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 filesystems will be initialized to
systems you specified. The file systems will be initialized to
contain
.Nx
bootstrapping binaries and configuration files.
@ -751,26 +761,30 @@ hard drive yet at this point.
.Note)
.\}
.It
.Em Getting the distribution sets.
.Em Getting the distribution sets
.if r_i386 \{\
.(pcmcia
.
Load a kernel tar file (i.e. the kern.tgz set file)
Load a kernel tar file (i.e. the
.Pa 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)
hard disk first, copying the
.Pa kern.tgz
file from floppy and unpacking it. Example:
.Pp
Then halt the machine using the 'halt' command. Power
.Dl # Ic "mount /dev/wd0a /mnt"
.Dl # Ic "cd /mnt"
.Pp
.D1 Em "repeat the following 3 steps until all kern.* files are there"
.Dl # Ic "mount -t msdos /dev/fd0a /mnt2"
.Dl # Ic "cp /mnt2/kern.* ."
.Dl # Ic "umount /mnt2"
.Dl # Ic "cat kern.* \&| tar zxpvf -"
.Pp
Then halt the machine using the
.Ic halt
command. Power
the machine down, and re-insert all the
.Tn PCMCIA
devices.
@ -781,7 +795,7 @@ you will
be presented with the main
.Ic sysinst
menu. Choose the
option to re-install sets. Wait for the filesystem
option to re-install sets. Wait for the file system
checks that it will do to finish, and then proceed
as described below.
.pcmcia)
@ -815,8 +829,9 @@ the install procedure.
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.
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, the directory on that host,
@ -839,8 +854,9 @@ the install procedure.
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.
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
@ -869,22 +885,23 @@ 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 MS-DOS
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.
.\}
.It
.Em Installation from an unmounted filesystem
.Em Installation from an unmounted file system
.Pp
In order to install from a local filesystem, you will
need to specify the device that the filesystem resides
In order to install from a local file system, you will
need to specify the device that the file system resides
on
.ie r_pmax .Pq for example Li rz1e
.el .Pq for example Li wd1e
the type of the filesystem,
and the directory on the specified filesystem where the sets are located.
the type of the file system,
and the directory on the specified file system where the sets are located.
.Ic sysinst
will then check if it
can indeed access the sets at that location.
@ -893,7 +910,7 @@ can indeed access the sets at that location.
.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.
file system that is already accessible.
.Ic sysinst
will ask you
for the name of this directory.
@ -908,7 +925,7 @@ 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
.Pq Sy kern, base No and Sy etc
they will not be shown in this selection menu.
.Pp
Before extraction begins, you can elect to watch the files being
@ -922,7 +939,7 @@ 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
.Em Finalizing your installation.
.Em Finalizing your installation
.Pp
Congratulations, you have successfully installed
.Nx \*V .

View File

@ -1,4 +1,4 @@
.\" $NetBSD: upgrade,v 1.6 2000/10/10 12:24:27 lukem Exp $
.\" $NetBSD: upgrade,v 1.7 2000/10/29 12:32:24 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -78,13 +78,17 @@ To do the upgrade, you must have the boot floppy
available.
.\}
You must also have at least the
.Ic base No and Ic kern
.Sy base
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.
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
If you have a few megabytes free on each of your root
.Pq Pa /
and
.Pa /usr
partitions, you should have enough space.
.Pp
@ -108,7 +112,7 @@ 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.
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
@ -122,8 +126,10 @@ 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
.Pa /dev ,
and run the command
.Pp
.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
@ -132,7 +138,7 @@ that the options given to many of the file systems in
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
for the file system's mount commands, for example
.Xr mount_nfs 8
for NFS.
.Pp

View File

@ -1,4 +1,4 @@
.\" $NetBSD: xfer,v 1.7 2000/10/11 11:47:46 tsutsui Exp $
.\" $NetBSD: xfer,v 1.8 2000/10/29 12:32:24 lukem Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -32,13 +32,12 @@
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.
.\" ===== MD instructions on setting up boot media
.\"
.\" ---------- MD instructions on setting up boot media
.
.if r_arm32 \{\
You will need to have an installation kernel and possibly a boot application.
See
.Li arm32/ Ns Ar platform Ns Li /prep
.Pa arm32/ Ns Ar platform Ns Pa /prep
for details.
.Pp
.\} \" r_arm32
@ -66,7 +65,9 @@ machines. this install image does not have drivers for PCI, PCMCIA,
EISA or SCSI (i.e. ISA-only), but can be used on machines with only
4 MB of RAM.
.Pp
If you are using a UN*X-like system to write the floppy images to
If you are using a
.Ul
system to write the floppy images to
disks, you should use the
.Xr dd
command to copy the file system image(s)
@ -79,9 +80,9 @@ system, and a comprehensive list of the possibilities is beyond the
scope of this document.
.Pp
If you are using
.Tn DOS
.Tn MS-DOS
to write the floppy image(s) to floppy disk, you should use the
.Li rawrite
.Ic rawrite
utility, provided in the
.Pa i386/utilities
directory of the
@ -104,7 +105,9 @@ software to install
.Nx
system.
.Pp
If you are using a UN*X-like system (such as
If you are using a
.Ul
system (such as
.Tn NEWS-OS
or other
.Nx
@ -120,10 +123,10 @@ system, and a comprehensive list of the possibilities is beyond the
scope of this document.
.Pp
If you have an i386 machine which runs
.Tn DOS
.Tn MS-DOS
and use them to write the floppy image(s) to floppy disk,
you can use the
.Li rawrite
.Ic rawrite
utility, provided in the
.Pa i386/installation/misc
directory of the
@ -186,7 +189,9 @@ disk to the target installation system, and then boot the miniroot.
.\} \" r_pmax
.
.if r_vax \{\
Installing on a "bare" machine requires some bootable
Installing on a
.Sq bare
machine requires some bootable
device; either a tape or floppy drive or a NFS server together
with a machine that can act as a MOP loader, such as another
machine running
@ -208,7 +213,8 @@ Use
.Pa loadbsd.x
utility to boot
.Nx
from Human68k
from
.Tn Human68k
.It
Create a boot floppy which contains the install kernel
.bullet)
@ -216,11 +222,11 @@ Create a boot floppy which contains the install kernel
When you chose the first method, you have to put the install kernel
.Pa netbsdsi
(for the standard
.Dq sysinst
.Ic sysinst
installer) or
.Pa netbsd
(for the small
.Dq script
.Ic script
installer) and
.Pa loadbsd.x
utility. These files can be found in
@ -231,20 +237,26 @@ distribution.
The difference between the two installer is described below.
.Pp
To invoke the installer, just type
.D1 Ic loadbsd.x netbsdsi
.Pp
.Dl Ic "loadbsd.x netbsdsi"
.Pp
or
.D1 Ic loadbsd.x netbsd
from Human68k command line.
.Pp
.Dl Ic "loadbsd.x netbsd"
.Pp
from the
.Tn Human68k
command line.
.Pp
When you chose the second method, you have to create the boot floppy
from the floppy image
.Pa sysinst.fs
(for the standard
.Dq sysinst
.Ic sysinst
installer) or
.Pa boot.fs
(for the small
.Dq script
.Ic script
installer).
The image files can be found in
.Pa installation/floppy
@ -253,19 +265,24 @@ directory of the
distribution.
The difference between the two installer is described below.
.Pp
If you are using a UN*X-like system to write the floppy image to
If you are using a
.Ul
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 dd(1) manual page or
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
arguments to use; it will be slightly different from system to system,
and a comprehensive list of the possibilities is beyond the scope of
this document.
.Pp
If you are using Human68k to write the floppy images to disks, you
should use the
.Pa rawrite
If you are using
.Tn Human68k
to write the floppy images to disks, you should use the
.Ic rawrite
utility, provided in the
.Pa installation/misc
directory of the
@ -289,49 +306,46 @@ the drive after the system has booted.
XXXX
..
.
.\"
.\" ===== MI instructions for getting distribution off installation medium
.\"
.\" --------- MI instructions for getting distribution off installation medium
.
Installation is supported from several media types, including:
.Pp
.(bullet -offset indent -compact
.
.if r_amiga \{\
AmigaDOS
.Tn AmigaDOS
.It
.\} \" r_amiga
.
CD-ROM
.It
.
.if !\n[news68k]:\n[pmax]:\n[vax]:\n[x68k] \{\
DOS floppy
.if !\n[news68k]:\n[macppc]:\n[pmax]:\n[vax]:\n[x68k] \{\
.It
.\} \" ! \n[news68k]:\n[pmax]:\n[vax]:\n[x68k]
.Tn MS-DOS No floppy
.\} \" ! \n[news68k]:\n[macppc]:\n[pmax]:\n[vax]:\n[x68k]
.
.It
FTP
.It
.
.if r_x68k \{\
.if \n[x68k] \{\
.It
Magneto-Optical (M-O) or other removable SCSI disk
.It
.\} \" r_x68k
.\} \" \n[x68k]
.
.It
Remote NFS partition
.if !r_news68k \{\
.It
.\} \" ! r_news68k
.
.if !r_news68k \{\
.if !\n[macppc]:\n[news68k] \{\
.It
Tape
.It
.\} \" ! r_news68k
.\} \" ! \n[macppc]:\n[news68k]
.
.if !r_news68k \{\
.if !\n[macppc]:\n[news68k] \{\
.It
Existing
.Nx
partitions, if performing an upgrade
.\} \" ! r_news68k
.\} \" ! \n[macppc]:\n[news68k]
.
.bullet)
.Pp
@ -340,15 +354,18 @@ The steps necessary to prepare the distribution sets for installation
depend upon which installation medium you choose.
The steps for the various media are outlined below.
.
.(tag DOS\ floppy
.(tag MS-DOS\ floppy
.
.if r_amiga \{\
.It Em AmigaDOS
.It Em AmigaDOS partition
To install
.Nx
from an AmigaDOS partition, you need to get the
from an
.Tn AmigaDOS
partition, you need to get the
.Nx
distribution sets you wish to install on your system on to an AmigaDOS
distribution sets you wish to install on your system on to an
.Tn AmigaDOS
partition.
All of the
.Pa set_name.xx
@ -372,7 +389,8 @@ supported by
(refer to the supported hardware list) or an ATAPI cd-rom connected to the
A1200 or A4000 internal IDE connector.
If it is a SCSI CD-ROM on a non-supported SCSI bus like Blizzard-3 SCSI
or Apollo SCSI you must first copy the distribution sets to an AmigaDOS
or Apollo SCSI you must first copy the distribution sets to an
.Tn AmigaDOS
partition as described above.
.Pp
If your SCSI CD-ROM is connected to a supported SCSI host adapter,
@ -384,9 +402,11 @@ Find out where the distribution set files are on the CD-ROM.
.Pp
Proceed to the instruction on installation.
.
.if !\n[news68k]:\n[pmax]:\n[vax]:\n[x68k] \{\
.It Em DOS floppy
Count the number of "set_name.xx" files that make up the
.if !\n[news68k]:\n[macppc]:\n[pmax]:\n[vax]:\n[x68k] \{\
.It Em MS-DOS floppy
Count the number of
.Pa set_name. Ns Ar xx
files that make up the
distribution sets you want to install or upgrade.
.ie r_i386 \{\
You will need one fifth that number of 1.2 MB floppies, or one sixth that
@ -399,36 +419,38 @@ You will need one sixth that number of 1.44 MB floppies.
\} \" ! r_i386
.Pp
Format all of the floppies with
.Tn DOS .
.Tn MS-DOS .
Do
.Em not
make any of them bootable
.Tn DOS
.Tn MS-DOS
floppies, i.e. don't use
.Li format /s
to format them.
(If the floppies are bootable, then the
.Tn DOS
.Tn MS-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
.Tn DOS
.Tn MS-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
.Tn DOS
Place all of the
.Pa "set_name." Ns Ar xx
files on the
.Tn MS-DOS
disks.
.Pp
Once you have the files on
.Tn DOS
.Tn MS-DOS
disks, you can proceed to the next step in the installation or upgrade process.
If you're installing
.Nx
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.
.\} \" ! \n[news68k]:\n[pmax]:\n[vax]:\n[x68k]
.\} \" ! \n[news68k]:\n[macppc]:\n[pmax]:\n[vax]:\n[x68k]
.
.It Em FTP
The preparations for this installation/upgrade method are
@ -464,32 +486,42 @@ If you're upgrading an existing installation, go directly to
the section on upgrading.
.(Note
This method of installation is recommended only for those already familiar
with using BSD network configuration and management commands.
with using
.Bx
network configuration and management commands.
If you aren't, this documentation should help, but is not intended to
be all-encompassing.
.Note)
.
.if r_x68k \{\
.if \n[x68k] \{\
.It Em M-O disk
To install
.Nx
from a device such as a removable SCSI disk or a magneto-optical disk,
the media
.Em must
be of the IBM
be of the
.Tn IBM
.Em Super-floppy
format.
The Human68k format is not recognized by this release of the
The
.Tn Human68k
format is not recognized by this release of the
.Nx*M .
If you have a
.Tn DOS
or MS-Windows
.Tn MS-DOS
or
.Tn Windows
machine with an M-O drive connected, use it.
If you don't, and if you have a program to handle IBM format M-O
for Human68k, copy all the files in the subdirectory
If you don't, and if you have a program to handle
.Tn IBM
format M-O for
.Tn Human68k ,
copy all the files in the subdirectory
.Pa x68k/binaries
and CHANGE THEIR NAMES TO UPPER CASE.
.\} \" r_x68k
and
.Em "change their names to upper case".
.\} \" \n[x68k]
.
.It Em NFS
Place the
@ -526,29 +558,41 @@ If you're upgrading an existing installation, go directly to the
section on upgrading.
.(Note
This method of installation is recommended only for those already
familiar with using BSD network configuration and management commands.
familiar with using
.Bx
network configuration and management commands.
If you aren't, this documentation should help, but is not intended to
be all-encompassing.
.Note)
.
.if !r_news68k \{\
.if !\n[macppc]:\n[news68k] \{\
.It Em Tape
To install
.Nx
from a tape, you need to make a tape that
contains the distribution set files, in "tar" format.
contains the distribution set files, in
.Sq tar
format.
.if \n[pmax]:\n[vax] \{\
.(Note
the tape devices with which
.Nx*M
is believed to work is the DEC
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.
.Note)
.\} \" \n[pmax]:\n[vax]
.Pp
If you're making the tape on a UN*X-like system, the easiest way
If you're making the tape on a
.Ul
system, the easiest way
to do so is probably something like:
.D1 Ic tar -cf Ar tape_device dist_directories
.No where Ar tape_device
.Pp
.Dl # Ic "tar -cf Ar tape_device dist_directories"
.Pp
where
.Ar tape_device
is the name of the tape device that
describes the tape drive you're using; possibly
.Pa /dev/rst0 ,
@ -564,10 +608,10 @@ For instance, to put the
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 \*M/binary
And then:\ \~
.D1 Ic tar -cf Ar tape_device misc etc kern
.Pp
.Dl # Ic "cd \&.../NetBSD-\*V"
.Dl # Ic "cd \*M/binary"
.Dl # Ic "tar -cf Ar tape_device misc etc kern"
.Pp
.(Note
You still need to fill in
@ -581,9 +625,9 @@ If you're installing
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.
.\} \" ! r_news68k
.\} \" ! \n[macppc]:\n[news68k]
.
.if !r_news68k \{\
.if !\n[macppc]:\n[news68k] \{\
.It Em Upgrade
If you are upgrading
.Nx ,
@ -596,9 +640,15 @@ To do that, you must do the following:
Place the distribution sets you wish to upgrade somewhere in
your current file system tree.
.if !r_pmax \{\
Please note that the /dev on
the floppy used for upgrades only knows about wd0, wd1, sd0,
sd1 and sd2.
Please note that the
.Pa /dev
on the floppy used for upgrades only knows about
.Li wd0 ,
.Li wd1 ,
.Li sd0 ,
.Li sd1 ,
and
.Li 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.
.\} \" ! r_pmax
@ -621,6 +671,6 @@ 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.
.\} \" ! r_news68k
.\} \" ! \n[macppc]:\n[news68k]
.
.tag)