Red Hat Linux 6.0
Manufacturer: Red Hat Software, Inc.
Reviewer: Jason Kroll
Red Hat Linux 6.0 is Red Hat's latest distribution, and it has improved noticeably since the days of version 5. In keeping with the high standards of modern distributions, Red Hat Linux 6.0 is relatively easy to install, preconfigured, aesthetic and functional. It comes with the standard Linux applications (including Netscape) and also includes a special applications CD, with over 50 various commercial applications (most of which are demo versions which expire or are disabled). GNOME (running by default with the Enlightenment window manager), Red Hat's desktop environment, is well-configured and attractive. In addition to aesthetic improvements, Red Hat made some significant technical changes in its newest distribution, including the complete adoption of the EGCS (Experimental GNU Compiler System). Still, many things will be familiar to users of previous Red Hat releases.
Red Hat Linux 6.0 comes with three CDs (and a floppy, just in case), the first being an auto-booting installer which looks rather like previous Red Hat installers. It presents three installation options: Workstation-class, Server-class and Custom. The 400+ page installation guide contains very little information regarding the installation options, but having tested them, I really recommend a custom install.
Before proceeding with any kind of installation, however, the installer offers a choice of eleven languages which are mostly implemented (though some need more work than others). These are mainly just for the installation process, although GNOME does support a few languages; so if you install in another language for the fun of it, your system could end up running in it. After language selection, the installer offers a choice between installation and upgrade.
Upgrading is a rather quick process; a large part of the convenience aspect of Red Hat is the ability to upgrade, whether one is dealing with individual packages (via RPM/GnoRPM) or a complete system. Upgrading is rather automated compared to installation, which presents various options.
The workstation-class installation is quite functional and easy to use but is not as complete or fun as a custom installation; KDE, among other things, is noticeably missing. The server-class installation is meant for servers and will be of little interest except to network enthusiasts. It is not exactly up-to-date, and still runs FVWM2 (AnotherLevel) instead of the newer desktop environments; it is reminiscent of Red Hat releases from quite a while ago. The custom installation is probably what most users would want, and is simple enough to make if one knows what hardware is inside the machine.
Custom installation allows the user to choose packages either categorically or one by one; in the latter case, the installer keeps track of dependencies between packages. The user is also given the choice of which programs to be launched automatically at startup, and is required to partition his own drives. A choice of either Disk Druid or fdisk is given for partitioning the drives. Disk Druid is menu-driven and simple enough, as long as one is familiar with partitioning; the time-tested fdisk is just as adequate. Although both partitioning programs perform the same task in basically the same way (selecting partitions, sizes and mount points), using a menuing system seems to be easier for most people.
Video configuration can be a bit problematic. Curiously, although the lists of available monitors and video cards are quite long, the installer cannot probe for the video card. Probing for a card instead of querying the user should not be very difficult to implement, since X can probe successfully. The video mode tests failed even though my card and monitor were listed, but after installation, X worked fine. Also, if one could test various preconfigured monitor frequencies against the standard X test pattern, a better picture could be had. Since you will presumably have this Linux system for a while before reinstalling, it would be worth the effort to have an optimally configured display. Too bad this option is not available.
If you do not know your hardware, installation can be a hang-up. The only thing the installer could successfully detect was my mouse; everything else had to be entered manually. Again, this is fine if you know your hardware, and it is probably even safer than probing. However, new Linux users to whom Red Hat is often recommended and people who do not know what is inside their computers might prefer the computer to figure out for itself what hardware is present. Certain other installers probe successfully, so accurate probing is possible. Since ease of use has long been one of Red Hat's main attractions, it seems the installer could stand to be brought up to a level on a par with the overall quality of the distribution.
Despite the need to enter hardware information manually, installation is not exactly difficult and an experienced user could reasonably expect to complete an installation in approximately thirty minutes. Once the installation process is at an end, the option is presented to have X start up by default at boot time. If you answer yes, reboot and log in, you will be greeted by a mysterious footprint on the desktop, shaped oddly enough like a G with toes.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide