I was not able to get Yaron Tausky's setup to work, but the following seems to be reliable. Fedora Core 4
/etc/udev/rules.d/20-ipaq.rules: DRIVER="ipaq", SYMLINK="ipaq", GROUP="uucp", MODE="0660", ACTION="add", RUN="/etc/udev/scripts/ipaq-add.sh" ========================================= end of /etc/udev/rules.d/20-ipaq.rules /etc/udev/scripts/ipaq-add.sh: #!/bin/bash export PATH=/sbin:/bin:/usr/sbin:/usr/bin # export LOGFILE=/var/log/synce export LOGFILE=/dev/null echo "`date +"%b %d %X"` `uname -n`: iPAQ plugged, starting connection..." >> $LOGFILE /usr/bin/synce-serial-start >> $LOGFILE 2>&1 ======================================== end of /etc/udev/scripts/ipaq-add.sh This technique also solves my problem of having a usb ipaq and a usb visor: By not specifying the NAME attribute the udev creates the device node under the default name, in my case ttyUSB%n. By specifying my SYMLINK as "ipaq", and for the visor specifying "visor", I no longer have to worry about the order I plug them in. synce uses /dev/ipaq and kpilot uses /dev/visor and the applications don't care that the real device nodes vary in name depending on the order I plug them in. I put a button on my panel to start dccm. ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Synce-devel mailing list Synce-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
