Adobe Acrobat Reader 64 bit for Red Hat Enterprise Linux 6

I just got Adobe Acrobat Reader 64 bit for Red Hat Enterprise Linux 6 working, and it wasn't too easy. First, I downloaded a binary from http://get.adobe.com/reader/. I made it executable and ran it, but the program wouldn't launch.

Using 'strace -e open acroread', I could see it was trying to open a libxml2.so.2, but it wasn't seeing the one on my system under /usr/lib64. Doing a 'yum list libxml2\*', I could see there was also a libxml2.i686 that wasn't installed yet. After doing 'yum install libxml2.i686', the program started up a little further, but then complained about another missing library. More searching led me to do 'yum install gtk2-2.18.9-4.el6.i686'. At last, the Adobe Acrobat Reader 9.4 ran successfully.

Adobe Flash Player 10.1 64 bit for Red Hat Enterprise LInux 6 / Fedora 14

Recently I've upgraded both my laptop and desktop to 64 bit. I wanted to share how I got Fedora 14 working on my laptop and Red Hat Enterprise Linux 6 working on my desktop with Adobe Flash Player 10.1.

On both distributions, I found the same solution for how to get Adobe Flash Player worked. It was not installing an rpm file or setting up a yum repositority. Instead, I downloaded http://download.macromedia.com/pub/labs/flashplayer10/flashplayer10_2_p3_64bit_linux_111710.tar.gz from the http://labs.adobe.com/downloads/flashplayer10_square.html page. Adobe's download links lead me in circles when I first tried to get this working, but I finally searched their site and found this page to download the plugin.

To get Firefox to work, I extracted the downloaded file libflashplayer.so to each user's home: ~/.mozilla/plugins directory. For Google Chrome 64 bit to work with Adobe Flash, I had to create a /opt/google/plugins directory and then copy the extracted libflashplayer.so file into it. Remember to close all browser windows, and restart the browser for the plugin to take effect.

I resisted going to 64 bit Linux up until recently for this very reason: support for getting common things to work in 64 bit Linux lags, at least as of the end of January 2011.


Using Linux Kernel SysReq

The SysReq feature of the Linux kernel allows for special system requests to be sent to the kernel. This can be useful to get the kernel to do things that it wouldn't normally do for testing purposes. As I write this, I am trying to test the kdump feature of the kernel, which dumps the kernel memory when the kernel crashes. Using this feature I am able to cause a kernel crash by doing the following:

echo 1 > /proc/sys/kernel/sysrq
echo c > /proc/sysrq-trigger

You can press Alt + SysRq + c (or whatever the character is that is listed below) to do the same thing, but on two out of the three systems I just tried this on it failed to work. It definitely does not work from within the GUI, as it triggers a Print Screen instead.

Besides just getting the kernel to crash, there are the following other system requests:

m: memory allocation information
t: thread information
p: CPU register and flag informationo
s: sync mounted filesystems
u: unmount all filesystems
b: reboot immediately
o: poweroff immediately

When the request is to do something to display information, then this data is typically dumped to /var/log/messages.

To permanently enable system requests, add to /etc/sysctl.conf the following:
kernel.sysrq = 1
To make system requests immediately available, run 'sysctl -p' as root or reboot.


Dad Died Day

After enjoying two weeks of vacation, the new year seemed to be off to a good start. At least January 1, 2011 was a good day. I got to talk to both of my parents, wish them a Happy New Year, and let them know that the Oklahoma Sooners (my Dad's favorite team) were on ESPN.
By the time they got to watching the game that night, it was already past half-time. My Mom said that Dad got to watch the first half of the game in the morning. As I watched it that night, I was enjoying it so much knowing that my Dad was watching it and enjoying it, too.
January 2, 2011 Dad died. I'm struggling to pull my head out of such a funk. I'm missing how much my Dad had shaped me throughout my life, and reflecting on what life will be like for my family without him.
It's just been a couple of days since this happened, so I feel like I'm just beginning the grieving process, and tomorrow, as I go to be with my family, I'm going to be diving into it deep. Next week, back to work, and a rapid track course to keep me busy. The usual routine might be what I'll be doing in less than a week, but it won't be the same after Dad Died Day.

About Me - WrightRocket

My photo

I've worked with computers for over 30 years, programming, administering, using and building them from scratch.

I'm an instructor for technical computer courses, an editor and developer of training manuals, and an Android developer.