Posted in Computers, Fedora, Linux

VMware Tools Cannot Find Kernel-Headers on Fedora 18 x64

I recently installed Fedora 18 x64 on VMware Workstation 9, and was unable to initially complete the VMware Tools installation using the same methods that I’d previously done many, many times with prior Fedora installations. The installer kept telling me that it couldn’t find the kernel-headers folder. I had installed the development tools with my Fedora install, and they were all up to date, so I was a bit puzzled.

Prior to installing the VMware Tools, you need to install the Fedora development tools if you don’t have them – or if you’re unsure, just check – otherwise the installer will complain that it cannot find something, and will ask you to provide a path.

The development tools needed are: gcc, make, binutils, kernel-devel, kernel-headers

I also recommend updating the existing kernel to match the versions from kernel-devel and kernel-headers.

  1. Update your kernel, restart the vm after the installation: # yum update kernel
  2. Install the development tools, restart the vm when finished: # yum install gcc make binutils kernel-devel kernel-headers
  3. Run the ./vmware-install.pl script, accepting all the defaults (unless you know what you’re doing and want or need to change something)

If the script complains that it cannot find the location of the kernel-headers – and you verify that they are installed by typing # rpm  -qa, then you must copy the kernel-headers from one location to another. Find out which kernel you’re using with # uname -a. The current kernel on my system as of 01-19-2013 is 3.7.2-201.fc18.x86_64

Run the following command to copy the folder from one location to another location, which is where the installer is looking for those header files.

# cp /usr/src/kernels/3.7.2-201.fc18.x86_64/include/generated/uapi/linux/version.h /lib/modules/3.7.2-201.fc18.x86_64/build/include/linux/

If you’re running the script, you can type that path into the installer where it asks for the header-files location. If you’re not running the installer script, run it again, and it should find the path automatically.

Thanks to user jgkirk from the VMware forums for this tip. The original post that helped me can be found here.

Posted in Linux, Ubuntu

Install Flash Player on Ubuntu 11.04 x64

I was under the impression that Ubuntu 11.04 installed a flash player during initial setup.

Well, I was wrong. After installing Ubuntu on my system and heading to Pandora, I discovered that flash was not installed. I installed the version from Adobe’s site, but that one still didn’t work.

Here’s a quick way to install it from the command line:

$  sudo apt-get install flashplugin-nonfree

Restart your browser, and give it a try. YouTube and Pandora should work now.

Posted in CentOS, Computers, Linux

Sharing Home Folders via Samba in CentOS 5.4

I’ve decided to re-write this post and add more details. I originally wrote it for self-reference, but figured that it could be also useful to others.

To share the home folder using the command line, we are going to do this:

  • Log on as root
  • cd /etc/samba/
  • cp smb.conf smb.conf.original (create a back-up file of smb.conf)
  • nano smb.conf (or use your favorite text editor)

Scroll down all the way to the [homes] section, check the settings, make sure they are what you need. My [home] settings look like this:

[homes]
comment = Home Directories
browseable = no
writable = yes
valid users = %S
create mask = 0770
directory mask = 0770

If there isn’t a [homes] section, create it, and save your changes, close the file, and restart the smb service:

# service smb restart

If SELinux is disabled, or if it is on permissive mode, you are done. You should be able to connect to the share from a Windows, Linux, or Mac machine.

If you can’t connect to the home share, chances are that either the firewall is not allowing access to the smb service, SELinux is set to enforcing, or both, and it hasn’t been configured to allow access to the home shares. I suggest checking the status on SELinux if you are not sure; it will save you some frustration and time if you have difficulties connecting to the share.

Check and change the status on SELinux

To view the current SELinux mode:

# sestatus | grep -i mode

If its current mode says “enforcing”, you will need to run the following command in order to be able to access the home folders:

# setsebool -P samba_enable_home_dirs=1

To disable access to shared home folders, either edit the smb.conf file (path above) and remove the [homes] section, or change the settings on SELinux.

# setsebool -P samba_enable_home_dirs=0

Now you should be good to go. Restart the smb service, and connect to your home share.

For more information on SELinux, visit the CentOS Administrator Control of SELinux page, which contains more information.

I might do a little write-up with some of the basic SELinux settings…

—————————————————

TO BE MOVED TO ANOTHER POST….

If sharing a folder outside your home – for example, a folder that you created in “/”, you will need to add the command:

# chcon -t samba_share_t /pathToFolder

This enables sharingthe “pathToFolder” folder via Samba.

Posted in Computers, Fedora, Linux, Software, Ubuntu

Setup and Configure NFS Server/Client in Linux

Up until now, I had been accessing my Ubuntu server via Samba, from my Fedora 12 box. Until I discovered what NFS really is and how it works.

The actual guide which I followed can be found on the Ubuntu forums here.

I was able to successfully install the server portion of it on my Ubuntu 9.10 server, and access it from Fedora 12.

BUT! In order to get it to mount automatically when booting, instead of editing /etc/fstab, I had to edit /etc/mtab. The rest was fine. Keep this in mind if you get an error when adding it to your “fstab.”

Now that I better understanding of what NFS is, it’s time to do some good reading and research on it for future reference.

Posted in Computers, Fedora, Linux, Software

Installing an RDP client on Fedora12

There is no Remote Desktop Protocol (RDP) client installed on Fedora 12 by default – at least not one that I could find.

An RDP client is needed to connect to Windows Terminal Servers and other Windows machines using the RDP protocol.

Installing a gnome-RDP program is fairly easy, and can be done from the command line in a few minutes.

To install the gnome-RDP client on Fedora 12, launch Terminal by going to Applications > System Tools > Terminal, and type in the following commands (commands are in bold, explanation in parenthesis)

  • su – (needed to become root, type password when prompted)
  • yum install gnome-rdp (this downloads and installs the RDP program. Accept dependencies if prompted)

After that’s all done – should take about 2-3 minutes – you can find the gnome-RDP program by going to Applications > Internet > Gnome-RDP

Posted in Computers, Fedora, Linux

Fedora 12 – Extremely Slow Yum Updates

I’ve been playing with Fedora for a few weeks now, and, one of the things I’ve noticed is that using the software updates installer (GUI) is nearly useless. It is slow, and crashes nearly every time!

After doing a bit of ‘Googling’, I found that there are a few recommendations for yum mirrors. Here are two that I found, and that work.

To add these to your yum list of mirrors, edit the yum.conf file, located in /etc/yum.conf (Fedora 12)

Add these two lines to the bottom of the yum.conf file:

baseurl=http://mirrors.kernel.org/fedora/core/$releasever/$basearch/os
baseurl=http://mirrors.kernel.org/fedora/core/updates/$releasever/$basearch

Save the file and exit. From the command line, (logged in as root or with sudo privileges) do this:

$ yum check-update
$ yum update

The list of updates should populate, and the updates should start downloading a bit faster. It worked for me.

Good luck.