Saturday 30 June 2012

Remove VMware from Linux


Manually uninstalling VMware Workstation from Linux hosts

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 on to the host to 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 the root using the command:
sudo su -
Warning: This command provides unrestricted access to the operating system. It is possible to cause damage 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 following steps.
  2. Shutdown 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.ormmod 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 above commands.
  7. Remove the remaining VMware files and directories:

    rm -rf /etc/vmware*rm /usr/bin/vmware*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>

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

Saturday 23 June 2012

Windows Server 2012: Free EBook!


For the last few months I have been talking about Windows Server 2012, and I am thrilled to see that so many of you are downloading it and using the Release Candidate.  When the product does release so many IT Pros will be ready to hit the ground running! 
If you, like me, are one of these who wants the newest and the best and want to take the time to learn it properly, there is a great new book from Microsoft Press (By Mitch Tulloch and the Windows Server Team) available for free on-line.  You can download it by clicking here: http://go.microsoft.com/?linkid=9811411
Now if you were fortunate enough to be at TechEd last week, they were handing out hard copies (which is my personal preference).  I assume that they will be doing the same next week at TechEd Europe…
By the way, the book is based on the beta release, not the Release Candidate.  So there may be some changes that you have to be aware of.  Relax though… it’s still pre-release software, and will be ready when it goes to market!

Thursday 7 June 2012

How to use FTP with Command Line (Command Prompt)

How to use FTP from the command line. 


 FTP (File Transfer Protocol) allows you to transfer files between your PC and other Internet systems (hosts). You can transfer files, work with local or remote directories, rename and display files, and execute system commands.

Before you start, you must know how to log on to the remote system and have a userid and password on that system. Note: Some systems allow anonymous ftp access. To use anonymous ftp, use anonymous as your userid and your e-mail address as the logon password. Logging Onto and Off of a Remote System To begin using Microsoft's FTP client, Open a command prompt and switch to the destination directory (where you want the download file).

To start an FTP session, enter: ftp host_name where hostname is the name or IP address of the remote system. You will then be asked to enter your userid and password.

Once you have successfully logged onto a remote system, you will be able to use ftp commands to view a listing of files on the remote system and transfer files between the two systems.


Example: Download i386.exe (Windows NT 3.5 Resource Kit) from ftp://ftp.microsoft.com/bussys/winnt/winnt-public/reskit/nt35/i386 to C:\Temp\Download
  1. Open a command prompt. Enter CD C:\Temp\Download (assuming that directory exists).
    Enter: ftp ftp.microsoft.com

    You should now see a prompt similar to this:
    Connected to ftp.microsoft.com.
    220 Microsoft FTP Service
    User (ftp.microsoft.com:(none)):


  2. For the userid, Enter: anonymous

    You should see a prompt similar to this:
    331 Anonymous access allowed, send identity (e-mail name) as password.
    Password:


  3. Enter: userid@domain.com as the password at the "Password:" prompt.
    Note: Any e-mail address in a userid@domain.com format should work. You will not be able to see the password as you type it.


  4. To download i386.exe from the bussys/winnt/winnt-public/reskit/nt35/i386 directory, Enter: get bussys/winnt/winnt-public/reskit/nt35/i386/i386.exe
    Note: You could have also used ls to view the directory and file names, cd bussys/winnt/winnt-public/reskit/nt35/i386 to switch directories, and get i386.exe to download the file from within that directory.


  5. To end the FTP session, Enter: quit or bye.
Note: Once you have extracted the resource kit, you will have to expand individual files 
example: expand choice.ex_ choice.exe



FTP Commands

For a list of FTP commands, at the "ftp>" prompt, Enter: helpWhen using ftp from the command prompt, the following list of supported commands will be displayed:
Note: Hover your mouse over a command to see what the output of "help *" is for that command.


!   

delete

literal

prompt

send

?   

debug

ls  

put 

status

append

dir

mdelete

pwd 

trace

ascii

disconnect

mdir

quit

type

bell

get 

mget

quote

user

binary

glob

mkdir

recv

verbose

bye 

hash

mls 

remotehelp

cd  

help

mput

rename

close

lcd 

open

rmdir


The question mark (?) command is equivalent to the help command. Typing help or ? followed by the name of a command will display a brief description of the command's purpose. The exclamation point (!) can be used to shell to the system (command) prompt. Type Exit to return to the FTP session.

You can also issue a subset of system commands to perform as you shell out, e.g., ! dir %windir% | more. When the commands in the shell have completed, you will be returned to the FTP session. The pwd command will list the current directory on the remote machine.

To change directories on the remote machine, use the cd command. To create a new directory on the remote machine, use the mkdir command followed by the name you would like to assign to the new directory. The lcd command can be used to change directories on the local (PC) machine.

To display a listing of files on the remote system, enter: ls or dir.



To download a file (copy a file from the remote system to your PC), you can use the command get or recv followed by the name of the file you would like to download. Optionally, you can follow the filename with a second filename which will be assigned to the file when it is downloaded to your PC.

To download multiple files, you can use the mget command followed by a descriptor for the files you would like to download (e.g.: *.f for all files ending in ".f" or *.* for all files).

You will be prompted to indicate whether you would like to download each file in turn. To turn off this prompting, enter the prompt command prior to entering the mget command; you will receive the message "Interactive mode OFF" indicating that prompting has been deactivated. By default, files are downloaded and uploaded in ASCII file transfer mode.

