Slashdot Mirror


Linus Renames 2.6.40 Kernel To Linux 3.0, Announces Release Candidate

An anonymous reader writes "Linus just released the first -rc of the next kernel series, but rather than continuing development as the Linux 2.6.40 kernel, he has renamed it to be the Linux 3.0 kernel." And he's tacked on a second dot and another zero (3.0.0), at least for now, because many scripts expect and rely on a three-part kernel version.

46 of 378 comments (clear)

  1. The problem with incremental version numbers by isorox · · Score: 4, Insightful

    There's never been a large enough jump in features to justify a major release increment, yet 2.6.40 is more distinct from 2.6.0 than 2.6.0 was from 2.0.0

    1. Re:The problem with incremental version numbers by Tar-Alcarin · · Score: 5, Insightful

      There's never been a large enough jump in features to justify a major release increment, yet 2.6.40 is more distinct from 2.6.0 than 2.6.0 was from 2.0.0

      I think that's part of the reasoning behind this; it's just time to reset the bar.
      If you have hardware or software that advertises itself as being "linux 2.6 compliant" today, it could still be up to 7 years old, and not give a damn about features added since then.

  2. Re:Really? That's important ? by master5o1 · · Score: 5, Funny

    Clearly 3.0.0 is 0.4.60 more advanced than 2.6.40.

    --
    signature is pants
  3. Version numbers? We can increment them! by MasterPatricko · · Score: 5, Informative

    I like his 3.0 commit message
    "Version numbers? We can increment them!"

    Thankfully, Linus hasn't rewritten the kernel in VB.

    Also this version has codename "Sneaky Weasel"

    --- a/Makefile
    +++ b/Makefile
    @@ -1,8 +1,8 @@
    -VERSION = 2
    -PATCHLEVEL = 6
    -SUBLEVEL = 39
    -EXTRAVERSION =
    -NAME = Flesh-Eating Bats with Fangs
    +VERSION = 3
    +PATCHLEVEL = 0
    +SUBLEVEL = 0
    +EXTRAVERSION = -rc1
    +NAME = Sneaky Weasel
     

    --
    I'd tell a UDP joke, but you may not get it. I'd tell a TCP joke, but I'd have to keep repeating it until you got it.
    1. Re:Version numbers? We can increment them! by Anonymous Coward · · Score: 3, Funny

      Linus is afraid that my prophecy from 2005 is coming true, so he's been trying to cheat destiny (as the 3.0 version codename clearly indicates), but it's too late, with this version number jump Linux has jumped the shark. The End is near, brace yourselves.

      Linux: the moribund wraith

      When Linux kernel hits version 2.8
      and you begin to cry,
      turn from Linux to BSD
      or along with Linux you, too, shall die.

      No amount of kernel hacking
      can save Linux from demise,
      your skills and knowledge are lacking,
      which, frankly, is no surprise.

      For your kernel is not eternal,
      it is a mere toy which will fry
      in the blazing flames of glory
      of the BSD flags raised high.

      With BSD you get diversity,
      with BSD you get stability,
      with BSD you get security,
      with BSD you get performance and tranquility.
      Your kung fu is no match for our ability.

      Can you hear him sobbing, your beloved Tux?
      He knows what's coming and he, too, thinks Linux sucks.

      SlashC*****P**

    2. Re:Version numbers? We can increment them! by lxs · · Score: 2

      I won't believe that Linux is dying until Netcraft confirms it.

  4. Re:Wow by Jaiz909 · · Score: 2

    Maybe this year is the year of the Linux desktop too?

  5. Re:Really? That's important ? by maeka · · Score: 5, Funny

    Clearly 3.0.0 is 0.4.60 more advanced than 2.6.40.

    Oh shit! Are you telling me there is a regression in how LInux does arithmetic?

  6. Long-term Support for 2.6.3x? by owlman17 · · Score: 2

    LFS user here. Will 2.6.39 get the LTS treatment just like 2.6.35 down to 2.6.32? Would be nice to have a stable target for years to come. I have a box that's still using 2.6.16 (formerly LTS) and another that's 2.4.37. Moving up from "minor" releases, e.g. from 2.6.35 to 2.6.36 haven't really been as minor as they used to be. They tend to be somewhat nerve-wracking experiences. Personally sticking to 2.6.35 as long I can.

    1. Re:Long-term Support for 2.6.3x? by Sipper · · Score: 2

      LFS user here. Will 2.6.39 get the LTS treatment just like 2.6.35 down to 2.6.32? Would be nice to have a stable target for years to come. I have a box that's still using 2.6.16 (formerly LTS) and another that's 2.4.37. Moving up from "minor" releases, e.g. from 2.6.35 to 2.6.36 haven't really been as minor as they used to be. They tend to be somewhat nerve-wracking experiences. Personally sticking to 2.6.35 as long I can.

      ALL new releases of the Linux kernel are considered to be stable releases. These get security updates and fixes (at least for a couple of months) for issues are reported; the rules are "no regressions", so if something breaks that used to work, you can report it and it will get fixed.

      Something you could call an "LTS" version essentially only happens when someone chooses to take ownership of maintaining a particular release for a while, usually for their own reasons. So if a Red Hat engineer decides to maintain 2.6.18 and backport drivers and fixes, you'd think of it as an LTS release, but it would mainly be that one person maintaining that branch rather than something all of the Linux developers decided to do. The maintainers as a whole have no good reason to do an LTS release a-la-Ubuntu, because every new kernel release is a stable kernel release, so from their point of view, doing an LTS release would just bog down development work.

      Additionally, even when someone or a distribution (like RHEL) decides to maintain a particular kernel as if it were an LTS release for a while, the Linux maintainers generally frown upon it, because it's quite difficult to keep up with all of the changes going on in the development kernel and sometimes might be difficult or impossible to backport due to internal infrastructure changes. Thus these old kernels tend not to keep up with newer kernel features and newer drivers, which is why the kernel maintainers think trying to do this isn't worth the effort.

      Now, I happen to be a person who builds his own kernel also, so I understand where you're coming from concerning the "minor" releases being a bit scary. Sometimes they are, like the Ext3 bug that happened in 2.6.19. I think the best you can do is exactly what you're doing -- which is to hold back one or two kernel versions such that they get security/bug fixes. However if everybody did that, then nobody would find the bugs to be fixed, so at the same time it's also nice to experiment with newer kernel versions in order to give the Linux kernel maintainers feedback, try out some of the new features, and to get some vision as to what is coming.

      This is one area where it's nice to be able to use some kind of package management, because that way you can add your own kernel and remove it later if it doesn't work out. Generally I make such kernel packages on Debian via 'make-kpkg' which is in the 'kernel-package' package, but the Linux kernel also itself has a make target for making .deb or .rpm packages, too. (Try running 'make help' within a top-level Linux kernel directory, and look under the "Kernel packaging:" section.) I'd like to think that your LFS distribution would let you do some kind of package management.

  7. Arithmetic by AliasMarlowe · · Score: 2

    Clearly 3.0.0 is 0.4.60 more advanced than 2.6.40.

    Hmm, are you forgetting to carry the overflow from minor digit to major digit? In this case, 3.0.0 would be 0.3.60 more advanced than 2.6.40, naturally.

    --
    Those who can make you believe absurdities can make you commit atrocities. - Voltaire
  8. Re:Sigh. by bunratty · · Score: 2, Insightful

    There's one more thing worse: the people who complain about how annoying the people who complain about the meaningless bump in version numbers are. Boy those guys are real jerks!

    --
    What a fool believes, he sees, no wise man has the power to reason away.
  9. Re:Really? That's important ? by chocapix · · Score: 2

    He wrote on the lkml: "the real reason is just that I can no longer comfortably count as high as 40."

  10. Re:Really? That's important ? by Rosco+P.+Coltrane · · Score: 5, Insightful

    No, 2.6.40 + 0.3.60 = 2.9.100

    I think he meant 1.-6.-40 more advanced.

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
  11. Re:This gives the impression that 2.6.40 is more by chocapix · · Score: 5, Funny

    That's a bold statement.

  12. Re:Really? That's important ? by c0lo · · Score: 2

    Usually a change in major version number means major incompabilities, that's what the "major" means. I.e. Python 3 is incompatible with Python 2. GTK 3 is incompatible with GTK 2. etc. Doing so when it is in fact not incompatible upsets people's expectations but is a pleasant surprise when they find out they don't actually have to adapt everything to it.

    This means: 3.0.x - expect disruptive changes?

    --
    Questions raise, answers kill. Raise questions to stay alive.
  13. Re:This gives the impression that 2.6.40 is more by CRCulver · · Score: 2

    But I guess the marketing mentality somehow, somewhere, has taken over. /looks at Gnome 3.0

    Gnome 3.0 deserved the update of the major version number because the libraries it depends on have been extensively revised (GTK+ went to version 3.0, for example).

  14. Not sure about the difference... by denzacar · · Score: 4, Funny

    But does anyone else get chills when thinking about the 3.1.1 version somewhere down the road?
    You know... as in for workgroups?

    --
    Mit der Dummheit kämpfen Götter selbst vergebens
  15. Re:Sigh. by Rennt · · Score: 2, Funny

    I hear ya bud, but do you know what really grinds my gears?!

    On second thought - lets just drop it... it's jerks from here to infinity.

  16. Odd version numbers by OoberMick · · Score: 3, Insightful

    My understanding is that the jump to 3.0 is simply that they no longer want to have the second digit even means stable and odd means unstable versioning any more. So rather than going to 2.7.0 and having everyone assume it's unstable or skipping 2.7.0 and going straight to 2.8.0 just to maintain an old and unused version system, they have went with 3.0.

  17. Re:Really? That's important ? by kvvbassboy · · Score: 2

    No, Linus mentioned that it is an evolutionary (not revolutionary) release, and that the APIs and ABIs wouldn't change.

  18. Re:This gives the impression that 2.6.40 is more by jareth-0205 · · Score: 4, Insightful

    But I guess the marketing mentality somehow, somewhere, has taken over.

    Hardly. It was already broken, the "2.6" part of the number was completely irrelevant, and whereas it might not bother you, if you're talking about version numbers all day every day, having superfluous data in there will get annoying. So yeah, the "upgrade" is misleading but from now on the version bumps more accurately reflect the scale of change in the kernel.

    Anyway, who markets the kernel? Distros are marketed, nobody cares about the kernel who doesn't already know what's going on.

    This is far more a case of developers wanting a version number system that makes sense to the current kernel development model than anything else.

  19. Time for a change by Anonymous Coward · · Score: 3, Funny

    This is a complete outrage. Not only will it require extensive re-testing but distros will need to change as well.

    I believe it's time for us to fork the GNU/Linux kernel to a more appropriate versioning scheme, while removing all non-libre blobs at the same time. Only then can we depose this dictator Torvalds and his pro-capitalist kernel.

  20. First base! by jabberw0k · · Score: 4, Funny

    Everyone knows minors don't overflow into majors. (And if you thought Naturally was the first baseman, then you don't know Who.)

    1. Re:First base! by capedgirardeau · · Score: 3, Funny

      Oh he's on second.

      --
      Wax on, wax off baby!
  21. Re:When new numbers meant new features by jareth-0205 · · Score: 3, Insightful

    Now the 3.0 Linux branch is just plain about shiny numbering.

    Yup, and is all the better for it. What you don't mention in your list is the fact that the development model changed in 2.6, from a break-> stabilise->break-> stabilise model to one of continuous stable development. The version number system stayed the same, which suggests the same development process of stabilisation with no new features, so this is a newer system that fixes that.

  22. Re:Really? That's important ? by Goaway · · Score: 4, Informative

    He is Finnish, but his first language is Swedish.

    (PS. This is why you should not choose the language for your web site based on a geographical lookup of the IP address.)

  23. Re:Really? That's important ? by RDW · · Score: 4, Funny

    "Can someone please explain what is the difference between 3.0 and 2.6.40 ?"

    Linus: The numbers all go to 3. Look, right across the git repository, 3, 3, 3 and...
    Interviewer: Oh, I see. And most kernels go up to 2.6?
    Linus: Exactly.
    Interviewer: Does that mean it's better? Is it any better?
    Linus: Well, it's one better, isn't it? It's not 2. You see, most blokes, you know, will be running 2.x. You're on 2.6 here, all the way up, all the way up, all the way up, you're on 2.6 on your computer. Where can you go from there? Where?
    Interviewer: I don't know.
    Linus: Nowhere. Exactly. What we do is, if we need that extra push over the cliff, you know what we do?
    Interviewer: Compile it up to 3.
    Linus: 3. Exactly. One better.
    Interviewer: Why don't you just make 2.6 better and make 2.6 be the top number and make that a little better?
    Linus: [pause] These go to 3.

  24. If Linux kernels had microsoft names by shoppa · · Score: 4, Funny

    If linux kernels had microsoft marketing setting the names, we wouldn't have decimal points etc.

    It would be "Linux NT", "Linux 95", "Linux Server 2003", "Linux XP", "Linux Vista", "Linux 7".

    Just think how much more marketable Linux could be and how much more the suits would want to buy it.

    1. Re:If Linux kernels had microsoft names by eqisow · · Score: 2

      That's disingenuous. Windows still has standard version numbers in addition to the marketing names.

    2. Re:If Linux kernels had microsoft names by steelfood · · Score: 4, Funny

      When it hits version 10, they can call it LinuX.

      --
      "If a nation expects to be ignorant and free in a state of civilization, it expects what never was and never will be."
  25. Re:This gives the impression that 2.6.40 is more by Kjella · · Score: 2

    Well, under the current development model "2.6" is essentially static, It's like OS X always remaining OS X rather than move to OS XI, OS XII, OS XIII etc. as there's absolutely no work on a "2.7" branch and probably never will be.

    The 2.6.x changes are far bigger than a 0.0.1 change should be, I mean it's the main development release. Making them 0.1 changes is more than reasonable. The stabilization team will get to move up from 4th to 3rd digit so 3.0.3 rather than 2.6.40.3. Simpler, shorter all around.

    I thought the Linux community wasn't shy of just minor, incremental updates. If it ain't broke don't fix it, don't rock the boat etc. But I guess the marketing mentality somehow, somewhere, has taken over. /looks at Gnome 3.0

    Also are you arguing that Gnome 3 isn't a radical enough departure breaking enough eggs to warrant it's version number? Sounds to me like most people complain it's too different from Gnome 2.x. In this case, you seem to argue Linux 3.0 will be too similar to Linux 2.x. Is there a way to win here?

    --
    Live today, because you never know what tomorrow brings
  26. I for one welcome the bump in ver # by McNihil · · Score: 3, Informative

    IMHO it should have been done back with 2.6.19 or no later than 2.6.25. Better late than never though.

  27. Re:When new numbers meant new features by ratboy666 · · Score: 5, Informative

    Oh really...

    What about removal of the big kernel lock?
    What about plug-in resource schedulers?
    What about fast ip locking?
    What about kernel video mode switching?
    What about systemtap?
    What about cgroups?
    And much more...

    When taken in combination, the growth of the Linux kernel since 2003 definitely warrants a major jump.

    The issue is whether it should be 2.8 or 3.0. I would side with 3.0.

    Because Linux is now ready for serious MP, both on a local and a cluster level. And these features are not "backwards portable".

    --
    Just another "Cubible(sic) Joe" 2 17 3061
  28. The reasoning behind this decision. by I'm+Not+There+(1956) · · Score: 2

    "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 longe rcomfortably count as high as 40," said Linus.

    --
    "If fifty million people say a foolish thing, it's still a foolish thing."
  29. Re:Really? That's important ? by maxwell+demon · · Score: 2

    Well, since there's no predefined definition of version numbers, you have considerable freedom in defining them. For example:

    Version numbers a.b.c and d.e.f are added by forming the ordinals (w^2 a + w b + c) and (w^2 d + w e + f) where w is the smallest infinite ordinal, then adding those (note that ordinal addition is not commutative!), giving an expression of the form (w^2 f + w g + h) which then is concerted back to the version number f.g.h in the obvious way

    For example, we would get 2.6.40 + 0.0.1 = 2.6.41, 2.6.40 + 0.1.0 = 2.7.0 and 2.6.40 + 1.0.0 = 3.0.0 -- which actually makes some sense. Also note that version comparison reduced to ordinal comparison would give the correct ordering.

    Note that the above definition assumes that all version number components are nonnegative (there is no such thing as a negative ordinal). However, the major version number could be allowed to be an arbitrary ordinal number :-)

    --
    The Tao of math: The numbers you can count are not the real numbers.
  30. Re:Really? That's important ? by Bing+Tsher+E · · Score: 5, Funny

    Actually, he was calculating it in his head because OpenOffice Calc was taking too long to load.

  31. Re:Really? That's important ? by Lord+Byron+II · · Score: 2

    That's because you didn't get the reference you insensitive clod!

  32. Re:Really? That's important ? by Dog-Cow · · Score: 2

    When Linus states that the ABI won't change, he means the user-space ABI (e.g. that (g)libc uses).

  33. Version numbers in the real world by dargaud · · Score: 5, Funny
    In the real (read 'commercial app') world, I've noticed that version numbers go something like this (not all version numbers shown):
    • 0.2 // It's not even working on our developper's PC
    • 0.4 // We can't sell that yet
    • 0.8 // We are trying to sell it
    • 1.0 // We are selling it
    • 1.1 // Now it works, we swear
    • 1.4 // OK, now it's stable
    • 2.0 // We know you wouldn't shell out for version 1.5
    • 3.0 // Just to keep you updating
    • 9 // Honestly we lost track of the minor number too
    • 13 // No real difference with version 9
    • 2005 // Well, our customers were losing track of the major version number too, so that'll make it easier for them
    • 2008 // Hey fatty, time to upgrade, you previous one is 4 years old now, can't you count ?
    • 2010 // No change, but, hey, time passes fast
    • 1.0 // We had to rename it
    --
    Non-Linux Penguins ?
  34. About damn time by spectro · · Score: 3, Insightful

    I could never understand what is with all these digits in version numbers. If it was up to me the kernel would be in version 8.x or 9.x already.

    What's with open source and all these version numbers starting with 0.x?. Why are they so afraid of just a freaking number? I've been using mythtv for about 10 years and they just released version 0.24.1 *facepalm*

    Linus just realized that version numbers are about marketing more than anything else. Microsoft has been doing this for decades. I should buy me some redhat stock.

    --
    HTML is obsolete. It's time for a new, simpler and richer markup language.
  35. Re:Really? That's important ? by Hal_Porter · · Score: 2

    Linux 3.1 was a certain ring to it.

    --
    echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
  36. Re:Really? That's important ? by aBaldrich · · Score: 3, Insightful

    I prefer to read in well-written English, rather than see them bastardize my mother tongue.

    --
    In soviet russia the government regulates the companies.
  37. Re:Really? That's important ? by siride · · Score: 2

    No, it's called "I'm an idiot", produced, written and directed by siride.

  38. Re:Really? That's important ? by DarwinSurvivor · · Score: 2

    Right, the ever-feared "divide by 2" error...

  39. Re:Really? That's important ? by geminidomino · · Score: 2

    First project (at least that I was using) I remember pulling it was Slackware jumping to 7. It seemed kind of odd to me at the time, though even moreso now.