summaryrefslogtreecommitdiffstats
path: root/UPDATING
diff options
context:
space:
mode:
authormckusick <mckusick@FreeBSD.org>2017-08-23 04:43:50 +0000
committermckusick <mckusick@FreeBSD.org>2017-08-23 04:43:50 +0000
commit2a1ed2b9268f51289dbf1a835dbbe86db37f3574 (patch)
tree8f34700cb31836e75b71714a352c8b3c01be397c /UPDATING
parent333947cd56f377ddcb1d8aaaf2bb3a01c2449bc8 (diff)
downloadFreeBSD-src-2a1ed2b9268f51289dbf1a835dbbe86db37f3574.zip
FreeBSD-src-2a1ed2b9268f51289dbf1a835dbbe86db37f3574.tar.gz
MFC of 322298 noting MFC 322806 in UPDATING
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING13
1 files changed, 13 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 91a78b5..1bb6a28 100644
--- a/UPDATING
+++ b/UPDATING
@@ -16,6 +16,19 @@ from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
the tip of head, and then rebuild without this option. The bootstrap process
from older version of current across the gcc/clang cutover is a bit fragile.
+20170822:
+ Since the switch to GPT disk labels, fsck for UFS/FFS has been
+ unable to automatically find alternate superblocks. As of r322806,
+ the information needed to find alternate superblocks has been
+ moved to the end of the area reserved for the boot block.
+ Filesystems created with a newfs of this vintage or later
+ will create the recovery information. If you have a filesystem
+ created prior to this change and wish to have a recovery block
+ created for your filesystem, you can do so by running fsck in
+ forground mode (i.e., do not use the -p or -y options). As it
+ starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
+ to which you should answer yes.
+
20170518:
arm64 builds now use the base system LLD 4.0.0 linker by default,
instead of requiring that the aarch64-binutils port or package be
OpenPOWER on IntegriCloud