On Thu, Feb 16, 2006 at 05:54:38PM +0100, Volker Christian wrote:
> On Thursday 16 February 2006 13:53, Sjoerd Simons wrote:
> > Imho the correct solution for hal is not to probe USB serial ports. The
> > only reason for the serial port prober is that you can't know if /dev/ttyS3
> > actually corresponds to a real device. But that's not an issue for USB.
> I agree, this is not really an issue for USB. I think this is a todo for
> upstream, isn't it? :-)
Yeah.
> >
> > Now i must admin that i don't know a lot about how synce works, but it's my
> > opinion that hal should remain a facts database and shouldn't start
> > triggering system setup programs. That should be done on a higher level.
> I agree also. But unfortunately, i am not a udev/hal expert. Could you please
> give me some hints how i could automate this triggering at a higher level? I
> am willing to integrate this in the synce software.
>
> Desired behaviour:
> ===========
> Everytimes a pda is connected to an usb-port a special command
> (synce-serial-start) should be called - this initiates a ppp-connection.
> Everytimes a pda is disconnected from the usb-port an other command
> (synce-serial-abort) should be called - this shuts down the ppp-connection.
This would mean you need to create a small daemon to manage synce devices,
which does the following:
* On startup, search for pda devices in hal's database, if a valid one is
run start synce-serial-start
* After that, listen for device-added events from hal. If such an events adds
an pda then also start synce-serial-start
Sjoerd
--
All Finagle Laws may be bypassed by learning the simple art of doing
without thinking.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
