Torvalds Christens The Next Linux Kernel Series 3.x
It's official, kernel version 3.0 is on its way. Linus confirmed this both in an announcement and by checking in the first 3.0 release candidate. The new branch is not expected to include any major milestones in terms of features, but it may stimulate developers to adopt policies of cruft removal and modernization.
Linus had mooted the idea of skipping 2.8 (stable branches use even numbers) in favor of 3.0 a couple of weeks ago on the kernel mailing list.
On the forums, reaction to the news has been mixed, with some wondering if Linus is falling prey to the current trend of large major version number jumps to give the impression of significant progress. But, that raises the question: is it worse to have a small version number jump for a new release that breaks everything, or a large version increase that turns out not to be hugely different from the previous release. It's a point that Linus touches on in his announcement:
[...]we are very much *not* doing a KDE-4 or a Gnome-3 here. No breakage, no special scary new features, nothing at all like that. [...] So no ABI changes, no API changes, no magical new features - just steady plodding progress.
His justification for the version jump is two-fold. First, the 2.6.x branch was around for an unusually long time. 2.6 has been with us since 2003, and version 2 itself began way back in 1996. Second, it is symbolic because, as the Linux kernel is 20 years old this year, it is now entering its third decade.
So, it's not a ground-breaking release, and the message seems to be: everything's going great, prepare for more of the same.
The original announcement on the Linux Kernel Mailing List.
UK based freelance writer Michael Reed writes about technology, retro computing, geek culture and gender politics.
|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
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- A Topic for Discussion - Open Source Feature-Richness?
- Tech Tip: Really Simple HTTP Server with Python
- Please correct the URL for Salt Stack's web site
2 hours 50 min ago
- Android is Linux -- why no better inter-operation
5 hours 6 min ago
- Connecting Android device to desktop Linux via USB
5 hours 34 min ago
- Find new cell phone and tablet pc
6 hours 32 min ago
8 hours 1 min ago
- Automatically updating Guest Additions
9 hours 10 min ago
- I like your topic on android
9 hours 56 min ago
- This is the easiest tutorial
16 hours 32 min ago
- Ahh, the Koolaid.
22 hours 10 min ago
- git-annex assistant
1 day 4 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
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?