<div class="gmail_quote">On Mon, Mar 9, 2009 at 5:49 PM, Sascha Silbe <span dir="ltr"><<a href="mailto:sascha-ml-ui-sugar-devel@silbe.org">sascha-ml-ui-sugar-devel@silbe.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Mon, Mar 09, 2009 at 05:25:50PM -0400, Luke Faraone wrote:<br> <br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> But unfortunately most Sugar installations other than XOs will lack<br> bitfrost, which is a wider issue that merits further investigation: Should<br> sugar adopt bitfrost?<br> </blockquote> IMO Rainbow (the current implementation of process/activity isolation) should be integrated into Sugar and made mandatory. At the very least it should be optional, though. I.e. just installing Rainbow should suffice to make your system more reliable, no Sugar-specific configuration required.<br> </blockquote><div><br>That's the problem: Rainbow is not currently compatible with GNOME, as in there are no bindings for launching a rainbow'd application. There's nothing to stop you from running it, it just won't isolate non-sugar-activities magically by default, and most programs will be incompatible with it. (and will need source changes)<br> </div></div>-- <br>Luke Faraone<br><a href="http://luke.faraone.cc">http://luke.faraone.cc</a><br>