C.Y.M wrote:
> I have a feeling that the last bug I reported on udev (#321033) is directly
> related to this change (#318313). When hal uses the RUN udev rules instead of
> the hotplugd.d and dev.d scripts, DEVNAME and SEQNUM do not get set, which
> causes the following errors:
>
> hal.dev[29779]: DEVNAME is not set
> hal.hotplug[12776]: SEQNUM is not set
>
> I especially notice the errors in the syslog when iptables and dvb devices are
> loaded.
>
Im not sure if this is right, but it fixes the problem for me:
--- hal.udev.rules 2005-08-06 04:05:56.000000000 -0700
+++ /etc/udev/hal.rules 2005-08-06 04:28:29.000000000 -0700
@@ -1,6 +1,12 @@
# hotplug.d and dev.d are obsolete, so simulate calling of the hal helpers
+
+if ! [ "ENV{DEVNAME}" = "" ]; then
ENV{UDEVD_EVENT}=="1" RUN+="/usr/lib/hal/hal.hotplug"
+fi
+
+if ! [ "ENV{SEQNUM}" = "" ]; then
ENV{UDEVD_EVENT}=="1" RUN+="/usr/lib/hal/hal.dev"
+fi
# unmount block devices when they are removed
ENV{UDEVD_EVENT}=="1", SUBSYSTEM=="block",ACTION="remove",
RUN+="/usr/lib/hal/hal-unmount.sh"
When I look at the code in hal_dev.c (for example), all it is doing is this:
--SNIP--
devname = getenv ("DEVNAME");
if (devname == NULL) {
syslog (LOG_ERR, "DEVNAME is not set");
goto out;
--SNIP--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
