<html><body bgcolor="#FFFFFF"><div><br>On Feb 24, 2011, at 8:27 AM, Daniel Weinreb <<a href="mailto:dlw@itasoftware.com">dlw@itasoftware.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>
My current favorite item of brain damage in Linux:<br>
<br>
<a class="moz-txt-link-freetext" href="http://opsmonkey.blogspot.com/2007/01/linux-memory-overcommit.html"><a href="http://opsmonkey.blogspot.com/2007/01/linux-memory-overcommit.html">http://opsmonkey.blogspot.com/2007/01/linux-memory-overcommit.html</a></a><br>
<br>
You ask Linux for memory. It says, sure, here's your memory.<br>
Then you make the mistake of actually trying to USE it,<br>
and you get an error from Linux.<br></div></blockquote><div><br></div>"Back when they thought manual memory management was a good idea" (apologies to Douglas)<div><br><blockquote type="cite"><div>
CCL does not like this, as we have discovered in practice.<br>
<br>
In theory, you can turn off this feature. But it turns out<br>
that a lot of Linux programs *depend* on it; they allocate<br>
a lot more than they need. So if you turned it off, enough<br>
other Linux programs would fail that it's out of the question.<br></div></blockquote><div><br></div>I'm not surprised. Linux was built by a bunch of kids in a garage as a cheap clone of a half-baked OS that was itself built by pole-climbing telephone jockeys as a cheap knockoff of a real OS (Multics).<br><div><br></div><div>(yes, I AM a curmudgeon!)</div><div><br></div><div>But Apple is a major commercial company that (usually) seems to try to get things right. That's why the Mach leak is a surprise.</div><br><blockquote type="cite"><div><blockquote cite="mid:900F56DB-9799-4FFD-AA9A-C21E5F5798FF@sandia.gov" type="cite">
</blockquote>
</div></blockquote></div></body></html>