summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorgad <gad@FreeBSD.org>2004-03-17 01:59:47 +0000
committergad <gad@FreeBSD.org>2004-03-17 01:59:47 +0000
commitfc9687ad3ceb3b017fef0aa4720106a33e4b5733 (patch)
tree1c5b5e004919f5e2398a22c47217d4f1dd3615dd
parentb4d98c68558acbe9782e24963999f922d52ccf28 (diff)
downloadFreeBSD-src-fc9687ad3ceb3b017fef0aa4720106a33e4b5733.zip
FreeBSD-src-fc9687ad3ceb3b017fef0aa4720106a33e4b5733.tar.gz
Add a tip for people who are using database-related ports on a sparc64
system that they intend to upgrade to 64-bit time_t. Noticed by: Roderick van Domburg
-rw-r--r--UPDATING.64BTT7
1 files changed, 7 insertions, 0 deletions
diff --git a/UPDATING.64BTT b/UPDATING.64BTT
index 16c5a23..6b04d25 100644
--- a/UPDATING.64BTT
+++ b/UPDATING.64BTT
@@ -97,6 +97,13 @@ Step Pre-4: For sparc64 machines which need DHCP:
that port and make sure you can get it working *before* you
make the change to use 64-bit time_t's.
+Step Pre-4: For people using database-related ports:
+ Ports like PostgreSQL may change how they store data after
+ they are recompiled for 64-bTT. So, you may have to do a
+ full dump of your data while you still have a 32-bTT system,
+ and do a matching initdb/restore of your data after the port
+ has been recompiled on the upgraded 64-bTT system.
+
After you have built and installed that src-snapshot with 32-bit time_t's,
edit the file /usr/src/sys/sparc64/include/_types.h
find the line:
OpenPOWER on IntegriCloud