I wrote:
+ <sect3>
+ <title>Udev creates a device incorrectly, or makes a wrong
symlink</title>
+
+ <para>This usually happens if an incorrect rule unexpectedly matches
+ the device, or some rule unexpectedly matches the wrong device. E.g.,
+ a poorly-writen rule can match by vendor both a SCSI disk (as desired)
+ and the corresponding SCSI generic device (incorrectly). Increase
+ the logging verbosity of udev, find the offending rule by examining the
+ logs and make it more specific.</para>
+ </sect3>
As written, this is incorrect. Increasing the logging verbosity achieves
nothing, because udev runs before syslogd. Proposed solution:
1) Implement some "restart" target in the udev initscript that kills old
udevd, starts a new one, pokes sysfs and waits for udev to process
uevents. This would be also useful for Suspend2, BTW.
2) Tell the reader to increase the logging verbosity and call this
target, so that everything gets logged.
Two more bugs:
1) ">/proc/sys/kernel/hotplug" doesn't unset the default hotplug
handler. You need "echo", in order for the kernel to see the terminating
newline.
2) No /dev/bus/usb rule
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
