Fedora /etc/os-release

Fedora 17 added support for /etc/os-release. Here is the contents of that file: # cat /etc/os-release NAME=Fedora VERSION=”17 (Beefy Miracle)” ID=fedora VERSION_ID=17 PRETTY_NAME=”Fedora 17 (Beefy Miracle)” ANSI_COLOR=”0;34″ CPE_NAME=”cpe:/o:fedoraproject:fedora:17″ A number of fields are specified, some mandatory, some optional. CPE_NAME is a stylized name for the operating system, following the proposed Common Platform Enumeration specification. This field is optional. This file is part of the generic-release-17-1.noarch package.

Add Adobe Flash to Firefox on Fedora 17

So you want to get Adobe Flash working on Firefox in Fedora 17? Here is a quick guide to doing it. Obviously you need root privileges to install the packages. First you need to install the appropriate repository (32-bit or 64-bit) for the Adobe RPM packages: # Adobe 32-bit x86 repository rpm -ivh rpm –import /etc/pki/rpm-gpg/RPM-GPG-KEY-adobe-linux # Adobe 64-bit x86_64 repository rpm -ivh rpm –import /etc/pki/rpm-gpg/RPM-GPG-KEY-adobe-linux If you cannot download these RPMs, check at Adobe for the latest version and download that. Then run yum to install the following packages: yum check-update yum install flash-plugin nspluginwrapper alsa-plugins-pulseaudio libcurl

Recursively Change The UID:GID For Users Files

Fedora 17, changed the default starting UID and GID for regular users from 500 to 1000. See the 1000System Accounts project page for more information. So what is the best and easiest way to fix up existing files that might have lower UID and GIDs? It turns out that the GNU version of chmod has a very useful long option for doing exactly what we want. Suppose you wish to change all files with a UID/GID of 500:500 to a new UID/GID of 1000:1000, here is how to do it: chown -R –from=500:500 1000:1000 / chown -R –from=501:501 1001:1001 /

Fedora 17 "Error: Protected multilib versions"

Getting an error like the following when installing a package or group of packages on your Fedora 17 system? Error: Protected multilib versions: XXXXXXXX.fc17.i686 != XXXXXXXX.fc17.x86_64 This is because whenever you have both 32 and 64 bit versions of a package, they must be of the same version and release. The error message is showing you that the 32 bit version-release of the package does not equal (!=) the 64 bit version-release. You either need to update the 32 bit version to match the 64 bit version, or erase the 32 bit version to get rid of this error. While