View Single Post
Old 09-06-2016, 03:19 AM   #6
Markismus
Guru
Markismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicingMarkismus causes much rejoicing
 
Markismus's Avatar
 
Posts: 955
Karma: 149907
Join Date: Jul 2013
Location: Rotterdam
Device: HiSenseA5ProCC, Cracked OnyxNotePro, Note5, Kobo Glo, Aura
Quote:
Originally Posted by rtiangha View Post
I actually thought about doing this myself, but less for improving performance and more to prevent my books from being wiped out after every factory reset (I have a GloHD and thus, no external sd reader; reloading from scratch takes like 20 hours to sync up my entire sideloaded library),
Yes, this was one of the many reasons I came up with wile considering it a year ago, too. In the end I just got to many segmentation faults to consider 64GB of FAT32 sane enough: That's what finally pushed me to do it. Syncing 23GB took me 10 minutes of preparation and a good night sleep.

Quote:
Originally Posted by rtiangha View Post
as I assume that the factory reset script is hard-coded to wipe out the third partition only.
Yes, /dev/mmcblk0p3 to be exact. Doesn't look at anything else, so make sure your Library doesn't end up on a partition with that identifier.
Quote:
Originally Posted by rtiangha View Post
I haven't had time to play around it myself, though, but I would assume that you'd need to change the mounting scripts to see the fourth partition. But I don't know if the OS is smart enough to automatically probe that partition for new books. If not, for devices without external SD, one thing I would try is figuring out what the mount point is for external SD cards and mount that fourth partition to that, assuming the OS is hard-coded to search that mount point. That wouldn't work for devices that have both internal and external SD readers, though.One day I will try this for myself...
I put the mount command it in a KSM-script that checks how to start (Nickel, koreader, sometimes, always, never). (We used to hack Kobo's /etc/init.d/rcS so that it would run an empty script at the start.) Most important thing to remember is that /etc/fstab is not called by Kobo, so it's not enough to put the mount there.
As for probing...I always thought that Kobo went ridiculously slow or even end in a loop when indexing 23GB of books?! That's one of the big reasons for using Koreader for me. Searching such a database was said to take forever. Is that not true anymore?
Markismus is offline   Reply With Quote