Hi,
My Debian System State before upgrading to etch:
Mix System (sarge(stable) + etch(testing) with custom built 2.6.15 kernel.

After upgrading:
Only Debian etch(stable). No Mix system. Kernel still the same: 2.6.15.

As soon as I rebooted my system after upgrading, my system hangs saying:
What do I do? Do I really need to upgrade my kernel also to 2.6.18-4 that is the default with Debian Etch(stable). Is this because I still may have the hotplug package installed? Do I need hotplug and udev both?

Plese advice.

I believe if you run the 2.6.15 kernel with etch udev is broken......stabel etch is with 2.6.18...

Anyone??????

Have you tried running the update-initramfs (or what's it called?)?

You gotta do this after changing udev...

You could try installing etch's kernel, your kernel will still be available on the grub menu.

And no udev and hotplug should not be on the same system. udev actually conflicts with hotplug and should have been automatically removed when you upgraded. Maybe something went wrong with the apt-get dist-upgrade?

Thank you guys for your responses. Here is what I found. I had to give the command:

in order to get my system to boot again. So basically once I finish upgrading my system I had to give the above command before booting the system otherwise, it will show the error messages (as mentioned in my first post) after booting.

It seems that udev does not like initrd to be created with initramfs tool, instead it likes the old tool better which is mkinitrd.

now, I went one step further and installed the default etch kernel 2.6.18-4-686. Everything with this kernel works no matter if I use the mkinitrd (old) tool or the mkinitramfs (new) tool.

Can anyone tell me what is going on? What is the relationship between udev, kernel version and initrd generator tool?

Thanks

anyone????

It seems simple to me. Old kernel needs Old mkinitrd. New kernel works with new initramfs tool and is backwards compatible with old tool mkinitrd. I could be wrong though.