&gt; They already have some knowledge about their OS and they&#x27;re not likely to do a hard turn for different OS just for the sake of &quot;understanding UNIX&quot;, as it would require quite large effort to just get to the point where they are already with Linux.<p>How about no priority 1 incidents at 02:03 in the morning, resulting in sleepless nights until 07:30 - 08:30 every day during one&#x27;s on call, wasted on stupid problems like ext3 filesystem corruption caused by lost writes (again: <a href="http:&#x2F;&#x2F;danluu.com&#x2F;file-consistency&#x2F;" rel="nofollow">http:&#x2F;&#x2F;danluu.com&#x2F;file-consistency&#x2F;</a>)? Is that a compelling enough reason?<p>No incidents at dead hours of the night.
A programming environment fully supporting standards.
Same software which runs on Linux.
Guaranteed application binary interface backward compatibility: compile on oldest SunOS 5.# you can find, run on all the versions newer than that one.
Change schedulers on the fly, as you need them.
Realtime subsystem.
kdb and mdb: the best post mortem analysis tools in the industry (what are those system administrators going to do when the kernel crashes so bad that it locks up and doesn&#x27;t dump a stack trace?)
Full security isolation and bare metal performance with zones.<p>Exhaustive documentation (&quot;he who can read is clearly at an advantage&quot;), much of it applicable to illumos &#x2F; SmartOS:<p><a href="http:&#x2F;&#x2F;docs.oracle.com&#x2F;cd&#x2F;E19253-01&#x2F;817-1985&#x2F;" rel="nofollow">http:&#x2F;&#x2F;docs.oracle.com&#x2F;cd&#x2F;E19253-01&#x2F;817-1985&#x2F;</a><p>Should I go on?