Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3684 - udev runs hal too early

Attached to Project: Arch Linux
Opened by Kurt Basil Cox (basilburn) - Sunday, 01 January 2006, 08:33 GMT
Last edited by Jan de Groot (JGC) - Sunday, 01 January 2006, 11:02 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

udev tries to run /usr/libexec/hal.hotplug too early in the boot process. If /usr is a separate mountpoint ...say an lvm2 logical volume, this fails with error messages to the console.

This is initiated by /etc/udev/hal.rules which belongs to the hal package so I guess its a hal bug.

One could check for the existence of hal.hotplug before trying to run it but its not possible to use /usr/bin/test before /usr is mounted and a second option would be using the builtin test in /bin/sh but its probably not a good idea to run /bin/sh on every event that is generated by udev.

This is minor as it doesn't seem to affect the function of udev or hal just nasty messages to the console until /usr is mounted.
(application/octet-stream)    hal.rules (0.1 KiB)
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 05 January 2006, 11:41 GMT
Reason for closing:  Fixed
Additional comments about closing:  hal-5 fix it
Comment by Tobias Powalowski (tpowa) - Sunday, 01 January 2006, 18:47 GMT
hi could you try changing hal.rules to:
RUN+="/usr/libexec/hal.hotplug > /dev/null 2>&1"

and please report if it helps, thanks
Comment by Kurt Basil Cox (basilburn) - Tuesday, 03 January 2006, 05:05 GMT
Nope, I tried that line. Redirecting to /dev/null doesn't do it either.

I still get the error.

"udev-event: Can't exec /usr/libexec/hal.hotplug, no such file found"

These messages appear right after starting up udev and persist until the /usr lv is mounted. In all, the message repeats 5 times.

unfortunately, its too early during bootup to get this info in the logs.
Comment by Tobias Powalowski (tpowa) - Tuesday, 03 January 2006, 07:55 GMT
an other idea:
could you try this, change /etc/start_udev to:
/sbin/udevstart > /dev/null 2>&1
and/or
/sbin/udevd --daemon > /dev/null 2>&1
Comment by Kurt Basil Cox (basilburn) - Thursday, 05 January 2006, 04:05 GMT
I still get the same error msgs. There doesn't seem to be anyway to turn off udev console logging.

Oh, well. I will just see if the hal.rules can be hacked to work arooung this.
(application/octet-stream)    start_udev (2.8 KiB)

Loading...