tried but failed
I did a little hack to the ereader. My idea is that "if the ereader can not write to the SD, it may not tring to do so and save some time."
First, I looked at the file system and noticed that the external memory is used as follows:
/dev/memorystick:
total 0
br--r--r-- 1 root root 121, 0 Dec 31 1969 cxd3452a
br--r--r-- 1 root root 121, 1 Dec 31 1969 cxd3452a1
cr--r--r-- 1 root root 243, 0 Oct 13 23:08 cxd3452actl
/dev/sdcard:
total 0
br--r--r-- 1 root root 122, 0 Dec 31 1969 r5c807a
br--r--r-- 1 root root 122, 1 Dec 31 1969 r5c807a1
cr--r--r-- 1 root root 246, 0 Dec 31 1969 r5c807actl
So I changed some of the hack here and add a function to change all the file in these two folder between readonly and read-write (The above file attributes has already been changed).
While I think this is a good idea, changing such file's attribute does not block the reader's access to the SD card.
During this process, I have already set up the framework that can run a linux program by pressing some button. If anyone has any clue how to address the problem at the OS level, please drop me a line.
|