Sun has always said that any application written for Solaris 6 will be forwards compatible with any other version. It’s a big claim, but as long as the application adheres to the API it’s possible.
Occasionally you bump into things that don’t adhere to the API, (quite a lot of applications really). This is usually caused by developers thinking that they should do things “this way”, because Sun does it oh so wrong all the time. Consequently, you end up with legacy applications that can’t run on Solaris 10.
Enter Solaris 8 brandz zones. Being able to run legacy applications in a Solaris 8 brandz generally gets you around most of the issues in the remaining apps that do stupid things. However, there’s a couple of quirks with a zone that can introduce odd behaviour in an application.
Sun’s Java Web Console is a nice little toy. Great for those people who prefer the less extreme learning curve of a CLI, and great for manager types who like pictures.
I’ve used it several times before, but thought I’d try it in on x86 Solaris10u6 box I have here. Bloody Sun. You think a released version implies that it’s stable, and working. Read more…
I’ve been playing around with Solaris jumpstart recently. I haven’t used it since the early days. It seems that a lot of the old problems still exist. So, I’ve listed most of the common problems and their solution here. This also covers Sun’s JET, (Jumpstart Enterprise Toolkit).
This is a Work In Progress — so I’ll be updating this from time time as I come across issues. Read more…
I had the situation at work where I wanted to run Clearcase under a Solaris 10 zone. With a bit of coercing it’s possible to do, and doesn’t impact much of the global zone at all. If you don’t know what Clearcase is, then this still may be handy information to know. Undoubtedly, there are other applications that rely on loadable modules. Read more…
