Creating a Solaris 10 zone on OpenIndiana
rqsall.com
rqsall.com
What were the primary use cases for Solaris in its prime? Is it still used anywhere now?
I used to administer many Solaris hosts in the past and they were super reliable for hosting enterprise services like mail, NFS, NIS, etc. Kernel panics were pretty rare. One really nice feature is that there’s no concept of out of memory killer. I remember one day our LDAP host went haywire and the load average shot up to something like 800. I was able to still get in as root and kill the offending processes.
I have fond memories of Solaris 10, including ZFS, dtrace, zones, SMF. The X4500 “Thumper” storage appliances were pretty bad ass back in the day.
What does it do when it’s out of memory?
Linux is the main Unix-y system that allows over-allocation.
When you dropped it on your toe
I think the instructions suggested a 4 person (5?) lift into the bay. Even with a hydraulic trolley to get it to the right level we used three people.
Interesting... So what happened if you ran out of memory ?
https://docs.oracle.com/cd/E19620-01/805-4453/6j47hg5qf/inde...
The switched memory architecture. Which was a boon to running Oracle and transaction processing monitors (e.g. Tuxedo) – or, anything that required large amounts of memory and the high memory bandwitdth, but did not require the highest performant CPU.
Also, an extensive network of partners and resellers that made it easy to purchase a SPARC system, service and upgrade it was also a major factor. If one had the money, it was just too easy to buy a SPARC box.
> That it was RISC?
That is where Sun was consistenly lagging behind other RISC vendors until (roughly) the arrival of the UltraSPARC-II CPU. Before then, Alpha, POWER and PA-RISC CPU's consistently outperformed current SPARC / UltraSPARC-I designs. Another part of the problem was that the highly optimising Sun C/C++ compiler was very expensive, and GCC could not generate the code that would be as efficient for quite a while – not until after GCC folks rewrote the register allocator (GCC v2.95 circa?). The problem partially stemmed from the SPARC's windowed register file design. GCC has eventually caught up and has been generating fast (Ultra-)SPARC code since then.
* https://en.wikipedia.org/wiki/Network_Equipment-Building_Sys...