Robert - Note what platform you'll be installing on. For example, if you have a cluster, 6.5.1 had a bug that caused one machine to lose time sync with the other. If you have a certain NVRAM board, you'd get bogus messages that the NVRAM was failing.
Make sure you go, at least, to 6.5.2. You'll miss some significant bugs there.
JKB
----- Original Message ----- From: Robert Borowicz rbaus@swbell.net Date: Friday, April 1, 2005 7:38 am Subject: Upgrading to 6.5
I'm upgrading to 6.5 this weekend. Is there any gotchas? (yes I'll be reading the Release Notes)
Isn't there an issue with the exports file being re-written? I thought I remembered seeing that discussed here a while back.
-Rob
If you are using NFS, then skip 6.5.2 altogether. 6.5.4 has the latest and greatest code for NFS.
Your exports can be rewritten because the format has changed. Once you upgrade, you can use the option nfs.export.auto-update to control this, but I believe if you ever have a -access in an export rule, it will force a rewrite anyway.
There is a /etc/exports.pre.upgrade created during the upgrade process.
Make sure your host names in your export lists are reverse resolvable. The export code makes heavy use of gethostbyaddr().
On Fri, Apr 01, 2005 at 08:48:33AM -0500, jbrigman@nc.rr.com wrote:
Robert - Note what platform you'll be installing on. For example, if you have a cluster, 6.5.1 had a bug that caused one machine to lose time sync with the other. If you have a certain NVRAM board, you'd get bogus messages that the NVRAM was failing.
Make sure you go, at least, to 6.5.2. You'll miss some significant bugs there.
JKB
----- Original Message ----- From: Robert Borowicz rbaus@swbell.net Date: Friday, April 1, 2005 7:38 am Subject: Upgrading to 6.5
I'm upgrading to 6.5 this weekend. Is there any gotchas? (yes I'll be reading the Release Notes)
Isn't there an issue with the exports file being re-written? I thought I remembered seeing that discussed here a while back.
-Rob
-
jbrigman＠nc.rr.com -
Tom Haynes