Slackware current with 2.6.16.22 kernel from "testing" a few weeks ago. Upgraded to udev096 and some other packages. (At least one missed as it could not be found)
Multi boot PC with all of Slack in a single partition - hda7

Now on boot after reiser checks the partition and moves on to fsck 1.39 followed by
"Failed to open the device '/dev/hda7': No such file or directory"

The boot then goes to a single user rescue mode.
If I enter the root password I can see the file system is there except for the contents of /dev which only has a initcl file and a file called null.

Mounting the drive on another machine allows access to the data without problems.

I spotted the .new files in rc.d and copied them over.
Now boot gets to the /dev/urandom line and locks up, where INIT runlevel 3 would normally go.
Nothing much showing in logs

Exact same problem I was having:

http://www.linuxquestions.org/questi...d.php?t=471812

So far, the only thing I have been able to do is boot the machine with a LiveCD, or the install CD, and chmod -x /etc/rc.d/rc.udev.

This will get the machine to boot, but I can't figure out how to get udev working again.

I will have a look at udev tomorrow.
What kernel are you running, I was thinking that I should update to 2.6.16.27 if I can get the machine to boot from its own drive.
This is the first major snarlup that I have had with current for ages, not good just before the 11.0 release.

I could reaaly do with a simple summary of what should and should not be running with 2.4, 2.6.16 and 2.6.17+ kernels

Running -current with 2.6.15 here. Had no problems although I had a few .new files to rename. I also notice on boot that hotplug is no longer running so I think everything is working as it should.

All I can think is check the changelog for any new packages you might have missed.

I'm running 2.6.12 on my machine.

Today's -current changelog has this comment from Pat:

"There are a few reports that the newest udev is not friendly to some systems.
Well, that's progress for you -- it isn't always a smooth journey. In most
cases the problems I've heard about could be fixed with a little bit of fine
tuning, such as blacklisting unwanted modules in /etc/modprobe.d/blacklist
and loading the desired replacements in /etc/rc.d/rc.modules. However, in
case either of these older versions of udev worked better for you, they'll
be kept in /extra for a while as alternates. Be aware that new kernels will
soon require the latest udev, though...
extra/udev-alternate-versions/udev-064-i486-2.tgz: Added alternate udev-064.
extra/udev-alternate-versions/udev-071-i486-2.tgz: Added alternate udev-071."

So, apparently you aren't alone...

Not a very useful changelog comment, this problem stops booting so reverting udev is not an immediate option.
I don't see any obvious module problems, but on this machine I have serveral rc.modules.2.6.16.x files and a symlink r.modules pointing at an old version. I used to have to manually enable lp and parport on 2.4 kernels, but 2.6 seems to handle these automatially.

There was also this:

"a/udev-096-i486-2.tgz: Added the psmouse module to /etc/modprobe.d/blacklist
so that /etc/rc.d/rc.modules can load it using the option "proto=imps".
This change restores the mouse options used in Slackware 10.2. At least on
my machine, the default module options render the mouse completely unusable,
but feel free to remove the module from the blacklist or configure rc.modules
to your liking if this is not the ideal default for your machine."

So, udev has already gone -2. I've installed the update, but I haven't rebooted yet. I'm going on vacation tomorrow, so this isn't the kind of problem I'd like to deal with tonight. Looks like before I shutdown though, I should probably make sure all my .new's in /etc/rc.d are moved over.

Okay, so that was briefly exciting...

I should not have been so smug about not figuring this udev stuff out until after my vacation. About an hour ago, we had a brief power burp, and my machine rebooted - right into udev purgatory.

Looks like I am back up now. I ended up using my slack 10.2 CD as an emergency disk, changed all the .new's to their respective rc.* scripts and rebooted. Had to set up rc.inet1.conf and start rc.inet1 and rc.inet2 again, but it worked.

Now, I think I will wait until after my vacation to assess what's changed.

i didn't upgrade -2 also. I'm quite satisfied with the current udev configuration

Now fixed.
I found that there was a rc.udev.new so I replace the older rc.udev with this and I was able to boot.
Then upgraded to 2.6.16.27 without any extra problems
I see warnings about the alsa driver codec being invalid, but sound is working

i upgraded to -3 also last night and put the .new on the rc.udev and i had no problem at all when i reboot my system.

NB : Kernel version 2.6.17.8