This Question is Answered
Yeah, I've stumbled through several hundreds of posts over the past 10-12 hours, and I've visited about 40+ forums, and various websites. I've bounced between the Ubuntu and the VMWare forums, but the begging and pleading for help (from VMWare) to fix their broken product seems to fall upon deaf ears.
Haven't received a single response from ANY of the VMWare developers. Amazing at how poorly VMWare supports a COMMERCIAL product. I could understand if this was an "open source" free product, but as far as a commercial product is concerned, I'm pretty disappointed that "cries for help" have been going on for 3-4+ months now, and the issues seem to be completely ignored by VMWare and the VMWare developers.
I found this thread here:
http://www.linuxformat.co.uk/index.php?name=PNphpBB2&file=printview&t=9116&start=0
I'm not sure if this helps you at all. But I think it has gotten me at least headed in the right direction. I've been unable to get an answer from any of the VMWare developers, and they seem to be "sleeping on the job" as far as support VMWare under Ubuntu 8.10.
I'll take a look at the link you sent, and if I can find a solution I'll post back my findings (and solution) if I can ever find one. Thanks for the response, and thanks for the help. Hopefully if enough of us work together, maybe we can fix VMWare's broken tools, and VMWare's broken product.
It seems odd that the "open source" community has to comb together to fix a broken commercial product. VMWare seems to continue to ignore the problems, and continue to stick their head in the sand. I'll comb over the link you sent from the Ubuntu forums, and hopefully we can get more help over at Ubuntu then we are getting from the VMWare developers.
I haven't found a single response from any of the VMWare developers as to how to resolve this issue, or get it fixed. I'll check the link you sent, because that's a new link that I haven't seen yet. I'll try it, and post back if I find a solution (or get it fixed, or get it to work).
Thanks for the response! It's pretty frustrating when VMWare doesn't work properly, just to say the least. Hopefully the Ubuntu developers can be a bit more help then the VMWare folks. VMWare seems to just ignore the cries and pleas for help from their PAYING CUSTOMERS, and leaves it up to the Open Source developers to fix all the bugs and problems with a commercial product like VMWare. Go figure.
Regardless, if I do find a fix, I'll post it back to this thread, just so others will have a solution (for Archive purposes).
Thank-you!
Haven't received a single response from ANY of the VMWare developers. Amazing at how poorly VMWare supports a COMMERCIAL product. I could understand if this was an "open source" free product, but as far as a commercial product is concerned, I'm pretty disappointed that "cries for help" have been going on for 3-4+ months now, and the issues seem to be completely ignored by VMWare and the VMWare developers.
I found this thread here:
http://www.linuxformat.co.uk/index.php?name=PNphpBB2&file=printview&t=9116&start=0
I'm not sure if this helps you at all. But I think it has gotten me at least headed in the right direction. I've been unable to get an answer from any of the VMWare developers, and they seem to be "sleeping on the job" as far as support VMWare under Ubuntu 8.10.
I'll take a look at the link you sent, and if I can find a solution I'll post back my findings (and solution) if I can ever find one. Thanks for the response, and thanks for the help. Hopefully if enough of us work together, maybe we can fix VMWare's broken tools, and VMWare's broken product.
It seems odd that the "open source" community has to comb together to fix a broken commercial product. VMWare seems to continue to ignore the problems, and continue to stick their head in the sand. I'll comb over the link you sent from the Ubuntu forums, and hopefully we can get more help over at Ubuntu then we are getting from the VMWare developers.
I haven't found a single response from any of the VMWare developers as to how to resolve this issue, or get it fixed. I'll check the link you sent, because that's a new link that I haven't seen yet. I'll try it, and post back if I find a solution (or get it fixed, or get it to work).
Thanks for the response! It's pretty frustrating when VMWare doesn't work properly, just to say the least. Hopefully the Ubuntu developers can be a bit more help then the VMWare folks. VMWare seems to just ignore the cries and pleas for help from their PAYING CUSTOMERS, and leaves it up to the Open Source developers to fix all the bugs and problems with a commercial product like VMWare. Go figure.
Regardless, if I do find a fix, I'll post it back to this thread, just so others will have a solution (for Archive purposes).
Thank-you!
Well almost done, but not quite finished yet...
I think I'm almost there. I'm having a problem tarring up the "vmblock, vmhgfs, vmmemctl, vmsync, and vmxnet modules" and putting those modules into the official VMWare Tools tarball. I posted what I thought was the solution on another thread, but I'm realizing that I'm having problems with this command:
*sudo for i in ; do sudo mv ${i} ${i}-only; sudo tar -cf ${i}.tar ${i}-only; done
This falls under the section entitled:
"From the open source modules/linux folder we have the vmblock, vmhgfs, vmmemctl, vmsync and vmxnet modules that we need to tar up and place into the official VMware tools tarball:"
The second line down says:
*sudo for i in ; do sudo mv ${i} ${i}-only; sudo tar -cf ${i}.tar ${i}-only; done
I've been unable to get that line to work. Any suggestions as to what could be wrong? Is there an error with that line, or are there any other commands I could use?
I see the files that need to be tarred up, but the command "sudo for i in *; do sudo mv ${i} blah blah blah" doesn't seem to work.
It comes back with a bash: syntax error near unexpected token 'do'.
Not sure what's wrong, how do I tar up those files and place them into the official VMware tools tarball, and when on earth is VMWare going to fix this, so that other users like me don't have to?
Any help with the above command (tarring up the files and putting them into the VMware tools tarball, would be greatly appreciated. I awarded you "helpful" points so far, but once I can get this resolved, I'll gladly close this out as "solved/answered" and give you the full credit for "correct answer". As it's the closest solution I have found so far from anyone.
I did notice that the other link you gave, actually was for 64-bit downloads, and I ammended the post that I had made with the links for i386 (32-bit) files. But I'm still stuck at the part with the "sudo for i in *; do sudo mv ${i} ${i}-only; sudo tar, blah blah blah command. I appreciate the help, and I'm slowly getting there. I have a feeling that I'm getting close, I just need to figure out how to get those built modules into the VMWare Tools tarball, so I can go back and re-run the VMWare install.
Do you have any idea how I can get those modules placed inside the official VMWare Tools tarball? What commands would I type? For some reason it doesn't like the "do", and keeps coming back with a syntax error. Is there any way to break that command up into maybe 4 or 5 different commands (line by line) so that it's not one big command (separated by semi colons). This way I can see what is causing the error/problem. Is there another way to zip those files up and add them to the VMWare tools tarball?
I think I'm almost there. I'm having a problem tarring up the "vmblock, vmhgfs, vmmemctl, vmsync, and vmxnet modules" and putting those modules into the official VMWare Tools tarball. I posted what I thought was the solution on another thread, but I'm realizing that I'm having problems with this command:
*sudo for i in ; do sudo mv ${i} ${i}-only; sudo tar -cf ${i}.tar ${i}-only; done
This falls under the section entitled:
"From the open source modules/linux folder we have the vmblock, vmhgfs, vmmemctl, vmsync and vmxnet modules that we need to tar up and place into the official VMware tools tarball:"
The second line down says:
*sudo for i in ; do sudo mv ${i} ${i}-only; sudo tar -cf ${i}.tar ${i}-only; done
I've been unable to get that line to work. Any suggestions as to what could be wrong? Is there an error with that line, or are there any other commands I could use?
I see the files that need to be tarred up, but the command "sudo for i in *; do sudo mv ${i} blah blah blah" doesn't seem to work.
It comes back with a bash: syntax error near unexpected token 'do'.
Not sure what's wrong, how do I tar up those files and place them into the official VMware tools tarball, and when on earth is VMWare going to fix this, so that other users like me don't have to?
Any help with the above command (tarring up the files and putting them into the VMware tools tarball, would be greatly appreciated. I awarded you "helpful" points so far, but once I can get this resolved, I'll gladly close this out as "solved/answered" and give you the full credit for "correct answer". As it's the closest solution I have found so far from anyone.
I did notice that the other link you gave, actually was for 64-bit downloads, and I ammended the post that I had made with the links for i386 (32-bit) files. But I'm still stuck at the part with the "sudo for i in *; do sudo mv ${i} ${i}-only; sudo tar, blah blah blah command. I appreciate the help, and I'm slowly getting there. I have a feeling that I'm getting close, I just need to figure out how to get those built modules into the VMWare Tools tarball, so I can go back and re-run the VMWare install.
Do you have any idea how I can get those modules placed inside the official VMWare Tools tarball? What commands would I type? For some reason it doesn't like the "do", and keeps coming back with a syntax error. Is there any way to break that command up into maybe 4 or 5 different commands (line by line) so that it's not one big command (separated by semi colons). This way I can see what is causing the error/problem. Is there another way to zip those files up and add them to the VMWare tools tarball?
I hate to ask this, but would you be able to streamline it a little? I'm having some problems following all the links and I'm not sure which parts from each other thread you actually did. It's still chaotic and confusing. I appreciate your effort. 