/etc/init.d/vmware stop * Stopping VMware services: /etc/vmware/init.d/vmware: line 83: /sbin/lsmod: No such file or directory [ ok ] * Virtual machine communication interface [ ok ] * Virtual machine monitor [ ok ] * Blocking file system [ ok ] /etc/vmware/init.d/vmware: line 90: /sbin/lsmod: No such file or directory It would appear that lsmod has been moved to /bin/lsmod and lines 83 and 90 in /etc/vmware/init.d/vmware must be modified to read /bin/lsmod Reproducible: Always
Seems that this was because of the update in *module-init-tools-3.8 (24 May 2009)
(In reply to comment #1) > Seems that this was because of the update in *module-init-tools-3.8 (24 May > 2009) > no, in all versions it is in /bin.
Can't say for sure but I know that when I modified sbin to bin, it worked
fixed in the cvs.
Curious, what was fixed? vmware or module-init-tools? I just synced and emerged and lsmod is still in /bin which also brakes bash-completion. If it was always in /bin, was it symlinked in previous versions of module-init-tools? thanks.
It appears to me that it was
(In reply to comment #5) > Curious, what was fixed? vmware or module-init-tools? > > I just synced and emerged and lsmod is still in /bin which also brakes > bash-completion. > > If it was always in /bin, was it symlinked in previous versions of > module-init-tools? > > thanks. > /sbin/lsmod link to /bin/lsmod has disappeared. /etc/vmware/init.d/vmware was using /sbin/lsmod. Now it (/etc/vmware/init.d/vmware) is fixed and it's using /bin/lsmod.
