Well, MySQL has released another Enterprise-only version. Not only are there no binary packages for the community, but they haven't even bothered to post a link to the source on the download page. Why they do this, I don't know, because it would really only take another 15 seconds to update the link to the source package on the community release page. As it stands, in order for someone to find out about this release they'd either have to be crawling the MySQL FTP site or watching the Enterprise edition release logs.
In any case, not to be left behind just because I "can't afford"/"refuse to pay" $600 (minimum) per server, I have once again built packages to provide a community release of the newest stable version of MySQL.
The files in my yum repository (32- and 64-bit) have been updated to the newest available versions of 'apr' (1.2.8), 'apr-util' (1.2.8), and 'pcre' (7.0). 'httpd' has also been rebuilt to take advantage of the newer versions. I would suggest that all users apply these updates.
Well, I've finally gotten VMWare working again. Now that I've got a suitable 64-bit development environment running, I'm finally able to compile both 32-bit and 64-bit binaries for httpd, PHP, MySQL, etc.
If you run a 64-bit system and you haven't already taken a look, now might be a good time to check out my yum repository.
If you're a regular reader of the site, you may have noticed the "Yum Repository" link at the top of the page. If so, congratulations, you're one of the first to try out a new service I'm offering on this site.
As it appears, most of the posts on this blog thus far have been how-to's on updating your RHEL & CentOS servers to use the newest versions of httpd, PHP, and MySQL. I'm still planning on creating those articles as needed, but only the source packages will be linked to the page. Binary releases for i386 (x86-64 coming soon) will now be available for easy updating through my brand new yum repository (and yes, before you ask, 'up2date' can read a yum repo).
I'm hoping that this will cut down on not only the effort required to update your systems, but also on the possible glitches that can come from updating a complex set of packages like PHP (where, with prior provided methods, you'd need to type out all of the file names that you wanted to install all at once, otherwise you'd have dependency issues with upgrading from an earlier release).
Well, I'm back again with yet another release of MySQL. Coming only a few short days after the Enterprise release of 5.0.36 under the Monthly Rapid Update program, MySQL has decided to release 5.0.37 as a community edition.
As with my last release, this one is based on the latest Fedora src.rpm from the development tree and has been modified to use the newest source package, package new files that didn't exist before, remove patches that have been integrated into the main code-base, and, as a first for me, to add a patch to reverse part of a recent commit that breaks regression testing.
If you followed my earlier guide on Upgrading to MySQL 5.0.36 on RHEL & CentOS 4, you don't really need to read this. If you haven't, you may want to read the other for reference, but I would strongly recommend that you follow this guide instead.
Let me start by saying, "yes, I know that MySQL 5.0.36 isn't on the download page yet". That's because this is an enterprise-only release under the Monthly Rapid Update program. That said, there is absolutely nothing preventing the build of this version as a community release.
As with my prior release of MySQL 5.0.33 for RHEL & CentOS 4, the i386 binary packages and the src.rpm are packaged in the "Red Hat"-style that is used for the RHEL-, CentOS-, and Fedora-distributed packages. That means that the client & shared libraries are packaged as "mysql", that the "mysqld" daemon is packaged as "mysql-server", etc.
Just under 2 weeks ago I ordered an Auzentech X-Meridian 7.1 Sound Card based on some recommendations I read over on AVSForum.com. The card finally arrived the middle of this past week and I got the time to install it in my HTPC last night (to replace the integrated sound from nVidia's SoundStorm).
For those of you that don't know, the X-Meridian is based on the C-Media Oxygen HD CMI8788 audio processor. Now, if you're not familiar with that particular chip, just know that it can do pretty much anything, including but not limited to Dolby Digital Live, Dolby ProLogic IIx, Dolby Headphone, Dolby Virtual Speaker, DTS Interactive, and DTS Neo:PC. While this card does pack some incredible features for digital output, where it really shines is when you switch over to the analog outputs.