Well I realized during my first installation that this simply was not the case. In fact throughout the entire process I felt entirely at home with RHELAS (wow that acronym was a handful). While there is plenty of cool stuff to talk about in this release, I am going to limit the scope of what I'm going to talk about to just relevant issues new to RHEL and issues relating directly to server installations of this product (scalability performance). If you (the reader) is already familiar with recent Red Hat releases or Fedora, then much of this may not be news to you.
So whats new in this release you ask?
What sort of cool features can I expect from this release that I didn't have in RHEL 2.1. Well there are quite a few features actually. While they are standard in Fedora and older regular Red Hat releases I figured I'd go over a few of them. The first that jumped out at me is that RHEL 3.0 supports Logical Volume Management. This is a way for an administrator to 'logically' manage disk space (rather than physically partition the disk) so that resizing file systems is easy. I would have loved to test this feature for this review but sadly I don't have access to a machine with enough disk space to make this meaningful (but rest assured this is on my to do list :) ).
RHEL 3.0 also adds support for Native POSIX Threading Libraries. This is simply a new implementation of POSIX threads for Linux. From all that I've read this promises greater performance than the older implementation in Linux but since I am not much of a programmer and I don't feel qualified to go into more detail for fear of getting anything wrong.
The last change Red Hat made that I felt was relevant to a review of this product was to the kernel rpm package. The package was separated into 2 packages: normal and unsupported. This makes quite a but of sense to me simply because it would be unreasonable for Red Hat to support every conceivable piece of hardware someone may be using. This way they can ensure that their core kernel is solid while users have the option of using other drivers/features that are not included by default. Although if one of these unsupported features if one that you need, support can be arranged through Red Hat in some situations.
The installation was exactly what I was expecting. Anaconda (Red Hat's installation program) worked and felt just like Red Hat 9. Except I normally use reiserfs as my file system of preference. I had booted up and where I would have expected the option to format as reiserfs I had nothing. This to me made sense if Red Hat didn't feel that reiserfs was stable enough for their prime time server OS that they would be expected to support. The only other thing I encountered (or didn't encounter) that I was used to in the Red Hat install process was the option to install a 'Personal Desktop', 'Workstation', etc. This again makes sense because the product is named 'Advanced Server'. The default install included the usual: Gnome, Apache, Samba, and Red Hat's graphical configuration tools. I accepted the defaults wherever possible for the sake of this review.
Set up a few servers:
First install I did was on my main desktop (AMD T-Bird 1.4, 1 Gig RAM, 60 Gig Western Digital Drive, Sound Blaster Live, nvidia GeForce 4 4600 ti). I had never really used the Red Hat configuration tool for Apache (httpd as Red Hat likes to call it). So I figured that this was as good a time as any my feet wet with this (I had always just edited httpd.conf manually). And since it was installed by default anyway I figured: 'What the heck?!'. I downloaded the latest phpnuke from the site (www.phpnuke.org). I figured this was was a good test of functionality because it involved apache, php, and mysql to get the entire package working (plus I've used it a few times in the past so I knew how it works). I installed the rpm packages required using Red Hat's graphical package management system. This seemed to go smoothly, but I'm used to the functionality of synaptic and apt, so I was not totally impressed with it, but whatever works. After feeding it the CD's it asked for the packages were installed. I went to the HTTPD configuration utility and made a few changes to the default document root directory, browsed the rest of the options in the tabs and clicked 'OK'. Wow that was easy (though I still felt a little weird not editing the con fig file by hand). After creating the necessary database per the phpnuke instructions, restarted the relevant ervices via the handy dandy Red Hat Service Configuration application and my site worked perfect. Just as it had in the past although I must say, it took much less time than when I did in FreeBSD with ports.
- "RHEL AS, Page 1"
- "RHEL AS, Page 2"