This morning's plan to find out what is going on - -
The Kindles use a lipc-daemon for inter-process communications:
Code:
[root@kindle root]# ps aux | grep 'lipc'
root 7378 0.0 0.7 18968 984 ? Ssl 00:25 0:00 /usr/bin/lipc-daemon -p /etc/lipc-daemon-props.conf -e /etc/lipc-daemon-events.conf
root 8392 0.0 0.4 2652 536 pts/0 RN+ 15:06 0:00 grep lipc
But the only entity that has access to the address space of all processes is the kernel.
The Linux kernel supports at least a half dozen such services.
One of which is dbus:
Code:
[root@kindle root]# ps aux | grep 'dbus'
92 6775 0.0 0.6 2236 788 ? Ss 00:24 0:00 /usr/bin/dbus-daemon --system
root 8390 0.0 0.4 2656 548 pts/0 RN+ 15:06 0:00 grep dbus
But not even Lab126 is ambitious enough to write a 7th ipc system for the kernel internals.
Code:
k2 $ readelf -d lipc-daemon
Dynamic section at offset 0x3254 contains 29 entries:
Tag Type Name/Value
0x00000001 (NEEDED) Shared library: [liblipc.so.0]
0x00000001 (NEEDED) Shared library: [libpthread.so.0]
0x00000001 (NEEDED) Shared library: [libglib-2.0.so.0]
0x00000001 (NEEDED) Shared library: [libgthread-2.0.so.0]
0x00000001 (NEEDED) Shared library: [libdbus-1.so.3]
0x00000001 (NEEDED) Shared library: [libc.so.6]
Translation: lipc is using dbus as its inter-process transport.
Note: This is not 'news' it has been posted here in the past - I just could not recall if it was done this way in the v-2.x firmware.
I.E: It was and still is being done that way.
So, snooping dbus traffic is one way of monitoring all lipc traffic.
(On the K2 there are 51 processes - all 'talking' to each other.)
The link a few posts above gives the details of a configuration file change that lets 'root' snoop all traffic (normally prohibited).
I get that set-up and working, then I'll re-enable 3G on this K2 and see just what it is that Amazon is doing.