Canonical To Drop Support For Ubuntu 9.10
With an announcement on the security mailing list, Canonical has confirmed that support for Ubuntu 9.10 will cease on April 29 2011. This came as no surprise as it adheres to the expected support cycle of a .10 Ubuntu release, and 9.10 is now 18 months old.
The recommended upgrade path from 9.10 is to Ubuntu 10.4. 10.04 is a long term support (LTS) release, and support will end on April 2013. Note that, according to official Ubuntu documentation, it's not possible to skip a release version when upgrading. So, it's not possible to go straight from 9.10 to 10.10. It is possible to upgrade from 9.10 to 10.04 and then to 10.10. That's quite a lot to go through, and personally, I'd be tempted to make a fresh install and migrate the user data.
The canonical policy of upgrades at dependable intervals is admirable, but its cyclic nature does present a problem because end of life periods coincide with new releases. At the moment, a person with a system that is on 9.10 might wonder if it is better to wait for the 11.x series to begin.
Take into account that a full system upgrade often cannot be carried out on a whim. Also bear in mind that most people wait for a new release to be confirmed as stable before taking the plunge. Presumably, the repositories themselves will become inaccessible, so this means that, for many users, there will be a gap when 9.10 is difficult to maintain and 11.4 isn't quite ready for installation.
Perhaps Canonical need to consider release and support cycles that include a period of overlap? Okay, okay, in all fairness, some might wave a finger and argue that this problem could be avoided by carrying out regular upgrades when they become available. However, at 18 months or less, the lifespan of 9.10, doesn't feel that long on a personal level.
UK based freelance writer Michael Reed writes about technology, retro computing, geek culture and gender politics.
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!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
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