Folks, *please* try to update the subject if it diverts too much from the original thread, okay?
On 18.09.2009, at 11:47, Martin Langhoff wrote: > On Fri, Sep 18, 2009 at 11:34 AM, Tomeu Vizoso <[email protected]> > wrote: >> I agree that an activity for repairing or recovering the DS would be >> quite beneficial, we'd need to add an exception for Rainbow though. > > So Rainbow would prevent a regular activity from reading .sugar? Depends on its permissions. If it allows reading by anyone, an activity can read. If not, a sandboxed activity can not access it. Checking ... yep, non-readable. - Bert - > I am > not familiar with how one goes about exceptions and such. I've > recently seen activities that do "out of the sandbox" things (Tony's > data manager, dsd's audio fixer...), don't know how... > > Alternatively, a python script to run on the Terminal might help (but > an activity is much better, naturally) > >> If we find the root cause and get a fix that seems to be worth >> deploying, can we deploy it to machines presently with 0.82? > > We can offer the patch to deployers, and I can integrate it into a > build. But our reach is limited there. A user-deployable "repair" tool > is a lot more effective. > > cheers, > > > > m > -- > [email protected] > [email protected] -- School Server Architect > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff _______________________________________________ Sugar-devel mailing list [email protected] http://lists.sugarlabs.org/listinfo/sugar-devel
