Re: USB Visor cradle and gnome-pilot?

["eric a . Farris" <eafarris al umces edu>]

On Thu, Jun 08, 2000 at 05:29:57PM -0700, Eskil Heyn Olsen wrote:
> Isn't the problem that the port "appears" when the sync button is pressend, and
> "dissapears" when the sync is over ?

yes, this is what happens. isn't that the nature of USB, that devices get
'created' and 'destroyed' on demand?

> gpilotd would register this during startup as the device being unavailable.
> Also, if this is the case, you'd would be running pilot-link after pressing
> sync, what happens if you run pilot-link before ?

again, correct. gpilotd will complain that /dev/ttyUSB1 (or the link to
it, /dev/pilot) does not exist. pilot-xfer says "Unable to bind to port
'/dev/pilot'." if it is run without a hotsync active from the cradle. The
work-around is that you have to start the sync from the cradle before
running pilot-*. don't know if a trick like that would work for gpilotd,
say, starting a sync and then typing startx. it might be enough, though,
if gpilotd just didn't complain about the port not being there when
it started.

-- 
eric a. Farris  eafarris@al.umces.edu  www.bigfoot.com/~eafarris
Systems Administrator
Appalachian Laboratory, UMCES  www.al.umces.edu

Linux: From each according to his ability, to each according to his need.

Do whatever you want, but be prepared to accept the consequences.