The openSUSE and Ubuntu Rollercoasters
The Linux World is rarely dull, but last week was an emotional roller coaster for users of openSUSE and Ubuntu. First Novell was sold to Microsoft and Attachmate with no mention of the fate of openSUSE. Then Ubuntu founder Shuttleworth told reporters that Ubuntu may switch from the six-month release cycle to daily updates. Both items garnered lots of speculation, elation, and worry until both parent companies finally addressed them.
In the wake of Sun's sell to Oracle and subsequent defunding and closing of several Open Source projects, FOSS advocates are understandably leery of any of our respected companies going to outsiders. So, when the news of Novell's sell to Attachmate hit the Web, users and developers of openSUSE were a bit worried. The news was later updated to include that a Microsoft holding company purchased many of Novell's patents. That set off more concern Linux-wide for the implications to Linux if Microsoft were to own UNIX. Some alarmists were afraid it would be SCO vs Linux all over again.
Even though not all of the details of the sale have been released and discussed, calmer heads pointed out that Linux was never proven to infringe upon UNIX in the first place, but Novell finally issued an announcement that UNIX was not sold to Microsoft. Just prior Attachmate had released their announcement that openSUSE would continue to be funded as before. While these announcements were a bit reassuring and most take them at face value, Andy Updegrove posted one of the most intelligent and comprehensive analysis of the situation. In summary, it's far from a straight-forward sale and Linux still may or may not be subject to litigation.
Then Ubuntu users were taken for a ride last week as well. The Register quoted Mark Shuttleworth, founder of Canonical and Ubuntu, as saying he would be moving the popular distribution from its six-month release cycle to daily updates through the Ubuntu Software Center. This sent shock waves throughout Ubuntu with lots of cheers and a few jeers, but mostly lots more speculation. Some thought this was another indication of Canonical's newly forming direction while many worried that more bugs and instability would result.
Then Rick Spencer, Director of Ubuntu Engineering, issued a statement on his blog retracting the statement. He said unequivocally, "Ubuntu is not changing to a rolling release" adding, "having a stable release with a six month cadence plus the option to stay cutting edge on certain packages (at your own risk) is not really a rolling release." Shuttleworth was quoted as saying they would be moving away from the six-month release cycle in favor of using daily updates. While the original source has been reworded and updated erasing that key quote, the original wording was the very definition of a rolling release. Whatever the reason for the turnaround, it was yet another up and down, back and forth, and to and fro in the Linux World last week.
Susan Linton is a Linux writer and the owner of tuxmachines.org.
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
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
- 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