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

Initial updates to document install and upgrades using the MI miniroot.

Browse Source 
Update revision numbers for 1.3.
This commit is contained in:
mhitch 1997-10-31 21:15:46 +00:00
parent 4dcb8c7d34
commit 6d3db8915a
5 changed files with 144 additions and 401 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

61
distrib/notes/amiga/contents
View File

@ -1,15 +1,15 @@
[ XXX file sizes need to be upgraded in this section ]
The Amiga-specific portion of the NetBSD 1.2 release is found in the
"amiga" subdirectory of the distribution. That subdirectory is layed
The Amiga-specific portion of the NetBSD _VER release is found in the
"amiga" subdirectory of the distribution. That subdirectory is laid
out as follows:
.../NetBSD-1.2/amiga/
.../NetBSD-_VER/amiga/
binary/ Amiga binary distribution sets;
see below.
miniroot/ Amiga installation and upgrade
file system images; see below.
miniroot/ Amiga miniroot file system
image; see below.
security/ Amiga security distribution;
see below;
@ -18,17 +18,16 @@ out as follows:
installation utilities; see
installation section, below.
There are two Amiga file system images to be found in the "amiga/miniroot"
subdirectory of the NetBSD 1.2 distribution. One of them is a upgrade
image and one is an installation image. They are described in more
detail below. There are gzipped versions of each available, for easier
The Amiga now uses a single miniroot filesystem for both an initial
installation and for an upgrade. A gzipped version is available, for easier
downloading. (The gzipped version have the ".gz" extension added to
their names.)
Installation file system:
Miniroot file system:
This file contains a BSD root file system setup to help
you install the rest of NetBSD. This includes formatting
you install the rest of NetBSD or to upgrade a previous version of
NetBSD. This includes formatting
and mounting your root and /usr partitions and getting
ready to extract (and possibly first fetching) the distribution
sets. There is enough on this file system to allow you to
@ -36,31 +35,15 @@ Installation file system:
NFS file system or ftp. You can also load distribution sets from
a SCSI tape or from one of your existing AmigaDOS partitions.
This file is named "inst-12.fs".
Upgrade file system:
This file contains a BSD root file system setup to help
you upgrade a previous version of NetBSD. This includes
converting existing partitions and mounting your root and
/usr partitions and getting ready to extract (and possibly
first fetching) the distribution sets. There is enough on
this file system to allow you to make a SLIP or PPP connection,
configure an Ethernet, mount an NFS file system or ftp.
You can also load distribution sets from a SCSI tape, from
one of your existing AmigaDOS partitions, or from an existing
NetBSD partition.
This file is named "upgr-12.fs".
This file is named "miniroot-13.fs".
The NetBSD/Amiga binary distribution sets contain the binaries which
comprise the NetBSD 1.2 release for the Amiga. There are seven binary
comprise the NetBSD _VER release for the Amiga. There are seven binary
distribution sets, and the "security" distribution set. The binary
distribution sets can be found in subdirectories of the "amiga/binary"
subdirectory of the NetBSD 1.2 distribution tree, and are as follows:
subdirectory of the NetBSD _VER distribution tree, and are as follows:
base12 The NetBSD/Amiga 1.2 base binary distribution. You
base13 The NetBSD/Amiga _VER base binary distribution. You
MUST install this distribution set. It contains the
base NetBSD utilities that are necessary for the
system to run and be minimally functional. It
@ -68,7 +51,7 @@ subdirectory of the NetBSD 1.2 distribution tree, and are as follows:
everything described below.
[ 8M gzipped, 20M uncompressed ]
comp12 The NetBSD/Amiga Compiler tools. All of the tools
comp13 The NetBSD/Amiga Compiler tools. All of the tools
relating to C, C++, and FORTRAN (yes, there are two!).
This set includes the system include files
(/usr/include), the linker, the compiler tool chain,
@ -79,7 +62,7 @@ subdirectory of the NetBSD 1.2 distribution tree, and are as follows:
call and library manual pages.
[ 6M gzipped, 15M uncompressed ]
etc12 This distribution set contains the system
etc13 This distribution set contains the system
configuration files that reside in /etc and in several
other places. This set MUST be installed if you are
installing the system from scratch, but should NOT be
@ -88,28 +71,28 @@ subdirectory of the NetBSD 1.2 distribution tree, and are as follows:
CAREFULLY upgrade your configuration files by hand.)
[ 77K gzipped, 340K uncompressed ]
games12 This set includes the games and their manual pages.
games13 This set includes the games and their manual pages.
[ 3M gzipped, 7M uncompressed ]
man12 This set includes all of the manual pages for the
man13 This set includes all of the manual pages for the
binaries and other software contained in the base set.
Note that it does not include any of the manual pages
that are included in the other sets.
[ 1M gzipped, 3M uncompressed ]
misc12 This set includes the system dictionaries (which are
misc13 This set includes the system dictionaries (which are
rather large), the typesettable document set, and
man pages for other architectures which happen to be
installed from the source tree by default.
[ 2M gzipped, 7M uncompressed ]
text12 This set includes NetBSD's text processing tools,
text13 This set includes NetBSD's text processing tools,
including groff, all related programs, and their
manual pages.
[ 900K gzipped, 3M uncompressed ]
The Amiga security distribution set is named "secr12" and can be found
in the "amiga/security" subdirectory of the NetBSD 1.2 distribution
The Amiga security distribution set is named "secr13" and can be found
in the "amiga/security" subdirectory of the NetBSD _VER distribution
tree. It contains crypt.c (the source file for the DES encryption
algorithm) and the binaries which depend on it. It can only be found
on those sites which carry the complete NetBSD distribution and that

300
distrib/notes/amiga/install
View File

@ -11,9 +11,9 @@ installed on your hard disk. If you wish to stop the installation,
you may hit Control-C at any prompt, but if you do, you'll have to
begin again from scratch.
Transfer the install miniroot file system onto the hard disk
partition used by NetBSD for swapping, as described in the
"Preparing your System for NetBSD Installation" section above.
Transfer the miniroot file system onto the hard disk partition
used by NetBSD for swapping, as described in the "Preparing
your System for NetBSD Installation" section above.
* Booting from AmigaOS, using loadbsd:
@ -43,6 +43,9 @@ begin again from scratch.
there might be small differences. Check your AmigaOS documentation
to learn about the exact procedure.]
[XXX should note someplace that using bootblocks may not work on some
systems, and may require a mountable filesystem on others?]
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
@ -80,32 +83,41 @@ begin again from scratch.
This disables synchronous transfer on all SCSI devices.
The system should continue to boot. For now ignore WARNING:
messages about bad dates in clocks. Eventually you will be
asked to enter the pathname of the shell, just hit return.
After a short while you should see a welcome message and a
prompt, asking if you wish to proceed with the installation.
messages about bad dates in clocks, and a warning about /etc/rc
not existing. Eventually you will be be asked to enter the
pathname of the shell, just hit return. 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 'install' section, 'i' would be the proper
response here...
If you wish to proceed, enter "y" and then return.
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 'y'. 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.
If you have configured your hard drive[s] correctly it
should find the drive and partition that you selected to
use as your root. You will be prompted for which device
you want to use for your root. If you have multiple disks
present with root partitions defined, you will need to be
sure you enter the device name of the correct partition you
want to install NetBSD on.
You should know at this point that the disks are NOT numbered
according to their scsi-id! The NetBSD 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 sd0,
the next one sd1, etc. Also, any Amiga internal IDE disk drives
will be configured as "SCSI" drives, and will be configured
before any 'real' SCSI drives (if any are present).
YOU ARE NOW AT THE POINT OF NO RETURN. If you confirm that
you want to install NetBSD, your hard drive will be modified,
and perhaps its contents scrambled at the whim of the install
program.
program. Type Control-C NOW if you don't want this.
If you are sure you want to proceed, enter "yes" at the
prompt.
At this time, you will need to tell the installer which partition
will be associated with the different filesystems.
The install program will now make the root file system you
specified. There should be only one error in this section
of the installation. It will look like so:
The install program will now make the the file systems you
specified. There should be only one error per file system in
this section of the installation. It will look like so:
newfs: ioctl (WDINFO): Invalid argument
newfs: /dev/rsd0a: can't rewrite disk label
@ -115,223 +127,40 @@ begin again from scratch.
does not write disklabels currently. You should expect
this error whenever using newfs.
Next the install program will ask you which drive and
partition you wish to use as /usr. First it will list the
available drives. Choose one. Next it will give you a
list of the partitions on that disk along with their sizes,
types, etc.. Choose the letter that corresponds to the
partition you wish to use for /usr. If you are doing a
full install this should be at the very least 45M-50M large.
If everything is ok the install program will then format
and mount your /usr. If not then it will ask again for a
drive and partition.
The install will now ask you want to configure any network
information. It ill ask for the machine's host name, domain
name, and other network configuration information.
When this completes your root partition will be mounted on
/mnt and your /usr partition on /mnt/usr. An fstab will
have been created and initialized to correctly mount these
two file systems. This fstab will be in /mnt/etc.
Since the network configuration might have lead to additional (nfs)
filesystem entries, you get another chance to modify your fstab.
What you do from this point on depends on which media you're
using to install NetBSD. Follow the appropriate instructions,
given below.
Your are finally at the point where some real data will be put on
your freshly made filesystems. Select the device type you wish
to install from and off you go....
Some notes:
- If you want to install from tape, please read the section
about how to create such a tape.
- Install at least the base and etc sets.
- If you have to specify a path relative to the mount-point and
you need the mount-point itself, enter '.'.
To install from an AmigaDOS partition:
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 filesystem. After the timezone-link is installed,
the installer will proceed by creating the device nodes on your
root filesystem.
You first need to mount the AmigaDOS partition
using the mount_ados command. If e.g. your AmigaDOS
partition is the first partition on sd0 you could
type:
mkdir /mnt/ados
mount_ados -o ro /dev/sd0d /mnt/ados
Be patient, this will take a while...
You can use `disklabel sd0' to find out what types
of partitions are on the disk `sd0'.
Next goto the directory in which you stored the
distribution sets. If e.g. you stored them in the
root directory of the partition:
cd /mnt/ados
When there, run "Set_tmp_dir" and choose the default
temporary directory, by hitting return at the
prompt.
Run the "Extract" command, giving it as its sole
argument the name of the distribution set you wish
to extract. For example, to extract the base
distribution, use the command:
Extract base12
and to extract the games distribution:
Extract game12
If the distribution sets are in different directories,
you will need to cd to each directory in turn, running
"Set_tmp_dir" and the appropriate "Extract" command(s).
Continue this process until you've finished installing
all of the sets which you desire to have on your
hard disk. Once you have extracted all sets and
are at the "#" prompt again, proceed to the section
"Configuring Your System," below.
To install from tape:
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, use the command "Set_tmp_dir" and enter
your choice. The default is /mnt/usr/distrib.
After you have picked a temporary directory,
you should issue the load command:
Load_tape
Next, you will be told to insert the media into
the appropriate drive, and hit return. Continue
to follow instructions until you are returned to
the "#" prompt.
Go to the directory which contains the first
distribution set you wish to install. This is
either the directory you specified above, or possibly
a subdirectory of that directory.
When there, run "Set_tmp_dir" again, and choose
the default temporary directory, by hitting
return at the prompt.
Run the "Extract" command, giving it as its sole
argument the name of the distribution set you
wish to extract. For example, to extract the base
distribution, use the command:
Extract base12
and to extract the games distribution:
Extract game12
After the extraction is complete, go to the location
of the next set you want to extract, "Set_tmp_dir"
again, and once again issue the appropriate
extract command. Continue this process until
you've finished installing all of the sets which you
desire to have on your hard disk.
After each set is finished, if you know that you
are running low on space you can remove the
distribution files for that set by saying:
rm set_name.??
For example, if you wish to remove the distribution
files for the game09 set, after the "Extract game09"
command has completed, issue the command:
rm game12.??
Once you have extracted all sets and are at the "#" prompt
again, proceed to the section "Configuring Your System,"
below.
To install via FTP or NFS:
First, use Set_tmp_dir to pick a temporary directory
for the installation files. /mnt/usr/distrib is
suggested.
Configure the appropriate Ethernet interface i.e. le0
if you have a 2065 or ed0 if you have a AMIGNET from
Hydra Systems.
ifconfig <ifname> <ipaddr> [netmask <netmask>]
where <ifname> is the interface name (e.g. ed0, etc.),
and <ipaddr> is the numeric IP address of the interface.
If the interface has a special netmask, supply
the word "netmask" and that netmask at the end of the
command line. For instance, without a special netmask:
ifconfig ed0 129.133.10.10
or with a special netmask
ifconfig ed0 128.32.240.167 netmask 0xffffff00
You should also be able to use SLIP or PPP as the network
connection.
[XXX instructions for ppp or slip would be usefull
perhaps the next release]
If the NFS server or FTP server is not on a directly-
connected network, you should set up a route to it
with the command:
route add default <gate_ipaddr>
where <gate_ipaddr> is your gateway's numeric IP address.
If you are NFS-mounting the distribution sets,
mount them on the temporary directory with the command:
mount -t nfs <serv_ipaddr>:<dist_dir> <tmp_dir>
where <serv_ipaddr> is the server's numeric IP address,
<dist_dir> is the path to the distribution files on
the server, and <tmp_dir> is the name of the local
temporary directory.
Once this is done, proceed as if you had loaded the
files from tape, "cd"ing to the appropriate directories
and running "Set_tmp_dir" and "Extract" as appropriate.
If you are retrieving the distribution sets using ftp,
cd into the temp directory, and execute the command:
ftp <serv_ipaddr>
where <serv_ipaddr> is once again the server's
numeric IP address. Get the files with FTP,
taking care to use binary mode to transfer
all files.
Once you have all of the files for the distribution sets
you wish to install, you can proceed using the instructions
above as if you had installed the files from a tape.
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 NetBSD system. See the 'installboot(8)'
manual page about how to do this.
Configuring Your System:
----------- ---- ------
Once you have finished extracting all of the distribution sets that
you want on your hard drive and are back at the "#" prompt,
you are ready to configure your system.
The configuration utility expects that you have installed the base
system. If you have not, you will not be able to run it successfully
(nor will you have a functional system regardless of configuration).
To configure the newly installed operating system, run the
command "Configure".
Configure will ask for the machine's host name, domain name, and other
network configuration information.
Once you have supplied `Configure' all that it requests, your machine
will be configured well enough that when you reboot it it will
almost be a completely functional NetBSD system.
Configure will also copy the generic kernel from the miniroot onto your
root partition, and will install a bootblock.
Once you are done with `Configure', halt the system with the "halt"
command (wait for "halted" to be displayed) and reboot. Then again
boot NetBSD this time with the command:
Once the installer is done, halt the system with the "halt" command
(wait for "halted" to be displayed) and reboot. Then again boot
NetBSD this time with the command:
loadbsd netbsd
@ -351,15 +180,6 @@ These things can be found in /etc/netstart. Use vi, if you installed
the man pages you can type `man vi' or `man ed' for instructions
on how to use these somewhat non-intuitive editors.
You should also put a copy of the netbsd kernel in your root partition.
This can be done easily by mounting the AmigaDOS partition containing
the kernel you used to start NetBSD and copying the "netbsd" file to
the root:
mount -r -t ados /dev/sd0d /mnt
cp /mnt/netbsd /
(where /dev/sd0d is the AmigaDOS partition where you have netbsd, and
/mnt/netbsd is the appropriate path of the netbsd file).
Once you are done with the rest of configuration unmount your file
systems and halt your system, then reboot:

