Palm wifi sync on Linux

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 09:39:17 +0200, John Stolz wrote:

> I've got a Palm device (LifeDrive) which apparently won't sync with linux
> software, so I want to sync by wifi - all the Linux programs need a device
> file (/dev/pilot or /dev/ttyUSB0 or some such - what should I use for a
> wifi connection?

You need to run pi-csd first:
pi-csd -H Motoko -a 127.0.0.1 -n 255.255.255.0 &

My system name is Motoko (but it doesn't seem to be used for anything).

Then the pilot-link "device" you use is "net:".

I've been using this to sync my LifeDrive since I got it without problems.

I'm using Mandriva 2005LE and pilot-link-0.12.0-pre4.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 09:39:17 +0200, John Stolz wrote:

> I've got a Palm device (LifeDrive) which apparently won't sync with linux
> software, so I want to sync by wifi - all the Linux programs need a device
> file (/dev/pilot or /dev/ttyUSB0 or some such - what should I use for a
> wifi connection?

You can get it to sync to Linux using USB but it takes a little work. Here
is what I did to get my Treo650 syncing to Evolution on FC3,

Created the following,

/etc/udev/permissions.d
ttyUSB1:$local:uucp:0660

/etc/udev/rules.d/10-visor.rules
KERNEL="ttyUSB1" SYMLINK="pilot"

Added a line to
/usr/share/gnome-pilot/devices.xml

<!-- PalmOne/Sprint Treo 650 -->
<device vendor_id="0830" product_id="0061" />

Check to see if your LifeDrive is already supported in your devices.xml
file, else you'll have to edit the file like I did.

Finally I had to update gpilot, the version that comes with FC3 is broken.
Download gnome-pilot-2.0.13 and install it, I had to install from source
because I couldn't find an rpm.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 05:20:26 -0400, Ranma wrote:
> You need to run pi-csd first:
> pi-csd -H Motoko -a 127.0.0.1 -n 255.255.255.0 &
>
> My system name is Motoko (but it doesn't seem to be used for anything).
>
> Then the pilot-link "device" you use is "net:".
>
> I've been using this to sync my LifeDrive since I got it without problems.
>
> I'm using Mandriva 2005LE and pilot-link-0.12.0-pre4.
I'd already seen your post and followed the steps you describe, but
without success:

[stolzy@uranus stolzy]$ pi-csd -H uranus -a 127.0.0.1 -n 255.255.255.0 &
[1] 10050
[stolzy@uranus stolzy]$ pi-csd(10050): Connection Service Daemon for Palm Computing(tm) device active.
pi-csd(10050): Accepting connection requests for 'uranus' at 127.0.0.1 with mask 255.255.255.0.
[stolzy@uranus stolzy]$ pi-csd(10050): Connection Service Daemon for Palm
Computing(tm) device active. pi-csd(10050): Accepting connection requests
for 'uranus' at 127.0.0.1 with mask 255.255.255.0.

And eventually i get the prompt back without any sync or further output.

Any ideas?

Archived from groups: comp.sys.palmtops.pilot (More info?)

> You can get it to sync to Linux using USB but it takes a little work. Here
> is what I did to get my Treo650 syncing to Evolution on FC3,
>
> Created the following,
>
> /etc/udev/permissions.d
> ttyUSB1:$local:uucp:0660
>
> /etc/udev/rules.d/10-visor.rules
> KERNEL="ttyUSB1" SYMLINK="pilot"
>
> Added a line to
> /usr/share/gnome-pilot/devices.xml
>
> <!-- PalmOne/Sprint Treo 650 -->
> <device vendor_id="0830" product_id="0061" />
>
> Check to see if your LifeDrive is already supported in your devices.xml
> file, else you'll have to edit the file like I did.
>
> Finally I had to update gpilot, the version that comes with FC3 is broken.
> Download gnome-pilot-2.0.13 and install it, I had to install from source
> because I couldn't find an rpm.

Thanks for this. How do I identify the correct parameters for the line in
the devices.xml?

Also any idea how I tell gnomepilot what to use for a port?

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 15:16:05 +0200, John Stolz wrote:

>> You can get it to sync to Linux using USB but it takes a little work. Here
>> is what I did to get my Treo650 syncing to Evolution on FC3,
>>
>> Created the following,
>>
>> /etc/udev/permissions.d
>> ttyUSB1:$local:uucp:0660
>>
>> /etc/udev/rules.d/10-visor.rules
>> KERNEL="ttyUSB1" SYMLINK="pilot"
>>
>> Added a line to
>> /usr/share/gnome-pilot/devices.xml
>>
>> <!-- PalmOne/Sprint Treo 650 -->
>> <device vendor_id="0830" product_id="0061" />
>>
>> Check to see if your LifeDrive is already supported in your devices.xml
>> file, else you'll have to edit the file like I did.
>>
>> Finally I had to update gpilot, the version that comes with FC3 is broken.
>> Download gnome-pilot-2.0.13 and install it, I had to install from source
>> because I couldn't find an rpm.
>
> Thanks for this. How do I identify the correct parameters for the line in
> the devices.xml?
>
> Also any idea how I tell gnomepilot what to use for a port?

I googled to find out the correct parameters for device.xml. If you don't
find your device that way then google the device line that I provided, the
guy who posted it also said how he found it.

Gnomepilot will use ttyUSB0 or ttyUSB1. I suppose that if you have a lot
of other USB devices, I only have a mouse, then it might use another port.
If you plug your palm in, hit hot sync, and then check /var/log/messages
you'll find which port it used.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 13:25:10 +0200, John Stolz wrote:

> On Mon, 25 Jul 2005 05:20:26 -0400, Ranma wrote:
>> You need to run pi-csd first:
>> pi-csd -H Motoko -a 127.0.0.1 -n 255.255.255.0 &
>>
>> My system name is Motoko (but it doesn't seem to be used for anything).
>>
>> Then the pilot-link "device" you use is "net:".
>>
>> I've been using this to sync my LifeDrive since I got it without problems.
>>
>> I'm using Mandriva 2005LE and pilot-link-0.12.0-pre4.

I think the step I'm missing is how to tell gnome-pilot that the sync is
by network - its obviously expecting a port (/dev/pilot or whatever) -
I've selected network sync, but what do I do for a port?

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 09:59:49 -0400, General Schvantzkoph wrote:

> Gnomepilot will use ttyUSB0 or ttyUSB1. I suppose that if you have a lot
> of other USB devices, I only have a mouse, then it might use another port.
> If you plug your palm in, hit hot sync, and then check /var/log/messages
> you'll find which port it used.

Sorry, I didn't make myself clear - I meant what do i tell gnome pilot
for a port when I sync by wifi?

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 16:39:01 +0200, John Stolz wrote:

> On Mon, 25 Jul 2005 09:59:49 -0400, General Schvantzkoph wrote:
>
>> Gnomepilot will use ttyUSB0 or ttyUSB1. I suppose that if you have a lot
>> of other USB devices, I only have a mouse, then it might use another port.
>> If you plug your palm in, hit hot sync, and then check /var/log/messages
>> you'll find which port it used.
>
> Sorry, I didn't make myself clear - I meant what do i tell gnome pilot
> for a port when I sync by wifi?

/dev/pilot

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 15:25:21 +0200, John Stolz wrote:
> I think the step I'm missing is how to tell gnome-pilot that the sync is
> by network - its obviously expecting a port (/dev/pilot or whatever) -
> I've selected network sync, but what do I do for a port?

I don't use gnome-pilot. I use pilot-link. The pi-csd program is part of
that package.

All the pi-csd program does is create a network "device" for pilot-link to
use.

In my case, to install new files on my LifeDrive:
pilot-xfer -p net: --install ~/palm/install/*

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 12:32:50 -0400, General Schvantzkoph wrote:

> On Mon, 25 Jul 2005 16:39:01 +0200, John Stolz wrote:
>
>> On Mon, 25 Jul 2005 09:59:49 -0400, General Schvantzkoph wrote:
>>
>>> Gnomepilot will use ttyUSB0 or ttyUSB1. I suppose that if you have a lot
>>> of other USB devices, I only have a mouse, then it might use another port.
>>> If you plug your palm in, hit hot sync, and then check /var/log/messages
>>> you'll find which port it used.
>>
>> Sorry, I didn't make myself clear - I meant what do i tell gnome pilot
>> for a port when I sync by wifi?
>
> /dev/pilot
But /dev/pilot is a link to a usb port:

ll /dev/pilot
lrwxrwxrwx 1 root root 12 Jul 26 07:27 /dev/pilot -> /dev/ttyUSB1

I don't see how that relates to a network sync

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 16:51:18 -0400, Ranma wrote:

> I don't use gnome-pilot. I use pilot-link. The pi-csd program is part of
> that package.
>
> All the pi-csd program does is create a network "device" for pilot-link to
> use.
>
> In my case, to install new files on my LifeDrive:
> pilot-xfer -p net: --install ~/palm/install/*
Thanks, now I can list the files on the palm ('pilot-xfer -p net: --list'
lists 200+ files) but when I try and install files on the palm I get:

pilot-xfer -p net: --install docs/numbers.txt
Listening to port: net:
Please press the HotSync button now... Connected
Unable to open 'docs/numbers.txt
Time elapsed: 0:00:10

permissions for the file are:
-rw-rw-rw- 1 stolzy stolzy 2661 Jan 14 2004 docs/numbers.txt

Is something special in terms of permissions required to transfer files?
I'm not sure how to go from here to syncing contact/email etc in
Evolution. Evolution uses the same dialogs as gnome-pilot and insists on
a (numeric) port number - any idea what I should use?

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 08:02:50 +0200, John Stolz wrote:
> pilot-xfer -p net: --install docs/numbers.txt

numbers.txt is not a palm database and cannot be installed.

I assume that you want to place the text file on the internal drive. To
do that, simply connect your LifeDrive to the USB cable and turn on Drive
Mode.

On Mandrake 2005LE (which is what I use) the LifeDrive is mounted as
/mnt/LIFEDRIVE and I can drag/drop files to it.

Remember to give the Linux command "sync" before turning off Drive Mode to
make sure that Linux has finished writing any files.

> I'm not sure how to go from here to syncing contact/email etc in
> Evolution. Evolution uses the same dialogs as gnome-pilot and insists on
> a (numeric) port number - any idea what I should use?

I don't know how to do that. As I said, this is a pilot-link solution
only. JPilot won't work with the new formats of the LifeDrive either.

In my case, I only use my PC to backup/restore/install my LifeDrive, so I
never looked into something like Evolution.

Since they are changing JPilot to work with the LifeDrive, I assume that a
change to Evolution will also be required.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 07:29:21 +0200, John Stolz wrote:

> On Mon, 25 Jul 2005 12:32:50 -0400, General Schvantzkoph wrote:
>
>> On Mon, 25 Jul 2005 16:39:01 +0200, John Stolz wrote:
>>
>>> On Mon, 25 Jul 2005 09:59:49 -0400, General Schvantzkoph wrote:
>>>
>>>> Gnomepilot will use ttyUSB0 or ttyUSB1. I suppose that if you have a lot
>>>> of other USB devices, I only have a mouse, then it might use another port.
>>>> If you plug your palm in, hit hot sync, and then check /var/log/messages
>>>> you'll find which port it used.
>>>
>>> Sorry, I didn't make myself clear - I meant what do i tell gnome pilot
>>> for a port when I sync by wifi?
>>
>> /dev/pilot
> But /dev/pilot is a link to a usb port:
>
> ll /dev/pilot
> lrwxrwxrwx 1 root root 12 Jul 26 07:27 /dev/pilot -> /dev/ttyUSB1
>
> I don't see how that relates to a network sync

It doesn't, I thought you wanted to do a network sync because you couldn't
get the USB sync to work.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 16:51:18 -0400, Ranma wrote:

> I don't use gnome-pilot. I use pilot-link. The pi-csd program is part of
> that package.

And you should be using pi-nredir, or just pilot-link -p net:

pi-csd does absolutely nothing for OS5 and up devices.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 15:25:21 +0200, John Stolz wrote:

> I think the step I'm missing is how to tell gnome-pilot that the sync is
> by network - its obviously expecting a port (/dev/pilot or whatever) -
> I've selected network sync, but what do I do for a port?

gnome-pilot cannot be syncronized over the network. It does not support
it, unless you find someone with some third-party patches that enables
this.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 25 Jul 2005 05:20:26 -0400, Ranma wrote:

> I'm using Mandriva 2005LE and pilot-link-0.12.0-pre4.

Oh the irony, since the release notes for 0.12.0-preX have ALWAYS stated
that it should never be included in production distributions.

"DO NOT PACKAGE THIS UP TO PUT IN LINUX DISTRIBUTIONS! You have been
warned." (right off of the front page of pilot-link.org and in the -preX
release notes).

I guess Mandriva and Fedora packagers can't read English.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 05:47:08 -0400, Ranma wrote:

> On Tue, 26 Jul 2005 08:02:50 +0200, John Stolz wrote:
>> pilot-xfer -p net: --install docs/numbers.txt
>
> numbers.txt is not a palm database and cannot be installed.
>
> I assume that you want to place the text file on the internal drive. To
> do that, simply connect your LifeDrive to the USB cable and turn on Drive
> Mode.
>
> On Mandrake 2005LE (which is what I use) the LifeDrive is mounted as
> /mnt/LIFEDRIVE and I can drag/drop files to it.
>
> Remember to give the Linux command "sync" before turning off Drive Mode to
> make sure that Linux has finished writing any files.
>
>> I'm not sure how to go from here to syncing contact/email etc in
>> Evolution. Evolution uses the same dialogs as gnome-pilot and insists on
>> a (numeric) port number - any idea what I should use?
>
> I don't know how to do that. As I said, this is a pilot-link solution
> only. JPilot won't work with the new formats of the LifeDrive either.
>
> In my case, I only use my PC to backup/restore/install my LifeDrive, so I
> never looked into something like Evolution.
>
> Since they are changing JPilot to work with the LifeDrive, I assume that a
> change to Evolution will also be required.

OK, now I understand - looks like I'm stuffed - at least for the moment.
At least I learned to make sure these will things will work in advance of
purchase.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 15:34:31 +0200, John Stolz wrote:

>> Since they are changing JPilot to work with the LifeDrive, I assume
>> that a change to Evolution will also be required.
>
> OK, now I understand - looks like I'm stuffed - at least for the moment.
> At least I learned to make sure these will things will work in advance
> of purchase.

Your device works fine with Linux, the Evolution folks are about 18
months behind the rest of the applications. They haven't yet ported over
their code to work with the new API in pilot-link 0.12.0.

J-Pilot and KPilot (and of course, pilot-link) works great with the
latest version of pilot-link, with all devices up to and including the
LifeDrive.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 10:52:04 -0400, David A. Desrosiers wrote:
> Your device works fine with Linux, the Evolution folks are about 18
> months behind the rest of the applications. They haven't yet ported over
> their code to work with the new API in pilot-link 0.12.0.

My LifeDrive, on Mandriva 2005LE, using pilot-link 0.12.0-pre4 will lock
up my system tight if I try to sync via USB.

> J-Pilot and KPilot (and of course, pilot-link) works great with the
> latest version of pilot-link, with all devices up to and including the
> LifeDrive.

Which version of J-Pilot?

I thought it was you who said that J-Pilot wouldn't work properly with the
LifeDrive because Palm changed the database layouts.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 10:46:38 -0400, David A. Desrosiers wrote:

> On Mon, 25 Jul 2005 05:20:26 -0400, Ranma wrote:
>
>> I'm using Mandriva 2005LE and pilot-link-0.12.0-pre4.
>
> Oh the irony, since the release notes for 0.12.0-preX have ALWAYS stated
> that it should never be included in production distributions.
>
> "DO NOT PACKAGE THIS UP TO PUT IN LINUX DISTRIBUTIONS! You have been
> warned." (right off of the front page of pilot-link.org and in the -preX
> release notes).
>
> I guess Mandriva and Fedora packagers can't read English.

Who put it in a distro?

I downloaded the source, compiled it and am using it rather successfully -
the only issue is that syncing via USB doesn't work.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 10:35:58 -0400, David A. Desrosiers wrote:

> On Mon, 25 Jul 2005 16:51:18 -0400, Ranma wrote:
>
>> I don't use gnome-pilot. I use pilot-link. The pi-csd program is part of
>> that package.
>
> And you should be using pi-nredir, or just pilot-link -p net:
>
> pi-csd does absolutely nothing for OS5 and up devices.

pi-csd works just fine for my LifeDrive. Are you saying that pilot-link
0.12.0 doesn't need pi-csd to sync via the network?

pi-nredir doesn't seem to do the same thing.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 10:52:04 -0400, David A. Desrosiers wrote:

>
> Your device works fine with Linux, the Evolution folks are about 18
> months behind the rest of the applications. They haven't yet ported over
> their code to work with the new API in pilot-link 0.12.0.
Like I said, stuffed ;-) - all my contacts/calander etc are in evo and it
puts up a considerable struggle to let you get them out.

>
> J-Pilot and KPilot (and of course, pilot-link) works great with the
> latest version of pilot-link, with all devices up to and including the
> LifeDrive.
When you say the latest version, should that be pilot-link-0.12.0-0.pre4.2
or something later.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 10:52:04 -0400, David A. Desrosiers wrote:
>
> J-Pilot and KPilot (and of course, pilot-link) works great with the
> latest version of pilot-link, with all devices up to and including the
> LifeDrive.
Oops, that was a mistake.
I upgraded pilot-link, J-Pilot and KPilot and the requested dependancies
and now whereas this used to happen:
pilot-xfer -p net: --list
Listening to port: net:

Please press the HotSync button now... Connected
..
..
.....and a list of files

now:

pilot-xfer -p /dev/pilot --list
or
pilot-xfer -p net: --list

causes:

pilot-xfer: relocation error: pilot-xfer:
symbol __printf_chk, version GLIBC_2.3.4 not defined in file libc.so.6
with link time reference

I have absolutly no clue what that might mean - can anyone enlighten me?

Archived from groups: comp.sys.palmtops.pilot (More info?)

> My LifeDrive, on Mandriva 2005LE, using pilot-link 0.12.0-pre4 will lock
> up my system tight if I try to sync via USB.

That's a kernel bug. Report it to Mandriva's kernel maintainers.

*NOTHING* in userland should lock up hardware. If it does, its a kernel
bug.

>> J-Pilot and KPilot (and of course, pilot-link) works great with the
>> latest version of pilot-link, with all devices up to and including the
>> LifeDrive.
>
> Which version of J-Pilot?

J-Pilot 0.99.8 should work fine, Judd is up to 0.99.8-pre9 already.

> I thought it was you who said that J-Pilot wouldn't work properly with
> the LifeDrive because Palm changed the database layouts.

No, thats the data side of things. From a connectivity standpoint, your
LifeDrive should work perfectly fine.

Because Palm neglected to document the changes in their new PIM database
structures, everyone has had to reverse-engineer the formats
byte-by-byte, which isn't exactly the fastest way to understand their
changes. Since that isn't a high-priority for us, we are focusing on
other things like device support and better protocol robustness.

Somewhere along the 0.12.0 line, we'll figure out the db formats and get
something coded up.

Palm is going to change them again on us to a "Schema" format, which I
seriously hope they begin documenting.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 17:55:58 +0200, John Stolz wrote:


> pilot-xfer: relocation error: pilot-xfer:
> symbol __printf_chk, version GLIBC_2.3.4 not defined in file libc.so.6
> with link time reference
>
> I have absolutly no clue what that might mean - can anyone enlighten me?

Looks like your Linux distribution maintainers broke the pilot-link
package (they did this on Fedora Core 4 that we know of already).

The source works fine, from pilot-link.org, and you won't see those
issues (unless some other underlying library on your system is broken).

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 17:22:43 +0200, John Stolz wrote:


>> J-Pilot and KPilot (and of course, pilot-link) works great with the
>> latest version of pilot-link, with all devices up to and including the
>> LifeDrive.
> When you say the latest version, should that be
> pilot-link-0.12.0-0.pre4.2 or something later.

I should say.. the latest release versions of J-Pilot and KPilot work
perfectly fine with the 0.12.x pre-release series of pilot-link. To
ensure that you get the most-reliable, fastest version.. make sure you're
running the latest pilot-link version, in this case 0.12.0-pre4.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 16:59:18 -0400, Ranma wrote:


> pi-csd works just fine for my LifeDrive. Are you saying that pilot-link
> 0.12.0 doesn't need pi-csd to sync via the network?
>
> pi-nredir doesn't seem to do the same thing.

It never has, and probably never will. In 7+ years of using and
writing and most-recently maintaining pilot-link, I have never ONCE found
a reason to run pi-csd at all, in any way.. (and I wrote the HOWTO on Palm
Network HotSync).

If it works for you, great, but it probably isn't doing what you
think it is.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Tue, 26 Jul 2005 16:56:04 -0400, Ranma wrote:

> Who put it in a distro?

Fedora and Mandriva that we know of so far. In doing so, they
added some wacky patches to it and broke a completely functional source
tree.

> I downloaded the source, compiled it and am using it rather successfully
> - the only issue is that syncing via USB doesn't work.

I suspect a misconfiguration on your end. Try using -pre5 sitting
in HEAD of CVS to see if it works better. Some recent changes were added
that add better LifeDrive protocol detection.

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Wed, 27 Jul 2005 00:15:50 -0400, David A. Desrosiers wrote:

> On Tue, 26 Jul 2005 17:55:58 +0200, John Stolz wrote:
>
>
>> pilot-xfer: relocation error: pilot-xfer:
>> symbol __printf_chk, version GLIBC_2.3.4 not defined in file libc.so.6
>> with link time reference
>>
>> I have absolutly no clue what that might mean - can anyone enlighten me?
>
> Looks like your Linux distribution maintainers broke the pilot-link
> package (they did this on Fedora Core 4 that we know of already).
>
> The source works fine, from pilot-link.org, and you won't see those
> issues (unless some other underlying library on your system is broken).
OK, built it from source, and now it runs, but:
'pilot-xfer -p /dev/pilot --list' just sits and waits for a connection to
the palm.

'pilot-xfer -p net: --list' on the other hand lists the files on the palm.
Is this just something in the 'known to be flakey' usb subsystem of MDK
10.1 or a problem in palm-pilot?

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Wed, 27 Jul 2005 11:01:24 +0200, John Stolz wrote:
> OK, built it from source, and now it runs, but:
> 'pilot-xfer -p /dev/pilot --list' just sits and waits for a connection to
> the palm.

That's because it's looking for the Palm to talk on /dev/pilot. There's
nothing special about /dev/pilot except that it's a symlink to the real
device (like /dev/ttyUSB0). Now, depending on your Palm, it may sync on
ttyUSB0 or ttyUSB1 - and /dev/pilot may be symlinked to the wrong device.

> 'pilot-xfer -p net: --list' on the other hand lists the files on the
> palm. Is this just something in the 'known to be flakey' usb subsystem
> of MDK 10.1 or a problem in palm-pilot?

No. The /dev/pilot stuff is a serial-emulation-via-USB type of thing. A
driver is loaded to make a device that LOOKS like a serial port, but talks
to a USB port.

The usb subsystem uses the device "usb:". I still haven't gotten it to
work on my box yet.