 | iop QNX questions, acap, dsm, np-misc.fs (modified 0 times) | slylock | |
|
| In my "running V2 image in QEMU emulator" thread, I talk about trying to find the email address book on an old iOpener Sandisk. I found it, but it's an acap file, named <ten digit number>_addressbook.acap. I figured out that acap is Application Configuration Access Protocol, and a description of it is "a protocol for arbitrary clients to store and retrieve client-specific configuration from a server. ACAP fills a niche somewhere between a full-blown directory service, a file system, and specialized single-service protocol support." Appears to be a standard designed to be used by IMAP servers, and I know the iOpener was IMAP based, so this is cool. My first question is, did the iOpener engineers develop their own IMAP client, or did they copy something that was open source? I'm curious to find out how acap got involved, sounds like something you'd use only if you already had source code for it.
Second, is there an acap file reader out there? Google didn't turn up anything, so I suspect not. I was able to get the email address out by hand, but a general purpose reader would be nice for future use.
Next, I found the acap files inside a directory labeled dsm. Searching around for DSM turned up only "Durable Storage Munger." Should that be Durable Storage Manager? Is it isolated to the embedded world? Or the Unix world? I could find almost no info about it.
Finally, while making backups of the files in the Sandisk, I found one, np-misc.fs, was corrupt, which might explain why the iOpener stopped working. Generally, what is an fs file? I'm guessing fs stands for file system, does an fs file get mounted? Perhaps this is something unique to QNX, as the fs directory where QNX mounts file systems (instead of mnt) seems to be uniquely QNX. Am I correct that the "np" in the name stands for NetAppliance, and those np-* files are something the iOpener engineers came up with?
Thanks,
Matt | |
|
|