51
distrib/notes/amiga/prep
View File

@ -20,10 +20,7 @@ Preparing you hard disk with HDToolBox:
What you need to do is partition your drives; creating at least
root, swap and /usr partitions and possibly at least one more for
/local if you have the space. (The root and swap partitions must
be on the same drive for your initial installation. You can use
other configurations after building a customized kernel once your
system is running.)
/local if you have the space.
This should be done as the HDToolBox manual describes. One thing
to note is that if you are not using a Commodore controller you
@ -82,10 +79,6 @@ Preparing you hard disk with HDToolBox:
Mask and maxtransfer are not used with NetBSD.
Until you compile your own kernel your swap partition
must exist on the drive that also holds your root
partition.
Once this is done NetBSD/Amiga will be able to recognize your
disks and which partitions it should use.
@ -100,36 +93,32 @@ Transferring the miniroot file system:
file system than would be available when using an 880K floppy
disk.
Once the hard disk has been prepared for NetBSD, the appropriate
miniroot file system (inst-12.fs for a new install or upgr-12.fs
for an upgrade) 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 "amiga/utilities" directory can be used on AmigaDOS to
transfer the file system for either a new installation or an
upgrade. The file system can also be transferred on an existing
NetBSD system for an update by using dd. This should only be
done after booting NetBSD 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.
Once the hard disk has been prepared for NetBSD, the miniroot
file system (miniroot-13.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 "amiga/utilities" directory can be used
on AmigaDOS to transfer the file system for either a new
installation or an upgrade. The file system can also be
transferred on an existing NetBSD system for an update by
using dd. This should only be done after booting NetBSD
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.
On AmigaDOS, the command:
xstreamtodev --input=inst-12.fs --rdb-name=<swap partition>
xstreamtodev --input=miniroot-13.fs --rdb-name=<swap partition>
where <swap partition> is the name you gave to the NetBSD
partition to be used for swapping. Use upgr-12.fs if you
are going to do an upgrade of an existing NetBSD system. If
xstreamtodev is unable to determine the SCSI driver device
name or the unit number of the specified partition, you may
also need to include the option "--device=<driver.name>" and/or
"--unit=<SCSI unit number>".
partition to be used for swapping. If xstreamtodev is unable
to determine the SCSI driver device name or the unit number
of the specified partition, you may also need to include the
option "--device=<driver.name>" and/or "--unit=<SCSI unit number>".
To transfer the miniroot using NetBSD, you should be booted up
in single user state on the current NetBSD system, or use the
"shutdown now" command to shutdown to single-user state. Then
copy the miniroot using dd:
dd if=upgr-12.fs of=/dev/rsd0b
dd if=miniroot-13.fs of=/dev/rsd0b
where /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 AmigaDOS to boot the upgrade kernel. NOTE: the
release kernel is a "generic" kernel, and requires that the
swap partition be on the same device as the root partition.
reboot back to AmigaDOS to boot the upgrade kernel.

122
distrib/notes/amiga/upgrade
View File

@ -1,14 +1,14 @@
The upgrade to NetBSD 1.2 is a binary upgrade; it would be prohibitive
to make users upgrade by compiling and installing the 1.2 sources, and
The upgrade to NetBSD _VER is a binary upgrade; it would be prohibitive
to make users upgrade by compiling and installing the _VER sources, and
it would be very difficult to even compile a set of instructions that
allowed them to do so. Because of the various changes to the system,
it is impractical to upgrade by recompiling from the sources and
installing.
To do the upgrade, you must have the NetBSD kernel on AmigaDOS and
you must transfer the upgrade file system upgr-12.fs onto the swap
you must transfer the miniroot file system miniroot-13.fs onto the swap
partition of the NetBSD hard disk. You must also have at least the
"base12" binary distribution set available, so that you can upgrade
"base13" 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,
@ -24,11 +24,11 @@ beginning the upgrade process.
To upgrade your system, follow the following instructions:
Transfer the upgrade miniroot file system onto the hard disk
partition used by NetBSD for swapping, as described in the
"Preparing your System for NetBSD Installation" section above.
Transfer the miniroot file system onto the hard disk partition
used by NetBSD for swapping, as described in the "Preparing
your System for NetBSD Installation" section above.
Now boot up NetBSD using the 1.2 kernel using the loadbsd
Now boot up NetBSD using the _VER kernel using the loadbsd
command:
loadbsd -b netbsd
@ -44,6 +44,8 @@ To upgrade your system, follow the following instructions:
there might be small differences. Check your AmigaOS documentation
to learn about the exact procedure.]
[XXX another note about bootblock support?]
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
@ -84,99 +86,49 @@ To upgrade your system, follow the following instructions:
However, if you hit it at an inopportune moment, your system
may be left in an inconsistent (and possibly unusable) state.
You will be asked if you wish to upgrade your file systems to
the new file system format. If you do, reply affirmatively.
If you don't have your file systems upgraded now, you should
probably do it manually after the install process is complete,
by using "fsck -c 2". Read the fsck(8) manual page for more
details.
You will now be greeted and reminded of the fact that this is a
potential dangerous procedure and that you should not upgrade the
etc-set.
The upgrade program will then check your root file system,
and, if you approved, will upgrade it to the new file system
format. It will then mount your root file system on /mnt.
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 filesystem is in a sane
state before making any modifications. After this is done,
you will be asked if you want to configure your network.
If your file systems are being upgraded, the upgrade script
will copy the new fsck(8) program to your hard disk and
upgrade your remaining file systems.
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 *won't* affect your actual fstab.
After you are satisfied with your fstab, the upgrade-kit will check
all filesystems mentioned in it. When they're ok, they will be
mounted.
The upgrade program will then mount all of your file systems
under /mnt. (In other words, your root partition will be
mounted on /mnt, your /usr partition on /mnt/usr, etc.)
You will now be asked if your sets are stored on a normally
mounted filesystem. You should answer 'y' to this question if
you have the sets stored on a filesystem that was present in
the fstab. The actions you should take for the set extraction
are pretty logical (I think).
If you don't already have the NetBSD distribution sets on your
disk, look in the installation section for information on how
to transfer them to your disk.
After you have extracted the sets, the upgrade kit will proceed
with setting the timezone and installing the kernel and bootcode.
This is all exactly the same as described in the installation
section.
Once the distribution sets are transferred to your disk,
continue here. (Obviously, if the NetBSD distribution sets
are already on your disk, because you've transferred them
before starting the upgrade process, you don't need to
transfer them again now!)
After the software has been transferred to the machine (or
mounted, in the case of upgrading via NFS), change into the
directory containing the "base12" distribution set. Once you
are there, run the "Set_tmp_dir" command, and hit return at
the prompt to select the default answer for the temporary
directory's path name. (It should be the path name of the
directory that you're in.)
Run the command "Extract base12" to upgrade the base
distribution.
Repeat the above two steps for all of the sets you wish to
upgrade. (For each, change into the directory containing the
set, run "Set_tmp_dir" and accept the default path name, then
run the "Extract <setname>" command.)
If you were previously using the security distribution set,
you MUST upgrade to the new version, or you will not be able
to log in when the upgrade process is complete. Similarly, if
you were not previously using the security set, you must NOT
upgrade to the new version.
When you are done upgrading all of the distribution sets you
wish to upgrade, issue the command "Cleanup". It will clean
up the installation, by remaking some system databases, and
install the kernel and a bootblock onto the root partition.
When it is complete, you should use "halt" to halt the system.
Your system has now been upgraded to NetBSD 1.2.
Your system has now been upgraded to NetBSD _VER.
After a new kernel has been copied to your hard disk, your
machine is a complete NetBSD 1.2 system. However, that
machine is a complete NetBSD _VER 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.
First, if you did not upgrade your file systems to the new
file system format during the upgrade process, you may want to
do so now, with "fsck -c 2". If you are unsure about the
process, it's suggested that you read the fsck(8) manual page.
Second, you will probably want to get the etc12 distribution,
You will probably want to get the etc13 distribution,
extract it, and compare its contents with those in your /etc/
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.
Third, you will probably want to update the set of device
nodes you have in /dev. If you've changed the contents of
/dev by hand, you will need to be careful about this, but if
not, you can just cd into /dev, and run the command "sh
MAKEDEV all".
Fourth, you must 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
/etc/fstab or by hand 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 mount_nfs(8) for NFS.
(Note that the information for mounts of type "ffs", i.e. Fast
File Systems, are contained in the mount_ffs(8) man page.)
Finally, you will want to delete old binaries that were part
You will want to delete old binaries that were part
of the version of NetBSD that you upgraded from and have since
been removed from the NetBSD distribution. If upgrading from
a NetBSD version older than 1.0, you might also want to

11
distrib/notes/amiga/xfer
View File

@ -5,11 +5,10 @@ Installation is supported from several media types, including:
FTP
NetBSD partitions, if doing an upgrade.
The install or upgrade miniroot file system needs to be transferred
to the NetBSD swap partition. This can be done from AmigaDOS in
the case of a new install or upgrade, or from NetBSD when doing an
upgrade. See the "Preparing your System for NetBSD Installation"
section for details.
The miniroot file system needs to be transferred to the NetBSD swap
partition. This can be done from AmigaDOS in the case of a new
install or upgrade, or from NetBSD when doing an upgrade. See the
"Preparing your System for NetBSD Installation" section for details.
The steps necessary to prepare the distribution sets
for installation depend on which method of installation
@ -102,7 +101,7 @@ following:
Place the distribution sets you wish to upgrade somewhere in
your current file system tree. At a bare minimum, you must
upgrade the "base" binary distribution, and so must put the
"base11" set somewhere in your file system. If you wish,
"base13" set somewhere in your file system. If you wish,
you can do the other sets, as well, but you should NOT upgrade
the "etc" distribution; the "etc" distribution contains system
configuration files that you should review and update by hand.