Hi all,

I upgraded my udev-050 to udev-054 yesterday (official packages). Today when I get my machine up again, oops, most of my programs got either "segmentation fault" or "no such file and directory". I have done nothing besides upgrading packages, so I fall back udev to udev-050. Bingo, Slack rocks again~!


Did anyone drop an email to Pat about this matter?

Thanks.

I'm not a slack user, but did you do anything to determine how udev-050 and udev-054 differed to cause these problems?

The two things I've seen regarding possible udev-054 problems are these:

(1) Change of permissions on some devs (notably null, tty, dsp) from 666 to 660.

(2) Failure to start the atd daemon, with this error message at bootup:
"Can't open var/run/atd.pid to signal atd. No atd running?". In fact, var/run/atd.pid isn't created when you have udev-054 installed (according to reports).

In both cases, reverting to udev-050 returned things to normal.

Do you think your problem could be related to number 1 above?

At any rate, I know that a report has been filed with Patrick.

I've been hit by the change of permissions problem (everything works a-ok as root). Rolling back did the trick and fixed my systems.

I can attest to this as well... i just reverted to 050 and everything is rosy.

Same here. I tried to figure out what causes the problems, but without success.

I would believe my problem is related to (1).
When I start my mozilla products, "Segmentation fault" + "cat /dev/null : Permisson denied" sth like that.

I should check the permission first, tough.

Hopefully pat will correct it ASAP.

Someone on alt.os.linux.slackware said that the problem is due to the fact in recent releases of udev (since udev-051, I think he said), udev has set permissions directly in udev.rules. Previously this was done in udev.permissions, apparently. The format of the two files is different, but it shouldn't be that hard to transfer the info from your udev.permissions into udev.rules.

Or you can just wait a couple of days (or less) while Pat and friends get things straightened out.

Oh this went unnoticed for me. Have been using root account all this while

Will try my dusty user account out later. I guess I got to roll back as well.

I am running udev-054 and have not noticed any problems yet. I am running the default "current" kernel, not 2.6.x

The reason you aren't experiencing this udev "problem" is because udev doesn't run on the 2.4.xx kernel.

Later,
MMYoung

Had same problem tried editing udev.rules and udev.permissions, to no availe. Removed 54 and installed 50 fixed.