From: Linus Torvalds firstname.lastname@example.org Newsgroups: comp.os.linux.announce Subject: Approaching 1.2.x, I hope Date: 30 Jul 1994 02:05:45 +0300
I'm slowly making ready for something looking like a code-freeze for 1.2.x, and that means you can all start doing your favorite pre-release stuff: doing weird things to the latest kernels and seeing how they break. And maybe even sending me in a report (or patches if you feel like it).
The latest kernel right now is 1.1.36 (but they have changed daily) and contains the “mprotect()” system call that some people have been asking for. The last kernels have gone through major re-organizations in the memory manager, so we'll see how well it works out. Also, I wrote the mprotect stuff from scratch instead of using any of the old patches, so that's rather untested. If you have something depending on mprotect, do give this one a try.
(Aside: The mmap() interface still doesn't allow shared writeable mappings, but now you can do a shared read-only map and then “upgrade” it with mprotect(). That's not supposed to work, but I didn't bother to put in the extra checks, as I hope to have real write-mappings working some day. Going through mprotect is likely to give bogus results, etc; don't even try it as the kernel may do strange things.)
Lots of other stuff has also changed in the 1.1.x releases; sorry for not doing release-notes, but I'm too lazy. Essentially everything is faster, bigger and better, but it may be a bit unstable which is why I'd like people to test it out. The credit goes to everybody who has written code and tested so far (including, but not limited to Alan Cox, Eric Youngdale, Mark Lord, Jacques Gelinas, Hannu Savolainen, Frank Lofaro, Rik Faith, Bjvrn Ekwall, Remy Card, Dmitry Gorodchanin...,the list goes on forever).
Anyway, I hope 1.1.40 (or 1.1.50 or whatever) will turn out stable enough to be called 1.2.0 so that people who want to use mainly stable kernels know which version to get. Sadly, everything always works perfectly for me, so in order to find the problems some outside help is needed.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- 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