clean up whitespace, formatting, copyrights
This commit is contained in:
lukem
parent
1d70ab3a63
commit
cfaac1c351
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: hardware,v 1.12 2002/04/23 19:48:41 bouyer Exp $
|
||||
.\" $NetBSD: hardware,v 1.13 2002/06/29 09:33:10 lukem Exp $
|
||||
.
|
||||
.Nx*M
|
||||
\*V runs on most of the
|
||||
@ -13,7 +13,8 @@ console can be distinguished from the ARC console (which is used to
|
||||
boot
|
||||
.Tn "Windows NT" )
|
||||
by the fact that it has a command line interface,
|
||||
rather than a menu-driven interface. The SRM prompt is
|
||||
rather than a menu-driven interface.
|
||||
The SRM prompt is
|
||||
.Sq Li \*>\*>\*> .
|
||||
.Pp
|
||||
Some platforms have both the SRM console and
|
||||
@ -44,20 +45,22 @@ Because
|
||||
.Nx
|
||||
has an extremely machine-independent device driver
|
||||
system, many device drivers are the same as used in other ports that
|
||||
use the same bus. For example, the
|
||||
use the same bus.
|
||||
For example, the
|
||||
.Em de
|
||||
network card driver is shared
|
||||
by the i386 and \*M ports. Some drivers on inspection appear as if
|
||||
they will work on the \*M but have not been tested because that
|
||||
hardware was not available to
|
||||
by the i386 and \*M ports.
|
||||
Some drivers on inspection appear as if they will work on the
|
||||
\*M but have not been tested because that hardware was not available to
|
||||
.Nx
|
||||
testers; these are marked as
|
||||
.Em UNTESTED
|
||||
below. If you have one of these devices, and it does work,
|
||||
below.
|
||||
If you have one of these devices, and it does work,
|
||||
please get in touch with
|
||||
.Mt port-\*M-maintainer@netbsd.org
|
||||
and let us know that it works. If it doesn't work, do the same thing and we
|
||||
can probably fix it pretty easily.
|
||||
and let us know that it works.
|
||||
If it doesn't work, do the same thing and we can probably fix it pretty easily.
|
||||
.
|
||||
.Ss2 Supported PCI bus devices
|
||||
.(bullet -offset indent
|
||||
@ -258,8 +261,9 @@ SCSI tapes st0, st1, ...
|
||||
SCSI and ATAPI CD-ROMs cd0, cd1, ...
|
||||
For each SCSI and IDE controller found, the SCSI or ATA(PI) devices
|
||||
present on the bus are probed in increasing ID order for SCSI and
|
||||
master/slave order for ATA(PI). So the first SCSI drive found will
|
||||
be called sd0, the second sd1, and so on ...
|
||||
master/slave order for ATA(PI).
|
||||
So the first SCSI drive found will be called sd0, the second sd1,
|
||||
and so on ...
|
||||
|
||||
3COM 3x59X or 3COM 3x90X PCI Ethernet boards
|
||||
ep0 any any [you must assign an interrupt in your
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
.\" $NetBSD: install,v 1.23 2002/02/16 18:17:04 he Exp $
|
||||
.\" $NetBSD: install,v 1.24 2002/06/29 09:33:10 lukem Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1999, 2000 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
|
||||
@ -62,8 +62,8 @@ The usual procedure is to write the installation system to a floppy
|
||||
disk set and then boot from the floppies, however, there
|
||||
are now six ways to boot the
|
||||
.Nx*M
|
||||
installation system! Each approach
|
||||
loads the exact same installation bits.
|
||||
installation system!
|
||||
Each approach loads the exact same installation bits.
|
||||
The six paths are:
|
||||
.Pp
|
||||
.
|
||||
@ -90,10 +90,12 @@ CD or from an ftp site to the chosen media type.
|
||||
Although booting from floppy is the usual path, the
|
||||
hard drive boot is useful if you have another operating system (and a spare
|
||||
drive) already installed, or if you don't mind swapping hard drives from
|
||||
box to box. CD and tape boots are nice and fast if you have a CD writer
|
||||
box to box.
|
||||
CD and tape boots are nice and fast if you have a CD writer
|
||||
or a tape format in common with another previously installed
|
||||
.Ul
|
||||
system. Finally, most versions of SRM can locate the
|
||||
system.
|
||||
Finally, most versions of SRM can locate the
|
||||
.Nx
|
||||
boot program
|
||||
.Ic netboot
|
||||
@ -148,7 +150,8 @@ system available, you can use
|
||||
the
|
||||
.Ic rawrite.exe
|
||||
utility to transfer the image to a floppy
|
||||
disk. This utility is provided with the
|
||||
disk.
|
||||
This utility is provided with the
|
||||
.Nx Ns /i386
|
||||
install tools, under
|
||||
.Pa i386/installation/misc ;
|
||||
@ -180,7 +183,8 @@ To boot from a magnetic tape device such as
|
||||
or
|
||||
.Tn DLT ,
|
||||
it is important
|
||||
to create the tape image with 512-byte records. Use a command like:
|
||||
to create the tape image with 512-byte records.
|
||||
Use a command like:
|
||||
.Pp
|
||||
.Dl # Ic "dd if=cdhdtape bs=512 of=/dev/rst0"
|
||||
.Pp
|
||||
@ -202,9 +206,9 @@ The installation subdirectory
|
||||
contains
|
||||
.Pa netbsd.gz ;
|
||||
this is the same install kernel but without a bootable file system
|
||||
image wrapped around it. You can perform an complete reinstall
|
||||
by beginning it as an upgrade, and booting this kernel in the
|
||||
normal way off the root file system
|
||||
image wrapped around it.
|
||||
You can perform an complete reinstall by beginning it as an upgrade,
|
||||
and booting this kernel in the normal way off the root file system
|
||||
.Pq Pa /
|
||||
of a previous installation.
|
||||
.Pp
|
||||
@ -217,26 +221,28 @@ Network Boot
|
||||
Booting
|
||||
.Nx*M
|
||||
\*V over a network requires a BOOTP or
|
||||
DHCP server, a TFTP server and an NFS server. (These are usually
|
||||
all run on the same machine.) There are three basic stages to
|
||||
the boot:
|
||||
DHCP server, a TFTP server and an NFS server.
|
||||
(These are usually all run on the same machine.)
|
||||
There are three basic stages to the boot:
|
||||
.Pp
|
||||
.
|
||||
.
|
||||
.(bullet
|
||||
\*M console software sends a BOOTP request to get its
|
||||
own address, the address of the TFTP server and the file to
|
||||
download. It downloads this file, which is the second stage
|
||||
bootstrap, via TFTP and then executes it.
|
||||
download.
|
||||
It downloads this file, which is the second stage bootstrap,
|
||||
via TFTP and then executes it.
|
||||
.It
|
||||
The secondary boot program resends the BOOTP request, this
|
||||
time also locating the NFS server and root path. It mounts the
|
||||
root path via NFS and reads in and transfers to the kernel:
|
||||
time also locating the NFS server and root path.
|
||||
It mounts the root path via NFS and reads in and transfers to the kernel:
|
||||
.Pa /netbsd .
|
||||
.It
|
||||
The kernel probes and configures the devices, and then sends
|
||||
out another BOOTP request so it can find out its address, the NFS
|
||||
server, and path. It then mounts its root
|
||||
server, and path.
|
||||
It then mounts its root
|
||||
.Pq Pa /
|
||||
via NFS and continues.
|
||||
.bullet)
|
||||
@ -249,8 +255,8 @@ from the network, untar the
|
||||
.Nx
|
||||
snapshot or distribution
|
||||
into a directory on your server and NFS export that directory
|
||||
to the client. Make sure you put a kernel there as well, and
|
||||
create the device nodes in
|
||||
to the client.
|
||||
Make sure you put a kernel there as well, and create the device nodes in
|
||||
.Pa /dev
|
||||
with
|
||||
.Ic sh ./MAKEDEV all .
|
||||
@ -299,8 +305,8 @@ so for the TFTP setup, you need to copy the second stage bootstrap,
|
||||
.Ic netboot ,
|
||||
into an appropriately named file such as
|
||||
.Li boot.netbsd.\*M
|
||||
in the directory used by your TFTP server. If you extracted a full
|
||||
snapshot, you can get the netboot program from
|
||||
in the directory used by your TFTP server.
|
||||
If you extracted a full snapshot, you can get the netboot program from
|
||||
.Pa /usr/mdec/netboot ;
|
||||
if not, you can get this from the
|
||||
.Pa installation/netboot
|
||||
@ -356,14 +362,16 @@ host axp {
|
||||
The only Ethernet device the console on most \*M systems
|
||||
knows how to boot from is the onboard Ethernet interface or a
|
||||
.Tn DEC
|
||||
Tulip (21040, 21041, 21140) PCI Ethernet card. Some
|
||||
older SMC 100 Mbps cards that use this chip have been known to
|
||||
work as well. Many older systems will not be able to use the
|
||||
newer 2.0 stepping of the 21140, however. If your system appears
|
||||
not to be receiving packets, this may be the problem. (You may
|
||||
or may not be able to update your firmware to fix this; see
|
||||
Tulip (21040, 21041, 21140) PCI Ethernet card.
|
||||
Some older SMC 100 Mbps cards that use this chip have been known to
|
||||
work as well.
|
||||
Many older systems will not be able to use the newer 2.0 stepping
|
||||
of the 21140, however.
|
||||
If your system appears not to be receiving packets, this may be the problem.
|
||||
(You may or may not be able to update your firmware to fix this; see
|
||||
the \*M port pages on www.netbsd.org for more information on
|
||||
this.) In general, 10 Mb cards from manufacturers other than
|
||||
this.)
|
||||
In general, 10 Mb cards from manufacturers other than
|
||||
.Tn DEC
|
||||
will work, and 100 Mb cards not from
|
||||
.Tn DEC
|
||||
@ -383,15 +391,17 @@ The 3000 series of Turbochannel systems and certain other models use
|
||||
.Em old SRM ,
|
||||
do not have a
|
||||
.Fl proto
|
||||
option and use different device names. They also tend to not netboot very
|
||||
well so you probably don't need to worry about this section. However, if you
|
||||
want to give it a try, note the following differences:
|
||||
option and use different device names.
|
||||
They also tend to not netboot very well so you probably don't
|
||||
need to worry about this section.
|
||||
However, if you want to give it a try, note the following differences:
|
||||
.(bullet -offset indent
|
||||
There is no
|
||||
.Fl proto
|
||||
argument, or
|
||||
.Ic ewa0_protocols
|
||||
variable. Old SRM uses bootp if the device name is given as
|
||||
variable.
|
||||
Old SRM uses bootp if the device name is given as
|
||||
.Sy ez0 .
|
||||
.It
|
||||
The use of the
|
||||
@ -434,7 +444,8 @@ unpacking the tar files into these followed by running MAKEDEV.
|
||||
.Pp
|
||||
However, as stated above it is also possible to do the installation yourself
|
||||
from the shell, and in any case it is helpful to understand
|
||||
what the install script does. The procedure is:
|
||||
what the install script does.
|
||||
The procedure is:
|
||||
.Pp
|
||||
.
|
||||
.
|
||||
@ -490,8 +501,8 @@ at the shell prompt and run them as you did in the good old days.
|
||||
.Pp
|
||||
You may install
|
||||
on either a SCSI or an IDE disk; you will be prompted for
|
||||
the disk to install on. The disks in your system will be numbered
|
||||
starting at
|
||||
the disk to install on.
|
||||
The disks in your system will be numbered starting at
|
||||
.Em x Ns Li d0
|
||||
(where
|
||||
.Em x
|
||||
@ -504,7 +515,8 @@ more than one disk, watch the boot messages carefully to see
|
||||
which ones are probed as which numbers.
|
||||
.Pp
|
||||
Once you've selected a disk to install on, you'll be prompted
|
||||
for the geometry. This is also displayed in the boot messages,
|
||||
for the geometry.
|
||||
This is also displayed in the boot messages,
|
||||
and you'll be given a chance to review the boot messages again
|
||||
to get the exact figures for the number of cylinders, heads
|
||||
and sectors.
|
||||
@ -515,7 +527,8 @@ program will tell you how many bytes there are in each cylinder.
|
||||
.Pp
|
||||
The swap partition is the second thing you specify, after the
|
||||
.Pa /
|
||||
(root) partition. Regardless of the size of your disk, you'll
|
||||
(root) partition.
|
||||
Regardless of the size of your disk, you'll
|
||||
want to specify a swap partition that's at least as large as
|
||||
the amount of RAM you have, and probably not less than 64 MB
|
||||
in any case.
|
||||
@ -531,22 +544,24 @@ and preferably 48 MB, to the
|
||||
.Pa /
|
||||
(root) partition.
|
||||
.Pa /usr
|
||||
will need 150 MB or so if you're not installing X, 200 MB or so if you
|
||||
are. A typical organization is 50 MB for
|
||||
will need 150 MB or so if you're not installing X, 200 MB or so if you are.
|
||||
A typical organization is 50 MB for
|
||||
.Pa /
|
||||
(root), 150-250 MB for
|
||||
swap, and the remaining space for
|
||||
.Pa /usr .
|
||||
With enough swap space configured, you can make
|
||||
.Pa /tmp
|
||||
a nice, fast mfs. See
|
||||
a nice, fast mfs.
|
||||
See
|
||||
.Xr mount_mfs 8 ,
|
||||
and note that the mfs will require swap space for
|
||||
the largest planned amount of
|
||||
.Pa /tmp
|
||||
storage. It doesn't return
|
||||
space when files are deleted, but just keeps it its own freelist
|
||||
so the swap space required is equal to the highwater mark of
|
||||
storage.
|
||||
It doesn't return space when files are deleted,
|
||||
but just keeps it its own freelist so the swap space required is
|
||||
equal to the highwater mark of
|
||||
.Pa /tmp
|
||||
use, plus space required to back up main memory and store inactive images.
|
||||
.Pp
|
||||
@ -567,10 +582,9 @@ shell commands or the script assist, you then need only
|
||||
unpack the distribution sets with the
|
||||
.Xr tar 1
|
||||
command.
|
||||
To do this you will need access from the target host
|
||||
to the tar files
|
||||
that contain the operating system in order to extract them to your
|
||||
disk. This is done via an NFS or FTP transfer over a network,
|
||||
To do this you will need access from the target host to the tar files
|
||||
that contain the operating system in order to extract them to your disk.
|
||||
This is done via an NFS or FTP transfer over a network,
|
||||
via a CD-ROM archive, a tape archive, or by preloading an accessible hard
|
||||
drive with the necessary tar files.
|
||||
.
|
||||
@ -579,8 +593,10 @@ drive with the necessary tar files.
|
||||
Preparing to Install from a CD-ROM
|
||||
.Pp
|
||||
All you need to do is mount the CD-ROM, which will generally
|
||||
be device cd0. (The initial boot messages will tell you what
|
||||
the CD-ROM drive is probed as.) This would be done with:
|
||||
be device cd0.
|
||||
(The initial boot messages will tell you what
|
||||
the CD-ROM drive is probed as.)
|
||||
This would be done with:
|
||||
.Pp
|
||||
.Dl # Ic "mount -r -t cd9660 /dev/cd0a /mnt2"
|
||||
.It
|
||||
@ -591,7 +607,8 @@ interface, which is done with the command
|
||||
.Pp
|
||||
.Dl # Ic "ifconfig lo0 127.0.0.1"
|
||||
.Pp
|
||||
Then you will have to configure your Ethernet card. The command
|
||||
Then you will have to configure your Ethernet card.
|
||||
The command
|
||||
.Pp
|
||||
.Dl # Ic "ifconfig -l"
|
||||
.Pp
|
||||
@ -631,8 +648,8 @@ parameter is one of:
|
||||
.
|
||||
.Pp
|
||||
If the host you are getting the data files from is not on the
|
||||
local network, you will also have to configure a gateway into
|
||||
your system. Do this with
|
||||
local network, you will also have to configure a gateway into your system.
|
||||
Do this with
|
||||
.Pp
|
||||
.Dl # Ic "route add default \*<gateway-IP-address\*>"
|
||||
.Pp
|
||||
@ -711,9 +728,9 @@ Now make the device nodes:
|
||||
.It
|
||||
Restart your system
|
||||
.Pp
|
||||
Unmount the file systems and halt. The exact instructions to
|
||||
type here will depend on the file systems you created, but
|
||||
typically the commands are:
|
||||
Unmount the file systems and halt.
|
||||
The exact instructions to type here will depend on the file systems
|
||||
you created, but typically the commands are:
|
||||
.Pp
|
||||
.Dl # Ic "cd /"
|
||||
.Dl # Ic "umount /mnt/usr"
|
||||
@ -735,9 +752,8 @@ This command might be:
|
||||
if your drive is on ID 1.
|
||||
You can usually use
|
||||
.Ic "show device"
|
||||
to see a full list of bootable
|
||||
devices in your system. Your system will come up in single-user
|
||||
mode, ready for you to configure it.
|
||||
to see a full list of bootable devices in your system.
|
||||
Your system will come up in single-user mode, ready for you to configure it.
|
||||
.
|
||||
.enum)
|
||||
.
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
.\" $NetBSD: prep,v 1.5 2000/10/10 12:55:16 lukem Exp $
|
||||
.\" $NetBSD: prep,v 1.6 2002/06/29 09:33:10 lukem Exp $
|
||||
.
|
||||
If you have any data on your disks that you want to keep,
|
||||
.Em back it up
|
||||
before starting. Note that
|
||||
before starting.
|
||||
Note that
|
||||
.Nx*M
|
||||
does not support booting more than
|
||||
one operating system from a single disk, although it's fine to have
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: whatis,v 1.7 2000/10/29 14:08:04 lukem Exp $
|
||||
.\" $NetBSD: whatis,v 1.8 2002/06/29 09:33:10 lukem Exp $
|
||||
.
|
||||
There have been many \*M-specific enhancements since the
|
||||
1.4 release.
|
||||
@ -21,7 +21,8 @@ Ability to boot off LFS partitions.
|
||||
traceback code added.
|
||||
.It
|
||||
Emulate user program use of BWX instructions on CPUs which don't
|
||||
support them. Handle unaligned accesses caused by BWX instructions.
|
||||
support them.
|
||||
Handle unaligned accesses caused by BWX instructions.
|
||||
.It
|
||||
Improved TGA graphics support, accelerating the text mode and adding
|
||||
support for the: 8bpp TGA2, and 32bpp ZLXp-E2 and -E3.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: hardware,v 1.43 2002/01/27 19:50:10 aymeric Exp $
|
||||
.\" $NetBSD: hardware,v 1.44 2002/06/29 09:36:23 lukem Exp $
|
||||
.
|
||||
.Nx \*V
|
||||
runs on any Amiga that has a 68020 or better CPU with
|
||||
@ -14,10 +14,12 @@ system utilities.
|
||||
68LC040, 68040V and 68LC060 systems don't work correctly at the moment.
|
||||
.Pp
|
||||
The minimal configuration requires 6 MB of RAM (not including CHIPMEM!)
|
||||
and about 75 MB of disk space. To install the entire system requires
|
||||
much more disk space, and to run X or compile the system, more RAM
|
||||
is recommended. (6 MB of RAM will actually allow you to compile,
|
||||
however it won't be speedy. X really isn't usable on a 6 MB system.)
|
||||
and about 75 MB of disk space.
|
||||
To install the entire system requires much more disk space,
|
||||
and to run X or compile the system, more RAM is recommended.
|
||||
(6 MB of RAM will actually allow you to compile,
|
||||
however it won't be speedy.
|
||||
X really isn't usable on a 6 MB system.)
|
||||
.Pp
|
||||
Here is a table of recommended HD partition sizes for a full install:
|
||||
.Bl -column -offset indent Partition Suggested 100xMBxx Needed 100xMB
|
||||
@ -141,8 +143,8 @@ Mustek SCSI scanner.
|
||||
SCSI scanner support is machine independent, so it should
|
||||
work, but hasn't been tested yet on most Amiga configurations.
|
||||
There are reports that the Mustek and HP ScanJet hang if
|
||||
accessed from the A3000. This might apply to other
|
||||
33C93-Adapters, too.
|
||||
accessed from the A3000.
|
||||
This might apply to other 33C93-Adapters, too.
|
||||
.It
|
||||
Most SCSI CD-ROM drives
|
||||
.It
|
||||
@ -161,11 +163,11 @@ Amiga floppy drives with Amiga (880/1760kB) and
|
||||
.Tn IBM
|
||||
(720/1440kB) encoding.
|
||||
Our floppy driver doesn't notice when mounted floppies are
|
||||
write-protected at the moment. Your floppy will stay
|
||||
unchanged, but you might not notice that you didn't write
|
||||
anything due to the buffer cache. Also note that HD floppy
|
||||
drives only get detected as such if a HD floppy is inserted at
|
||||
boot time.
|
||||
write-protected at the moment.
|
||||
Your floppy will stay unchanged, but you might not notice that
|
||||
you didn't write anything due to the buffer cache.
|
||||
Also note that HD floppy drives only get detected as such if a
|
||||
HD floppy is inserted at boot time.
|
||||
.It
|
||||
Amiga parallel port
|
||||
.It
|
||||
@ -185,7 +187,7 @@ DraCo builtin (r/o)
|
||||
.bullet)
|
||||
.bullet)
|
||||
.Pp
|
||||
If its not on the above lists, there is no support for it in this
|
||||
release. Especially (but this is an incomplete list), there are no
|
||||
If its not on the above lists, there is no support for it in this release.
|
||||
Especially (but this is an incomplete list), there are no
|
||||
drivers for: Blizzard III SCSI option,
|
||||
Ferret SCSI, Oktagon SCSI.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
.\" $NetBSD: install,v 1.29 2002/02/10 20:43:33 is Exp $
|
||||
.\" $NetBSD: install,v 1.30 2002/06/29 09:36:23 lukem Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1999, 2000 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
|
||||
@ -43,8 +43,8 @@ detailed in the section on preparing your system for install.
|
||||
.Pp
|
||||
The following is a walk-through of the steps necessary to get
|
||||
.Nx
|
||||
installed on your hard disk. If you wish to stop the installation,
|
||||
you may press
|
||||
installed on your hard disk.
|
||||
If you wish to stop the installation, you may press
|
||||
.Key CONTROL-C
|
||||
at any prompt, but if you do, you'll have to
|
||||
begin again from scratch.
|
||||
@ -65,11 +65,13 @@ directory on
|
||||
.Tn AmigaDOS .
|
||||
You also need to have the
|
||||
.Ic loadbsd
|
||||
program in your command path. If
|
||||
program in your command path.
|
||||
If
|
||||
.Tn AmigaDOS
|
||||
complains about loadbsd not being an executable file, be sure that the
|
||||
.Em Execute
|
||||
protection bit is set. If not, set it with the command:
|
||||
protection bit is set.
|
||||
If not, set it with the command:
|
||||
.Pp
|
||||
.Dl Ic "Protect loadbsd add e"
|
||||
.Pp
|
||||
@ -106,8 +108,9 @@ before using loadbsd, else the kernel will hang!
|
||||
.Nx ,
|
||||
with boot blocks installed
|
||||
.Pp
|
||||
[This description is for V40 (OS 3.1) ROMs. For older ROMs,
|
||||
there might be small differences. Check your
|
||||
[This description is for V40 (OS 3.1) ROMs.
|
||||
For older ROMs, there might be small differences.
|
||||
Check your
|
||||
.Tn AmigaDOS
|
||||
documentation
|
||||
to learn about the exact procedure.]
|
||||
@ -116,7 +119,8 @@ systems, and may require a mountable file system on others.
|
||||
.Pp
|
||||
Reboot your machine, holding down both mouse buttons if you
|
||||
have a 2-button mouse, the outer mouse buttons if you have
|
||||
a 3-button mouse. On the DraCo, press the left mouse button
|
||||
a 3-button mouse.
|
||||
On the DraCo, press the left mouse button
|
||||
instead, when the boot screen prompts you for it.
|
||||
.Pp
|
||||
From the boot menu, select
|
||||
@ -126,8 +130,9 @@ Select the swap partition with the miniroot, and then
|
||||
Select
|
||||
.Ic Boot No now .
|
||||
The machine will boot the bootblock, which
|
||||
will prompt your for a command line. You have a few seconds time
|
||||
to change the default. Entering an empty line will accept the default.
|
||||
will prompt your for a command line.
|
||||
You have a few seconds time to change the default.
|
||||
Entering an empty line will accept the default.
|
||||
.Pp
|
||||
The bootblock uses command lines of the form:
|
||||
.br
|
||||
@ -147,14 +152,15 @@ use
|
||||
.Dl "netbsd -bsSn2"
|
||||
.Ss2 Once your kernel boots
|
||||
You should see the screen clear and some information about
|
||||
your system as the kernel configures the hardware. Note which
|
||||
hard disk device(s) are configured
|
||||
your system as the kernel configures the hardware.
|
||||
Note which hard disk device(s) are configured
|
||||
.Po
|
||||
.Li sd0 ,
|
||||
.Li sd1 ,
|
||||
etc.
|
||||
.Pc
|
||||
Then you will be prompted for a root device. At this time type
|
||||
Then you will be prompted for a root device.
|
||||
At this time type
|
||||
.Li sd0b ,
|
||||
where
|
||||
.Li sd0
|
||||
@ -163,8 +169,8 @@ partition you created during the hard disk preparation.
|
||||
When prompted for a dump device, answer
|
||||
.Sq Ic none
|
||||
for the install
|
||||
(normally, you would tell it one of the swap devices). When
|
||||
prompted for the root file system type, confirm
|
||||
(normally, you would tell it one of the swap devices).
|
||||
When prompted for the root file system type, confirm
|
||||
.Sq Ic generic ,
|
||||
which will auto-detect it.
|
||||
.Pp
|
||||
@ -175,42 +181,46 @@ again with
|
||||
.Pp
|
||||
This disables synchronous transfer on all SCSI devices.
|
||||
.Pp
|
||||
The system should continue to boot. For now ignore
|
||||
The system should continue to boot.
|
||||
For now ignore
|
||||
.Dq WARNING
|
||||
messages about bad dates in clocks, and a warning about
|
||||
.Pa /etc/rc
|
||||
not existing. Eventually you will be be asked to enter the
|
||||
pathname of the shell, just press
|
||||
not existing.
|
||||
Eventually you will be be asked to enter the pathname of the shell, just press
|
||||
.Key RETURN .
|
||||
After a short while,
|
||||
you will be asked to select the type of your keyboard. After
|
||||
After a short while, you will be asked to select the type of your keyboard.
|
||||
After
|
||||
you have entered a valid response here, the system asks you if
|
||||
you want to install or upgrade your system. Since you are
|
||||
reading the
|
||||
you want to install or upgrade your system.
|
||||
Since you are reading the
|
||||
.Em install
|
||||
section,
|
||||
.Sq Ic i
|
||||
would be the proper response here...
|
||||
.Pp
|
||||
The installer starts with a nice welcome messages. Read this
|
||||
message carefully, it also informs you of the risks involved
|
||||
in continuing! If you still want to go on, type
|
||||
The installer starts with a nice welcome messages.
|
||||
Read this message carefully, it also informs you of the risks involved
|
||||
in continuing!
|
||||
If you still want to go on, type
|
||||
.Sq Ic y .
|
||||
The installer now continues by trying to figure out your disk
|
||||
configuration. When it is done, you will be prompted to
|
||||
The installer now continues by trying to figure out your disk configuration.
|
||||
When it is done, you will be prompted to
|
||||
select a root device from the list of disks it has found.
|
||||
.Pp
|
||||
You should know at this point that the disks are
|
||||
.Em not
|
||||
numbered according to their SCSI-ID! The
|
||||
numbered according to their SCSI-ID!
|
||||
The
|
||||
.Nx
|
||||
kernel numbers the SCSI
|
||||
drives (and other devices on the SCSI bus) sequentially as it
|
||||
finds them. The drive with the lowest SCSI-ID will be called
|
||||
drives (and other devices on the SCSI bus) sequentially as it finds them.
|
||||
The drive with the lowest SCSI-ID will be called
|
||||
.Li sd0 ,
|
||||
the next one
|
||||
.Li sd1 ,
|
||||
etc. Also, any Amiga internal IDE disk drives
|
||||
etc.
|
||||
Also, any Amiga internal IDE disk drives
|
||||
will be configured as
|
||||
.Dq SCSI
|
||||
drives, and will be configured
|
||||
@ -220,7 +230,8 @@ SCSI drives (if any are present).
|
||||
.Pp
|
||||
The installer will offer you to look at the
|
||||
.Nx
|
||||
disk label of the disks at this point. You should do this, to find out
|
||||
disk label of the disks at this point.
|
||||
You should do this, to find out
|
||||
what partition letters the
|
||||
.Nx
|
||||
kernel assigned to the partitions you created, and as a check whether the
|
||||
@ -232,14 +243,15 @@ you want to install
|
||||
.Nx ,
|
||||
your hard drive will be modified,
|
||||
and perhaps its contents scrambled at the whim of the install
|
||||
program. Type
|
||||
program.
|
||||
Type
|
||||
.Key Control-C
|
||||
.Em now
|
||||
if you don't want this.
|
||||
.Pp
|
||||
At this time, you will need to tell the installer which partition
|
||||
will be associated with the different file systems. Normally, you'll
|
||||
want to add a partition for
|
||||
will be associated with the different file systems.
|
||||
Normally, you'll want to add a partition for
|
||||
.Pa /usr ,
|
||||
at least.
|
||||
.(tag Caveat:
|
||||
@ -255,28 +267,31 @@ correspond to any Amiga partition!
|
||||
.tag)
|
||||
.Pp
|
||||
The install program will now make the file systems you
|
||||
specified. There should be only one error per file system in
|
||||
this section of the installation. It will look like this:
|
||||
specified.
|
||||
There should be only one error per file system in
|
||||
this section of the installation.
|
||||
It will look like this:
|
||||
.(disp
|
||||
newfs: ioctl (WDINFO): Invalid argument
|
||||
newfs: /dev/rsd0a: can't rewrite disk label
|
||||
.disp)
|
||||
.Pp
|
||||
If there are any others, restart from the beginning of
|
||||
the installation process. This error is ok as the Amiga
|
||||
does not write disklabels currently. You should expect
|
||||
this error whenever using newfs.
|
||||
the installation process.
|
||||
This error is ok as the Amiga does not write disklabels currently.
|
||||
You should expect this error whenever using newfs.
|
||||
.Pp
|
||||
The install will now ask you want to configure any network
|
||||
information. It ill ask for the machine's host name, domain
|
||||
information.
|
||||
It ill ask for the machine's host name, domain
|
||||
name, and other network configuration information.
|
||||
.Pp
|
||||
Since the network configuration might have lead to additional (nfs)
|
||||
file system entries, you get another chance to modify your fstab.
|
||||
.Pp
|
||||
You are finally at the point where some real data will be put on
|
||||
your freshly made file systems. Select the device type you wish
|
||||
to install from and off you go....
|
||||
your freshly made file systems.
|
||||
Select the device type you wish to install from and off you go....
|
||||
.Pp
|
||||
Some notes:
|
||||
.(bullet -offset indent
|
||||
@ -304,9 +319,9 @@ you need the mount-point itself, use
|
||||
.Sq Pa \&. .
|
||||
.bullet)
|
||||
.Pp
|
||||
Next you will be asked to specify the timezone. Just select the
|
||||
timezone you are in. The installer will make the correct setup
|
||||
on your root file system
|
||||
Next you will be asked to specify the timezone.
|
||||
Just select the timezone you are in.
|
||||
The installer will make the correct setup on your root file system
|
||||
.Pq Pa / .
|
||||
After the timezone-link is installed,
|
||||
the installer will proceed by creating the device nodes on your
|
||||
@ -320,17 +335,18 @@ After this, it will copy the kernel from the installation miniroot to
|
||||
the newly installed / upgraded system.
|
||||
If the installed system already has a kernel, it will ask you for
|
||||
confirmation.
|
||||
.Pp If you are doing an upgrade and you did not install the
|
||||
.Pp If you are doing an upgrade and you did not install the
|
||||
kern.tgz distribution set, this is an old kernel, and you should answer
|
||||
"y" to install a working (although restricted) INSTALL kernel.
|
||||
.Pp
|
||||
If you did install the kern.tgz kernel, you normally should answer "n".
|
||||
.Pp
|
||||
Finally, the installer ask you if you want to install the bootblock
|
||||
code on your root disk. This is a matter of personal choice and can
|
||||
also be done from a running
|
||||
code on your root disk.
|
||||
This is a matter of personal choice and can also be done from a running
|
||||
.Nx
|
||||
system. See the
|
||||
system.
|
||||
See the
|
||||
.Xr installboot 8
|
||||
manual page about how to do this.
|
||||
.Pp
|
||||
@ -339,7 +355,8 @@ Once the installer is done, halt the system with the
|
||||
command
|
||||
(wait for
|
||||
.Li halted
|
||||
to be displayed) and reboot. Then again boot
|
||||
to be displayed) and reboot.
|
||||
Then again boot
|
||||
.Nx
|
||||
this time with the command:
|
||||
.Pp
|
||||
@ -351,22 +368,23 @@ from the boot menu, and tell it to boot
|
||||
.Pp
|
||||
.Dl "netbsd -s"
|
||||
.Pp
|
||||
You need to do your final tweaks now. First mount your file systems
|
||||
like so:
|
||||
You need to do your final tweaks now.
|
||||
First mount your file systems like so:
|
||||
.Pp
|
||||
.Dl Ic "mount -av"
|
||||
.Pp
|
||||
Your system is now complete but not completely configured; you
|
||||
should adjust the
|
||||
.Pa /etc/sendmail.cf No file as necessary to suit your
|
||||
site. You should also examine and adjust the settings in
|
||||
.Pa /etc/sendmail.cf
|
||||
file as necessary to suit your site.
|
||||
You should also examine and adjust the settings in
|
||||
.Pa /etc/rc.conf .
|
||||
You can use
|
||||
.Xr vi 1
|
||||
or
|
||||
.Xr ed 1
|
||||
to edit the files. If you installed the man pages
|
||||
you can type
|
||||
to edit the files.
|
||||
If you installed the man pages you can type
|
||||
.Ic man vi No or Ic man ed
|
||||
for instructions on how to use these somewhat non-intuitive editors.
|
||||
.Pp
|
||||
@ -385,4 +403,5 @@ functional:
|
||||
When it boots off of the hard drive, you will have a complete
|
||||
.Nx
|
||||
system!
|
||||
.Em Congratulations! No (You really deserve them!!!)
|
||||
.Em Congratulations!
|
||||
(You really deserve them!!!)
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
.\" $NetBSD: prep,v 1.25 2001/02/11 11:30:54 is Exp $
|
||||
.\" $NetBSD: prep,v 1.26 2002/06/29 09:36:23 lukem Exp $
|
||||
.
|
||||
You will need an
|
||||
.Tn AmigaDOS
|
||||
@ -16,8 +16,8 @@ Note that
|
||||
can't currently be installed on disks with a sector
|
||||
size other than 512 bytes (e.g.,
|
||||
.Dq 640 MB
|
||||
90mm M-O media). You can, however,
|
||||
mount ADOSFS partitions on such M-O's.
|
||||
90mm M-O media).
|
||||
You can, however, mount ADOSFS partitions on such M-O's.
|
||||
.
|
||||
.Ss2 Preparing your hard disk with HDToolBox
|
||||
.
|
||||
@ -27,19 +27,20 @@ A full explanation of HDToolBox can be found with your
|
||||
manuals and is beyond the scope of this document.
|
||||
.Pp
|
||||
The first time you partition a drive, you need to set its drive
|
||||
type so that you have working geometry parameters. To do this
|
||||
you enter the
|
||||
type so that you have working geometry parameters.
|
||||
To do this you enter the
|
||||
.Dq Change drive type
|
||||
menu, and either use
|
||||
.Dq read parameters from drive
|
||||
or set them manually.
|
||||
.Pp
|
||||
Note you will be modifying your HD's. If you mess something
|
||||
up here you could lose everything on all the drives that
|
||||
you configure. It is therefore advised that you:
|
||||
Note you will be modifying your HD's.
|
||||
If you mess something up here you could lose everything on all the
|
||||
drives that you configure.
|
||||
It is therefore advised that you:
|
||||
.(enum -offset indent
|
||||
Write down your current configurations. Do this
|
||||
by examining each partition on the drive and the
|
||||
Write down your current configurations.
|
||||
Do this by examining each partition on the drive and the
|
||||
drives parameters (from Change drive type.)
|
||||
.It
|
||||
Back up the partitions you are keeping.
|
||||
@ -52,8 +53,8 @@ partitions and possibly at least one more for
|
||||
.Pa /usr/local
|
||||
if you have the space.
|
||||
.Pp
|
||||
This should be done as the HDToolBox manual describes. One thing
|
||||
to note is that if you are not using a Commodore controller you
|
||||
This should be done as the HDToolBox manual describes.
|
||||
One thing to note is that if you are not using a Commodore controller you
|
||||
will need to specify the device your SCSI controller uses, e.g.
|
||||
if you have a Warp Engine you would:
|
||||
.(tag From\ cli -offset indent
|
||||
@ -80,8 +81,8 @@ to boot the installation miniroot directly.
|
||||
.It
|
||||
Changing the file system parameters of the partitions to
|
||||
.Nx
|
||||
ones. This must be done from the
|
||||
partitioning section and
|
||||
ones.
|
||||
This must be done from the partitioning section and
|
||||
.Dq Advanced options
|
||||
must
|
||||
be enabled.
|
||||
@ -175,11 +176,11 @@ installation or upgrade now uses a
|
||||
.Em miniroot
|
||||
file system which is installed on the partition used by
|
||||
.Nx
|
||||
for swapping. This removes the requirement of using a floppy
|
||||
disk for the file system used by the installation or upgrade
|
||||
process. It also allows more utilities to be present on the
|
||||
file system than would be available when using an 880 KB floppy
|
||||
disk.
|
||||
for swapping.
|
||||
This removes the requirement of using a floppy disk for the
|
||||
file system used by the installation or upgrade process.
|
||||
It also allows more utilities to be present on the file system
|
||||
than would be available when using an 880 KB floppy disk.
|
||||
.Pp
|
||||
Once the hard disk has been prepared for
|
||||
.Nx ,
|
||||
@ -187,22 +188,22 @@ the miniroot file system
|
||||
.Pq Pa miniroot.fs
|
||||
is transferred to the swap
|
||||
partition configured during the hard disk prep (or the existing
|
||||
swap partition in the case of an upgrade). The xstreamtodev
|
||||
utility provided in the
|
||||
swap partition in the case of an upgrade).
|
||||
The xstreamtodev utility provided in the
|
||||
.Pa \*M/installation/misc
|
||||
directory can
|
||||
be used on
|
||||
.Tn AmigaDOS
|
||||
to transfer the file system for either a new
|
||||
installation or an upgrade. The file system can also be
|
||||
transferred on an existing
|
||||
installation or an upgrade.
|
||||
The file system can also be transferred on an existing
|
||||
.Nx
|
||||
system for an update by
|
||||
using dd. This should only be done after booting
|
||||
system for an update by using dd.
|
||||
This should only be done after booting
|
||||
.Nx
|
||||
into single-user state. It may also be possible to shutdown
|
||||
to single-user, providing that the single-user state processes
|
||||
are not using the swap partition.
|
||||
into single-user state.
|
||||
It may also be possible to shutdown to single-user, providing that
|
||||
the single-user state processes are not using the swap partition.
|
||||
.Pp
|
||||
On
|
||||
.Tn AmigaDOS ,
|
||||
@ -212,7 +213,8 @@ the command:
|
||||
.Pp
|
||||
where \*<swap partition\*> is the name you gave to the
|
||||
.Nx
|
||||
partition to be used for swapping. If
|
||||
partition to be used for swapping.
|
||||
If
|
||||
.Ic xstreamtodev
|
||||
is unable
|
||||
to determine the SCSI driver device name or the unit number
|
||||
@ -241,8 +243,8 @@ Then copy the miniroot using
|
||||
where
|
||||
.Li /dev/rsd0b
|
||||
should be the device path of the swap partition
|
||||
your system is configured to use. Once the file is copied,
|
||||
reboot back to
|
||||
your system is configured to use.
|
||||
Once the file is copied, reboot back to
|
||||
.Tn AmigaDOS
|
||||
to boot the upgrade kernel.
|
||||
.(tag Caveat:
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
.\" $NetBSD: upgrade,v 1.22 2000/10/29 14:08:05 lukem Exp $
|
||||
.\" $NetBSD: upgrade,v 1.23 2002/06/29 09:36:24 lukem Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1999, 2000 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
|
||||
@ -45,22 +45,25 @@ and you must transfer the miniroot file system
|
||||
.Pa miniroot.fs
|
||||
onto the swap partition of the
|
||||
.Nx
|
||||
hard disk. You must also have at least the
|
||||
hard disk.
|
||||
You must also have at least the
|
||||
.Sy base
|
||||
binary distribution set available, so that you can upgrade
|
||||
with it, 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
|
||||
with it, 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
|
||||
.Pa /
|
||||
(root) and
|
||||
.Pa /usr
|
||||
partitions, you should have enough space.
|
||||
.Pp
|
||||
Since upgrading involves replacing the kernel, and most of the system
|
||||
binaries, it has the potential to cause data loss. You are strongly
|
||||
advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the
|
||||
binaries, it has the potential to cause data loss.
|
||||
You are strongly advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK,
|
||||
whether on the
|
||||
.Nx
|
||||
partition or on another operating system's partition, before
|
||||
beginning the upgrade process.
|
||||
@ -93,8 +96,9 @@ before using loadbsd, else the kernel will hang!
|
||||
.Nx ,
|
||||
with boot blocks installed
|
||||
.(Note
|
||||
This description is for V40 (OS 3.1) ROMs. For older ROMs,
|
||||
there might be small differences. Check your
|
||||
This description is for V40 (OS 3.1) ROMs.
|
||||
For older ROMs, there might be small differences.
|
||||
Check your
|
||||
.Tn AmigaDOS
|
||||
documentation to learn about the exact procedure.
|
||||
Booting using bootblocks doesn't work at all on some systems, and may
|
||||
@ -103,17 +107,20 @@ require a mountable file system on others.
|
||||
.Pp
|
||||
Reboot your machine, holding down both mouse buttons if you
|
||||
have a 2-button mouse, the outer mouse buttons if you have
|
||||
a 3-button mouse. On the DraCo, press the left mouse button
|
||||
instead, when the boot screen prompts you for it.
|
||||
a 3-button mouse.
|
||||
On the DraCo, press the left mouse button instead,
|
||||
when the boot screen prompts you for it.
|
||||
.Pp
|
||||
From the boot menu, select
|
||||
.Ic Boot Options .
|
||||
Select the swap partition with the miniroot, and then
|
||||
.Ic ok . No Select
|
||||
.Ic Boot No now .
|
||||
The machine will boot the bootblock, which
|
||||
will prompt your for a command line. You have a few seconds time
|
||||
to change the default. Entering an empty line will accept the
|
||||
.Ic ok .
|
||||
Select
|
||||
.Ic Boot
|
||||
now.
|
||||
The machine will boot the bootblock, which will prompt your for a command line.
|
||||
You have a few seconds time to change the default.
|
||||
Entering an empty line will accept the
|
||||
default.
|
||||
.Pp
|
||||
The bootblock uses command lines of the form:
|
||||
@ -136,31 +143,34 @@ use
|
||||
.Ss2 Once your kernel boots
|
||||
.
|
||||
You should see the screen clear and some information about
|
||||
your system as the kernel configures the hardware. Note which
|
||||
hard disk device is configured that contains your root
|
||||
your system as the kernel configures the hardware.
|
||||
Note which hard disk device is configured that contains your root
|
||||
.Pq Pa /
|
||||
and swap partitions. When prompted for the root device, type
|
||||
and swap partitions.
|
||||
When prompted for the root device, type
|
||||
.Li sd0b
|
||||
(replacing
|
||||
.Sq Li 0
|
||||
with the disk number that
|
||||
.Nx
|
||||
used for
|
||||
your root/swap device). When prompted for a dump device,
|
||||
answer
|
||||
your root/swap device).
|
||||
When prompted for a dump device, answer
|
||||
.Sq Ic none
|
||||
for the upgrade. (For a normal boot, you would
|
||||
tell it one of the swap devices). When prompted for the root
|
||||
file system type, confirm
|
||||
for the upgrade.
|
||||
(For a normal boot, you would tell it one of the swap devices).
|
||||
When prompted for the root file system type, confirm
|
||||
.Sq Ic generic ,
|
||||
which will auto-detect it.
|
||||
.Pp
|
||||
You will be presented with some information about the upgrade
|
||||
process and a warning message, and will be asked if you wish
|
||||
to proceed with the upgrade process. If you answer
|
||||
negatively, the upgrade process will stop, and your disk will
|
||||
not be modified. If you answer affirmatively, the upgrade
|
||||
process will begin, and your disk will be modified. You may press
|
||||
to proceed with the upgrade process.
|
||||
If you answer negatively, the upgrade process will stop, and your disk will
|
||||
not be modified.
|
||||
If you answer affirmatively, the upgrade process will begin,
|
||||
and your disk will be modified.
|
||||
You may press
|
||||
.Key CONTROL-C
|
||||
to stop the upgrade process at any time.
|
||||
However, if you press it at an inopportune moment, your system
|
||||
@ -171,27 +181,29 @@ potential dangerous procedure and that you should not upgrade the
|
||||
.Sy etc
|
||||
set.
|
||||
.Pp
|
||||
When you decide to proceed, you will be prompted to enter
|
||||
your root disk. After you've done this, it will be checked
|
||||
When you decide to proceed, you will be prompted to enter your root disk.
|
||||
After you've done this, it will be checked
|
||||
automatically to make sure that the file system is in a sane
|
||||
state before making any modifications. After this is done,
|
||||
you will be asked if you want to configure your network.
|
||||
state before making any modifications.
|
||||
After this is done, you will be asked if you want to configure your network.
|
||||
.Pp
|
||||
You are now allowed to edit your fstab. Normally you don't have
|
||||
to. Note that the upgrade-kit uses it's own copy of the fstab.
|
||||
You are now allowed to edit your fstab.
|
||||
Normally you don't have to.
|
||||
Note that the upgrade-kit uses it's own copy of the fstab.
|
||||
Whatever you do here
|
||||
.Em won't
|
||||
affect your actual fstab.
|
||||
After you are satisfied with your fstab, the upgrade-kit will check
|
||||
all file systems mentioned in it. When they're ok, they will be
|
||||
mounted.
|
||||
all file systems mentioned in it.
|
||||
When they're ok, they will be mounted.
|
||||
.Pp
|
||||
You will now be asked if your sets are stored on a normally
|
||||
mounted file system. You should answer
|
||||
mounted file system.
|
||||
You should answer
|
||||
.Sq Ic y
|
||||
to this question if
|
||||
you have the sets stored on a file system that was present in
|
||||
the fstab. The actions you should take for the set extraction
|
||||
you have the sets stored on a file system that was present in the fstab.
|
||||
The actions you should take for the set extraction
|
||||
are pretty logical (we think).
|
||||
.Pp
|
||||
After you have extracted the sets, the upgrade kit will proceed
|
||||
@ -205,8 +217,8 @@ section.
|
||||
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.
|
||||
There are several things that you should do, or might have to
|
||||
do, to insure that the system works properly.
|
||||
.Pp
|
||||
@ -215,7 +227,8 @@ You will probably want to get the
|
||||
distribution,
|
||||
extract it, and compare its contents with those in your
|
||||
.Pa /etc
|
||||
directory. You will probably want to replace some of your
|
||||
directory.
|
||||
You will probably want to replace some of your
|
||||
system configuration files, or incorporate some of the changes
|
||||
in the new versions into yours.
|
||||
.Pp
|
||||
@ -225,14 +238,16 @@ of the version of
|
||||
that you upgraded from and have since
|
||||
been removed from the
|
||||
.Nx
|
||||
distribution. If upgrading from a
|
||||
distribution.
|
||||
If upgrading from a
|
||||
.Nx
|
||||
version older than 1.0, you might also want to
|
||||
recompile any locally-built binaries, to take advantage of the
|
||||
shared libraries. (Note that any new binaries that you build
|
||||
shared libraries.
|
||||
(Note that any new binaries that you build
|
||||
will be dynamically linked, and therefore take advantage of
|
||||
the shared libraries, by default. For information on how to
|
||||
make statically linked binaries, see the
|
||||
the shared libraries, by default.
|
||||
For information on how to make statically linked binaries, see the
|
||||
.Xr cc 1
|
||||
and
|
||||
.Xr ld 1
|
||||
|
||||
Loading…
Reference in New Issue
Block a user