So it looks like I'm going to have to downgrade to 5.2.1P2 from 5.2.2 to avoid panics from assertions in the netbios name service.. Patches for 5.2.2 are somewhere in the indeterminate future.. (all of this for bug 12712, which for some reason isn't listed in Bugs Online)
This brings up one of the points that Tom (?) was ranting on a week or so ago.. Why release 5.2.2, a minor bug-patch revision, that don't incorporate patches from its predecessor?
Perhaps I shoud've called support first, but I just brought these 760's online with 5.2.2, under the apparently false impression that I was getting all the up-to-date fixes.. Was there an erratta for 5.2.2 that I missed that said "THE FOLLOWING IS STILL BROKEN:"?
argh.
..kg..
On Thu, 6 May 1999, kg wrote:
Perhaps I shoud've called support first, but I just brought these 760's online with 5.2.2, under the apparently false impression that I was getting all the up-to-date fixes.. Was there an erratta for 5.2.2 that I missed that said "THE FOLLOWING IS STILL BROKEN:"?
What I usually do is make sure the bugs are listed in numerical order then compare two release with the same base to check out the differences. Unfortunately, I haven't found yet a nice enumeration of bugs fixed in major releases. It's a shame because I'd like to compare 5.2.1P2 to 5.3.x and see if I am ready to upgrade to benefit from the new features without breaking old functionality I depend on (NIS support is a good example).
Pay attention to the "base" of the release. If the base is the same and you don't see a fix for a given bug in one release that means that the bug fix was not included in that release. If 5.2.1P2 WAS the base for 5.2.2 and they did not include the patch (unlikely) then you can rightfully complain to NetApp.
Tom
-
kg -
tkaczma＠gryf.net