Wednesday 10 July 2013

Manually uninstalling VMware Workstation from Linux hosts

Manually uninstalling VMware Workstation from Linux

VMWare Workstation doesn't ship in a deb, so it isn't registered in dpkg (which is why you can't find it in the software center). It does have an install and uninstall utility though.

To uninstall VMWare Workstation, you will need to run


#vmware-installer --uninstall-product vmware-workstation

Details

This article provides steps for manually removing VMware Workstation when the uninstaller script or RPM package fails to remove the product automatically.

Solution

Note: Log into the host using the root account to execute the terminal commands in this article. If running Ubuntu, the root account is not available by default. Prepend all commands with sudo,or switch to root using this command:

sudo su -

Warning: This command provides unrestricted access to the operating system. It is possible to cause damage to the system when using this access level.

  1. Open a command prompt. For more information, see Opening a command or shell prompt (1003892). Type the commands as indicated in the steps of this procedure.
  2. Shut down all VMware applications and services.

    /etc/init.d/vmware stop

  3. Verify that all processes have stopped:

    lsmod | grep vm

    Note: A zero must be listed beside VMware related modules to indicate that they are no longer running.

  4. Move the VMware libraries to the /tmp directory:

    cd /lib/modules/kernel_version/misc
    mv vm* /tmp


    Note: If the kernel has ever been updated, you must check and move the files from multiple paths. Substitute the kernel version where indicated above.

  5. Unload the kernel modules:

    rmmod vmnet.o
    rmmod vmmon.o
    rmmod vmci.o
    rmmod vmblock.o
    rmmod vmppuser.o


  6. Remove the VMware startup scripts:

    RedHat and Most Distributions:
    rm /etc/rc.d/init.d/rc2.d/*vmware*
    rm /etc/rc.d/init.d/rc3.d/*vmware*
    rm /etc/rc.d/init.d/rc5.d/*vmware*
    rm /etc/rc.d/init.d/rc6.d/*vmware*


    Ubuntu:

    rm /etc/rc2.d/*vmware*
    rm /etc/rc3.d/*vmware*
    rm /etc/rc5.d/*vmware*
    rm /etc/rc6.d/*vmware*


    Note: If you are using a different Linux distribution, substitute the correct path in the commands.

  7. Remove the remaining VMware files and directories:

    rm -rf /etc/vmware*
    rm /usr/bin/vmware-usbarbitrator
    rm /usr/bin/vmnet*
    rm -r /usr/lib/vmware*
    rm -r /usr/share/doc/vmware*


  8. If an RPM package was used to install the VMware product, complete these steps to delete the RPM database entry:

    rpm -qa | grep VMware

    A list of VMware packages is presented. Copy the exact package name for the next step and paste it into the command where indicated.

  9. Remove the VMware packages:

    rpm --erase --nodeps VMware_Package_Name

Tuesday 25 June 2013

How do You Install XvidCap on uBuntu 12.04 Distro

Xvidcap is a small tool to capture things going on on an X-Windows display to either individual frames or an MPEG video. This software is not present in the Ubuntu 12.04 repository by default. You can get a copy of the distributed binary in the form of a .deb package at the following link.
https://launchpad.net/ubuntu/precise/amd64/xvidcap/

Once you download this package, go ahead and install the package with the following command. The amd64 package given as example is for 64 bit machine.
$ sudo dpkg -i xvidcap_1.1.7-0.2ubuntu12_amd64
In case if the above command fails giving out errors, please note that Xvidcap depends on libavdevice-extra-53 package. So go ahead and install this package first with the following command.



$ sudo  apt-get install libavdevice-extra-53
By default, the Ubuntu 12.04 comes with libavcodec53 package. This conflicts with the  libavdevice-extra-53. In such a case, feel free to go ahead and replace the libavcodec53 package with libavdevice-extra-53. This satisfies the dependency requirement for Xvidcap.

Once done with setting dependencies, you can then install the Xvidcap package.

This is another posting showing "how to do computing" for everyday computer usages... For a general public 

Friday 21 June 2013

Friday 7 June 2013

POSSIBLE WordPress Under Attack again !!!

ALERT - ALERT - WordPress Based website under attack Again !!!



Potential WordPress problem (Brute Force attack against WordPress websites)
We have monitored on-going brute-force attack against WordPress websites, in order to keep your WordPress website secure, we recommend you do the following:

1. Please change your password for WordPress admin area.

2. Go to your cPanel > File Manager and find your wp-login.php file.



Temporary rename wp-login.php file (for example into wp-login1.php).

You need to change a line in your wp-login.php to reflect the change to the file name. Its line 671 where the form action refers to wp-login.php

-------------------------Update---------------------------

wp-login.php is temporary disabled because of huge brute force attack. Please rename wp-login.php to something else.

How to Create a Ansible Lab on your Local Machine using Vagrant in 5 min using ChatGPT - Part 2

Update the above Vagrantfile Centos 8 servers and add Public IP and dhcp on each server .. To update the provided Vagrantfile for the three ...