summaryrefslogtreecommitdiff
path: root/distrib/notes/hp300/upgrade
diff options
context:
space:
mode:
Diffstat (limited to 'distrib/notes/hp300/upgrade')
-rw-r--r--distrib/notes/hp300/upgrade93
1 files changed, 92 insertions, 1 deletions
diff --git a/distrib/notes/hp300/upgrade b/distrib/notes/hp300/upgrade
index 25bcdb9f97c..aa51832ae4e 100644
--- a/distrib/notes/hp300/upgrade
+++ b/distrib/notes/hp300/upgrade
@@ -1 +1,92 @@
-There is no previous release of NetBSD/hp300 to upgrade.
+It is possible to easily upgrade your existing NetBSD/hp300 system
+using the upgrade program in the miniroot. If you wish to upgrade
+your system by this method, simply select the `upgrade' option once
+the miniroot has booted. The upgrade program with then guide you
+through the procedure. The upgrade program will:
+
+ * Enable the network based on your system's current
+ network configuration.
+
+ * Mount your existing filesystems.
+
+ * Extract binary sets from the media of your choice.
+
+ * Fixup your system's existing /etc/fstab, changing the
+ occurrences of `ufs' to `ffs' and let you edit the
+ resulting file.
+
+ * Make new device nodes in your root filesystem.
+
+ * Copy a new kernel onto your root partition.
+ NOTE: the existing kernel WILL NOT be backed up; doing
+ so would be pointless, since a NetBSD 1.0 kernel will
+ not run NetBSD 1.1 executables.
+
+ * Install a new boot block.
+
+ * Check your filesystems for integrity.
+
+While using the miniroot's upgrade program is the preferred method
+of upgrading your system, it is possible to upgrade your system
+manually. To do this, follow the following procedure:
+
+ * Place _at least_ the `base' binary set in a filesystem
+ accessible to the target machine. A local filesystem
+ is preferred, since there may be incompatibilities
+ between the NetBSD 1.1 kernel and older route(8)
+ binaries.
+
+ * Back up your pre-existing kernel and copy the 1.1
+ kernel into your root partition.
+
+ * Reboot with the 1.1 kernel into single-user mode.
+
+ * Check all filesystems:
+
+ /sbin/fsck -p
+
+ * Mount all local filesystems:
+
+ /sbin/mount -a -t nonfs
+
+ * If you keep /usr or /usr/share on an NFS server, you
+ will want to mount those filesystems as well. To do
+ this, you will need to enable the network:
+
+ sh /etc/netstart
+
+ NOTE: the route(8) commands may fail due to potential
+ incompatibilities between route(8) and the NetBSD 1.1
+ kernel. Once you have enabled the network, mount the
+ NFS filesystems. If you use amd(8), you may or may not
+ have to mount these filesystems manually. Your mileage
+ may vary.
+
+ * Make sure you are in the root filesystem and extract
+ the `base' binary set:
+
+ cd /
+ tar --unlink -zxvpf /path/to/base11.tar.gz
+
+ NOTE: the `--unlink' option is _very_ important!
+
+ * Install a new boot block:
+
+ cd /usr/mdec
+ disklabel -B <root disk, e.g. sd0>
+
+ * Sync the filesystems:
+
+ sync
+
+ * At this point you may extract any other binary sets
+ you may have placed on local filesystems, or you may
+ wish to extract additional sets at a later time.
+ To extract these sets, use the following commands:
+
+ cd /
+ tar --unlink -zxvpf <path to set>
+
+NOTE: you SHOULD NOT extract the `etc' set if upgrading. Instead, you
+should extract that set into another area and carefully merge the changes
+by hand.