VMWare 4.5.2 broken?
James C. Bevier
jim at jbsys.com
Thu Oct 14 21:17:50 UTC 2004
I saw the same error a few OS revisions ago. I copied the following
device definitions to the /etc/udev/devices directory and the errors
went away. I am currently at 610 and all is well in 32 & 64 bit
versions.
Copy from /dev directory to /etc/udev/devices directory:
vmmon
vmnet0
vmnet1
vmnet8
parport0
parport1
parport2
parport3
Jim
----- Original Message -----
From: "Steve Fox" <drfickle at k-lug.org>
To: "Fedora Test" <fedora-test-list at redhat.com>
Sent: Thursday, October 14, 2004 11:20 AM
Subject: VMWare 4.5.2 broken?
> I did a 'yum update' yesterday and now when I try the new kernel, I get
> the below message from VMWare. Any clues as to why mknod would break?
> udev stuff?
>
> ----------------------------------------------------------------
>
> This program previously created the file /dev/vmmon, and was about to
> remove it.Somebody else apparently did it already.
>
> mknod: `/dev/vmmon': File exists
> Unable to create the character device /dev/vmmon with major number 10
> and minor
> number 165.
>
> Execution aborted.
>
> --
>
> Steve Fox
> http://k-lug.org
>
> --
> fedora-test-list mailing list
> fedora-test-list at redhat.com
> To unsubscribe:
> http://www.redhat.com/mailman/listinfo/fedora-test-list)
>
More information about the test
mailing list