Review: The features Red Hat says will be in RHEL 5 sound great, but the promise was hard to prove in tests because of some system flakiness and omissions.
With the release of the first beta of Red Hat Enterprise Linux 5, eWEEK Labs was looking forward to getting an early look at the progress Red Hat has made with the platform since RHEL 4. Unfortunately, Beta 1 of Version 5 is too flaky for even testing purposes.
The biggest problem we encountered was RHEL 5s thoroughly broken software management system. In RHEL 5, Red Hat is moving from up2datethe software installation and update front end to RPM (Red Hat Package Manager)to yum, the software tool thats fronted the past few Red Hat Fedora Core releases. Red Hat is also moving RHEL to the same graphical package installer, Pirut, and graphical package updater, Pup, that have graced recent Fedora releases.
We have not been particularly impressed with Pirut or Pup in the pastwe much prefer the set of graphical package management tools, anchored by the excellent Synaptic, that ship with Ubuntu Linuxbut yum has always worked well for us from the command line. However, when we tested RHEL 5, back-end troubles with Red Hats repositories nearly prevented yum from working at all. (The update and install commands we issued worked for us about 10 percent of the time.)
Along similar lines, RHEL 5 includes some interesting-looking
new tools for creating and managing Xen virtual machines, such as a new panel applet for handling these tasks, but the tool didnt work for us. It appears that the Virtualization Manager application
that the applet is meant to call on is missing from the distribution at this point.
Also apparently absent from RHEL 5 so far is an implementation of the Red Hat Directory Server, technology that Red hat purchased from AOL and subsequently released as open-source software. We hope to see Red Hat address this gap with a well-integrated directory server implementation by the time that RHEL 5 ships.
Click here to read Labs review of Red Hat Directory Server.
The final straw for this round of testing was when sawhappily, at firsta menu entry for the Sabayon user profile editor for GNOME, an important piece of management framework and one whose progress weve been tracking through recent GNOME releases. We began to configure a sample user profile, but the operation locked up our X session, along with some unsaved edits in this very story.
Fortunately, we could enable from a separate machine on our network the autosave option for the Gedit text editor wed been usinga trick made possible by the same GNOME Gconf settings framework on which the Sabayon profile editor depends.
Advanced Technologies Analyst Jason Brooks can be reached at firstname.lastname@example.org.
Check out eWEEK.coms for the latest open-source news, reviews and analysis.