I don’t need to be patronized on the difference between zones and VM’s as I’m also one of those VMware users from 1999 in Brendan’s article.
Zones however are superior to VM’s because they don’t require hard pre-allocation of resources like virtual machines do, so they are a superior choice in environments where Windows isn’t desired or required.
As for my Linux hate, if Linux were so great and well made, I wouldn’t hate it. I like well made things.
> Zones however are superior to VM’s because they don’t require hard pre-allocation of resources like virtual machines do, so they are a superior choice in environments where Windows isn’t desired or required.
In public cloud that's not a problem, that's a requirement, so one VM wouldn't trash all its neighbors.
That is what containers are for. On SmartOS a container is used to constrain resource limits of a zone, but if a zone is using less than the limits it’s more efficient in terms of hardware. However, if one is not using this technology, one is forced to hard partition with virtual machines.
> As for my Linux hate, if Linux were so great and well made, I wouldn’t hate it.
With Linux running on ~10^11 devices, everything from watches to supercomputers to the Falcon 9 rocket, the market disagrees with you to a pretty comical extent.
Masses have always been wrong, to the extent that they burned and killed innocent people for one reason or another. No mass has ever produced any innovation; if you look at revolutionary inventions, they were always invented by single persons or very small, focused group of individuals, but never masses. Masses don't have the competence to judge whether that which they are following is good or bad, correct or incorrect. That's why they follow. It's what defines them as a mass.
As for Latin, this is the same reasoning of "learning" Linux and not understanding UNIX and mis-configuring the OS or breaking Linux backwards compatibility. Or re-inventing the wheel all the time while basic functionality like booting or the fiberchannel stack still do not work correctly after 20+ years.
Thank you masses for all the sleepless nights I was forced to endure because Linux has the same problems Solaris solved decades ago. Because masses know what's good and what's bad.
You're arguing one edge of a very much double-edged sword, and I must say (as someone that was deploying the linux-vserver patches by at least 2004) it's incredibly tiring to watch.
Yes there is definitely a way to praise alternatives without railing against the current discussion topic.
Some may appreciate being made aware of another technology; unfortunately this specific example reinforces the importance of marketing and pursuing mindshare.
No less tiring than reading about re-inventing virtualization in Linux. For both of us the fix is the same: either don’t read it or remark how tiresome it is.
Where we both agree is that it’s tiresome, but for very different reasons.
Perhaps it is because given technical capability, I cannot understand why Amazon is even being discussed when it is technically inferior to what Joyent offers and Amazon is the most expensive provider.
Sounds to me that your understanding is the real problem here. There are a lot of resources you can use to read up on the value proposition, and while I do think AWS is pretty expensive and perhaps priced a bit too high, it's a great platform that goes way beyond just the speed of the VM tech.
That had basically nothing to do with the architecture. The key reason was likely the diverging requirements between laptop (Apple) and server (IBM) chips.
Yeah I agree. It would be great if parts of the kernel could be written in a safer language. I think in 10 years that will be happening in at least some widely used OS, but most likely one that only supports a small range of architectures.
At least with GNU as you can use %r1, %r2 etc. as an "intrinsic part of the syntax". Which means you can't use a register name where an immediate is expected.
However that doesn't fix the gotcha with r0 being special, that is specified in the ISA. In fact it's that way precisely so you can load an immediate without needing a separate opcode.
Huh, never knew that... but I just tried it and GAS (the version Debian installed as powerpc-linux-gnu-as, at any rate) accepted "lwz %r0, %r5(%r0)". Snatching defeat from the jaws of victory...
It would still be a gotcha, but a pretty minor one if messing it up just resulted in an error. I suppose the approach taken by AArch64 and others is preferable, where one register is just completely reserved as constant 0 rather than only in some encodings.
