VMWare 4.5.2 broken? - Fixed now
Christopher A. Williams
chrisw01 at privatei.com
Fri Oct 15 05:11:23 UTC 2004
On Thu, 2004-10-14 at 19:35 -0500, Allen Kistler wrote:
> Steve Fox wrote:
> > On Thu, 2004-10-14 at 13:20 -0500, Steve Fox wrote:
> >
> >>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?
> >
> >
> > After updating again today and getting udev-036, vmware-configure.pl
> > works again.
>
> /dev is a tempfs with udev, so everything gets deleted every time you
> shut down. Without explicit instructions to recreate vmmon, vmnet*, and
> parport*, they don't get created by udev on boot.
OK - that's all well and good. How do we fix this problem? VMware isn't
the only application that will be creating devices under /dev that udev
will need to know about and re-create as appropriate.
We still have a similar problem with syncing USB palm devices that
remains unresolved as well.
Cheers,
Chris
--
======================
When the solution is simple,
God is answering.
-- Albert Einstein
More information about the fedora-test-list
mailing list