The real solution for vmware-workstation to make it play nice on a pure udev system (without saving devices to a tarball) is to make vmware-workstation sysfs-aware. However this is not the case (yet). For people that use a pure udev system vmware-workstation doesn't work out of the box. Hereby a patch to the init-file to make vmware-workstation work on a pure udev system out of the box. The init-script still works on systems with devfs or static devices.
Created attachment 42509 [details, diff] patch for vmware-workstation init-script
I would also like to see this fixed, but its a duplicate of bug 54269. But maybe we can get wolf31o2(please assign this bug to him) to accept this solution. Looks pretty good imho :)
I checked bugzilla before creating this report and saw bug 54269. I don't agree with you that this a duplicate, because the proposed solution in the other bug is to create an (other) tarball to save the devices. This script just creates the devices when vmware-workstation starts and the devices are destroyed after a reboot. We want to accomplish the same thing but use different methods.
Same bug, and regardless of the solution, we've already decided that its an upstream bug *** This bug has been marked as a duplicate of 54269 ***
upstream says we should add for a in `seq 0 9`; do mknod /dev/vmnet$a c 119 $a; done at the top of /etc/init.d/vmware See this post from petr: http://www.vmware.com/community/thread.jspa?forumID=19&threadID=8892&messageID=83028#75774
*** This bug has been marked as a duplicate of 54269 ***