The battle cry of IT brinksmanship, "If it ain't broke, don’t fix it," means that risk has triumphed over cost. This fate is commonplace for legacy applications which can be found sitting on an outdated/unsupported box, running on ancient OS sporting a "Do Not Touch" sign.
Not important enough to fix; too important to fail. These applications are at risk of failure. And everyone knows it.
AppZero offers an alternative that changes the risk/cost math by eliminating the risk at a slashed cost/effort – with no re-engineering or coding required.
Over the last few years, we have helped a number of significant IT operations use our application virtualization solution to migrate their legacy Solaris applications onto newer systems that are reliable and powerful systems. Prior to learning about AppZero, these organizations lived with risk hunting spare parts for their hardware systems from Ebay and Craigslist – sites that, like the old buffalo grounds, are now hunted-out. At this point, risk becomes probability.
(Get More Information . .)
Oracle has posted a tabular list of Supported Virtualization and Partitioning Technologies for Oracle Database and RAC Product Releases that identifies those virtualization/partitioning technologies already supported and reaffirms the policies that each new OS and its complementary virtualization/partitioning technology, must be certified by Oracle and, further, that each new OS plus its virtualization/partitioning solution must be guaranteed by the appropriate hardware vendor to be backward compatible to the version listed in the tables cited in the above link.
(Get More Information . .)
The "documentation for Solaris 10 Operating System" page includes links to the HTML and/or PDF versions of the documents for each of the releases of Solaris 10:
The jury’s still out on the Loch Ness monster and alien abductions, but I can personally testify to the existence of Solaris 2.6 and 7 applications. They are very real -- the stuff of IT nightmares. Why? Because, undocumented by app dev owners long since departed, these applications are chugging away on antiquated hardware that can not be replaced at any cost - when they fail.
And that’s the key point here: when they fail. In this case, "if" is an exercise in delusion and denial.
I have the answer for apps that go bump in the night. AppZero virtualizes legacy Solaris applications without re-compiling or change so that they can quickly and easily run in supported environments on current hardware. Fast. Painless. Inexpensive. Effective ...
(Get More Information . .)
With the release of Solaris 11 Express, users will find a new implementation of the forced privileges mechanism. In addition to being system agnostic, it does not store additional information on disk with the binary as did the version from Trusted Solaris 8 and earlier. Darren Moffat comments on this feature in "When setuid root no longer means setuid root (Forced Privileges,)" where he explains that now, when the kernel is processing an exec(2), it treats setuid to root differently (setuid to any other uid or setgid is as in Solaris 10). In the new implementation the kernel looks for an entry in the Forced Privilege RBAC profile in exec_attr(4) to determine which privileges the program should run with. It will now run with only the current uid and just those additional privileges the Forced Privilege RBAC execution profile assigned to that pathname, he adds. This means that Solaris 11 Express has 15 fewer "true" setuid binaries, although this may change with future software updates.
(Get More Information . .)
News and Solutions for Users of Solaris, Java and Oracle's Sun hardware products
Just the news you need, none of what you don't –
42,000+ Members – 24,000+ Articles Published since 1998
