I just noticed that Patrick has posted an update to udev-054 that should fix our permission problems. The update is udev-054-i486-2.tgz. See the current changelog for more info:

ftp://ftp.slackware.com/pub/slackwar.../ChangeLog.txt

I upgraded to this package and I still get the same prob with /dev/null permissions. I don't know hoaw to properly edit udev.rules etc. to fix this prob so have rolled back to udev-050.

That's strange. The new udev-054 fixed everything for me -- device permissions reset to 666, and my problem with var/run/atd.pid, also.

Let's see what others say. Maybe there's a secondary problem that you're having.

I have to edit the files:
and
but I don't see how that would cause a prob with /dev/null. The changes I make are outlined here

Hmm ... looks like a glitch in the Matrix.

No, in truth, I don't know what that's all about. I'm just glad you have a fix. So this is a problem that you had with udev previously, and you have to keep re-fixing it every time you update udev, right?

yep, but with the current release of udev /dev/null is incorrectly assigned. The original files I use are from and earlier version of udev (i just copy the files to the relevant places). Maybe I should do a clean edit of the new udev-054 files.

You may want to have a look at a post on alt.os.linux.slackware. If you read this group already, it's dated 7 March 2005, has the subject "udev-054" and was posted by "accdias". It may have some useful info if you're going to edit rules under new udev.

For some reason this post hasn't shown up on Google Groups yet.

A bit embarrased to ask this but how do I look at that site?? I've never been near it before.

Actually, after looking at his post again, I think the guy just pasted in his modified udev.rules file. I thought that he'd included some explanatory comments, but he didn't really. So I don't know how helpful this would have been to you.

alt.os.linux.slackware is a Usenet newsgroup which you have to access by using a newsreader (Pan, for example) to log on to a Usenet server (some are free, most charge a monthly fee). Or you can use Google Groups to search the group. The latter is simpler, if you haven't used Usenet before. Just go to groups.google.com. If you know the name of the group you want to search, you can type it in and you'll see a list of the recent posts, e.g., "alt.linux.os.slackware". If you want to search all the groups to which Google has access, you can just type in your search terms rather than going to a particular group.

One problem is that Google Groups usually lags behind a bit, so you don't always see the latest posts. In this case, I don't think they've updated alt.os.linux.slackware recently, because I couldn't find the post I wanted to refer you to. Either that or Google's listing is incomplete somehow.

BTW, I assume you're fooling around with udev on your machine that has a 2.6.x kernel, right? The 2.4.x kernel doesn't support udev at all, I don't believe.

of course I'm using the 2.6.x series.

Thanks for your help. I've upgraded to the new udev on my laptop (with 2.6.11-cko1) and on a mates pc (also with 2.6.11-cko1) and it works fine there. I must have made a mistake somewhere. The instructions in that other thread worked with every upgrade before.

I'll give google groups a look, thanks for the tip.

The new udev package (udev-054-i486-3.tgz) has completely fixed my problems. Yippee.

Did you even have to edit your rules files or whatever it was you had to do before? Or did the latest udev take care of all of that for you?

Good news either way.

no I didn't have to edit the files. I was about to edit the files but I noticed a couple of changes in the script make_extra_nodes.sh that looked like they'd fix my system and they did. I'm so happy right now. I have another system to maintain that has the same problem so this has just made my life a little easier.

Mmmm, I am now tempted to try and upgrade to it.