Slashdot Mirror


Video Interview With Linus On Linux 2.7

daria42 writes "ZDNet Australia has put up a video interview of Linux creator Linus Torvalds talking about the kernel development process, explaining why the unexpected resilience of kernel version 2.6 has delayed the move to 2.7." From the interview: "One of the original worries was that we would not be able to make big changes within the confines of the development model... I always said that if there is something so fundamental that everything will break then we will start at 2.7 at that point... We have been able to do fairly invasive things even while not actually destabilizing the kernel... Having stable and unstable in parallel: I think it used to be a great model, and I think we may see that the kernel has actually become more mature and stable and it just doesn't seem to be that great a model, for the kernel."

178 comments

  1. Is flash player 8 available for linux? by Anonymous Coward · · Score: 0, Insightful

    It would be nice if the video on Linux could be viewed on Linux.

    1. Re:Is flash player 8 available for linux? by Anonymous Coward · · Score: 4, Funny

      Flash 8 has been shown to destabilize the 2.6 kernel... Supposedly it will play nicely with the 2.7 kernel, though.

    2. Re:Is flash player 8 available for linux? by FudRucker · · Score: 1

      true...

      oh! the irony...

      --
      Politics is Treachery, Religion is Brainwashing
    3. Re:Is flash player 8 available for linux? by vladsinger · · Score: 3, Informative

      Flash Player 9 is avaliable for linux. I was going to gripe about it too, but there are at least two posts above which link to the download site.

    4. Re:Is flash player 8 available for linux? by Dadoo · · Score: 1

      Works fine for me, and I'm using Flash 9 on an Athlon 64.

      --
      Sit, Ubuntu, sit. Good dog.
    5. Re:Is flash player 8 available for linux? by dtfinch · · Score: 1

      Flash 9 for Linux has been available for at least a month or so, practically forever. Occasionally the sound stops and I have to restart Firefox, but that's the worst of my problems.

    6. Re:Is flash player 8 available for linux? by smittyoneeach · · Score: 2, Funny

      I installed, and even rebooted my laptop, for that Genuine Windows feel, and video still no worky-worky. Is this an elaborate prank?

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    7. Re:Is flash player 8 available for linux? by towsonu2003 · · Score: 1
      Flash 9 for Linux ... the sound stops and I have to restart Firefox, but that's the worst of my problems.
      how nice...
    8. Re:Is flash player 8 available for linux? by supertoad · · Score: 1

      but not on a 64-bit operating system, or at least not a 64-bit version of firefox

    9. Re:Is flash player 8 available for linux? by Anonymous Coward · · Score: 0

      Flash 9 has been in beta, you should say. That is why you have those problems. Flash 9 was officially released today. Not everyone enjoys the experiences of such quality software and therefore his gripe is legitimate.

    10. Re:Is flash player 8 available for linux? by goaty_the_flying_sho · · Score: 1

      Amen.

    11. Re:Is flash player 8 available for linux? by vhogemann · · Score: 1

      Agreed,

      How hard it would be to provide an OGG Theora version of the video?

      --
      ---- You know how some doctors have the Messiah complex - they need to save the world? You've got the "Rubik's" complex
    12. Re:Is flash player 8 available for linux? by miscz · · Score: 1

      Heard of nspluginwrapper?

  2. Too bad Flash 9 isn't released for linux yet by Wonko+the+Sane · · Score: 3, Insightful

    How difficult is it to release a video about linux kernel development in a format that is easy to watch by people running linux? At least use flash 7...no need to blow their minds talking about ogg/theora.

    1. Re:Too bad Flash 9 isn't released for linux yet by punkrockguy318 · · Score: 3, Interesting

      Flash 9 was released for linux today. Enjoy :)

    2. Re:Too bad Flash 9 isn't released for linux yet by kras · · Score: 1

      I just watched the video with flash 9 beta for linux. no problem. you find it here.

      --
      memento mori
    3. Re:Too bad Flash 9 isn't released for linux yet by Wonko+the+Sane · · Score: 1

      Talk about timing. It does seem to be x86 only, however. Seems like it will be a while until I can ditch the 32 bit firefox.

    4. Re:Too bad Flash 9 isn't released for linux yet by Anonymous Coward · · Score: 0

      . . . flash 7 . . .

      Bleh. Now that Java will soon be freed, I'd rather see something akin to Cortado than the continued reliance on proprietary garbage.

    5. Re:Too bad Flash 9 isn't released for linux yet by Anonymous Coward · · Score: 0

      u furgot ur link

    6. Re:Too bad Flash 9 isn't released for linux yet by sulfur · · Score: 1

      (Un)fortunately, Flash format is better than other popular video streaming formats like WMV or Real Video. At least it works with flash player 9 beta (however, it crashes firefox once in a while). So I guess it is better to choose the lesser of two evils here. And please don't say about OGG, I know that it's great, but I am talking about popular video formats.

    7. Re:Too bad Flash 9 isn't released for linux yet by Wonko+the+Sane · · Score: 2, Interesting
      Bleh. Now that Java will soon be freed, I'd rather see something akin to Cortado than the continued reliance on proprietary garbage.

      True, but that would really blow their minds. Sometimes progress happens in baby-steps.
    8. Re:Too bad Flash 9 isn't released for linux yet by bubbl07 · · Score: 1

      I've been using nspluginwrapper in my 64-bit firefox (compiled, using gentoo) for months now and, the first release notwithstanding, it has been completely stable. I suggest you give it a shot. It even enables your current 32-bit plugins for you on install (at least on gentoo)!

    9. Re:Too bad Flash 9 isn't released for linux yet by jazir1979 · · Score: 1


      i believe it autodects your OS based on your user agent, you insensitive anonymous coward. why are you in windows??

      --
      What's your GCNSEQNO?
    10. Re:Too bad Flash 9 isn't released for linux yet by Wonko+the+Sane · · Score: 1

      So close, and yet so far:

        * Auto installing 32bit plugins...
      *** NSPlugin Viewer *** WARNING: Flash Player 9 beta 1 detected and rejected
      *** NSPlugin Viewer *** WARNING: Flash Player 9 beta 1 detected and rejected

      This is an awesome program nonetheless.

    11. Re:Too bad Flash 9 isn't released for linux yet by Wonko+the+Sane · · Score: 4, Funny
      i believe it autodects your OS based on your user agent, you insensitive anonymous coward. why are you in windows??

      Maybe he uses the user agent switcher to work around broken websites, you insensitive... logged in user
    12. Re:Too bad Flash 9 isn't released for linux yet by EzInKy · · Score: 1

      I just tested it out on my amd64 system using the nspluginwrapper and it seems to work fine. I didn't use the installer-script though, just untarred and copied libflashplayer.so and flashplayer.xpt to /opt/netscape/plugins.

      --
      Time is what keeps everything from happening all at once.
    13. Re:Too bad Flash 9 isn't released for linux yet by physicsnick · · Score: 2, Informative

      The CVS version of Gnash has started getting video playback support; it's only a matter of time before it has full support for YouTube, Google Video, etc. Once this happens, we can happily accept Flash video in the open-source desktop.

      On a somewhat related note, hopefully by August the nouveau project will deliver an open source 3D driver for NVidia cards; between nouveau and Gnash, I'll soon be able to completely eliminate binary blobs on this machine. Here's hoping it happens sooner rather than later :D

    14. Re:Too bad Flash 9 isn't released for linux yet by zsau · · Score: 1

      By the way, just lest anyone thing Nouveau and Gnash are the sort of thing only "RMS-wannabe free software fanbois" would want, us people using Linux on PPC (and we count Torvalds among our ranks!) have no binaries blobs available from NVidia and no binary flash players available from Adobe. Nouveau and Gnash are absolutely essential for us to be able to keep up.

      --
      Look out!
    15. Re:Too bad Flash 9 isn't released for linux yet by Anonymous Coward · · Score: 0

      He said that freedom has practical advantages, burn the open source heretic!

    16. Re:Too bad Flash 9 isn't released for linux yet by Ash-Fox · · Score: 1
      (Un)fortunately, Flash format is better than other popular video streaming formats like WMV
      No it isn't, I can play WMV9 media just fine on Linux machine (using VLC), without the need to have windows dlls, or other non-sense.
      So I guess it is better to choose the lesser of two evils here.
      Flash isn't a real video format and usually to compensate for the larger file sizes, they reduce the video quality really badly.
      --
      Change is certain; progress is not obligatory.
    17. Re:Too bad Flash 9 isn't released for linux yet by jsoderba · · Score: 1
      Flash isn't a real video format
      VP6 and h.263 are as real as any any other codec. An MPEG-4 codec would be nice, admittedly.
      and usually to compensate for the larger file sizes, they reduce the video quality really badly.
      This is not a limitation of the Flash video system, but a choice by webmasters. Why do need high bitrates in an interview, anyway?
    18. Re:Too bad Flash 9 isn't released for linux yet by Ash-Fox · · Score: 1
      VP6 and h.263 are as real as any any other codec. An MPEG-4 codec would be nice, admittedly.
      But flash it self is not in my opinion a reasonable player (I have issues with it under Windows!). I've not been impressed with the options one can use for making videos available under Flash either -- large file sizes.
      This is not a limitation of the Flash video system, but a choice by webmasters. Why do need high bitrates in an interview, anyway?
      To see them clearly.
      --
      Change is certain; progress is not obligatory.
    19. Re:Too bad Flash 9 isn't released for linux yet by h2g2bob · · Score: 1

      There is a reason for using Flash 8 for video - VP6 video support which is much better than the H.263 video in Flash 6.

      Can't get it to work in WINE for some reason though. Perhaps it's my uni proxy.

    20. Re:Too bad Flash 9 isn't released for linux yet by tehcyder · · Score: 1

      They should have done it as a WMV or MOV file, then anyone could have seen it without having to have that horrible proprietary Flash at all.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    21. Re:Too bad Flash 9 isn't released for linux yet by Anonymous Coward · · Score: 0

      Flash Player 9 is now available for Linux. We're still waiting for the authoring app, Flash 9.

  3. Ummmm by aussersterne · · Score: 5, Informative

    Visit the download page from a Linux browser and you can download Flash 9 for Linux now. And P.S. the beta was out for months before this was...

    --
    STOP . AMERICA . NOW
    1. Re:Ummmm by __aaclcg7560 · · Score: 2, Informative

      If it's not working on the Mac, download and install. There's separate versions for the Intel and PPC.

    2. Re:Ummmm by Anonymous Coward · · Score: 0

      For Linux.... on x86. Wow, useful!! Not.
      How about some free as in Freedom software, Adobe? Or at least an Open specification?

    3. Re:Ummmm by FliesLikeABrick · · Score: 1

      I have flash 9 and it still tells me I need 8 and above. I think there's something about Firefox or Linux that is preventing it from detecting my version right. Does anyone have a youtube link?

    4. Re:Ummmm by physicsnick · · Score: 1

      Not only that, but Flash 9 has hit the Ubuntu backports already, probably along with many other distributions. The video played perfectly for me, and I didn't even know I had Flash 9 until I saw the above comment and checked my Flash version.

    5. Re:Ummmm by aussersterne · · Score: 1

      Hmmm, check to see that you actually do have Flash 9 (do the "about:plugins" thing in your URL bar). Barring that... I dunno... ?! It worked for me and I've still got the beta installed, haven't bothered to install the "official release" yet since I've experienced absolutely zero problems with the beta over the months I've had it installed.

      --
      STOP . AMERICA . NOW
    6. Re:Ummmm by FliesLikeABrick · · Score: 1

      I've been using it fine with many other sites. Right clicking on a running flash applet yields the "About Adobe Flash 9" option in the menu.

    7. Re:Ummmm by zsau · · Score: 2, Insightful

      Umm... still doesn't work from PPC/Linux. And considering that's the platform Torvalds develops on, you'd think they could at least release the video in a format he could watch from his own computer. It's not hard to release a video in MPEG format people!

      --
      Look out!
    8. Re:Ummmm by Kjella · · Score: 1

      And P.S. the beta was out for months before this was...

      Yes, it was and I installed it because of how horribly outdated Flash 7 was, and it was pre-alpha quality. If you navigated to another page before the current one was done loading, your browser would freeze 50% of the time with no recourse but to kill it.

      --
      Live today, because you never know what tomorrow brings
    9. Re:Ummmm by Nutria · · Score: 1
      Yes, it was and I installed it because of how horribly outdated Flash 7 was, and it was pre-alpha quality.

      Adobe released multiple beta versions of F9. (That's the beauty of getting it thru your package manager: no need to constantly recheck the Adobe web site...)

      --
      "I don't know, therefore Aliens" Wafflebox1
    10. Re:Ummmm by caluml · · Score: 1

      From the page: Adobe Flash Player Download Center Linux (x86)
      Notice that? Not everyone running Linux uses x86. Now shut up.

    11. Re:Ummmm by xtracto · · Score: 2, Funny

      And considering that's the platform Torvalds develops on, you'd think they could at least release the video in a format he could watch from his own computer

      Duh! Everyone knows Mr. Trovalds develops on a PPC/Linux machine but his home machine is still a Wintel one

      *runs*

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    12. Re:Ummmm by TheSunborn · · Score: 1

      The installer told me
      "ERROR: Your architecture, \'x86_64\', is not supported by the Adobe Flash Player installer."

      What happend to the 64bit flash? I seems to remember that someone said it does exists.

    13. Re:Ummmm by 3vi1 · · Score: 1

      As someone who's been beta-testing v9b2 on Linux, I think that's a horrible idea. The thing is so buggy it crashes the browser every other Shockwave you open, and sound is even harder to get working than in v7 (if you can believe that).

      If you're a beta-type of person who won't mind your browser crashing/hanging frequently, install it and please give Adobe feedback. However, it's definitely not ready for prime-time at this point.

    14. Re:Ummmm by hunterkll · · Score: 1

      Where's my reliable preempt damnit! :D

    15. Re:Ummmm by Thoron · · Score: 1

      Sure, all Linux users love Adobe's proprietary crap.

  4. well by User+956 · · Score: 5, Funny

    Having stable and unstable in parallel: I think it used to be a great model

    It certainly works when dual-booting.

    --
    The theory of relativity doesn't work right in Arkansas.
  5. Video interviews by Anonymous Coward · · Score: 1, Insightful

    I've never bothered to look at a video interview on the net (part often not being able to, part just not liking video on my desktop, part that the moving images distract me from all the multitasking I somehow can do while reading), but if someone could post a transcript of what was said, I'd be sure to read it :)

    1. Re:Video interviews by mollymoo · · Score: 4, Informative
      if someone could post a transcript of what was said, I'd be sure to read it
      There's really no more to it than what's in the /. summary (for a change). Unless you really want to see Linus trying to remember how long the 2.6 kernel has been out and whether they ever had a 4 month gap between releases, you're not missing much.
      --
      Chernobyl 'not a wildlife haven' - BBC News
    2. Re:Video interviews by Anonymous Coward · · Score: 0

      give me a break.

      are you _that_ busy "multitasking" that you can't stop what you are doing for three minutes to watch a video?

      is your "desktop" _that_ broken that it can't even play "moving images" (i like to just call it video, but whatever)?

      whats the big deal with video on your "desktop"?

      its 2007. enjoy the technology we have today.

      geeze...

    3. Re:Video interviews by Anonymous Coward · · Score: 0

      I actually watch it because I love Linus' voice. Mellow and full of love.

  6. What is he saying? by Reverse+Gear · · Score: 1

    I can't watch the video due on that site, but I really am not certain what he is trying to say from the text I can read.

    Does he want to sacrifice stability for innovativeness in kernel 2.7 or does he think that things are going fine the way they are right now with a stable and an unstable kernel?

    1. Re:What is he saying? by Mogster · · Score: 1
      There used to be stable eg 2.4 and unstable e.g 2.5
      Minor changes made to unstable had to be back ported to stable and it was painful to do that as well as develop the unstable version.

      He is now saying that they

      have been able to do fairly invasive things even while not actually destabilizing the kernel ie the changes can be made to the current version without having to backport.

      Unless there is a very major change to be made which will break the current version they will continue with just the one version.
      --
      ACK NAK RST
    2. Re:What is he saying? by harkabeeparolyn · · Score: 2, Insightful

      In other words, instead of doing things the right way, they are going to start taking shortcuts until things get bad again, and then, chastened, they'll go back to doing what they never should have stopped doing to begin with. Laziness, in other words.

    3. Re:What is he saying? by Reverse+Gear · · Score: 1

      Thanks, I had already forgotten the era of stable in even numbers and ubstable version in uneven numbers, I guess that just shows that I have already gotten used to only stable versions existing, not that I ever really have been working a lot with the uneven numbered kernels.

      Maybe Linus has to big a workload on his shoulders? Seems he would rather stay with making and has plenty to do with keeping the stable version of the kernel stable, maybe he should ask/find someone else do his work on the uneven numbered kernels.
      But then again that leaves behind the question what are we then going to do when 2.7 is starting to move towards being stable with all the experiments done, some of them having turned out successful and the 2.6 kernel having gone in a different direction.

    4. Re:What is he saying? by notamisfit · · Score: 1

      He's traditionally handed off the stable kernels, not the development ones (the "point" releases are handled by Greg KH). Of course, it would be fairly interesting to see what could actually break 2.6 enough to force a 2.7 line.

      --
      Jesus is coming -- look busy!
    5. Re:What is he saying? by gmack · · Score: 1

      Actually getting chastened is why the new dev cycle was invented. A good ways through each dev cycle people would start demanding new features and drivers from the dev kernel. The stable maintainer would then try to backport the new drivers without any of the supporting infrastructure resulting in TWO unstable kernels. The new system of merge small changes then debug has actually made both stable and unstable more reliable.

      For the first time in years I can actually use a stable kernel on production hardware.

  7. Another interview with Linus? by Xenographic · · Score: 3, Funny

    Does it contain anything inflammatory about the GPL v3? If not, I'm not interested. :]

    1. Re:Another interview with Linus? by eldepeche · · Score: 1

      When did he say something inflammatory? Last I read, he said arguments about GPLv3 were going to be a lot of hot air, and they'd die down eventually and everyone would go on with their lives.

    2. Re:Another interview with Linus? by Xenographic · · Score: 1

      While I think it's been over-hyped, Linus has said that he doesn't like the GPL v3, etc. He thinks that the anti-DRM measures are a bad idea and so forth.

      It's gotten to the point where his every mention of the GPL on mailing lists and such gets reported on Slashdot, which is kind of excessive no matter whether you're for or against it.

      For the record, I believe that the GPL v3 is both futile and necessary. Necessary because it will be forced upon us without the need of legal intervention. Futile because they'll cram it down our throats via the law, too.

  8. For anyone who can't watch the video by canyon289 · · Score: 5, Informative

    He's basically saying that no one is really developing a 2.7 kernel because 2.6 is extremely stable even with whatever experimentation they've done. He states that theres been times where they've gone over the 2 month release cycle because of the "big changes" they've done on the kernel. He states that unstable next to stable used to be a good model but it isn't good anymore. He states that if there was a 2.7 kernel they'd have to do all sorts of backporting to get whatever fixes on the 2.7 kernel to work on the 2.6 kernel.

  9. Translation by ClamIAm · · Score: 4, Interesting

    In my opinion, the real reason for no 2.7 is:

    If we open up an unstable branch, I have less testers. --Linus Torvalds

    I'm not saying the 2.6 series is unstable or anything, either. However as I watch Linux's development from the sidelines, I get the impression that most policy decisions Linus makes are designed to make his life easier. See also: Bitkeeper.

    1. Re:Translation by springbox · · Score: 3, Insightful

      It's harder to get a kernel that works nicely if a lot of people end up flocking to another version. This would leave 2.6 in a bad position because fewer people would be finding and reporting bugs, critical or not. One person can only do so much. Linux is very much a community project that needs participants to work well.

    2. Re:Translation by Anonymous Coward · · Score: 1, Informative

      What closing down the Stable/Unstable branches "so everyone becomes a tester" really means is: everyone gets Unstable. This makes life really harrowing if you have an important server running on hardware with buggy drivers in successive kernel releases. You can't backtrack because a previous kernel had some important security updates. You can't go back to kernel 2.4 because it doesn't support this or that. Your only option is to ditch and replace hardware -- which is not always a practical option.

      Linus certainly is a smart guy, but, this particular decision has been extremely annoying and frustrating.

    3. Re:Translation by Tony+Hoyle · · Score: 1

      I've been on projects where that's a temptation but it's a shame Linus has fallen for it.

      Yes you have less testers on one or other of the branches (mostly people stick to unstable) but if you merge them then you essentially force everyone onto the unstable branch and lose a lot of credibility with those that like to stick to stable releases.

      In my own case I haven't upgraded a linux kernel since this policy change because my servers are too important to risk bringing in unstable code.

    4. Re:Translation by hey! · · Score: 1

      I'm not saying the 2.6 series is unstable or anything, either. However as I watch Linux's development from the sidelines, I get the impression that most policy decisions Linus makes are designed to make his life easier. See also: Bitkeeper.


      What is seldom appreciated about Larry Wall's famous "Laziness, impatience and hubris" is how all three qualities are needed to keep each other in check. Laziness -- or at least an aversion to unnecessary work, is critical to moderating unrealistic goals for functionality and schedule. It's hard enough creating good software, without creating organizational problems for yourself.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    5. Re:Translation by gmack · · Score: 1

      As opposed to the old way where the "stable" kernel has drivers that crash the system? Try the percraid drivers on 2.4.30 sometime.

    6. Re:Translation by Dan+Ost · · Score: 1

      I believe the reasoning went something like this: people who want to stick with stable releases will use the kernel prepared by their distro. Anyone willing to build the kernel on their own is knowledgeable enough to deal with potentially unstable upgrades.

      Seriously, how often do you update the kernel on a production machine?

      --

      *sigh* back to work...
    7. Re:Translation by iabervon · · Score: 1

      The problem with your approach is that most of the bugs that last for more than a development cycle and are in 2.6.19.y at this point are very old bugs, from 2.6.0 if not before. If you're using 2.6.8, for example, you may get file corruption for Berkeley DB. The incorrect behavior was introduced in the 2.5 series, made to trigger frequently with a recent (correct) patch, and then fixed. When this was publicized, people started mentioning that they'd been getting corruption that fits the symptoms for years, and had assumed it was application bugs. Before too long, the mainline is going to switch to new IDE code, at which point any bugs remaining in the old IDE code will probably never get fixed (and the current IDE code is known to be irreparably flaky in the case of disk errors, which is one reason it's being replaced).

      If you look at kernel releases in terms of the expected number of significant bugs in a release, 2.6.19.2 is probably the best kernel available.

      The kernels to avoid are 2.6.x (3-digit) ones; they contain known bugs for which the correct fix in terms of long-term maintainability and clean code is too risky or intrusive to apply late in the release cycle. These bugs are left in 2.6.x and fixed in a way that's obviously right but not clean in 2.6.x.1 and in the long-term viable way in 2.6.x+1-git1. Personally, I think that Linus should turn over the 2.6.x version numbers to the stable team, and have his final release be 2.6.20-rcmax, with 2.6.20 (stable team) and 2.6.21-git1 (him) forking at that point. This would then permit the stable team to be more relaxed about their first patch in a series (because the kernel they're fixing isn't an all-digit, stable-looking version) and they can make sure that all of the known issues are fixed before going into the regime where fixes need to be released quickly because they affect a kernel production users are encouraged to use.

      (Of course, 2.4.x was really bad in terms of stability; vendor 2.4.x kernels contained many backports of important features from 2.5/2.6, and these backports were never seen by the original developers and untested by the community outside of that particular distro. And the original developers generally wrote those features expecting that they'd be used in the context of 2.6, so there's no telling what assumptions they made.)

    8. Re:Translation by Crispy+Critters · · Score: 1
      What closing down the Stable/Unstable branches "so everyone becomes a tester" really means is: everyone gets Unstable.
      Hardly.

      First, anyone running "an important server" on hardware that doesn't have a history of stable support is incompetent.

      Second, anyone wanting a thoroughly tested kernel (with security patches backported) should be running one from a commercial distribution. That is what they are for.

      It is ludicrous to say "everyone becomes a tester." It is reasonable to say, "everyone who downloads and runs the newest kernel from kernel.org the first day it is released becomes a tester." That has always been true even for the stable branches anyway.

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

      First, anyone running "an important server" on hardware that doesn't have a history of stable support is incompetent.

      Off your high-horse, champ. Various drivers get broken and unbroken. What may have had stable support for years may yet be broken and left broken if the current developers don't happen to have hardware to hand.

      Second, anyone wanting a thoroughly tested kernel (with security patches backported) should be running one from a commercial distribution. That is what they are for.

      So you're essentially saying: "Yes, people need a Stable tree but Linus has palmed that responsibility off to commercial interests. Trust those businesses. If you don't like it, lump it." Gee, thanks.

      From what I've seen, the only reason people use commercial distributions is if their Management decides needs paid technical support or someone they can officially blame if things go wrong. On a quality basis, the commercial distros are almost always quite inferior.

      It is ludicrous to say "everyone becomes a tester." It is reasonable to say, "everyone who downloads and runs the newest kernel from kernel.org the first day it is released becomes a tester." That has always been true even for the stable branches anyway.

      Doesn't match my experience. Kernel 2.5 was where things got broken and unbroken. Kernel 2.4 was a much more stable tree.

  10. Corporate development OWNS the 2.6 kernel by poopie · · Score: 3, Insightful

    The resiliency of the 2.6 kernel is most certainly due to corporate involvement in the development of and support for Linux. Companies can't design, build, test, and support product for a moving target.

    If anyone wanted to seriously break the Linux kernel ABI, I don't think corporate interests or major distros would support it or follow.

    OSes or platforms seem to change rapidly up until the point they reach a critical mass - at which point, the next ABI change is cause for general revolt. After that, $ENTITY learns their lesson and vows to never significantly break backwards compatibility again.

    1. Re:Corporate development OWNS the 2.6 kernel by Anonymous Coward · · Score: 2, Informative

      WTF are you talking about? The kernel ABI gets "broken" practically every version. It's a bit wacky if you ask me. Make a good design and stick with it guys.

    2. Re:Corporate development OWNS the 2.6 kernel by bfields · · Score: 4, Informative
      If anyone wanted to seriously break the Linux kernel ABI, I don't think corporate interests or major distros would support it or follow.

      The ABI rules haven't changed at all: the user-kernel ABI (system-call interface) is supposed to be backwards compatible indefinitely; the internal ABI (e.g. for drivers) changes without warning whenever it's convenient.

      What's changed is the release cycle--we no longer have this odd-numbered fork where the kernel's half-broken for years at a time.... Which is a good thing.

    3. Re:Corporate development OWNS the 2.6 kernel by notamisfit · · Score: 1

      Or they could do the MS approach and end up with 5 or 6 "stable" ABI's because nobody wanted to break the first one to fix it...

      --
      Jesus is coming -- look busy!
    4. Re:Corporate development OWNS the 2.6 kernel by Anonymous Coward · · Score: 0

      the internal ABI [...] changes without warning whenever it's inconvenient.

      There, fixed for you.

    5. Re:Corporate development OWNS the 2.6 kernel by oliverthered · · Score: 1

      convenient is an odd choice of words, convenient for who? I don't think it's the end users, driver developers or distributions.

      --
      thank God the internet isn't a human right.
    6. Re:Corporate development OWNS the 2.6 kernel by BobNET · · Score: 1
      What's changed is the release cycle--we no longer have this odd-numbered fork where the kernel's half-broken for years at a time.

      Yeah, now there's an even-numbered fork where the kernel's half-broken for years at a time...

  11. Resilience? by SuperBanana · · Score: 5, Insightful

    explaining why the unexpected resilience of kernel version 2.6 has delayed the move to 2.7.

    Uh...resilience?

    2.6 releases have "shipped" numerous times with some serious bugs, probably because Linus and company have let lots of people slip major new features into the 2.6 kernel, when it's supposed to be stable. 2.6 kernels regularly make it SEVERAL "point" releases into each point release:

    • 2.6.19.2
    • 2.6.18.6
    • 2.6.17.14 (!)
    • 2.6.16.37 (thirty seven releases. From 3/20/06 to 12/28/06. That's one release, on average, once a week.)
    • 2.6.15.7

    Go and look at the timestamps on 'em on ftp.kernel.org. Some of the sub-versions are just a few days apart. How the hell are end-users supposed to know when the kernel is ACTUALLY useable, if there are THIRTY SEVEN bug-fix releases?

    One of the more amazing bugs involved a bug in md that would hose raid partitions, and I assure you, it was not the only serious filesystem bug. I lost a reiserfs partition thanks to a half-baked 2.6 release.

    1. Re:Resilience? by Anonymous Coward · · Score: 5, Informative

      The point releases (or .y releases as they are sometimes called), are a new feature of the 2.6.x release cycle that's intended to get fixes in the hands of users faster. These are always small changes, usually only a handful of line changes in the diff.

      The 2.6.16 kernel is a special case. One of the core kernel devs decided to try an experiment to maintain a kernel release for an extended period of time. He continues to provide small fixes at a very regular rate without porting in the newer features of the more current kernel releases. This has only happened for 2.6.16 and there are no plans that I know of to offer extended maintenance on any other kernel release.

    2. Re:Resilience? by notamisfit · · Score: 5, Insightful

      In the interests of fairness, about 20 or so of those 37 bugfix releases were done after 2.6.17 was released as stable (2.6.16 is still being maintained as a "super-stable" type kernel). Bugfix releases pretty much seem to be a non-issue, considering that most people are going to be using the kernel provided with the distribution, as opposed to a vanilla one.

      --
      Jesus is coming -- look busy!
    3. Re:Resilience? by MadnessASAP · · Score: 0

      I think maybe you need to be reminded that the 2.6 kernel is still the development kernel. That means that it is at times unstable and you SHOULD NOT be running important data on it, that's the job of the 2.4 stable kernel.

      --
      I may agree with what you say, but I will defend to the death your right to face the consequences of saying it.
    4. Re:Resilience? by notamisfit · · Score: 1

      Maybe a few years ago. 2.4 only gets the odd bugfix and has shit support for most modern hardware (do they even have x86_64?).

      --
      Jesus is coming -- look busy!
    5. Re:Resilience? by MadnessASAP · · Score: 1

      I'm pretty sure it does, at least I remember installing a x86_64 2.4 kernel at some point in the misty pasts.

      --
      I may agree with what you say, but I will defend to the death your right to face the consequences of saying it.
    6. Re:Resilience? by bfields · · Score: 1
      Go and look at the timestamps on 'em on ftp.kernel.org. Some of the sub-versions are just a few days apart. How the hell are end-users supposed to know when the kernel is ACTUALLY useable, if there are THIRTY SEVEN bug-fix releases?

      They release those pretty frequently; each often consists of very few patches. But the kernel does have tons of bugs--it's a complicated piece of software.

      That doesn't mean any one user is likely to hit any of them--most are in drivers, most triggered only by particular workloads. I run almost every -rc and release kernel, and that doesn't get me in trouble.

      One of the more amazing bugs involved a bug in md that would hose raid partitions, and I assure you, it was not the only serious filesystem bug. I lost a reiserfs partition thanks to a half-baked 2.6 release.

      Sorry to hear that. But 2.4, 2.2, 2.0,... weren't bug-free either.

      It would be interesting to know whether the current development cycle is more or less bug-prone, but I don't know how we'd figure that out; one person's experience isn't enough, since bugs are rare and highly dependent on particular hardware configurations and workloads. Total number of bugs reported or fixed is probably determined less by inherent bugginess than by size of the user community (hence chance of someone somewhere hitting a particular case), variety of hardware supported, and size of developer community--all of which have increased over time.

      The current system has the advantage that new features are continually released and tested, so developers are forced more than ever to figure out how to break down radical changes into small, incremental, testable steps. With the long odd-numbered development kernels something could be broken for a lot longer before anyone noticed....

    7. Re:Resilience? by fimbulvetr · · Score: 1

      We're still waiting for your kernel, since you apparently can do so much better. This is just peanuts to you, I suppose.

    8. Re:Resilience? by Anonymous Coward · · Score: 1, Interesting

      On the other hand, try maintaining a module that actually does something useful and works on the latest 10 releases of 2.6 kernel. It's freakin impossible. They change so much shit just on a whim you end up with a big mess -- or your own little API abstraction, which itself is a smaller, but still big mess.

    9. Re:Resilience? by mcrbids · · Score: 3, Insightful

      Go and look at the timestamps on 'em on ftp.kernel.org. Some of the sub-versions are just a few days apart. How the hell are end-users supposed to know when the kernel is ACTUALLY useable, if there are THIRTY SEVEN bug-fix releases?

      The people that go to kernel.org to choose a kernel to download and compile hardly qualify for what most people will call a "user".

      What Linus is calling "unexpected stability" is probably due to the distros intermediating between the kernel devs and the actual users. To put it another way, what's really happened is that the "stable" kernel is now being maintained by the likes of RedHat and Debian, while the "unstable" kernel is what you find at kernel.org.

      We'll see how this plays out - but for the real world, this leaves Linus doing what he does best - develop and oversee cool developments - while the more rank-and-file organizations lead by the distros intermediate for the end users.

      I've been using CentOS and Fedora Core, it's been at least 5 or 6 years since I felt the need to go to kernel.org!

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    10. Re:Resilience? by mcrbids · · Score: 0, Offtopic

      Don't you hate it when you forget to close a tag?

      Arghghg!

      (Cue three lame comments about "Preview"...)

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    11. Re:Resilience? by JebusIsLord · · Score: 1

      I remember 2.4 was a disaster, actually... the whole VM system got turfed and replaced somewhere around 2.4.8 because it was broken by design, and something drastic had to be done.

      This is just from memory, someone with a better memory could probably be more specific. But anyhow, the 2.6 releases have been pretty smooth.

      --
      Jeremy
    12. Re:Resilience? by Anonymous Coward · · Score: 0, Troll

      Yunno, if my doctor fucks up my treatment, it doesn't matter that he still knows more about medicine than I do -- he's still a quack. The kernel is being fucked up because Linus would prefer to hack and not plan.

    13. Re:Resilience? by arose · · Score: 1

      And that's why 2.6 is the way it is, most people just don't seem to want a stable as in "Debian stable" kernel, they want a "stable as in runs well, but gets new drivers and features" kernel.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    14. Re:Resilience? by XMode · · Score: 1

      The point releases (or .y releases as they are sometimes called), are a new feature of the 2.6.x release cycle that's intended to get fixes in the hands of users faster. These are always small changes, usually only a handful of line changes in the diff.

      The 2.6.16 kernel is a special case. One of the core kernel devs decided to try an experiment


      Woah.. wait.. hold it right there.. Experiment.. Wasn't this the point of a stable and dev branch? So all the experimenting could go on in the dev branch and those of us that just want a kernel that, i don't know, doesn't corrupt our file system at random, can stay in stable?

    15. Re:Resilience? by tetromino · · Score: 1

      Indeed. At this point, I have basically decided never to install a 2.6.x.y kernel until y >= 2. Losing data ain't worth it.

    16. Re:Resilience? by Arimus · · Score: 4, Interesting

      The use of the word experiment is a bad choice of words.... the 2.6.16.y releases are all stable releases but instead of batching up fixes and implementing them maybe weeks or months after discovery 2.6.16 was used to test the idea of rapid fixing of the kernel. The experiment was in the process of kernel fixes rather than experimental code.

      --
      --- Users are like bacteria -> Each one causing a thousand tiny crises until the host finally gives up and dies.
    17. Re:Resilience? by Anonymous Coward · · Score: 0

      Woah.. wait.. hold it right there.. Experiment.. Wasn't this the point of a stable and dev branch? So all the experimenting could go on in the dev branch and those of us that just want a kernel that, i don't know, doesn't corrupt our file system at random, can stay in stable?

      So, you want experiments with making a stable kernel even more stable, by backporting bugfixes without the new features (which may introduce new bugs) done in an unstable branch?

    18. Re:Resilience? by Ed+Avis · · Score: 1
      How the hell are end-users supposed to know when the kernel is ACTUALLY useable
      When your vendor ships it to you through 'yum update'...
      --
      -- Ed Avis ed@membled.com
    19. Re:Resilience? by octopus72 · · Score: 1

      Good thing is that those stabilised releases are much more similar to development versions than when 2.4 and 2.5 were state of art, so most fixes can easily be comitted to latest upstream version (or backported from it).

      Turning experimental version of such a big project into a stable one is a long and painful job. It's order of magintude easier for Linus and kernel team to wait for a patchset to stabilise out of main tree until it's refactored, tested and good enough to go in. I believe both users and developers are happier with this (and improvements get a fair review, aren't just bumped in).

    20. Re:Resilience? by HvitRavn · · Score: 1

      Since the kernel development is decentralized, there is seemingly no point in branching (keeping stable branches) since there is already a lot of branches at each and every developer. But I don't get this - why can't Linus maintain a definite "stable" branch/tree and keep branching (or what to call it) while upping the minor revision for the big changes? Why is it so important to keep only one (un)stable branch and adding the big stuff into it?

    21. Re:Resilience? by HotBBQ · · Score: 1

      Pfft, your distribution comes with a kernel? =)

    22. Re:Resilience? by Vintermann · · Score: 1

      I wondered why you became so insistent all of a sudden.

      --
      xkcd is not in the sudoers file. This incident will be reported.
    23. Re:Resilience? by MikeBabcock · · Score: 1

      You obviously haven't actually read how the 2.6 kernels are maintained. The kernels on kernel.org mirrors are not for end users, but for developers and distribution maintainers. If you want to work with one yourself on a development machine, that's great. Otherwise, you should be using the packaged kernels from your distributor.

      That's not me talking, that's a paraphrase of what was said when 2.6 was continued in this way.

      --
      - Michael T. Babcock (Yes, I blog)
    24. Re:Resilience? by Dan+Ost · · Score: 1

      My approach is to not upgrade until the 'y' in 2.6.x.y hasn't been incremented for a week or two.

      Never had any problems (but I don't have any strange needs either...that probably has more to do with the stability I've experienced with 2.6).

      --

      *sigh* back to work...
    25. Re:Resilience? by swillden · · Score: 1

      On the other hand, try maintaining a module that actually does something useful and works on the latest 10 releases of 2.6 kernel.

      That's why you should focus on getting your module in the kernel tree. Then each version of the kernel will contain a version of your module that is compatible, and as more internal API changes occur, the updates to your module will often be made for you.

      Of course, that only works for GPL modules. If you don't want to GPL your module, it's going to be painful.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    26. Re:Resilience? by cortana · · Score: 1

      Why wouldn't you just get the module included upstream?

    27. Re:Resilience? by cortana · · Score: 1

      I think you should have stayed with your distribution-supplied kernels...

  12. Why backport? by Colin+Smith · · Score: 1

    I thought the odd numbers were "run with it" kernels. Leave the even number kernels static for bugfixing only.

    How about 2.9 then. Blue sky how would you design an OS for all the cheap commodity hardware around.

    --
    Deleted
    1. Re:Why backport? by Zerathdune · · Score: 4, Informative

      That scheme ended when 2.6 came out. The new system consists of 3 or 4 numbers formatted as:

      a.b.c
      or
      a.b.c.d

      a changes only when there is a massive restructuring of the kernel
      b changes when there are large sweeping changes, but not of quite the same order as a. (linus, in the interview, says they'll do a 2.7 when and if they need to make changes large enough that they will be breaking everything.)
      c changes when new features and/or drivers are added
      d changes for small bug fixes and security patches. after a new c release the d number is ommitted when the c number has just changed.

      --
      No single raindrop believes that it is responsible for the storm.
    2. Re:Why backport? by Frank+T.+Lofaro+Jr. · · Score: 2, Interesting

      Very good.

      I'd add an (e) (Oracle has 5 :)

      Seriously (d) would be for bug fixes/security patches in general, e would be for ones that are expected to almost certainly not break anything.

      e level upgrades: should be nearly 100% safe
      d: should be safe, necessary fixes that could break things (e.g. fix a security hole but certain programs could have issues). NO API CHANGES or ADDITIONS!
      c: new features. Usually safe, but not for mission critical servers. NO API drops/deprecations.
      b: Major upgrade. System tools may need upgrading, app breakage can occur but not extreme. old APIs deprecated.
      a: Extreme upgrade. Only twice so far. Whole system replacement can be expected, old APIs dropped

      --
      Just because it CAN be done, doesn't mean it should!
  13. don't shit on my head please by towsonu2003 · · Score: 0, Redundant
    You'll need Macromedia Flash Player 8 or above in order to view some of our content. Download now!
    and I'm using the interviewee's kernel

    apparently, zdnet isn't ready for desktop yet

    :)

  14. Use beta 2 by ChunderDownunder · · Score: 1

    The release notes suggest that beta 1 doesn't work but beta 2 does!

  15. What the hell are you talking about? by Browzer · · Score: 1

    "...2.6 kernel is still the development kernel...."

  16. bad website by towsonu2003 · · Score: 4, Insightful

    can anyone post this "fragmented" and unaccessible interview video to youtube or google video as one or two big file(s)?

    1. Re:bad website by towsonu2003 · · Score: 1

      nevermind, I was in a stupid loop because I was too stupid to see that the website gets you into a loop in order to watch 2 short videos (. stupid me :)

  17. Virtue of laziness by Anonymous Coward · · Score: 0

    I wonder how far Linus would have gotten if he had found so many ways to free up his time.

  18. Re:9 sucks as bad as any other version by smclean · · Score: 1
    The main thing that sets the flash player apart from those other audio-producing applications you listed is that the flash player uses OSS. I'd assume you have software audio mixing, and my guess is that flash player doesn't know how to "play nice" with the software mixing solution you use, be it arts, alsa's dmix plugin (which new version of alsa enable by default for some cards), or esd.

    Not that I'm a fan of Adobe's flash player. I still open a 32 bit browser whenever I absolutely need flash, and use a 64 bit browser the rest of the time. One of the main reasons I'm still using my old SoundBlaster Live! is because it has hardware mixing, and gets around problems like what it sounds you are experiencing.

    --

    "'Yrch!' said Legolas, falling into his own tongue."

  19. Resilience is futile! by Anonymous Coward · · Score: 0

    had to say it

  20. Unfriendly? by Profane+MuthaFucka · · Score: 0, Troll

    Oh come on, that's harsh. He's only accused of killing his wife.

    --
    Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
  21. Re:9 sucks as bad as any other version by flight_master · · Score: 3, Informative

    It's Easy, I'm assuming you're using Firefox, so fire up Nano and open the file "/etc/firefox/firefoxrc" (as root)
    Add this line: FIREFOX_DSP="aoss" (remove FIREFOX_DSP=)
    Install the alsa-oss package.
    Restart FF, and you are playing sound!

    --
    "Free software" is a matter of liberty, not price.
  22. So what will cause 2.8 or 3.0? by wellingj · · Score: 1

    So does any one wonder if there is ever going to be a 2.8 or a 3.0 Kernel?
    This is just speculation but...
    I'm guessing as soon as Ingo Molnar and friends get the real time premption patch fully
    merged into the mainline we'll see a new Kernel release (not a 2.6.x+1)

  23. Re:9 sucks as bad as any other version by 10Ghz · · Score: 5, Insightful

    It's Easy, I'm assuming you're using Firefox, so fire up Nano and open the file "/etc/firefox/firefoxrc" (as root)
    Add this line: FIREFOX_DSP="aoss" (remove FIREFOX_DSP=)
    Install the alsa-oss package.
    Restart FF, and you are playing sound! Um, I'm not sure what planet you are living on, but that's not "easy". It's tedious and frustrating.
    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  24. Seconded by empaler · · Score: 1

    There's really no more to it than what's in the /. summary (for a change). Unless you really want to see Linus trying to remember how long the 2.6 kernel has been out and whether they ever had a 4 month gap between releases, you're not missing much. True, there's not even the three minutes of video promised in the article. at 1:56 it you could say that it's closer to 3 than to 0. Which is a pretty bad argument.
    1. Re:Seconded by Nutria · · Score: 1
      True, there's not even the three minutes of video promised in the article. at 1:56 it you could say that it's closer to 3 than to 0. Which is a pretty bad argument.

      There are 2 videos, the 2 minute video and a 3 minute video.

      In the text of the article, there's a link to the article containing the 3 minute video.

      --
      "I don't know, therefore Aliens" Wafflebox1
  25. Re:9 sucks as bad as any other version by KiloByte · · Score: 1
    The first half of your post -- these bozos want to do everything their way and won't let us fix it. So no wonders sound doesn't work for you when it works with everything else.

    The second half -- hell yeah.

    Flash is the only program I can truthfully say I hope is *never* open sourced. I guarantee you it has too many cooties for "safe source" viewing.
    Too bad, Gnash is already out there.
    --
    The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
  26. Ow... my sides hurt from laughing! by Builder · · Score: 1

    We have been able to do fairly invasive things even while not actually destabilizing the kernel...

    Oh gods, my sides hurt sooo much.

  27. Beowulf by jlebrech · · Score: 0
    Can't they just implement some kind of automatic load balancing system from the kernel,

    and make it work really easy, so if you have 10 linux workstations for example they'll piss all over 10 boxes with Vista!!! And without configuration just have them on the same subnet and they'll do that automatically.

    Then call it kernel 2.7

  28. Re:9 sucks as bad as any other version by Anonymous Coward · · Score: 0

    Neither do I have a firefoxrc anywhere in my system nor does about:config show something even remotely similar to FIREFOX_DSP

    Besides, flash is only for those folks, that run some kind of intel like CPU.

  29. Re:9 sucks as bad as any other version by WhodoVoodoo · · Score: 1

    Changing one line in a text file, then typing "apt-get install alsa-oss" is at least as simple as operating a coffee machine.

  30. Re:9 sucks as bad as any other version by Anonymous Coward · · Score: 0

    Address your complaints to Adobe for only supporting OSS

  31. Laziness, impatience and hubris by Per+Abrahamsen · · Score: 1

    Laziness is one of three virtues of the good programmer, according to Larry Wall. And I believe he is on to something.

  32. Well by Anonymous Coward · · Score: 0

    It's still better than Flash 7. During the few times the audio actually worked at all it was horribly out of sync. And then if you're actually using flash (ie, watching a video) there would usually be about a 70% chance of it crashing the browser (Firefox really needs to sandbox plugins, a plugin should not crash the browser or pose a security risk...).

    I've been using the Flash 9 beta since the first release. So far, no crashes. No loss in audio. And synchronized A/V. I don't know why the GP has audio problems, must be an issue with his setup (I'm using Ubuntu Edgy and their Firefox). I still use Flashblock, though, due to fscking Flash ads.

  33. Wow by joshier · · Score: 0

    Did anyone see the star at 0:58, he is clearly the son of Christ.

    Either that or he can see 'microsft users... All The Time!'

  34. Re:9 sucks as bad as any other version by somersault · · Score: 1

    I dunno, sounds pretty easy to me.. inconvenient maybe, but hardly tedious and frustrating compared to say trying to get games working properly on WINE. Seems like a stroll in the park

    --
    which is totally what she said
  35. Re:9 sucks as bad as any other version by multi+io · · Score: 1

    Flash 9 for Linux uses Alsa (and only Alsa, no OSS anymore), and it "plays nice" with other Alsa-using sound apps just fine.

  36. Re:9 sucks as bad as any other version by moro_666 · · Score: 1

    not on my machine. the video frezes at 3/4 of the playthru and the sound is gone. to make it more interesting the whole browser has to be restarted to get anything in flash to work again. i'll wait for the next version, perhaps in that it will work. tested with both fx 1.5 and 2.0, none of them wanted to work properly with it, kernel is 2.6.18 no other problem with alsa sound anywhere else, go figure.

    and some smartkickass javascript checks still don't realize that you have version 9 which is greater than 8, and go on complaining and redirect you somewhere else.

    --

    I'd tell you the chances of this story being a dupe, but you wouldn't like it.
  37. Re:9 sucks as bad as any other version by BecomingLumberg · · Score: 1

    I have a french press, which is much easier than the instructions. I don't even have buttons, just one plunger.

    --
    If a nation expects to be ignorant and free, in a state of civilization, it expects what never was and never will be.-TJ
  38. Agile kernel development by mixonic · · Score: 1

    Heh, see, even Linus has gone Agile. New-wave 2.0 web developers rejoice! :-)

  39. Re:9 sucks as bad as any other version by just_another_sean · · Score: 2, Insightful

    I take it you've never had to fix anything with regedit either then?

    --
    Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
  40. Re:9 sucks as bad as any other version by 10Ghz · · Score: 2, Insightful

    Changing one line in a text file, then typing "apt-get install alsa-oss" is at least as simple as operating a coffee machine. I don't have to anything like that with any other OS I have used. I don't have to go around installing weird stuff and editing text-files just so I could get frigging sound working in a web-browser.

    And yes, I use Linux (among other OS'es). Have been using it since 1999, and I'm a card-carrying member of a national LUG. But anyone who says that "It's easy, just edit this text file and install these apps and you are all set" is totally, 100% missing the point. Tasks like that are way beyond the capabilities of most users. They just want their systems to work. And if it's so easy to fix the problem, why isn't it fixed by default? Why are tasks like that left to the user to figure out?
    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  41. You Nutty Torval you... by Anonymous Coward · · Score: 0

    Woo Hoo 2.8 here we come.. err ummm.. McFry's anyone?

  42. Re:9 sucks as bad as any other version by 10Ghz · · Score: 1

    I take it you've never had to fix anything with regedit either then? Unfrotunately, I have. But I don't have to go poke around Registry just so I could do something as simple as getting sound working in a web-browser. Things like that should "just work"
    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  43. Re:9 sucks as bad as any other version by Anonymous Coward · · Score: 0

    He's probably from a planet where the OS used on most desktops requires regular tinkering with something arkane called "registry", comparing to that changing plain text files (that either contain helpful coments or are described in program manuals) seems easy.

  44. Re:9 sucks as bad as any other version by The+Dotmeister · · Score: 0

    Tasks like that are way beyond the capabilities of most users. Well yeah...beyond the capabilities of the average Joe that uses Windows and surfing MySpace is his full-time "job"... If you want to use Linux you have to know what to do...well it was like that last time I checked...hmm I think so... Disclaimer: Mac OSX user here, that doesn't mind playing around with config files.
  45. off-topic by mapkinase · · Score: 1

    I am getting ridiculously anti-Linux pro-Windows videoad with this story on /.

    Irony.

    --
    I do not believe in karma. "Funny"=-6. Do good and forbid evil. Yours, Oft-Offtopic Flamebaiting Troll.
  46. Some 2.7 ideas by Anonymous Coward · · Score: 5, Insightful
    I'm a linux user, my company's products depend on it and I've contributed to it. I see a a couple of painful transitions coming though. I haven't seen the kernel quality go down, I'm not sure how people say "2.6 isn't stable" without specific issues they can point to. Overall the code keeps getting better. I say this as a warning, not as a doom and gloom kind of message.

    VFS probably needs to be addressed. Reiserfs4 sort of exposed some of the issues. There are others though. To my knowledge ext2/3 are the only OSes that actually code strcitly against VFS and the other layers. XFS, JFS, Reiserfs, etc.. are all hacked in to it. If you follow the kernel list, you'll see nobody uses JFS and XFS seems to have regular crash reports. Upon using it myself (for 5 years) it has memory leaks, it routinely has trouble with new kernels. There have been regular performance regressions. Now, I don't really care about the filesystem itself that much but it seems fundamentally broken to me that a non-experimental filesystem has such routine problems. Either the API is uses is broken, the filesystem is broken or both. I'm becoming more inclined to think that it's VFS. This creates a circular sort of problem, you don't need VFS if ext2,3,4 are the only filesystems that are really supported, it's not nearly as important as it is treated. Either that or the process of having something included and non-experimental needs to include some kind of support aspect and maybe be rethought. So far as I can tell, IBM isn't really doing much more with JFS and nobody uses it, let's move to remove it (bummer too because it's a quite clean and elegant FS, much better than reiserfs or xfs in terms of code and design quality and cleanness.) There isn't a clean process for removing stuff from the kernel. Reiserfs is a prime example, Reiserfs3 isn't supported, time to move to remove it; it has known bugs and design flaws which are not being addressed. This particular area is more complex also because selinux depends on filesystem support, LVM behaves differently with different filesystems, different filesystems have different and variable tools support.. System filesystems need some work too, what's debugfs? configfs? How is sysfs different than configfs or procfs?

    Filesystems are just an easy to see and expose portion of this problem there are other APIs which have the same issues. We retooled the build system a few years back, it's much better but there are major flaws still. There are drivers which cannot work unless loaded as a module and yet they can be linked in. There are a huge number that depend on other subsystems and you can easily misconfigure them (SATA depends on parts of SCSI. So I can static link some SATA modules in and dynamic link parts of the SCSI system in and the build system won't complain. Worse, if I break it just so, I can actually get it to build cleanly and freak out at runtime) I'm not advocating making it more difficult to hack on the kernel or add new modules to the build but it's fucked if it doens't catch that stuff. Worse, the driver is fucked if it can't be statically linked and if that's an acceptable limitation then it should be an option. (the Fusion series of RAID/SCSI/SAS type drivers is one that suffers from this problem) At the same time the build system is holy, good luck changing that without pissing off half the free world, and I don't even want to think about what would have to happen if it required a change to a .config file to take it to the next level. Part of the beauty of Linux in this regard is that it is remarkably simple to build and get involved with, there really aren't any tricks or anything to building it. This is something else where there needs to be a support component. There are good companies with well supported drivers and there are orphans. I'd rather have modules marked as supported or unsupported than whether or not they are GPL clean or tainted, I'd like to see that

    1. Re:Some 2.7 ideas by AxelTorvalds · · Score: 1

      It is a much more approachable and friendly group during the unstable tree periods.

    2. Re:Some 2.7 ideas by Anonymous Coward · · Score: 0

      For example, the firewire stack is going to be rewritten. More correct would be to say: There is a new* firewire stack being written, and we will see whether it will get into a shape that makes it a viable replacement of the current stack. It's not set in stone yet.

      I would have welcomed an in-place rewrite, component by component. But the contributor of the new stack has valid technical arguments against that approach. This and the problem that there are simply almost no other contributions to the firewire drivers make his approach acceptable to me.

      -- Stefan Richter

      *) It's not entirely new. Some parts are branched developments during Linux 2.4 times; some are duplicated from the current stack. And AFAICT so far, the directions the new stack takes are first and foremost steered by the good and bad experiences made with the current stack over the years, including application programming experience.
    3. Re:Some 2.7 ideas by Anonymous Coward · · Score: 0

      I think his point was that regardless of why or if the firewire stack is rewritten, that's all good but should that go directly into a "stable" kernel tree or an "unstable" one and there is no longer an "unstable" one. What's the process now? I don't know how I feel about getting a new firewire stack dropped on me, I use it for backups, it works right now. I guess it's up to Redhat and Suse when we all get it. Instead of Linus and the guys working on it deciding when to call it stable we let the different distribution vendors decide and I don't think we get consistent results. Maybe that's why so many people think 2.6 is unstable still.

    4. Re:Some 2.7 ideas by Anonymous Coward · · Score: 0

      I think his point was that regardless of why or if the firewire stack is rewritten, that's all good but should that go directly into a "stable" kernel tree or an "unstable" one and there is no longer an "unstable" one. Well, there actually is kind of an "unstable" branch: The -mm patchset. And that's where also the new firewire stack currently lives and evolves. If/ when/ how it will get from there into Linus' tree cannot be determined yet.

      Note, even very local bug fixes that looked like a sure shot occasionally turn out to introduce a new bug or new hardware interoperability problem a few weeks after commit, or worse, weeks after Linus' release or ages later in a distributor's release. The testing of bug fixes in a subsystem development repository and in -mm cannot fully prevent this. Thus the "stable" kernel is always in a certain danger of regressions merely by bug fixes.

      But back to the "rewrite". Sure, it would be nice if a major development step of a subsystem would coincide with a major release step of the overall kernel. But that's just not going to happen: All of the projects have different schedules and...

      What's the process now? ...also partly different processes, due to different position of the subsytems in the software lifecycle, different pools of manpower, different persons, and more factors.

      Linus' processes are quite well known and not rapidly changing (but not entirely frozen either).

      -- Stefan Richter
  47. Re:9 sucks as bad as any other version by just_another_sean · · Score: 1

    Well I use Debian Etch and Ubuntu Dapper and Edgy on several different systems and I've never had a problem with what you are describing. My sound in the browser "Just Works".

    Now I don't doubt that yours is not working, for whatever reason. I guess my point is usually things just work for me using Debian or Ubuntu. Sometimes they don't, rarely these days, but it happens. When things don't work I occassionly have to do something odd or tedious to get it to work again. But this is true of any OS and I've spent at least as long in Windows trying to get something that should have been easy to work and it's not always simple.

    --
    Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
  48. Re:9 sucks as bad as any other version by cortana · · Score: 1

    s/web browser/propritary browser plugin that uses an obsolete/deprecated audio output system/

    Fortunately Flash 9 is now available (at least for i386) and so this particular piece of config-file cargo-culting can by forgotten, and sink back to the depths of the Pit from whence it came.

  49. Summary of interview by Anonymous Coward · · Score: 0

    So to sum up the interview, Lunis says he is still chasing Microsoft's tail lights.

    It's too bad Lunis doesn't throw some of his concern toward worthless efforts like making a useful installer which will work on all distros, or toward making Lunix able to install without manual work... both things the venerable Windows 95 accomplished far better than Lunix does today.

    But hey, Lunix is all about choice, so feel free to choose among one of the zillions of different text editors, and dream about the day all the game creators will realize OpenGL is teh bettar than DirectX.

  50. Re:9 sucks as bad as any other version by Anonymous Coward · · Score: 0

    Works fine in Ubuntu. I'm not sure how they do it but it works out of the box no problems.

    What distro are you using?

  51. Re:9 sucks as bad as any other version by flight_master · · Score: 1

    Actually, I dug this up from Kubuntu Dapper, and the previous one (sorry, I forgot the name of it). It's a fluke that only happens with Intel onboard AC`97 audio chips. (My *other* computer has no issues, just this one with the 865PERL mobo).
    I agree it's a PITA for newbies, but hardly something so hard that it can't be fixed.

    --
    "Free software" is a matter of liberty, not price.
  52. Re:9 sucks as bad as any other version by Frank+T.+Lofaro+Jr. · · Score: 1

    OSS sound is deprecated? So much for ALSA just being an alternative, now it is crammed down our throats.

    ALSA is LINUX specific, OSS is cross platform. We are taking a step back just because the high end audio people want extra features.

    Make it an OSS extension, or just go ahead with the ALSA push and let's make Linux specific APIs and drop any pretense of UNIX/POSIX compatibility.

    --
    Just because it CAN be done, doesn't mean it should!
  53. Re:9 sucks as bad as any other version by cortana · · Score: 2, Informative

    Frankly, in this area, "UNIX/POSIX" compatibility can go fuck itself. Does POSIX even specify audio output interfaces? Did "UNIX" (System V? BSD?) even ever have sound output?

    ALSA is not only desired by high-end audio users. All users want basic features such as the ability for two programs to use the sound card at the same time. ALSA provides this (part of alsa-lib) and OSS does not.

    ALSA is not necessarily Linux-specific. As far as application programs are concerned, ALSA is merely a stable program library (libasound.so.2). Nothing stops you from porting alsa-lib to another platform, or implementing another library with the same interface. If would probably be quite easy to get it working today, by configuring alsa-lib to use the pcm plugin that talks to Pulse Audio server, which can output to OSS or many other sound systems/devices/interfaces.

    Finally, if you bothered to do the most basic research about the i386 GNU/Linux Flash player, you would have found out that it is Adobe's plan to separate out the GNU/Linux-specific parts of the player into a separate library with a stable interface. Anyone (who uses i386) would then be able to implement their own platform-specific replacement and thus get the Flash player running on their platform.

  54. Re:9 sucks as bad as any other version by tknd · · Score: 1
    I take it you've never had to fix anything with regedit either then?

    I believe the point of the post was that the operation was abstract and required extra knowledge, not that there are better/worse alternatives. The point is, you still have to learn/know something. The only way to avoid it is to make it work out of the box. Power users and people interested in stuff like that (geeks) may not care. But for everyone else it's like their car broke down in the middle of the road. They have no way of fixing it other than calling a mechanic or learning more about the car themselves--neither of which they are interested in except that it is the only way to get the car working again.

  55. JFS is used by Anonymous Coward · · Score: 0

    Whilst I liked most of your post, I disagree with you on one point.
    That point is JFS, I use it almost exclusively on my boxen (6 so far) with Gentoo.
    If you take a look at the Gentoo forums (forums.gentoo.org) you will also find other people using it.
    I am sure there are many others besides.

    The rationale behind "there are no posts on the kernel dev list about JFS therefore no one is using it!" is flawed and incorrect.
    There are posts on the kernel dev list - the one about JFS that I can see is: -

    JFS: possible recursive locking detected Tomasz Kvarsin (Tue Jan 09 2007 - 02:33:50 EST)

    Also JFS is in tree, stable and has very few problems.
    When breaking changes are made to the kernel that affect JFS they go and fix it up just like all other in tree modules.
    IBM also is usually very quick with other fixes that are necessary from past kernel patch reports.
    Therefore I would expect not to see many posts about it on the kernel dev list.

    People who are happily using stuff don't generally post to the kernel dev list about it and so it can seem that a piece of functionality is not used when in fact it may be widely used.

    I consider JFS to be the best available file system at the moment if you want stability, reliability, journaling and good performance.

    So lets not remove it otherwise me and possibly many others like me would be very unhappy.

  56. Re:9 sucks as bad as any other version by 10Ghz · · Score: 1

    "I've never had a problem with what you are describing."

    I'm not describing it, others are. My Linux-box has died due to hardware-failure, so this issue does not affect me sinse I don't have a working Linux-installation at all. But the point is that no-one should tell other how "easy" it is to fix a problem, when all you have to do is to edit few text-files and install few apps. First of all, the problem should not exist at all. Second: Editing text-files and installing apps is not "easy" for regural users. It's easy for powerusers, but for that soccer-mom down the street it's too much.

    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  57. Re:9 sucks as bad as any other version by 10Ghz · · Score: 1

    So why don't we just forget this crap about "year of the Linux-desktop" then?

    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  58. Re:9 sucks as bad as any other version by Anonymous Coward · · Score: 0

    So why don't we just forget this crap about "year of the Linux-desktop" then? Feel free, by all means. While you're at it, please stop using "we" when you mean yourself.
  59. Re:9 sucks as bad as any other version by WhodoVoodoo · · Score: 1

    You're totally right on this point, but I [i]still[/i] wouldn't classify editing one line in a text file and then typing one command as "tedious and frustrating".

    I've never claimed it's all happy automagical justworksness, however one diff would remove this insurmountable hurtle and since the GGP or wherever it was seems to be relatively technologically savvy, one bug report to his distribution could fix this for all.

    And yes, I use Linux (among other OS'es). Have been using it since 1999, and I really don't care if my grandma uses it.

  60. Re:9 sucks as bad as any other version by just_another_sean · · Score: 1

    What does "the soccer mom down the street" do when Windows gets spyware? A virus? What if a driver downloaded from Windows Automatic Updates hoses the video card?

    You seem to think that any and all things to do with computers should be easy to fix. Their not always. Fixing the issue with the sound sounded pretty damn easy to me compared to some things I've had to deal with on both Linux and Windows.

    Not to mention your comment about your box dieing from a hardware failure. Hearing that I'm thinking "so this guy put Linux on an old, dieing box and is wondering why it sucked?". Have you tried a modern distro on a modern PC? "Look mom! No config files to edit!"

    --
    Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
  61. Re:9 sucks as bad as any other version by just_another_sean · · Score: 1

    OK sure, I can agree with that. But it seems from reading the post and especially the follow ups that the guy threw Linux on an old box with the expectation that he wouldn't like it.

    To continue your car analogy (love the car analogies!) it's like someone driving a beat up, 89 Nova and wondering why it so hard to keep going. Oh and then blaming Ford for selling him a POS.

    --
    Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
  62. Re:9 sucks as bad as any other version by just_another_sean · · Score: 1

    Er, I mean, blaming Chevy.

    --
    Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal