summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortholo <tholo@openbsd.org>1996-10-12 03:21:38 +0000
committertholo <tholo@openbsd.org>1996-10-12 03:21:38 +0000
commit75ac1c79932a5ecbe6715f62ccef48410190d9bb (patch)
tree2e5a3e416b55ae438baeacf9c91accc51723e5cb
parentStop if the sum of unreachables and timeouts are >= number of probes, but (diff)
downloadwireguard-openbsd-75ac1c79932a5ecbe6715f62ccef48410190d9bb.tar.xz
wireguard-openbsd-75ac1c79932a5ecbe6715f62ccef48410190d9bb.zip
Warn about changed all-disk partition and updating boot blocks
-rw-r--r--distrib/notes/i386/upgrade8
1 files changed, 7 insertions, 1 deletions
diff --git a/distrib/notes/i386/upgrade b/distrib/notes/i386/upgrade
index 61df886333d..8c7aaae7652 100644
--- a/distrib/notes/i386/upgrade
+++ b/distrib/notes/i386/upgrade
@@ -1,3 +1,9 @@
+NOTE! If you are going to do the upgrade manually, you MUST use the
+"-r" flag when invoking disklabel(8). You MUST also change the
+partition table such that partition 'c' encompasses the entire drive,
+and not only the OpenBSD partition. Finally, partition 'd' is no
+longer special and can be used for any purpose whatsoever.
+
To do the upgrade, you must have the appropriate kernel-copy floppy
image on a disk, and the upgr20.fs floppy image on another. You must
also have at least the "base20" binary distribution set available,
@@ -42,7 +48,7 @@ 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
+ You may 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,