Hans;<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Sorry, it was a rhetorical agreement, same as &quot;yes&quot;. Ambiguous, like in this video:<br>
  <a href="http://www.youtube.com/watch?v=6JrIYR8jArk" target="_blank">http://www.youtube.com/watch?v=6JrIYR8jArk</a><div class="im"><br></div></blockquote><div><br></div><div>I really don&#39;t think there is any disagreement here, but it can&#39;t hurt to be clear and precise.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
However, sudo is a tool to protect the installation against unauthorised modifications.<br>
</blockquote>
<br></div>
Actually, not: it is just a shortcut to become root; try &#39;sudo -s&#39;.</blockquote><div><br></div><div>Quite so, and I believe that unlike with becoming root outright the commands given with sudo are logged, which can be helpful to trace what went wrong, if something does.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Though restrictions can be implemented, that is not so in Mac OS X. In addition, when one does a &#39;sudo&#39;, it is valid for a few minutes, which can be exploited by malware, by trying every minute if the user has enabled root permissions.<div class="im">
<br></div></blockquote><div><br></div><div>It might be preferable to restrict root access to a single bash session, or perhaps to require it for every command. System-wide root access sounds a bit excessive to me, but I don&#39;t know what considerations went into that choice.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On the other hand, whenever you install something on Mac OS X, and is asked for the password, one is in effect doing the same thing as a &#39;sudo&#39;, becoming root. So one should never do that unless one trust the software.<br>

<br></blockquote><div><br></div><div>Good advice. I do trust our devs, even though they can be a bit chaotic at times ;-)</div><div>..</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<br>
FYI: Though it derives from FreeBSD, it is now certified UNIX (Intel 1.5 and later).<br>
<br></blockquote><div><br></div><div>It is. Of course the main thing that this indicates is that Apple (unlike some other *nixes) has a budget for certification.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

I suspect he has absolutely no knowledge about the console (Terminal). Therefore, to start with it, it might be safest to put it into ~/bin/.<br>
<br>
It is good with this discussion - ChucK with strange downloading comments, is directed to the console-savvy user, in effect shutting others out.<div><div></div><div class="h5"><br></div></div></blockquote><div><br></div>
<div>Yes. There have been a lot of questions about this. Commandline interfaces do look alien and a bit scary to many. Perhaps we should spend some time on this in a FAQ, for example with a link to a good online tutorial. We may also need to update the docs on the mini since the mini really isn&#39;t all that experimental and dangerous any more.</div>
<div><br></div><div>Yours,</div><div>Kas.</div></div>