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.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Roll your own dynamic dns
5 hours 6 min ago
- Please correct the URL for Salt Stack's web site
8 hours 17 min ago
- Android is Linux -- why no better inter-operation
10 hours 32 min ago
- Connecting Android device to desktop Linux via USB
11 hours 1 min ago
- Find new cell phone and tablet pc
11 hours 59 min ago
13 hours 28 min ago
- Automatically updating Guest Additions
14 hours 36 min ago
- I like your topic on android
15 hours 23 min ago
- This is the easiest tutorial
21 hours 59 min ago
- Ahh, the Koolaid.
1 day 3 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?