Hi Steve, I think I haven't been clear enough about the issue. The server component is starting up fine, as are the virtual machines that I have starting automatically. What I am trying to do is get the console going, and just as the logged on user rather than having to invoke sudo and provide the password. Hope this makes it clearer?

Cheers,
Roger

Steve Holdoway wrote:
sudo /etc/init.d/vmware start

should do the trick.

On Fri, 04 Apr 2008 09:02:44 +1300
Roger Searle <[EMAIL PROTECTED]> wrote:

Good morning. I took the bait of the minor upgrade available from VMWare Server to go up a massive 0.01 to 1.05, downloading their tar file and running the install script. The installation went fine and VMs run and behave as usual. However I am no longer able to use a KDE menu or Autostart entry to launch the application, the only method I have found so far is to launch manually via command line thus:

[EMAIL PROTECTED]:~$ sudo /usr/bin/vmware -l
[sudo] password for roger:

which is a pain and obviously not good practice. Without sudo I get permission denied which seems to be contrary to my understanding of the permissions in that I have execute rights:

[EMAIL PROTECTED]:~$ sudo ls -al /usr/bin | grep vmware
-r-xr-xr-x  1 root   root        4570 2008-04-02 11:45 vmware

Yes, yes, I know, use Adept - and I'm really bad. It's only offering 1.04, sure I could remove 1.05 and go back a release but it's the learning for me. How can I create a desktop icon command that doesn't require the use of sudo? I know the "right click the desktop, create new, link to application" bit, and /usr/bin/vmware as the application command doesn't do it.

Thanks for any pointers!
Roger




Reply via email to