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 http://linuxdownload.adobe.com/adobe-release/adobe-release-i386-1.0-1.noarch.rpm rpm –import /etc/pki/rpm-gpg/RPM-GPG-KEY-adobe-linux # Adobe 64-bit x86_64 repository rpm -ivh http://linuxdownload.adobe.com/adobe-release/adobe-release-x86_64-1.0-1.noarch.rpm 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
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 /
While Matthew Garrett has been gathering a lot of attention with his blog posts about UEFI Secure Boot, another Red Hat employee, Peter Jones, has been doing excellent work down in the trenches developing a utility (pesign) for securing signing of UEFI binaries on Linux platforms and a setup tool for enrolling your public key(s) in UEFI firmware. Is Secure Boot breakable? Yes, of course, but it is not that easy to do. The technology underlying Secure Boot is battle tested and proven. Here is how it basically works. Assuming you have generated a 2048-bit RSA key, the signing process
If you are on a RPM-based Linux platform (such as Redhat, CentOS, Fedora, ArchLinux, Scientific Linux, etc.), here are two ways to determine the list of packages installed. Using yum: yum list installed Using rpm: rpm -qa You can also easily get a count of the installed packages by piping the output to wc: yum list installed | wc -l rpm -qa | wc -l
In this post, I examine how to directly boot Fedora 17 from UEFI firmware. I also discuss a number of non volatile variables which the Linux kernel can create during an kernel crash.