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.

378 comments

  1. Really? That's important ? by zero.kalvin · · Score: 1

    I've always wondered what the heck with version numbers... Can someone please explain what is the difference between 3.0 and 2.6.40 ?

    1. 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
    2. Re:Really? That's important ? by elsurexiste · · Score: 1

      IIRC, Linus wanted some sort of distributed operating system for 3.0, but I read it too long ago, not sure about it...

      --
      I rarely respond to comments. Also, don't ask for clarifications: a brain and Google are faster, believe me!
    3. Re:Really? That's important ? by Anonymous Coward · · Score: 1

      You mean 0.3.60 more.

    4. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      math fail

    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. Re:Really? That's important ? by master5o1 · · Score: 1

      Yes.

      --
      signature is pants
    7. Re:Really? That's important ? by freedumb2000 · · Score: 1

      Obviously, Linus wants to follow Mozilla and speed up the release cycle by only releasing full version number releases from now on. Expect the 4.0.0 kernel sometime in the fall with no point releases in between!

    8. Re:Really? That's important ? by Anonymous Coward · · Score: 1

      I guess 3.0.0 is but a symlink to 2.6.40.

    9. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      It's just time to make a change...

      There's also the timing issue - since we no longer do version numbers
      based on features, but based on time, just saying "we're about to
      start the third decade" works as well as any other excuse.

    10. 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."

    11. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      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.

    12. 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
    13. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      It's not brought out much but the Swedish language actually has not concept of numbers above 47. This could somewhat explain the problems Linus is is having.

    14. 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.
    15. Re:Really? That's important ? by Sparx139 · · Score: 0

      My kingdom for mod points!

      --
      Our culture doesn't get smarter, it just finds new ways of being retarded.
    16. Re:Really? That's important ? by Anonymous Coward · · Score: 0

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

      I do not care about the version but his reasoning does not make any sense. He could as well have changed it to 2.8.0.

    17. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      Just call it cloud linux and that's good enough. No need for anything new as long as you get 'cloud' in the name somewhere.

    18. Re:Really? That's important ? by Anonymous Coward · · Score: 0

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

      It's twice as expensive, but well worth it.

    19. Re:Really? That's important ? by Rolgar · · Score: 1

      Kernel version 2.6.0 originally released in December 2003. The second digit was incremented from 4 to 6 (odd numbers are (were?) reserved for development work) due to significant changes in coding. Since then, several stable releases have come out every year, incrementing the third series, indicating that no significant changes, to the overall kernel design, but most releases have had some important features added.

      Recently, Linus expressed an interest in changing the numbering from 2.6 to 3.0. Unlike the significant amount of change between 2.4 and 2.6, Linus decided to make this change based not upon a significant change, but personal preference. Having run the first two numbers the same for over 7 years, they have had relatively little meaning for the last several years anyway, and they still won't really. It might be a minor inconvenience for those who run distributions to have to accommodate the change, but for most folks, it doesn't mean much. I wouldn't mind a numbering where like 11.2 (year and release number within the year), or just going with 40 and dropping the 2.6. I would then know that we are in the 40th release since the 2003 rewrite, and it would be shorter to say than the complete numbering system currently being used. I think that Linus is keeping the format the same going forward due to tradition (and maybe it means not having to reprogram the coding repository, or some related code that depends on kernel version number), and I suppose that's fine since it still gives you information if you understand the meanings the number system has.

    20. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      It might do, if ( 1 ) it were true and ( 2 ) he was Swedish...

    21. 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.

    22. Re:Really? That's important ? by JustOK · · Score: 1, Flamebait

      he was using ms excel to calculate the results.

      --
      rewriting history since 2109
    23. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      His native language is Swedish.

    24. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      heh Well he is a Swedish-Finn.

    25. 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.)

    26. Re:Really? That's important ? by Goaway · · Score: 1

      You... took that seriously.

    27. 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.

    28. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      Don't you mean 0.3.60 advanced? Otherwise it would be version 3.1.0 :)

    29. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      While Swedish may or may not have a concept of number related humour , Linus is a Swedish speaking Finn, a rather large minority group. Finnish being his second language.

    30. Re:Really? That's important ? by TheRaven64 · · Score: 1

      This is Linux, so let's say the APIs and ABIs won't change intentionally...

      --
      I am TheRaven on Soylent News
    31. Re:Really? That's important ? by flex941 · · Score: 1
    32. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      Exactly. It should always be english.

    33. Re:Really? That's important ? by rjforster · · Score: 1

      In the small print, one of the instructions for compiling it up to 3 is "make lickmylovepump"

    34. 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.
    35. Re:Really? That's important ? by Plainswind · · Score: 1

      Except that it's Linus Torvalds at the helm, who's publicly said that he's not above intentionally changing the ABI to try to force vendors to open their drivers.

    36. Re:Really? That's important ? by MightyMartian · · Score: 0

      1. There's an app for that.
      2. In Soviet Russia math fails you!
      3. Netcraft confirms it, Linux is undead.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    37. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      The developers just couldn't find an existing proprietary OS to imitate.

    38. 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.

    39. Re:Really? That's important ? by quenda · · Score: 1

      These made up conversations are never funny.

      Sorry ... what is the reference there?

    40. Re:Really? That's important ? by Anonymous Coward · · Score: 0

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

      nope, they are equivalent:
      2.6.40 -> 2+6+4+0 = 12 -> 1+2 = 3
      3.0 -> 3+0 = 3

    41. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      Excellent Spinal Tap reference! :-D

    42. Re:Really? That's important ? by TheBilgeRat · · Score: 1

      Spinal Tap much?

    43. Re:Really? That's important ? by siride · · Score: 1

      This looks like a conversation the poster made up to be funny. If it's real, than disregard my remark.

    44. Re:Really? That's important ? by quenda · · Score: 1

      Isn't it a bit soon? We've been waiting 23 years for version 12 of X windows.

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

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

    46. Re:Really? That's important ? by TheDarkMaster · · Score: 1

      LOL!

      --
      Religion: The greatest weapon of mass destruction of all time
    47. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      Clearly 3.0.0 is 0.4.60 more advanced than 2.6.40.

      I think it is 0.3.60 more advanced...

    48. Re:Really? That's important ? by countertrolling · · Score: 1

      And who are you? Will Hunting?

      --
      For justice, we must go to Don Corleone
    49. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      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?

      Only on Intel CPUs.

    50. 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).

    51. Re:Really? That's important ? by A12m0v · · Score: 1

      It is called Chromifacation. Maybe Google didn't start it, but the popularized it with version numbers that mean nothing. Even Mozilla is now guilty of it with the release of Firefox 5 Beta.

      --
      GENERATION 25: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
    52. Re:Really? That's important ? by FoolishOwl · · Score: 1

      Now aren't you glad he turned down the job at the NSA?

    53. Re:Really? That's important ? by FoolishOwl · · Score: 1

      With Linus Torvalds, sometimes it's hard to be sure whether he's joking.

    54. Re:Really? That's important ? by FoolishOwl · · Score: 1

      Curiously, I can easily calculate the price of 3.0 based upon the price of 2.6.40, but when I try to calculate the price of 2.6.40 based upon the price of 3.0, gcalc gives me an error message.

      I hope they fix that bug by 3.0.2.

    55. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      Clearly 3.0.0 is 0.4.60 more advanced than 2.6.40.

      2640 + 0460 = 3100

    56. 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;
    57. Re:Really? That's important ? by Hal_Porter · · Score: 1

      It's not impossible he got the reference and still didn't find it funny

      --
      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;
    58. Re:Really? That's important ? by allo · · Score: 0

      well, lets use a base-40 system. So it counts till 3.39 and then overflows to 4.0. The Big Question is: Will there be a 40.0 kernel? Or will it be 1.0.0?

    59. Re:Really? That's important ? by the_one(2) · · Score: 1

      As a Swede, I wholeheartedly agree=)

    60. Re:Really? That's important ? by hitmark · · Score: 1

      Another thing is that 2.5 development went on forever, to the point that Red Hat had backported a solid subset of the major new features.

      It seems to me that any kind of numbering scheme runs into issues sooner or later. Hell, even simply incrementing a single number of each release runs into issues once people wants to maintain a stable branch that forgoes feature creep. Now all of a sudden you got two numbers, the number of the branch point, and the number incrementing for each release of updates to said branch.

      Funny enough, it would appear that the system i describe above is where things are headed with Linux. Now they can increment to x.1 while the stable branches increment x.x.1.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    61. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      I think he ought to use colors instead of numbers. For security-fix releases, he should use colors that are tasteful, not festive, but bright enough to create a sense of urgency.

    62. Re:Really? That's important ? by houghi · · Score: 1

      And in an install script, differentiate the language from the keyboard layout and from the country.
      e.g. : In Belgium the standard keyboard layout is BE_FR, but sometimes you still see FR_FR. The language could be NL, FR or DE and linked to the originating countries; those have different keyboard layouts.

      --
      Don't fight for your country, if your country does not fight for you.
    63. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      No, just the early Pentiums.

    64. Re:Really? That's important ? by hedwards · · Score: 1

      Clearly this is the first evidence that Linux is entering that Google/Mozilla dick measuring by proxy of version number contest.

    65. 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.
    66. Re:Really? That's important ? by quenda · · Score: 1

      This looks like a conversation the poster made up to be funny.

      A paraphrasing of a classic movie scene.
      See http://www.google.com/search?q=spinal+tap+eleven

    67. Re:Really? That's important ? by siride · · Score: 2

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

    68. Re:Really? That's important ? by da5idnetlimit.com · · Score: 1

      You know reverse polish notation ?
      This is the inverse finnish version 8p

      --
      It takes 40+ muscles to frown, but only four to extend your arm and bitchslap the motherfucker
    69. Re:Really? That's important ? by Doug+Neal · · Score: 1

      This wasn't one of those times...

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

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

    71. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      er.... 0.3.60 I would think...

    72. Re:Really? That's important ? by Runaway1956 · · Score: 1

      Could we just Finnish this round of inanities now?

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    73. Re:Really? That's important ? by Unequivocal · · Score: 1

      I thought I was the only one!

    74. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      Clearly 3.0.0 is 0.4.60 more advanced than 2.6.40.

      You mean 0.3.60 :-(.

    75. 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.

    76. Re:Really? That's important ? by JWSmythe · · Score: 1

          You know, I understand the Linux kernel version numbers, and even that gave me a headache. I guess they let the monkeys out of the cages at the NSA once in a while, just to taunt the rest of us. :)

      --
      Serious? Seriousness is well above my pay grade.
    77. Re:Really? That's important ? by JWSmythe · · Score: 1

          They could adopt the the DHS threat level color method. Every release would be orange, with the exception of the occasional red update, which would be randomly selected by background noise.

      --
      Serious? Seriousness is well above my pay grade.
    78. Re:Really? That's important ? by Savantissimo · · Score: 1

      w^2(t) f ?!

      --
      "Is life so dear, or peace so sweet, as to be purchased at the price of chains and slavery?" - Patrick Henry
    79. Re:Really? That's important ? by JAlexoi · · Score: 1

      Nooo.... It's 0.4.59999999999999999+ times better.

    80. Re:Really? That's important ? by Savantissimo · · Score: 1

      Rumors to the contrary aside, Finnish only causes mild brain damage, no worse than APL, aquavit or Apple.

      --
      "Is life so dear, or peace so sweet, as to be purchased at the price of chains and slavery?" - Patrick Henry
    81. Re:Really? That's important ? by MobileTatsu-NJG · · Score: 1

      That's a bad idea. Slashdotters are allergic to the word 'cloud'. They'd revolt!

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    82. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      Wrong. It's actually 0.3.60 more advanced.

    83. Re:Really? That's important ? by kiddygrinder · · Score: 1

      version numbers have never meant anything.

      --
      This is a joke. I am joking. Joke joke joke.
    84. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      On a Pentium?

    85. Re:Really? That's important ? by deniable · · Score: 1

      My native language is English and I agree.

    86. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      Spinal Tap reference! You Rock!

    87. Re:Really? That's important ? by bennettp · · Score: 1

      In Soviet Russia, mother tongue bastardize you!

    88. Re:Really? That's important ? by bennettp · · Score: 1

      In Soviet Russia, mother tongue bastardizes you!

    89. Re:Really? That's important ? by maxwell+demon · · Score: 1
      --
      The Tao of math: The numbers you can count are not the real numbers.
    90. Re:Really? That's important ? by kasperd · · Score: 1

      The last two components in the version number are 8 bit integers. So if you actually compute the difference, the result would be 0.249.216.

      --

      Do you care about the security of your wireless mouse?
    91. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      Microsoft Word for Windows jumped from 2.0 to 6.0 back in the Windows 3.1 days.

    92. Re:Really? That's important ? by petermgreen · · Score: 1

      The second digit was incremented from 4 to 6

      Rather it went from 2.4.x (stable) to 2.5.x (development) to 2.6.x (stable). Meanwhile the 2.4.x releases continued (and went on for a long time even after the release of 2.6.0.

      After the release of 2.6.0 linus conidered the code of linux to be stable enough to no longer need a seperate development branch for radical changes preffering to bring in individual changes direct to the stable releases as and when they were ready. The result is 2.6.40 is very different from 2.6.0 but the changes were evoloutionary with all the intermediate steps being "stable" releases.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    93. Re:Really? That's important ? by JAlexoi · · Score: 1

      No... He couldn't find the right way to do it in Office 2007.

    94. Re:Really? That's important ? by disi · · Score: 1

      Only 3.1 versions to go and we catch up with the Windows kernel 6.1 ^^

    95. Re:Really? That's important ? by andymadigan · · Score: 1

      I thought 3.0 was the version that would be written in a special message-passing version of Visual Basic... leading to his commitment to an asylum.

      --
      The right to protest the State is more sacred than the State.
    96. Re:Really? That's important ? by Anonymous Coward · · Score: 0

      Punds/shillings/pence is back. Long live the empire!

  2. 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:The problem with incremental version numbers by TheCount22 · · Score: 1

      You found some 2.6 compliant hardware?! Amazing! You mean like an HID mouse? You're probably right 2.6.40 probably doesn't HID devices anymore.

    3. Re:The problem with incremental version numbers by Anonymous Coward · · Score: 0

      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

      Maybe the problem is that people perceive there is a problem with the incremental version numbers.

    4. Re:The problem with incremental version numbers by Nimey · · Score: 1

      Well, there /has/, but not since the late '90s. 2.0 introduced the ELF executable format, which replaced the old a.out format that the 0.x and 1.x series used.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    5. Re:The problem with incremental version numbers by MikeBabcock · · Score: 1

      Major versions aren't about features in Linux, or at least they weren't. They were about compatibility. Going from 2.4 to 2.6 meant you were going to break things. Going from 2.6.1 to 2.6.2 shouldn't break things.

      Going from 2.6 to 3.0 means possible major ABI changes, and if that allows for a major improvement in internals that has been building up, I'm all for it.

      --
      - Michael T. Babcock (Yes, I blog)
    6. Re:The problem with incremental version numbers by Anonymous Coward · · Score: 0

      oh come on ,since when did Linus worry about compatibility?
      That's the job of the distros.
      If he cared held be doing branches and maintenance releases like FreeBSD does.

    7. Re:The problem with incremental version numbers by Anonymous Coward · · Score: 0

      That's a good thing.
      Stability is desirable.

  3. Wow by ivucica · · Score: 1

    Duke Nukem Forever, Linux 3.0... what is this world coming to?

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

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

    2. Re:Wow by tepples · · Score: 1

      I'll believe it once 2023 comes and goes with no extension of the term of U.S. copyright in works made for hire.

    3. Re:Wow by rsimpson · · Score: 1

      Don't worry, you only need to start panicking when GNU Hurd is released.

    4. Re:Wow by Anonymous Coward · · Score: 0

      Dogs and cats living together??

    5. Re:Wow by FunPika · · Score: 1

      Don't worry, Episode 3 or Half Life 3 have yet to be given a release date, we are not COMPLETELY fucked yet.

      --
      After years of not using a signature, I am going to make one to say the following: Fuck Beta
    6. Re:Wow by camperdave · · Score: 1

      They've got to get all the upgrades in before the world ends in 2012. When we had that surprise drill earlier this month, the only people who were ready were IANA, having allocated the last IPv4 addresses at the beginning of the year.

      --
      When our name is on the back of your car, we're behind you all the way!
    7. Re:Wow by pinkushun · · Score: 1

      Year of the rapture.. oh wait, never mind.

    8. Re:Wow by SEE · · Score: 1

      2018 is the important year, 20 after 1998 which was 20 after 1978.

    9. Re:Wow by Bengie · · Score: 0

      Linux needs user mode video drivers so if your video card crashes, it doesn't crash your windowing system or your computer.

      The ability to use your IGP when processing is low and transparently switching to your dedicated GPU once it gets high enough would be nice to.

      I know I won't be using Linux for my desktop until I get some multi-threaded 3D rendering support and drivers that don't crash the computer. I want to make use of my 3rd gen $300 graphics card. I get a new video card every 2-3 years, I don't want to wait 5 years to use it. It's not like I get the newest tech either, I wait for the 2nd-3rd gen of a tech so it's stabilized.

    10. Re:Wow by Anonymous Coward · · Score: 0

      Perl 6

    11. Re:Wow by Hal_Porter · · Score: 1

      You don't necessarily need user mode drivers to recover from crashes. I've seen XP recover from a hang in driver - actually due to a badly seated connector in a laptop - by switching to the stock VGA driver and popping up a dialog box.

      http://technet.microsoft.com/en-us/library/dd349392(v=ws.10).aspx

      Very impressive actually - XP must have a watchdog timer and the ability to switch back to the non accelerated Microsoft VGA driver when the accelerated and vendor provided driver gets stuck waiting for the hardware. What's interesting is that the resolution and bit depth of the display changes. So the GDI must be able to recover from this on the fly.

      On Windiows - auto switching from IGP to defdicated graphics is done by at least the NVidia "Optimus" drivers.

      http://news.cnet.com/8301-17938_105-10449383-1.html

      --
      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;
    12. Re:Wow by jones_supa · · Score: 1

      The ability to use your IGP when processing is low and transparently switching to your dedicated GPU once it gets high enough would be nice to.

      By the way I did a bit googling and there now seems to be some support for Nvidia Optimus technology under Linux called Bumblebee. Apparently it can even run tasks simultaneously on the two GPUs. Quite interesting...

    13. Re:Wow by Bengie · · Score: 1

      A hanging driver or non-responsive hardware is different than a crashing driver. If code crashes while in kernel mode, bad things happen.

      I'm happy with the responses I got. I learned some new stuff :-) I love learning

      P.S. Can't wait for Linux to catch up with games. I'll be there, front and center.

    14. Re:Wow by Anonymous Coward · · Score: 0

      mass hysteria!

    15. Re:Wow by Hal_Porter · · Score: 1

      A hanging driver or non-responsive hardware is different than a crashing driver. If code crashes while in kernel mode, bad things happen.

      That's true. Actually Windows has a strange history with display drivers. Initially NT based OSs (NT 3.1 and NT 3.5) were supposed to run almost all of the display driver in user mode with a small kernel mode component called a video miniport that could access hardware.

      Of course that was too slow in practice so everyone mapped the hardware registers into user mode memory. E.g.

      http://www.osronline.com/ddkx/graphics/vidintro_5d7r.htm

      The display driver has direct access to I/O-mapped and memory-mapped video registers. This access allows a display driver to achieve high performance. For example, the driver might need to access video hardware registers to send line-drawing commands at high throughput.

      Similarly, for graphics cards, such as the S3, many of the innermost loops in the graphics engine code require reads and writes of several video controller ports (for example, text output in graphics mode, bit block transfers, and line drawing). Rather than requiring the display driver to send an IOCTL to the miniport driver for each request, the display driver is permitted to access the video hardware directly.

      But user mode that can access DMA registers can bring down the system.

      NT 4.0 moved everything to kernel mode for performance with the memorably bogus justification that "if you crash the display driver the system is useless anyway". Then again if everyone just mapped both the framebuffer and the hardware registers to user mode memory anyway, the kernel mode part wasn't really doing anything.

      XP was the same but added time outs for threads stuck in the driver. Vista moved most of the code back to user mode with a small KMD.

      The architecture is clever than the NT 3.x video miniport though - see here

      http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/pri103_wh06.ppt

      It all sounds quite sensible the way they describe it - most of the code is in user mode. It packs commands into packets and calls kernel mode code whose sole purpose is to add the packets into a DMA list. Graphics hardware then DMAs the commands and executes them. In the later versions of WDDM the display memory is virtualised. So theoretically you can stop buggy user mode code using the DMA engine to clobber memory it shouldn't be able to access.

      Mind you I'm pretty sure that architectural changes like this are the reason for Vista's reputation for being a resource hog. OTOH Windows 7 seems OK, and it still has much the same architecture.

      --
      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;
    16. Re:Wow by Anonymous Coward · · Score: 0

      Next up: Cold fusion!

    17. Re:Wow by Anonymous Coward · · Score: 0

      Linux needs user mode video drivers so if your video card crashes, it doesn't crash your windowing system or your computer.

      You are aware that Linux has been moving FROM user mode video drivers to a split user / kernel mode model lately? It's called KMS, and puts all the setup code in kernel mode, while keeping the drawing in user mode.

      People used to complain "Linux needs kernel mode video drivers".

    18. Re:Wow by makomk · · Score: 1

      It all sounds quite sensible the way they describe it - most of the code is in user mode. It packs commands into packets and calls kernel mode code whose sole purpose is to add the packets into a DMA list. Graphics hardware then DMAs the commands and executes them.

      Of course, the open source Linux drivers for ATI/AMD graphics have used pretty much the same approach since more or less forever...

    19. Re:Wow by Hal_Porter · · Score: 1

      And how's that working out for them?

      http://www.phoronix.com/scan.php?page=article&item=amd_gardenshed_drm&num=6

      Published on May 27, 2011
      Written by Michael Larabel
      Page 6 of 6

      There's really no change compared to our previous round of open-source Radeon DRM + Gallium3D vs. Catalyst driver testing... Most users interested in playing any sort of semi-intense OpenGL game will certainly be best off with the Catalyst driver for the near future.

      If taking a geometric mean of all the frame-rates for each of the tests, from the OpenBenchmarking.org result file, it clearly shows the Catalyst driver is still many times faster overall.

      If then condensing the results from the four Radeon HD 4000/5000 series graphics cards, the AMD Catalyst 11.4 Linux driver is about 7.76x faster than the latest open-source Radeon Linux driver code as of yesterday..

      Not so good it seems.

      --
      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;
  4. 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.

    3. Re:Version numbers? We can increment them! by Anonymous Coward · · Score: 0

      BSD Big Shite Dump been wanting to get that across for yonks
       

    4. Re:Version numbers? We can increment them! by Dunbal · · Score: 1

      Change 2.8 to "three". 2.8 doesn't rhyme anyway, three would scan better, and there you go. FTFY.

      --
      Seven puppies were harmed during the making of this post.
    5. Re:Version numbers? We can increment them! by Pieroxy · · Score: 1

      Since when does "eternal" rhymes with "glory" ?

    6. Re:Version numbers? We can increment them! by mandelbr0t · · Score: 1

      I'm sure the "commit" pun wasn't intended. :D

      --
      "Please describe the scientific nature of the 'whammy'" - Agent Scully
    7. Re:Version numbers? We can increment them! by Anonymous Coward · · Score: 0

      By the looks of it, BSD is so stable it even fails to take up market share. That's how stable it is. Gaining market share would be a form of instability :)

    8. Re:Version numbers? We can increment them! by Anonymous Coward · · Score: 0

      Linux does suck, but I'll credit it for at least trying to improve in some ways, unlike the BSD's which haven't done anything substantial since the early 1980's.

    9. Re:Version numbers? We can increment them! by Anonymous Coward · · Score: 0

      He should have called it Sleepy Weasel -- that was the code name for the operation in "Hot Shots!".

  5. I know it doesn't really matter but by Rosco+P.+Coltrane · · Score: 1

    Up to now, Linus had resisted this fad of jumping major version number to get everyone excited - you know, like these software that cycle normally through version 1.0, 1.1, 1.2... at the beginning of their life, then suddenly become v2.0, v3, v6 SE, 8 XL, 9 UltraTurbo when all they are is just minor releases, then eventually run out of credible major version number and just plain look stupid...

    Is there a real reason for skipping 2.8 here, or does Linus want to experience the magical three-dot-oh release effect in his lifetime?

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
    1. Re:I know it doesn't really matter but by erroneus · · Score: 1

      I think he succeeded at not getting everyone excited. I haven't been excited by a new kernel version in what seems like a decade. Hardware support under Linux is pretty damned mature. I only wish X.org would catch up with support of hybrid graphics.

    2. Re:I know it doesn't really matter but by jon3k · · Score: 1

      By skip I assume you think the logical progression was 2.2->2.4->2.6->2.8->3.0 but in reality there could have been any number of kernels between 2.6 and 3.0. Assuming that you HAVE to go from 2.8 to 3.0 is not correct. You could easily go 2.8->2.10->2.12, etc. There's no guarantee that there would be justified reason to go from 2.8->3.0, it _could_ have been smaller changes than 2.4->2.6.

    3. Re:I know it doesn't really matter but by hedwards · · Score: 1

      I think he went a bit overboard with that. With Linux it's a bit odd in that the kernel itself isn't what people typically see the version number for at first. They'll probably see the 13.37 Slackware release number of the 11.04 for Ubuntu, and the version of the kernel isn't something which many people will even notice. Personally, I'm not even sure what version Linux Mint 11 is going to be using.

    4. Re:I know it doesn't really matter but by Anonymous Coward · · Score: 0

      ... you know, like these software that cycle normally through version 1.0, 1.1, 1.2... at the beginning of their life, then suddenly become v2.0, v3, v6 SE, 8 XL, 9 UltraTurbo...

      Don't forget version v10 HT (Huge Tits).

    5. Re:I know it doesn't really matter but by MikeBabcock · · Score: 1

      2.8 isn't the increment before 3.0.

      3.0 is a MAJOR version upgrade. The upgrade after 2.8 would logically be 2.10 and then 2.12 (assuming we continue skipping the old odd numbered development kernels). In other words, there's no carry function from 2.8 to 3.0. We could've possibly gone to 2.144.632 before going to 3.0.0 but Linus seems to think its time to break a few things and really make a big jump.

      --
      - Michael T. Babcock (Yes, I blog)
    6. Re:I know it doesn't really matter but by Anonymous Coward · · Score: 0

      It's all opinion. If your 5 year plan is to add 12 features, and you 4 of them in a release, it's probably ok to up the version number.

      There is no 'right' way to do it.

    7. Re:I know it doesn't really matter but by Xtifr · · Score: 1

      Is there a real reason for skipping 2.8 here

      Why do you only mention 2.8? What about 2.7 and 2.9? (For that matter, what about 2.10 and 2.11?) Since odd minor no longer indicates a development branch, 2.7 would have been just as reasonable a choice for the next notable increment as 2.8. Which, BTW, I think may be your answer--by skipping 2.{7,8,9,...}, he carefully avoids any confusion over the meaning of the second digit, and allows all that to be relegated to pre-3.0 history.

    8. Re:I know it doesn't really matter but by Anonymous Coward · · Score: 0

      Excuse me?
      Hardware support mature in linux?
      That's the best joke i've heard all year :D

    9. Re:I know it doesn't really matter but by Anonymous Coward · · Score: 0

      The kernel is 20 years old this year, why not 3.0? Seems as good a time as any, I mean there aren't many active software projects of equivalent age that haven't passed the 3.0 version mark.

  6. Sigh. by Rennt · · Score: 1, Insightful

    He really went and did it, eh? Crap. The only thing more annoying then a meaningless bump in version numbers is all the people going to be complaining about how annoying it is.

    1. 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.
    2. Re:Sigh. by Anonymous Coward · · Score: 1

      You mean like this guy?

    3. 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.

    4. Re:Sigh. by Anonymous Coward · · Score: 0

      My god, bunratty, that post annoyed me.

    5. Re:Sigh. by Anonymous Coward · · Score: 0

      Nah, the jerk stops with you.

    6. Re:Sigh. by Anonymous Coward · · Score: 0

      Yes, but 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!

    7. Re:Sigh. by Bing+Tsher+E · · Score: 1

      it's jerks from here to infinity.

      That's not the meme.

      It's jerks all the way down.

    8. Re:Sigh. by Anonymous Coward · · Score: 0

      You mean like this guy?

      Aaaaaaaaaah ! recursive comment thread !

      Run, run for your life !

    9. Re:Sigh. by Anonymous Coward · · Score: 0

      It's better than the meaningless 2.6 that was tacked on to the past however many years worth of kernels. Perhaps we'll actually start to see the major and minor places getting used again?

    10. Re:Sigh. by grcumb · · Score: 1

      it's jerks from here to infinity.

      That's not the meme.

      It's jerks all the way down.

      QED

      (Also: QED )

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
  7. 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.

    2. Re:Long-term Support for 2.6.3x? by Anonymous Coward · · Score: 0

      Read the announcement: there are no major changes in 3.0. It's just some new drivers and a bunch of bug fixes. The only reason it's being called 3.0 is because it's been 15 years since 2.0 came out and Linus feels like making an executive decision.

  8. His call by Anonymous Coward · · Score: 0

    Certainly 3.0 will be just the same thing as 2.6.40, but easier to remember.
    So 4.0 will be incompatible break with the past, once the time comes.
    Well I expected some sort of cleanup, but realistically these days it's not a smart move because there is too much of world's software depending on some obscure features of the kernel.
    And for now actually nothing serious enough popped up to justify the ABI breakage.
    My support for this.

  9. This gives the impression that 2.6.40 is more by blind+biker · · Score: 0

    This gives the impression that 2.6.40 is more than an incremental update. But 2.6.40 is>/b> an incremental update, so IMHO it should have stayed 2.6.40. Renaming it to 3.0 is just so random.

    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

    --
    "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
    1. Re:This gives the impression that 2.6.40 is more by chocapix · · Score: 5, Funny

      That's a bold statement.

    2. 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).

    3. 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.

    4. 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
    5. Re:This gives the impression that 2.6.40 is more by Anonymous Coward · · Score: 0

      Gnome 3.0 was more like, if it ain't broke, why the fuck not? Let's re-write it and see how much we can fuck this up!

    6. Re:This gives the impression that 2.6.40 is more by Anonymous Coward · · Score: 1

      Do you have any clue how different 2.6.40 is to 2.6.0?
      Do you have any clue how different 2.6.0 was to 2.4 or even 2.0?
      Do you have any clue how to compare those differences?
      Do you have any clue how to close the bold tag?
      Do you have any clue whatsoever?

    7. Re:This gives the impression that 2.6.40 is more by oldhack · · Score: 1

      Well, they've been at it since 2.6(?) started. Why change now? Cuz it turned out to be less than brilliant idea?

      --
      Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
    8. Re:This gives the impression that 2.6.40 is more by hvm2hvm · · Score: 1

      That's more or less the thinking behind KDE 4.0 too. While I like the new kde a lot I still think it was a mistake to release so early and sometimes I long for the snappiness and low resource usage of KDE 3.5.x. And it still has some quirks although most of the applications are great.

      --
      ics
    9. Re:This gives the impression that 2.6.40 is more by jareth-0205 · · Score: 1

      More important things to worry about, maybe?

    10. Re:This gives the impression that 2.6.40 is more by oldhack · · Score: 1

      Because at the start of 2.6 there wasn't anything important to worry about?

      --
      Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
    11. Re:This gives the impression that 2.6.40 is more by Anonymous Coward · · Score: 0

      THIS oh so this...

      Could you take a 2.6.0 and replace it in place with a 2.6.39? Not even close. The middle number should have been bumped LONG ago. They have changed the interface layer what three or four times during 2.6?

      The number is meaningless. They made it so. Version numbers only have meaning if we make it that way. This 'oh they dont have any meaning' is a cop out.

      Then he turns around and bumps the major version. Hope he has some major arch changes in mind or a different dev method and this isnt just a 'thought it was time' sort of thing.

    12. Re:This gives the impression that 2.6.40 is more by volkerdi · · Score: 1

      This gives the impression that 2.6.40 is more than an incremental update. But 2.6.40 is an incremental update, so IMHO it should have stayed 2.6.40. Renaming it to 3.0 is just so random.

      Try comparing the 2.0 kernel to the 3.0.0-rc1 kernel and then tell me again there's no justification for a major version bump.

    13. Re:This gives the impression that 2.6.40 is more by Ixokai · · Score: 1

      It is just a minor, incremental update, the 2 in 2.6 has been incremented to 3; you know, instead of the 39 being incremented to 40.

      Its not like it jumped to 4 or anything, now -- that wouldn't be an incremental update, indeed!

      The 2.6.~inf thing was getting a bit silly, frankly. There's nothing wrong with incremental updates, but at a certain point you if your whole release strategy is about a steady plodding progress forward, you should stop using feature-ish-inspiring version numbers. He didn't, but hey.

      Of course, he didn't go with a time-based number, so 3.x makes no more or less sense then the ever approaching 2.6.inf, but if the numbers don't actually make any sort of sense, what's it matter? Its all arbitrary, and he felt like being 3.x.

    14. Re:This gives the impression that 2.6.40 is more by Anonymous Coward · · Score: 0

      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.

      Good point. Though while I'm in no position to argue with Apple's success... I always thought that was dumb.

      What os are you running?
      OSX.
      What version are they on now?
      Black Panther.
      Erm.. is that like, version 3 or 47 or what?

    15. Re:This gives the impression that 2.6.40 is more by brantondaveperson · · Score: 1

      The 'bold statement' guy was funnier.

    16. Re:This gives the impression that 2.6.40 is more by Pinchiukas · · Score: 1

      So is this.

  10. 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
  11. Annoying by Anonymous Coward · · Score: 0

    Why change the versioning scheme? When you do this, all you do is exchange one set of shortcomings for another with the added benefit of much confusion.

    My experience has been that when autocratic lead developers start doing things like this, they are (getting) bored.

    1. Re:Annoying by TheCount22 · · Score: 0

      I was expecting something amazing for 3.0.0 like hard real-time and a micro-kernel. Never did I expect this crap from Linus.

  12. Everyone knows it takes until at least version 3.x by Barbara,+not+Barbie · · Score: 1

    ... where "x" > 0 ... The "unwritten rules":

    1. It takes at least until version 3 to get (most of) the bugs out.

    2. Any version that ends in point-zero is a disaster - wait until the next point release (DOS 4.0, DOS 6.0, Windows 3.0, KDE 4.0)

    3. People will now start asking if this means that this will finally be the year of linux on the desktop.

    --
    Let's call it what it is, Anti-Social Media.
  13. Architectural changes by Anonymous Coward · · Score: 0

    While this appears to be a semantic change (which somewhat irritates me), I hope they use this opportunity to commit some bigger changes that have been on the cards for a while.

  14. Why not use dates scheme? by DaKritter · · Score: 1

    linux-2011-06
    linux-2011-09
    linux-2011-12
    etc.

    1. Re:Why not use dates scheme? by Anonymous Coward · · Score: 0

      Because it breaks every script that assumes a standard incremental 3-point version number?

      Because it eliminates any possibility of inferring the magnitude of the change from the version number by eliminating the major/minor/sub heirarchy?

      Because what's wrong with counting?

    2. Re:Why not use dates scheme? by mikael_j · · Score: 1

      But it's.. it's... it's... AGILE! (Or something, for some reason those who jump on every new trend and who have been screaming about "agile" development even where it doesn't make any sense have also thrown themselves at replacing version numbers with either dates or funny names for their releases, only thing worse than that is the ever classic "The fix is in CVS/Just grab it from the repo" answer from project maintainers too lazy to make a new release on at least a yearly basis)

      --
      Greylisting is to SMTP as NAT is to IPv4
    3. Re:Why not use dates scheme? by Anonymous Coward · · Score: 0

      Most sane versioning follows the format:

      Major.Minor.Build for example 1.3.1

      Normally, you increment the major number when you've broken backwards compatibility. You increment the minor, when you're replacing/upgrading some subsystem but you're still maintaining compatibility with the Major number. The build is incremented every-time you refactor or bug-fix the code but your changes don't modify the subsystems such that they stay the same. Essentially the rule is, 'If you add public API interfaces then upgrade the Minor. But if you change an already published public API interface such that it is no longer backwards compatible and you keep the name of the API method OR if you deprecate an already published API interface then you must increment the Major.

      So given the above:

      If you have let's say a codebase that is version 2.3.1 and a snapshot of that codebase at 2.3.10 and let's say a third snapshot of the codebase at 2.4.3 then you know the following:

      Let's say you have a customer that is reporting problems using 2.3.1, you can them they can safely upgrade to 2.3.10 without having to re-write thier in-house scripts or 3rd party tools. BUT if they are still having problems at 2.3.10 then you can tell them they can upgrade to 2.4.3 BUT it would require an uninstall and install of the new software and that any scripts they wrote or 3rd party apps that worked with 2.3.x would have to be upgraded as well.

      So you see, version numbers help with knowing what you can safely replace without breaking the overall system (in house scripts, 3rd party tools).

      Using your suggested date system would not help since it does not show the backwards compatibility.

    4. Re:Why not use dates scheme? by Anonymous Coward · · Score: 0

      Because it eliminates any possibility of inferring the magnitude of the change from the version number by eliminating the major/minor/sub heirarchy?

      You can't do this now.

      Because what's wrong with counting?

      "Counting"? Nothing. But tell me, how old is version 2.6.21?

    5. Re:Why not use dates scheme? by TheBig1 · · Score: 1

      For the first issue, why not call it 2011.06.01, 2011.09.16, etc?

      The second issue is valid, if you expect revolutionary changes; however that does not seem to be in the cards for any time soon.

      As for the last issue, what's wrong with counting to 2011?

    6. Re:Why not use dates scheme? by Anonymous Coward · · Score: 0

      So there are a large number of production scripts that depend on the kernel version number? Is it because the scripts are dependant on the kernel version or just lazy programming?

      If it's the later, I expect more from Linux progammers than that. Sheesh, put it in a variable, or something.

    7. Re:Why not use dates scheme? by Drinking+Bleach · · Score: 1

      There's a release about every three months, which gives four releases per year. I would say about 4-5 years old. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=de46c33745f5e2ad594c72f2cf5f490861b16ce1 Oh hey, it's four years old after all.

  15. Broken version checks by grahammm · · Score: 1

    I wonder how many broken build & configure scripts and runtime version checks will fail because they do not check the major version number.

    1. Re:Broken version checks by cbiltcliffe · · Score: 1

      Well, that's what the developers get for shitty coding practices, and that's what the users get for relying on software written by (an) idiot(s).

      --
      "City hall" in German is "Rathaus" Kinda explains a few things......
    2. Re:Broken version checks by Anonymous Coward · · Score: 0

      and that's what the users get for relying on software written by (an) idiot(s).

      you mean that's what you all get for using Linux?

  16. But does it run Linux? by Anonymous Coward · · Score: 0

    Oh, right... Sorry.

  17. When new numbers meant new features by La+Gris · · Score: 1, Informative

    When Linux 2.0 release june, 9 1996 was the first stable complete workable versatile version.
    As of January, 25 1999 Linux 2.2, many new distro was available to average user.
    January, 4 2001 Linux 2.4 introduced many device changes. There are still so much embeded devices running the 2.4 kernel.
    Decembre, 17 2003 Linux 2.6 stabilized and enhanced changes from 2.4, introduced the fully able IPv6 stack.

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

    --
    Léa Gris
    1. Re:When new numbers meant new features by The+One+KEA · · Score: 1

      If you read Linus' thoughts on the subject of numbering, he has stated numerous times that the Linux development process has moved so far beyond "new version = new features" that forcing it back into that paradigm for Linux 3.0 is broken. He believes instead that "new version = some time has passed + some new feature may be included". The fact that Linux 3.0 will be finalized and released very close to the 20th anniversary of the first Linux kernel is just a bonus.

      --
      SCREW THE ADS! http://adblock.mozdev.org/ Proud user of teh Fox of Fire - Registered Linux User #289618
    2. 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.

    3. Re:When new numbers meant new features by bregmata · · Score: 1

      When Linux 2.0 release june, 9 1996 was the first stable complete workable versatile version.
      As of January, 25 1999 Linux 2.2, many new distro was available to average user.
      January, 4 2001 Linux 2.4 introduced many device changes. There are still so much embeded devices running the 2.4 kernel.
      Decembre, 17 2003 Linux 2.6 stabilized and enhanced changes from 2.4, introduced the fully able IPv6 stack.

      May 2011, Linux 3.0 is delivered to celebrate the year of the Linux Desktop.

    4. 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
    5. Re:When new numbers meant new features by Anonymous Coward · · Score: 0

      The fact that Linux 3.0 will be finalized and released very close to the 20th anniversary of the first Linux kernel is just a bonus.

      From TFA, quoting Linus:
      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.

      So yeah, you're right, it is a serendipitous occasion.
      Luckily Linux isn't about to turn 40, who knows what numbering scheme Linus would've come up with then.

    6. Re:When new numbers meant new features by tepples · · Score: 1

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

      Some other people who have posted comments to the topic appear to think that the big change warranting a shiny number is the loss of the Big Kernel Lock in the 2.6 series, which ordinarily would have been done in a 2.7 series before Linus decided not to use a 2.7.

    7. Re:When new numbers meant new features by Psicopatico · · Score: 1

      This is just the first step of a more broad action plan.
      Soon also the version number of the distribution license will be bumped.

      --
      Mastering the English language is fucking easy: all you have to do is to put an f* word in every fucking sentence.
    8. Re:When new numbers meant new features by Bing+Tsher+E · · Score: 1

      When Linux 2.0 release june, 9 1996 was the first stable complete workable versatile version.

      Not hardly. 1.2.13 was really good, and 1.2.17 was even better and a lot of us stuck with it for a long, long time.

    9. Re:When new numbers meant new features by Anonymous Coward · · Score: 0

      Decembre, 17...

      That's right near the centre of the month, give or take a metre or so.. It also happened to be my first opening at the theatre.. Oh.. wait.. You meant diciembre? ay! perdon!

    10. Re:When new numbers meant new features by allo · · Score: 0

      he wanted to change from 2.6.X to a Y.X scheme. Now he NEEDED to increase 2, or should he have continued 2.6.39, 2.7, 2.8, 2.9, ...? This would be confusing, using 3.X is okay.

    11. Re:When new numbers meant new features by timbo234 · · Score: 1

      June 2011 Linux Kernel 3.0 released to continue the recent development work that has enabled Linux to become seriously popular and widespread in mobile devices and servers, while vastly improved driver support has made it's use on laptops and desktops viable for many.

      Where's the problem with that milestone?

      --
      Pre-canned Evolution Links for all those Slashdot holy wars.
    12. Re:When new numbers meant new features by MikeBabcock · · Score: 1

      Indeed, I used a number of pre-2.4 kernels that were very good. I have at least a couple machines still running 2.0.36 in fact, just for fun.

      --
      - Michael T. Babcock (Yes, I blog)
    13. Re:When new numbers meant new features by Provocateur · · Score: 1

      For the rest of us that barely know, MP above does not mean "multiplayer".

      Though I would kill them 'Flesh-Eating Bats with Fangs' with my trusty ol' boomstick!

      --
      WARNING: Smartphones have side effects--most of them undocumented.
    14. Re:When new numbers meant new features by Anonymous Coward · · Score: 0

      More like continuous broken development. 2.6 was like 2.5, there is no stable linux any more.

    15. Re:When new numbers meant new features by Anonymous Coward · · Score: 0

      Because Linux is now ready for serious MP, both on a local and a cluster level.

      Maybe the Linux development should slow down a bit. Sure it's fun to see when Windows is playing catch-up, but I start feeling sorry for them. Maybe add sleep(1) here and there just to even things out?

  18. Chanes like... by leuk_he · · Score: 1

    Arm cleanup. (who oh who)
    Big kernel lock. (recently declared complete)
    Really really fast. (top of wish list...)

    1. Re:Chanes like... by GameboyRMH · · Score: 0

      Moving the GPLv3 would be a smart move...GPLv2 has been broken for years, when did the first tivoized device come out? Security exploits get fixed fast, what about this big licensing exploit?

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    2. Re:Chanes like... by jimicus · · Score: 1

      Not going to happen.

      IIRC Torvalds has said that he's not too keen on GPLv3 - and even if he was, he doesn't ask for copyright assignment for patches. Which means you'd need to get everyone whose code is in the kernel to agree to a license change - and re-write any bits where the copyright holder either refuses or cannot be contacted.

      In short, an awful lot of work for little perceived benefit.

    3. Re:Chanes like... by tomhudson · · Score: 1

      Tivoization isn't that big a deal - if you don't like it, don't buy the hardware

      Do you drink GPLv3 soft drinks? Do you eat GPLv3 food at your local restaurant? No. They're products, not software. Tivo is hardware. You're free to download the tivo software and implement your own hardware if you want, completely free of drm, just like you're free to cook your own meals using any publicly available recipe.

      The worst, of course, is the AGPL. Do you really want some schmuck asking you for the old version of your web site's code from when they visited it 2 years ago?

    4. Re:Chanes like... by Bing+Tsher+E · · Score: 1

      GPLv3 trolls are rarely successful when you tack them on as a comment reply this far down in a thread. Next time stick it up as a reply to one of the first few comments.

    5. Re:Chanes like... by GameboyRMH · · Score: 0

      No need, I wasn't trolling.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    6. Re:Chanes like... by WuphonsReach · · Score: 1

      The worst, of course, is the AGPL. Do you really want some schmuck asking you for the old version of your web site's code from when they visited it 2 years ago?

      Why would those files not be sitting in a version control system anyway? In which case it's a minor annoyance rather then "we don't have that".

      --
      Wolde you bothe eate your cake, and have your cake?
    7. Re:Chanes like... by tomhudson · · Score: 1
      Maybe the reason it's old code that's no longer used is because it's like dirty underwear, and you don't want people seeing it?

      Maybe that old code has defaults that you have since learned are insane?

      Maybe that old code had back doors in it for testing purposes?

      Only a fool would use the AGPL when it would require you to distribute old code.

  19. 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
    1. Re:Not sure about the difference... by Gordonjcp · · Score: 1

      I've still got a real, genuine, bought-and-paid-for copy of Windows 3.11 somewhere. It didn't suck, much. I wish XP was as quick and compact.

    2. Re:Not sure about the difference... by Anonymous Coward · · Score: 0

      Are we doing development branches in the 3.x.x series again?

    3. Re:Not sure about the difference... by i.r.id10t · · Score: 1

      Me too. When I got my first P2 box many moons ago (late '98?) I put DOS 6.22 and Win 3.11 on it , and it was *blazing* fast.

      --
      Don't blame me, I voted for Kodos
    4. Re:Not sure about the difference... by TheRaven64 · · Score: 1

      Even on a Pentium it was fast. My first new PC was a 133MHz pentium, a huge upgrade from my 16MHz 386. I use Windows NT4, but I also installed a DOS partition for games. I tried installing Windows 3.11 on it, to see what it was like. It launched instantly, and everything was amazingly fast (for someone use to the 386, where waiting for things was just normal). The biggest problem was that Windows 3 was really designed for screens that did 640x480. Running it in 1024x768 meant that you had a lot of empty screen for most things. NT4 was also fast on that machine, but installing IE5 with the shell extension stuff made it much slower.

      --
      I am TheRaven on Soylent News
    5. Re:Not sure about the difference... by pak9rabid · · Score: 1

      3.1.1 would only be a developmental version (ie, not a stable release version)

      The Linux kernel uses an even-odd system version numbering system, such that any odd-numbered minor version number is a development (beta) version.

    6. Re:Not sure about the difference... by siride · · Score: 1

      It hasn't used that system for a while, as even the Wikipedia article you linked to says.

    7. Re:Not sure about the difference... by infolation · · Score: 1

      It's still got to be better than Linux ME

    8. Re:Not sure about the difference... by pandrijeczko · · Score: 1

      You do realise that for any a.b.c Linux kernel, if b is an odd number then that means a development kernel, which is likely to not work that well and be very unstable.

      So comparing a Linux 3.1.1 kernel to Windows 3.1.1 is...

      Oh wait.

      --
      Gentoo Linux - another day, another USE flag.
    9. Re:Not sure about the difference... by pandrijeczko · · Score: 1

      That I can handle.

      "Steve Jobs today announced the Apple release of Linux kernel 3.1.1" definitely *WOULD* drive me over the edge!

      -25 SAN with no sanity roll.

      --
      Gentoo Linux - another day, another USE flag.
    10. Re:Not sure about the difference... by pandrijeczko · · Score: 1

      "Applux" anyone?

      [SHUDDER]

      --
      Gentoo Linux - another day, another USE flag.
    11. Re:Not sure about the difference... by Anonymous Coward · · Score: 0

      You do realize you're a retard? Linus dropped the "odd minor release means development version" after 2.6.0 was released.

    12. Re:Not sure about the difference... by timbo234 · · Score: 1

      No, the 'odd-number means a development release' scheme was dropped many years ago. All the 2.6 kernels from 2.6.0 onwards are considered 'stable' releases, as will all the 3.X ones.

      --
      Pre-canned Evolution Links for all those Slashdot holy wars.
    13. Re:Not sure about the difference... by Arancaytar · · Score: 1

      But... will it be backwards compatible with OS/2?!

    14. Re:Not sure about the difference... by EvanED · · Score: 1

      You do realize "Under this new versioning model, the next major release of the Linux kernel to follow will be Linux 3.1, then Linux 3.2, etc."

      That's FTFA. So there will be a 3.1; in fact, it will likely be quite soon.

    15. Re:Not sure about the difference... by pandrijeczko · · Score: 1

      Thanks, and I am more than happy to stand corrected & go away feeling good that I have learnt something today from someone kind enough to explain it succinctly.

      Hence not gracing the AC trolling above with any form of a response.

      --
      Gentoo Linux - another day, another USE flag.
    16. Re:Not sure about the difference... by pandrijeczko · · Score: 1

      Thanks again for a succinct explanation and correcting my error.

      I have used Linux for some years and did try one or two 2.5 kernels before 2.6 came out properly. Now that you mention it, I do remember Linus mentioning it at some point, and it's good to be reminded.

      --
      Gentoo Linux - another day, another USE flag.
    17. Re:Not sure about the difference... by pandrijeczko · · Score: 1

      Actually, on second thoughts, I will grace your response with one from me.

      I would just like to highlight to anyone else reading this who is not currently a Linux user but thinking of trying it, that the above type of abusive response is not typical of most Linux professionals.

      I personally consider an operating system to be a tool to get a job done and I consider Linux to be an exceptionally good tool at getting the jobs I need to get done.

      However, unlike the AC above, I am not an abusive Linux zealot who clearly has very deep personality issues such that he/she needs to turn an operating system into a religion.

      If, for example, a relation or colleague gives me their Windows PC to fix, they do not get it back a week later with Windows wiped, Ubuntu installed in its place and a finger-wagging lecture from me about the sins of Microsoft - no, they get back a repaired Windows PC along with some useful Windows OSS software and some instruction on how to use it so they can avoid getting into trouble again.

      So please disassociate me from morons like the AC above who do nothing to further OSS or Linux because they are far too concerned about their miniscule penile dimensions.

      --
      Gentoo Linux - another day, another USE flag.
    18. Re:Not sure about the difference... by MikeBabcock · · Score: 1

      Me too. The last copy of Windows I bought and paid for was WFW 3.11. It was a pretty stable OS, although I was using Desqview/X as well on another machine and if the software had existed, I would've used it even more.

      By the time Windows 95 came out, I was mostly running Linux.

      --
      - Michael T. Babcock (Yes, I blog)
    19. Re:Not sure about the difference... by Runaway1956 · · Score: 1

      I'm not a professional, so I can be abusive all I want. Now, say something retarded so I can feel justified in abusing you . . .

      Meanwhile, AC is truly retarded. You were making funny, and he was just to stupid to see that. See? I'm an equal-opportunity abuser!!

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    20. Re:Not sure about the difference... by rrossman2 · · Score: 1

      So when it hits 3.1.1 is when it starts supporting Networking, right?

    21. Re:Not sure about the difference... by Mr.+DOS · · Score: 1

      It launched instantly, and everything was amazingly fast (for someone use to the 386, where waiting for things was just normal).

      The extra RAM also helped amazingly with the stability, too. I tried putting Windows 3.11 on a 166MHz Pentium with 64MB RAM years ago on a lark, and was shocked at just how performant the installation was. I mean, you couldn't really do much due to the lack of modern backported software, but what it could do, it did fantastically.

    22. Re:Not sure about the difference... by V!NCENT · · Score: 1

      To explain further:
      Linux version a.b.c.
      First number is first stable (comming after 1.0 is 2.0). This number never changes again and is thus useless, because;
      b number means architecture change. After 2.1 (unstale (because b is odd)) comes stable 2.2. Now b indicates stable or unstable.
      Now that 6 (third and final acrhitecture change as Linux is pleased with the way everything is working) is not needed anymore we enter;
      c number. Odd indicating unstable and even stable. So 2.6.37 is unstable comming after stable 2.6.36 and heads for stable 2.6.38.

      As you can see, having 2.6.x is useless, because they don't represent trackable numbers anymore (they don't ever change), and the c number was getting huge. A logical follow up was choosing a number higher than 2; being 3.

      Now expect 3.0 to be stable (actualy the last version was 2.6.39, going 2.6.40, but Linus wanted to go with 3.0 now, so this is a stable release), 3.1 to be unstable and 3.2 to be stable, etc.

      Once we hit 3.39 (after 20 stable releases), Linux will probably hit 4.0.

      --
      Here be signatures
    23. Re:Not sure about the difference... by MrDoh! · · Score: 1

      I'd not worry. I'd forgotten that he'd dropped that naming sequence too and was thinking the odd weren't the stable release until this thread.

      --
      Waiting for an amusing sig.
    24. Re:Not sure about the difference... by lolcutusofbong · · Score: 1

      That just makes the eventual Win32s port of PuTTY that much sexier.

    25. Re:Not sure about the difference... by Anonymous Coward · · Score: 0

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

      OMG!!! 3.1 ???? NO WAY

    26. Re:Not sure about the difference... by kasperd · · Score: 1

      The Linux kernel uses an even-odd system version numbering system, such that any odd-numbered minor version number is a development (beta) version.

      That system has been abandoned, which is in fact the major change from 2.6.39 to 3.0.0.

      --

      Do you care about the security of your wireless mouse?
    27. Re:Not sure about the difference... by Timmmm · · Score: 1

      No they stopped doing the even-odd thing ages ago. There are no major changes from 2.6.39 to 3.0.

    28. Re:Not sure about the difference... by smithmc · · Score: 1

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

      Maybe we can just skip over that and go straight to the reasonably stable Linux NT 4.0 SP3...

      --
      Downmodding is the refuge of the weak. Don't downmod, make a better argument!
    29. Re:Not sure about the difference... by kasperd · · Score: 1

      Even in recent years, they haven't used an odd number in the second component for any stable release. But with 3.x.y they intend to do so. The first stable kernel with an odd number for the second component will be 3.1, and it will probably be released before the end of this year.

      --

      Do you care about the security of your wireless mouse?
    30. Re:Not sure about the difference... by Anonymous Coward · · Score: 0

      Yeah but that's just because they removed one level of numbers. The second component is going to act in the same way as the third component of 2.6, not the second.

      They've changed from 2.6.x.y to 3.x.y

  20. No changes in 3.0 by Estevao · · Score: 1

    There will be no significant changes or magic features in 3.0, it's _just_ a rename... but why? Linus said that 40 is a big enough to deal with, just like that.

    1. Re:No changes in 3.0 by Anonymous Coward · · Score: 0

      He's hoping to cash in as he can see that Linux really has hit it's high water mark and he realizes the future for him and his ilk is bleak.

  21. 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.

    1. Re:Odd version numbers by Estevao · · Score: 1

      Good point.

  22. Waste of time by Anonymous Coward · · Score: 0

    This is clearly a waste of time. Changing numbers just for the sake of changing numbers.

    The argument Linus gave for the change is something you would be fired for where I work. Forty is too big a number ?????? What?!

    1. Re:Waste of time by Anonymous Coward · · Score: 0

      Linus said "can no longer comfortably count" rather than "can't count". Quite different I think?

      Maybe he is developing a memory disorder (no pun), and if that is the case, should he be trusted with numbers, even if it is 0 and 1:)

      thank you

    2. Re:Waste of time by BreezeC · · Score: 1

      Linus want to celebrate Linux 20th.

    3. Re:Waste of time by evilbessie · · Score: 1

      It's his toy, if you want you can take the code and give it whatever version number you like there is nothing stopping you.

    4. Re:Waste of time by camperdave · · Score: 1

      Linus said "can no longer comfortably count" rather than "can't count". Quite different I think?

      It's a case of arthritis in his left thumb. Since he counts in binary using his hands, finger/thumb touching the table for 1 and not touching for 0, any number from 32 to 63 gives him pain.

      --
      When our name is on the back of your car, we're behind you all the way!
    5. Re:Waste of time by Dog-Cow · · Score: 1

      That's the nice thing about being in-charge, even if it's a de-facto appointment. You can do whatever the Hell you want, without caring how silly or capricious it is. And you don't have to account for yourself to mostly-anonymous slashdot posters.

  23. Better question... by RichiH · · Score: 1

    > Is there a real reason for skipping 2.8 here

    What makes you think there shouldn't be a 2.10.x and 2.12.x?

    Moral: Version numbers are just that, numbers. Personally, I would have preferred 11.05 but as long as the Kernel remains healthy, they can start naming it after cereal for all I care.

    1. Re:Better question... by Anonymous Coward · · Score: 0

      Yay, cereal kernel! Will there be special releases we get at the bottom of the box?

  24. 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.

    1. Re:Time for a change by Anonymous Coward · · Score: 0

      Yes. So fork it and do it, then.

    2. Re:Time for a change by siride · · Score: 1

      This must be a joke post. Even Stallman wouldn't require calling it the "GNU/Linux kernel".

    3. Re:Time for a change by Anonymous Coward · · Score: 0

      Well, fork you!

    4. Re:Time for a change by MikeBabcock · · Score: 1

      Its the Linux kernel. The OS with supplementary GNU-sourced components are GNU/Linux. As in GNU on Linux. GNU on HURD would be GNU/Hurd or just GNU as HURD is GNU as well.

      Sigh. Nomenclature is lost on people these days.

      --
      - Michael T. Babcock (Yes, I blog)
  25. 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 Abreu · · Score: 1

      But, who's on first?

      --
      No sig for the moment.
    2. Re:First base! by Kompressor · · Score: 1

      And if you thought Naturally was the first baseman, then you don't know Who.

      What?

      --
      kmem russian roulette: Aquillar> dd if=/dev/urandom of=/dev/kmem bs=1 count=1 seek=$RANDOM
    3. Re:First base! by Morose · · Score: 0

      No, he's on second.

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

      Oh he's on second.

      --
      Wax on, wax off baby!
    5. Re:First base! by lennier · · Score: 1

      Who's the General Secretary of the Chinese Communist Party?

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    6. Re:First base! by treeves · · Score: 1

      Yes, but you spelled it wrong.

      --
      ...the future crusty old bastards are already drinking the Kool-Aid.
  26. "Sneaky Weasel" by mrmeval · · Score: 0

    diff --git a/Makefile b/Makefile
    index 529d93f..afb8e0d 100644 (file)
    --- 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 go on a Vegan diet but the delivery time from Vega is too long. --brownkitty
  27. Read Linus on Linux Kernal Message by Anonymous Coward · · Score: 0

    He explains it all. If you don't have a clue about the subject then shut the fack up.

  28. I'm more concerned by Anonymous Coward · · Score: 0

    about Linux ME.

  29. Waste of time by TheCount22 · · Score: 1

    Changing numbers just to change numbers is a waste of time. The reasoning Linus gives for the change is absolutely worthless. He can't count to 40. what!? Where I work you would get fired for something like this.

    This wastes everyones time and causes unnecessary confusion. If at least he said something like "It makes people talk about Linux" or "We wanted to celebrate our good work by tagging 3.0" I might have accepted the reasoning. I think the features between 2.6.40 and 3.0.0 have not earned the 3.0.0 badge.

  30. 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 TarMil · · Score: 1

      What, you mean "Sneaky Weasel" is not appealing for suits? What a letdown.

    2. 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.

    3. Re:If Linux kernels had microsoft names by Anonymous Coward · · Score: 0

      I'd pay extra for Linux 7 'extreme' edition!

    4. Re:If Linux kernels had microsoft names by DMoylan · · Score: 1

      huh i would have thought a microsoft kernel would be along the lines of;
      ProfessionalEnterpriseKernel NoBugsHere SafeAsHouses ReallyExpensiveSoMustBeGood

    5. Re:If Linux kernels had microsoft names by zamboni1138 · · Score: 1

      Microsoft didn't give up the version numbers after Windows NT 4. I've posted this before, so here goes again:

      Windows NT 4 = Windows NT 4
      Windows 2000 = Windows NT 5
      Windows XP = Windows NT 5.1
      Windows Vista = Windows NT 6
      Windows 7 = Windows NT 6.1

      Don't believe me? Open up your favorite browser in Windows and check the User Agent string.

    6. Re:If Linux kernels had microsoft names by SEE · · Score: 1

      Yeah, I was kinda annoyed that they didn't increment the version number all the way to 7.0 for Windows 7. Now what are they going to use for Windows 8, 6.2 or 7.0?

    7. Re:If Linux kernels had microsoft names by Bing+Tsher+E · · Score: 1

      Yes, but Microsoft gave up on meaningful version numbers when the very first release of Windows NT was version 3.1. (presumably to synch with Windows 3.1 which was the current version at the time)

      Since the numbering system is based on that start, it can't really ever be a valid sequence. Unless, maybe, NT 4.0 had been called NT 6.2, and Windows 2000 was called NT 9.3.

    8. Re:If Linux kernels had microsoft names by Anonymous Coward · · Score: 0

      linux isent as cool as windows ie linux 3

    9. Re:If Linux kernels had microsoft names by Anonymous Coward · · Score: 0

      They should have gone for "Linux 9" - that way they'd be way ahead of Microsoft!

    10. Re:If Linux kernels had microsoft names by Anonymous Coward · · Score: 0

      The general public when utilizing Linux (say for mobile phones) doesn't know the kernel version number. They just know it as whatever Android package version it is.

    11. Re:If Linux kernels had microsoft names by 91degrees · · Score: 1

      Probably 6.2, but honestly, they could just as reasonably use 8.0 or even 9.0 or 14.0 for all the difference it makes. Doesn't really matter as long as the current version number is higher than the previous one.

    12. Re:If Linux kernels had microsoft names by Bacon+Bits · · Score: 1

      Currently, Windows 8's version is "7.0".

      The internal version number is indicative of what kernel they're using. 2000 = 5.0, XP = 5.1, 2003 (and XP x64) = 5.2 because they're slightly different kernel revisions. Vista = 6.0 and 7 = 6.1 because Vista was completely different and 7 rewrote the bits of the kernel that sucked in 6.0. 8 will be 7.0 presumably because of major changes such as ARM and SoC support.

      --
      The road to tyranny has always been paved with claims of necessity.
    13. 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."
    14. Re:If Linux kernels had microsoft names by Anonymous Coward · · Score: 0

      And if Microsoft had the Ubuntu marketing settings for names we'd have shit like Masturbating Monkey and Gay Giraffe.
       
      Get over it. They all pull the same shit and it's only your selective memory that makes Microsoft looks any worse than anyone else. Either that or you're a straight up astroturfing troll.

    15. Re:If Linux kernels had microsoft names by unencode200x · · Score: 1

      Or just open a command line in any version of Windows and type ver.

      --

      Chance favors the prepared mind.
      Perfect is the enemy of good.
    16. Re:If Linux kernels had microsoft names by F.Ultra · · Score: 1

      Yes, and they are used extensively throughout the industry ;-)

    17. Re:If Linux kernels had microsoft names by TheQuantumShift · · Score: 1

      But will fan-boys annoyingly insist you pronounce it "Lin-uh-Ten"?

      --

      Shift happens. Fire it up.
    18. Re:If Linux kernels had microsoft names by Anonymous Coward · · Score: 0

      But will fan-boys annoyingly insist you pronounce it "GNU Lin-uh-Ten"?

      FTFY

    19. Re:If Linux kernels had microsoft names by Anonymous Coward · · Score: 0

      Version 11 would be LinuxX2 and version 12 LinuxX3.
      (corel paint shop photo pro)

    20. Re:If Linux kernels had microsoft names by Blakey+Rat · · Score: 1

      It's technically the NT kernel version, not the version of the entire package. The reason it's 6.1 instead of 7 is that there simply aren't enough NT kernel changes between Vista and Windows 7 to justify a full version number.

  31. Tablets by Anonymous Coward · · Score: 0

    Since Android 3.0, WebOS 3.0 and iOS 3.2 were tablet operating systems, does that mean???

  32. 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.

  33. Linux 300 by ei4anb · · Score: 1

    Spartans! Prepare for glory!

    1. Re:Linux 300 by colinrichardday · · Score: 1

      Shouldn't that be Spartans, prepare for twelve-year old boys!

  34. 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."
  35. Why Not? by hduff · · Score: 1

    GNU 3.0.0?

    Then Stallman can say "GNU 3 is not GNU. It should be called GNU GNU. Ouch! My head hurts!"

    --
    "I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
    1. Re:Why Not? by Anonymous Coward · · Score: 0

      I would think that GNU 3 would be GNU GNU GNU. Of course, GNU I

  36. You left out the best one... by anti-pop-frustration · · Score: 1

    Linux ME (aka Linux Millennium Edition)

    1. Re:You left out the best one... by MikeBabcock · · Score: 1

      The problem with Windows Me is that "Buggy" isn't spelt with an M.

      --
      - Michael T. Babcock (Yes, I blog)
    2. Re:You left out the best one... by Bob+the+Super+Hamste · · Score: 1

      I thought ME stood for Mistake Edition

      --
      Time to offend someone
  37. Final nail int he coffin. RIP Centos! by Anonymous Coward · · Score: 0

    Long Live SL!!!

    ssh-dss AAAAB3NzaC1kc3MAAACBAOW8CkHHDmwv3ZES/Z5hFMRQEKS/UNEyJU272/E/KChoAtWe4ImX
    91MRfX3PkeqGbdOWi8oBKCTUF76aUWOYTkLNKM/kgyE5IdTIboh7Yg8NhqQe9Y8Am50PTX3xtYmd5aUd
    yDAmCW+Wrq4f6IBAMaOWUmztdAeAVI+kPsGT+qW/AAAAFQCvwds0FwtfX113DBGEa43Yeosq9QAAAIEA
    04z4dtCqeW09JfgocMQvvqtBG3cDt7GyfMzju/XCYlMQFgKQd3ClLK6cbKQ3dFumMEKzVHME/bCNAIli
    naYODlSOIoEa3uFmCxOYbegy2oipTUBobGhU9U379YywHQfztxmUYJp5nCiiW+KDkEc2lB6IggRZi3fQ
    qaYt01ygc8AAAACBAI4dvLYbwe0AvJm/Wd3Bts/DXqjnzZLrXldG2OYwoZ6xuFKnWsqpa9+DdJn+BlDL
    ye1/vbLkXgirYlUAePI/mtgkqb3zQnHJ7NKzN3l4AKmJ5VElyXx2n4ijhfko0inEc76vWXXnwyQFAD90
    5/r6FYrTthgzN390Q/vUR5alyXGm

  38. How can he do that? by Anonymous Coward · · Score: 0

    Does he own it?

    1. Re:How can he do that? by armanox · · Score: 1

      Why yes he does.

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
  39. It will be useful to marketing flakes by RogueWarrior65 · · Score: 1

    Just think, the marketing flakes will all be able to say "Our new product uses Linux 3.0! Everyone else is using that old, outdated 2.6 stuff."

    I had always subscribed to the methodology that the third digit was for bug fixes. The second was for minor features and the first for a major new version. As I learn (or attempt to learn) about Linux development I see that there are so many little esoteric changes and/or new features every time a new version comes out that I have no idea if upgrading is really worth the effort.

  40. Now we know ... by clyde_cadiddlehopper · · Score: 1

    Now we know exactly how many angels can dance on the head of a pin: 2.6.39. Move along, nothing to see here.

    --
    Obi-Wan: "I felt a great disturbance in the Force, as if millions of voices suddenly cried out in terror and were sudden
  41. Running out of integers? by Arrepiadd · · Score: 1

    then eventually run out of credible major version number and just plain look stupid...

    Anything wrong with 10, 11, 15, 70, 200?

    1. Re:Running out of integers? by KevinColyer · · Score: 1

      Perhaps he should follow one other good example (http://en.wikipedia.org/wiki/TeX) and start the progression towards pi, and hence, perfection?

      3.0.0
      3.1.0
      3.1.4
      3.1.41...

  42. Just name it 1337 by Jawcracker+Fuzz · · Score: 1

    Like that Volkerstein guy did.

  43. OMG elevent1111! by Anonymous Coward · · Score: 0

    This is teh R0x4r.!!!!

  44. Here is WHY 3.0 by wzzzzrd · · Score: 1

    Linux enters it's 3rd decade soon, that's the sole reason.

    --
    On second thought, let's not go to Camelot. It is a silly place.
  45. Re:Should have waited by Bing+Tsher+E · · Score: 0

    It's not karma whoring when it's done for just the joy of being a nerd. Who pooed in your drinky?

  46. 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 ?
    1. Re:Version numbers in the real world by dargaud · · Score: 1

      Whoosh...

      --
      Non-Linux Penguins ?
    2. Re:Version numbers in the real world by Anonymous Coward · · Score: 0

      FUCK.YOU.ASS.HOLE

    3. Re:Version numbers in the real world by rdnetto · · Score: 1

      1.0 // We are selling it

      1.1 // Now it works, we swear

      2.0 // We know you wouldn't shell out for version 1.5

      3.0 // Just to keep you updating

      Am I the only one thinking of the .NET Framework? (at least 3.5 added some nice features)

      --
      Most human behaviour can be explained in terms of identity.
    4. Re:Version numbers in the real world by Anonymous Coward · · Score: 0

      fuck you you self centered short sighted condescending bastard.

      Why hold back? Say what you really think.

      lol...

      Anyways: The most important and influential software in the world by far is of the in-house variety. I can only note that you obviously haven't got even the faintest clue about software in the real world. You are funny. Made my day. Thank you.

  47. The end of the world by skovenborg · · Score: 1

    According to Linux there's an ancient Sumerian prophecy which imply that the moon will explode if they called it 3.0. I hope they decoded those old tablets wrong because this could mean the end of the world. See http://joebarr.sys-con.com/node/32801 question 3.

    1. Re:The end of the world by Anonymous Coward · · Score: 0

      I was hoping we would blow up the moon before the last decade was out. Better late than never, I guess.

  48. Free +1 for you! by Nimey · · Score: 1

    Easy +1 for the pointless and off-topic anti-Microsoft post.

    Why'd you feel the need to bring them up, anyhow?

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
  49. It is a sad sad day by Anonymous Coward · · Score: 0

    ...when Linus Torvalds becomes a pawn of the digitary-industrial complex.

  50. 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.
    1. Re:About damn time by allo · · Score: 0

      1.0 is for me as developer the release, which features everything i think my software should have, with no known bugs at releasetime. Thus 1.0 is a hard release. Then its easier to follow, i.e. releasing Bugfixes-Release as 1.0.1, working on 1.1.1 as Release with new features.

    2. Re:About damn time by Anonymous Coward · · Score: 0

      Sounds to me like you are the one afraid of some specific numbers.

    3. Re:About damn time by reub2000 · · Score: 1

      Same idea as google's perpetual betas. All software has bugs, but it's easier to explain when you can just say that something is pre-release.

    4. Re:About damn time by Anonymous Coward · · Score: 0

      In at least some open source sub-communities, there's a cultural drive to use tiny version numbers. It's a way of showing humility about your own project, and acknowledging that you haven't done nearly all the quality control work that you'd like to see any major project do before hitting 1.0. It's also a slap back at the commercial software vendors who often have a release 4.7 that's still alpha quality in the eyes of serious developers.

      It was a running (only kinda) joke in some Perl circles at one time that when a Perl module hit 1.0, that meant it had already been replaced by a newer and better project and was now just in maintenance mode.

      The sometimes-crappy part is, people who think like this and use those low version numbers purposefully tend to write really high quality software in the long term, and they often never bother releasing a 1.0, they just keep chugging through 0.x releases well after any outside observer would have called the software badass enough to earn more than a mere 1.0. And then outsiders who aren't aware of all of this assume it must be low-quality software, which it isn't.

    5. Re:About damn time by MikeBabcock · · Score: 1

      Did you also have a hard time understanding Dewey Decimal?

      --
      - Michael T. Babcock (Yes, I blog)
    6. Re:About damn time by swillden · · Score: 1

      Linus just realized that version numbers are about marketing more than anything else.

      Not a bit. Linus just got tired of the extra baggage of the meaningless 2.6. Under the model they've been using, those numbers will likely never change, so they're just dead weight. They should have been chucked a long time ago, but it took some time to overcome the inertia.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    7. Re:About damn time by Anonymous Coward · · Score: 0

      Version 1.0 of MythTV will manage multirec properly and let you record as many programs that are available on a bouquet, not a maximum of 5 (which are actually 5 tuner entries in the database, to make recording scheduling a headache).

    8. Re:About damn time by Anonymous Coward · · Score: 0

      I agree with the 0.x stuff
      I can see using 0.x for pre-first release. But your first release that's not intended for devs ought to be 1.0(.0)

    9. Re:About damn time by Eil · · Score: 1

      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.

      Why? What six or seven major changes have happened to the kernel since 2.6.0 to justify as many major version bumps? Or is the kernel just old enough that it "feels" like it should be in version 8 or 9 by now? How would that be any different than Linus suddenly bumping the version to 3.0 purely (by his own admittance) on a whim?

      What's with open source and all these version numbers starting with 0.x?. Why are they so afraid of just a freaking number?

      The rule of thumb is that a release with a version number < 1 is considered incomplete by its authors. Of course, "incomplete" can mean different things to different people. Also, never reaching 1.0 can lend a feeling of "perpetual beta" to the project. It feels a lot less fun to be working on a project that can be considered finished.

      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.

      Not sure what correlation you're implying... Linus doesn't work for Red Hat. And Red Hat doesn't ship the mainline kernel, they ship their own.

    10. Re:About damn time by Anonymous Coward · · Score: 0

      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.

      red hat sits squarely at the bottom of the list of major software providers in earnings per share. OS zealotry is one thing, but if you extend that to your investment portfolio, free beer is in fact what you'll need, never mind want.

  51. Want v3.1.1 by Anonymous Coward · · Score: 0

    Linux for Workgroups!

  52. Memories by G3ckoG33k · · Score: 1

    Most smartphones are way faster than a P2. I'm not sure if that is good or bad, as I had a $2000 P2 (300MHz Klamath) too.

  53. Re:Everyone knows it takes until at least version by hedwards · · Score: 1

    So then, the problem with Windows is that MS didn't number the releases properly? So, that's why they largely gave up on numbers for a while. They go from 3.11 to 95 to 98 then to a weird Me thing, before skipping all the way to 2000. After which they went XP to Vista before going all the way back to 7.

    Thank you, I finally get the problem, MS developers can't count. Thankfully they fixed the problem. The next release was going to be Windows Eleventy thousand billion.

  54. Brace for the flood of Windows users! by MasterOfGoingFaster · · Score: 1

    At last! My Microsoft experience has taught me to wait for the third version before buying. Sounds like the Linux that Microsoft users have been waiting for!

    So this thing is finely stable, right? Like DOS 3?

    --
    Place nail here >+
  55. The Year of Linux by Anonymous Coward · · Score: 0

    This year will be the year of Linux. Version 3.0 will put the final blow to Windows and MacOS X. Yeahy!! :)

  56. Slackware 96 by srobert · · Score: 1

    Don't laugh. The first Linux distribution I used was "Slackware 96". (Which contained the Linux 2.0.0 kernel.) Perhaps one-upping "Windows 95" in the naming subconsciously persuaded me to give it a try.

    1. Re:Slackware 96 by Anonymous Coward · · Score: 1

      Bah...you kids had it easy. I ran Yggdrasil with the 1.2 kernel. Had to run all the man pages through troff before I could get X running in 8MB on my '386, at which point it wasn't actually capable of doing much else, really. I check back in with Linux every five years or so, it's been crap each time - half-baked open shovelware with horrendously bad interfaces, infinite obscure configuration files, always-faulty drivers... nothing works without hours of pain for every little thing. Productivity-wise, it's always been a complete waste of time. I suppose it's time to have another go, but on the other hand I could just hit myself repeatedly on the head until the feeling goes away... yeah, actually that sounds more useful and pleasant - certainly much quicker.

  57. Please read Linus's post on.... by jim_kaiser · · Score: 1
    Linus musing about 3.0

    This has been in the pipeline for a while now and it kinda makes sense. Currently the 2.6.xxx has so many versions, it is no longer clear which is from when. His reasoning for the 3.0 as Linus says is that 2 decades have passed in the linux kernel development (Sounds like he's trying to avoid a conflict by giving a reason which cannot be argued against). But it also feels like the 3rd generation in linux kernels too with all the new hardware nowadays.

    I feel somewhat relieved by this move.. its like i have been holding my breath for decades and can let it go now!

    --
    The last person to mod me down is a rotten egg..... there.. that should do it..
  58. Re:Everyone knows it takes until at least version by jonbryce · · Score: 1

    And to be really confusing, Windows 7 is actually Windows 6.1, or saying as there was never an NT1 or NT2, it is probably actually Windows 4.1.

  59. < -- (missing &lt;) by Anonymous Coward · · Score: 0

    Have one on me. :-)

  60. Apple is going to run into this problem eventually by makubesu · · Score: 1

    Mac OS XI?

  61. When WWF chair throwing became common.. by WaffleMonster · · Score: 0

    What is the point of maintaining a versioning schemes if you seek to undermine it for political reasons unassociated with actual scope or effect of changes?

    It will be interesting to see how many people stick with a 2.x series kernel normally than they would otherwise simply because they *think* an abnormal amount of change is present in 3.x.

  62. Life ends at 2.6.40 by Anonymous Coward · · Score: 0

    Linus must have looked at the number and thought, my god!, that's my age, and decided he want them younger.

  63. Well ... by lennier1 · · Score: 0

    Shouldn't a kernel which jumps to 3.x contain something groundbreaking to warrant more than a 0.1 increase?

    1. Re:Well ... by Anonymous Coward · · Score: 0

      No.

  64. Wake up, bad hardware vendors by bmidgley · · Score: 1

    I've seen hardware like an awful touchscreen flat panel or an embedded arm board that reportedly support "linux 2.6" in their marketing materials. This could literally mean they ship a kernel module or patches or whatever that haven't worked with a current kernel for something like **7 years**! Yes, we should have meaningless version bumps in the kernel, but they should happen more often than once or twice each decade.

  65. Backwards compatibility by Weaselmancer · · Score: 1

    No, the error is included for backwards compatibility to early Pentium processors. Linux NEVER abandons a platform.

    --
    Weaselmancer
    rediculous.
  66. Pedantry: Systemtap isn't in an upstream kernel by Sits · · Score: 1
  67. Meh. Give me a cluster with a single OS image by Colin+Smith · · Score: 1

    Till then it's all just incremental.
     

    --
    Deleted
  68. Re:Everyone knows it takes until at least version by Barbara,+not+Barbie · · Score: 1

    Windows 95 was internally labelled as Windows 3.95 because too much softwaare broke in testing when they had it report as Windows 4.0. Also keep in mind that it ran atop DOS 7.0, so they didn't "do away" with the numbering system. It's always been there, through 95, 98, ME, XP, NT, W7.

    --
    Let's call it what it is, Anti-Social Media.
  69. I think it is the "perpetual beta" mentality by Sycraft-fu · · Score: 1

    A good number of OSS projects seem to have the Google "It is always in beta," thing going on. By that I don't mean that the code isn't ready for general use, but that because it is "beta" you can kinda brush off bugs. If there's something you don't want to fix or a feature that doesn't work right you have the "Oh it is beta" excuse to pull out. To them, 1.0 seems like committing to something major, to stable release quality, and that kind of thing.

    I think it is silly. I've always thought version numbers should move relatively rapidly since the whole purpose is to let people know when something is new. Do it as two numbers major.minor. Decide what roughly constitutes a major release and when that happens, increment the first one. Anything else that isn't just a bug fix, increment the second one.

    Don't just increment to big numbers randomly, but don't be scared of them. Make it a useful guide for your customers.

  70. Re:Apple is going to run into this problem eventua by Anonymous Coward · · Score: 0

    Except that it is Mac OS X v. 10.? That is not the Roman numeral for '10' it is the letter X.

  71. Re:Apple is going to run into this problem eventua by networkzombie · · Score: 1

    You are incorrect. The X stands for 10, as in the Roman numeral. Did you just spew that out without looking it up or did a Mac user tell you that it was pronounced ex? The X in Mac OSX is pronounced Ten. Perhaps you are trolling?

  72. Like Python by cyberrodent · · Score: 1

    Coincidental for sure but Python made the same jump from 2.6 to 3.0

    http://python-history.blogspot.com/2009/01/brief-timeline-of-python.html

    (yes there is/was python 2.7 but it was released after 3.0)

    --
    Talk is cheap. Supply exceeds demand.
  73. Really? by laddiebuck · · Score: 1

    Is this just his way of dealing with mid-life crisis?

  74. KDE Compatible? by formfeed · · Score: 1

    Obviously gimp 2.6 will have to be replaced by 3.0 as well.
    But now, will a 3.0 kernel also work with KDE 4.6 or would I have to go with a lower version number like Gnome3 ?

  75. Semantic versionning by anarcat · · Score: 1

    I am always fascinated by Linux version numbers. I can't quite figure out what they mean, and I suspect I'm not the only one. Reading that "2.6.40 is more distinct from 2.6.0 than 2.6.0 was from 2.0.0" doesn't make any sense to me. For my projects, I have always intuitively followed the Semantic Versionning principles: x.y.z, where X is a major version, Y is a minor version and Z is a patch release. You increment X when you change the API. You change Y when you add a feature. You change Z when you make a small bugfix. Simple and clear. Linux, on the other hand, seems to follow more the whims of Linus than any logical process, which seems to be a common pattern in this project, and which is not always for the worst though...

    --
    Semantics is the gravity of abstraction
  76. So with 3.0, is he allowing breakage? by SheeEttin · · Score: 1

    So Linux 3.0 is on its way... Which makes me wonder--given that it's a major increment for something that has traditionally been very stable (in terms of API/ABI, etc.), is Linus going to allow breakage or incompatability with 3.0? Or is it just a "yeah, it's been too long, let's just bump it for numbers' sake"?

  77. FreeBSD bumps bersion numbers every 18 months by Pigskin-Referee · · Score: 1

    If version numbering in Linux resembled the method used in FreeBSD, they would be at be version 50 by now. FBSD bumps their major version number every time someone dots an "I" or crosses a "T". Code improvement is not a requirement. More than 5 years since the original wireless "N" draft was released and still the FreeBSD developers have failed to produce drivers for devices that support that protocol. The developers are too busy bumping version numbers to be concerned.

    --
    Pigskin-Referee
    Linux: Yesterday's technology, tomorrow ...
  78. Drawing the line or just counting? by bill_mcgonigle · · Score: 1

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

    You could almost go by RHEL major versions there... but, speaking of arbitrary:

    Does anybody track the number of releases? That is, will Linux 3.0.0 be Linux release #127 or something along those lines? I'd really rather track that kind of number, and if somebody is already doing the counting, so much the better. At a minimum, it would make programming easier.

    if (linux_version > 122 && linux_version 149) { ....
    }

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  79. oh, hell, Slashcode by bill_mcgonigle · · Score: 1

    if (linux_version >= 122 && linux_version <= 149) { ....
    }

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)