Re: [coldsync-hackers] Re: Problem respawning coldsync daemon

[Greg KH <greg at kroah dot com>]

On Mon, Mar 04, 2002 at 10:04:37AM +1100, Andrew Bainbridge-Smith wrote:
> The process happens like this:
> 1. Press hotsync button on cradle: this triggers the kernel to hotplug
> in the various kernel modules (visor.o, m500.o etc)

There is no m500 module, the visor module handles all Palm OS devices.

> 2. Coldsync does it hotsyncing stuff
> 3. Call to Palm to finish communications as a part of the shutdown
> procedure.
> 4. Palm cradle triggers the kernel to hot-unplug the various kernel
> modules, occurs at some asynchronus time.

No, the modules do not ever get unloaded.  The device disconnects itself
from the USB bus, and then /sbin/hotplug gets called with a USB REMOVE
event.

> A second point.  It occured to me that it may be possible to use this
> hotplugging facility in a much better way.  I understand that when a
> device is hotplugged it can call a script, perhaps this script could
> then call coldsync to do its stuff.  With this approach one doesn't need
> to run coldsync as a daemon (avoiding a process running which has to
> continually poll the USB).

Here's a nice small replacement for /sbin/hotplug that will do just
that, syncing a visor with coldsync:
	http://www.kroah.com/linux/hotplug/ols_2001_hotplug_talk/html/mgp00013.html

So yes, it is quite easy to do this :)

thanks,

greg k-h

-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.