Skip to main content

VMware Workstation 12 Working with Fedora 23 !! 

As the following instruction we can start VMware workstation 12/12.1 On the Fedora 23. 


Login as root first. 




$ sudo su -

Force rebuild of VMWare modules:

# vmware-modconfig --console --install-all  


Replace the vmware glib version with the fedora version:

# cd /usr/lib/vmware/lib


# for mylib in $(ls /usr/lib64/*4600*); do /bin/cp -afv $mylib $(basename $mylib.4600.1 )/$(basename $mylib .4600.1 ); done




This basically does the following:



# pwd
/usr/lib/vmware/lib
# /bin/cp -afv /usr/lib64/libgio-2.0.so.0.4600.1 libgio-2.0.so.0/libgio-2.0.so.0
# /bin/cp -afv /usr/lib64/libglib-2.0.so.0.4600.1 libglib-2.0.so.0/libglib-2.0.so.0
# /bin/cp -afv /usr/lib64/libgmodule-2.0.so.0.4600.1 libgmodule-2.0.so.0/libgmodule-2.0.so.0
# /bin/cp -afv /usr/lib64/libgobject-2.0.so.0.4600.1 libgobject-2.0.so.0/libgobject-2.0.so.0
# /bin/cp -afv /usr/lib64/libgthread-2.0.so.0.4600.1 libgthread-2.0.so.0/libgthread-2.0.so.0


Start VMware or VMplayer:

$ VMWARE_USE_SHIPPED_LIBS=force vmware
or:
$ VMWARE_USE_SHIPPED_LIBS=force vmplayer



For ease of use/convenience, you might also want to do this:

# cd /usr/bin/
# mv -iv vmplayer vmplayer.bin
# mv -iv vmware vmware.bin

Then create two scripts replacing the previous scripts/tools:
$ cat /usr/bin/vmplayer
#!/bin/bash
export VMWARE_USE_SHIPPED_LIBS=force
/usr/bin/vmplayer.bin $*

$ cat /usr/bin/vmware
#!/bin/bash
export VMWARE_USE_SHIPPED_LIBS=force
/usr/bin/vmware.bin $*










Source is: 




https://bugzilla.redhat.com/show_bug.cgi?id=1278896









































Comments











Post a Comment



















Popular posts from this blog



















Canonical Kubernetes Platform




























Recently,  Canonical has announce the release of the Canonical Kubernetes Platform  version 1.32, a robust and user-friendly solution for seamless cluster creation and management. This platform is designed to simplify the deployment and maintenance of containerized workloads, making it an ideal choice for both developers and enterprises. Here are some of the attracting features of this Platform.  ZeroOps with Built-in Essentials:  The platform comes pre-configured with critical components such as networking, DNS, metrics server, local storage, ingress, gateway, and load balancer, enabling immediate productivity post-installation. Simplified Installation and Maintenance:   Leveraging snap packages, the installation process is straightforward, and automated patch upgrades enhance security without manual intervention. Effortless Scalability:  Adding new nodes is seamless, and achieving high availability requires minimal effort, ensuring your infrastructure sca...




















Post a Comment









Read more






























Docker Container Management from Cockpit




























  Cockpit  can manage containers via docker. This functionality is present in the Cockpit docker package.     Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket.     Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system.   [root@rhel8 ~] #  yum install cockpit-docker    -y    Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console.      We can search or pull an image from docker hub just by searching with the keyword like nginx centos.                       Once the Image download...




















Post a Comment









Read more




























Add The Group Information  IN Yum Repository in simple Two steps




























 = Yum groups and repositories = Yum supports the group commands   * grouplist   * groupinfo   * groupinstall   * groupremove   * groupupdate Groups are read from the "group" xml metadata that is optionally available from each repository. If yum has no repositories which support groups then none of  the group operations will work.  #yum grouplist    This will list the installed and available groups for your system in two    separate lists. If you pass the optional 'hidden' argument then all of     the groups which are set to 'no' in the group xml  tag.   yum groupinfo groupname     This will give you detailed information for each group including:   description, mandatory, default and optional packages.       #yum groupinstall groupname      #yum groupupdate groupname   Despite their differing names both of these commands perform the same   func...




















Post a Comment









Read more