Kindle index files: file path hash method

[Doitsu]

I had a look at the files in:

/mnt/us/system/Search Indexes

which appears to contain the actual search indexes and the following two files:

Index.db 
Index.lg

Index.db appears to be a B-Tree database that contains words as well as file paths and hash values.

I've got the following questions:

1. Is there any database program that can open index.db or is it a custom Amazon file format?
2. What kind of hash method does the Kindle firmware usually use to convert Unix file paths to hashes? (Index file names always start with a lowercase y followed by a 32 character hexadecimal number, which is not an MD5 hash.)

[knc1]

try the sqlite already installed on the Kindle.

[Doitsu]

Originally Posted by knc1

try the sqlite already installed on the Kindle.

Even though the database has a .db extension it is not an SQLite database.

[knc1]

Originally Posted by Doitsu

Even though the database has a .db extension it is not an SQLite database.

What is the output of the utility "file" when used on the database?

Ah, this is *nix, file extensions are not significant (except sometimes, to the human involved), so your observation is not relevant.

[Doitsu]

Originally Posted by knc1

What is the output of the utility "file" when used on the database?

"file" only identifies the file as a data file. I.e. it's not a common run-of-the-mill file.

Originally Posted by knc1

Ah, this is *nix, file extensions are not significant (except sometimes, to the human involved), so your observation is not relevant.

My observation is relevant. Based on the strings in the .db file, for example, jdbm.btree.BTree, I'm pretty sure that it's some kind of Java B-Tree database file.

[knc1]

Originally Posted by Doitsu

"file" only identifies the file as a data file. I.e. it's not a common run-of-the-mill file.


My observation is relevant. Based on the strings in the .db file, for example, jdbm.btree.BTree, I'm pretty sure that it's some kind of Java B-Tree database file.

Ah, a case of apples and oranges -

Your observation that an extension of .db implies a SQLite file, and that you thought that was my reasoning for making the suggestion that I did **is wrong**.

And any implied association between an extension and the file format **is not relevant** for any *nix system.

I made no reference to the btree appearance of the data, many things are "btree" in appearance.

[Doitsu]

Originally Posted by knc1

Your observation that an extension of .db implies a SQLite file, and that you thought that was my reasoning for making the suggestion that I did **is wrong**.

On the contrary. Since you tend to assume that non-regular posters in this forums are idiots lack techical skills and often jump to conclusions when replying, this is exactly what I expected your reply to be.

Originally Posted by knc1

And any implied association between an extension and the file format **is not relevant** for any *nix system.

It may surprise you to learn that I'm actually well aware of this fact. (I'm writing this post on a Linux machine.)

Originally Posted by knc1

I made no reference to the btree appearance of the data, many things are "btree" in appearance.

Indeed. You made no reference to the btree appearance and obviously haven't even looked at the database file. How about you grab one of the "many devices" that you own according to your profile and have a look at the actual file instead of posting more conjecture?

[knc1]

Originally Posted by Doitsu

How about you grab one of the "many devices" that you own according to your profile and have a look at the actual file instead of posting more conjecture?

Because I am not the one asking the questions.
You (write) sound as if you are fully capable of discovering the answer.
Let us know what it is when you do.