Hello, I noticed that the lfs bootscripts changed to echo /sbin/udevsend into /proc/sys/kernel/hotplug instead of /sbin/hotplug.
Does hotplug ever get called anymore in this case? My problem is with my digital camera. It does not have a /dev entry. When I plug it in, a new entry is created in /proc/bus/usb along with some very hidden usb entry in the /sys filesystem usually /sys/class/usb_host/usb2/device/usb2/2-1 or something to that effect. That is all that happens when the camera is plugged in. On my old system when /sbin/hotplug was used, the usb scripts properly found the /proc/bus/usb entry and my usbcam script properly set the permissions so I could use the camera as my normal user. I have always used gphoto and it seems to communicate to the camera through this /proc entry. Now that /sbin/udevsend is used, nothing is happening. My usb hotplug scripts are never called and udevinfo prints nothing about a camera device. So I have a few questions about how to best solve this. Why was the switch made to use /sbin/udevsend? On my old system using /sbin/hotplug, buth udev and hotplug worked great. Now hotplug does not seem to work. Can I switch back to /sbin/hotplug? Will there be any adverse effects? Is there a better way to get my digital camera to work than using hotplug with a usbcam script? Perhaps a udev rule (The camera never used a /dev entry in the past at all, so I don't know if this is possible) ? I read the udevsend manpage and it seems that udevsend is supposed to be called by hotplug, but that doesn't seem to be happening. Is there a way to get use /sbin/hotplug and have it call udevsend or even have /sbin/udevsend call /sbin/hotplug so both tools can work? Thanks, Kareem -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
