Friday, 12 July 2013

How to get Fedore 17 to upgrade to Fedore 18 Using Yum !!


Hi Guys !!!

I am using Fedora 17 for quite a while on VMware I decide to give it a go because my older brother advice me to do so.. Since here, most of time I've using  CentOS, RedHat, Debian Kali and uBuntu mainly... 



But I decided to give it a go on Fedora 17, after some months into it I realize that a new release was launched, therefore I decide to upgrade my machine ... And here is the workout ...

Here are some WORDS of RECOMMENDATION BEFORE YOU DO THIS ...

Upgrading using the yum method described here is not recommended for new users. Use FedUp instead 
 
For upgrades to Fedora 18 and later, the recommended upgrade method is the FedUp tool. This section has instructions on using FedUp to upgrade. 


For upgrades to Fedora 17 and earlier, the recommended installation method is with a boot media with the Anaconda installer as detailed in the Installation Guide or via PreUpgrade. PreUpgrade is a slightly different upgrade method where all the packages are downloaded before the system is rebooted into the Anaconda installer. 

Although upgrades with yum do work, they are not explicitly tested as part of the release process by the Fedora QA and are not documented in the Fedora installation guide. If you are not prepared to resolve issues on your own if things break, you should probably use the recommended installation methods instead
 Extracted from: https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum

2 Upgrading To Fedora 18 (Desktop & Server)

First we must upgrade the rpm package:

# sudo yum clean-all

yum upgrade yum
yum install fedup
yum -y upgrade
fedup-cli --network 18 --debuglog fedup-to-18.log


Than when the install finished .. run on terminal the command " # reboot "
Let the machine boot up and then look into the Grub menu and choose the option that says "fedora fedup upgrade"


Press "Enter" and let the system upgrade start ! When it finish's the system will reboot again and then if all goes well you will boot up on the Fedora 18 ...

For more help  here are some links : http://fedoraproject.org/wiki/FedUp , http://tech.saos.co.in/post/2013/02/16/upgrade-fedora-17-to-18-using-yum.aspx

To download Fedora : go here http://fedoraproject.org/get-fedora

Hope this article help you guys somehow .. If you guys got any query please drop me some questions  I will very happy to answer them ..

:-) Enjoy

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

Thursday, 11 July 2013

Solve VMWare Workstation 9 Error on Linux Kernel 3.8.0-26



I have VMware Workstations 9 installed on my uBuntu 13 machine and today without any apparent reason it stop working throwing me the following error, every time I've tried to boot up any VM machine.


To solver the problem .. here is what I have done ... created bash script to handle problems with VMware Player on 13.04 ...




  • #!/bin/bash
  • if [[ $UID != 0 ]]; then
  •     echo "Please run this script with sudo:"
  •     echo "sudo $0 $*"
  •     exit 1
  • fi
  • sudo ln -s /usr/src/linux-headers-$(uname -r)/include/generated/uapi/linux/version.h /usr/src/linux-headers-$(uname -r)/include/linux/version.h
  • cd /usr/lib/vmware/modules/source
  • sudo tar -xf vmci.tar
  • cd vmci-only
  • sudo sed '127s/.*/   .remove = vmci_remove_device,/' driver.c > driver.c.tmp
  • mv driver.c.tmp driver.c
  • sudo sed '1753s/.*/static int/' driver.c > driver.c.tmp
  • mv driver.c.tmp driver.c
  • sudo sed '1981s/.*/static void/' driver.c > driver.c.tmp
  • mv driver.c.tmp driver.c
  • cd ..
  • sudo tar -cf vmci.tar vmci-only/
  • sudo rm vmci-only/ -Rf
  • sudo vmware-modconfig --console --install-all
  • sudo rm /usr/src
  • Before write the script I've open the terminal and type " #sudo kate " then when kate opened I entered the script and saved on " /usr/src/open-vm-tools-xxxx.xx.xx" (replace the x with year month and day) and save it. Then close Kate

    The Open terminal again and do the following;


    after you should have VMware workstation running...



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

    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 check for open ports on Linux

    Checking for open ports is among the first steps to secure your device. Listening services may be the entrance for attackers who may exploit...