NetBSD/distrib/notes/mac68k/upgrade

264 lines
8.0 KiB
Plaintext
Raw Normal View History

2002-06-30 03:54:05 +04:00
.\" $NetBSD: upgrade,v 1.19 2002/06/29 23:54:05 lukem Exp $
1999-01-13 10:30:01 +03:00
.\"
2002-06-30 03:54:05 +04:00
.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
1999-01-13 10:30:01 +03:00
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
The upgrade to
.Nx \*V
is a binary upgrade; it can be quite difficult
to advance to a later version by recompiling from source due primarily
to interdependencies in the various components.
1999-01-13 10:30:01 +03:00
.Pp
No automated upgrade procedure exists for upgrading to release \*V for the
.Nx*M
2002-06-30 03:54:05 +04:00
architecture.
The current procedure is essentially to perform a new install from scratch.
It is hoped that there will be a good upgrade procedure for future releases.
Please feel free to volunteer to help replace these installation tools.
1999-01-13 10:30:01 +03:00
.Pp
2002-06-30 03:54:05 +04:00
The following steps outline the current upgrade procedure.
These steps should help ease the upgrade process.
Please read these instructions carefully and completely before proceeding.
.(enum
1999-01-13 10:30:01 +03:00
Since upgrading involves replacing the kernel and most of the system
2002-06-30 03:54:05 +04:00
binaries, it has the potential to cause data loss.
You are strongly advised to
1999-01-13 10:30:01 +03:00
.Em back up any important data on your disk,
whether on the
.Nx
partition or on another operating system's partition, before
2002-06-30 03:54:05 +04:00
beginning the upgrade process.
Although the upgrade should not damage your file system(s) in any way,
you never know what may happen.
1999-01-13 10:30:01 +03:00
.It
Download the distribution sets you want from the
.Pa \*M/binary/sets
1999-01-13 10:30:01 +03:00
subdirectory of the
.Nx \*V
2002-06-30 03:54:05 +04:00
distribution.
You will need the base set and the kernel at a minimum.
Be sure to download the files in
1999-01-13 10:30:01 +03:00
.Em binary
2002-06-30 03:54:05 +04:00
mode.
If you will be upgrading from within
.Nx ,
make sure
that you place the distribution sets on a file system you will be able to
1999-01-13 10:30:01 +03:00
reach from single-user mode.
.It
2002-06-30 03:54:05 +04:00
Install the \*V kernel.
You may either use the Installer utility
(included in the
1999-01-13 10:30:01 +03:00
.Pa installation/misc
subdirectory) or install from within
.Nx
2002-06-30 03:54:05 +04:00
(the latter is recommended for speed reasons).
If you choose the former, proceed as you normally would.
If you choose to install from within
.Nx ,
then boot (or shutdown) into single-user
1999-01-13 10:30:01 +03:00
mode and do the following:
.Pp
.Dl # Ic "cd /"
.Dl # Ic "pax -zrvpe -f /path/to/kern.tgz"
.Pp
1999-01-13 10:30:01 +03:00
There is no need to backup your old kernel explicitly since it will be
incapable of running many of the newer binaries you are about to
2002-06-30 03:54:05 +04:00
install.
(Unless, of course, you have a backup copy of your older
binaries and want to revert to them for some reason.)
However, you might want to keep a backup if you are upgrading from within
1999-01-13 10:30:01 +03:00
.Nx
just in case the newer kernel has trouble booting your machine.
1999-01-13 10:30:01 +03:00
.It
2002-06-30 03:54:05 +04:00
If you are installing using the Installer, skip to step 5.
Otherwise, reboot into
1999-01-13 10:30:01 +03:00
.Nx
2002-06-30 03:54:05 +04:00
in single-user mode.
Run
1999-01-13 10:30:01 +03:00
.Ic fsck Fl f
and then mount all
2002-06-30 03:54:05 +04:00
local partitions read/write.
Usually
1999-01-13 10:30:01 +03:00
.Ic mount Fl a t Ic nonfs
should do the
trick, but if you have several partitions on the same disk, take note of
the fact that a change in partition numbering may have moved a few of
2002-06-30 03:54:05 +04:00
your partitions around.
You can do a
1999-01-13 10:30:01 +03:00
.Ic disklabel sd Ns Ar X
(where
.Ar X
is a
drive on which you have
.Nx
partitions) to see how the partitions are
2002-06-30 03:54:05 +04:00
currently laid out.
It is likely that a partition has shifted into the
.Li sd Ns Ar X Ns Li d
1999-01-13 10:30:01 +03:00
or
.Li sd Ns Ar X Ns Li e
1999-01-13 10:30:01 +03:00
slots, slots that often were not available under
previous releases of
.Nx .
If this is the case, you will need to
manually mount your root partition
.Pq Pa /
via
.Ic "mount -w /"
1999-01-13 10:30:01 +03:00
and edit your
.Pa /etc/fstab
2002-06-30 03:54:05 +04:00
file to reflect the new partition layout.
Unless you are familiar with
1999-01-13 10:30:01 +03:00
.Xr ex 1
or
.Xr ed 1 .
the easiest way to fix your
.Pa /etc/fstab
file
is probably to simply do a
.Ic "cat \*> /etc/fstab"
1999-01-13 10:30:01 +03:00
and type in the corrected file in its entirety.
.It
2002-06-30 03:54:05 +04:00
Install the distribution sets.
Keep in mind that the
1999-01-13 10:30:01 +03:00
.Nx \*V
distribution takes up a considerably larger amount of disk space than
2002-06-30 03:54:05 +04:00
did the 1.3 family of distributions.
If you are using the Installer, proceed normally
(remember that you will need to mount non-root partitions by hand using
the MiniShell before installing).
If you are installing from within
.Nx ,
do the following:
.Pp
.Dl # Ic "cd /"
.Dl # Ic "pax -zrvpe -f /path/to/base.tgz"
1999-01-13 10:30:01 +03:00
.Pp
Keep in mind that there is
1999-01-13 10:30:01 +03:00
no going back once you have installed the base set short of a complete
2002-06-30 03:54:05 +04:00
re-install of an earlier distribution.
Continue with the appropriate command line for each of the other sets
you wish to install except for the
.Sy etc
set.
If you are in the Installer, open up the Minishell and do the following:
.Pp
.Dl Ic "cd /tmp"
.Dl Ic "exit"
.Pp
2002-06-30 03:54:05 +04:00
Ignore the warning message this will cause.
Now, use the Installer to install the
.Sy etc
set (it will install into
.Pa /tmp
instead of the
.Pa /etc
directory).
.Pp
If you are in
.Nx ,
do the following instead:
1999-01-13 10:30:01 +03:00
.Pp
.Dl # Ic "cd /tmp"
.Dl # Ic "pax -zrvpe -f /path/to/etc.tgz"
1999-01-13 10:30:01 +03:00
.It
If you are in the Installer, quit it and boot into
.Nx
2002-06-30 03:54:05 +04:00
in single-user mode.
From there,
.Ic cd
to the
.Pa /tmp/etc
directory and compare each file there with your old files in
1999-01-13 10:30:01 +03:00
.Pa /etc .
You will probably want to replace
some of your system configuration files, or incorporate some of the
2002-06-30 03:54:05 +04:00
changes in the new versions into yours.
You should take note of the following when upgrading to the
1999-01-13 10:30:01 +03:00
.Nx \*V
etc.tgz set:
.(bullet
1999-01-13 10:30:01 +03:00
Several of the options given to many of the file systems have changed,
and some of the file systems have changed names.
.(Note
It is imperative that you change any instances of
.Sy ufs
.Pa /etc/fstab
to
.Sy ffs .
.Note)
1999-01-13 10:30:01 +03:00
To find out
more about different file system options, read the man page for the
associated
.Ic mount
command (e.g.
1999-01-13 10:30:01 +03:00
.Xr mount_mfs 8
for MFS file systems; note:
FFS type file systems are documented in the
1999-01-13 10:30:01 +03:00
.Xr mount 8
2002-06-30 03:54:05 +04:00
man page).
If you have not already done so, you may also need to correct
1999-01-13 10:30:01 +03:00
.Pa /etc/fstab
2002-06-30 03:54:05 +04:00
for a shift in the partition numbering scheme.
See step 4 above for more details.
1999-01-13 10:30:01 +03:00
.It
2002-06-30 03:54:05 +04:00
You will also probably want to upgrade your device nodes at this time as well.
Make sure you have installed the latest MAKEDEV script
(it should be included in the etc set) and perform the following commands:
.Pp
.Dl # Ic "cd /dev"
.Dl # Ic "sh MAKEDEV all"
.bullet)
1999-01-13 10:30:01 +03:00
.It
Run
.Ic fsck Fl f
2002-06-30 03:54:05 +04:00
to make sure that your file system is still consistent.
If fsck reports any errors, fix them by answering
.Sq Ic y
1999-01-13 10:30:01 +03:00
to its suggested
solutions
.(Note
If there are a large number of errors, you may wish
to stop and run
1999-01-13 10:30:01 +03:00
.Ic fsck Fl fy
to automatically answer
.Ic yes
instead.
.Note)
1999-01-13 10:30:01 +03:00
.It
Exit from single-user mode and it should continue to boot into
multi-user mode.
.enum)
1999-01-13 10:30:01 +03:00
.Pp
At this point you have successfully upgraded to
.Nx \*V .