Linux Code Freeze
In short, the next version of Linux (0.99.15) will be a “full-featured” release, and only obvious bug-fixes to existing features will be applied before calling it 1.0. If this means that your favourite feature or networking version won't make it, don't despair: there is life even after beta (and it's probably not worth mailing me about it any more: I've seen quite a few favourite features already ;-).
In fact, 1.0 has little “real meaning”, as far as development goes, but should be taken as an indication that it can be used for real work (which has been true for some time, depending on your definition of “real work”). Development won't stop or even slow down: some of it has even been shelved pending a 1.0 already.
Calling it 1.0 will not necessarily make all bugs go away (quite the opposite, judging by some other programs), but I hope it will be a reasonably stable release. In order to accomplish this, the code-freeze after 0.99.15 will be about a month, and I hope people will test out that kernel heavily, instead of waiting for “the real release” so that any potential bugs can be found and fixed.
As to where we are now: as of this moment, the latest release is the `r' version of pl14 (aka “ALPHA-pl14r”). I've made ALPHA releases available on ftp.funet.fi almost daily, and expect a final pl15 within a few more days. Testing out the ALPHA releases is not discouraged either if you like recompiling kernels every day or two..
And finally: we also try to create a “credits” file that mentions the developers of the kernel and essential Linux utilities. The credit file compilator is firstname.lastname@example.org (John A. Martin), and if you feel you have cause to be mentioned in it, please contact him.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
- SourceClear Open
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