╭─fenris@fenris in ~ took 13ms
╰─λ /etc/conf.d/vmware start
bash: /etc/conf.d/vmware: Permission denied
╭─fenris@fenris in ~ took 4ms
[🚫] × sudo /etc/conf.d/vmware start
[sudo] password for fenris:
sudo: /etc/conf.d/vmware: command not found
╭─fenris@fenris in ~ as 🧙 took 5s
[🔴] × sudo /etc/vmware start
sudo: /etc/vmware: command not found
╭─fenris@fenris in ~ as 🧙 took 17ms
[🔴] ×
I should share with you some of my stories I had. God help us all should you still for some reason beyond human understanding still want to use a 32-bit operating system to try and breath life in older computer systems with chip sets that cannot do 64-bit.
My old GETAC M230N system still holds some tactical value to me in a world of Bill Gate’s version of hijacking all our processors in the distant future to keep unique ID tags on pictures and PDF’s so we can all know who spreads “disinformation”. No, they wouldn’t keep tabs on AI systems…just us humans. It reminds me of learning what the Soviet Union did with type writers. Mark a key so we know who is writing articles government doesn’t like so someone can show up at your house and disappear you.
So anyway, I had asked for some assistance to make VMware Workstation 10 work because that was the last version supported to work on i386 systems, and of course, nobody could help me make it work. Then the response was “why can’t you just use QEMU?” and at that point, there is no sense in even replying anymore. For the record, I have never in my life ever been able to make QEMU function the way I want it to in anyway what so ever. I can’t even get to the load a Windows 7 ISO file stage booted without all kinds of errors kicking me down. There comes a point where I am willing to just get a key for myself and go with the flow. Are these people really going to waste there time to help me with QEMU after all this? I think it is safe to say that’s a big fat no.
Yes. Just to explain my thought process, vmware.service is set up to execute vmware start and vmware stop from a script it expects to be in /etc/init.d/. See here in the service:
Where these system service scripts are installed to I understand is specified by the user during installation. The ArchWiki article makes it sound like /etc/init.d is the default, but for whatever reason it looks like yours has been either installed somewhere else, or not installed.
Like you mentioned, probably not a big deal since it is working now but I thought if we could amend the service file so it is pointing to the actual location of the script on your machine, then that service would start working normally and it will do whatever it is supposed to be doing.
This output suggests that file is not the script–that file is something else.
Try running this other file the same way and see what happens:
sudo /usr/lib/vmware/bin/vmware start
You could try some of the other results from that search to see if you can find it, but the other possibility we should acknowledge is those scripts were not installed at all for some reason. In that case, re-installing the vmware-workstation package might help.
╭─fenris@fenris in ~ took 13ms
╰─λ /etc/conf.d/vmware start
bash: /etc/conf.d/vmware: Permission denied
╭─fenris@fenris in ~ took 4ms
[🚫] × sudo /etc/conf.d/vmware start
[sudo] password for fenris:
sudo: /etc/conf.d/vmware: command not found
╭─fenris@fenris in ~ as 🧙 took 5s
[🔴] × sudo /etc/vmware start
sudo: /etc/vmware: command not found
╭─fenris@fenris in ~ as 🧙 took 17ms
[🔴] × sudo /usr/lib/vmware/bin/vmware start
[sudo] password for fenris:
I/O warning : failed to load external entity "/etc/vmware/hostd/proxy.xml"
╭─fenris@fenris in ~ as 🧙 took 29s
╰─λ
It also stared vmware workstation and it poped up a window for some reason
Thank you! Since I use Debian, all I had to do was switch out ‘micro’ with ‘nano’ and it worked just like that.
Just switched from Windows → about a month or two ago, and I’m already trying to load up a VM of Arch so I can practice installing it in a safe environment. Again thank you!
