I upgraded my kernel from 2.4.33.3 to 2.6.16.9 under Slackware 11. Ever since then, when I start the computer I get a string of these messages when udev starts.
udevd-event[1136]: udev_node_symlink: symlink(vcc/2, /dev/vcs2) failed: File exists
udevd-event[1137]: udev_node_symlink: symlink(vcc/a2, /dev/vcsa2) failed: File exists
udevd-event[1138]: udev_node_symlink: symlink(vcc/3, /dev/vcs3) failed: File exists
udevd-event[1139]: udev_node_symlink: symlink(vcc/a3, /dev/vcsa3) failed: File exists
udevd-event[1140]: udev_node_symlink: symlink(vcc/4, /dev/vcs4) failed: File exists
I just posted 5 of these messages. There actually about a screen and a half of them. Why might this be happening? Thanks.

Supposedly, udev's device nodes are not supposed to survive the next reboot. I have Slackware 11 installed on two partitions. One is a stable Slackware 11 the other one is for testing and creating packages. Anyways, I looked at the /dev directory on the stable linux partition while using the unstable linux partition. The directory was filled with nodes from the last boot. Is this normal? Why are there so many nodes? There are even nodes that I don't use like loop0 through loop9. Because I haven't loaded any loopback device drivers, those nodes shouldn't be there. What is the problem?

I'm bumping this up to the top again, please help

I'm not familiar with Slackware but in general the udev device system hasn't taken over management of all devices. For example the loop devices absolutely should be there. They are managed by the devfs device management system. Many other traditional devices are also still managed by the old system.

You can find out about how udev is working on your system by finding the udev configuration file(s). If you have updatedb running you can use the locate utility to find all of the files that include the string udev. This will show you a ton of files. All or almost all are related to documentation. Some are configuration files. On my OpenSuSE v10.1 system there is a udev file in /etc/sysconfig and there is a udev directory under /etc. Then there is a ton of documentation.

/etc/sysconfig/udev
/etc/udev
/etc/udev/rules.d
/etc/udev/rules.d/05-udev-early.rules
/etc/udev/rules.d/29-net_trigger_firmware.rules
/etc/udev/rules.d/30-net_persistent_names.rules
/etc/udev/rules.d/31-network.rules
...

/usr/share/doc/manual/suselinux-manual_en/manual/cha.udev.html
/usr/share/doc/manual/suselinux-manual_en/manual/sec.udev.boot.html
/usr/share/doc/manual/suselinux-manual_en/manual/sec.udev.debug.html
/usr/share/doc/manual/suselinux-manual_en/manual/sec.udev.drivers.html
/usr/share/doc/manual/suselinux-manual_en/manual/sec.udev.hplug.html
/usr/share/doc/manual/suselinux-manual_en/manual/sec.udev.kernel.html
/usr/share/doc/manual/suselinux-manual_en/manual/sec.udev.moreinfo.html
/usr/share/doc/manual/suselinux-manual_en/manual/sec.udev.persdev.html
/usr/share/doc/manual/suselinux-manual_en/manual/sec.udev.rules.html
/usr/share/doc/packages/hwinfo-devel/html/structs__udevinfo__t.html
...

And that is only a partial list.

Well, everything seems to work fine without the rc.udev script. Seems like the new kernel is initializing udev before the script is called. The the udev script is called and complains that the work is over. So, I just chmod 644 rc.udev and everything works fine. I still wish I knew exactly what is going on.

When you upgraded did you overwrite the /etc/udev/rules.d/udev-rules file with the .new one? You have to because the rule format changed with 11.

Actually, I did a fresh install. I formatted and repartitioned the drive so no old files would be laying around.