The I.T. Nerve Center

If you have recently updated to the most recent mod_security RPM from Fedora and you are running Drupal, you've probably noticed that certain things don't work correctly. Most specifically, some of the system CSS pages and tabs look funny, and if you're using the pathauto module with the default URL aliases you are probably get a Forbidden (or HTTP 403) when you try to access your content.

Last night I wanted to record some things (for personal use only) coming out of the stereo mix on my Linux workstation (currently running Fedora 11 x64). In the past I've been able to use Audacity (http://audacity.sourceforge.net/) - the awesome open source and free audio editing software available for Linux, Mac, and Windows. For some reason I wasn't able to get Audacity to pick up the stereo mix as an input so I searched around to find out how I could record the stereo mix coming out of a Linux workstations soundcard. Here's what I found ...

So I've wanted to try out Google Chrome on Fedora, but I'm kind of a purist in that I only like to install software on my workstation that comes packaged in an RPM. Many times if software is not available in RPM format I'll build my own with our in-house Koji buildsystem. Koji is the same system that the Fedora Project uses to build it's packages (http://koji.fedoraproject.org).

The Droid from Verzion was released today (2009-11-06) and already we have people at work coming over and asking if we will support it with our Exchange and ActiveSync infrastructure. Well the answer in our case is 'no' and here's why

So I was building RPM packages for the Asterisk GUI when it was the 1.0 branch. I haven't done work on the package in quite a while and I finally got around to building some new RPM packages for Fedora.

These Asterisk GUI RPMs are from the current SVN 2.0 branch and the SVN revision number is in the package name (e.g. RPM asterisk-gui-0.4986-3.fc11.noarch.rpm is SVN version 4986).

I try to do basic testing with the RPMs after they are built and they WorkForMe(tm) before I post them. YMMV.

OK, so I now have a combination of things that will successfully PXE boot a Linux qemu-kvm virtual machine with Windows DHCP services and Windows Deployment Services (WDS). I'm using the gPXE CD ISO image to PXE boot the VMs. Now the WDS PXE process works as expected.

We have our WDS/RIS server setup similar to the following wiki article on the syslinux wiki:

http://syslinux.zytor.com/wiki/index.php/PXELINUX#Deploy_Linux_from_Wind...

Here's what I did on my workstation (I'm using Fedora 11):

[UPDATE]: Read the updated article here

So VMware Server 2.x on Fedora 11 has been driving me nuts. I recently re-imaged my workstation and decided to ditch VMware Server and give Linux qemu-kvm a try since it is now the default hypervisor in Fedora and will be the standard hypervisor going forward in Red Hat Enterprise Linux (http://www.redhat.com/rhel).

We are an almost exclusively Windows shop so we use Windows DHCP servers and Windows Deployment Services (WDS/RIS) server to image all of our workstations and servers via PXE booting. If we were using an ISC dhcpd server things would probably have been a lot easier. Below I describe how I get things (partially) working.