View Single Post
Old 11-20-2014, 09:03 PM   #91
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by NiLuJe View Post
That would have to go in the bridge, but we don't really have an easy way to check if the user already has the RP/CWRP installed, so it's a bit tricky to decide wether or not something should be restored, and I'm a bit wary of unilaterally adding upstart jobs that early in the boot process. (A workaround would be for the RP/CWRP to ship with a modified bridge).
Can't you have a job wait for the framework to start/userstore to mount, then source an emergency file etc. and setup fw5.6.1-friendly permissions for KUAL like a working su? Then the JB bridge could respawn the upstart job if necessary.

The RP and other assorted stuff could simply do what they always did i.e. reinstall.
eschwartz is offline   Reply With Quote