Probably I am a little bit old-fashioned, but I still use J-Pilot on my PC and my Tungsten T5 and sync them. It mostly serves as a kind of backup so I have my valuable address and datebook data on separate media. So in case my PC gets inaccessible then I have my data on this device at least.
These are the commands I use.
echo 1 > /proc/sys/net/ipv4/ip_forward
/usr/bin/dund --listen --channel 1 --pppd /usr/sbin/pppd call dun
hciconfig hci0 piscan
Since more than ten years I use IceWM, a clean and compact window manager for X. I can only recommend it.
IceWM in its own words: The goal of IceWM is speed, simplicity, and not getting in the user’s way.
These goals are nicely met.
Here are some thoughts about possible enhancements for J-Pilot.
- Convert pdb’s and pc3’s to sqlite. This makes it easier to analyze data according some criteria, e.g., find how many addresses have the same telephone numbers, how may entries in datebook contain the same substring, etc.
- Convert and transform pdb’s and pc3’s to Google GData. The Google id, which is returned after transmitting data, is then possibly stored in pdb/pc3.
mmap() instead of all its
malloc()‘s inside pilot-link and J-Pilot.
- When J-Pilot searches for strings in the case-insensitive case, then it copies all elements and uses
malloc() for each element. Instead, just use a home-brewed
strstr() which takes care of case.
- Provide ncurses interfaces instead of Gtk. See for example calcurse.
There is a lesser known command,
jpilot-dump, to print portions of J-Pilot files.
Here is an example to print category, first name, last name:
jpilot-dump -A +A"%C %f %l" | less
And here is another command:
I wanted to see what files and when J-Pilot accesses its pdb and pc3 files. In my case
strace produces much more output than actually needed. But
inotifywait shows what and when files are accessed.
inotifywait -m .jpilot/