View Single Post
Old 03-06-2019, 07:54 AM   #6
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by BloodRagg View Post
OKreader ... Ohh nice
Im still using ntx_hwconfig and the koreader.sh suggests otherwise (see reboot clause), but ill take your word for it
Running KOReader by using other launcher is supported (ie: launching KOReader via telnet/ssh) but KOReader expects a working Kobo filesystem (including their "weird" drivers path and their binaries)

Quote:
Originally Posted by BloodRagg View Post
What is do not understand though is why one would use the variables from rcS instead of relying solely on ntx_config. Because when i look at the default rcS
Repurposing system environment variables is a good thing on a device which should retain compatibility with stock firmware and other 3rd party software.

If you want to make KOReader available on other kind of systems you can create a "koreader-standalone.sh", like we do on BQ Cervantes devices: https://github.com/koreader/koreader...-standalone.sh and get your environment variables there.
pazos is offline   Reply With Quote