summaryrefslogtreecommitdiffstats
path: root/UPDATING
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2000-03-28 06:59:46 +0000
committerimp <imp@FreeBSD.org>2000-03-28 06:59:46 +0000
commit9c60490f9c6bfc1cca909053f05b8c1553e089fb (patch)
tree290c252ea322e1b363f6e35412b30d6fa681f8b9 /UPDATING
parentcc7dea2aa9f734b58bd9e4e4114e22237d2dc3c9 (diff)
downloadFreeBSD-src-9c60490f9c6bfc1cca909053f05b8c1553e089fb.zip
FreeBSD-src-9c60490f9c6bfc1cca909053f05b8c1553e089fb.tar.gz
Normally I don't put entries that should have been made months ago
into UPDATING. However, in this case I'm making an exception. I'm adding a recommendation that people update their boot blocks. Old boot blocks will cause a system to become unbootable if you have removed /dev/{,r}wd*. Submitted by: Jeroen Ruigrok/Asmodai <asmodai@freebsd.org>
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING7
1 files changed, 7 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 814578a..d1dbf8b 100644
--- a/UPDATING
+++ b/UPDATING
@@ -22,6 +22,13 @@ ITEMS:'
that you are loading are up to date.
20000315:
+ If you are upgrading from an older version of FreeBSD, you
+ need to update your boot blocks as well. 'disklabel -B ad0'
+ will do the trick. This isn't critical until you remove your
+ wd device entries in /dev, at which point your system will not
+ boot.
+
+20000315:
4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
to upgrade to 4.0 from 3.x.
OpenPOWER on IntegriCloud