The End Is In Sight For RHEL 3
It's doubtful that anyone really likes having to upgrade, but at some point it has to be done. For those particularly adverse to the upgrade — like enterprise users, with good reason — there are extra-long windows, but eventually even those windows close. Last week, Red Hat announced that the oldest of its supported platforms has officially entered the homestretch.
Red Hat Enterprise Linux 3 was originally released in October 2003, when the kernel was still 2.4 and several of today's most popular distributions weren't even a twinkle in a developer's eye. As one might expect, quite a bit has changed in the Linux world over the past seven years.
Those still holding on to RHEL 3 will see at least a bit of the change come October, when the operating system will reach a well-deserved end-of-life. Per Red Hat's support policy, new software functionality has been unavailable since mid-2006, while minor releases, "new functionality, new hardware enablement [and] updated installation images" ceased in mid-2007.
According to Advisory RHSA-2010:0386-1, as of October 31st:
New bug fix, enhancement, and security errata updates, as well as technical support services will no longer be available for the following products:
- Red Hat Enterprise Linux AS 3
- Red Hat Enterprise Linux ES 3
- Red Hat Enterprise Linux WS 3
- Red Hat Enterprise Linux Extras 3
- Red Hat Desktop 3
- Red Hat Global File System 3
- Red Hat Cluster Suite 3
Those still running RHEL 3 in a production environment are strongly advised to begin moving to RHEL 5, itself three years into its seven year tenure. (RHEL 6 is currently in beta, with no official word on when a final version may be available.) Active Red Hat subscribers can update to any currently-maintained version at no cost.
Justin Ryan is a Contributing Editor for Linux Journal.
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!
- Stunnel Security for Oracle
- Interview with Patrick Volkerding
- Tips for Optimizing Linux Memory Usage
- What's GNU
- Secure Logging Over a Network
- Apache 2.0: The Internals of the New, Improved
- User-Mode Linux
- Getting Started with mod_security
- Using C for CGI Programming
- FSlint: annoyingly vague, but useful
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