Hans;<div><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Actually, this is not the case on later Mac models, as the OS controls the fan cooling system. So you can really destroy the Mac by overheating it. I think it may have happened to a MacBook Air here - there were problems with the software in earlier models. Suddenly, it would no more reboot. It happened on a very hot day. Eventually, the motherboard, or something had to be replaced.<br>

<br></blockquote><div><br></div><div>Yes, there will be exceptions, on specific models under unusual conditions, I believe there have also been some hard-drives that could be destroyed by software commands in the recent past. However that&#39;s A) rare and B) not a issue with the terminal as such. Though it might be possible I wouldn&#39;t know how to address the fan speed through Bash here&amp;now.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
One can also destroy the Mac by making a poorly written KEXT (kernel extension). It is too slow to let all stuff run as programs, so one can make an extension to the kernel itself, running without the normal kernel checks then. If it sabotages the kernel, then the cooling system may not run properly. I&#39;m not sure this has happened, but it is a theoretical possibility, in fact mentioned on the Darwin-kernel list.<div>
<div></div><div class="h5"><br><br></div></div></blockquote><div><br></div><div>No doubt that&#39;s true... but that definitely wouldn&#39;t happen by accident and I also feel that that is the kind of design error that a warranty should cover, certainly in the case of computers sold as a matched pair of a OS and hardware. Normal use of the terminal, including the installation of languages like ChucK should -and will- be perfectly safe and normal usage of a computer.</div>
<div><br></div><div>Yours,</div><div>Kas.</div></div></div>