Skip to comments.Say Hello To Linux 3.0
Posted on 05/30/2011 10:08:42 AM PDT by zeugma
.. except there are various scripts that really know that there are three numbers, so it calls itself "3.0.0-rc1".
Hopefully by the time the final 3.0 is out, we'll have that extra zero all figured out.
Yay! Let the bikeshed painting discussions about version numbering begin (or at least re-start).
I decided to just bite the bullet, and call the next version 3.0. It will get released close enough to the 20-year mark, which is excuse enough for me, although honestly, the real reason is just that I can no longer comfortably count as high as 40.
The whole renumbering was discussed at last years Kernel Summit, and there was a plan to take it up this year too. But let's face it - what's the point of being in charge if you can't pick the bike shed color without holding a referendum on it? So I'm just going all alpha-male, and just renumbering it. You'll like it.
Now, my alpha-maleness sadly does not actually extend to all the scripts and Makefile rules, so the kernel is fighting back, and is calling itself 3.0.0-rc1. We'll have the usual 6-7 weeks to wrestle it into submission, and get scripts etc cleaned up, and the final release should be just "3.0". The -stable team can use the third number for their versioning.
So what are the big changes?
NOTHING. Absolutely nothing. Sure, we have the usual two thirds driver changes, and a lot of random fixes, but the point is that 3.0 is *just* about renumbering, 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. We've been doing time-based releases for many years now, this is in no way about features. If you want an excuse for the renumbering, you really should look at the time-based one ("20 years") instead.
So no ABI changes, no API changes, no magical new features - just steady plodding progress. In addition to the driver changes (and the bulk really is driver updates), we've had some nice VFS cleanups, various VM fixes, some nice initial ARM consolidation (yay!) and in general this is supposed to be a fairly normal release cycle. The merge window was a few days shorter than usual, but if that ends up meaning a smaller release and a nice stable 3.0 release, that is all
good. There's absolutely no reason to aim for the traditional ".0" problems that so many projects have.
In fact, I think that in addition to the shorter merge window, I'm also considering make this one of my "Linus is being a difficult ^&^hole" releases, where I really want to be pretty strict about what I pull during the stabilization window. Part of that is that I'm going to be travelling next week with a slow atom laptop, so you had better convince me I *really* want to pull from you, because that thing really is not the most impressive piece of hardware ever built. It does the "git" workflow quite well, but let's just say that compiling the kernel is not quite the user experience I've gotten used to.
So be nice to me, and send me only really important fixes. And let's make sure we really make the next release not just an all new shiny number, but a good kernel too.
Go forth and test,
3.0 is apparently not going to be a major change. Seems like we're moving from 2.6.x to 3.0.0 pretty much just because Linus wants to. I'm fine with it, given that there really has been a lot of change in the Linux kernel in the years since the 2.6 series started. There's also an article at Slashdot (of course). Some of the comments are even funny.
Mods, feel free to move to blogs or whatever if you want.
I hate to post and run, but I’m about to hop on my Sportster and blow through a few tanks of gas this beautiful memorial day. God bless our soldiers, past, present, and future.
Please don’t use the term “Nerd”. The word “Geek” is far more complementary.
Just updated two Dell laptops from Fedora 14 to Fedora 15. The Dell 820
has the Broadcom BCM4312 based wireless mini_PCI...fails. The
Dell D630 has the IntelPRO card...no problem. Not thrilled with the
Gnome 3.0 change. The D820 has to run crippled with an external
Ethernet to 802.11b/g gaming adapter until I can fix the wireless drivers.
The switch to the 3.0 kernel numbering will impact folks who carefully
script installs against kernel version. Another time burner for no net
gain in features.
“Just updated two Dell laptops from Fedora 14 to Fedora 15. The Dell 820 has the Broadcom BCM4312 based wireless mini_PCI...fails. The Dell D630 has the IntelPRO card...no problem. Not thrilled with the Gnome 3.0 change. The D820 has to run crippled with an external Ethernet to 802.11b/g gaming adapter until I can fix the wireless drivers.Annoying.
The switch to the 3.0 kernel numbering will impact folks who carefully script installs against kernel version. Another time burner for no net gain in features.”
I just turned on my Dell w/Windows 7 and it worked. No time burned ;-).
Don't wanna hafta upgrade my Ubuntu 10.4 LTS! DON'T WANNA!
< /drama >
But seriesly, the one tip I've found for dramatically speeding up Ubuntu's (and probably other Linux distros') performance was to reduce "swappiness" from the default 60 to 10
The least he could have done is put the new KDE-4 or Gnome-3 face on it.
A new version should offer the user at least something different.
You're talking applications. They kernel is code that all the applications run on.
Thanks for the updater.
I still use windows primarily, but I fire up any of my several Linux live CDs on a regular basis to perform certain
They are like handy little swiss pocket knives. I have Kaspersky Antivirus in a Linux bootable CD. It goes out and
updates the virus signaures too, before it scans.
It has saved me from rootkits a few times.
I can assure you that I've wasted many more hours helping people with Win 7 problems. Definitely a time burner. The D820 isn't even supported by Dell for Win 7.
I’m running a newish Dell and I have had zero hours OS-related down time (a hard drive crapped out, though), although I do little more than surf/email/upload/download music
I've found a distro I really like: CrunchBang. I've ran it from a USB flash drive and I'm pretty happy with the responsiveness of Openbox.
But, I have a netbook with no optical drive. I can't figure out how to partition and install from the USB drive.
I have "Windows 7 Starter" with the hard drive not partitioned. I'd like to partition the drive and install CrunchBang on the other partition.
Can this even be done if I don't have an optical drive? I'd love any suggestions at this point.
I take huge offense being called a geek. I do NOT bite chicken heads off! nerd is the much preferred term.
Yes, I understand that.
Please correct me if I’m wrong (I’m still new to Linux), but isn’t KDE and Gnome simply the interface layer? In other words the desktop atmosphere, etc.?
As far as the kernel, it sounds like he only made driver upgrades and a few other tweaks.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.