Re: [Barry-devel] upldif hangs

[Chris F. <cd...@fo...>]

On Tue, Feb 19, 2013 at 07:09:59PM +0100, YuGiOhJCJ Mailing-List wrote:
> > This is what happened when I try to dump my contacts with upldif:
> > "$ sudo upldif -v
> > 
> > "
> > The program hangs.
> > My objective is to dump my contact list from the SIM card.

Some clarification.  The upldif program is a tool meant to *write* to
your BlackBerry.  Since it has the potential of deleting all your
contacts and then writing what you give it, it does not actually
upload by default.  You have to explicitly give it the -u option.

If you want to *read* data from your blackberry, you want other tools,
such as btool, or bio.




> I found a way to dump my contact list from the SIM card using the btool program instead of the upldif program:
> $ btool -c dn > file.txt
> (in fact, it can't be done directly, I need before this to go in my BlackBerry menu to copy my contact list from the SIM to the phone)
> Then I can upload it using the upldif program:
> $ upldif -u < file.txt

I'm not aware of any direct access to the SIM card, but I haven't looked
too closely either.  If it doesn't show up by default in Address Book,
then it would either be in some other database (btool -t) or it may always
require the "copy from SIM" operation first.


> But if I read the help of the upldif program I can see that it should be able to dump my contact list:
> "$ upldif -h
>  -u        Do the upload.  If not specified, only dumps parsed
>              LDIF data to stdout.
> "
> So, I think the behaviour of the upldif program is not the expected behaviour.

Since upldif reads LDIF data on stdin, for safety's sake, it writes what
it thinks it just read to stdout for verification, and it writes it in
BlackBerry record style.  This way you can feed in your ldif data, and make
sure that upldif is parsing your data correctly (by viewing stdout) before
using the -u to blow away your existing contacts and upload.



> Is there a way to copy the contact list from/to the SIM directly ?

Not that I know of.


> Can you correct the behaviour of the upldif program to be the expected behaviour ?

Perhaps I can clarify the man page.  upldif is not for reading, but for writing.

Thanks!
- Chris