On Thu, 2004-11-04 at 21:31 -0500, Paul Iadonisi wrote: > On Thu, 2004-11-04 at 20:22, Brian Callahan wrote: > > [snip] > > You shouldn't need to do any of what you've listed below. I'm not > sure about FC3T3, but on FC3RC5 (kernel 2.6.9-1.667), when I run > vmware-config.pl, the path that it defaults to is > /lib/modules/2.6.9-1.667/build/include and everything builds fine. When > all is done, vmware launches just fine, as well, but I haven't tried > actually installing and/or running a guest OS in it yet. Have used VMware 4.5.2 on FC3T1->FC3rc5 without kernel source installed, but with vmware-any-any-update73. Did see the kind of behavior described with not finding headers in /lib/modules... on earlier versions of VMware/Fedora - fixed by installing kernel sources, but that no longer seems necessary. [snip] > > I'd suggest updating to FC3RC5 (or just do a yum update) and make sure > there's no /usr/src/linux* directories. Then maybe vmware-config.pl > will find the right place to look for the needed kernel headers. > Barring that, just try plugging in > /lib/modules/2.6.8-1.541/build/include when it asks for where your > headers are. > I've also noted in http://platan.vc.cvut.cz/ftp/pub/vmware/readme.txt > that one of the updates is udev support for vmnet, so you may want to > grab vmware-any-any-update84.tar.gz from there and apply it, too. Cool - with an earlier vmware-any-any-update version and udev had to do "cp -a /dev/vm* /etc/udev/devices/" to keep from having to re-run vmware-config.pl after every reboot. Should have checked for an update. Thanks, Phil