Quote:
Originally Posted by eschwartz
Have you ever tried saving a file on a linux machine in the same location where there is already a folder? Clearly not...
no one ever suggested the goal was stopping the root user from overwriting a file.
|
Vitalidon did in a post above when trying to disable indexing:
"What about deleting index.db file and create instead a folder with exactly the same name Index.db [...] If kindle will not be able to delete the folder, then maybe it will not be able to recreate another index.db file, and therefore it will not be able to start the index process."
This doesn't work.
I tried something similar when I first got my Kindle with "special offers." I noticed that if the folder, .assets, in the system folder were deleted, no ads would be displayed, however within a day if one went online for even a minute the .assets folder would be re-created and ads would reappear as the folder filled with image files. Then I tried making a .assets file in the system folder on the same theory as the one espoused by the poster who wanted to disable indexing. However, no joy. The .assets file got deleted to make way for the .assets folder.
This is similar to Windows behavior. Using this method, I have successfuly stopped the creation of unwanted files created by various third party programs, but if one tries to prevent the creation of a system file, Windows has no trouble creating that file. Apparently Linux works the same way.