View Single Post
Old 06-17-2017, 02:06 PM   #6
coplate
Guru
coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.
 
Posts: 645
Karma: 1888888
Join Date: Jun 2009
Device: prs-505, Kindle Keyboard 3g, PW3
I have built up the kernel modules to enable this on my PW3.

I get my drive device created at /dev/sda1

I mount that into /mnt/us/documents/sda1

But it is not triggering a rescan of that folder, as if I had copied it into the filesystem.

I imagine that there could be somethings about this 'fuse' filesystem I don't understand, but that's a naive guess.


I have also tired these lipc commands:

This one the log says triggering partial scan, but nothing happens.
Code:
lipc-set-prop com.lab126.scanner triggerUpdate 1
This one says invalid parameter
Code:
lipc-set-prop com.lab126.scanner reScanFile /mnt/us/documents/sda1

Even if I did get this working, I imagine the kindle would not be terribly happy with having the folder plugged in and unplugged etc. ( If would re-index when you plugged it in every time? and then delete the caches when removed? )

I have not yet tested what happens to the mount point if it goes to sleep, or if having the usb plugged in prevents suspend mode.

Last edited by coplate; 06-17-2017 at 02:08 PM.
coplate is offline   Reply With Quote