Slashdot Mirror


2.6.13 Linux Kernel Released

LynuxFre@k writes "Linux Torvalds announced the release of the 2.6.13 Linux kernel. He noted that there was a major change to the x86 PCI code, and that while all bugs from the change were believed to be found during the release candidate phase, it's possible that some devices may have problems. From this release on, it is intended that major changes only be merged into the kernel within two weeks after a major release. The rest of the time will be spent fixing bugs, with the goal of both increasing overall stability and decreasing the amount of time between major releases. Download the latest Linux kernel from a kernel.org mirror."

464 comments

  1. kernel bug fixes by Ritz_Just_Ritz · · Score: 3, Insightful

    "From this release on, it is intended that major changes only be merged into the kernel within two weeks after a major release. The rest of the time will be spent fixing bugs, with the goal of both increasing overall stability and decreasing the amount of time between major releases."

    I wish Linus would arrive at a policy and just stick with it instead of all these gyrations of "we'll use this method from now on...no wait...we'll use this one from now on...and by the way I want everyone to switch revision control systems now...oh wait...sigh.

    1. Re:kernel bug fixes by red_dragon · · Score: 2, Insightful

      I wish Linus would just stick with fixing bugs in stable releases and leave major changes to development versions, but I guess that'd take finding him a new toy to play with.

      --
      In Soviet Russia, Jesus asks: "What Would You Do?"
    2. Re:kernel bug fixes by Skye16 · · Score: 3, Insightful

      As long as things aren't changing bimonthly, I don't see a horrendous problem. There's much to be said for being flexible.

      Then again, if it happens too often, more time is spent switching back and forth between the new "great" ideas than doing actual work.

    3. Re:kernel bug fixes by Knome_fan · · Score: 5, Insightful

      I can't really understand why so many people have a problem with the current policy and the policy changes.

      What exactly is wrong with refining the development process?

    4. Re:kernel bug fixes by Neo-Rio-101 · · Score: 1

      That just sounds like my company. The minute we get used to filling out reports a certain way, the management come up with another *brilliant* excel sheet format and we have to relearn how to fill out reports all over again.

      --
      READY.
      PRINT ""+-0
    5. Re:kernel bug fixes by 10Ghz · · Score: 5, Insightful

      It's not THAT bad. Revision control system has been changed twice during the lifetime of the kernel. Developement-method has been changed once, and now that method is simply being tweaked a bit. And what do you care how they develop the kernel? Are you are kernel-developer?

      Or how would you like them to do it? "We will do things this way, and by god, we will do it like this untill the end of time! Even if better ways of doing this comes along, we will not change our ways!"

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    6. Re:kernel bug fixes by 10Ghz · · Score: 1

      Developement-version = 2.6.x and 2-6.x-mmz

      Stable-version: 2.6.x.y and vendor-kernels

      Maybe things were named differently in the past. But what matters is they way they are named today.

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    7. Re:kernel bug fixes by Anonymous Coward · · Score: 2, Insightful

      Well I'm fairly sure Linus has a better handle on all the issues than you do.

      But... gee, if it bothers you that much you can point Andrew Morton to your kernel tree, or send him your patches. He does a pretty good job of ensuring things don't clash, and queues it up and merges with Linus, getting initial bug testing and review along the way.

    8. Re:kernel bug fixes by erlenic · · Score: 1

      Why don't you put it in Access? Then you only have to change the report template, and you never have to relearn the data entry. If the boss insists on seeing it in Excel ... I feel sorry for you ... er, I mean, Access can export it to Excel. You could even do it in a real database solution, like SQL Server or Postgres, it will just take a little longer.

    9. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      What exactly is wrong with refining the development process?

      Hmm, let's see. Doing it too often so that noone actually knows what process is in effect currently?

      Linux isn't the center of the world. Look at the BSDs. A release is a release I can use. I don't have to lookup what development "process" the top coder monkey sucked out of his ass this week.

    10. Re:kernel bug fixes by Anonymous Coward · · Score: 0
      $ finger @ftp.kernel.org
      [zeus-pub.kernel.org]
      The latest stable version of the Linux kernel is: 2.6.13
      ...

      I'm not rejecting your claim that 2.6.x is development and 2.6.x.y is stable, but if it's right I'd like them to make it a bit more clear.

    11. Re:kernel bug fixes by GigsVT · · Score: 3, Informative

      When I can't find a stable kernel for one of my servers, it's a serious problem.

      It's been hard to get long uptimes with 2.6... the network drivers are leaky/crash, SCSI support sucks.

      It's just not been very hot.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    12. Re:kernel bug fixes by Anonymous Coward · · Score: 0, Flamebait

      When I looked at FreeBSD, I saw their 5.x development cycle slipped 3 years and the resulting release was so crap the're hastily trying to shove 6 out the door - not that it appears to be much better.

      Their development lists and process is closed to outsiders and seems to have done a good job at driving away talent and installing politicians.

      No, if I'm thankful for anything about Linux's development process, I'm thankful that it is nothing like "the BSDs".

    13. Re:kernel bug fixes by makomk · · Score: 1

      2.6.x kernels are officially stable versions too, though it might still be advisable to wait a while for the bugs to get ironed out.

    14. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      Report the bugs and help the kernel developers find them.

      FWIW, I haven't had any problems at all since 2.6.5 and have enjoyed a great 20% speed boost for one of my servers.

    15. Re:kernel bug fixes by GigsVT · · Score: 1

      Report the bugs and help the kernel developers find them.

      If no one else is using adaptec scsi cards or 3com ethernet cards, then we have a problem!

      Usually though the bugs have already been reported to LKML and the thread just died with no one doing anything about it.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    16. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      Since pretty much everyone and their dog is using adaptec scsi cards and 3com lan cards, and since you seem to be the one having problems, assume for a moment that the problem is specific to your setup, otherwise millions of people would be affected. So, either Linus & camp are doing a terrific job hiding those millions of people's complaints, or you're the only one having those problems.

      Take your pick.

    17. Re:kernel bug fixes by MattWhitworth · · Score: 2, Insightful

      I guess you've been posting bug reports on bugzilla.kernel.org? Otherwise it's not *really* their fault that something doesn't work. Kernel developers test their code pretty well.

    18. Re:kernel bug fixes by NickCatal · · Score: 2, Funny

      Didn't you get the memo? We're putting cover sheets on the TPS Reports before they go out now. I'll get you another copy of that memo.

      --
      -nick
    19. Re:kernel bug fixes by ilitirit · · Score: 1
      I wish Linus would arrive at a policy

      Perhaps he believes that a move like that would not be consistent with the Spirit of Linux.

    20. Re:kernel bug fixes by m50d · · Score: 1
      What exactly is wrong with refining the development process?

      Sometimes it seems like it's all refining and no development process actually happening. There are plenty of things that seem far more urgent, like releasing a kernel that's actually stable (it's at the stage that I'd go back to 2.4 if my distro didn't have so many things depending on 2.6).

      --
      I am trolling
    21. Re:kernel bug fixes by m50d · · Score: 4, Interesting
      And what do you care how they develop the kernel?

      I care about the results, and so far the 2.6 tree has produced a grand total of one kernel that actually works for me (2.6.11). And the obvious cause, rightly or wrongly, seems to be Linus messing around with the development process.

      Or how would you like them to do it? "We will do things this way, and by god, we will do it like this untill the end of time! Even if better ways of doing this comes along, we will not change our ways!"

      How about "We will change things only when the alternative has been shown to be unambiguously better on a smaller project, and only when changing major versions". I believe in experimentation but the kernel is such an important project that a bit more conservatism is called for.

      --
      I am trolling
    22. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      The key problem that people seem to have with major changes in the kernel tree is that they tend to leade to a forked kernel tree (2.4 and 2.6). It also plays havoc on oem or odd ball hardware that doesn't become addressed until 2 released down the road. As for the rest of the people, they are the windows crowd that hasn't seen an upgrade to their kernel tree since windows 2000. I am personally hoping that linus continues to add broad changes to the kernel tree and continue to progress the kernel (2.8 anyone?). You have to keep in mind that a kernel upgrade isn't mandatory in linux. Now if your need to keep on the bleeding edge and the kernel doesn't work, you simply boot into trusty 2.6.12.

      However I am expecting some addle-pate coming around and presenting his viewpoint of the micro vs monolithic kernel.

    23. Re:kernel bug fixes by 10Ghz · · Score: 2, Informative
      I care about the results, and so far the 2.6 tree has produced a grand total of one kernel that actually works for me (2.6.11). And the obvious cause, rightly or wrongly, seems to be Linus messing around with the development process.


      if you have a kernel that work, why upgrade? And why use the vanilla-kernels at all? Vendor-kernels are the ones that are considered stable these days. And there IS a "stable"-branch of the kernel (the 2.6.x.y).

      believe in experimentation but the kernel is such an important project that a bit more conservatism is called for.


      In that case you should't be using bleeding-edge kernels, stick to the vendor-kernels. I mean, we are being conservative here?
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    24. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      At least it's not Brillant.

    25. Re:kernel bug fixes by Homology · · Score: 1
      No, if I'm thankful for anything about Linux's development process, I'm thankful that it is nothing like "the BSDs".

      OpenBSD have two releases each year, on time, and has done so for years. FreeBSD and NetBSD is discussing about doing the same as OpenBSD.

    26. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      Report the bugs TO BUGZILLA, not some random kernel hackers on the mailinst list that day.

    27. Re:kernel bug fixes by bfields · · Score: 2, Insightful
      I wish Linus would arrive at a policy and just stick with it instead of all these gyrations of "we'll use this method from now on...no wait...we'll use this one from now on...

      This case is typical of most such "policy changes" in that he's really just voicing something that's been a defacto policy for a while. All of 2.6 has followed the pattern that the biggest changes went in at the beginning of the -rc, with later -rc's being for stabilization, it's just that this hasn't been an explicit policy and hasn't been consistently enforced, so there have been some weird exceptions.

      and by the way I want everyone to switch revision control systems now...oh wait...sigh.

      Linus has switched revision control systems twice in the history of the kernel. The first time, from nothing to Bitkeeper, took a long time to happen. The second, from Bitkeeper to Git, was obviously much more sudden. But Linus didn't really have much choice (except that many would argue it was partly his fault for choosing Bitkeeper in the first place).

      Those of us that aren't among the few big subsystem maintainers mostly haven't been affected since most of us just rely on emailing patches and ignore bitkeeper and git anyway.

      From the point of someone just reading slashdot or kerneltrap it may look like things are changing very often. But really these changes have been pretty gradual.

      --Bruce Fields

    28. Re:kernel bug fixes by mrchaotica · · Score: 1

      I would just like them to have a consistent and sane versioning scheme so that I don't have to guess which versions are stable or bugfixes or bleeding-edge alpha features or whatever. I liked the "even for stable, odd for bleeding-edge."

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    29. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      Yeah, hopefully this release will maybe address some of the issues I've been having with getting my Adaptec 2940 working in kernels > 2.6.5 :-P

    30. Re:kernel bug fixes by freshman_a · · Score: 1


      It's been hard to get long uptimes with 2.6... the network drivers are leaky/crash, SCSI support sucks.

      I experienced the same thing for about a week, before I switched back to 2.4. Can't argue with a kernel that gave me 300+ days uptime without breaking a sweat.

    31. Re:kernel bug fixes by DistantShadow · · Score: 1

      What exactly is wrong with refining the development process?

      I guess it depends on who changes the policy.

      -ds

    32. Re:kernel bug fixes by jhantin · · Score: 1

      OpenBSD is also code-reviewed from top to bottom on a regular basis. Nothing gets "thrown in". Linux achieves its stability largely by identification and removal of bugs once it's in the field, relying on a large base of early adopters more than it does code review.

      Given ESR's musings on the cathedral and the bazaar, it seems to me one might view OpenBSD as a rather "bizarre" sort of cathedral, and Linux as a bazaar overrun by cults of personality. In Microsoft's world, on the other hand, you can't even get in to see the interior of the cathedral until the clergy grants you access.

      Okay, have I stretched this metaphor too much? :-)

      --
      ...when you're writing a game...tweak the difficulty of "Easy" to something [your mother] can cope with. -- onion2k
    33. Re:kernel bug fixes by sloanster · · Score: 2, Insightful

      Hmm, it sounds somebody is trying to build a do-it-yourself kernel and screwing it up somehow. It sounds like somebody needs to quit trying to play kernel hacker and just use the kernel shipped by the vendor of the distro.

      We've been using SuSE Enterprise server on H/P DL hardware here and it is absolutely rock solid. We've been replacing HPUX with SuSE, and no matter how these boxes are pounded they handle the load very gracefully and without any hint of trouble. We're pleased to find that the 2.6 kernel scales much better than the old 2.4, so the difference has been all good - oh and we don't bother compiling our own kernels, we leave that to Novell/SuSE since we've got other things to do, and they've been doing a great job.

      Just some real world data as a counterpoint to the FUD.

    34. Re:kernel bug fixes by GigsVT · · Score: 1

      It's not FUD. I'm just reporting what I've run into.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    35. Re:kernel bug fixes by m50d · · Score: 1
      if you have a kernel that work, why upgrade?

      My distro is starting to depend on 2.6, with things like NPTL. 2.4 is no longer supported. I'm fortunate in that I found this one 2.6 release that works on my system, but there may be other systems with which I'm not so lucky.

      And why use the vanilla-kernels at all? Vendor-kernels are the ones that are considered stable these days. And there IS a "stable"-branch of the kernel (the 2.6.x.y).

      All of those I have tried. None are stable.

      In that case you should't be using bleeding-edge kernels, stick to the vendor-kernels. I mean, we are being conservative here?

      I would, but they don't work. My distro has moved on to 2.6, so I'll try any 2.6 kernel I can to get a stable one.

      --
      I am trolling
    36. Re:kernel bug fixes by GigsVT · · Score: 1

      Given, the adaptec cards giving trouble were somewhat older, 40 and 80 meg cards. They still used aic-7xxx.

      As for the 3com issue, it only showed up after several weeks of heavy traffic. The network would slow down to about half speed. Reloading the kernel module made it go back to full speed. I suspect some hard to track down memory leak.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    37. Re:kernel bug fixes by Fred_A · · Score: 1

      In practice though :

      Developement version = 2.6.x
      Stable version = Whatever works for you

      At least that's the way most people see it nowadays.
      I wish it was a bit more tidy but obviously things aren't headed that way.

      FWIW :
      4 fred@ix ~ > uname -mr
      2.6.11-gentoo-r6fred x86_64
      And I'm not especially eager to fix what currently isn't broken.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    38. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      Uh... so none of the vanilla sources are stable for your system, and none of the vendor kernels work either? Smells like you have a configuration or hardware problem. Check the changelogs from 2.6.10 to 2.6.11, and from there to 2.6.12. Unless some major changes are listed there that specifically lists your hardware, I find it hard to believe that only that one particular version will work. If there ARE changes related to your hardware, submit a bug report or give some input on the kernel development mailing lists. I'm assuming you have a hardware issue, since you don't specify what device/filesystem/etc. is actually having problems, nor if you are using any vendor-supplied drivers, patches, etc. Can't fix anything until it is narrowed down and brought to the developers' attention. "My system isn't stable" is a generic statement, and the generic answer is hardware/config problem until some specifics are provided. Cheers and good luck.

    39. Re:kernel bug fixes by ThinkingInBinary · · Score: 1

      I don't know what kind of system you're running, but on my laptop, every 2.6 kernel has worked, and everything since 2.6.10 has had perfect ACPI support!

      And I run a gentoo- and swsusp2-patched kernel, so it's even stable when patched. (I don't know how much of the stability comes from the patches, but normally patched kernels are considered another source of instability.)

      I don't think there's anything wrong with how Linus develops the kernel. I do get tired with all the 2.6.12.x versions, but they're usually a diff of literally 5-10 lines.

      I really don't see what's so bad here.

    40. Re:kernel bug fixes by oconnorcjo · · Score: 2, Insightful
      I guess you've been posting bug reports on bugzilla.kernel.org? Otherwise it's not *really* their fault that something doesn't work. Kernel developers test their code pretty well.

      Even if he has reported bugs, with the new features breaking stuff, he would probably find new bugs next release. But the fact of the matter is that 2.6 is less stable and it is the new development method that is to blame. Most people don't have time to track down bugs of this nature, especially in a bussiness environment where the OS is just supposed to work. If Linus and gang are looking for Linux to just be some developers toy where the fun is in creating and fixing things then they are doing the right stuff but if they want to make a reputation for solid systems that bussinesses can use, they are making a mistake. When someone relies on an OS to do multimillion dollar transactions and it goes down, they don't want to hear "I am sending in a bug report to the kernel mailing list right now".

      --
      I miss the Karma Whores.
    41. Re:kernel bug fixes by m50d · · Score: 1
      Uh... so none of the vanilla sources are stable for your system, and none of the vendor kernels work either?

      I can't say certainly none, but I have tried a variety and this is the only one which works

      Smells like you have a configuration or hardware problem.

      Such a problem would surely be apparent under 2.4 and 2.6.11. You sound like those people who say windows instability is usually due to bad ram. When the same system with the same config is stable with one kernel version but not others, I blame the kernel.

      If there ARE changes related to your hardware, submit a bug report

      I have. The issue that was causing my most obvious problem in 2.6.0-3 even got fixed, but sadly it was only to reveal another one.

      I'm assuming you have a hardware issue, since you don't specify what device/filesystem/etc. is actually having problems

      That's because I don't know. My system just freezes. There don't seem to be any untoward log entries or anything.

      nor if you are using any vendor-supplied drivers

      I've tried removing these. Makes no difference.

      --
      I am trolling
    42. Re:kernel bug fixes by m50d · · Score: 1
      I don't know what kind of system you're running, but on my laptop, every 2.6 kernel has worked, and everything since 2.6.10 has had perfect ACPI support!

      Glad someone's benefiting then. ACPI has been working fine for me since 2.4.20, 2.6 has brought me nothing but instability.

      And I run a gentoo- and swsusp2-patched kernel, so it's even stable when patched. (I don't know how much of the stability comes from the patches, but normally patched kernels are considered another source of instability.)

      I've tried gentoo kernels, in fact the one I'm using at the moment is the last gentoo 2.6.11 release, but the other versions are all unstable.

      I don't think there's anything wrong with how Linus develops the kernel. I do get tired with all the 2.6.12.x versions, but they're usually a diff of literally 5-10 lines.

      The kernel is, for me, no longer stable with 2.6, and the obvious change to attribute this to is Linus' not branching off a 2.7 for development.

      I really don't see what's so bad here.

      My system worked perfectly with 2.4. It doesn't with 2.6. That's why I have a problem.

      --
      I am trolling
    43. Re:kernel bug fixes by JebusIsLord · · Score: 1

      Yeah, why can't he just stick to the development model tested and proven by all the other enormously distributed kernel development projects. Oh, wait...

      --
      Jeremy
    44. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      Linux is only a kernel, blah, blah, blah...

    45. Re:kernel bug fixes by Donny+Smith · · Score: 1

      > I guess you've been posting bug reports on bugzilla.kernel.org?

      I used to do that up to two years ago, but then I realized it's easier to change to another kernel or another distro rather than spend my time on that. Return on bug report is just too low.

    46. Re:kernel bug fixes by Nevyn · · Score: 1

      The point is that it's never worked well to install vanilla kernels into production (unless you floow lkml very closely and do the same kind of work Red Hat etc. do), they've always had problems and missing features ... the only difference now is that due to development changes everything is happening much faster.

      If you are driving with your eyes closed and no seat belt no, and it kind of worked ok when doing 2MPH the fact you are now doing 20MPH isn't the problem and slowing down again isn't the solution.

      --
      ustr: Managed string API with ave. 44% overhead over strdup(), for 0-20B
    47. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      eesh. what kinda hardware u running here?

    48. Re:kernel bug fixes by tyrione · · Score: 1
      That is where support contracts by a specific vendor, say SUSE, comes to mind. The point of such a contract is to provide patch support to protect against any issues that keep you from doing your business.

      Support contracts are standard practice at Microsoft, Apple, IBM, Sun, etc. They even offer custom contracts that with the right amount of finanical incentive provide custom patches only to that specific customer.

    49. Re:kernel bug fixes by Malek+the+Damned · · Score: 1

      Ditto. My desktops have been living in 2.6.x since .0, and every 3 or 4 releases I notice a speed boost in some part of the OS - be it encodes are quicker from the CPUs being more efficient, disk I/O isn't as hoggy, or it's just generally more responsive. When I have to use one of work's servers on 2.4.x they just feel SLOW in comparison...

      That said, I'll be waiting for 13.2 or .3 to come out before patching up =)

    50. Re:kernel bug fixes by sloanster · · Score: 1

      The problem is, you're reporting something as a problem, but it's a problem of your own making. The kernel.org tarball is not meant for end-users, it's meant for kernel developers and vendors.

      End users such as yourself should use the vendor-supplied kernels, which come ready to use, no patching or compiling required.

    51. Re:kernel bug fixes by shellbeach · · Score: 1

      The kernel.org tarball is not meant for end-users, it's meant for kernel developers and vendors.

      Err ... what planet did you spring from? There's plenty of end-users out there who've been compiling their kernels for years. It's part of being a linux user, being able to customise the kernel to suit your own needs, getting rid of the dross, compiling in the good stuff, patching in extra bits that you want.

      How many laptop linux users do you think use vanilla distro kernels?? Ever heard of swsusp2? Really, I never thought I'd hear building a linux kernel described as only for kernel developers and vendors!

    52. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      Unless you want to use hardware invented in the past three years, in which case you're stuck 1) compiling your kernel or 2) using Windows. I can't count the number of times I've heard "Linux has excellent $foo support! You just go to some third-party website and download the $foo driver (version 0.0.7) and patch it into your kernel without any documentation..." which is what I, as a home user, had to do to get wireless support to work a little while back.

      Heck, back when I started with Linux, it was expected that every Linux user know how to compile their kernel. It was part of the normal user experience. Of course, we also had to fuss with boot and root floppies and know the horizontal and vertical frequences of our monitors, so maybe it's a positive thing that Linux has simplified enough that recompiling a kernel isn't something users should be expected to run into.

      - Perpetual Newbie

    53. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      I'm only a kernel tester (not a developer) although I have sent back highly detailed bug reports to kernel developers who (after I bellyache about something) request much more information specifically from me (including but not limited to: Alan Cox, Andrew Morton, Ben Collins, Len Brown, Dave Jones, Rusty Russell, Vojtech Pavlik, etc.). The switch from Bitkeeper to git does not affect me, since the patches come out the same and are applied in exactly the same way. Ksymoops and backtraces work the same way. I don't tend to build every subrelease that comes out (although I have built 3 kernels in the last week --and ran each of them for at least 1 whole day). Any improvement in the development process that Linus wants to try is a good thing in my estimation. The day I start to worry is the day Linus stops wanting to improve both the kernel, and the process by which it gets developed. Yes, the development process in place now beats the pants off commercial processes (by a factor of at least 10:1). Could we do better? Maybe! We get to try (and Linus is the guy who gets the all the quarters, and gets 10 tries for a quarter).

    54. Re:kernel bug fixes by andreyw · · Score: 1

      What drivers suck, specifically? What network devices? What SCSI HBAs?

      Can you provide specific bugs and reports, or is this anecdotal evidence?

      Also mind you that all distributions modify their kernel (it's not vanilla), with some doing it more than they really should (RedHat, SuSE^H^H^HUSE).

    55. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      "I wish Linus would arrive at a policy and just stick with it instead of all these gyrations of "we'll use this method from now on...no wait...we'll use this one from now on...and by the way I want everyone to switch revision control systems now...oh wait...sigh." - by Ritz_Just_Ritz (883997) on Monday August 29, @08:47AM

      OK, this is 1 time I will REALLY "stick-up" for the Linux Penguins, especially "Penguin #1", Mr. Torvalds:

      I am going to do this, with a famous saying first of all, & secondly, a quote from one of my fav. characters from Science Fiction (the literature of change):

      1.) "You can't please everyone, ALL of the time!"

      &

      2.) Anakin Skywalker (pre-Darth Vader), speaking to Obi-Wan Kenobi in "REVENGE OF THE SITH" about R2D2 & near the start of the film, where R2 sent the elevator in the WRONG (down) direction while attempting to save Chancellor Palpatine (ala Darth Sidious):

      Anakin Skywalker: "Uh, ahem: NO LOOSE WIRE JOKES!"

      Obi-Wan Kenobi: "Did I say anything?"

      Anakin Skywalker: "He's trying..."

      * :)

      I give credit to Mr. Torvalds, still managing as much of his creation as he does, because odds are, it is one HELL of an undertaking (the man has a full-time job from what I understand as well ontop of this)... so, you penguins (or even "pro-Win32" people like myself mostly), mellow out!

      Have you EVER written something upwards over 1 million-40 million lines of code (basing the latter on the alleged size on NT-based Os' currently)?

      NO?? You haven't??? I have... it's not cake work, & the larger & more complex something grows, the more "moving parts" it generally has... ones that directly can adversely affect others, when you fix 1, you can inadvertently BREAK OTHERS!

      So, to be blunt? If you have NOT been designers of "Enterprise Class" systems, or OS' yourselves??

      Before you try to cut this man down, walk a mile in HIS shoes, otherwise?

      STFU!

      (Seriously, not meant as being a prick either... just decent to a person like Linus T/Penguin #1, really, I do admire what Linux has become & especially in the 2.6x series, even though much of it (e.g.-> SMP work via threads in the core/kernel level of Linux was always there in NT-based Os', but copied by Linux architects, or how immensely modern Linux has process scheduling that seriously imo, mimics NT-based Os' I/O completion ports usage VERY much))...

      Heck, the guy's trying, ok?

      ABOVE ALL? DO think about this:

      Look, if he makes a 'bad move' w/out experimenting or figuring it out RIGHT first? He "F's up" major... it's not worth it.

      Linux is STILL growing, as nice as it has become (first time I saw it was Slackware 1.02 in 1992-1993 iirc, & it sucked by comparison to today's model of it, seriously)

      Also, & imo? Linux, it WILL kill UNIX... & not MS' works, Linux will kill its forebear... who tells me this the MOST? A couple things:

      1.) IBM suddenly the last couple years now 'befriending' Linux suddenly, even though they HAVE AIX!!! Call it a prediction...

      &

      2.) The fact that Linux runs on SO many kinds of hardwares (a great advantage it has over even NT-based Os' imo) that UNIX folks can turn to it & be QUITE @ home with it, in minutes imo!

      (I was nearly instantly, even back with Slackware 1.02, because I came out of a mixed Vax VMS, Unix (System V), &/or OS400/System34/36/38 background prior to using it... & VMS and UNIX commandlines? Amazingly similar!)

      Anyhow:

      Well... imo, there is NO harm in Mr. T. being cautious, as well as experimenting... he is FAR better off being safe, than sorry (especially in the LONG haul)!

      APK

    56. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      Correction - the 2.6.x-* versions are development, e.g 2.6.13-rc5. However, 2.6.x designates a stable version (treat as 2.6.x.0), and 2.6.x.y is a patch release for that stable version.

      E.g, up until now, one of the 2.6.12.x releases was current, and 2.6.13-rc5 was a development version. Now, 2.6.13 has been released, and is the current stable (until a 2.6.13.1 appears)

    57. Re:kernel bug fixes by oconnorcjo · · Score: 1
      That is where support contracts by a specific vendor, say SUSE, comes to mind. The point of such a contract is to provide patch support to protect against any issues that keep you from doing your business.

      I think that is lame excuse and a lame approach. The people who know the kernel code best are the kernel developers who developed it. To lay the burden on a third party vendor means more work for everybody and it still means less stable code in general. When Linux had a stable release kernel, vendors would still test kernels to make sure they were good but they were not burdened with any real development. Now vendors are expected to have kernel developers on staff rather than it being an optional desire.

      There is now a fundamental change in Linux development. It used to be create a solid system. Now it is create a featurfull system. Personally I just want a solid system and I can wait a few years for new features.

      --
      I miss the Karma Whores.
    58. Re:kernel bug fixes by rempelos · · Score: 1

      The kernel is, for me, no longer stable with 2.6, and the obvious change to attribute this to is Linus' not branching off a 2.7 for development.

      My system worked perfectly with 2.4. It doesn't with 2.6. That's why I have a problem.

      You are stack with the old process, you need to understand that 2.6 vanilla aren't considered stable, in the same way 2.4 and 2.5 were. Now, why do you want so much to upgrade to 2.6 if you are so happy with 2.4 kernel? I really can't see what is your point.

    59. Re:kernel bug fixes by Anonymous Coward · · Score: 0

      Solaris 10.

    60. Re:kernel bug fixes by GigsVT · · Score: 1

      Usually these have been problems fixed by swapping hardware around until it works.

      I'm not paid to spend hours debugging the kernel, I'm paid to get things working.

      I wasn't even aware the kernel had a bugzilla until this thread. Last I heard Linus didn't want a bugzilla and wanted people to send shit to LKML.

      Usually the way it goes down is the vendor kernel breaks, so we go to the vanilla kernel, that breaks, then we move hardware around until it works. You seem to be advocating using the vanilla kernel. That's not what many other replies to this are saying.

      They are saying that specifically because when Linus decided to make the stable kernel unstable, he said the distros would make it stable. I don't agree with this philosophy one bit.

      I can only think many of these problems are unforseen interactions between certain chipsets and add-in cards, because often changing the motherboard with a different one shows both the motherboard and the hardware work fine, just not together.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    61. Re:kernel bug fixes by m50d · · Score: 1

      Mobo is an FIC AZ11EA, 800MHz AMD Duron "Spitfire" proc, 384mb DDR SDRAM (don't tell me it doesn't exist) in 3 sticks, Netgear FA312 (I think), Nvidia RIVA TNT2 M64 (AGP) and then a PCI geforce2 MX/MX400.

      --
      I am trolling
    62. Re:kernel bug fixes by m50d · · Score: 1
      You are stack with the old process, you need to understand that 2.6 vanilla aren't considered stable, in the same way 2.4 and 2.5 were.

      2.5 wasn't stable, it's a development branch. Linus has officially declared that 2.6 is stable - if it wasn't, it should have remained 2.5 - and what we should use, and 2.4 is the legacy branch.

      Now, why do you want so much to upgrade to 2.6 if you are so happy with 2.4 kernel?

      I don't, but my distro no longer supports using 2.4.

      I really can't see what is your point.

      2.6 is officially the stable branch of the kernel, and distributions are flamed if they do not switch to it. As such, it should actually be stable.

      --
      I am trolling
    63. Re:kernel bug fixes by rempelos · · Score: 1
      2.5 wasn't stable, it's a development branch. Linus has officially declared that 2.6 is stable - if it wasn't, it should have remained 2.5 - and what we should use, and 2.4 is the legacy branch.

      Sorry for my poor english, I didn't mean 2.5 was stable, I was refering to the process of having the most expiremental features added on 2.5 and keep 2.4 as stable as possible. And 2.4 is not a legacy branch, it's still being developed and most things of 2.6 (like new hardware support) are being backported to 2.4

      I don't, but my distro no longer supports using 2.4.

      In my company we have Debian for our servers running with 2.4 kernels. I also use Debian and Ubuntu for my desktop PCs with 2.6 kernels (so far without any stability issue). Both 2.4 kai 2.6 kernels are fully supported by my distros, non of those distros have a policy that forced me to upgrade to 2.6.

      Most of the nice things of 2.6 are backported to the 2.4 series. So there isn't any reason for a distro to stop supporting 2.4 or be flamed for supporting it.

      2.6 is officially the stable branch of the kernel, and distributions are flamed if they do not switch to it. As such, it should actually be stable.

      Actually most of the linux servers out there are still running on 2.4, and 2.6 is recommended mostly for desktop workstations. Switching to 2.6 is not the only option, since both can be supported. I can think of a reason for a distro to be flamed if it _does stop_ supporting 2.4, but not in the other way around.

      When you say that distros are flamed for not switching, flamed by who? Maybe from people like you, eager to upgrade everything to the last version because they think that this is always the right thing to do.

      Maybe you should stop blaming linus for the way he chooses to develop _his_ project, and start complaining to your distro maintainers for quiting on 2.4 and shiping with an unstable 2.6.

    64. Re:kernel bug fixes by m50d · · Score: 1
      And 2.4 is not a legacy branch, it's still being developed and most things of 2.6 (like new hardware support) are being backported to 2.4

      It's older than the current stable, it's legacy. 2.2 and 2.0 are still under development and occasionally get things backported

      Both 2.4 kai 2.6 kernels are fully supported by my distros, non of those distros have a policy that forced me to upgrade to 2.6.

      Those are relatively major distos. It's difficult for smaller distros to support two separate versions. Given that they had to choose one I can't blame mine for picking 2.6.

      Actually most of the linux servers out there are still running on 2.4, and 2.6 is recommended mostly for desktop workstations. Switching to 2.6 is not the only option, since both can be supported. I can think of a reason for a distro to be flamed if it _does stop_ supporting 2.4, but not in the other way around.

      Distros which didn't switch to 2.6 as default were flamed quite severely, here for starters. I remember a post along the lines of "why is slackware still using 2.4 as a default 3 months after 2.6 came out? Answer: because it's an obsolete distribution for obsolete people. It just isn't relevant today". I'm pretty sure I saw a comment from Linus along the lines of "2.6 is the stable tree, distributions should be using it, I can't do much more until distributions have it as their default."

      When you say that distros are flamed for not switching, flamed by who? Maybe from people like you, eager to upgrade everything to the last version because they think that this is always the right thing to do.

      When have I ever said anything like that? I was happy with 2.4, it worked, and I didn't switch to 2.6 until it became necessary.

      Maybe you should stop blaming linus for the way he chooses to develop _his_ project, and start complaining to your distro maintainers for quiting on 2.4 and shiping with an unstable 2.6.

      Linus is free to develop however he likes, but when he releases a new kernel as the stable kernel, says that it's the stable tree, changes the version number to indicate that it's no longer the development tree it's now the stable tree, tells distributions they should be shipping it, and it isn't fucking stable, there is no one to blame but him. I have no problem with him releasing unstable versions of the kernel, but he shouldn't call it a stable version if it isn't.

      --
      I am trolling
    65. Re:kernel bug fixes by rempelos · · Score: 1

      Some things to be noted:

      • 2.4.31 is very up to date, and is not legacy.
      • From web surfing a little and reading about the current status of kernel 2.6, I found out that most of the people complaining for stability issues were gentoo users, using 2.6 with the gentoo patches.
      • No kernel version can be considered stable unless it's widely tested from the world. 2.6.x.y are the more stable kernels since they 're bugfixes to 2.6.x.
      • Patches for bugs are incorporated in the immediate next official release, no matter what. It's the new features that are being affected by the developement process.
      • I agree with linus that 2.6 is stable, it seems rock solid on my systems.

      And why are you forced to use 2.6. Your distro doesn't provide a package, so what? Have you tried to download and install 2.4.31 by yourself? What is exactly that you fear it will break in your distribution by installing a 2.4 kernel? You can have both 2.4 and 2.6 installed in a system anyway. Compile your kernel and configure lilo/grub, what's stoping you?

      PS.
      You said that your 2.6 kernel is unstable, but didn't mention the symptom. Why is it unstable? it hangs up and reboots? X just freezes? filesystem data corruption? Are you sure it's something that can't be fixed? Have you found others with the very same exact problem? Are you sure it isn't something you did wrong?

    66. Re:kernel bug fixes by m50d · · Score: 1
      What is exactly that you fear it will break in your distribution by installing a 2.4 kernel?

      NPTL and maybe ALSA.

      You can have both 2.4 and 2.6 installed in a system anyway. Compile your kernel and configure lilo/grub, what's stoping you?

      I keep a 2.4 kernel around for emergencies, but it's missing things like up to date svgalib and alsa modules, and I don't know if it would work with my new glibc. It's just much more hassle to deal with a kernel that isn't at /usr/src/linux.

      You said that your 2.6 kernel is unstable, but didn't mention the symptom. Why is it unstable? it hangs up and reboots? X just freezes? filesystem data corruption?

      The system hangs. It isn't just X because I've tried sshing in when it happens, no good. I've tried enabling the software watchdog and running the userspace program that goes with it, to no effect. (It doesn't reboot within a minute of locking up like it should).

      Are you sure it's something that can't be fixed?

      No, but I can't isolate anything that causes it. I've tried running the same applications that I was when it locked up, doing as far as possible the same things in them - no good. I wouldn't know where to start, and I know bugreporting such "random" occurrences doesn't seem to help anyone, it's just left and marked CANTFIX.

      Have you found others with the very same exact problem?

      No, not as such. Plenty of people have system lockups like mine, but the fixes I've seen haven't worked or just haven't made sense on my system, and I haven't found anyone else for whom 2.6.11 but no other 2.6 versions work.

      Are you sure it isn't something you did wrong?

      Pretty sure. I configure all my kernels the same way, as far as possible, so a config error, or pretty much any error, would show up on 2.4 and certainly 2.6.11.

      --
      I am trolling
    67. Re:kernel bug fixes by rempelos · · Score: 1

      I wish I could help you more. Anyway, I never use svgalib, I had found out that it was buggy (in much older kernels, like 2.2), that or the apps that were using it. It seems totally useless to me. And another thing, don't mess linux headers with glibc headers. /usr/src/linux/include and /usr/include/linux shouldn't be the same http://linuxmafia.com/faq/Kernel/usr-src-linux-sym link.html. That is unless you compiled glibc yourself, but that is something you shouldn't do in an already unstable system. Well if you did, I would suggest to go back to the package provided by your distro.

  2. Linux Torvalds by The+New+Andy · · Score: 4, Funny
    I'm sure there is a witty comment to make about the fact that the very first word in the article summary is wrong, but I can't quite fit it all together.

    I'm not really a grammar/spelling/correctness nazi either, so I can't really complain about slashdot going down hill. I just feel compelled to post.

    Uh... I wish my name was Linux?

    1. Re:Linux Torvalds by carndearg · · Score: 4, Funny

      Uh... I wish my name was Linux? No y'dont. You'd have Aussie lawyers after you for licencing fees!

    2. Re:Linux Torvalds by amightywind · · Score: 1

      I'm sure there is a witty comment to make about the fact that the very first word in the article summary is wrong...

      You're right. They should have said GNU/Linux.

      --
      an ill wind that blows no good
    3. Re:Linux Torvalds by Anonymous Coward · · Score: 1

      Excellent! He's up there with Synthesizer Patel and Computer Jones!

    4. Re:Linux Torvalds by MattWhitworth · · Score: 1

      All the lawyer's names would be Bruce, and they'd repeat 'G'day mate' until your mind shuts down and you give them the money :)

    5. Re:Linux Torvalds by xer.xes · · Score: 1

      I'm sure he will sue you for this comment using the linux (TM).

      I'll guess I'll get sued too...

      --
      xer.xes -- 4181
  3. Coral by Saiyine · · Score: 2, Informative


    This is a cool use for the Coral Cache, mirroring files this big: the kernel.


    --
    Dreamhost superb hosting.
    Kunowalls!!! Random sexy wallpapers (NSFW!).

    --
    Hosting 20G hd, 1Tb bw! ssh $7.95
    1. Re:Coral by croddy · · Score: 3, Informative
      dude, there's no need to stick kernel.org behind the (comparatively sluggish) coral cache.

      it's kernel.org. they mirror other people's stuff.

    2. Re:Coral by Saiyine · · Score: 1

      Yeah, you're right.

      I was thinking about posting something about binary patches to alleviate the use of bandwidth, when I read this on the kernel web: Apr 9, 2005: Both the new servers are now in full production use. Each is connected to a separate ISC gigabit link. Enjoy!...

      But again, it's a 40 megs file... who will win?

      --
      Dreamhost superb hosting.
      Kunowalls!!! Random sexy wallpapers (NSFW!).

      --
      Hosting 20G hd, 1Tb bw! ssh $7.95
    3. Re:Coral by Saiyine · · Score: 1


      And what can I say about the servers???

      two separate Proliant DL585 quad Opteron servers, each with 24 GB of RAM and 10 TB of disk.

      Man, those are machines!

      --
      Dreamhost superb hosting.
      Kunowalls!!! Random sexy wallpapers (NSFW!).

      --
      Hosting 20G hd, 1Tb bw! ssh $7.95
    4. Re:Coral by ScriptedReplay · · Score: 1

      IIRC, they said they expected to come close to saturating their connection while mirroring a new Fedora Core release - and it didn't happen. That's significantly more than 40MB. I think kernel.org doesn't really have to worry about slashdotting.

    5. Re:Coral by LnxAddct · · Score: 5, Informative

      You're kidding right? A kernel release like this doesn't even make kernel.org break a sweat. Read this. The only time they ever even start to see some strain on their bandwidth is with a new release of Fedora, because they are a mirror for it (both of their gigabit links become saturated). For kernel releases though, they say that their bandwidth stays pretty normal at around 150Mbps to 200Mbps.
      Regrds,
      Steve

    6. Re:Coral by WWWWolf · · Score: 1

      What's further, I don't know if Coral even caches huge files. One time I tried downloading an ISO through Coral and, some puzzling later, it just redirected me to a non-Coralized link.

      Kernel tarball might be cached, though, not going to try right now though...

    7. Re:Coral by TheLink · · Score: 1

      Maybe you could get your fedora core release from here.

      Site seems quite slow though. Wonder who's using all the bandwidth at that site. Maybe slashdotters downloading the latest iso's... ;)

      --
    8. Re:Coral by Anonymous Coward · · Score: 0

      Yeah, nice entry-level servers.

    9. Re:Coral by OrangeTide · · Score: 1

      I tend to wait about a 2 weeks before I upgrade to a new kernel. One, because of personal time constraints; two, because I would rather let other people try it first to see if it blows up.

      I suspect a fair number of people do the same thing, upgrading the kernel is easy but it's not convenient. So we put it off rather than all rushing to the latest version.

      --
      “Common sense is not so common.” — Voltaire
  4. Linus, not Linux by altanhaider · · Score: 5, Funny

    It's LINUS Torvalds. God, I hate reading typoes!

    1. Re:Linus, not Linux by I+confirm+I'm+not+a · · Score: 0, Redundant

      God, I hate reading typoes!

      Uh, dude, that's typos, not typoes! ;-)

      /me slinks off...

      --
      This is where the serious fun begins.
    2. Re:Linus, not Linux by bro1 · · Score: 2, Funny

      And in another news Bill Gates anounces that he is going to change his name to Bill Windows.

    3. Re:Linus, not Linux by bdeclerc · · Score: 1

      Gates, Windows - both are ways of getting through a wall...

    4. Re:Linus, not Linux by Anonymous Coward · · Score: 0

      God, I hate reading typoes!

      Godd, I hayte reeding speling mistaikes.

    5. Re:Linus, not Linux by Dhar · · Score: 1

      Uh, dude, that's typos, not typoes! ;-)

      Uh, dude, that's humor, not typos! ;-)

      -g.

    6. Re:Linus, not Linux by Anonymous Coward · · Score: 0

      WHOOOOOOOOOOOOOOOOOOOOSH!!!

      Lameness filter encountered.
      Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted.

    7. Re:Linus, not Linux by xerxesdaphat · · Score: 1

      Hahahah... my old IPT teacher (a subject for general computing stuff in highschool) was called Bill Window - the funny thing was he was a hardcore Mac zealot.

      --
      The Shoes of the Fisherman's Wife Are Some Jive Ass Slippers
  5. Linux Torvalds... by Thijs+van+As · · Score: 0, Redundant

    funny :)

  6. What kind of person are you? by Anonymous Coward · · Score: 0

    What kind of person are you that these "linux fanatics" would make so angry and desperate as to spend hours writing this stuff and posting it to slashdot?

  7. Nope by Knome_fan · · Score: 0, Offtopic

    Sorry, I don't know if your post was intended to be funny, or simply a troll, but the kernel is just Linux and nobody ever claimed otherwise, least of all Stallman.

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

      Not anymore, fuzzypants.

      It's all GNU/Linux. All of it! Mwuahahahahahahah!

      --
      Richard M. Stallman

    2. Re: Nope by zalt · · Score: 1

      Don't get me wrong, i use Linux every day, but I'm always amused when people criticize it.

      Alternative #1: Negative criticism
      -"Man, Linux SUCKS. NOTHING WORKS!!!"
      -"Shut up you ignorant Redmond-loving fool. Noone ever said Linux was anything but a kernel."

      Alternative #2: Positive criticism
      -"Man, your desktop looks awesome. Can i get my machine to behave like that?"
      -"No. This is Linux. You should try it. Best. OS. Ever."

  8. Why aren't we at 2.7 yet? or 2.8? by Anonymous Coward · · Score: 0

    The non-technical people out there understand version #s only enough to be confused here. They probably think Linux is stagnating. I'm not saying we need to rush ahead to "Linux XP" or something, but wouldn't it be wise to start incrementing something other than the 3rd set of digits?

  9. Re:Why aren't we at 2.7 yet? or 2.8? by Anonymous Coward · · Score: 0

    Non-technical people probably don't give a rat's arse which version of the kernel their Ubuntu/ SUSE/ Linspire install is running, if they even know what a kernel is at all.

  10. New release strategy by Sv-Manowar · · Score: 2, Interesting

    The new release strategy being introduced as of this kernel, with two weeks before a feature freeze is an interesting step. The kernel development process has been changed a lot, and as much as some people may complain about these frequent changes, I believe it is in the search for a better way of working/more productivity. Surely exploring the problem for better solutions is a better way of trying to improve releases than putting up with a good-enough release method..

  11. Ahem... by dwalsh · · Score: 5, Funny

    2.6.13 Linux(TM) kernel

    --
    ${YEAR+1} is going to be the year of Linux on the desktop!
  12. Re:Something wrong by Musteval · · Score: 1, Funny

    Are you running Windows?

    --
    Note to mods: I'm probably being sarcastic.
  13. Hey! It's not Linux Torvalds... by yogix · · Score: 5, Funny


    ... it's GNU/Linux Torvalds!

    - RMS

    1. Re:Hey! It's not Linux Torvalds... by cybersaga · · Score: 2, Informative

      ... it's GNU/Linux Torvalds!

      No it's not. We're talking about the kernel.

    2. Re:Hey! It's not Linux Torvalds... by Anonymous Coward · · Score: 0
      An imposter! As any fule no, I sign myself:

      - GNU/RMS

    3. Re:Hey! It's not Linux Torvalds... by Pastis · · Score: 1

      reread the first line of the annoucement. There's a typo. Hence the joke.

    4. Re:Hey! It's not Linux Torvalds... by cybersaga · · Score: 1

      Yeah, I got it, conveniently after I posted that message.

    5. Re:Hey! It's not Linux Torvalds... by Pastis · · Score: 1

      ... it's GNU/Linux(TM) Torvalds!

      - paperclip

    6. Re:Hey! It's not Linux Torvalds... by Anonymous Coward · · Score: 0

      But notice that everyone just calls it "kernel". Unfortunatly, nobody uses the word linux to mean what it was intended to.

  14. Re:Why aren't we at 2.7 yet? or 2.8? by bastiaannaber · · Score: 1

    Even non-technical people these days know that version numbers don't mean jack shit.

  15. Re:How about a stable ABI? by erlenic · · Score: 5, Interesting

    I'll give you my opinions on these.

    A) It's been years since I've recompiled a kernel, and I've only compiled a few software packages in years. I use Linux daily at work, and exclusively at home. It may not be as easy to install software as on a Mac, but a good distro is equal to Windows.

    B) I agree, but at the same time I find it rare that I have to drop to a command line to do normal computing tasks. I still go there daily, but by choice.

    C) I can usually find anything I need online without having to post to a message board myself. However, I do agree that it needs significant improvement. I wouldn't expect non-technical people to search online for their answers.

    By the way, you should find other examples to "prove" your technical skill. Ripping videos and using Photoshop aren't too "technical" in nature, especially here. Alternatively, don't try to prove it, just leave it assumed. Note: I'm not calling your knowledge into question, just your examples.

  16. Sorry by Anonymous Coward · · Score: 4, Insightful
    You cannot admit that no one in their right mind would do professional video editing in Linux.


    Industry standard 3d, compositing and editing tools all run under linux which is the natural progression because of their IRIX legacy.

    I've also done some DTP under linux but that probably wasn't professional, since I didn't just bang a series of poorly masked raster images together like most 'professional' agencies we dealt with.

    Does this make me a linux fanatic?

    1. Re:Sorry by cailyoung · · Score: 1

      Compositing and 3D yes, editing no. Yes there's a pro-level edit suite out there, forget the name, but the Big Two, Avid and FCP are Mac/Win and Mac only respectively. Sorry :(

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

      speaking as a former film and video editor who suffred avid and their consumption of lightworks

      avid are jackass assholes
      and will never develop a prgram for linux unless they can lock their pro edition to their fork of editingdesktopLinux that would hyptheitically come with their 15k [linux]workstations shuld a linux version ever exist. the lite version will be free to run on windows however with draconian copy protection and arbitrarily disabled feautures to justify buying the pro-edit kit .

      and the FCP stable owned by apple have a vested interst in keeping FCP on the mac.

      all mac apps will be bale to run on desktop linus with ease as a wine style osx layer will come at least for the available for OSX.x86 prgrams [those few that haven't been ported to linux/ bsd - yes, few! as it will be easier to make thse ports available.

    3. Re:Sorry by delire · · Score: 1

      Compositing and 3D yes, editing no [...]

      This may be the pro-level suite you mean. More here.

      That said, no one in the feature film industry considers Final Cut Pro to be a standard, in fact MainActor on Linux is a far more widely adopted platform AFAIK.
    4. Re:Sorry by Anonymous Coward · · Score: 0

      Ignoring proprietry solutions that were ported from IRIX with the rest of any studios workflow, because these are unlikely to be updated to handle 16bpp. Avid is a hardware based solution, we all know it's had its day. FCP has made inroads but is no more industry standard in the mid-end than discreet's smoke although FC does seem to have eaten a big slice of premiere's cake down at the lower end of the market.

      Cinelerra compares well to the cost of a smoke seat, pity it's so hard to use.

    5. Re:Sorry by Overly+Critical+Guy · · Score: 1, Interesting

      Final Cut Pro is a widely adopted standard for people not using expensive Avids. Did you watch Cinderella Man by any chance? All done in Final Cut Pro. I don't know of anyone professionally using MainActor on Linux in any feature films.

      --
      "Sufferin' succotash."
    6. Re:Sorry by Anonymous Coward · · Score: 0

      i heard lord of the rings was done using linux

    7. Re:Sorry by EngMedic · · Score: 2, Informative

      lest we forget, Weta does all their video processing on massive linux clusters. I'd consider Lord of the Rings to be a pretty "professional video editing" example, wouldn't you?

      --
      filter: +3. Hey, look! all the trolls went away!
  17. Devfs removed by Saiyine · · Score: 5, Informative


    As they say in osnews, devfs seems to have been removed from the kernel.

    --
    Dreamhost superb hosting.
    Kunowalls!!! Random sexy wallpapers (NSFW!).

    --
    Hosting 20G hd, 1Tb bw! ssh $7.95
    1. Re:Devfs removed by diegocgteleline.es · · Score: 4, Informative

      not that many people is going to notice it - devfs wasn't really used in most of mainstream distros except 2 or 3. In some cases like Mandrake, they used it and then switched back.

      And it's not a surprise, linux's devfs implementation was broken from start, and the idea behind devfs isn't a relly good one. Fortunately, udev is much better...

    2. Re:Devfs removed by XO · · Score: 1

      er... ? devfs has been deprecated for several revisions now, and was hardly in use to begin with... ?

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    3. Re:Devfs removed by m50d · · Score: 1
      I can remember devfs being the next big thing, quite recently. People were saying it had huge advantages over the current system for /dev, was the future of linux, and it was a good idea to switch now.

      In fact, it was almost identical to what people are now saying about udev. Makes me less eager to switch. Linux seems to have so many of these false starts that you hear nothing but praise of and then afterwards people say they were broken all along.

      --
      I am trolling
    4. Re:Devfs removed by diegocgteleline.es · · Score: 1

      In fact, it was almost identical to what people are now saying about udev. Makes me less eager to switch. Linux seems to have so many of these false starts that you hear nothing but praise of and then afterwards people say they were broken all along.

      Well, devfs was better than nothing, and udev is better than devfs.

      I'm shocked that you seem to opose to getting things improved.

    5. Re:Devfs removed by ytm · · Score: 1

      I agree with GP. I have followed discussions about udev vs. devfs and still I don't see how udev is much better than devfs. These discussions along with final reason for pushing udev were concentrated on devfs weaknesses rather than udev superiority. E.g. messy code, race conditions and lack of maintainer. That only told me that devfs was in bad shape, nothing more.

      Devfs served me well. I'm not going to upgrade to a kernel without it anytime soon.

    6. Re:Devfs removed by ytm · · Score: 1

      They were not supposed to do it until 2.7.x split. How is this 2.6.x stable now?

    7. Re:Devfs removed by Anonymous Coward · · Score: 1, Informative
      not that many people is going to notice it - devfs wasn't really used in most of mainstream distros except 2 or 3. In some cases like Mandrake, they used it and then switched back.
      Gentoo used to rely on devfs but Gentoo users running the 2.6 kernel should switch to udev.
    8. Re:Devfs removed by Anonymous Coward · · Score: 0

      There's no 2.7 split. 2.6.x is now your "new features" release, with the 2.6.x.y patches adding bug/security fixes.

      There was an article on it a while back. Linus was disappointed in the fact that 2.5 didn't get enough testers, so they decided that from now on there was only going to be one kernel branch.

    9. Re:Devfs removed by diegocgteleline.es · · Score: 4, Insightful

      These discussions along with final reason for pushing udev were concentrated on devfs weaknesses rather than udev superiority.

      udev pushes all the device naming policy to userspace. Moving policy stuff to userspace is something that linux developers (and hackers of other OSes too) love because it's a much better design. That was the main reason for udev.

    10. Re:Devfs removed by iabervon · · Score: 2, Informative

      Seems is the right word; the only thing removed at this point is the option to enable it. The idea is to get the attention of people who are still using it but haven't noticed, because things continued to work with old config files.

    11. Re:Devfs removed by phsdv · · Score: 1

      I am running without devfs in my 2.6 kernel without any issues on both my PCs since a few months. No problems encountered so far!

    12. Re:Devfs removed by m50d · · Score: 1
      I'm shocked that you seem to opose to getting things improved.

      I'm not, I'm opposed to having to switch around my OS every other week. And I saw no benefit of devfs or udev over a simple static /dev.

      --
      I am trolling
    13. Re:Devfs removed by Wonko · · Score: 1

      I'm not, I'm opposed to having to switch around my OS every other week. And I saw no benefit of devfs or udev over a simple static /dev.

      Then don't change it around. Nobody forced you to use devfs. Nobody is forcing you to use udev. If you like the old school way of doing things, don't change.

    14. Re:Devfs removed by petermgreen · · Score: 1

      the debian installer (sarge etch and sid not woody) uses devfs, iirc due to diskspace issues on the root floppy or something like that.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    15. Re:Devfs removed by Rutulian · · Score: 1

      Uhhh, then I take it you don't use too many usb devices because running mknod everytime you want to plug in your usb camera is not what I would consider user friendly. And having /dev/hd* enumerate all the way out to k30 is also annoying when you have only one hard disk with three partitions on it.

    16. Re:Devfs removed by burner · · Score: 1
      E.g. messy code, race conditions and lack of maintainer.


      These are not insignificant concerns!
      --
      MRSH-Recording device, corned beef sandwich with kraut, seafaring bird, and the foamy top of a beverage.
    17. Re:Devfs removed by m50d · · Score: 1
      Uhhh, then I take it you don't use too many usb devices because running mknod everytime you want to plug in your usb camera is not what I would consider user friendly.

      Huh? The only time I've had to mknod is when I tried devfs. If you have to mknod the same node more than once it's devfs or udev that's causing your problem, not the solution. /dev/sda, /dev/sda1, and equivalents all the way up to sdg are all present and correct on my system, not that I plug in more than one at a time.

      And having /dev/hd* enumerate all the way out to k30 is also annoying when you have only one hard disk with three partitions on it.

      Marginally, but less annoying than having the permissions on them change around when you're not looking (udev), or the whole thing disappear when you reboot (devfs). Besides, if you don't use them you can delete them, then if you find you need them you can just mknod them again.

      --
      I am trolling
    18. Re:Devfs removed by m50d · · Score: 1
      Then don't change it around. Nobody forced you to use devfs. Nobody is forcing you to use udev.

      No, but they strongly recommend it. Words like "obsolete" are being bandied around, and I've known people not help in fora unless you're using devfs.

      --
      I am trolling
    19. Re:Devfs removed by Wonko · · Score: 1

      No, but they strongly recommend it. Words like "obsolete" are being bandied around, and I've known people not help in fora unless you're using devfs.

      Well, if you need to be looking for help in forums you should probably not worry this issue at all. You should just use what your distro uses. If your distro wants to continue to use devfs they can attempt to patch it into future kernels. It is something you shouldn't have to worry about.

  18. Re:How about a stable ABI? by Anonymous Coward · · Score: 2, Insightful

    As you may have noticed, this article is about the KERNEL. Changing your kernel is a very much geek thing to do. If there is any place you should expect to need the CLI to install something it is the kernel!

    Compiling and installing a new kernel isn't for everyone, that's why there are these collections of tested software known as "Linux Distros" where geeks get the software packaged nicely so you can use a GUI to do all your upgrading. If the CLI scares you so much and you want to use Linux, I'd recomend using Fedora or Ubuntu and sticking to standard packages.

  19. Re:How about a stable ABI? by 10Ghz · · Score: 3, Insightful
    I don't want to have to compile anything, ever. Just to make this clear, never.


    You don't have to. years ago when I used SuSE, I never ever compiled anything, and I had no problems

    Come up with either something akin to Windows where I click on a standard installer, or make it like Mac where I just drag and drop the folder.


    Linux does have something similar. How about Yast or Synaptic or up2date? True, it's not identical to way things are done in Windows or OS X. But Linux is not Windows or OS X.

    Any time I'm forced to drop to a command line, you as a developer have failed.


    I don't think the kernel-developers are to blame if some GUI-tool doesn't do the job. They work on the kernel, not on the GUI.

    Again, you have failed.


    Failed at what? To satisfy the whims of some random user who propably hasn't paid one dime for the software he's using? Here's a hint to you: they (the developers) don't owe you anything.
    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  20. Is this a joke? by Anonymous Coward · · Score: 0

    Linux Torvalds announced the release of the 2.6.13 Linux kernel.

    If it is, it's funny, if it's not...well, it's even funnier!

  21. More kernel crashes as of late? by suso · · Score: 4, Interesting

    I've been using Linux since 2.0.27. It has usually been generally quite stable for me. But recently, I've been encountering more and more kernel crashes. For trivial things to, like a kernel crash when I try to use ifconfig yesterday when setting up a machine. And random crashes on one of my servers that doesn't seem related to RAM. I know that some kernel versions have "problems", but it seems to be more than that. A recent trend of unstability. Can anyone else who has been using Linux for a significant amount of time attest to this?

    1. Re:More kernel crashes as of late? by arkhan_jg · · Score: 1

      Can't say I've noticed kernel problems of late, and I tend to use the ck branch. Been having freezes, but that was heat-related in one case, and dodgy nvidia drivers in the other.

      --
      Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
    2. Re:More kernel crashes as of late? by tomstdenis · · Score: 1

      I've had a few lock ups recently but I tend to blame the GLX module [happens with GL enabled XMMS plugins]. The kernel doesn't lock but XMMS basically rapes the cpu.

      As for instability I've been able to boot/run Linux on pretty much anything. Laptops are fairly bad for standards compliance and some cheaper mobos like MSI are not too friendly.

      Stick with ASUS or Gigabyte mobos, use dlink or broadcom networking, use nvidia GFX, etc... basically use HW from people who are linux friendly. :-)

      Tom

      --
      Someday, I'll have a real sig.
    3. Re:More kernel crashes as of late? by suso · · Score: 1

      Right, I was also having the same problem with nvidia drivers and GL in general. But I'm talking about kernel panics, from the console (not even running X).

    4. Re:More kernel crashes as of late? by tomstdenis · · Score: 1

      I'm running 2.6.12.5 on all my boxes [which include a Presario laptop, AMDX2 desktop, P4 Prescott desktop, P4 Smithfield desktop, P4 Northwood and a few AMD Semprons] with various configurations [both kernel and hardware].

      My only complaint with 2.6.12.x is that the timer is poorly based on TSC [hint: cpufreq changes the TSC rate!!!]. So I keep losing time. Fortunately I've mitigated this through a */10 in my crontab and I run rdate.... it's a poor fix but for now will do.

      Tom

      --
      Someday, I'll have a real sig.
    5. Re:More kernel crashes as of late? by Anonymous Coward · · Score: 5, Insightful

      Yes, unfortunately I have the same experience. I used to rely on the vanilla Linux kernel tree being rock solid. Now I feel I must stay many months behind in order to avoid potentially catastrophic problems. Considering the number of bug fixes, particularly w/ regard to security, that can show up in new kernel releases, it's not an ideal situation: you're damned if you do, and you're damned if you don't.

      I've recently had networking go south when packets were being written to localhost. Some adaptec scsi stuff was recently messed up, apparently now fixed in 2.6.13 - but no way I'm going to try it until it's been out for a while. I've seen problems with quotas in combination with ext3. I recently started experiencing connection tracking weirdnesses with an iptables setup I've used at home for probably a couple of years. I've seen versions where network latencies would grow ever so slowly until they reached a critical threshold that sent my server(s) spiraling into oblivion. Yes, I file bug reports. Yes, problems get fixed. But at the same time, new ones show up. Sometimes bad ones.

      I've become accustomed to rebooting Windows to fix problems, but that's exactly why I use Linux - because it was rock solid. I won't say that anymore, and it bums me out big time. I like new shiny objects too, but not at the expense of stability. Especially not on servers, which is where Linux has made the most headway.

      The problem with the current versioning system is that even if there is a bug-fix only decimal release, and even if there is only a two week window to introduce new features, the bug fixing won't get done. Why? Because new features are more fun than fixing bugs. Even if I can't submit a new feature until several months from now, that doesn't mean I won't work on it in leiu of fixing bugs.

      Linus should freeze the 2.6 kernel series against *any* new features at all, for a period of about a year. All work should be on increasing stability, ironing out bugs, improving device drivers, and other such menial housekeeping. The kernel contributers who really buck up, get to work, and help with this effort should get big karma bonuses from Linus. Those who hang back and work on their own thing should be pushed down a level in future kernel submission evaluations.

      Sorry to be so negative, but I really hope this gets better. I'm a huge fan, but I have been wasting way too much time lately dealing with problems that end up being way beyond my control. When there is a problem with my systems, I want it to be my fault, because then I can do something about it.

    6. Re:More kernel crashes as of late? by RAMMS+EIN · · Score: 1

      ``broadcom networking, ... basically use HW from people who are linux friendly.''

      Hmm, Broadcom haven't been that Linux friendly lately with their wireless chipsets. People I know have bought Linksys gear with Broadcom chipsets, and were forced to use ndiswrapper because neither Broadcom nor Linksys will release drivers or specs.

      --
      Please correct me if I got my facts wrong.
    7. Re:More kernel crashes as of late? by makomk · · Score: 1

      I think there's a kernel option to change this. Take a look at the Gentoo forums where there have been various threads on the matter. (I don't know much about this; my PC doesn't support cpufreq, so it's not a problem for me.)

    8. Re:More kernel crashes as of late? by ookaze · · Score: 1

      I attest that I have seen a surge of unstability on my Linux machines.
      And I can also attest that all the kernel panics or lock ups where due to hardware problems : SCSI and IDE disks crashing; IDE cdroms dieing, killing the IDE port entirely; mobo dieing.
      Actually, I think this must be due to the fact that my Linux machines run 24/24 7/7 since 2001 and that some components had never been replaced.

    9. Re:More kernel crashes as of late? by coolGuyZak · · Score: 1
      Linux has become somewhat less stable of late, and that's the number one reason for this "tweak: of the development model. Since the BitTorrent days, you could see large flurries of patches being shipped in... And many (certainly not all) of those patches have been feature-upgrades or systems-rewrites.

      Around the realease of 2.6.11, they added another "point" to the releases, in an effort to increase stability... which is why you saw 2.6.12.x releases. This helped the situation somewhat, but developement was still somewhat frenetic... Basically, this led to a degeneration of the overall quality of the code.

      However, the developers know this, and (thankfully) they're doing something about it. :D So, rest assured, the solid kernel you're used to will be making a comeback soon.

    10. Re:More kernel crashes as of late? by hackstraw · · Score: 4, Informative


      Are these crashes repeatable or do they have any kind of similarity?

      I've been using Linux since 0.9x, and its been very stable for me over the years with a few exceptions that were experienced by other people as well.

      My first assumption when I have a seemingly random kernel crash with no meaningful data from the OOPs or other messages is that there is a problem with my hardware.

      For me, the Linux kernel is more robust than electrical power or hardware.

      YMMV.

    11. Re:More kernel crashes as of late? by Triffid_Hunter · · Score: 1

      my desktop box (running 2.6.12-gentoo-r6) has a couple of unkillable processes..

      apart from that my desktop and two servers have been rock solid stable since 2.6.7 when I set them all up

    12. Re:More kernel crashes as of late? by vranash · · Score: 1

      I've been using it since 1.2.x/1.3.xbeta series and I've noticed with the 'supposed' increase in features, the testing for them has seemingly gone in the toilet... 1.x series stuff I had basically no issues with kernel-wise unless I was using direct access hardware programs (like anything using svgalib), and it's quite possible that stuff just crashed my terminal (I still didn't know a lot back in those days, and the reset button was the quicker fix... until it detected a dirty unmount and spent 10 minutes checking the filesystem ;p)

      Seriously though 2.2 was mostly stable, although usb mass storage was borked in the older sub 2.2.19 kernels.

      2.4 was mostly stable, way more featureful, but not quite as good as 2.2 (I actually found the 2.4.0 test kernels stabler than anything before 2.4.6 or after 2.4.9, up until like 2.4.20, and let me tell ya, the 2.5 devel kernels sucked until the .9x releases.

      2.6 I honestly can't remember how the first few pub releases were, although I think I went back to 2.4.20 or 2.4.22 waiting for them to stabilize a bit.

      As a further note here, support for sparc32 has sucked since 2.2.18 or so, and even most patchsets against newer kernels don't allow SMP on Sparcstation 20's (although some of the 2.4 kernels will run if compiled for UP on them, 2.6 still hasn't worked properly for me.)

      Mind you this is just my views, but I've been seriously considering migrating a number of my boxes off linux because of these, as well as other annoying habits (like changing the freaking module tools between 2.4 and 2.6 leaving a gap during which they couldn't both be installed, ugh. Plus the whole DevFS being added then removed thing, which I actually found useful for automatically keeping my dev directory relatively clean).

    13. Re:More kernel crashes as of late? by tomstdenis · · Score: 1

      yeah granted their wireless support sucks but their tg3 based gige cards are ok.

      Though I like the dlink 530-T card better. It's $33 CAD, hasa driver in linux [sk98lin] and gets me proper network speeds [I can write over network to another HD at 20MiB/sec as opposed to 9.8MiB/sec or so].

      Tom

      --
      Someday, I'll have a real sig.
    14. Re:More kernel crashes as of late? by fire-eyes · · Score: 1

      Can anyone else who has been using Linux for a significant amount of time attest to this?

      Been going on 8 years now, and I tend to stay right on the edge of stable. I have not seen these issues, except in a system with a shitty power supply.

      Replacing it took care of the issues.

      --
      -- Note: If you don't agree with me, don't bother replying. I won't read it.
    15. Re:More kernel crashes as of late? by m50d · · Score: 1

      I haven't been a long time user, but all I can say is that I never had these random crashes with 2.4, and with 2.6 I get a lot, as bad as windows 98 in some cases. If you can, I'd say stick with 2.4 until 2.6 stabilises.

      --
      I am trolling
    16. Re:More kernel crashes as of late? by twilight30 · · Score: 1

      For my part I have to agree with you. It's ameliorated somewhat by using Debian stable (this will change tonight as I'm finally getting DSL in) but Debian has got its own set of irritating problems from the flip side of shiny new instability.

      I am seriously thinking about moving over to FreeBSD. I don't care about the trendiness factor at all; I just want my stuff to work consistently at as high performance as it can muster.

      --
      ========================================
      Death will come, and will have your eyes
      -- Pavese
    17. Re:More kernel crashes as of late? by bfields · · Score: 4, Insightful
      I've been using Linux since 2.0.27. It has usually been generally quite stable for me. But recently, I've been encountering more and more kernel crashes.... Can anyone else who has been using Linux for a significant amount of time attest to this?

      Not me.

      But it's very hard to generalize from one person's experience to any general "recent trend of unstability." Most of the bugs are in drivers, so people's experiences tend to be highly dependent on exactly which hardware they have.

      --Bruce Fields

    18. Re:More kernel crashes as of late? by archen · · Score: 2, Interesting

      I use 2.6 on my desktop machine at home and I'm quite happy with it, but I'm glad I moved from Redhat 7.3 to FreeBSD. At the time it was a tough call between moving to another Linux distro and FreeBSD, but I decided to go with BSD for various reasons. Then 2.6 comes out, fine and dandy. But they keep adding stuff to it and it never stabalizes. Even worse is you finally get a stable version for your situation, and then you need to get a new version for security fixes. Ugh!

      Linus needs to branch the tree and get the hell OUT of 2.6 and give us our stability back. Seriously, I don't know why everyone is so scared shitless about incramenting a (minor) version number every year or two. Kernel stability needs to be an absolute priority. We already have enough issues with X, and Window managers and other software crashes in the Linux world, but with no solid foundation to build on, we have a situation not that far from Windows 9x.

    19. Re:More kernel crashes as of late? by iabervon · · Score: 3, Interesting

      I've been using it since 1.2.13, and my experience has been the opposite: a 2.0.x had a "ping of death" bug; I skipped 2.2.x until I already needed features not available in it; 2.4.x was generally stable; early 2.6.x had a bug where it would sometimes not set up the keyboard or mouse correctly; and recent 2.6.x has had no problems at all.

      Have you tried reporting these crashes? I can't find anything about ifconfig triggering crashes. They can't test everything themselves, because they don't have every hardware configuration, so it's important for people who do to tell them when something is wrong.

    20. Re:More kernel crashes as of late? by jrumney · · Score: 1

      I've yet to see a 2.6 kernel that doesn't crash on boot on my PC. I'm still using 2.4.31, since 2.6 seems to be another development branch, which is what I thought 2.7 should be.

    21. Re:More kernel crashes as of late? by Thundersnatch · · Score: 1

      Hmmm... the Linux kernel was initially fast, stable, and built by a very small number of very smart people. However, it gets more and more unstable as new features are added and support for more hardware is added. The development process becomes unmanageable, because hundreds of developers are spread across the globe, speak different languages natively, and communitacate at irregular intervals. Each developer has pet features and subsystems they want to work on, while skimping on other "grunt work" tasks. Some silly mistakes are made. But backwards compatability must be maintained at all costs - we can't go around breaking applications from 10 years ago, no matter how stupid added experience makees those decades-old design decisions appear.

      This sounds remarkably like the development history of another popular OS...

    22. Re:More kernel crashes as of late? by Anonymous Coward · · Score: 0

      "I've seen versions where network latencies would grow ever so slowly until they reached a critical threshold that sent my server(s) spiraling into oblivion."

      ARRRRGHHH!!!
      So it IS a bug. I'm only a network neophyte so I tend to assume really freaky things are my own fault. Thanks.

    23. Re:More kernel crashes as of late? by twilight30 · · Score: 1

      Absolutely. With all the inotify/dnotify/whatever the hell it is, I've noticed that Linux performance -- honestly -- is not far off Mac System 7.

      And not better either. Worse.

      --
      ========================================
      Death will come, and will have your eyes
      -- Pavese
    24. Re:More kernel crashes as of late? by Mad+Merlin · · Score: 1

      Did you try using ntp? It's designed to deal with clocks that gain or lose time. Even beyond that, it'll keep your clocks set properly.

    25. Re:More kernel crashes as of late? by Hurricane78 · · Score: 0

      are you using framebuffer support? this killed my logger (metalog) very often and createy various oopses adn problem. I can't recommend console framebuffers at all anymore. too dangerous...

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    26. Re:More kernel crashes as of late? by Anonymous Coward · · Score: 0

      If you're having the same problem I was, and this was several versions ago, the problem only occured if the network drivers were statically linked into the kernel. Compiling and loading them as modules circumvented the problem.

    27. Re:More kernel crashes as of late? by iabervon · · Score: 1

      Actually, the biggest source of bugs in the 2.6.13 process (hopefully all fixed before release, but you never know) was that the PCI setup code was changed, because the old code was inherently flawed and didn't work on a lot of laptops, while the new code does work, but places more correctness requirements on the drivers. So lots of pre-existing driver bugs started actually causing problems.

      As you say the first time, when bugs occur, they get fixed, but things do get broken temporarily. People actually are responsive to bug reports when they're made. People generally feel most motivated to fix reported bugs, less to write new features, and very little to fix bugs that nobody knows about. And the problem is really bugs that are uncovered by correct changes to other code, and you want these to be fixed before they're discovered, which is obviously not going to happen. Combing the source for bugs is not going to be possible, because most of the bugs that can be found by looking at them have already been found and a lot of bugs are cases in which the kernel fails to handle obscure hardware correctly or fails to work around hardware bugs.

      The stable series is an attempt to create releases where bugs are hacked over (because fixing them would reveal other bugs) and no new bugs are introduced. That's about the best you can reasonably get in the modern world of non-compliant hardware and unimplementable specifications.

    28. Re:More kernel crashes as of late? by at_slashdot · · Score: 1

      I've been using Linux only for a little bit more than one year on different hardware and I never had a kernel crash.

      --
      "It is our choices, Harry, that show what we truly are, far more than our abilities." -- Prof. Dumbledore
    29. Re:More kernel crashes as of late? by GloomE · · Score: 1

      Boot a 2.6.9 or 2.6.10 kernel with devfs.
      Unplug your USB Modem (CDC ACM module).
      Wait for the kernel panic.

      Not even confined to modems, the USB hotplug code was broken and was not clearing references correctly.

      Stoopid

    30. Re:More kernel crashes as of late? by Anonymous Coward · · Score: 0

      2.6.12.5 has been good for me as well (on a Thoroughbred workstation and a Thinkpad T42 with a PM Dolthan)

      Your TSC problem could be fixed by using the HPET timer (if you have one) or the ACPI timer.

      commrade

    31. Re:More kernel crashes as of late? by Anonymous Coward · · Score: 0

      The stable series is an attempt to create releases where bugs are hacked over (because fixing them would reveal other bugs) and no new bugs are introduced.

      You're describing the 2.4 series kernels, not 2.6. The stable kernel series used to be just that, stable, meaning new features were eschewed in favor of refactoring code and doing the kind of optimization you describe, which does indeed turn up bugs (which can then be squashed). The old way was better. New features should wait until 2.7, or 2.6 is going to give 'stable' a bad name.

  22. Re:Why aren't we at 2.7 yet? or 2.8? by epaton · · Score: 1

    2.7 would be the unstable version, this is currently being done by a branch of the 2.6 kernel which was designed to be expanded and have features ported back into it.

  23. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    Hi! Where else have I seen your _exactly_ same points? Do you get paid for doing this?

  24. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    You will never, ever, become successful on the desktop until idiocy like this is exorcised from the OS

    Well, it sounds like we've got you out of the way, so we must be getting close.

  25. Well, Yes! by scsirob · · Score: 1

    It does..

    --
    To Terminate, or not to Terminate, that's the question - SCSIROB
  26. Yes but... by Anonymous Coward · · Score: 1

    Does it run linux?

    1. Re:Yes but... by Anonymous Coward · · Score: 0

      No, I'm afraid not.

  27. 2.6 a year and a half old but... by SuperBanana · · Score: 2, Informative
    I wish Linus would arrive at a policy and just stick with it instead of all these gyrations of "we'll use this method from now on...no wait...we'll use this one from now on...and by the way I want everyone to switch revision control systems now...oh wait...sigh.

    This PCI code rewrite doesn't bother me as much as some of the recent 2.6 releases including new drivers for obscure proprietary hardware.

    A large number of organizations (as well as Debian Stable and Redhat) still use 2.4. It's pretty pathetic. 2.6 was released in December of 2003, over a year and a half ago. It offers significant performance advantages over 2.4 in many areas. Maybe instead of spending time switching policies, kernel developers should be consulting with end-users (note: this does not mean just/predominantly IBM and the other big fish. It means people like US, too) to find out why we're not using 2.6. Aside from security patches, any effort on 2.4 development/maintenance needs to stop. It's a brain drain, and active maintenance is encouraging people to be lazy in upgrading (and that's probably part of the issue).

    Right now 2.6 is a lame-duck kernel, and if they keep trudging on and release the next stable without looking at why 2.6 isn't the defacto kernel of choice today, Linux will be rather fubar'd.

    1. Re:2.6 a year and a half old but... by XO · · Score: 1, Insightful

      Why would the developers care one bit about what's going into use in old ass distributions, by default?

        Debian Stable = things that have been 'thoroughly' tested for like 2 years or more. Hell, even using Debian Unstable, most of your software is still incredibly out of date.

        Red Hat isn't quite as slow. But pretty darned slow.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    2. Re:2.6 a year and a half old but... by JonJ · · Score: 2, Informative

      A large number of organizations (as well as Debian Stable and Redhat) still use 2.4. It's pretty pathetic. Debian provides both a 2.6 and a 2.4 kernel when you install debian stable, if you don't like it, use another distro. RHEL 3 was released quite some time ago, and the 2.4 kernel that was provided was probably heavy patched, since RedHat has quite a number of kernel hackers employed. RHEL 4 features a 2.6 kernel. If the only examples you could come up with of distros still using the 2.4 kernel, I'd say pretty much every distro uses 2.6. SUSE does, Mandrake does, Slackware has it as an option, debian has the option, Ubuntu uses 2.6, and so on.

      --
      -- Linux user #369862
    3. Re:2.6 a year and a half old but... by Pastis · · Score: 1

      Aside from security patches, any effort on 2.4 development/maintenance needs to stop. It's a brain drain


      It's a brain drain if you are in a resource limited environment. The resources working on 2.4 today would maybe not work on 2.6 if the 2.4 work was taken out from them (this is not even possible, given the open nature of the kernel).

      All my machines run on 2.6 and I have no issues with it.

    4. Re:2.6 a year and a half old but... by Anonymous Coward · · Score: 1, Informative

      Sorry, but that's just wrong. There isn't a single distribution (that matters, anyway) whose primary kernel is 2.4, now-a-days. You're talking out of your ass on this one.

      RedHat has been on 2.6 since Fedora Core 2, which was launched in April of 2004 -- about 4 and a half months after 2.6.0 shipped. Debian offers both a 2.6 kernel and a 2.4 kernel, but it comes as no surprise they support 2.4 still -- they're probably the only mainstream distro that has never shipped X.org in any officially released product. Debian is very conservative about its released products, so they tend to be a year or two behind others, in what concerns versions.

      All other large distros switched to 2.6 a /long/ time ago -- SuSE, Mandrake, whatever.

    5. Re:2.6 a year and a half old but... by ckaminski · · Score: 1

      The reason why so many people are still using releases like RHEL 2 is that there's no compelling need to upgrade. The machine was stable then, why take it down and upgrade it for no reason?

    6. Re:2.6 a year and a half old but... by pyrotic · · Score: 1

      RHEL 4.1 includes kernel 2.6.9-11.ELsmp

      Redhat version 4 has been out since May. I'm just about to put one of those boxes into production use, so it had better be stable.

    7. Re:2.6 a year and a half old but... by Flying+Purple+Wombat · · Score: 1

      A large number of organizations (as well as Debian Stable and Redhat) still use 2.4.

      Big companies don't like to change things. They don't want to be on the bleeding edge, due to perceived risk or some other nonsense. At my employer (a mega insurance company) there are still desktops and servers running Windows 2000, because it's too risky to upgrade. "They" are afraid something will break.

      None of our servers run the latest Solaris, AIX, DB2, WebSphere, Java VM or anything else for the same reason. No production Linux in this shop, but if there were, it would be RHEL 9.

      --
      If God had meant for man to see the sunrise, He would have scheduled it later in the day.
    8. Re:2.6 a year and a half old but... by Pastis · · Score: 1

      Hell, even using Debian Unstable, most of your software is still incredibly out of date.

      Could you give some examples?

      I run Debian unstable and I don't think it is 'incredibly out of date'.

      I have the latest gaim (1.5.0), evolution, gnomemeeting, firefox, mono (1.18.2), the latest gnome (2.10), the latest kernel as of yesterday (2.6.12)...

      The latest openoffice 2.0 beta can be obtained from experimental, but openoffice 2.0 is not yet officially released.

    9. Re:2.6 a year and a half old but... by m50d · · Score: 1

      There is a simple reason why people don't use 2.6. It isn't stable. That's all there is to it. When the kernel devs finally get their act together and release a 2.6 that doesn't crash, that's when you'll see people switch.

      --
      I am trolling
    10. Re:2.6 a year and a half old but... by Anonymous Coward · · Score: 0
      Aside from security patches, any effort on 2.4 development/maintenance needs to stop. It's a brain drain


      Yes, because as we all know, the best way to speed up a project is to put more programmers on it.

    11. Re:2.6 a year and a half old but... by diegocgteleline.es · · Score: 2, Informative

      A large number of organizations (as well as Debian Stable and Redhat) still use 2.4.

      Debian didn't care about switching to 2.6 because that would have delayed sarge even more...we all know debian. Redhat Advanced Server 4.0 uses 2.6 not 2.4, suse's versions for servers too, so what is your point?

      As far as I know, except debian there's no major distro using 2.4 as default kernel.

      Right now 2.6 is a lame-duck kernel

      Wrong. Ubuntu, redhat, fedora, mandriva, suse, gentoo, knoopix, all of them use 2.6. I don't know where you got that impression, looking at current distros it's pretty clear 2.6 is the preffered kernel version for most of people.

    12. Re:2.6 a year and a half old but... by andyross · · Score: 1
      A large number of organizations (as well as Debian Stable and Redhat) still use 2.4.

      This isn't correct. The most recent Red Hat Enterprise Linux release (6 months old) is using the 2.6 kernel, and of course the Fedora releases have been shipping 2.6 since shortly after it was released. Debian Stable (released June 6th) ships with the choice of 2.4.27 or 2.6.8, and of course many users have been using the unstable distribution under the 2.6 kernel for the past several years.

    13. Re:2.6 a year and a half old but... by ookaze · · Score: 2, Interesting

      some of the recent 2.6 releases including new drivers for obscure proprietary hardware

      What is this nonsense ? You don't want Linux to support hardware ? Linux can not be usable by just supporting standard hardware you know ?

      A large number of organizations (as well as Debian Stable and Redhat) still use 2.4. It's pretty pathetic

      Isn't that a good thing ?!!! You sound like a troll. What is pathetic with that ?!! And FYI, RH does not use 2.4 as default anymore, and their 2.4 kernel included backports from 2.6. Debian Stable supports both 2.4 and 2.6, you're several weeks late.

      Maybe instead of spending time switching policies, kernel developers should be consulting with end-users to find out why we're not using 2.6

      What for ? Are you stupid ? Clearly, you are not representative of Linux users : we use what is provided by our distro, and they supported Linux 2.6 since a long time ago. Most distros do actually support Linux 2.6, and FYI there was a race about which distro would support it first when the kernel was out. I think you can not understand that because you think a distro can't support 2.4 and 2.6 at the same time. This thinking must come from the people that want you to believe that apps running on 2.4 are incompatible with apps running on 2.6. I tell you : these people are MS shills and they are wrong.

      Aside from security patches, any effort on 2.4 development/maintenance needs to stop. It's a brain drain, and active maintenance is encouraging people to be lazy in upgrading.

      You have to let go of this Windows mentality that you are forced to upgrade even when it works. Linux 2.4 still works pretty well, it was still running circles around every version of Windows for example. To this day, MS still have to take very old RH releases with Linux 2.4 (without 2.6 backports) to compare to its latest Win2003, because of that.
      So why should people change when it's not broken ?

      Right now 2.6 is a lame-duck kernel, and if they keep trudging on and release the next stable without looking at why 2.6 isn't the defacto kernel of choice today, Linux will be rather fubar'd.

      Please stop making a fool of yourself. Even the more specialised distros like Geexbox use the latest Linux 2.6 refinements. You are 3 years late at least ! Like most MS shills. I don't imply that you are one BTW, but you are pretty clueless like them.

    14. Re:2.6 a year and a half old but... by Anonymous Coward · · Score: 1, Insightful
      Big companies don't like to change things. They don't want to be on the bleeding edge, due to perceived risk or some other nonsense. At my employer (a mega insurance company) there are still desktops and servers running Windows 2000, because it's too risky to upgrade. "They" are afraid something will break.


      Nonsense? Ah, so you've never seen an update screw the pooch or a supposed migration that was supposed to be easy as pie go totally awry on a mission critical system.

      None of our servers run the latest Solaris, AIX, DB2, WebSphere, Java VM or anything else for the same reason. No production Linux in this shop, but if there were, it would be RHEL 9.


      Yeah, it's called "if it works, don't fuck with it unless you have a damned good reason." Just because a newer version comes out is not a valid reason unless it supports a feature that your shop cannot live without.
    15. Re:2.6 a year and a half old but... by Ghostx13 · · Score: 1

      "due to perceived risk or some other nonsense"

      Not perceived risk, actual risk. Lets say I'm a major share holder of company X, and the CIO decides he's going to deploy gentoo with the latest kernel, and keeps the kernel at the bleeding edge, and lo and belhold they discover a bug in the kernel. Said bug leads to down time. Down time leads to lost revenue. Guess who isn't going to have a job? Right! The CIO. And why? Because he didn't exercise due dillegence in performing his job.

      On the other hand, if we have a field-proven install of a 2.4 kernel, or say Solaris 8, and there is a bug discovered, well thats just the cost of doing business.

      This might not be the most interesting method, or the one that leads to the most innovation, but this is business, not a university research lab.

    16. Re:2.6 a year and a half old but... by mrchaotica · · Score: 1
      Why would the developers care one bit about what's going into use in old ass distributions, by default?
      Didn't you read the post you're replying to?
      Aside from security patches, any effort on 2.4 development/maintenance needs to stop. It's a brain drain, and active maintenance is encouraging people to be lazy in upgrading (and that's probably part of the issue).
      That's the point: he would like the developers to concentrate on the new technology instead of wasting time on the old. I agree with him, especially considering that there is no barrier to upgrading. The way I see it, one of the greatest strengths of Free Software is that everyone can stay on the cutting edge (or at least the newest stable version) and the system can always continue to improve instead of being stuck with bad designs for backwards compatibility.
      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    17. Re:2.6 a year and a half old but... by JahToasted · · Score: 1

      Haha, I can remember the exact same things being said about 2.4 being a lame duck (or maybe greased turkey?) It wasn't until around 2.4.15 or so that everyone started using it, though redhat used a heavily patched version a little sooner.

    18. Re:2.6 a year and a half old but... by ultranova · · Score: 1

      I agree with him, especially considering that there is no barrier to upgrading.

      As one who upgraded a RH9 system to 2.6 manually, I must say that this is quite untrue. Module utilities, automatic module loading and RPM all broke. Maybe I just couldn't do things properly, but that doesn't change the fact that there most certainly was a barrier.

      The way I see it, one of the greatest strengths of Free Software is that everyone can stay on the cutting edge (or at least the newest stable version) and the system can always continue to improve instead of being stuck with bad designs for backwards compatibility.

      If you know of a distro in which this is possible, please tell me. I'm still stuck on RH9 and know of no simple way to update to FC - and even if I did, wouldn't that just be outdated soon too ?

      No, wiping everything and installing from scratch isn't an acceptable option, since I'd lose my data - not everyone can afford backups.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    19. Re:2.6 a year and a half old but... by dasunt · · Score: 2, Insightful

      I'm using 2.4 under Debian (Woody, or Old-Stable) for the past 2-3 years.

      It works with my hardware, and I consider it a proven kernel.

      Why should I upgrade a working kernel?

    20. Re:2.6 a year and a half old but... by Donny+Smith · · Score: 1

      > there is no barrier to upgrading.

      Like, you leave the /home partition as-is, reformat the rest and re-install the OS, is that it?

      That's quite funny.

      Upgrading is the WORST barrier to OS adoption there is.

    21. Re:2.6 a year and a half old but... by Donny+Smith · · Score: 1

      Well, not everyone is a student.

      Most of servers we maintain are kernel 2.4 and we're not in a hurry to upgrade at all.
      To database customers, we still recommend kernel 2.4.

      >Wrong. Ubuntu, redhat, fedora, mandriva, suse, gentoo, knoopix, all of them use 2.6.

      Sorry, but that doesn't prove shit. It only indicates that:
      a) marketing (and novelty) takes precedence over stability
      b) "bleeding edge" distros aren't suitable for enterprise use (even when they're stable; if for no other reason, then because they change too fast)

    22. Re:2.6 a year and a half old but... by diegocgteleline.es · · Score: 1

      To database customers, we still recommend kernel 2.4.

      Redhat and suse recommend 2.6. I'll take their advice instead...

    23. Re:2.6 a year and a half old but... by mrchaotica · · Score: 1
      If you know of a distro in which this is possible, please tell me. I'm still stuck on RH9 and know of no simple way to update to FC - and even if I did, wouldn't that just be outdated soon too ?
      Gentoo, for one. Just do `emerge -uDav world` every once in a while (along with the other related commands to fix config files and whatnot).

      Although I haven't used it, I'm told Debian (and maybe other apt-based distros) can be kept up-to-date with `apt-get upgrade` or something.
      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    24. Re:2.6 a year and a half old but... by mrchaotica · · Score: 1

      I was thinking of something more along the lines of putting `apt-get upgrade` or `emerge -uDav world` in a cron job.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    25. Re:2.6 a year and a half old but... by richlv · · Score: 1

      slackware.
      2.6 is in testing, 2.4 - default. there is full support for 2.6.

      generally i tend to use 2.6 for workstations and 2.4 for servers that i would prefer to put up and forget :)

      --
      Rich
    26. Re:2.6 a year and a half old but... by ccp · · Score: 1

      I don't know where you got that impression

      In Astroturf School, where else?

    27. Re:2.6 a year and a half old but... by Donny+Smith · · Score: 1

      >Redhat and suse recommend 2.6. I'll take their advice instead...

      Of course they do. And perhaps it's good enough for most people.

      But, look at the relevant newsgroups and you'll see the truth - crashes, problems with performance, filesystems, etc.

      Kernel 2.4 = peace of mind.
      Does it handle extreme workloads better than kernel 2.6? No. How many people run extreme workloads? About 1% of all customers.
      Is kernel 2.4 more stable for almost all database programs out there? Yes.

    28. Re:2.6 a year and a half old but... by XO · · Score: 1

      Automatic upgrade from RH7 to RH8 nuked my system. Automatic upgrade rom RH8 to RH9 nuked my system. A hacked up form of making apt-get work in RH9 got me a successful upgrade from RH9 to FC1. Automatic upgrade from FC1 to FC2 nuked my system. Automatic upgrade from FC2 to FC3 nuked my system.

        That was for one of my two boxes that ran Linux, that one running for about 5 years.
        The other one was a Debian unstable, that "ran" for about 3 years, but I had to discontinue doing regular updates on it because it would take 12-16 hours to process the updates regularly.
        So, I'd only do system updates every couple of weeks when I'd be going away for a weekend. OF course, I'd always come back, and the auto-upgrade that wasn't supposed to ask any questions, and just do the things it was supposed to do was inevitably, and always, sitting there waiting for my input after about the 10th file.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    29. Re:2.6 a year and a half old but... by Minna+Kirai · · Score: 1

      I run Debian unstable and I don't think it is 'incredibly out of date'.

      Debian sid still (as of last week) doesn't have KDE 3.4 yet, meaning it's KDE filebrowser doesn't permit removing media like CDs or USB keys.

    30. Re:2.6 a year and a half old but... by Pastis · · Score: 1

      According to http://packages.qa.debian.org/k/kdelibs.html and
      http://packages.qa.debian.org/k/kdelibs/news/3.htm l

      it seems like 3.4.2 started entering unstable more than 2 weeks ago. And you could have gotten 3.4.1 from experimental end of May.

      The delay may have been partly incured by the gcc 4.0 upgrade.

  28. Re:How about a stable ABI? by arkhan_jg · · Score: 1

    Do you have to post this in EVERY goddamn thread about linux? Enough already.

    Use SuSE or Mandriva. No compilation necessary, pretty user-frontends for config, and a big thick paper manual in the box in SuSE's case. If you don't want to have to make any choices, try ubuntu.

    --
    Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
  29. Re:How about a stable ABI? by ooze · · Score: 1

    A) For any distro that considers itself a desktop distro you don't have to compile a kernel. Hell, evem when you use debian you don't have to compile a kernel. Needing to complile is only for those who want to do something very specific or for those who want to have "full control", which are very wide spread in the Linux community for some weird reason. And it is like this for at least 5 years already.

    B)Anytime there is something I can't do automated, because there is no proper comand line or scripting tool, then the developer has failed. Right, computers are becoming used by virtually everyone. So the things everyone has to do with them (like opening doors in a car, and sitting into it) need to be simple. But if you want do real work (like actually driving a car), you need lots of training and learning, and preferably a test and a licence (this was kidding now) anyway. With computers it is far too often that people who only were passengers so far want to do a car mechanics job, and complain that it's hard, and that they fucked up their computer. But is sealing the whole chassis the solution? Access to the engine must be there...and not everything can be done from the backseat.

    C) A little comparison. Whole company staffs, schools, public offices etc. get company sponsored, and even Microsoft sponsored training programs for Microsoft products several times every year. Yet most of them still are inept with computers and fail to grasp such simple concepts as file versioning. For Linux such things are just developing at the moment. Yet, there are millions of very able linux users out there who learned all they learned by only this very documentation and mailing lists you just trashed so passionately. Something's odd.

    --
    Just because I can imagine doing a hippopotamus, doesn't mean I'd like to do it.
  30. Re:How about a stable ABI? by ledow · · Score: 4, Insightful

    A) Fine. So we'll distribute one binary version of the kernel. It won't work as fast. It'll be hundreds of megs in size. It will take ages to load as it checks for every single known piece of hardware. You've just lost all the speed/memory advantage of having a tailored kernel. Alternatively, it'll come with a hundred modules. It'll also never be x64 optimised or, for that matter, able to work on every machine (some options crash some machines, while the opposite options may crash others) and APM/ACPI will NEVER work on some machines.

    B) Fine. You come up with a GUI that can allow me to find files modified on the second Tuesday of every month between May 1, 1946 and June 27, 1978, which contain the words 'secret' and 'report' within 26 characters of each other, sort them by date, and replace any occurence of the word 'anchovie' by 'dead bug'. Some things GUI's just cannot do, some things GUI's do that are just command line interfaces in a fancy coloured textbox, some things GUI's can do once in the time that someone who knows the command can do twenty times.

    Secondly, how do you expect a GUI to be able to do stuff like modify computer internals safely? Windows answer to this is usually that settings won't take effect until the next reboot, which makes your computer *stop all it's work* until it's done. X can be restarted with a single keystroke to have the same effect. Maybe a couple of command line edits in between but meanwhile none of your users have been disconnected, no programs have stopped doing what they were supposed to be doing.

    Command-lines are not for the faint-of-heart. Then again, last time I touched the command line on my own Linux desktop (not counting other machines that are cmd-line only via SSH) was to run LILO - not something that a "desktop doughnut" should be doing. You obviously have either different ideas of what you should be doing on a normal desktop machine or have not found out how to do them GUI-wise. By the same token, Windows should never expect me to recover in safe mode, or via recovery console, or by running any batch commands ever. Fine for the ordinary desktop user because it very rarely does. Not fine for a power user. An ordinary desktop user wouldn't even notice if you ran a Windows GUI on a Linux machine.

    C) Man pages can be a pain in the arse (make it compulsory to include enough examples to demonstrate every option!). HOWTO's are not always up-to-date. Forums are, pretty much, for people who want to know how to install this Linux thing they downloaded. Then again... how much documentation do you get with Windows?

    A small booklet showing you how to use a mouse to point at the various icons. An online help system that, even with it's wizard-style help for some items, is next to useless if you don't know the terms to look for (I work support for six schools... that's about 60-100 staff and a few thousand pupils. I have NEVER seen or heard of anyone even bother to try using Windows Help or Help inside ANY program because it's never been useful to them). Annoying dogs, wizards, paperclips that people want me to TURN OFF for them because they can't figure out how.

    That's surely Linux 0-0 Windows in terms of help.

    If you're an advanced user, you've got to be comfortable with the command-line. I carry a USB key full of cmd-line utils and use them almost every day on Windows and Linux. It's amazing how much quicker "Start, Run, Cmd, ipconfig" is than navigating that poxy GUI network settings. And while I'm there, doing "route print" is the ONLY way to discover Windows network routes.

    Anyone who's not going to set up networks or advanced stuff (i.e. users), or home users shouldn't ever NEED to worry about the command line on either OS. And they don't. They pick a distro like Lindows and once the installation is complete, they never see it again. Or they have a decent desktop set up and then never see the command-line again. You, however, are on the border. You are trying to do stuff that NEEDS a command line, stuff that's beyond a GUI point-and-click.

  31. Summary of new features by makomk · · Score: 4, Informative

    There's a good summary of the new features over at LWN. Among other things, inotify has finally been merged in - about time! I wonder when Gentoo will add the new version to Portage, and if I'll dare to upgrade?

    1. Re:Summary of new features by Derek+Pomery · · Score: 1

      inotify has been patched in and enabled by gentoo for a good long while now.
      Of course, there's the complete rework of it in the new kernel which applies to all versions of beagle after 0.0.12 I believe.

      --
      -- perl -e'print pack"H*","6e656d6f406d38792e6f7267"' /. ate my old sig. Bastards.
    2. Re:Summary of new features by makomk · · Score: 1

      To be quite honest, I suspect most non-vanilla kernels had inotify already. On the plus side, it means I can use vanilla-sources and install the latest version now - which I think I will, more for IO priority support than anything else. (Hopefully, I'll finally be able to give MythTV priority access to the hard drive)

    3. Re:Summary of new features by Derek+Pomery · · Score: 1

      Planning on running MythTV as root? :)
      I was under the impression Linus was keeping that out of reach of ordinary users.
      (well, 'cept for *downgrading* priority I 'spose - I really do need to read the code)

      --
      -- perl -e'print pack"H*","6e656d6f406d38792e6f7267"' /. ate my old sig. Bastards.
    4. Re:Summary of new features by makomk · · Score: 1

      Planning on running MythTV as root? :)

      Only the backend (need to fix that sometime), and even if I wasn't, running (as root) "nice -n-1 su username -c command" should probably do it. (According to the summary, IO priority is derived from niceness by default).

      For the backend, Gentoo's /etc/init.d/mythbackend will even handle all that itself.

  32. Re:Real world vs. fanboy fantasies by Anonymous Coward · · Score: 0

    Wow, I'm really impressed you managed to pass a multiple choice test, where you don't even need to have used the OS in question to get a certificate!

    You sound like a fill the printer with paper lacky. Ooh, we're so impressed.

  33. I feel lazy today... by penguinoid · · Score: 1

    Download the latest Linux kernel from a kernel.org mirror.

    apt-get install kernel-image-2.6-686

    No, it won't get the latest kernel, but it will get one that has been tested a bit first.

    --
    Don't waste your vote! Vote for whoever you want, unless you live in a swing state it won't matter anyways
    1. Re:I feel lazy today... by WWWWolf · · Score: 1

      apt-get install kernel-image-2.6-686

      No, it won't get the latest kernel, but it will get one that has been tested a bit first.

      Pfff! apt-get install kernel-package kernel-source-2.6.13 # latter not available for a while though

      Damn me if I'm ever going to use a pre-built kernel, but I do want Debian to do the patching and QA for me. And make-kpkg rocks. =)

    2. Re:I feel lazy today... by eldacan · · Score: 1

      The names have changed, now it is:
      linux-image-2.6-686
      (although kernel-image-* packages are still provided as metapackages)

  34. Re:Why aren't we at 2.7 yet? or 2.8? by fok · · Score: 1

    That would be Gnome XP or KDE XP or whatever-window-manager-you-are-running-XP. The kernel would be Linux NT. \m/

    --
    \m/
  35. Perfect Timing... by hardcorey · · Score: 2, Funny

    I just finished configuring and compiling the kernel for my desktop last night, and now Linus decides that I'm not important to him. Why doesn't he return my calls? Doesn't he love me anymore??

    --
    I have bad karma :(
  36. Re:Ahem... Linux® kernel by Colin+Smith · · Score: 1

    They forgot the attribution as well:

    Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

    http://www.linuxmark.org/attribution.html

    --
    Deleted
  37. MOD PARENT DOWN by Anonymous Coward · · Score: 0

    How quickly they forget about the XP service pack that broke everything and of course Microsoft's lack of documentation is laughable compared to the wealth of additional documentation availiable on linux (HOWTO's and package documentation).

    Sounds like you already found an OS that fits your needs but feel free to rant about unrelated software in a story about a new kernel release.

  38. Re:How about a stable ABI? by Anonymous Coward · · Score: 0
    You will never, ever, become successful on the desktop until idiocy like this is exorcised from the OS.

    Who is this "you" that you keep referring to? Your post reads like every person involved in linux development is part of one coherent group that has the single aim of producing a successful desktop operating system, and that not reaching this aim is failure.

    The extent to which kernel developers care about end users is that it works, and works well. Saving users from compiling kernels? Not there problem, it's the distribution makers role to produce packages. Protecting users from the command line? Likewise. Similarly for documentation.

    Don't get me wrong, Linux being suitable for everyone's desktop would be wonderful. But that it isn't there just yet isn't failure. For me, everybody working on Linux has already won. They've produced an operating system that I want to use, and choose to use over the alternatives (and not due to the cost). For that, I thank them.

  39. Re:How about a stable ABI? by penguinoid · · Score: 1

    Having to recompile kernels/worrying that apps will be broken by upgrading that kernel. For that matter, I don't want to have to compile anything, ever. Just to make this clear, never. Come up with either something akin to Windows where I click on a standard installer, or make it like Mac where I just drag and drop the folder.

    I'm a debian user. I am very lazy. I install everything with apt. If I don't know what I want installed I use synaptic (graphical installer, click to install). Soooo... `apt-get install kernel-headers-2.6-686`

    --
    Don't waste your vote! Vote for whoever you want, unless you live in a swing state it won't matter anyways
  40. Re:How about a stable ABI? by KiloByte · · Score: 2, Insightful

    >> Any time I'm forced to drop to a command line, you as a developer have failed.
    > I don't think the kernel-developers are to blame if some GUI-tool doesn't do the job. They work on the kernel, not on the GUI.


    In fact, if some functionality requires a GUI, people like me are mightily upset. The moment I'm forced to drop to a goddamn GUI, you (the grandparent poster) as a whiny user have failed.
    [Disclaimer: not a single byte of my code can be found in the official kernel tree, so take my words with a grain of salt. Still, I don't really imagine Linus using mouse for anything but cut&paste]

    --
    The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
  41. Re:How about a stable ABI? by penguinoid · · Score: 1

    Oops, I am also very careless. that should read kernel-image-2.6-686

    --
    Don't waste your vote! Vote for whoever you want, unless you live in a swing state it won't matter anyways
  42. Re:Why do you hate freedom so much? by Anonymous Coward · · Score: 0

    There ought to be limits to freedom.
    - G. W. Bush

  43. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    Feel free to continue paying (but see the * below) for inferior one-size-fits-all software. Linux is not for you, as you're certainly not a technical or advanced user as borne out by your odd reference to man pages - you are aware that there are alternative interfaces to the man pages other than the terminal? Oh wait, I forgot - you're neither technical nor advanced. Riddle me this - if a command line is such a failure, why are MS making a song, dance & musical extravaganza about the new command-line shell in a certain forthcoming OS? Bet that caught you out.

    Quick rant - it's obvious that you want Linux to become some kind of free Windows clone so that you stop warezing* it and hunting around for serialz.

    Just admit that you would rather pay for software, than use (or god forbid, contribute to) free software.

  44. Woah by FullMetalAlchemist · · Score: 1

    Woah, that Linux Torvalds guy must be annoyed that some retarded bearded hippie at MIT insists that he's a really is wilderbeast and thus should be named thereafter.

  45. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    make menuconfig kthx

  46. Linux DOES has a stable ABI by diegocgteleline.es · · Score: 3, Informative

    Linux DOES has a stable ABI, this is, the syscall interface. It hasn't been changed in years...I know people who is running binaries compiled for linux 1.0 in 2.6 kernels. If your app breaks or works bad when changing the kernel version (ej: openoffice when the semantics of yield() where changed in 2.5) is probably because your app was broken in first place. Now, regression and bugs can happen too, but those aren't on purpose

    Maybe you mean the internal kernel API - which affects to modules, NVIDIA & friends etc. That API is unstable on purpose, as explained here: http://kernel.org/git/?p=linux/kernel/git/torvalds /linux-2.6.git;a=blob;h=f39c9d714db3d6bf2f6440d2f6 cf9353057eeae5;hb=02b3e4e2d71b6058ec11cc01c72ac651 eb3ded2b;f=Documentation/stable_api_nonsense.txt

    Or maybe you mean "compatibility" WRT gtk & friends, if GTK breaks compatibily thats their broblem

    1. Re:Linux DOES has a stable ABI by coolGuyZak · · Score: 1
      Well, while the GCC crew was prepping their C++ ABI they managed to break it at least once as well. GCC3->GCC4 compiles slightly different. Quite a pain when you run Gentoo and KDE :-!

      But, in all honesty... I don't really know why we respnded to the GP in the first place... It was most obviously a troll.

    2. Re:Linux DOES has a stable ABI by Anonymous Coward · · Score: 0

      > (ej: openoffice when the semantics of yield() where changed in 2.5)

      Sorry, but this is a particularly bad example. The way the semantics of sched_yield(2) were changed is (1) incompatible with the way Linux has always behaved, and (2) incompatible with the way traditional Unix behaves.

      (And contrary to what the kernel developers will tell you, there are perfectly legitimate reasons to want to yield without getting one's priority lowered; the obvious example is waiting for a video card to flush the command FIFO.)

    3. Re:Linux DOES has a stable ABI by fnj · · Score: 1

      Maybe you mean the internal kernel API - which affects to modules, NVIDIA & friends etc. That API is unstable on purpose, as explained here: Apologia for constant gratuitous compatibility breaking changes

      I have one carefully considered word to describe my reaction to the referenced apologia: UNCONVINCING. I recognize that it's not a piece of cake, but it's not rocket science either.

      Depending on the version of the C compiler you use, different kernel data structures will contain different alignment of structures.

      Maybe if this were the dark ages and we did not have compiler packing pragmas to handle exactly this situation, then it would be a problem. Anyone with a modicum of experience knows how this problem is customarily turned into a non-problem.

      Depending on what kernel build options you select, a wide range of different things can be assumed by the kernel:
      - different structures can contain different fields


      The way to handle this is via embedding versioning/option information in the structures. This is not rocket science.

      Some functions may not be implemented at all, (i.e. some locks compile away to nothing for non-SMP builds.)

      A non-problem using the same techniques above mentioned.

      Parameter passing of variables from function to function can be done in different ways (the CONFIG_REGPARM option controls this.)

      No rationale being offered, you're going to have to cut me some slack if I say this sounds like a gratuitous obstruction.

      etc. etc.

      Pretty much all the offered rationales are excuses for not designing properly up front. I don't mean designing perfectly; that's impossible; but designing with a view to accomodating future changes in a way that preserves compatibility with carefully written modules.

      Bottom line: the linux kernel design is an extremely impressive piece of work; a magnificent gift to the community, but it does have major conceptual flaws in that no one ever bit the bullet in terms of maintaining module compatibility across versions; particularly important if you have any interest in supporting binary-only modules in any real sense. If it's a religious decision that we don't want to support binary-only modules because they are inherently evil, then fine; there's no point in arguing religion; but if it's that we don't want to support binary-only modules because it's too hard and we don't want to exercise the discipline necessary to support them effectively, that's another thing entirely.

    4. Re:Linux DOES has a stable ABI by diegocgteleline.es · · Score: 1

      The way to handle this is via embedding versioning/option information in the structures. This is not rocket science.

      Methods like the "Windows Driver Model" thing, which would give us back that compatibility HAVE been proposed, implemented and then, rejected. Google for "overengineering".

      Again, the kernel HAS a stable ABI - the syscall interface. Lots of projects change their internals while conserving their "public" interface stable. This is what the linux kernel does, and the fact that modules are "different" doesn't make it a bad idea.

  47. Humm...2.6.12 broke... by Dimensio · · Score: 1

    ...When 2.6.12 came along it broke my IDE-SCSI setup (I use one quirky piece of software that REFUSES to work unless my DVD-ROM drive is accessable as a SCSI device, and there's no alternatives available for it) and I couldn't make it work again. In addition, I completely lost audio from my bttv device and couldn't restore it.

    I'm a bit hesitant to switch from 2.6.11.

    1. Re:Humm...2.6.12 broke... by diegocgteleline.es · · Score: 1

      When 2.6.12 came along it broke my IDE-SCSI setup

      Well, maybe those bugs have been fixed in 2.6.13, which is why new kernel versions are released in first place

      Because you did care about reporting them, yeah?

    2. Re:Humm...2.6.12 broke... by vranash · · Score: 1

      ide-scsi hasben deprecated due to native atapi support, so its unlikely any such bug would get fixed.. also I think I had similiar issues to the poster, thankfully fixable by just installing a new version of cdrecord.

    3. Re:Humm...2.6.12 broke... by Spicerun · · Score: 1

      Kernel-2.6.12.x wouldn't boot on my machines, locking up after the usb ports were detected. I've been using the 2.6.13-rcX series from the beginning, today 2.6.13, and have had no problems with any of the 2.6.13 series kernels.

    4. Re:Humm...2.6.12 broke... by Dimensio · · Score: 1

      Sadly, this is a Windows app used through Cedega. I suspect that updates to accomidate a setup that very few users have is not forthcoming.

    5. Re:Humm...2.6.12 broke... by jone1941 · · Score: 1

      So, it sounds like it is a bug in Cedega. Tell them that they are leveraging a deprecated kernel feature for their ide-scsi dvd support. They are a great company and completely use focused maybe they just need to be made aware of the issue.

      --
      Fear trumps hope and ignorance trumps both
    6. Re:Humm...2.6.12 broke... by Dimensio · · Score: 1

      I can't really blame Cedega, though. I'm using it with MagicEngine, a commercial TurboGrafix-16/PC-Engine emulator (for which I do have a legal license), and even with the 'new' CD-ROM code there are still issues with CD access. It needs direct device access under any circumstances, because PC-Engine CD-ROMs are not ISO9660 format, so the data has to be read directly. I'm not sure what the Cedega team could do for it, especially since the software is so obscure as it is.

      Even then, there's still the "no sound from bttv". I suspect both of these are local configuration issues, however, because I can't get reports of anyone else having the same problem with 2.6.12 or 2.6.13.

  48. -1, Karma Whore by Anonymous Coward · · Score: 0

    kernel.org has plenty of bandwidth for this.

  49. Re:Windows? by Anonymous Coward · · Score: 0

    of course! you can run an X window system (xfree86, xorg) and the window manager of your choice.

  50. Re:THE NEWEST FEATURE by diegocgteleline.es · · Score: 1

    You must be new here.

    I mean, here in slashdot we have high-quality trolls, we love to be troll-ized by them.

    But your start has been quite poor, really. Continue training...

  51. Re:How about a stable ABI? by strider44 · · Score: 1

    Add to that that noone's actually forcing him to compile his kernel or anything or even *shock horror* open the command line. Why can't the guy just wait until the distro has compiled it for him?

  52. Re:How about a stable ABI? by Progman3K · · Score: 1

    > Having to recompile kernels/worrying that apps will be broken by upgrading that kernel. For that matter, I don't want to have to compile anything, ever.

    I always want to compile EVERYTHING from scratched, tuned to my precise build settings, I NEVER want to install binary-only applications again.

    Until Windows and Mac give me this option, I won't consider them.

    All this being said, there are Linux distros that are as easy to use and administrate as the Mac or Windows, I encourage you to seek them out and use them, but don't imagine that your idea of a perfect operating system coincides with everyone else's.

    --
    I don't know the meaning of the word 'don't' - J
  53. Re:How about a stable ABI? by osxforpcs · · Score: 2, Insightful

    OK, first off, this guy is obviously a desktop user. So, yeah, it's understandable he wants everything driven via a GUI. Fair and reasonable request really. But he should understand that not everyone is a desktop user and many people who use Linux as more than just for servers are power users who LIKE having the power and flexibility of low level configuration files. Man pages do suck when not written properly. Would a few examples kill people to write?? But, the argument that Linux is free and that "the developers don't owe you anything" is getting old. Ok, it's free. BUT it's being put out there as a superior OS to Windows. So if you're going to develop and tout it as such, stand behind it and stop running for cover behind statements like: "Failed at what? To satisfy the whims of some random user who propably hasn't paid one dime for the software he's using? Here's a hint to you: they (the developers) don't owe you anything" This isn't helping anyone's cause. Learn to take and use criticism to make a better OS. Linux isn't better becuase it's free, linux is btter becuase it's a superior system is so many ways. Hardly any REGULAR desktop users would say it's as easy to use/configure as Windows and until they do, there's work ahead for developers....

  54. Feature changes by digitalderbs · · Score: 1

    I always have trouble finding the new features and driver changes with each major release.

    For reference, Kernel trap has a copy of Linus' e-mail to the Linux Kernel Mailing List with a list of changes. If someone has a better link, please reply.

    1. Re:Feature changes by TCM · · Score: 1

      If someone has a better link, please reply.

      Here, I think this link is better: http://www.netbsd.org/

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
  55. Re:How about a stable ABI? by RAMMS+EIN · · Score: 1, Offtopic

    Can people please stop pretending that everything that doesn't have a click-and-go binary installer GUI whizzbang gadget is somehow a flaw in Linux?

    Linux is perfectly usable as it stands. You can get your command line if you want it, you can get your GUI if you want it, it comes with a slew of drivers for various kinds of hardware, and a typical installation will provide you with everything you need for browsing, email, chat, development, and some light entertainment.

    Just because you have to dive into an editor to get some leet-o feature to work, or recompile the kernel to get your not-yet-fully-supported hardware to work, doesn't mean the system sucks. At least you have the possibility, aye?

    And if you want to use the system in a certain way, but you don't like the interface you have to use, you can develop another. If you won't develop another, then maybe Linux isn't for you. Well, guess what? Nobody is forcing you to use it.

    Linux is primarily a system developed by the people who use it, and used by the people who develop it. That it has gotten user-friendly enough for even non-developers to use is a great achievement. It's intention was to be a Unix-like operating system, developed purely for the fun of it.

    Sure, criticism is good, as it can help improve the product. But this criticism of yours insn't helpful in any way. All your saying is "it's flawed because my favorite features don't work the way I want them to." If at least you had been specific about what things needed to be improved and how, somebody might be kind enough to do it for you. But that still doesn't mean Linux is flawed, it just means it isn't your perfect match.

    --
    Please correct me if I got my facts wrong.
  56. Re:How about a stable ABI? by MikeDawg · · Score: 1

    I completely disagree with you on several points. In a comparison to your Windows operating system, every single one of these points fail. A) Remember when SP2 got released, that broke several applications, and applications had to be rebuilt around SP2. Furthermore, Microsoft forces you to upgrade to SP2 (the only way to get around that is hacks, that John Q. Public doesn't know). In linux, you are never *forced* to upgrade your kernel, if you live in fear of it breaking an application. ( I really have nothing to say about you not wanting to compile programs, if you don't want truely optimized code for your specific machine, fine. ), there are many "binary" installers available that many companies build. For instance, I just installed QLogic's SANSurfer program from a single executable. Works great. B) I don't care what operating system you run. Command line is *not* a bad thing. The fact that people are generally inept to do anything that requires typing is scary. Remember that device that was around long before the mouse, the keyboard? What is the big deal of using it. It may not be quite as easy, but c'mon. C) man pages are completly acceptable, and they do cut it. As compared to Microsoft's KB, you got to give me a break. I've searched for information using a fairly accurate search string and still have found KB articles buried 3 pages deep. Furthermore, man pages give you a full description rather than KB articles that can either be good or be crap. They can give you a quick workaround, or they could give you a description on a command or a problem. This is not a linux error. And on your last little comment you make. I'm one of those who still believe that each OS has its place. I don't think linux deserves to be on the desktop, but in that same idea, I don't think that Windows deserves to be on my server.

    --

    YOU'RE WINNER !
    Another lame blog

  57. Re:How about a stable ABI? by kwark · · Score: 1

    You should really brush up on your trolling skills. This one is to obvious:
    - A and B are simply not true for the stuff you describe you are comfy with.
    - man pages are fine, only thing (IMHO) they might be lacking are decent examples.
    - the need to prove yourself
    - posting as an AC

  58. Re:Why aren't we at 2.7 yet? or 2.8? by Alwin+Henseler · · Score: 1

    The non-technical people out there understand version #s only enough to be confused here. They probably think Linux is stagnating. I'm not saying we need to rush ahead to "Linux XP" or something, but wouldn't it be wise to start incrementing something other than the 3rd set of digits?

    Simple answer: wherever you read version 2.6.x, read 2.7.x instead. For all intents and purposes, I regard Linux 2.6.x as development branch.

    Just look at the the huge number of patches that go into the kernel between 2.6.x releases. And check the size of all those patches combined. Even changelogs are in the MB. range. Compare that with 2.4.x series.

    Anybody who claims 2.6.x is a 'stable' kernel series, is a liar. Stable running: yes. I'm used to compiling my own kernels from vanilla 2.6.x sources, and I can't remember ever having had a hard lockup (where the machine is totally frozen). And my use of Linux includes all common things like webbrowsing (JavaScript, Java + flash plugins all used on and off), MP3 music, and internet multipayer, hardware accelerated 3D gaming.

    But stable from a development point of view ('mature')? No way. Personally I suspect things are done this way, because the 2.6.x series provide such a powerful foundation, that allmost everything you can cook up, one way or the other can be fitted into existing infrastructure. And putting it into 2.6 releases, exposes it to a lot of users/testers, so that bugs can be shaken out fast.

    If you don't like this, then I suggest you either a) don't compile your own kernels, but have a stability-oriented distro like Debian or Slackware-based do it for you, or b) look at *BSD instead.
  59. Re:How about a stable ABI? by XO · · Score: 1

    To reply:

      A) This is already done by all the people that put together distributions. They typically have one kernel that works on virtually everything. You're right, it's not going to be as streamlined for the particular hardware as a custom compiled kernel. re: ACPI/APM not working, either fix the code, or know that it's not going to work and disable it.
      B) "modify computer internals safely"? What are you talking about? You mean mucking with important config files? Great, whatever uses those config files should know that the files have changed, and re-read them as needed.

    --
    "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  60. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    I guess it all depends on what you want from your Operating System.
    When I read your post I kept thinking to myself "this person wants things exactely opposite of how I prefer them". Let me try and explain by using your own examples.

    A) Having to recompile kernels/worrying that apps will be broken by upgrading that kernel. For that matter, I don't want to have to compile anything, ever. Just to make this clear, never. Come up with either something akin to Windows where I click on a standard installer, or make it like Mac where I just drag and drop the folder.

    Not being able to recompile the kernel of my operating system would worry me. It would leave me unable to quickly fix bugs when they become known and would also leave me completely unable to customize my OS's inner workings (and yes, I actually do that, both for fun, but also for work).
    As for "point and click" installation of software, I prefer building from source since I like to inspect the software I install before running it instead of just having to trust other peoples binaries.
  61. Re:How about a stable ABI? by sydneyfong · · Score: 1

    You sound like a person who thinks you have some "technical skills" and heard the hype about Linux, but got bitten when you tried to jump on the bandwagon.

    Here:
    A) Use the package manager that comes with the distro. Don't upgrade your kernel unless you have good reasons. If you do, still use the one packaged by your distro.
    B) It's just the preferred way of doing things in Linux (and most Unices). If that bugs you, don't use this method and use the GUI tools available. The major desktop environments like KDE and GNOME supports most (if not all) commonly used configuration options.
    C) man pages are fine, thank you (at least on Debian). It's not to provide you with an introduction to Linux, and definitely not to tell you what you should be doing if you have no damn clue. It's a reference for those who know what they are doing -- the command line options, the config file format, the arguments of the C-library/system calls... etc. If you want documentation in the sense of "linux-for-dummies", then buy a book or something.

    All of your ramblings suggest that you've heard somewhere (probably from some Gentoo zealots...) that you NEED to compile your own kernels, edit config files by hand, type in cryptic commands in a CLI and RTFM like nuts. No. Most Linux users do use it that way because they prefer it, but if you install and use a decent "user-friendly" distribution as some other posters have suggested and stay out of the dirty work like tweaking your system, you wouldn't need to even KNOW anything about compiling kernels, shell commands and man pages.

    Yep, so quit trolling. Go back to your warm and fuzzy Photoshop and Illustrator apps and stop pretending to be 1337 in Linux (or in tech). All the "feats" that you have mentioned is nothing extraordinary and are things any computer-literate person with a sound mind could do easily -- except perhaps the Photoshop/Illustrator part, in which (if your claim is true) I'll acknowledge you as a decent graphics designer, but nothing else.

    --
    Don't quote me on this.
  62. Re:How about a stable ABI? by swillden · · Score: 3, Insightful

    Any time I'm forced to drop to a command line, you as a developer have failed.

    Without getting into the whole "you have failed" thing and whether or not your particular requirements are some sort of mandatory minimum, it's my opinion that the same thing applies to GUIs. I think every piece of functionality should be available in three different ways:

    1. From a command line. This is so that common processes can be scripted. Yes, this is a usage mode that novice users won't get into, but even Windows "power users" understand the value of a batch file. Tasks that are lengthy, repetitive and frequent can often be automated away. For serious computer users, scriptability is a key requirement.
    2. From a GUI. GUIs are great for things that you only do occasionally, plus for the applications that actually benefit from graphical interaction. GUIs are also crucial for novice users, because they lay out the options visually. GUIs are not the end-all, however, and they're not necessarily easy to use. Look at some of Microsoft's system administration tools, for example, like MMC, the GPO editor, the CA configuration interface, and you'll quickly find that GUIs can be just as obscure and arcane as any command line.
    3. From a library. If you are a developer, or have access to a developer, there are many times that even scripting doesn't quite cut it. Being able to write a real program, but take advantage of complex functionality from other programs is immensely valuable. Microsoft does some of this, providing mechanisms for assembling programs with VB, VBScript and even C++ using some components of Office and Windows. It needs to be done with everything, though.

    The common Unix and OSS methodology is to build the command-line tools first, then factor out libraries and add GUI interfaces that use either the libraries or even the command-line tools underneath. So, it's common that features are accessible for a while from the command line, but not from the GUI. In the Windows world, the methodology is to construct the GUI first, then expose functional components via OLE and then, maybe, to create command-line tools. Of course, it's very common in the Windows world to stop after the GUI.

    IMO, the Unix and OSS approach is superior because it improves the odds that all three interfaces will be implemented, leading to maximum functionality not only for novices, but also for power users and developers. But I won't clam that Microsoft has "failed" because I understand the difference between my opinion and global Truth.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  63. Did ATAPI/AHCP on SATA become true on default? by Wolfier · · Score: 2, Interesting

    I'd like to use the stock kernel as much as possible.

    As of now no SATA DVD drive works well unless you change one line and recompile the kernel.

    So many systems are now built as SATA-only (yes, the IDE ports are completely unused), stock kernels break all live-CD distributions - none of them will boot :(

    1. Re:Did ATAPI/AHCP on SATA become true on default? by hardcorey · · Score: 1

      I work (temporarily) as a technician at a custom computer shop where we build computers and do repairs and service to all brands, and we've yet to build or service a computer with a SATA optical drive. There aren't a whole lot of them out there, and there is no current advantage to them, with the exception of SATA being an overall nicer to use interface than IDE in many regards. I think it will be a year or more before SATA really takes hold as far as optical drives are concerned. When I was building this new computer, I looked into SATA optical drives and I noticed how few there were (just a handful, it seemed), and they were way overpriced considering the nearly non-existant performance gain.

      --
      I have bad karma :(
    2. Re:Did ATAPI/AHCP on SATA become true on default? by coolGuyZak · · Score: 1
      That doesn't change the fact that he has one, and cannot boot a LiveCD though...

      My reccomendation to the GP: put in a bug report at the kernel (or your distros... or better yet, both!) bugzilla. If you provide some software testing, they'll hopefully fix it by the next release.

      As far as your current problem goes... Unfortunately, my only advice is to find an IDE drive you can use... or a ::cringe:: floppy drive to boot from. A flash drive might work as well... or a network boot.

  64. Obligatory Gentoo post... by Danuvius · · Score: 2, Funny

    Damnit! I just finished compiling Kernel 2.6.12-gentoo-r9 yesterday!!!! No. REALLY!

    --
    Akarsz Magyar Gentoo fórumot? Akkor
    1. Re:Obligatory Gentoo post... by Just+Some+Guy · · Score: 2, Informative
      So:
      1. Copy your /boot/config-2.6.12-gentoo-r9 to /usr/src/linux/.config
      2. Run cd /usr/src/linux; make oldconfig and answer the questions.
      3. Spend 20 minute compiling the new kernel.

      There! You're all done for another few months, or until you feel the need to upgrade again.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:Obligatory Gentoo post... by TeknoHog · · Score: 1

      I run Gentoo as well, but I always use the vanilla kernel instead of the Gentoo version. Thus I'm happily running 2.6.13 already on my laptop :) It will take some time (days, if not weeks) for the 2.6.13-gentoo release, and I don't see any benefits in using it.

      --
      Escher was the first MC and Giger invented the HR department.
    3. Re:Obligatory Gentoo post... by Danuvius · · Score: 1

      Do you *know by experience* any difference between running vanilla and gentoo-sources?

      I've done both, and tried some other ones too in the past... but I must admit that unless the computer stop working in some specific way, it worked just as well under one as under another.

      Curious if you have a different experience.

      --
      Akarsz Magyar Gentoo fórumot? Akkor
    4. Re:Obligatory Gentoo post... by Anonymous Coward · · Score: 0

      aye - i compiled that 3 days ago. yesterday I just got around to installing 2.6.13-r13 on my dev box. duh! :-)

    5. Re:Obligatory Gentoo post... by Fastball · · Score: 1

      I'd take a *-r9 kernel over a vanilla, unpatched kernel any day. There's a reason the Gentoo devs have provided 8-12 revisions for each 2.6.x release, and I'm quite happy to stick with a 2.6.12-r9 until others take the plunge and patch 2.6.13 into something useable.

  65. Re:Windows? by Flying+Purple+Wombat · · Score: 1

    Assuming you mean Microsoft Windows, yes, it does.

    If you just want to run some programs that are designed for MS Windows, look at Wine. It can be a pain to set up, but it's free and it works.

    If you want to run a MS Windows OS, then you need VMware. This lets you run MS Windows in a virtual machine under Linux (or vice-versa). It's nto free, but works well.

    --
    If God had meant for man to see the sunrise, He would have scheduled it later in the day.
  66. Re:How about a stable ABI? by /ASCII · · Score: 1

    Hear, hear. I don't know of a single moderatly common desktop user task that requires the commandline, and that is the way it should be.

    That said, the commandline is an exceptional tool, and while it has some shortcomings that could be adressed, there is no reason to remove it. Microsoft tried, realised their mistake and plan to release a next-generation shell to correct it. Let's not try to copy their mistake, especially not after their indirect admission of this mistake by creating the Monad shell.

    --
    Try out fish, the friendly interactive shell.
  67. So when do I get my.... by Anonymous Coward · · Score: 0

    Update disc. Or can I just download an executable somewhere? Or can I just access a web site and run an ActiveX script or Java script to run a hotfix? Hmmm. OOOPS!!! My Bad!!! I forgot this was not a Microsoft Operating System. When are you Linux people going to figure out that the only way you are ever going to get mainstream acceptance is when I (the average joe blow user) can click on a link, choose to run or save and run later in order to update my system? Figure this out already why don't you.....

    1. Re:So when do I get my.... by Anonymous Coward · · Score: 0

      Sorry you dont have a clue. Many linux distros will have the new kernel pre-compiled. Click update, and it will install for you.

    2. Re:So when do I get my.... by PorchPuppy · · Score: 1

      And how would one know that this new update was available? There are so many distros out there it is too unorganzized to expect any type of standardization. There should be an autoupdate feature available that runs in the background to tell you when there is an update available. Ooops, there's that pesky Windows reference aqgain. I totally support the Linux effort but the downside to the model is that you do not have any standardization out there. I know there are a number of people out there that just get pissed off when newbies have so many questions. But that is just the nature of the beast. Computers are cheap enough for the masses. If Linux ever wants to become more than a grass roots effort, then the model is going to have to change. By that, I mean that the update process must be streamlined. There should be one master update location (with mirrors of course) and all distros should refernece that one site. Software should be easier to install. A user should not have to know how to open a tar file or how to chmod so they can execute a file. Is this making any sense? I know many hard core Linux users out there want to tell me to stick it where the sun does not shine, but this is reality. Otherwise, Linux will remain as nothing more than just a hobbyist OS for most of us. Yes, there are corporations out there using it for more than hobbyist type of activities, but those are not mainstream users. Those are corporate users with technical degrees and backgrounds to support such use. Like I said, Linuz is great, but not for the masses. Good day...

    3. Re:So when do I get my.... by coolGuyZak · · Score: 2, Informative
      Well... I'm not sure about SuSE, but I know that RedHat and Mandriva both support such a device. It rests, safe and serene, nestled in its loving system tray. When updates are available, it changes from its tender green manner into a somewhat irritated orange. When critical updates are available, it becomes really noticable... a form of colicky red.

      When it comes to community distributions... they may handle things differently. But they can afford to... as they are the true hobbyist form of Linux. (Well, except for K/Ubuntu)

      Overall, though... The astroturfing/trolling was a refreshing experience. Nice to see that you can still bring up the oldies-but-goodies (no matter how false) of linux fix-its. As a matter of fact, you should be heralded as the paragon of all members on the site. I propose a petition! Let everyone who wants to assign Mr PorchPuppy a UID of 2^32 speak now, as it is surely his proper place amongst /.ers.

      I think I've said enough though. Have a nice day.

    4. Re:So when do I get my.... by Sean+Umphlet · · Score: 1

      Maybe when you figure out that linux is not supposed to be geared towards the average joe blow user. If you're running a fairly user-friendly linux like Redhat or SuSE, and don't know how to install a binary kernel from the GUI package manager, (let alone configure and compile the thing yourself) then you're better off just sticking with your Microsoft Operating System.

      --
      -- Sean "nosebleed"
    5. Re:So when do I get my.... by Bent+Mind · · Score: 1

      SuSE uses Yast to fetch updates automaticly. You could also add Gentoo to the list of distributions that support auto-update: emerge --sync && emerge -u world. In fact, are there any distributions that don't have an auto-update feature?

      --
      Request a Linux Shockwave player here: http://www.macromedia.com/support/email/wishform/
    6. Re:So when do I get my.... by Anonymous Coward · · Score: 0

      Suse of course has a very similar system (YOU - Yast Online Update) - not only for the Kernel, but for all applications of the distribution one has installed. Only security patches will be installed, very transparent to the user, or completely automatically if he prefers that. Quite convenient.

    7. Re:So when do I get my.... by Anonymous Coward · · Score: 0

      But not for the masses.
      If you can not find a flavor of linux to fit your skill level then you are just too stupid to use a computer of any kind.
      Go back to TV but stay away from cable as the menus are very confusing.

    8. Re:So when do I get my.... by QuesarVII · · Score: 1

      If you're using any modern distro, you can just open up the system update tool.... and then apply all updates in one fell swoop. I have wasted so many hours of my life repetitively rebooting windows systems to apply more and more updates. Example: Apply update foobar reboot Apply update foobar 1.01 reboot Apply update foobar 1.01b reboot Apply update for update foobar 1.01b reboot When in Linux, it would just install the latest version the first time.. and unless it was a kernel.. it wouldn't even need to reboot a single time! That's one thing that I find Linux is way ahead in. There is absolutely no reason that MS should still require countless reboots for installing software. An application install should not need a reboot.

    9. Re:So when do I get my.... by coolGuyZak · · Score: 1
      Right, but manual-command line stuff doesn't fall in the lines of "automatic", at least as far as he was describing it.

      Think about MS Windows' Automatic Update... it will download patches for you, and then ask you (really, I find it more annoying than clippy) about a million times whether or not you want to install the updates. And when you don't turn off configurations in 2 different places, it will bitch at you that Automatic Updates is off... (This is XP SP2).

      Interesting story: my roomate was in the middle of playing one of his games (on a week-old install), and a new update came out for XP... his computer downloaded and installed it. (His game got a tid bit laggy, but we figured the connection was tripping out). he was promptly kicked out of his game while his computer rebooted automatically. I was in hysterics.

    10. Re:So when do I get my.... by Anonymous Coward · · Score: 0

      You dont need to take this update. Its optional. Its not a security update like ones you would see on windows update. Hence there is no reason to notify the user that this update is available.

    11. Re:So when do I get my.... by Anonymous Coward · · Score: 0

      Obviously you haven't tried linux anytime in the past 10 years.

      All distributions (excluding lfs, which is more a howto than a distribution) come with a package manager that will keep every single piece of software I have installed up to date with a single command. When windows update includes updates and silent installs for firefox, opera, quake 3 and other games, thunderbird, compilers, development environments, chat and im clients, p2p applications, various server suites, whichever my favourite media player happens to be, and the plethora of other programs that most computers have installed, I might give it a go.

      Many distributions come with graphical frontends for their respective package manager too - when will windows allow me to update my entire system with only two mouse clicks, and install almost any software available from within the same program?

      Also, having to reboot for even minor updates is stupid. There's only two times a linux box needs to be shut down or rebooted - when changing non-hotpluggable hardware, or changing kernel (and even that is paleing with the new kexec patch). I can turn a pure gaming machine into a pure file server and then into a pure internet gateway and back into a pure gaming machine without a single reboot - a windows machine would require no less than 5 reboots for that, and probably closer to 20.

      Then there's the fact that windows and its associated software suite has no way for me to fix problems I find, or set up headless servers without graphics support, or indeed completely remove the pieces I don't want installed.

      The memory leaks and number of non-associative and non-commutative operations makes windows a poor choice for reliable systems too.. if my linux boxes start doing strange things after 6 months of uptime, then there's definitely something wrong with them. The windows world would tell me reboot and hope for the best, which is completely unacceptable in a production environment. A properly built computer should work perfectly, no matter how long its been since its last reboot. Linux gives me that, while windows has been failing that simple test for the past 10 years.

      Windows was designed to make every concievable operation of a computer as easy as possible - unfortunately that includes all the nefarious and malicious things that people do. Linux was designed to be reliable and extensible through massive peer review, and has picked up usability along the way through that process.

      It's also almost impossible to find out why things won't work when using windows - 99% of the error messages are absolutely useless, and that's on the rare occasion that you actually get an error message about something. case in point - windows network at a friend's place. one computer can access the other's shares, but not vice-versa. all settings are the same and have been tried in every imaginable configuration. The only information available is that the computer that can't be accessed is recieving the access requests, but failing authentication attemps even though its been told quite explicitly to allow guest logins. There's abysmally little documentation on filesharing problems, and no way to enable verbose output for the filesharing component, so the "best" solution seems to be reinstall windows. I had a similar problem with a linux fileserver, but I just upped the debug level a notch or two and it told me exactly what its gripe was and was fixed within 10 minutes.

      so in summary:

      linux - reliable, extensible, highly configurable to almost any given need, stronger security in default configuration, good usability, able to be fixed or modified in-house, far more information available when something goes wrong.

      windows - popular, decent usability.

      If linux scares you, try ubuntu or knoppix.. ubuntu hides all of linux's best features "under the hood" so it may seem a little more familiar when you're used to the uselessness of windows. knoppix allows you to poke around at things without making any lasting changes to

  68. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    I guess it all depends on what you want from your Operating System.
    When I read your post I kept thinking to myself "this person wants things exactely opposite of how I prefer them". Let me try and explain by using your own examples.

    A) Having to recompile kernels/worrying that apps will be broken by upgrading that kernel. For that matter, I don't want to have to compile anything, ever. Just to make this clear, never. Come up with either something akin to Windows where I click on a standard installer, or make it like Mac where I just drag and drop the folder.
    Not being able to recompile the kernel of my operating system would worry me. It would leave me unable to quickly fix bugs when they become known and would also leave me completely unable to customize my OS's inner workings (and yes, I actually do that, both for fun, but also for work).
    As for "point and click" installation of software, I prefer building from source since I like to inspect the software I install before running it instead of just having to trust other peoples binaries.

    B) Any time I'm forced to drop to a command line, you as a developer have failed. Back 10 years ago, this may have been acceptable. In this day and age, it isn't. Furthermore, while once in a blue moon I may change a text file in Windows, in Linux it's a constant occurence. Again, you have failed.
    If an OS forces me to use a mouse to accomplish every task instead of letting me quickly string together the tasks I want to perform on a commandline, then that OS has, in my oppinion, failed. If an OS forces me to only use GUI tools to configure things instead of plain text files that I can easily copy from host to host, easily write scripts to manipulate etc, that OS has again failed.

    C) MAN pages do not cut it. Neither does a message board where half the time I'll be called a clueless n00b, 25% of the time I'll be told to use a different distro, and the other 25% of the time I'll get genuinely helpful people giving me contradictory answers. If I'm expected to jump to an alien computing environment you'd best make sure your documentation is up to snuff. Linux sucks in this regard.
    Most of the time I find that man pages cut "it" just fine. I like my documentation brief and to the point, I don't appreciate documents that use up an entire page just to tell me something basic in a language that assumes I'm a moron. When man pages don't cut it, there are tons of HOWTO's available online at tldp.org as well as distributed with most distributions.
    Ohh, and who said anyone expects you to jump aboard an alien computing environment? If you prefer something else then just go on using whatever that something else may be and I doubt anyone would loose any sleep on that account.

    I'm an advanced user who's in favor of open source, but the bizarre, arcane, and technical details I have to jump through to achieve the same things that are comparatively simple in Mac or Windows may Linux a deal breaker. You will never, ever, become successful on the desktop until idiocy like this is exorcised from the OS.
    The day Linux turns into an OS similar to Windows is the day I'm switching to something else. I don't want my OS to hold my hand, I want my OS to perform the tasks I set it in an efficient manner and I want to be able to script and modify every little corner of it. And I don't give a damn if Linux succeeds on the desktop or not - who cares, as long as it fullfills the needs of the people who create it.

    Different people, different needs, different Operating Systems.
    Why don't you just stick with Mac or Win if those make you happy? You can still use many Open Source apps on those platforms.

  69. MOD PARENT UP!!! by Anonymous Coward · · Score: 0

    Too bad I don't have mod points SuperBanana. Hopefully moderators will see the obvious brilliance of your comment.

    Good stuff.

  70. Re:How to tell if you are a linux fanatic. by Anonymous Coward · · Score: 1, Informative

    I don't mind being trollbait, for this is not feeding the trolls; this is making the rest of the world see the troll feeding in a zoo.

    So here's to the trolls.

    1. You rejuvenate and dance when you hear a windows flaw exposed, but you conveniently ignore the thousands of security flaws exposed in linux.

    We fix them too. We don't sit on our asses warming the chairs and overload the cooling. Microsoft takes ages to come out with an unpleasant fix, sometimes ONLY after a major outbreak. Go figure.

    2. You yell loudly TROLL! at any person's post or at any person you see posting facts that you do not want to hear about your oh so cool linux.

    You pour millions into a "Get the facts", fund "independent" studies with "unbiased" results, all the time lying through your teeth. We atleast have *FUN* calling you a troll, while you sit around paying your lawyer crowd. You throw the money, we get to crack the joke. Understandably, you're the one who's pissed off.

    3. You know it's a classic case of penis envy, you don't have all the support, software and hardware available for linux and you have to let that anger out somewhere, but you don't have the brains to admit it.

    Not everyone has the clout to SUCCESSFULLY support an installation. We help over mailing lists and stuff, you rip your paying customers for a slimy product. It shows.

    Winmodems (eg.), etc. are pieces of specifity made for interoperating with specifics. Make more general hardware, without perverting standards, and your hardware will work. You will find people using Microsoft keyboards with Linux; for the reason that it doesn't suck as much as your crappy OS, and dont have to upgrade to a new keyboard after every three years.

    4. You hate windows, hate Microsoft, but race to emulate windows, have programs to run office from within linux, and spend a $300 on a Windows emulator, only Windows fools.

    You suffer from being a control freak; you cannot accept the fact that some people have to build stuff that serves to glue your crap into the rest of the world. If youre pissed off about someone ELSE making your stuff work with other stuff, you have an attitude problem. Fix it, look at and accept the reality, and THEN let your gob pour forth its inane ramblings.

    5. You cannot admit that you don't have professional usage of Linux outside server markets.

    You don't even have the PROFESSIONAL guts to admit your lock on the OEMs. If it wasnt for your nutcracker at their testicles, you'd be nowhere, and you are where you are cause you pay Congress to hold that nutcracker for you.

    We admit that we do nothing of the above sort, and Linux's market share is built on goodwill, performance, and sheer superiority. We have cut into your market, and you're shit scared of it.

    6. You cannot admit that most of the joe user out there when told that there is linux will respond, what is that?

    Fix your senses, then your English. That doesn't make any sense at all. This is what happens when you have to do "Innovative(tm)" Feature Fillers.

    7. You cannot admit that there is no professional printing capabilities in linux.

    If "Professional", coming from the horses' mouth, means "insecure by default" and needs a "get the facts" push for shoving down closed throats, then I, personally, care to admit that printing in Linux works satisfactorily to suit my needs. I think most people feel so too.

    8. You cannot admit that you are a masochist (otherwise why would someone spend hours playing with scripts,
    and recompiling programs that are available for Windows?)

    If thats the only language you will ever understand, here's a fitting reply for your like and brotherhood:

    Doing Windows is S&M, actually. Install (fuck the computer up), 3 months and your computer is a wet soggy noodle, (get fucked by it). Then again, the next time around, we have DRM giving it to you up the other end of your digestiv

  71. Re:How about a stable ABI? by Lost+Found · · Score: 1

    A. If you want bleeding edge features long before your distribution provides them to you, it's your choice to decide to be technical and build your own kernel. The other option is that you use whatever your distribution gives you. The third option is that you use Windows, and get virtually nothing for your $100+ every time an upgrade comes out.

    Oh, by the way, there is strong resistence to breaking APIs in the kernel development community. Generally, it only happens with kernel-related systems like the deprecation of DEVFS - and even then, they leave it around and available and marked as on its way to the grave.

    If your software breaks when you upgrade the kernel, chances are that you don't know what you're doing and should opt for the distribution's stock kernel. If it doesn't suit you, pick another distribution... choices and all.

    B. This has nothing to do with the kernel, and while I'll grant that the desktop environments don't provide universal system control, this situation is gradually getting better.

    C. Man pages are pretty damn informative. Some systems like KDE are lacking help in certain areas. It would be nice to have more of a universal help center, if you will - perhaps some of the free books available online could be distributed with the distribution?

  72. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    Uhh maybe I'm missing something, but where precisely do you type "make menuconfig" if not the command line?

  73. YBT. YHL. HAND. by ckaminski · · Score: 1

    GP post comes up every other week or so, almost exact, word for word. Surprised it hasn't been modded to oblivion as Trollbait by now.

  74. Re:How about a stable ABI? by podperson · · Score: 1

    Insightful?

    A) Precompiled kernels are there if you want 'em. And you can compile your own if you want to. Much simpler, friendlier answer.

    B) Mac OS X's and Windows's search functions get closer to doing this search than most folks could easily get using the command line, so this is a pretty stupid example. Meanwhile, I think you might point out that having to edit the registry is no improvement over having to edit text files, both of which are about as necessary in the respective OSs.

    C) I actually think man pages are a step up from Windows's now absent DOS docs.

  75. Re:How about a stable ABI? by LinuxPoultergist · · Score: 1

    I don't know if your trolling or really serious, but I feel your post elicits a response either way.

    B) To call yourself a fairly technical user then start whining about having to drop into the command line is simply disingenuous. A command line is far more efficient and easy to work with than a GUI. Many times GUIs are a crutch which allow non technical people to do things they shouldn't be doing. Most technical people I know prefer the command line.

    A) Recompiling the kernel? Come on. Only in very rare cases do you have to do ANYTHING that requires recompiling the kernel. Your making that problem up. It simply doesn't exist for most users.

    C) Just because you don't like MAN pages, doesn't mean you have to villify them. Many volunteers have written great docs on sites like The Linux Documentation Project. If you don't like MAN pages do a little searching on the internet.

    If you are going to call yourself an advanced user please act like one.

  76. Issues wit any OS by Anonymous Coward · · Score: 0

    First I have been using some OS since 1984. I have admin and engineer experience with many OS's. There are issues with any OS/kernel. I have been using Linux regularly since 1997 and soley since 2000. Yet I really would rather use something like Linux with all of the support from the kernel dev's and user's out there. My cousin is having a really hard time with his Windows 2000 box get support it is always costing him an arm and a leg and the virus and other problems that just enundate WindowXXXX. Like I say I will continue using Linux as my sole OS for a long time.

  77. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    Gah. Clueless n00bs.

  78. Re:How about a stable ABI? by 32771 · · Score: 1

    The ABI doesn't matter all that much to you, even if you have to compile code yourself and use the prescribed compiler version. This is important when you are programming assembly, which you have already ruled out with your comment.

    In case you actually want to learn something new have a look at this:
    http://www.caldera.com/developers/devspecs/

    or this to get an overview:
    http://www.linuxassembly.org/

    You may have figured out by now that ABI means Application Binary Interface (How come you didn't write about it in the article?). As a user you run into trouble mainly when two compilers have to live together on one system, and they support a different ABI.

    See here for an example:

    http://lists.debian.org/debian-release/2005/04/msg 00153.html

    While all those changes may seem a nuisance to you, this may just be the thing some people are willing to accept to get some benefits out of not having to carry along the remnants of a legacy architecture.

    If that's not what you want then Windows may just be the thing for you. To say that Linux developers have failed is maybe a sign of a somewhat overboarding sense of self-importance. Don't forget, that those people frequently write the code for fun or to scratch an itch, if they are happy they certainly haven't failed.

    --
    Je me souviens.
  79. Re:How about a stable ABI? by ookaze · · Score: 1

    I'm a fairly technical user, not a tech god by any stretch of the imagination, but I know my way around

    Actually you don't, but have problems admitting it. That's one of the first problem you should overcome. I understand, given your attitude and perceived proficiency, the reactions you must have gotten from true technical users on Linux forums.

    I do all my own XVID rips from Vdub, I can install most Linux distros without a problem, and I'm damned proficient at packages like Photoshop and Illustrator. In addition, I'm a gamer from back in the DOS days, so concepts like editing text files (config.sys, autoexec.bat, etc) don't necessarily scare me.

    You are a vibrant example of the fact that you do not learn anything that lasts on a MS platform. Nothing of what you cited is actually valuable when learning to use a computer and understanding it. All what you learned will be lost. All the things I learned on Windows are lost already. On Linux it's the complete opposite. What you say also shows that people think they are technical when they learn such things, because clueless users around them praise them as gurus. Even your proficiency in Photoshop and Illustrator are very specialised and won't help you understanding how to use an OS.

    That said, as much as I like the concept of Linux, I simply will not try it any longer until I hear that a number of problems have been solved.

    Number one should be swallowing your pride and accepting you are a newbie. Your "problems" show it well ...
    Number two should be really understanding the concept of Linux (you meant FOSS, but you're a newbie), which you still did not grasp, your "problem" B is evidence of that. Of course, often, for various reasons, this means you have to buy a commercial Linux distro. You are not a freeloader right ? I thought so, because you would not have the indecency to make such complaints if you were one.

    A) Years ago, binary distros appeared to fix that very "problem". You are actually worse than a newbie for that matter.

    B) Any time you are forced to drop to a command line, you should inform the developer. That is, if you really understood the concept of Linux. But obviously you don't, so such a thing is beyond you. And as you are a newbie, you still see the command line badly, even though even MS is tripping over itself to provide a decent one. It's strange too, that you have to modify so many text files constantly in Linux. You must be applying the MS way to your Linux tests I think.

    C) You forgot to say what would "cut it" (since man pages and message boards won't). There is at least something positive : 50 % of the time, you got the answer you were searching for, which I find amazing because you are truely a clueless n00b like they called you. It shows because among the people giving you contradictory answers (or at least that's how you perceived the answers), you did not try one to come back and report to people what worked. FOSS is still a stranger to you I'm afraid.

    You are not in favor of Open Source, as you think, because you do not even understand it and the process implied by it. You do not even know the existence of binary distros that fix all the problems you have stated. Too bad, but this only means that if everyone was to switch to Linux, you would be one of the last.

  80. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    Well, i'm just curious why do the anti-gnu/linux (more fud | less insightful) stuff get posted by anonymous cowards ? >:)
    And, no i don't have an account.

  81. Re:Why is Linux so great? Please share your reason by bohemian72 · · Score: 1

    Besides being nearly a verbatum copy of something I've read before, this is really off topic as the announcement had nothing to do with either Quake or Linux on the desktop. Whatever these PCI changes are, maybe they'll be of interest in the server arena where Linux does have a sizable presence.

    --
    The greatest thing you'll ever learn is just to love and be loved in return.
  82. Kernel torrents by snuvlorgin · · Score: 1

    In case anyone's interested, a torrent for this latest Linux kernel is available at torrent.ibiblio.org.

    1. Re:Kernel torrents by PorchPuppy · · Score: 1

      Here is another comment that supports my original comment about a standardization for Linux users. There should be only one source for OS updates. While it is great that there is a bit torrent available, how do I know that this is an authentic release? One source for OS related updates. PERIOD.

    2. Re:Kernel torrents by Anonymous Coward · · Score: 0

      Perhaps once you've understood the difference between a kernel and an OS you might be able to make a comment that has some value.

  83. Re:How about a stable ABI? by DoofusOfDeath · · Score: 1
    Any time I'm forced to drop to a command line, you as a developer have failed. Back 10 years ago, this may have been acceptable. In this day and age, it isn't. Furthermore, while once in a blue moon I may change a text file in Windows, in Linux it's a constant occurence. Again, you have failed.
    Several points:

    (1) Unless you know what the author's intentions were for a program, you don't know whether or not he failed to meet his goals.

    (2) Some tasks are far easier on the command line than via GUI, because of stdin / stdout piping. It's also far easier to script together a set of command-line programs than a set of gui programs. You really should read Eric Raymond's great book, "The Art of Unix Programming".

    (3) Actually, YOU failed because someone gave you something for free, and you bitched rather than put your should to the wheel and helped fix it, you ungrateful self-centered ass.

  84. Re:Why is Linux so great? Please share your reason by diegocgteleline.es · · Score: 2, Interesting

    Linux packaging technology beats the ass of windows any time. I can click double click on .debs and get them openened by a installer just like .msi

    The problem is in how they're delivered and the lack of 1) a common packaging format and 2) lack of a common "package namespace" (ie: xorg can be called xorg in fedora and xserver-xorg in debian, that makes dependencies fail and can be only fixed by using a common packaging framework where developers and not distros makers package things)

    But Linux continues being much better than windows in some areas. For example, you've to download the .exe programs from docens of differents web pages. This becomes SCARY when you've to update things. For the vast majority of software you've to check for new versions visiting their web page and reading the text to check visually if there's a new version. Compare it to the magic of apt-get and emerge....I wonder when Microsoft will catch up with the early 90's and will develop a new .msi format where developers can suministrate a URL for a XML file which tells Windows what are the latest file versions of a given program...there're hints that makes me believe that they'll use RSS for this in Windows Vista, but I don't expect that much from microsoft...

  85. Re:How about a stable ABI? by Vicsun · · Score: 2, Insightful

    Snobbery like this is partly why Linux fails. GUIs are easier to use, especially for the non-technical user - i.e. 90% of computer users -or- who you should be catering to if you ever want Linux to be anything other than a niche operating system.

  86. Tannenbaum's Revenge? by Anonymous Coward · · Score: 3, Interesting

    Okay, this is something that's been on my mind a while, so I hope it'll get some amount of attention and hopefully an interesting reply or two.

    I also hope it's not going to get modded down to the seventh level of hell, as I'm about to (gasp!) express disagreement with Linus.

    First of all, I am vaguely concerned about the Linux kernel development. It's been a long time since there's been major improvements under the hood. I've had Linux desktops freeze on me. In the past, that never happened. Ever. I don't know which kernels are trustworthy anymore. I've read something to the extent that stabilizing kernels is now considered the Linux commercial vendors' job. Excuse me, but WTF?

    In the meanwhile, while we Linux types wave our dicks around and gloat over how great we are, the guys at Redmond are happily making it possible to change video drivers in their OS on the fly, and to unload a crashed driver without taking down the system. Will it work? Probably not 100% well right away, but trust me, they WILL make it work or they'll die trying. And Windows 2000 is proof that they can certainly do things well when they put their minds to it.

    And Linux is about to become the unstable OS choice and it seriously pisses me off.

    A very long time ago, Linus Torvalds and Andrew Tanenbaum had a since famous argument about the core structure of the kernel.

    Linus's argument was, if my memory serves, that it all boils down to pushing bits around, and that you should as well push the bits in the simplest way.

    And this is where I disagree.

    Kernel development is about pushing around the bits that will push bits around. Those are the bits you want to push around in the simplest way. The goal is not simply to produce a good kernel, it's to produce a maintainable, efficiently improvable set of source that will compile into a good kernel. Otherwise, the end product you get is a good kernel for its time that will be a bitch to drag into the future.

    Perhaps the state of the Linux kernel development today is but Tanenbaum's schadenfreude.

    Assuming that kernel improvements have indeed, as is my admittedly fragmentary view, slowed down worryingly, I find myself wondering if, simply, now is when Tanenbaum should be speaking up, rather than all those years ago. The structural needs then were simple: few consumer devices, reduced architechtural diversity. Today's aren't. And there is STILL no 'just-works' way for third parties to deliver drivers to their customers. The least worse they can do is deliver sources to the kernel maintainers and hope that 1) they will be accepted, and 2) there won't be too many months between now and the moment their customer's OS uses that kernel. Or they can ship scripts that will compile glue code between their driver and the currently running kernel, and hope that the customer has a freaking compiler installed. I'm sorry, I can compile drivers and upgrade kernels manually, but neither are acceptable solutions for the mass market.

    In fact, I'll go out on a limb and predict that unless the kernel's structure and development processes are rethought to take into account the use of an OS as a three-party system -- the OS vendor, the user, and the commodity/paraphernalia providers -- Linux will never be a significant player in the desktop market.

    Thought on that? Please, please, please prove me wrong. I'm a long time Linux user, I did in my time the mandatory contributions to the kernel that allows me to speak up and bitch now, and from what I can see the future is not looking well for the Linux kernel. So please prove me wrong. Thanks.

    1. Re:Tannenbaum's Revenge? by PorchPuppy · · Score: 1

      This is exactly my point. You speaking as a long time Linux user/contributor is very relevant to the point I am trying to make. Microsoft is actively working with hardware vendors to make it easier for them to design hardware that is compatible with the MS OS. What is the Linux community doing? I don't really know the answer to that other than to naively say that most likely, they are reverse engineering the code to work with the hardware instead of the otherway around. Has anyone here ever seen a sticker on a hardware product that says LINUX COMPATIBLE like you see with Windows Compatible products? That's because Microsoft acts based upon their standards where as Linux is a conglomerate of programmers around the world. Unless Linux contributors around the world start using a coding standard, we are always going to deal with these types of incompatibilities. Cheerio and pip pip to you all...

    2. Re:Tannenbaum's Revenge? by Anonymous Coward · · Score: 0

      Has anyone here ever seen a sticker on a hardware product that says LINUX COMPATIBLE like you see with Windows Compatible products?

      Yes. I first saw it almost five years ago in a RTL8139-based ethernet card.

    3. Re:Tannenbaum's Revenge? by Bent+Mind · · Score: 1

      Has anyone here ever seen a sticker on a hardware product that says LINUX COMPATIBLE like you see with Windows Compatible products?

      My HDTV3000 tv card was marked Linux Compatible, as was my Samsung laser printer.

      That's because Microsoft acts based upon their standards

      Yes, that's part of the problem. When is Microsoft going to support a common standard, like EFI? Linux has supported it for a while now.

      --
      Request a Linux Shockwave player here: http://www.macromedia.com/support/email/wishform/
    4. Re:Tannenbaum's Revenge? by slavemowgli · · Score: 2, Insightful

      I'd prove you wrong, but I stopped reading after you said that there's no major improvements "under the hood" (is there any part to the kernel that is not considered "under the hood") anymore. That claim alone shows that no matter how insightful you might otherwise be, you're completely out of touch with reality. :)

      --
      quidquid latine dictum sit altum videtur.
    5. Re:Tannenbaum's Revenge? by PenGun · · Score: 0

      You have no idea pooky. Study some ... it'll do you good.

          PenGun
        Do What Now ??? ... Standards and Practices !

    6. Re:Tannenbaum's Revenge? by dbIII · · Score: 1
      the guys at Redmond are happily making it possible to change video drivers in their OS on the fly
      Please read about linux - in most cases the video driver isn't in the OS and is handled by X, it's in userspace, and is just another process that can be started or stopped. Exceptions exist, like the Nvidia kernel module - but in that case it's no big deal to run the nv driver instead or to have two cards in the system with completely different divers.
      to unload a crashed driver
      It has been possible to build modular linux kernels for a long time - and they have been the default for years. Loading and unloading a kernel module is not a big deal.
      And there is STILL no 'just-works' way for third parties to deliver drivers to their customers
      Nvidia appear to disagree with this statement, as do many other hardware vendors that supply linux kernel modules and install scripts on their install CDs. Sometimes they do rely on gcc being present, but not always, the nvidia install script checks to see if you have a kernel it knows about (highly likely if you don't have gcc on the system) and downloads the appropriate binary.
      The least worse they can do is deliver sources to the kernel maintainers
      The alternative is drivers the kernel maintainers don't know anything about - which in the windows world was really one of the reasons the OS was crap for so many years (bad drivers) and why there is so much abandoned win98 only hardware (some of it very expensive). This was the big argument against the nvidia binary only drivers - it only works well so long as you can rely on the manufacturers writing good drivers and supporting old gear.
      Linux will never be a significant player in the desktop market.
      The desktop market is not about people who don't know much about computers installing bleeding edge kernels - it's about a sysadmin doing a remote install of a distro onto a dozen machines or more from the same kickstart or whatever script. Win3.11 with all its faults was ready for the desktop, this argument is incredibly old and stupid when everything is easier to use than Win3.11.
    7. Re:Tannenbaum's Revenge? by Anonymous Coward · · Score: 0

      By all means, no! I'd be grateful if you would be so kind as to post about some structural changes that you feel are relevant to my post. I AM aware that I am, not unlikely, wrong; what I would like to know is the REASONS why I'm wrong. That is why I was asking. Slashdot being Slashdot, I knew that I was likely to get a number of replies along the lines of, you're full of shit, Linux is perfect, etc. You seem better informed than those; please be so kind as to detail the reasons upon which you base your opinion. Thanks!

      However:

      > That claim alone shows that no
      > matter how insightful you might otherwise be, you're completely out of
      > touch with reality. :)

      I do not know if you were essentially replying in order to enlighten me, or out of an urge to take Linux's defense (which I could not blame you for), but I would not advise resorting to copouts such as the above. I do feel that my concerns regarding both the closedness of the Linux kernel to third parties, and the kernel's stability in a desktop environment, have not be answered, and your attiture, which might be read as willful denial, only increases my concerns.

      So I hope you won't mind my reiterating my demand regarding the two issues mentioned in the above paragraph: please *proove* me wrong. I thank you in advance.

    8. Re:Tannenbaum's Revenge? by Anonymous Coward · · Score: 0

      I thank you kindly for taking the time to reply to my post.

      However... I am sure you understand that, while I appreciate your attempts at reassuring me, frantic and -- please forgive me -- ill-researched denial is bound to have the very opposite effect, right?

      For instance, it is not possible to cleanly unload a crashed module, contrary to what you seem to think; likewise, *any* video driver based on the DRI architecture has a module in kernel space, that can take the whole machine down in case it crashes. Which, please correct me if I am wrong, you didn't seem to be aware of, were you? I am thus not certain what you were attempting to do when replying, as -- please forgive me -- it doesn't seem like you really understood the core of my concerns.

      I *do* appreciate that you took the time to write such a long post, though, once more, so thank you for that, if nothing else.

    9. Re:Tannenbaum's Revenge? by Anonymous Coward · · Score: 0

      > First of all, I am vaguely concerned about the Linux kernel development. It's been a long time since there's been major improvements under the hood. I've had Linux desktops freeze on me. In the past, that never happened. Ever. I don't know which kernels are trustworthy anymore. I've read something to the extent that stabilizing kernels is now considered the Linux commercial vendors' job. Excuse me, but WTF?

      You're confusing two different issues. "under the hood" changes have sped up, rather than slowed down. Look at the changes in memory management in the middle of the 2.4 series... look at the current rate of patches going into 2.6 kernels.

      Stability, on the other hand, is, indeed, down. There are more changes being made to the kernel, faster. There's no comprehensive testing in place; there are various branches where patches get tried for a while, and people can report when something doesn't work, but Linus ones said, to paraphrase, "if it compiles, it's great, if it boots, it's perfect" - breakage happens.

      > The goal is not simply to produce a good kernel, it's to produce a maintainable, efficiently improvable set of source that will compile into a good kernel. Otherwise, the end product you get is a good kernel for its time that will be a bitch to drag into the future.

      Linux doesn't do too terrible of a job of that. It could certainly be better, but they're not a posterchild for badness in that direction.

      > Assuming that kernel improvements have indeed, as is my admittedly fragmentary view, slowed down worryingly, I find myself wondering if, simply, now is when Tanenbaum should be speaking up, rather than all those years ago. The structural needs then were simple: few consumer devices, reduced architechtural diversity. Today's aren't.

      They haven't slowed down. Tanenbaum's points had to do with the the fact that microkernels are, in some ways, cleaner than monolithic kernels, and that, as a researcher, he greatly preferred microkernels to the older, traditional, but unpopular due to its shortcomings monolithic kernel design. Support for multiple platforms or devices is quite doable with either design, and Linux has become somewhat modular.

      > And there is STILL no 'just-works' way for third parties to deliver drivers to their customers.

      This is entirely unrelated to the kernel architecture choice above. It's a matter of backwards compatability. Linus has no interest in maintaining backwards compatability, even in source form, with older kernels. If that's a priority for you, you're probably suited better by another OS, such as netbsd - which has, incidentally, also a monolithic kernel. -THAT- is what makes driver distribution and maintainance under Linux such a pain. (on the good side, it allows for cleaner designs....)

    10. Re:Tannenbaum's Revenge? by dbIII · · Score: 1
      *any* video driver based on the DRI architecture has a module in kernel space
      I was not aware we were limiting this discussion to only those video drivers, you should be aware that there are others. If this point invalidates all I have said previously then so be it.

      As for the point that if a module brings the machine down it cannot be unloaded - that is perfectly accurate but by then it is to late for any OS to do anything about it. Modules that are causing less final problems can be dealt with in a variety of operating systems.

      it doesn't seem like you really understood the core of my concerns.
      The microkernal debate? It has been addressed by a lot of people. Look at some old entries on the hurd mailing list for all kinds of opinions. Other things? Hard to reply to an opinion of things not being quite right instead of examples of what isn't right. Is the new numbering scheme pissing you off and the lack of a 2.7 branch and some unstable stuff in 2.6?

      If the hurd was more open to outside contibutions it may well become the microkernel with decent drivers you appear to be interested in.

  87. Memory Management Change? by PhYrE2k2 · · Score: 1

    Sounds like the big 2.4 memory management VM change that messed so much stuff up, made at around this point in the 2.4 release cycle (I think .10?).

    Why aren't these major changes made when 2.6 is launched rather than changing things that may already be used in people's systems?

    Keep some compatibility and have more releases more often that aren't minor. I don't see how VM chnagesin 2.4 and this change in 2.6 are minor and considered acceptable by its users.

    -M

    --

    when you see the word 'Linux', drink!
    1. Re:Memory Management Change? by slavemowgli · · Score: 1

      Because that's the new development process. Stuff gets tested in -mm, and if it's deemed stable and useful enough, it eventually gets promoted to Linus' tree (or not). There is no development series anymore.

      The reason for that is apparent in what you say, too: in the old development process, such changes could only happen in an unstable series, which means that in the worst case, it'd take *years* until they'd actually reach the stable series where people could benefit from them (those who don't want to live on the bleeding edge, that is).

      If you don't like this, stick to 2.4. Or 2.2 - even 2.0 is still getting fixes. Or start your own, more conservative, kernel tree. But you won't be able to change the basic development process - it's been discussed to hell and back on lkml already, and, believe it or not, it's working.

      --
      quidquid latine dictum sit altum videtur.
  88. Re:How about a stable ABI? by 10Ghz · · Score: 1
    But, the argument that Linux is free and that "the developers don't owe you anything" is getting old


    No it doesn't get old, because they really don't owe anyone anything! Well, they DO owe something to their employers, buut some anonymous coward on /. is not Linus Torvalds's or Andrew Mortons employer.

    This isn't helping anyone's cause. Learn to take and use criticism to make a better OS.


    there is valid criticism, and then there are unreasonable demands. To me the GP sounded like one of those users who shout "This doesn't work like I want it to work! Fix it! NOW!". He MIGHT have something to argue about if he was a paying customer. And even then he should be complaining to his distributor.

    Seriously, where does this idea that users are entitled to something come from. Yes, it's great when things work really well, and everyone tries to make it work. But that doesn't mean that developers are required to bend over backwards because some almighty user feels that he's "entitled" to something.
    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  89. Re:Why is Linux so great? Please share your reason by zsau · · Score: 1

    Yes, because typing in "apt-get" or "emerge" makes so much more sense to new users than double-clicking an icon that says "setup".

    Apparently: I've met many a Windows-user who's petrified of installing software, but I've never had any difficulty with running apt-get.

    --
    Look out!
  90. Re:Why aren't we at 2.7 yet? or 2.8? by Deusy · · Score: 1

    People paying attention to Linux kernel releases are not non-technical. Non-technical people go with the latest version of their preferred distribution. The release numbers of the distribution are what counts to them.

    --

    Free Gamer - Free games list and commentary

  91. No shit by msormune · · Score: 1
    while all bugs from the change were believed to be found during the release candidate phase, it's possible that some devices may have problems.
    Yeah, this is really amazing news. It would be even more amazing if there were no devices having problems with each time there are some "major" changes in the kernel.
  92. The sad thing is ... by khasim · · Score: 1

    ... you won't be mod'ed up, but he will.

    I plan to test the new kernel on a couple of my servers this weekend just because of, as you noted, the PCI changes.

    As for the desktop, I'll wait until the Ubuntu people package the kernel update and automatically deliver it to me.

  93. You mean like this one? by khasim · · Score: 1

    Anonymous poster claims to be a pilot, too:
    http://science.slashdot.org/comments.pl?sid=159551 &cid=13360840

  94. Re:MOD -1 ASTROTURFING by Anonymous Coward · · Score: 0

    I've had problems with adaptec drivers that actually delayed deployment of several new servers the other year, that was adaptecs fault and as a result they are now on our vendor blacklist

    I use LSI also. Right now I'm having trouble with Megaraid 320 PCI-E cards overheating when under load. So tell me what the best solution for high performance SCSI and/or hardware RAID is on Linux. I'm mostly interested in DAS, but I'm also interested in any advice you have about SAN solutions also ... *if* you can back up your opinions.

    You wouldn't dream of using iptables?! And this is supposed to be an argument in support of Linux?! Iptables has worked very well for me indeed, solving lots of problems for a price that can't be beat; and I use it for much more than simple port blocking.

  95. Re:Why is Linux so great? Please share your reason by theurge14 · · Score: 1

    Troll all you want, but please don't insult my emerge! /gentoo zealot

  96. Re:How about a stable ABI? by alexq · · Score: 1
    As far as I can see, all of your concerns are GUI-layer issues. That shouldn't be the responsibility of the kernel developer, it should be the responsibility of some GUI administrative tool's developer...

    Which linux COULD definitely use - but I think the power of linux would disappear if the current interface were replaced by something like this.

    When a new feature is added to a linux kernel, because of its text-based interface, it's very easy for it to flow to the end-user. No one has to update GUIs, etc.

  97. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    Hmmmpfffff....

    Go away you clueless n00b.

  98. I've got a problem... by Anonymous Coward · · Score: 0

    Wnyone else who can burn DVD's only single-speed with the new kernels?

    I know it still works with 2.6.8 but reiser4 is only available for 2.6.9+ :-(

    Any ideas (except "use 2.4.x...!" or "reiser4 blablabla...!")?

    I would like to hear from someone if he can write DVD's with full speed using cdrecord (which version?) and a kernel newer than 2.6.8!

    Thank you!

    1. Re:I've got a problem... by WhiteWolf666 · · Score: 1

      Hi :)

      Yes, I can

      2.6.11, 2.6.13rc2

      Not sure of the cdrecord version, I'm at work right now, on my powerbook.

      Works for sure, though, at 4x.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    2. Re:I've got a problem... by PenGun · · Score: 0

      Not a problem at all. Get dvdrecord and use /dev/hdc or whatever. Lose the Schilling nonsense.

        You can write ISO or UDF if your kernel is configured properly. You can do on the fly UDF writes just like windows if you want.

        Works just fine, you can force speed if you want but I find it's detected accurately nearly all the time.

          PenGun
        Do What Now ??? ... Standards and Practices !

    3. Re:I've got a problem... by QuesarVII · · Score: 1

      growisofs from dvd+rwtools works great. It isn't just for dvd+, it works with dvd-r and dvd-rw too. Turn off scsi emulation in the kernel and have regular ide cdrom support turend on.

  99. Re:How about a stable ABI? by Makarakalax · · Score: 1

    In an ideal world we could have a stable ABI and all the benefits of rapid development, and rapid improvement. But that is not possible currently. We choose the benefits of an unstable ABI, and those of us who understand the realities do not try and sell Linux to people who can't use it. I'm sorry someone lied to you about Linux, I'm sorry some zealot made Linux out to be something it isn't. The reality is Linux is not the same as what you are used to, and it may never be. Please don't be annoyed about this, it doesn't achieve anything.

    I have a lot of respect for how MS manage to keep Windows so ABI stable. But it carries a lot of dead-weight with it. I love Linux because it strives for perfection. You apparently value other properties in your operating system, which is fine, but you have to accept that Linux is not for you.

  100. Re:MOD -1 ASTROTURFING by Anonymous Coward · · Score: 0

    So when is Longhorn due again?

    Delaying the addition of new features in order to focus on reliability and stability is much different than delaying release because you have nothing to ship yet.

  101. Re:Why is Linux so great? Please share your reason by Anonymous Coward · · Score: 0

    "Take installation. Linux zealots are now saying "oh installing is so easy, just do apt-get install package or emerge package": Yes, because typing in "apt-get" or "emerge" makes so much more sense to new users than double-clicking an icon that says "setup"."
    Isnt that why we have GUI programs like synaptic?? You can use synaptic without even touching the shell.. I actually think it is easier to install programs this way, than doing it on windows. On windows i would have to first download the installer and then manually install it, while on linux distros, it would do both automaticly.

  102. Re:Why is Linux so great? Please share your reason by Anonymous Coward · · Score: 0

    I could swear I see this exact post in every Kernel release story on Slashdot. No, it's not insightful, It's tired and repetative.

    Not to mention off-topic, package isntallation isn't the responsibility of the kernel devs, it doesn't even really have much to do with the kernel itself. Maybe if this were copy/pasted to every distro-related story, it'd be less annoying, and actually worthy of a plus whatever insightful.

  103. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    "B) Any time I'm forced to drop to a command line, you as a developer have failed."

    I learned how to read and write in first grade and have had no problem doing it ever since. However I almost never understand funny looking little pictures on the screen or what they are supposed to mean. Don't they teach reading/writing in school anymore?

  104. Re:Why is Linux so great? Please share your reason by Bent+Mind · · Score: 1, Offtopic

    User: "How do I get Quake 3 to run in Gentoo?"

    Zealot: "Oh that's easy! From a shell, su so you have rights to install software and execute emerge quake3.

    User: "How do I get Quake 3 to run in Windows?"

    Zealot: "Just click on the setup icon."

    User: "What setup icon?"

    Zealot:"The one that appeared in windows explorer when you put the cd in"

    User: "What CD? I need a CD?"

    Zealot:"Yes, or you can download a demo from any random site. Just make sure your anti-virus is up to date and your spyware programs are running."



    An interesting side note, The parent suggested editing /etc/X11/XF86Config and adding a section called "GL" and put "driver nv" in it. The Section is called Device and the nv driver doesn't support 3D. You need the nVidia driver for 3D.

    --
    Request a Linux Shockwave player here: http://www.macromedia.com/support/email/wishform/
  105. Re:Why is Linux so great? Please share your reason by Anonymous Coward · · Score: 0
    Linux is *not* user friendly, and until it is linux will stay with >1% marketshare

    blah blah blah


    Do you really think the kernel developers care about how easy it is for Joe Noob to install Linux and play Quake with it? I certainly don't, and I resent the fact that distributions like Lindows (or whatever it's called this week) and Ubuntu have drawn so many idiots to the Linux community because of their ease-of-installation.

  106. Re:Why is Linux so great? Please share your reason by ookaze · · Score: 2, Insightful

    anti-Linux (MS ?) Shills are at it again, with their support to mod them up. The oldest occurrence of this post I can find is this one : http://ask.slashdot.org/comments.pl?sid=135647&cid =11333134 .

    What's sad is that you see them coming from far far away, but the worst is that their arguments are always flawed.
    So they play with emotional things, and don't even get that right (Linux is *not* user friendly, and until it is linux will stay with > 1% marketshare, I suppose they meant < 1 % ...).
    And then, say stupid things like :

    Take installation. Linux zealots are now saying "oh installing is so easy, just do apt-get install package or emerge package": Yes, because typing in "apt-get" or "emerge" makes so much more sense to new users than double-clicking an icon that says "setup".

    Eliminating the context, and deliberately forgetting the part about the GUI, like Synaptic or Mandrake Update (which are available in the menu, with names like "Update your system" or "Add new applications").

    But wait, they are even more stupid than that !!!! They have no shame. They even talk about the difficultly of Linux configuration issues and then, to illustrate that, ask How do I get Quake 3 to run in Linux?. Which of course, has nothing to do with Linux configuration issues, and everything to do with the Quake 3 editor not providing a convenient installation method. I don't know Quake 3 per se, so I can't verify what these unreliable sources say, but if these guy http://wcuniverse.sourceforge.net/ can provide an installation file for their Open Source game that works on any Linux thanks to the very old Loki installer, I think any proprietary company can do it too.

    Oh but wait, I checked and Quake 3 actually comes with the same installer at least for the french version !!!!

    But of course, this old troll had to detail all the installation instructions of the NVidia driver and whatnot for XFree, to sound complicated. Trolls these days ... I suppose this one will be resurrected often though. Reminds me of the good old days, when old trolls were reappearing even though the problems were fixed a long time ago.
    Heck, today I just saw "X does not support PNP displays", "X is slow", "Linux has bad font support" ...

    Fortunately, anti-Linux trolls do not include "Linux has no games" when they talk about difficulty of installing Quake 3 on it, thank god !

  107. Re:Windows? by tendays · · Score: 1

    It's amusing how "does it run Linux" for an article about windows would get modded +5 Funny and "does it run Windows" for an article about linux get modded -1 Troll :-)

  108. fuck! by urbster1 · · Score: 0

    I JUST installed the 2.6.12 kernel yesterday! Son of a bitch! Looks like this will be another exercise in "learn how to compile a Linux kernel... again..."

  109. Re:How to tell if you are a linux fanatic. by Frank+T.+Lofaro+Jr. · · Score: 2, Interesting

    You will find people using Microsoft keyboards with Linux; for the reason that it doesn't suck as much as your crappy OS, and dont have to upgrade to a new keyboard after every three years.

    Does Microsoft make the keyboards themselves (I doubt it) or do they just outsource the production of them or license their trademark to the company which produces it?

    --
    Just because it CAN be done, doesn't mean it should!
  110. Ubuntu LiveCD by Anonymous Coward · · Score: 0
    Try the Ubuntu LiveCD, it worked for me (Plextor PX-716SA)

    I was able to use it to bootstrap my Gentoo install until I could install a custom kernal with STAT-ATAPI enabled.

  111. YES!!!!!! by OneByteOff · · Score: 1

    " Fix oops in fs/locks.c on close of file with pending locks" Fuck Yeah they fixed it! !, now my plan for World domination can continue!!!!

  112. Re:How about a stable ABI? by beanlover · · Score: 1

    Seriously, where does this idea that users are entitled to something come from.

    They are "entitled" by the fact that if you don't make the change to cater to them then they will find someone else who will. This may mean your particular project dies because everyone is ditching it for another, similar project because they have that feature...or it could be a very small minority that you can safely ignore.

    Other than that they aren't entitled in the least.

  113. Re:Why is Linux so great? Please share your reason by Anonymous Coward · · Score: 0

    I'm a Windows user, and I just set up Ubuntu 5.04 in a VMWare session. It looks awsome, and I was looking forward to playing with it.

    First install: VMware tools. Two files on the CD: .rpm and .tar.gz. Ok, so I checked around the net and found out I had to use the alien -i command to convert it to a .deb package. Did that. No luck - both files open with an 'Archive Manager'. No buttons in the Linux equivalent of Add/Remove Programs to say 'run this' (and the Help | Contents entry for 'Running applications' was blank).

    Apparently the original .rpm file was copied incorrectly, since I couldn't delete it afterwards. Had to remove it from a root command line, after searching the net for that command.

    I had to run a number of commands to mount the drive and copy the file, unzip it or whatever, and then try to install it (using a .pl file, which wasn't recognized by the commandline - so I had to find out how to run the perl command). Text installer, but works ok. Except it didn't recognize Ubuntu, so it wanted to recompile - and I didn't have the source installed.

    In the end I gave up. And with a number of other serious flaws (such as 'Search for Files' not being integrated in the file explorer, and it's inability to find a fucking folder with the specified name), and a whole slew of other things .. my conclusion is this:

    Ubuntu looks nice, but it won't replace my Windows system - or that of any of my friends' - for the next couple of years.

    I might try SuSe or some other linux distro, but at the moment I'm not optimistic that my experience would be better.

    I agree with one of the parent posters - Linux desperately needs to have more GUI options for day to day operations, and it sorely needs something like Windows Installer technology that works for all Linux distributions.

    Until that comes, Linux stays in a VMWare to play with. If even that. And I don't care if it's 'linux's (as in the kernel) fault, or the apps that we use or try to install - it all just needs to 'work'. That's my experience in Windows, and I expect the same ease of use with Linux before I'll make the switch.

  114. An Unstable Linux by MogNuts · · Score: 2, Interesting

    There are discussions here regarding Linux's instability. However, there is a bigger problem that exists which I have pointed out earlier.

    The issue is that it is not Linux that is unstable, but X (XOrg or XFree). I recently installed a multitude of distributions recently*. X crashed on all of them, many times frequently. All occurred within the first few days of installing. Bear in mind that not everyone has another computer hooked up to the Internet where one can SSH into the machine and kill X. For some, the crash of X is the crash of the computer. CTRL + ALT + BACKSPACE doesn't always work. This is my biggest issue with Linux or UNIX variants.

    I do propose a solution: a patch or replacement to X in where it does not run as root at all (to the uninformed, running X as a user still has parts run as root). If this is not possible, then revise it as such:

    1) Include only the minimal, absolute necessary code required to run as root
    2) A small, and as a result less complex, code will make it easier to reduce bugs and increase stability
    3) Make this root code standard across platforms (Linux and other UNIX variants) so no modifications which add to code size are required, again reducing code and enlarging the audience that can review the code

    Strip the code that runs as root the *barest* essentials and let all functionality run as a user. Long story short, whatever can't run as root can't crash your computer. Therefore, eliminate or make it as small as possible (significantly less than what X runs as root today).

    Are there working projects available that I am not aware of? Recently, I have heard that OpenBSD has something akin to what I am talking about. Is this accurate? What of GNU Hurd? If I remember correctly it implements some of this (at least to my limited micro kernel understanding); however, is it even usable yet?

    * I was let down by the new Debian Stable (stock install 3.1ra) (1 of 5 distributions I evaluated). It's wonderfully easy now and set up everything out of the box (mp3 and video support included which many users have been clamoring for from other distributions), but X crashes very frequently when switching to a VC and randomly crashes a lot in general.

    1. Re:An Unstable Linux by Anonymous Coward · · Score: 0

      Graphic drivers can't be moved into user space.

      X never crashs from my experence (see above).

    2. Re:An Unstable Linux by PenGun · · Score: 0

      A badly supported card, poor configuration. I find X to be real solid once you've set it up right.

          PenGun
        Do What Now ??? ... Standards and Practices !

    3. Re:An Unstable Linux by DarkDigger · · Score: 2, Informative

      You can already run X as non-root. Just don't start X at boot-up time. Then when you're computer finishes booting, login at the console, then type 'startx' and then inside of an xterm window, start up your favorite window manager. You now have X running under your username instead of root.

      There is however a security risk (to you, not the system) of running X as yourself, which is described here:
      http://www.gentoo.org/doc/en/fluxbox-config.xml
      Read the section entitled 'Preparing X11'

    4. Re:An Unstable Linux by MimsyBoro · · Score: 1

      I'm not very sure I'm right but here are two things which to the best of my knowledge are true:
      1. You can run a program as a user and crash a computer (as long as the user-level program can talk to kernel land, and it always can)
      2. X doesn't only run as root -- it actually writes directly to the video card memory and stuff like that. It's its own kernel. That is a huge problem.

      --
      God made the natural numbers; all else is the work of man - Kronecker
    5. Re:An Unstable Linux by KevinColyer · · Score: 1

      Are you sure this is not a hardware problem? It has the wiff of one to me...

    6. Re:An Unstable Linux by shish · · Score: 1
      $ ps aux | grep X
      shish ... xinit /home/shish/.xinitrc -- /usr/bin/X
      root ... /usr/bin/X :0

      X needs root to get access to the hardware

      --
      I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
    7. Re:An Unstable Linux by slavemowgli · · Score: 1

      Hum. The security risk is that someone with *physical* access to your machine while you are *not around* can use your account?

      I don't know, but that doesn't sound like such a big deal to me. If I'm not around and someone else has physical access to my computer, then I have lost anyway, no matter whether I'm logged in at that moment or not. He could just as well steal my computer (which does not require me to be logged in).

      --
      quidquid latine dictum sit altum videtur.
    8. Re:An Unstable Linux by Anonymous Coward · · Score: 0

      No, what you're describing is having an ordinary user *start* X. That's not the same thing as having the X server run as that user, since the executable needs to be root-suid (i.e always runs as root) in order to access hardware.

      That said, I believe one of the goals of Xegl is to change that so that the bulk of the X server runs as an unprivileged user.

    9. Re:An Unstable Linux by MogNuts · · Score: 1

      I thought the same thing at first (great point). However, the one exception I have found is Mandrake 9.1 in which I was using prior for a very long time. No crashes, X or otherwise--ever.

    10. Re:An Unstable Linux by MogNuts · · Score: 1

      Correct, I said I would want X to run as an unprivileged user. Thank you for a recommendation. You have any good references as where to find out quality info on it?

  115. Re:How about a stable ABI? by diamondsw · · Score: 1

    Wait, you're complaining about the kernel not being as fast to boot? Are you seriously saying Linux is fast at that, with it's bloody serial boot process, initrd's, slow as hell SCSI detection (for those who have it)?

    Am I trolling? No. I have a Dell PowerEdge 2300 2x400Mhz server sitting here, and two 800Mhz laptops. The Dell has a 6-drive SCSI RAID I/O subsystem (ServeRAID 3L, 6 x 9.1GB Seagate drives), and better bus speeds than the laptops. The laptops each load Windows (Thinkpad T21) or Mac OS X (iBook G3/800Mhz) in under a minute. The Dell takes a leisurely 5 minutes to boot Gentoo, Fedora, etc, taking a long time just to post (SCSI adapters, mostly), but then at least a minute and a half before reaching "INIT 2.85 booting" or somesuch, and then another minute or so after that. Windows on the same box takes (again) about 30 seconds to a minute after post.

    As for the CLI vs GUI, haven't we fought this enough? You can of course come up with a bajillion bizarre completely unrealistic examples that can only be done with a command line. I can come up with many simpler examples that are BETTER done with a command-line. What the original poster referred to were the bajillion things in Linux that would be BETTER done with a GUI (or best, a GUI wrapped around CLI apps). After all, what's the point of all of these piecemeal UNIXy apps that can be chained together if someone can't put a decent GUI on top of common operations and text files? If I *force* you to use a GUI, that's bad. However, if you *force* someone to use the CLI, it's every bit as bad.

    Finally, ABI. This isn't all that kernel specific, so it's not really germane; what breaks things isn't the kernel as much as things like glibc. And then once you upgrade a critical thing like that, you have to upgrade EVERYTHING else. I'm sorry, but you just don't see BS like that on Windows, Mac OS X, or anywhere else. That's just painfully fragile, and leads to the upgrade hell that turns people off to Linux.

    On Windows and Mac OS X, I can download an app as a single file (not all the time) and it just works. I can copy an app from one system to another (or even when upgrading systems) and it just works. In most cases, I can even copy kernel extensions from one system to another, upgrading at the same time, and it all still works (sadly, the ext2fs driver was one exception to this). There is true binary compatibility there, and this just doesn't exist on Linux.

    --
    I don't know what kind of crack I was on, but I suspect it was decaf.
  116. Re:How about a stable ABI? by Anonymous Coward · · Score: 0

    Uh, but "light-years" behind the Windows help system!!!

  117. Not metioned elsewhere by DaveAtFraud · · Score: 1

    The PCMCIA subsystem has been substantially re-written. The good news is that the lame support that was there before has hopefully been fixed. The bad news is that people who had something running with the old, lame support may find out that 2.6.13 breaks it. Support in Fedora is *probably* coming but don't expect it right away:

    > Date: Mon, 29 Aug 2005 01:23:22 -0400
    > From: Dave Jones
    > Reply-To: For users of Fedora Core releases
    > To: For users of Fedora Core releases
    > Subject: Re: 2.6.13 Kernel
    >
    > On Sun, Aug 28, 2005 at 08:36:30PM -0600, David G. Miller (aka DaveAtFraud)
    wrote:
    >> The 2.6.13 version of the kernel is now available from
    >> http://www.kernel.org/ as well as the usual mirrors. Anyone have any
    >> thoughts as to plans by Fedora to move FC4 to the 2.6.13 kernel?
    >
    >'soon'. But not probably not in the next week or two.
    >
    >> I'm normally not a "new kernel junkie" but PCMCIA support gets
    >> significant fixes in 2.6.13.
    >
    > read as: almost complete rewrite. It needs completely different userspace,
    > and is almost guaranteed to break existing configurations.
    > We're still trying to make it work in rawhide.
    >
    > I'm not sure how this is going to play out in FC4 yet.
    > It may even come to the extreme of reverting chunks of it so that
    > the existing cardmgr style in FC4 continues to work.

    Unfortunately, by the time 2.6.13 finished building on my laptop (HP Pavilion zv6015) last night, it was too late to do much besides see if it would boot (it did). Next step is get ndiswrapper working with 2.6.13 (haven't even recompiled it yet) and then see if a PCMCIA card I insert is at least recognized (it would be a nice start).

    --
    They that can give up essential liberty to obtain a little temporary safety deserve neither safety nor liberty.
    Ben
  118. Re:How about a stable ABI? by gartogg · · Score: 1

    And damnit, stop with the google posts too. It's getting ridiculous that every time that stupid tech company has a new online service, every geek in the world is supposed to stand up and clap.

    Also get rid of all of these stupid technical scientific posts, since nobody normal understands it anyways, and just leave the gaming stuff. Windows gaming. That's all anyone has a computer for, right?

    --
    I'm a concientious .sig objector.
  119. Re:Why is Linux so great? Please share your reason by Anonymous Coward · · Score: 0

    I know the OP was trolling, but your response (as well as the OP) is also based on assumptions. I mean, what if the 'user' cannot get his proprietary wireless card to work in Gentoo, hence no internet? What if he only has a dialup and emerge takes forever? What if he DID get it to install through emerge (assuming the gentoo installation itself wasn't too confusing), then his proprietary video card doesn't support 3D acceleration? ... Point being you can't ASSUME certain conditions and situations and use that as your basis to counter an argument (in this case) or to somehow illustrate that your option is in fact better than the alternative (which you allude to).

  120. Re:Why is Linux so great? Please share your reason by Frank+T.+Lofaro+Jr. · · Score: 1

    Do you think that anyone who can't compile a kernel or write an XF86Config is an idiot?

    --
    Just because it CAN be done, doesn't mean it should!
  121. Re:Why is Linux so great? Please share your reason by dtfinch · · Score: 1

    I've seen this post before.

  122. Re:How about a stable ABI? by runderwo · · Score: 1
    Windows on the same box takes (again) about 30 seconds to a minute after post.
    To reach the desktop. You know, it's still starting services in the background. A distro could do this just as well, but they have chosen to not present the user with the desktop until the system is fully loaded.
    This isn't all that kernel specific, so it's not really germane; what breaks things isn't the kernel as much as things like glibc. And then once you upgrade a critical thing like that, you have to upgrade EVERYTHING else.
    Bullshit. You can keep whatever crusty libc version you want around, installed in parallel with the current version. It will continue to work for applications that are linked against it.

    Maybe you are thinking about the C++ name mangling change? But that wasn't a glibc change, that was a GCC change, and it was done in the name of standards conformance. You know, so you can more easily combine objects created with different compilers. Is having more flexibility worth a bit of hassle or not?

    On Windows and Mac OS X, I can download an app as a single file (not all the time) and it just works.
    You can do that on Linux too. Just statically link your app.
    I can copy an app from one system to another (or even when upgrading systems) and it just works.
    Bullshit. You forgot about the registry, components, Application Data, etc.
    There is true binary compatibility there, and this just doesn't exist on Linux.
    That binary compatibility comes at a cost in terms of maintenance, and is important to very few users who have special-case requirements. Limited manpower means it is prioritized very low at this time compared to things like having hardware drivers that actually work. It's a growing pain, nothing more.
  123. If ctrl-alt-backspace doesn't work... by James+A.+Y.+Joyce · · Score: 0

    ...have you tried ctrl-alt-F1 to get back to the console? That may work even if X has stopped responding to ctrl-alt-backspace, as long as it's just X that locked up.

    1. Re:If ctrl-alt-backspace doesn't work... by Al+Dimond · · Score: 1

      Well... I've never had X crash that badly on me, but as far as I know (and correct me if I'm wrong) the Alt+Fn key combos are actually built into the kernel as a way of switching through terminals; when a program takes control of a terminal (as X typically does with, say, /dev/vt7) it can disable these commands, since in the case of X and many other graphical programs there are things that need to be done before the console is switched. The keycombos ctrl-alt-Fn from within X basically ask X to do whatever must be done, and then switch consoles (I don't know whether this is handled completely by X but I'd assume so). So if X is totally fucked to the point that ctrl-alt-bcksp doesn't work, I doubt that ctrl-alt-F1 and its brethren would work either. But again, I've never tried. I have been in situations where X was slowed to a near-halt because I was being dumb, and it took a long time for ctrl-alt-f1 to take effect so I could drop to the console and kill my stupid task.

    2. Re:If ctrl-alt-backspace doesn't work... by MogNuts · · Score: 1

      Another great point that readers should be aware of. Unfortunately, neither method worked.

  124. Re:Still doesn't work by PenGun · · Score: 0

    Fishing without a hook. The stream is muddy today.

        PenGun
      Do What Now ??? ... Standards and Practices !

  125. Re:How about a stable ABI? by exKingZog · · Score: 3, Insightful

    That works both ways - the users do not owe you anything either, which means that you can't complain if they then decide to go and use XYZ other OS.

    "Why do all these lusers keep using crappy Windows? They should use a product that they don't understand and that we refuse to improve for them because it's free and we don't owe them anything!"

    Because THAT'S a good sales pitch...

    --
    "If he were a plant, people would roll him up and smoke him."
  126. Re:Why is Linux so great? Please share your reason by Anonymous Coward · · Score: 0

    If you can't figure it out with the wealth of information on the internet, then yes.

  127. Was not serious by Danuvius · · Score: 1

    I was going for a healthy mixture of +1 Funny and -1 Redundant.

    My complaint is wholly faux and not meant to be taken seriously. =)

    But, good Sir, you are absolutely right of course... assuming one already downloaded and unpacked the 2.6.13 kernel and symlinked it up to /usr/src/linux.

    --
    Akarsz Magyar Gentoo fórumot? Akkor
    1. Re:Was not serious by Anonymous Coward · · Score: 0

      What I find amusing personally is that I honestly did recompile 2.6.12-r9 last night. It was in an effort to shave off a minute or two of startup time by getting rid of some DMA errors, though...

      --Arcum

    2. Re:Was not serious by stor · · Score: 1

      assuming one already downloaded and unpacked the 2.6.13 kernel and symlinked it up to /usr/src/linux.

      KHAAAAAAAAAAAAAAAAAAAAAAAAAAAN!!!

      Cheers
      Stor

      --
      "Yeah well there's a lot of stuff that should be, but isn't"
  128. Re:How about a stable ABI? by PenGun · · Score: 0

    Second that motion. Why do they always go on about how advanced they are when they obviously have trouble crossing the street?

      Yes with my karma ACs are my only friends.

        PenGun
      Do What Now ??? ... Standards and Practices !

  129. wealth of information on the internet by Anonymous Coward · · Score: 0

    The wealth of information on the internet is not always relivante nor correct. Most of the information out there is so outdated where it takes someone who already has an idea of what they are doing to figure out what to chose.

    (post anon because of mod)

  130. Re:Why is Linux so great? Please share your reason by cortana · · Score: 1

    You should have used my packages of VMWare. :p

  131. DVB / HDTV Improvements by tji · · Score: 1

    The 2.6.13 kernel also includes updates to the DVB c ode / drivers to support newer devices.

    - pchdtv.com HD3000 -- Previously, they used v4l drivers. It seems that the direction now is to use DVB drivers. The new kernel will work in DVB mode with th HD3000.

    - DVico FusionHDTV3 QAM -- Newly supported card, I have one & have tested it with OTA and cable (QAM) reception. Works great with MythTV (as does the HD3000).

    --

    Support for the DVico FusionHDTV5 cards is also under way. I'm not sure if it made it into the 2.6.13 release ( I doubt it.. patching the kernel will probably be necessary ).

    1. Re:DVB / HDTV Improvements by kelnos · · Score: 1

      Actually, the pcHDTV HD3000 DVB drivers (yes, the DVB, not the V4L) have been in the mainline kernel since 2.6.12rc2. I have one and I've been using the in-kernel drivers for a while now.

      --
      Xfce: Lighter than some, heavier than others. Just right.
    2. Re:DVB / HDTV Improvements by bani · · Score: 1

      How did you get cable reception working? Most cable providers encrypt or use some whackjob proprietary encoding. Or does yours have unencrypted channels?

      eg charter uses the Motorola DCT2000 which requires a whacko 2-way authentication system to the central office, with authentication keys and such. If you leave your tuner unplugged for a few days, they shut you off remotely from the CO by revoking your authentication key and your box stops working.

    3. Re:DVB / HDTV Improvements by tji · · Score: 1

      You can't get the premium channels, like HBO, Showtime, etc. But, most cable systems I have heard of have the locals available in the clear (I have heard the FCC requires them to be unscrambled, but I am not sure of this).

      My local Comcast system has ABC, CBS, NBC, and Fox in the clear. They also have InHD, InHD2, and ESPN-HD in the clear.

      Most cable systems use QAM256 encoding.

    4. Re:DVB / HDTV Improvements by bani · · Score: 1

      the locals are all analogue on charter.

  132. Re:YBT. YHL. HAND. by erlenic · · Score: 1

    I figured as much. I didn't mention it because I wasn't absolutely sure (I haven't seen the repeat posts yet) and didn't want to offend someone I was trying to help if I was wrong.

  133. Re:How about a stable ABI? by spitefulcrow · · Score: 1

    It's open source. Go write your own distro that can do everything automagically without ever showing you a command-line, and I'm sure you'll convert thousands of Windows users. NOT.
    You'll get added to the pile of "user-friendly" distros that grows every time someone bitches about Linux being arcane.
    I personally enjoy the power of the command line. Anyone who regards a GUI-enabled app as superior just because it has a GUI is a stupid computer user.
    You fail your trolling attempt.

    --
    Sorry, my karma just ran over your dogma.
  134. Re:How about a stable ABI? by diamondsw · · Score: 1

    To reach the desktop. You know, it's still starting services in the background. A distro could do this just as well, but they have chosen to not present the user with the desktop until the system is fully loaded.

    And numerous HCI studies have shown people value responsiveness over necessarily "real" speed. After all, what is preemptive multitasking other than a way to keep responsiveness while processing a lot of other things (and dammit, I know there is a lot more to it - I'm not looking at "Design of the UNIX Operating System" and "Modern Operating Systems" on my bookshelf for nothing here)? Linux has its philosophy; other systems used to handle things that way and abandoned it. Meanwhile, it still doesn't cover the abysmally serial nature of the Linux boot. Mac OS X flew when they parallelized the boot process (was that Jaguar or Panther - I forget).

    Maybe you are thinking about the C++ name mangling change? But that wasn't a glibc change, that was a GCC change

    I freely confess my ignorance of the specifics. I just know that whenever I go to update things in Gentoo, or in synaptic in ubuntu, or whathaveyou, more often than not I have to update a dozen seemingly unrelated packages because the new version of foo required an updated library of bar, and a whole bunch of programs dependent on bar suddenly need to be updated. Maybe it's just me, but I see a lot of similar comments and complaints.

    You can do that on Linux too. Just statically link your app.

    Then for God's sake, do it sometimes! I know, then you miss out on fixes and security exploits and such that could be fixed in one shared library, but this is seriously hell at times.

    Bullshit. You forgot about the registry, components, Application Data, etc.

    I said not many apps are single files (especially on Windows). On the Mac, I really can freely copy an application from one computer, and the vast majority of the time it Just Works. No hidden support files of whatever for most apps. Larger apps like Photoshop, yes (although even Microsoft Office can be copied by dragging its folder - everything it needs is right there).

    That binary compatibility comes at a cost in terms of maintenance, and is important to very few users who have special-case requirements. Limited manpower means it is prioritized very low at this time compared to things like having hardware drivers that actually work. It's a growing pain, nothing more.

    Then please get the Linux community to quit posting "This is the year of Linux" every damned year. It's not until these issues are recognized and accepted as legitimate.

    --
    I don't know what kind of crack I was on, but I suspect it was decaf.
  135. Caused some hardware to not work by robertchin · · Score: 1

    This one caused many hours of annoyance when some of my hardware stopped working. Apparrently you now have to pass no-apic as a boot argument now, if your computer has problems with apic (supposedly there was some fix in linux that meant people no longer had to have no-apic on, but not in my case with my MSI motherboard). Hopefully this hint saves at least one other poor soul from some hours of trying to figure out why their ethernet card no longer works properly (the driver loads, the interface appears, but the device doesn't actually work).

  136. Re:Why is Linux so great? Please share your reason by poofyhairguy82 · · Score: 1
    If even that. And I don't care if it's 'linux's (as in the kernel) fault, or the apps that we use or try to install - it all just needs to 'work'.

    Very sensible. You blame Linux (Ubuntu actually) for the faults of VMware. And then you say "I don't care if its not Ubuntu's fault, that should just work." Your demands are unreasonable.

    That's my experience in Windows, and I expect the same ease of use with Linux before I'll make the switch.

    If your Linux box much match exactly your experiance with Windows, you will never be happy. Ubuntu is not Windows, nor is it a copy, nor is it trying to be.

    But it does not matter in the end. Ubuntu and Linux do not need you and people like you: Windows users with high demands but no desire to help and make things better. Linux will get double digit desktop use by catering to most of the world that does not own a computer yet; people who have way less needs than you and are far less picky. Plus they might actually give something back besides complaints.

    Enjoy Windows, I'm glad there is an option that fits you. Just please note that Linux as a whole gains nothing by your "conversion" so there is little reason to help you with it.

  137. run the daemon :) by ^Z · · Score: 1

    What I like about FreeBSD is that it is noticeably more stable. Yes, with fewer shiny features.

    Really, if I need to run a heavy-loaded server, I consider FreeBSD first and Linux second. Your comment just explained why.

    Not that I don't like Linux or want to start a flamewar :)

    --

    Computers make very fast, very accurate mistakes

  138. Re:Why is Linux so great? Please share your reason by jownz · · Score: 1

    yes - only because they can't RTFM!
     
      jownz

  139. Re:How about a stable ABI? by poofyhairguy82 · · Score: 1
    On Windows and Mac OS X, I can download an app as a single file (not all the time) and it just works. I can copy an app from one system to another (or even when upgrading systems) and it just works. In most cases, I can even copy kernel extensions from one system to another, upgrading at the same time, and it all still works (sadly, the ext2fs driver was one exception to this). There is true binary compatibility there, and this just doesn't exist on Linux.

    Thats because Linux is not an OS like OSX and Windows are. Its just a kernel. Now if you take a Linux based OS, you will have the same results. An Ubuntu deb you install from the server will just work. If you copy that deb to another Ubuntu machine it will just work again. You can copy the settings, and your config files and it will still just work. Every deb file made for an Ubuntu release will work with every Ubuntu install that is of the same version. Its pretty simple.

    I know what you are implying. You are saying that Linux (as in everything that uses the Linux kernel) does not have binary compatibility. And this is true, because such compatibility is impossible. One version of Linux runs on a router. One runs on a cell phone. One works in my Tivo. One is just to make a computer into a firewall. One is for clustering machines. One is for desktop use. One is for servers. How are you supposed to unify all of these different Linuxs into one binary file? Can you install a Windows XP file on a Windows CE device? No? but Linux takes up the role of both....and fits into the market with both. Linux is just a kernel. Operating systems matter. OSes like Ubuntu, OSX, Windows XP, SUSE, or FreeBSD. Complaining that you can't install a file on every Linux install out there is like complaining that you can't install a deb file from Ubuntu into FreeBSD even though they use the same desktop environment....they are different OSes.

    Hope you learned something.

  140. Re:How about a stable ABI? by dnaumov · · Score: 1
    [Disclaimer: not a single byte of my code can be found in the official kernel tree, so take my words with a grain of salt. Still, I don't really imagine Linus using mouse for anything but cut&paste]

    Actually, Linus Torvalds is a KDE user.

    http://www.osnews.com/story.php?news_id=161
    http://dot.kde.org/1057763789/

    Yes, I know these links don't directly state he is a KDE user, but do a search for KDE on those pages and draw your own conclusions. You can use Google to see Linus has even reported bugs to the KDE team.
  141. Re:How to tell if you are a linux fanatic. by jasonmicron · · Score: 1

    For the record, none of my Microsoft Windows 2003 Servers have ever been compromised. They've been probed, prodded and thrown around the room a few times but never actually broken in to.

    Each admin runs their own game differently. Whether Linux or Windows, both provide great benefits as well as great risks.

  142. Re:Why is Linux so great? Please share your reason by Anonymous Coward · · Score: 0

    "An interesting side note, The parent suggested editing /etc/X11/XF86Config and adding a section called "GL" and put "driver nv" in it. The Section is called Device and the nv driver doesn't support 3D. You need the nVidia driver for 3D."

    Jesus if this isn't a perfect example of what he's talking about. How in hell would the average (i.e. "what's a config file" average) Windows user even have a clue about something like this?

  143. Re:How about a stable ABI? by runderwo · · Score: 1

    I did not claim one way or another that one approach to loading priority is correct and the other is not, and I don't believe that can be shown in general because different users have different requirements. (A server administrator has different requirements from a desktop user.). I certainly think that if this is some kind of stumbling block to user adoption, there will be some distro that takes the helm in addressing it.

    I must confess that I'm puzzled why you see shared library components as a problem. As long as you don't have dependency problems when you go to upgrade (in other words, use a quality and well-supported distro), what could be the matter, even if tens of dozens of unrelated libraries are upgraded at the same time. If that functionality wasn't in libraries, it'd be a static component of the application you are upgrading, so you get to download it in any case.

    As for installing apps in a single folder, I do this all the time for locally installed programs (that aren't managed by the package manager). Install into /usr/local/foobar-1.2 and link everything in /usr/local/foobar-1.2/bin to /usr/local/bin. If I want to get rid of that version of foobar I just trash the directory. Some programs are not smart enough to use relative paths, but that would be a bug in the program.

    As for your last comment, I do not speak for nor control the "Linux community". I was responding to your insinuation that some obvious and utterly important user need was being overlooked in the area of binary compatibility. I can still run a copy of Maple from 1995 and a copy of Quake 3 from 1998; QED in my case.

  144. "Train" Model by davecb · · Score: 1
    I'm pleased to see this change in the release progress, as it tends to drive more stability. Called the "train" model, it means that the release leaves the station the same time every year (day, week (;-)). The "Bus" model has the release happening whenn the bus (Linus's brain) is full and can't hold any more.

    --dave

    --
    davecb@spamcop.net
  145. XFS issues? by Confessed+Geek · · Score: 1

    A few months ago I was running into problems with XFS crapping out and sometimes even doing file corruption when the filesystem got past about 80% full. I had to drop back down to a XFS patched version of 2.4. Anyone who has been activly following the RC's for the last few minor versions... has this been addressed?

  146. Re:Why aren't we at 2.7 yet? or 2.8? by Anonymous Coward · · Score: 0

    Remeber the version numbering convergence to PI. The version number of an ideal piece of software equals PI. Real programs are never ideal and therefore have smaller version numbers. As they are perfected, the version numbers asymptotically approach PI. Linux is still at the very beginning of its lifespan and therefore it would be unwise to rush to version numbers that are too close to the goal state.

  147. Re:Why is Linux so great? Please share your reason by Keaster · · Score: 1

    No, they shouldn't have to SFTW RTFM or even study *FOO to use a PC that anyone can purchase from a retailer and use out of the box with minimal stress. Now, lets not forget that is is not the hardcore, but, the hardened that sit any whine about others abilitys, the same USERS that forget about the first time they re-compiled a kernel which I can guarentee even with step by step documentation was a bit stressfull.

  148. Re:How about a stable ABI? by DigitalReverend · · Score: 1

    I must not be geek enough, what is ABI?

    I have heard of API, use many API's and in fact have been involved in the development of a couple API's.

    This is the first time I have ran into the abbreviation of ABI. What is it?

    --
    I read Slashdot for the headlines, because the headlines, unlike the articles, are usually original and never duplicated
  149. Re:How about a stable ABI? by Mancat · · Score: 1

    Explain how Microsoft is forcing users to upgrade to SP2. There are still many users of SP1, and even pre-SP1, many who willingly refuse to upgrade to SP2 for a myriad of reasons.

    --
    hello dear sirs my name is jamesh i are india (bihar) can u guide me install red had linux 9?
  150. Win2K???? where were you the last two weeks???? by Anonymous Coward · · Score: 0

    What You Should Know About Zotob

    Zotob is a worm that targets Windows 2000-based computers and takes advantage of a security issue that was addressed by Microsoft Security Bulletin MS05-039. This worm and its variants install malicious software, and then search for other computers to infect.



    Windows 2000 Transitions to Extended Support June 30, 2005

    Microsoft is not ending support for Windows 2000. During the Extended Support phase, Microsoft continues to provide security hot fixes and paid support but no longer provides complimentary support options, design change requests, and non-security hotfixes.*


    * Unless you have an Extended Hotfix Support Agreement, which must be acquired by September 30, 2005, for customers who do not have Software Assurance.


  151. Re:How about a stable ABI? by DigitalReverend · · Score: 1

    Nevermind, I guess I wasn't geek enough. :)

    I found it.

    http://www.pcmag.com/encyclopedia_term/0,2542,t=AB I&i=37329,00.asp

    Slashdot: The more you know!!

    --
    I read Slashdot for the headlines, because the headlines, unlike the articles, are usually original and never duplicated
  152. Oh yeah?? by Anonymous Coward · · Score: 0

    Well, I've been using it since 0.01, and No kernel version has ever been even remotely stable for me (I've used every major/minor version)!! In fact, I'm compiling 2.6.13 by hand right now cause my 2.6.12 box won't stay up for move than a few seconds!!

  153. Surely that's the wrong way around? by Julian+Morrison · · Score: 1

    You make a major release, and the first thing you do is throw tons of new crap into it? Surely the first priority ought to be, to see how it shakes out in the much larger testbed of public use? Then new stuff should be added on top of a stable base, rather than hung off the side of some iffy point-zero release, where bugs will compound on top of bugs.

    1. Re:Surely that's the wrong way around? by Anonymous Coward · · Score: 0

      basically, it's just a fencepost issue. either way, you add features, then fix bugs. just this way, a kernel goes to the next revision when it's apparently bug-free, not when you've added features. The more time between the introduction of a feature into a codebase and release, the better, usually.

  154. Re:How about a stable ABI? by petermgreen · · Score: 1

    if you are carefull and use the right tools (things like autopackages apbuild and relaytool for example) you can make binaries that will run on almost all reasonablly recent normal i386 distros and on freebsd too for that matter if linux binary compatibility support is installed.

    The biggest problem comes from the way libraries and headers are normally dealt with on linux. e.g. if i build a gtk app normally on a system with gtk 2.4 then it won't run on a system with gtk 2.2 even if i don't use any of the new functionality from 2.4.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  155. Re:How about a stable ABI? by Rocky1138 · · Score: 1

    I understand your point and his, but you've got to realize that this type of person is the majority of computer users. If you want increased quality software (by bringing more developers [and money] to the table) and an increase in userbase, there has to be a way to find common ground for both parties: people who like to use the command line and people who want everything done by graphical means.

    That's the benefit of Linux, it has both. I just think that some of the command-line people should lower the 'holier than thou' elitist attitude that is very common in Linux. It's scaring Joe User away.

    By the same token, I understand the comment posted above that states the passenger of the car is trying to be a mechanic and wants to adjust technical things in a non-technical way.

    I am not very technically adept at Linux, but that shouldn't affect the value of my opinion. Nor should it affect the value of the original poster's opinion. Everyone starts somewhere, and the best way to find out is to ask questions. IE: Why are we doing it this way? Why not this way? etc.

    Tell me: Why can't someone create an app that compiles a new kernel? One that has checkboxes for every command-line switch?

  156. Re:Why aren't we at 2.7 yet? or 2.8? by Mancat · · Score: 1

    So, the ideal release of Windows was version 3.1?

    --
    hello dear sirs my name is jamesh i are india (bihar) can u guide me install red had linux 9?
  157. A new kernel model? by VincenzoRomano · · Score: 2, Insightful

    Maybe that the time has come for Linus to take in some consideration the need for a change in the kernel code model. As of today it is released as a monolythic piece of software wheighing 27+ MB of compressed code (almost 240 MB when uncompressed).
    If you add this to the complexity of an OS anyone can easily understand why a "partitioned" schema would greatly help the development.
    Of course I'm also thinking about an oldish querelle between Linus and Andy Tanenbaum about monolythic kernel and microkernel approaches. I'm not talking just about this, but at least about partitioning of the code into (almost) independed units.
    And maybe a microkernel approach could help to move in this direction: none can deny that both of them have a lot to teach about OSes.
    Please, send flames to /dev/null.

    --
    Maybe Computers will never be as intelligent as Humans.
    For sure they won't ever become so stupid. [VR-1988]
    1. Re:A new kernel model? by Anonymous Coward · · Score: 0

      um.. heard of modules?

      the kernel source is big because its ported to several differnet architectures

    2. Re:A new kernel model? by VincenzoRomano · · Score: 1

      Maybe I'm wrong, but modules are not there for development organisation issues.
      The portability code (/usr/src/linux/arch) is about 45 MB, the whole sources are about 250MB. No big save to have Linux run only on x86, for example.
      The kernel is big because, IMHO, it is complex!

      --
      Maybe Computers will never be as intelligent as Humans.
      For sure they won't ever become so stupid. [VR-1988]
  158. Re:Why is Linux so great? Please share your reason by Anonymous Coward · · Score: 0
    So, I guess the point I'm trying to make is that what seems easy and natural to Linux geeks is definitely not what regular people consider easy and natural. Hence, the preference towards Windows.

    "Easy" to a Linux geek means, "These series steps are logical and make sense".

    "Hard" to a Linux geek means, "All this black magic hides what's going on. How am I supposed to know if the "foo" audio|video|monitor|RAID controller is supported or make it supported if it isn't?"

    The notion that someone will make black-box installers that accomodate every target hardware invarient is unthinkable -- there must be a pattern or standard that is being leveraged... or is there? Maybe, my hardware isn't supported, but could be.

    Complex, scalable, extensible systems can exist only because of an underlying robust structure. Linux exposes that structure, whereas Windows hides it, or tries to. Without seeing the structure, a geek can't understand how and why and is reduced to having to learn what appear to be a myriad set of unreleated things. This is unacceptable because such shallow understanding does not scale the way that deep understanding does.

    Geeks don't want to know how to install a few most popular packages on a small number of platforms -- they want to know how to install anything that can leverage any hardware capable of providing the necessary capabilities said thing requires. Geeks buying a house want to know how a house is built, not just where the rooms are -- what if they want to change something?

    For some pepole, a capacity for deep understanding comes naturally, and tends to accompany a capacity for abstract thought. Lacking deep understanding results in a belief in not understanding at all -- shallow understanding is useful only in such restricted specific circumstances that it isn't worth the storage space in the brain to remember.

    So, yes, Windows is hard for geeks. Less so, if one develops for the platform, but that is generally not an option for anyone on a closed O/S.

    A lesser effect is that geeks don't seam to respond to the same kinds of cues "normals" do. Take pictographic toolbar icons, for example. Many times, I could not use a Windows app because I could not understand the instruction "to print, click the print icon" because the latter was non-obvious to me and the familiar File->Print was somewhow not available. "Where?" "On the toolbar" "With the other pictograms?" "Yes" "Which one?" "The print one!" "But which one is the print one?" "The one that looks like a printer!!". "That's a printer? I wasn't sure what it was." "So! The tooltip will tell you!" "There are no tool tips." "Yes, there are. Mouse over the pictograms." "On the toolbar...?" "Yes! (exasperated)" "Nothing happens." "Show me... (comes over to look)." "See, nothing." "NO!! Like this! (mousing over s l o w e r)" "And just how was I supposed to know how fast to mouse over? And what was mouse-over-able?" "No one mouses over that fast, they can't read the tooltips, and they'd pop up too fast and when they weren't wanted." "Don't assume how fast I can read. Anyway, thanks, I can print now... er, how do I make this app select the same stuff and print from a command line?" "Well, if it has automation.... but why do you want to do that?" "Well, I want to do this every day at the same time and not forget." "Oh, it has to have an automation interface, and you code to that." "So, does it?" "Dunno." "How do I add one? Well, if you ask real nice, and lots of people want it, it will get done." "But I need it soon!" "Well, you're the minority."

    ... and thus Linux was born: the "Unix philosophy" of stringing together the right bits to do what one wants is appealing to a minority of people because they deeply understand the simplicity and power of what looks to outsiders like gibberish. Yeah, doing something the first time is hard. But, you can do anything.

    To put it another way: Linux exists because someone found Windows hard. So, to argue that Linux is "hard" and Windows "easy" is just plain wrong as an absolute.

    Oh, BTW, how do I get an equivalent to a backquote in the CMD shell?

  159. is there any site by petermgreen · · Score: 1

    that tracks when security patches go into the linux kernel.so if i have a box thats running a kernel.org kernel i can see if that kernel has any known vulnerabilities.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  160. Re:How about a stable ABI? by paranoidgeek · · Score: 1

    Very good.

    Regarding the statement by the OP about man pages: If you are using a late version of KDE go into konqueror and type "man:/" then whatever man page you want into the address bar. On windows there is no common help 'area' is there ? KDE will even config 2.4 kernels through a GUI.

    The man pages are meant to be developer/power-user friendly not idiot friendly. For example the page pages for printf(3) but not howToUseAMouse(9).

    --
    Lima India November Uniform X-ray
  161. OT:How about a stable ABI? by Anonymous Coward · · Score: 0

    about drag'n'drop installing: Can be possible with something like kioslaves, rox-filer app folders or nautilus to wrap apt,yum or emerge so one can see a folder called "Respository" with all the available packages and another one called "Installed", so when you drag a folder from the first to the later, appears a dialog showing you the list of packages that will be installed, and asking you to confirm...?

    if i delete a folder from "Installed", the package is uninstalled; the "repository" folder has some extra items in the right-click menu like "edit repository list" and "update repository", and the "Installed" folder can have the option for "update","purge unneeded dependencies" and "repair broken dependencies".

    This could be made to shut up all those whinners that complain about apt... It's sad that they have to be tricked to make them quiet.

    1. Re:OT:How about a stable ABI? by penguinoid · · Score: 1

      You should look into synaptic. It is a GUI for apt (actually, for dselect) and is pretty much like you said. Others have told me that you can click a link to a .deb file and (with proper mimetypes, I suppose) be asked if you want to install it. Debfoster is a package that keeps track of which files you requested and which were dependencies for those, but needs integrating with synaptic IMO.

      --
      Don't waste your vote! Vote for whoever you want, unless you live in a swing state it won't matter anyways
  162. dma with sata by nri · · Score: 1

    still wont allow dma to be set when your laptop uses sata

    even compiling the ide parts as modules and loading them later doesn't help. applying the patch

    http://seclists.org/lists/linux-kernel/2005/Jul/02 73.html
    doen't help.

    even defining these /usr/src/kernel-source-2.6.x-blah/include/linux/li bata.h:

    #define ATA_ENABLE_ATAPI
    #define ATA_ENABLE_PATA

    doesn't help.

    hmm, bloodly Dell810's. It took me a week to get wpa wireless working on this thing. Lucky its a quite spell at work..

    (ps, i went with ubuntu instead of debian testing, bummer eh, probably all my own fault)

    --
    if :w! doesn't work, try :!cvs commit -m""
    1. Re:dma with sata by Anonymous Coward · · Score: 0

      DMA is automatically enabled on SATA drives.

    2. Re:dma with sata by nri · · Score: 1

      dell lappy dvd's use an ide interface which is controlled via the SATA controller.
      You can't easily set dms. even though the live CD does.

      lspci shows...
      0000:00:1f.2 IDE interface: Intel Corp. 82801FBM (ICH6M) SATA Controller (rev 03)

      sudo hdparm -d1 /dev/dvd
      Password: /dev/dvd:
        setting using_dma to 1 (on)
        HDIO_SET_DMA failed: Operation not permitted
        using_dma = 0 (off)

      --
      if :w! doesn't work, try :!cvs commit -m""
  163. Re:How about a stable ABI? by arkhan_jg · · Score: 1

    I don't mind people posting complaints or problems with linux, but when you've seen the 5th repost of the exact same complaint by an AC, and it's modded up every time, it starts to get a little trollish.

    --
    Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
  164. Obligatory AOL post... by fedux · · Score: 1

    Me too!

  165. Problem solving is a process by dbIII · · Score: 1
    My system worked perfectly with 2.4. It doesn't with 2.6. That's why I have a problem.
    Consider these questions:

    What in paticular is not working? What are your build options in 2.4.* vs those in 2.6.*? Have all the drivers for your hardware been updated to 2.6.* yet (some things like promise disk controllers only have old drivers) - what does the README in the directory for the drivers for the hardware that doesn't work properly have to say about the subject? All this may seem like a hassle, if so there are still 2.4.* kernels coming out.

    1. Re:Problem solving is a process by m50d · · Score: 1
      What in paticular is not working?

      I *don't know*. The system freezes.

      What are your build options in 2.4.* vs those in 2.6.*?

      The same, as far as possible.

      Have all the drivers for your hardware been updated to 2.6.* yet (some things like promise disk controllers only have old drivers) - what does the README in the directory for the drivers for the hardware that doesn't work properly have to say about the subject?

      The only external modules I'm using are nvidia and svgalib, both of which are updated. I assumed (perhaps naively) that in-kernel drivers would all be up to date with 2.6.

      All this may seem like a hassle, if so there are still 2.4.* kernels coming out.

      Yes, but my distro no longer supports them.

      --
      I am trolling
    2. Re:Problem solving is a process by phrasebook · · Score: 1

      I *don't know*. The system freezes.

      I'm another who has been getting the occasional freeze with recent 2.6 kernels. My hardware is not very new but has been very stable in the past. I've been through all the usual checks; temperature, memtest86 for days, hdd cables etc. but with no improvement. Right now I'm back to using 2.6.8 which seems to work ok (been up for more than 3 days with no lockup).

      When I get time I'm going to give FreeBSD another try. I tried it out some time ago but couldn't get my head completely out of Debian Land and ended up putting it in the too-hard basket. Everything I hear and see about FreeBSD is that it generally develops more slowly, conservatively and predictably than Linux does thesedays. I'm hoping I might be able to put more confidence in it than Linux 2.6. It's a real shame because I'm so happy with Debian otherwise.

      The worst part is that I just can't get myself to pretend that newer kernels don't exist. I keep wanting to upgrade, even though 2.6.8 appears to work ok. I guess it's because I feel that I should be able to upgrade without having these problems. It shouldn't be like it is.

  166. Re:How about a stable ABI? by ltbarcly · · Score: 1

    From: The desk of LinuxCorp
    To: Coward, Anonymous

    Here at LinuxCorp we pride ourselves in creating the most usable desktop environment and most stable server environment available. It might not be as pretty as OSX or as familiar as Windows, but this is the path we have chosen.

    I must regretfully inform you that your application to become a Linux user has been rejected. The following may have contributed to this decision:

    * Too little relevant computer experience
    * Intellectual laziness
    * Failure to understand that a different operating system might have a different philosophy with regards to any of the following:
    **installing software
    **uninstalling software
    **command line or lack of command line
    **hand holding
    * Belief that ability to perform mundane tasks corresponds in some way to computer knowledge or ability
    * Unhealthy fear of compilation

    We are sorry that we could not offer Linux use to you at this time. We hope you are satisfied with LinixCorp and will continue to recommend Linux to your friends and associates.

    We would like to again remind you that you are not to attempt to use any Linux product, and use of said product(s) may cause you to be accosted and / or threatened by one Richard Stallman.

    Sincerely,
    LinuxCorp AutoReject 2.0

  167. Re:How about a stable ABI? by ltbarcly · · Score: 1

    Linux succeeds every day where I work.

    And since we aren't skimming 98% of the effort going into linux in order to fund an ever larger house for Bill 'Reginald' Gates III and other assorted Fops and Dandies, it takes very little to support the community.

    So even with only 2% of the market share Linux is progressing faster than Windows, and only OS X is setting the pace, although OSX is built on a GNU base, and Darwin is OSS even if not GPL'd.

    So by all measures Linux is better for people who 'know' computers than windows. I know if I had to use Windows at work I would find a different job instead, developing on windows is painful.

  168. Re:How about a stable ABI? by dbIII · · Score: 1
    Any time I'm forced to drop to a command line, you as a developer have failed. Back 10 years ago, this may have been acceptable.
    Years ago I had an an Atari ST. One of the most useful programs on it let me run batch files and have a shell. The command line shell is an important and useful thing, anyone that thinks we should avoid it entirely has never heard of "grep" or moved files based on pattern in their name more comples than *.exe.
    to achieve the same things
    Like it or not it is different, there is no C: drive and never should be due to the differences, so you probably should not be trying to do the same things - a pop up search window may not be the solution while a few characters on the command line may well be. All that training in MS windows is sadly MS Windows specific, it's different and there is more than one way to do things.
  169. Re:How about a stable ABI? by too_poland · · Score: 0

    You pervert =]

  170. Lack of test data for released 2.6.13 under x86? by Anonymous Coward · · Score: 0

    Considering we don't have boot results for the released 2.6.13 kernel on a non-NUMA i386 ... maybe we should wait for a bit before installing it on our own x86 systems?

  171. If you are a geek then do something about it by kiwi_mcd · · Score: 1

    I am sitting here reading this and not believing what I am seeing. Everybody is complaining about the kernel but nobody is saying "I logged a bug report" or "I sent an e-mail to the maintainer".

    Yes I am a kernel developer (part of DCCP - to be in 2.6.14) but I cannot fix bugs if I am not told of them. And whinging on /. does not count!!!

  172. Re:How about a stable ABI? by 10Ghz · · Score: 1

    I don't think Linux-folks are really concerned about that. Sure, they would like more people using the software. But that doesn't mean that the users are "entitled" to something. If the user switches to OS X (for example), they wouldn't really care, since the people writing the software are doing it mostly for themselves. If someone else find their software useful as well, good!

    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  173. Re:Windows? by Triffid_Hunter · · Score: 1

    windows 2k/xp also runs beautifully in qemu, which is open source. '98 doesn't run quite so well, but it doesn't run quite so well natively either ;)

    qemu has available a free (as in beer) kernel module that turns it into a virtualiser rather than an emulator, which you can use if you want the speed of vmware without the cost, and are not bothered by non-oss modules in your kernel.

    with the kernel module, its slower than vmware only by a negligible amount, and vmware is definitely not worth the cost for the speed increase alone.

  174. Re:How about a stable ABI? by 10Ghz · · Score: 1
    They should use a product that they don't understand and that we refuse to improve for them


    The software IS improved. But it's not improved so that some AC on /. would feel better. If there is a way to make the system better, they will do it. But if someone comes along and demands (for example) that "I think it would be great if kernel handled the GUI as well! Do it!", he's not going to get very far. And when his suggestion is show down, he starts whining that the developers "don't care about the users".

    Because THAT'S a good sales pitch...


    But they are not "selling" anything. They are writing software. It just happens that many people find that software to be good and useful. But that doesn't mean that the developers owe the users anything.

    I mean, really! The developers write kick-ass software and give it away to users. And still some people think that it's the DEVELOPERS who owe something to the users, and not vice versa?!?!
    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  175. 2.6.13 broken on ATi based PPC machines by Jack+Malmostoso · · Score: 1

    Too bad, a patch between -rc7 and final broke the framebuffer in ATi based PPC machines (my iBook). Let's wait for 2.6.13.1

  176. a kernel a day keeps the user away by DirtyFly · · Score: 1

    wasnt that an apple ? Linux is really aproaching microsoft , in a year we will it its patch release timming. Linux should be about stability, im switching some of my servers to BSD now. This update stravaganza is killing me :) Bet ill get modded to troll fastest than the next kernel release .

  177. Re:How about a stable ABI? by exKingZog · · Score: 1

    Exactly, they're writing software. If they're not selling it (by which I mean actively promoting its use), why are you surprised when people don't use it? There are software users out there who have better things to do with their time that search out the best piece of software on SourceForge; they will simply buy commercial software where they KNOW that the developer owes them something.

    --
    "If he were a plant, people would roll him up and smoke him."
  178. Re:How about a stable ABI? by 10Ghz · · Score: 1
    If they're not selling it (by which I mean actively promoting its use), why are you surprised when people don't use it?


    Am I surprised? And last time I checked, that software IS widely used. And most users are grateful when they get that kick-ass software for free. then we do have those "Fix this! Now!"-types who feel that the developers are required to crawl at their feet and kiss their asses.

    they will simply buy commercial software where they KNOW that the developer owes them something.


    Well, the commercial developers don't really owe them anything either. If you have a problem with Windows for example, and complain to MS, you will most likely be ignored.
    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  179. Re:Why is Linux so great? Please share your reason by JPyun · · Score: 1

    Really, reading your comment makes me wonder what lame ass things you tried. a) Instead of a VMware Session, you should have just used the Ubuntu LiveCD. b) Search for the command to delete? What command? Right Click > Delete? Highlight > Delete Key? c) All your problems with installing could be avoided by either doing section a or using Ubuntu packages. Simply googleing "VMware Ubuntu" gives you a tutorial on as the FIRST RESULT. d) If you actually INSTALL Ubuntu it will auto-mount drives, CDs, iPods, etc. e) Applications > System Tools > Add/Remove Programs. f) Places > Search for Files. Most of your problems are from trying to use VMWare, which I'm almost sure you pirated. Or did you purchase a piece of software thats $299 last time I checked to test Ubuntu when you could have just burned the FREE LiveCD? When you can't even figure out Places > Search for Files, I wonder what the hell you are doing using something like VMware. Ubuntu GNU/Linux has it's flaws (some slight bugs in supporting my video card for one, Intel i810) but the community (ubuntuforums.org, ubuntuguide.org) are the best I've seen (they won an award at arstechnica) and once again, it's FREE. The first time you used a computer, did you sit down at your Wintel PC and know how to do everything you're doing now? No. People expect Linux to be a clone of Windows. The only thing is, it's better.

  180. Re:How about a stable ABI? by MikeDawg · · Score: 1

    Hence the post I wrote. After some research, it looks like it was mostly FUD I was reading in regards SP2 being forced upon the user. But all my points still stand in my original post.

    --

    YOU'RE WINNER !
    Another lame blog

  181. Questions to ask yourself by dbIII · · Score: 1
    I *don't know*. The system freezes.
    So we have a start, but you'll need to look furthur - try to remember what it was doing when it froze and look at the logs next time it starts to find out what it was trying to do - it may even just be an X lockup which would be fixed by a newer or older version of X.
    The same, as far as possible.
    That's a start - so look for the differences and leave out modules for hardware you don't need and options you don't want.
    that in-kernel drivers would all be up to date with 2.6.
    They may be called in different ways, so as I said before, what do the docs for the drivers for each bit of hardware say? Not simple, but if you do want to be on the leading edge not everything is going to be ready at the same time. As I said earlier, not all the hardware supported by the 2.4.* kernels in supported in 2.6.*, and some stuff may not be detected properly so the wrong driver may be used if you don't specify it in /etc/modules.conf.
    Yes, but my distro no longer supports them.
    How do things work with the kernel updates from the distro? What does knoppix have to say about your hardware when it sets things up with a 2.6 kernel? This should give you some clues as to setting it up yourself.
    1. Re:Questions to ask yourself by m50d · · Score: 1
      So we have a start, but you'll need to look furthur - try to remember what it was doing when it froze and look at the logs next time it starts to find out what it was trying to do - it may even just be an X lockup which would be fixed by a newer or older version of X.

      There doesn't seem to be any common factor, running the same programs after a lockup hasn't seemed to produce another one, and there never seem to be any unusual log entries. It's not just X, I've tried to ssh in when it locks up, no good.

      That's a start - so look for the differences and leave out modules for hardware you don't need and options you don't want.

      I've always built my kernels with the minimum I want/need. The differences in options seem to just be reorganisation of the menus - other than the inclusion of alsa, but I always had the alsa modules loaded when I was using 2.4.

      They may be called in different ways, so as I said before, what do the docs for the drivers for each bit of hardware say? Not simple, but if you do want to be on the leading edge not everything is going to be ready at the same time.

      I don't want to be on the leading edge. 2.6 is supposed to be a *stable* kernel tree.

      I've tried to troubleshoot this before, but it just seems to be a random lockup. It doesn't happen with this particular version and that will have to do.

      --
      I am trolling
    2. Re:Questions to ask yourself by dbIII · · Score: 1
      I don't want to be on the leading edge. 2.6 is supposed to be a *stable* kernel tree.
      The convention changed - there is no 2.7 tree for the leading edge, you are on the leading edge.
    3. Re:Questions to ask yourself by m50d · · Score: 1

      What was the change from 2.5 to 2.6 about then? I thought that was the 2.5 tree being declared stable, and it was only after that that it was decided development would take place within the 2.6 tree.

      --
      I am trolling
  182. Apt-get? by IpalindromeI · · Score: 1
    --

    --
    Promoting critical thinking since 1994.
  183. Then don't read typos by Engie_Viral · · Score: 1

    Do what I do, just read what was supposed to be there and move on with your life. If you freak about every typo on slashdot you are going to give yourself a heart attack!