<div dir="ltr">On Wed, Jan 30, 2013 at 2:28 PM, Eneko Gotzon Ares <span dir="ltr"><<a href="mailto:enekogotzon@gmail.com" target="_blank">enekogotzon@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
To execute powerful commands (for MacPorts) in Terminal, can cause negative side effects? (disturb the drivers of smart card readers, the display adjustment, etc…).<br></blockquote><div><br></div><div>All's fair for root --- this is why MacPorts uses sandboxing and does builds as a nonprivileged user, to minimize the chances of this happening. (Hm, do we have a paranoid mode where it makes an archive but doesn't install it automatically, so one can inspect the archive before activating it?)</div>
<div><br></div><div>I would be inclined to suspect something else is wrong; first guess would be power, although you might also check things like CPU temperature etc. If MacPorts is building from source instead of downloading prebuilt archives, it may be pushing some marginal component too close to the edge. (Electronic components do age and fail, and can sometimes be defective in ways that only show at the outside edges of their design specifications.)</div>
</div><div><br></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div>
<div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div>