View Single Post
Old 11-18-2011, 08:19 PM   #86
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@yifanlu: When we want to start it at boot, the cleanest way to play nice with Amazon's volumd that I found was to start it *after* volumd, and before the framework (And not in rcS like it was done at some point, or in the range the fonts & ss hack use early in rc6 (for no good reason, AFAIK, it wouldn't hurt them to run a bit later in rc6)). If it's started before volumd, weird stuff happens (nothing exported over usb, stuck on the connected to computer screen, etc). AFAICT, Duokan does some tricky stuff to deal with that issue, but this seemed simpler and cleaner ^^.

Short answer: just before the framework would be good .

Last edited by NiLuJe; 11-18-2011 at 10:30 PM.
NiLuJe is offline   Reply With Quote