Arch Linux

fowler

Member

Registered: 2009-01-26

Posts: 152

Other udev problems on boot after kmod update...

I looked for a similar issue in the forums but I don't see any... so I get the following warning when I boot with udev:

Mon Jan 23 09:18:49 2012: :: Loading User-specified Modules    [BUSY] udevd[347]: RUN+="socket:..." support will be removed from a future udev release. Please remove it f

Any ideas?  Can I provide any other useful information?

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: Other udev problems on boot after kmod update...

find /etc/udev/ /lib/udev/ -name '*rules'| xargs grep -l 'RUN+="socket' | xargs pacman -Qo

Try to find an update for that package, or post a bug report.

---

1000

fowler

Member

Registered: 2009-01-26

Posts: 152

Re: Other udev problems on boot after kmod update...

$ find /etc/udev/ /lib/udev/ -name '*rules'| xargs grep -l 'RUN+="socket' | xargs pacman -Qo
/lib/udev/rules.d/90-hal.rules is owned by hal 0.5.14-6

I guess that means I should uninstall hal since it is deprecated?

lagagnon

Member

From: an Island in the Pacific...

Registered: 2009-12-10

Posts: 1,087

Website

Re: Other udev problems on boot after kmod update...

I get the same error, however I don't think I can uninstall hal because it depends on "ivman" which in turn uses "consolekit" which I require for my .xinitrc "ck-launch-session dbus-launch wmii". Is there any way around this mess?

---

Philosophy is looking for a black cat in a dark room. Metaphysics is looking for a black cat in a dark room that isn't there. Religion is looking for a black cat in a dark room that isn't there and shouting "I found it!". Science is looking for a black cat in a dark room with a flashlight.

Gusar

Member

Registered: 2009-08-25

Posts: 3,605

Re: Other udev problems on boot after kmod update...

I'm not sure, but I think there are successors to ivman out there that don't require hal. Or you'll have to switch to some other device manager, like say udiskie or something.

But just to be clear, there is no "mess" here. HAL has been declared deprecated a long time ago. While it did receive some patches last year, so it's not completely unmaintained, adjusting it to use libdev instead of a socket seems like a big change, so big that I doubt it'll be made. Kinda shame, I still use hal too, but this was bound to happen sooner or later.

And another thing: For now this is just a warning, not an error. But that future that the message mentions will come, so use the time until then to find another device manager.

tarun.hellknight

Member

From: India

Registered: 2010-11-30

Posts: 65

Website

Re: Other udev problems on boot after kmod update...

Getting the same error here. I was thinking of removing HAL but the Arch Beginner's Guide mentions that hal should be present in the daemons section of the rc.conf file. I'm really confused regarding this subject.

karol

Archivist

Registered: 2009-05-06

Posts: 25,440

Re: Other udev problems on boot after kmod update...

I was thinking of removing HAL but the Arch Beginner's Guide mentions that hal should be present in the daemons section of the rc.conf file.

Link please.

hleung

Member

Registered: 2011-01-10

Posts: 20

Website

Re: Other udev problems on boot after kmod update...

HellKnight,

I haven't put hal in the list of daemons in /etc/rc.conf, and I've never got any problems.  I ran into this "warning message" (since it's not really an error but a reminder) because I did install HAL recently for SynCE.  I just removed HAL, and I can confirm to you and to everyone here that I don't have that "message".

As for SynCE, well, I guess I'll try to get my hands on ActiveSync to work with Wine.

---

Everyone has their own belief, and that belief becomes their own religion.
My bible = "Rapture for the Geeks " by Richard Dooling