View Single Post
Old 10-22-2013, 10:37 AM   #28
eureka
but forgot what it's like
eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.
 
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
Quote:
Originally Posted by Aeris View Post
Eureka, adding a <script> import row in this file:

/usr/share/webkit-1.0/pillow/default_status_bar.html

in the head wouldn't be a safer approach?

If default_status_bar.html file goes fucked up someway, the kindle shouldn't brick anyway, right?
You're asking either wrong question, or wrong person.

"Upstart job" way with automatic runtime modifications of Pillow app internals is appealing me much more than your alternative and I personally can deal with its known quirks. I have KT with easy accessible USB downloader mode, so any "bricking" concern is not a problem for me.

But even if I would have PW, possible "unsafeness" of adding new Upstart job wouldn't bother me at all.

And direct modifying of files on system partition is just not sexy solution. So its "safeness" is not an interesting discussion subject for me in this case.

UPD: that said, both methods are equally safe from my POV.

Last edited by eureka; 10-22-2013 at 10:46 AM.
eureka is offline   Reply With Quote