To download or upload files using Binary format mode, enter the command Binary at the "ftp>" prompt prior to downloading or uploading the file(s). To return to ASCII file transfer mode, enter the ASCII command. To upload a file (copy a file from your PC to the remote system), you can use the command put or send followed by the name of the file you would like to upload.

Optionally, you can follow the filename with a second filename which will be assigned to the file when it is uploaded to the remote system. The mput command can be used to upload multiple files.

You can use the close or disconnect command to drop the current ftp connection without exiting from the command enironment and then use the open command to connect to a new host.

Monday 21 May 2012

VMware Workstation 8.0.2 does not Work with uBuntu 12.04 LTS

Hi there ...

About some day ago, I have updated my system,

I'have created this post to share, the way I have troubleshoot and successfully update the Linux Kernel make VMware Workstation 8.0.2 work and Kubuntu 12.04..


Installing VMware 8.0.2 64bit
Ubuntu 12.04LTS 64bit BETA
My Kernel version is: 3.2.0-20-generic
pst007x@pst007x-Aspire-5741:~$ sudo sh VMware-Workstation-Full-8.0.2- 591240.x86_64.bundle
Installs ok
When I launch I am asked to install modules which are compiled and loaded into the running kernel.
A window opens
VMware Kernel Module Updater
This fails on Virtual Network Device
UPDATE:
When I try to add patch, following error:
 pst007x@pst007x-Aspire-5741:~$ sudo sh patch-modules_3.2.0.sh
 [sudo] password for pst007x: 
 patch-modules_3.2.0.sh: 27: [: workstation8.0.2: unexpected operator
 patch-modules_3.2.0.sh: 28: [: workstation8.0.2: unexpected operator
 Sorry, this script is only for VMWare WorkStation 8.0.2 or VMWare Player 4.0.2. 
 Exiting
 pst007x@pst007x-Aspire-5741:~$
I have fully un-installed, and re-installed. I am installing the correct version. Probably a problem with the patch. VMware installs perfectly on Ubuntu 11.10..
.. Here is how I've worked it out .. 

Move to Home folder

  1. VMware-Workstation-Full-8.0.2-591240.x86_64.bundle
  2. PATCH: patch-modules_3.2.0.sh
  3. PATCH: vmware3.2.0.patch
Patch download link (xtact contents to Home folder):

"root@mukonda:/home/malange/Downloads# sudo  sh VMware-Workstation-Full-8.0.2-i386.bundleExtracting VMware Installer...done.
No protocol specified
No protocol specified
No protocol specified
No protocol specified

You must accept the VMware OVF Tool component for Linux End UserLicense Agreement to continue.  Press Enter to proceed.
                                                
VMWARE OPEN VIRTUALIZATION FORMAT TOOL LICENSE AGREEMENTNotice to User:This Open Virtualization Format Tool ("OVF Tool") License Agreement is a ... "bla bla bla "


Here is the Ubuntu Terminal Log record ...

"root@kubata:/home/malange/Downloads# ./patch-modules_3.2.0.sh                                                                                                                
-bash: ./patch-modules_3.2.0.sh: Permission denied                                                                                                                                  
root@kubata:/home/malange/Downloads# ./patch-modules_3.2.0.sh                                                                                                                      
patching file vmnet-only/filter.c                                                                                                                                                   
patching file vmnet-only/netif.c                                                                                                                                                    
patching file vmnet-only/userif.c                                                                                                                                                   
Stopping VMware services:                                                                                                                                                           
   VMware Authentication Daemon                                        done                                                                                                         
   VM communication interface socket family                            done                                                                                                         
   Virtual machine communication interface                             done                                                                                                         
   Virtual machine monitor                                             done                                                                                                         
   Blocking file system                                                done                                                                                                         
Using 2.6.x kernel build system.                                                                                                                                                    
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'                                                                                                                      
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \                                                                                            
          MODULEBUILDDIR= modules                                                                                                                                                   
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driver.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/apic.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/comport.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/task.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/vmware-root/modules/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmnet-only/driver.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/hub.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/userif.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/netif.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/bridge.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/filter.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/procfs.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac_compat.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/vmware-root/modules/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/vmware-root/modules/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmnet module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/block.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/control.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/file.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/inode.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/module.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/super.o
  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o
  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmblock module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/driverLog.o
  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmci-only/vmci.mod.o
  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmci module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/notify.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/notifyQState.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/stats.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/util.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/driverLog.o
  LD [M]  /tmp/vmware-root/modules/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vsock-only/vsock.mod.o
  LD [M]  /tmp/vmware-root/modules/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-root/modules/vsock-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vsock module
Starting VMware services:
   Virtual machine monitor                                             done
   Virtual machine communication interface                             done
   VM communication interface socket family                            done
   Blocking file system                                                done
   Virtual ethernet                                                    done
   VMware Authentication Daemon                                        done
   Shared Memory Available                                             done


All done, you can now run .
Modules sources backup can be found in the '/usr/lib/vmware/modules/source-workstation8.0.2-2012-05-21-
kubata@kubata:/home/malange/Downloads# 
"

Now here it VMware Working ... :-) 

                                                                                             Snapshot 1....


Snapshot 2 ....




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

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

This is an exciting experiment of mine as DevOps. As I am experimenting with the Tools available ... So, the quest is to " Vagrantfile ...