[jp] ln -sf /dev/ttyUSB* /dev/pilot

> Are you sure "ln -sf /dev/ttyUSB* /dev/pilot" will work.  My guess 
> is that it will not work.  Trying to link multiple ttyUSB devices to 
> one /dev/pilot seem like it would confuse the system/link.

 	It would simply fail. The right method would be to fix the 
problem, not try to trick the kernel into sending bytes to two 
separate ttys at the same time (not even sure if that's possible, 
but..)

> Also the "http://www.pilot-link.org/README.usb" seems to be a bit 
> dated with the latest systems and "udev"

 	Dated how? If something needs to be added/removed/changed, 
please let me know so I can update the master copies. Quite a lot has 
been added to the HOWTO in the last couple of releases:

 	http://tinyurl.com/y4d7gf

> I am always looking at others ideas as away to gather info. 
> However, udev/hal/kernel options/"god only knows" seems to install 
> and remove devices at will.

 	This is precisely how they're supposed to function. Devices 
are added dynamically, in /dev/.

> In SuSE 10.2 you have lsusb, hwinfo -usb and the good old lsmod to 
> track down USB devices but I am unable to find and maintain the 
> correct major/minor numbers to add to modprobe directive like the 
> README.usb suggest.

 	You'll want usbview, most-likely, written by Greg Kroah, 
maintainer of the visor driver and the entire USB subsystem (now I 
think he owns the whole module subsystem in Linux, actually).

> Anyone have a good way to add this without solid numbers to 
> /etc/modprobe.conf, /etc/modules.conf (legacy) or /etc/modprobe.d/ I 
> think udev is putting them in /dev as 180,0 however, they come and 
> go. Adjusting the release time might also be helpful.

 	Are you confusing device node major,minor numbers (which has 
nothing to do with modprobe at all) with actual Palm device values 
(which modprobe can use for devices not supported directly by the 
visor module)?

 	As the HOWTO suggests, when you're running a 2.4.x kernel or 
one that probably doesn't use udev to dynamically create devices, you 
have to create them manually.

 	IF YOU RUN udev (!!) and you find that your devices are not 
being created, the solution is NOT to create them manually, but to 
find and fix the underlying udev disconnect that would stop the 
devices from being created properly.

 	Creating a device node in /dev/ for a device the kernel and 
udev still don't recognize, won't magically force that non-working 
detection and connection to work.

> At boot time if added to modprobe.conf I think I will get a boot 
> error that no device is found at 180.

 	I don't know of any Palm device that claims that number:

 	http://www.pilot-link.org/DeviceMatrix

 	Or are you referring to the device node values? If so, these 
should be 188,[10], not 180 (188,0 and 188,1 respectively)

 	With all of the recent messages and people trying hack-n-slash 
techniques at the wrong symptoms, I think its time for a very, VERY 
detailed walkthrough for everyone to follow. This is all VERY simple 
to get working, unless you have a.) broken/damaged hardware, or b.) a 
misconfiguration [which can be fixed].


David A. Desrosiers
desrod at gnu-designs.com
http://gnu-designs.com