On 10/9/07, Matthew Dale Walburn <matt at railwave.com> wrote: > The biggest gotcha in my environment would have to be the large > number of legacy, unmaintained applications. Many of these > applications are built around older application frameworks that are > not supported on anything other than Solaris 8 (or 9), and the > developers that wrote them are long gone so we can't easily port them > to newer, supported frameworks. I have a feeling that even though the > sol8 zones will look like Solaris 8, that my ISVs will use that as a > loophole to get out of support.
When I look around at legacy systems running "older application frameworks" I tend to see things where the version that is running is not supported. More than likely, it is on hardware that is near or past end of support life as well. At some point the decision has to be made where the support is most important (hardware, OS, application). Etude helps with the hardware but it doesn't extend the OS at all. I somehow think that Solaris 8 support on sun4v has minimal benefit over Etude. The question gets more interesting when you look at leveraging the ABI guarantee to move Solaris 8 stuff to Solaris 10. The unsupported app stays unsupported, but the hardware and OS are in much better shape. Back to a topic appropriate for the list, how many threads of a T2 processor does it take to equal a E420? I somehow suspect that it 3 - 4 threads would be roughly equivalent. Hmm... I need look at ldoms 1.0.1 software to see how the FPU plays into this. Is the FPU allocated to an LDOM like the MAU is in 1.0? > The heavy use of VxVM will also making using them tricky. Is that really an issue? Are you using features of VxVM beyond POSIX file operations (open, close, read, write, etc.)? If you aren't using snapshots, storage checkpoints, quickio, odm, BLIB, or similar things your apps shouldn't know the difference. -- Mike Gerdts http://mgerdts.blogspot.com/
