Slashdot Mirror


Alan Cox Quits As Linux TTY Maintainer — "I've Had Enough"

The Slashdolt writes "After a stern criticism from Linus, the long-time kernel hacker Alan Cox has decided to walk away as the maintainer of the TTY subsystem of the Linux Kernel, stating '...I've had enough. If you think that problem is easy to fix you fix it. Have fun. I've zapped the tty merge queue so anyone with patches for the tty layer can send them to the new maintainer.'" A response to a subsequent post on the list makes it quite clear that he is serious.

909 comments

  1. Thanks by Hatta · · Score: 5, Insightful

    Thanks for all the hard work. Good luck to the next maintainer. Not much else to say.

    --
    Give me Classic Slashdot or give me death!
    1. Re:Thanks by haus · · Score: 1

      hear hear

    2. Re:Thanks by Deton8 · · Score: 5, Insightful

      After reading the thread on a mirror, it's important to note that after the argument, Alan and Linus continued to debate the technical merits of how to patch the bugs. The ongoing conversation was civilized and concise. Of course Linus is too much of a pompous ass to apologize to Alan for completely misunderstanding the problem and proposing dangerous and useless ways of fixing it, then arguing about it ad nauseum. Oddly, this doesn't seem to bother Alan or maybe he's just used to it. I don't personally care what happens to the linux kernel but let me suggest that any of you who depend on a stable USB stack need to take special note of whatever decision Linus finally makes.

    3. Re:Thanks by dotgain · · Score: 5, Interesting

      Not much else to say.

      How about "Nice work Linus, you'll have the entire kernel back to yourself any day now, I'm sure"

      Back three years ago I was sure I'd never leave. Now, I was no kernel dev, but I found out what it was like to try. In the meantime I grew up, and realised there's two sides to Linux.

      • The 'user' side, where you put up with limited, buggy and badly designed software, finding yourself grateful it even exists, and
      • The 'dev' side, where your success is proportional to the thickness of your skin. Your willingness to sit there and listen to argue with some other twit whose age you guess at 13 over something you know isn't furthering your project one bit. Oh, and telling people who post "I'm leaving" threads on the forum how wrong they are about everything, and how little their contribution was really worth anyway.

      Go and have a look at forums.gentoo.org, where you'll see both at work. I gave up too. For a long time I thought, through contributions and advocacy, I'd help Linux make some real headway in the Server and desktop market. Eventually I came to believe that it would never be big, it'd just mean more communities and more infighting and little real progress.

      So I'm sorry, Alan. I'm really sorry, but you've made the right move. Thanks for everything.

    4. Re:Thanks by abigor · · Score: 5, Insightful

      Former Gentoo and Debian user here...same experience exactly, except I actually did contribute code from time to time (well, mostly bugfixes). The Gentoo maintainers were particularly rude, and you had to pretty much be rude right back to convince them that what you had done was correct. Totally draining experience.

      In an offtopic note, I remember a sort of userland breaking point: I tried to drag and drop a jpg in a browser window (Firefox) to some photo editor. It didn't work. Macs and Windows have been able to do this since at least the mid-90s. I have no idea if you can drag an image from Firefox to the Gimp nowadays, and I don't care.

    5. Re:Thanks by Anonymous Coward · · Score: 1, Insightful

      Yeah, mod it Flamebait. That'll make that mean, awkward truth go away.

    6. Re:Thanks by krkhan · · Score: 4, Informative

      I tried to drag and drop a jpg in a browser window (Firefox) to some photo editor. It didn't work. Macs and Windows have been able to do this since at least the mid-90s. I have no idea if you can drag an image from Firefox to the Gimp nowadays, and I don't care.

      Just tried it, GIMP connected to the server and pulled the image from there. Not sure if that's how you want it to work though.

    7. Re:Thanks by dynamo · · Score: 2, Interesting

      Agreed. Alan, thank you for all the hard work for so many years. You deserve a vacation.

    8. Re:Thanks by Knara · · Score: 4, Insightful

      It's probably a case of them both recognizing "it's just business." You can like someone but be totally unable to work with them, after all.

    9. Re:Thanks by timeOday · · Score: 2, Insightful
      What I find interesting is that the top people in all organisations are like this. Politics is an obvious example. Look at Larry Ellison, Steve Jobs, and Steve Ballmer, you think having a disagreement with any of these guys would be fun, or that they're always right? Even the more senior managers where I work have big arguments and personal vendettas.

      I like the idea of owning a business, but at some point I'd probably hire somebody like that, and they'd probably take control over from me. Being willing to go out on a limb and take a stand with no fear of being proven wrong (even though you sometimes are) seems to be a job requirement for gathering a following.

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

      "The 'dev' side, where your success is proportional to the thickness of your skin. Your willingness to sit there and listen to argue with some other twit whose age you guess at 13 over something you know isn't furthering your project one bit. Oh, and telling people who post "I'm leaving" threads on the forum how wrong they are about everything, and how little their contribution was really worth anyway."
      ...and how exactly is this different from any other work in IT ?

    11. Re:Thanks by dotgain · · Score: 2, Insightful
      Obviously it depends on the scenario, but the presence of a boss often stops stupid little arguments that don't further the purpose from happening. I've had my boss stick up for me when someone else has been a dick, and I've been told to shut up and listen for a minute when I've been a dick. Sometimes the boss fires someone because it's too hard to stop them from being a dick, in spite of whatever intelligence they possess. Last time I got fired was 12 years ago, I didn't see it then, but I do now: it was because I was being a dick, and my boss was right to fire me. Sometimes I was technically correct, but still giving priority to being a dick.

      It's not only IT - in the activity of parenting and marriage both my wife and I have seized opportunities to make dicks out of ourselves to each other. And just like this Cox/Torvalds incident, sometimes the way through isn't knowing whose right or wrong, it's acknowledging you were a dick and apologising.

      It's basic social relationships at work here, not bugs in kernels. OSS groups are like relationships, and have their associated problems. Having a boss is in a way like having a full-time relationship councillor on board. Cox/Torvalds happened because nobody stood up and said "hey guys, come on". I don't care which of the two were right about the TTY bug, there was no way that needed to erupt into the argument that it did, yet time and time again it happens. Imagine what the FOSS world would have been by now if people could have swallowed their pride rather than pack their bags and spread the skills thinly by way of forking.

    12. Re:Thanks by ioshhdflwuegfh · · Score: 0, Redundant

      I have no idea if you can drag an image from Firefox to the Gimp nowadays, and I don't care.

      Me neither.

    13. Re:Thanks by logfish · · Score: 1

      We still love you Alan! Pursue your happiness and we will be happy.

    14. Re:Thanks by Anonymous Coward · · Score: 1, Informative

      That's not Linux, that's KDE or Gnome you are talking about.

    15. Re:Thanks by RichardJenkins · · Score: 3, Insightful

      That was an anecdote! no steps, no software versions, no expected result == no bug. let's be a little more formal:

      Prerequsites:
          Ubuntu Intrepid Ibex, default packages installed, all updates as of 2009-07-29 applied.

      Steps to execute:
          1> Open Firefox 3.0.12
          2> Navigate to www.google.com
                * Note the prominent Google logo
          3> Open GIMP 2.6.6
          4> Drag and drop the Google logo to the GIMP toolbox

      Expected result:
          1> GIMP establishes a connection to the remote server and downloads the image
          2> GIMP opens the image for editing

      Result:
          PASS

      Does this cover your needs, or are you just trolling?

    16. Re:Thanks by leenks · · Score: 1

      It's called leadership.

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

      Before accusing someone of trolling, check they're really replying to the comment you think they're replying to.

    18. Re:Thanks by Eravnrekaree · · Score: 1

      I definitely know what your talking about. I have had experience with the rude, arrogant developers, and the simply brain dead design on Linux, that causes a simple thing like drag and drop to not work at all.

      One of the problems with Linux useability is the lack of backwards compatability which is essential for useability and for Linux to become an OS that can be used by most people and stable application and driver ABIs. This is important since many times users will not want to wait years for a driver to be made for their hardware by an OSS developer. Hardware manufacturers develop anbd test drivers and make sure they are highly reliable. My own expierence is that windows hardware support is many times more reliable and complete than Linux. No hardware vendor wants to support Linux buecause its poorly ddocumented, and there is no stable ABI. They dont want to maintain 20 different binaries for different kernel distro combos. Linux developers pride themselves in making Linux hard on users who just want to use hardware by making it hard to make a binary driver for Linux. Not every driver or application a user wants to use will be in the kernel source tree or the native package installer and thats just a fact we have to accept. Sometimes users will want to install a driver on an older install of Linux, they dont want to do a full blown upgrade of Linux just to install a driver, and they may want to be able to use an older driver with a newer Linux. Its arrogant to assume that every driver the user needs will haev come with their Linux DVD. What happens if they are using a peice of hardware which came out after they installed their Linux?

      On Windows, you just throw in the disk, click ok, and your hardware is working. On Linux is just too painful a process to install drivers and third party software and that keeps it from being used in ther mainstream.

      Ironically, by allowing for more ease of third party drivers and software, Linux would become more useable and thus the deployment of open source software would be greatly expanded. By puuting up with some binary drivers and proprietary applications we can actually increase the amount of open source software in use in the world greatly.

      ABI Backwards compatability is essential for Linux to be useable, both in the kernel and in X. Linux too can be user frtiendly and expert friendly at the same time, by creating a user friendly API on top of the CLI environment you have a choice between either. The key to useable software is not in sparse features, you want software to be as configurable as possible, but in placing lesser used features in expert screens and such, and more commonly used features up front. So useability is in layout, not in having few features.

    19. Re:Thanks by commodore64_love · · Score: 4, Insightful

      I can understand his frustration. I've walked-away as well from various clubs. You volunteer hundreds of hours of your time, without pay, and all you hear from the members is complaint-after-complaint-after-complaint.

      You eventually reach a point where you say, "What am I doing this for? No one's appreciating it or saying thanks. I could be out having fun instead of this shit," and then you stop volunteering.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    20. Re:Thanks by Anonymous Coward · · Score: 1, Insightful

      Studies have shown that a significant fraction of managers (disproportionalely large compared to the general workforce) exhibit sociopathic/psychopathic tendencies. No reason the free software realm should be any different.

    21. Re:Thanks by Derek+Pomery · · Score: 1

      You can.
      Not sure since when.
      At least GIMP 2.5/2.6.

      --
      -- perl -e'print pack"H*","6e656d6f406d38792e6f7267"' /. ate my old sig. Bastards.
    22. Re:Thanks by commodore64_love · · Score: 1

      Where does somebody go if they want to see this TTY code first hand?

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    23. Re:Thanks by RichardJenkins · · Score: 1

      D'oh, how embarrassing.

    24. Re:Thanks by commodore64_love · · Score: 2, Interesting

      >>>The Gentoo maintainers were particularly rude

      Couldn't you just avoid the forums and focus on coding? Then when it's done, hand it over and say, "Here is it. Peer review it and I'll make the changes." Ignore rude persons by killfiling them (first give them a warning; then if they are still rude, block 'em).

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    25. Re:Thanks by Dog-Cow · · Score: 1, Flamebait

      I'd say huge FAIL. An app should have no need to know about http to get an image from any program to an image editor. What would happen if you dragged it out of an email attachment? Would gimp use imap to retrieve it?

      Linux GUI usability is a huge FAIL compared to its commercial competitors.

    26. Re:Thanks by commodore64_love · · Score: 2, Insightful

      I don't waste time arguing with my manager.

      I simply don't care enough about the project. For me work is just a means to acquire money so I can live comfortably, so I just do whatever the manager asks me to do, unless it's exceptionally stupid in which case I'll suggest an alternative action, but I still won't argue over it.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    27. Re:Thanks by Anonymous Coward · · Score: 0

      more communities and more infighting and little real progress.

      Democracy in action. Been there, done that.

      And Alan really shows the true nature of the Linux dev environment: EGO = caring. And it's not wrong in that environment and keeps that environment rich in innovation. Since, because to most of us, we care because we are being paid ($$ = caring) where as to Alan, he cared cause of his ego and now his ego has been unprofessionally squashed in some "human git rebase".

      Hence, in the end, he was right to leave.

      Thanks and good luck Alan. As for the rest of the kernel community, keep this up and the big corporations will swoop in, fork everything, and likely end up with a better system for the rest of us a la Debian vs. RedHat (or do I smell some sell outs here?).

    28. Re:Thanks by KangKong · · Score: 5, Insightful

      I switched to *BSD 5-6 years ago, the reason being that the community was more relaxed and there was less politics. I've been really happy, the users are more informed and the developers are more eager to help out and less elitist. The best technical solution is chosen and there is way less "not invented here" attitude among the developers. The development is more structured and is not based on the opinions/goals of a single person.

    29. Re:Thanks by Mycroft_VIII · · Score: 2, Insightful

      I'm sorry, how is an IMAGE manipulation program connecting to the internet when passed an image from another program the expected result, isn't this kind of crap what made Outlook Express (which WAS expected to connect to the internet!) such a huge virus vector.
            If I drag from app a to app b I expect the two apps to pass the data itself, in this case an image, NOT connect to a third party on the net. The only time I'd expect some other behavior is when app b isn't capable of handling the data, IE passing a pdf file to an mp3 player would be an ok reason for an error message.

          Sorry if that's a pass then I'd rather have a fail the just passes the image across.

      Mycroft

      --
      https://signup.leagueoflegends.com/?ref=4c3ed6600b6ea
    30. Re:Thanks by Anonymous Coward · · Score: 0

      I have no idea if you can drag an image from Firefox to the Gimp nowadays, and I don't care.

      (emphasis added)

      Yes. Yes, you can.

    31. Re:Thanks by Anonymous Coward · · Score: 0

      Where does somebody go if they want to see this TTY code first hand?

      I don't know the specifics of accessing kernel development source repositories. But it strikes me as very unlikely...that you would be suitable to dig into the code, but that your first stab at finding the source would be through a question such as yours directed to the Slashdot community in this context.

      Anyway, so as not to be thoroughly unhelpful, I suggest you have a start here: http://www.kernel.org/

    32. Re:Thanks by iserlohn · · Score: 5, Insightful

      The unstable ABI is the result of the kernel devs wanting for devices drivers to be in the source tree. The implication is that with a stable ABI, there would be no incentive to release source code and to include this code in the kernel.

      Windows H/W support from my POV is abysmal, and that is even with MS' at-all-cost backward compatibility culture. Creative's SB Live drivers do not work at all in Vista. They work fine on all recent versions of Linux distros. Because Windows is so widely used, H/W manufactures have to make passable drivers in order to get their product sold. However, once they are finished with selling them, you get situations like these in which old devices are unsupported. Normally this is ok as the backward compatibility works, but it doesn't all the time.

      From my point of view, the current Linux dev model for driver is the right way to go with the current state of things in the free software world. Having a stable ABI for kernel modules will fix some short term problems but cause long term ones in the dev model.

    33. Re:Thanks by Pyrion · · Score: 4, Interesting

      On Windows, you just throw in the disk, click ok, and your hardware is working.

      Unless you're running Vista x64, have 4GB or more of memory, and are trying to install the drivers for a TV tuner. Doesn't matter which manufacturer, they all would tend to fuck up under such conditions. I gave up trying to get TV tuners to work on my rig after wasting close to $250 on various models cuz I found only one commonality amongst them: they don't fucking work.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    34. Re:Thanks by Pyrion · · Score: 1

      Now for a bit of unexpected hilarity, try the same thing with GIMP for Windows.

      It won't work.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    35. Re:Thanks by Intron · · Score: 2, Informative

      A browser gets the original image from the server along with html tags width & height and information about your PC's display mode. Then it mangles the image to fit - losing resolution and pixel depth along the way. An image editor like the GIMP wants the full-size original.

      --
      Intron: the portion of DNA which expresses nothing useful.
    36. Re:Thanks by chebucto · · Score: 1, Offtopic

      That's not Linux, that's KDE or Gnome you are talking about.

      Pedantry like this, which willfully ignores the issue at hand, is a kind of passive-aggressiveness which is an example of the attitude problem the parent was referring to.

      --
      The English word fart is one of the oldest words in the English vocabulary.
    37. Re:Thanks by smash · · Score: 1
      Blame creative. Besides, as a former sb-live on linux user, i went through many many months of having no audio output without totally rooting around with different versions of ALSA because the linux driver blindly decided to use digital output, and who the fuck cares about anyone on analogue.

      Solution to the problem? Go back to an old inferior card? Wait?

      At least with the windows box your solution is to fork out $20 on an audigy...

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    38. Re:Thanks by RichardJenkins · · Score: 1

      A universal way for image editors to import data via drag and drop from any arbitrary program would be nice - I don't believe it exists on Linux or Windows though.

      To get the type of integration you're alluding to it is the applications you'll need to constrain. The use case I describe would work the same way on Windows rather than Ubuntu, whilst dragging an image from Firefox to Visio 2003 would just result in a useless plain-text label being displayed.

      Both Linux (via GNOME) and Windows (via OLEDB) have mechanisms that allow applications to transfer data and negotiate content types between themselves in whatever format the application designer decides to do use. Mozilla decided to do it by sending text URL; IE does it by sending the graphic. I'm not sure what other browsers send when you drag images from them - I'd be very surprised if they were all consistent. Certainly if you dragged from an application that sent image data rather than a URL, GIMP would happily use that.

      I'd buy the argument that many different desktop environments and themes between Linux distributions are extremely confusing - and wouldn't contest an assertion that whilst I'm most productive in GNOME it says little about usability for a majority of computer users - but not that the GUI usability in GNOME sucks compared to the competition because GIMP can interpret URL's it receives from arbitrary applications.

      You can probably tell I know very little about how Drag and Drop works in OSX: can't afford a Mac.

    39. Re:Thanks by cathector · · Score: 2, Informative

      this particular exercise can be a bit subtle, at least in windows. (i know this is a linux discussion, but it may apply)
      if the image is a Link, then what gets "dropped" onto the target application is the URL of the link, which many apps handle just fine. if it's not a link (ie it's an image tag not wrapped in an anchor tag) then what gets dropped is the binary data of the image itself, which fewer apps handle because it's a pita.

    40. Re:Thanks by rohan972 · · Score: 1

      The 'dev' side, where your success is proportional to the thickness of your skin.

      Possibly this affects kernel developers particularly but it is still generally true of any occupation or business. Learn to develop a thicker skin and you'll be amazed what you become capable of accomplishing.

    41. Re:Thanks by kjs3 · · Score: 1

      Cite, beyond the single limited study I'm aware of that doesn't really prove the point but makes an excellent way of boosting the authors Google search score when they apply for their next grant?

    42. Re:Thanks by f0dder · · Score: 1

      You're kidding right? I am linux noob.. but wouldn't the answer be to download the source code?

    43. Re:Thanks by rs79 · · Score: 1

      "It's called leadership."

      It's called psychosis. Get used to it maggots, that's the way the world works. Do better when it's you.

      http://www.bullyonline.org/workbully/serial.htm

      --
      Need Mercedes parts ?
    44. Re:Thanks by RichardJenkins · · Score: 1

      Firefox sends a text URL when you drag and drop an image - I'm not sure why Mozilla built it that way, Konqueror looks as though it sends the actual data. Perhaps that's partly why it is still behind IE in usage rates.

      Certainly behaves the same regardless of platform though - so it rather poignantly highlights the fact that data import/export is in the realm of the applications rather than the OS.

    45. Re:Thanks by RichardJenkins · · Score: 1

      The use case I describe would work the same way on Windows rather than Ubuntu

      ...or maybe it just fails outright on Windows.

    46. Re:Thanks by Kjella · · Score: 1

      Amen to that. The only binary I tolerate is nVidias blob, and that's only because it's much better than the AMD open source drivers at the moment. Once they reach parity it's bye-bye blobs. Everyone else get with the program already, I don't want blobs just to run a network/raid/spund/whatever card.

      --
      Live today, because you never know what tomorrow brings
    47. Re:Thanks by Stray7Xi · · Score: 1

      I'd say huge FAIL. An app should have no need to know about http to get an image from any program to an image editor. What would happen if you dragged it out of an email attachment? Would gimp use imap to retrieve it?

      Linux GUI usability is a huge FAIL compared to its commercial competitors.

      Funny because I just tested it and windows can't do it either. It's a silly thing to say one program should transfer the data to an unknown program in a magical way that the user wants.

      What if you were dragging that image to another browser, should it open as an image or a link. To a folder, would it be a bookmark or a file? What if you were dragging it to notepad, should it appear as a binary splegh of nonsense or a URL? What if you dragged that image to MyProgram.exe? No the side sending the data gets to determine the context.

      For firefox, a web browser, the only logical way is to interpret it in the URL context. For a email program it should be an image if it's an attachment. If its an html img tag it should be a URL.

    48. Re:Thanks by blue+trane · · Score: 1

      Bosses are often wrong though. Maybe this is the right thing. Graphs > hierarchies.

    49. Re:Thanks by eyrieowl · · Score: 2, Interesting

      no one said it had to pass the resized displayed image. as you noted, it downloads the original image. why would it not pass the original image to the other application? that is the behaviour I expect, and that I've seen. and it doesn't involve my image editor going out to the web to re-get what is already on my machine, in my browser cache if not actually in memory.

    50. Re:Thanks by Shimmer · · Score: 2, Insightful

      So you spend about half your waking hours doing stuff you don't care about? Let us know how that strategy works out for you after 10 or 20 wasted years.

      --
      The most rabid believers in American Exceptionalism are the exact same people whose policies are destroying it.
    51. Re:Thanks by XO · · Score: 0, Troll

      An added point here, is that pretty much through the whole 2.3 and 2.4 kernels, Alan might as well have been the head of kernel development. I haven't kept up with 2.6, but Linus has pretty much always been terrible, depending on everyone else in the community to fix the utter crap that he half-wits.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    52. Re:Thanks by Directrix1 · · Score: 1

      Don't confuse the FOSS world with Linus and his cohorts. Working with F/OSS is all about developer relationships. These are unique to each project, which is why this isn't like the world falling apart.

      --
      Occam's razor is the blind faith in the natural selection of least resistance and in universal oversimplification. -- EF
    53. Re:Thanks by Anonymous Coward · · Score: 0

      Hmm. The thing is that the JPEG might have addtional information - IPTC tags, EXIF information, ICM profiles, XMP tags - that The Gimp and similar tools can take advantage of and understand, but the web browser ignores. And it's not exactly unreasonable to type a URL into the File-Open dialog box and expect the image manipulation program to download and open that file.

    54. Re:Thanks by abigor · · Score: 2, Interesting

      This was on the bug-tracker, not the forums. I've never posted in the Gentoo forums.

      To be honest, I was being a bit unfair - I have the feeling a lot of the Gentoo devs are very young and quite atypical in the Linux world. A lot of the times they clearly didn't understand certain concepts.

    55. Re:Thanks by abigor · · Score: 1

      Can I also drop that jpg onto the desktop, and have it sit there as a file? Or onto a folder in a file manager? Or into a word processing document (say, Abiword) and have it automatically embed? It's not up to the individual app to handle these things. That's why it's a "desktop" and not a "window manager" - to handle drag and drop correctly, among many other things.

      In all fairness, you can do all of this if you select your apps carefully - KDE has it sorted, I believe. But it should be ubiquitous.

    56. Re:Thanks by Manfred+Maccx · · Score: 1

      On the other side, fighting back those stupid ideas during half your waking hours or quitting all the time may not be a good strategy either...can lead to 10 or 20 wasted years arguing...

    57. Re:Thanks by Anonymous Coward · · Score: 0

      PS - Remember Alan, there are places where your efforts are still appreciated and respected. Hail and Farewell!

    58. Re:Thanks by kriston · · Score: 3, Insightful

      He's only really talking about giving up maintainer of the TTY subsystem. Don't sweat it. He's not actually going away from working on the Linux kernel completely.

      --

      Kriston

    59. Re:Thanks by Anonymous Coward · · Score: 1, Interesting

      The ongoing conversation was civilized and concise

      Sorry, but that wasn't my impression. All bolding mine:

      Why are you making those outlandish claims? [...]
      Without making idiotic excuses [...]
      that's just bogus [...]
      What you describe is just crazy talk.

      Linus uses melodramatic emphasis and a condescending tone throughout the entire conversation.

      you have been CONTINUALLY arguing [...]
      And no, that was not a fluke. TODAY, you sent out an email saying that [...] would be "correct". [emphasis on the scare quotes]
      Despite me having told you that it _clearly_ is not correct [...]
      WHY? [...]
      Then we can revert [...] for pty's entirely. No? [...]
      The case you mention ALREADY HAPPENS [...]
      Yes. Consider exactly that. And notice how it happens [...]
      so that all seems fine already. No?

      I'm not in any way partial here, but I haven't suddenly been overcome by the urge to buy that man a beer.

    60. Re:Thanks by Anonymous Coward · · Score: 0

      Where does somebody go if they want to see this TTY code first hand?

      Inside your hard drive. You have to squint, though.

    61. Re:Thanks by dotgain · · Score: 2, Interesting
      You don't understand - it's not the role of the boss to say who's right and who's wrong in this case - it's to decide who's being unreasonable - he knows that all the expertise needed is possessed by the two individuals arguing, what they lack is mediation. This I learned primarily from Slashdot itself. There's many talented and knowledgeable people here (there's also a share of twits) and absolutely no mediation.

      What I've learned in this Cox/Torvalds case is

      • As well as seeming correct, Linus most assuredly is an asshole, because being correct ain't quite enough for him - he must call someone a douche as well. I never had to deal with him, and I'm now glad I never will.
      • That the F/OSS situation is more hopeless than I originally thought. It's not just a KDE vs. Gnome, OK/Cancel vs. Cancel/OK, Gentoo vs. Debian thing. These are two grown men that have worked together for years, among the most technically able F/OSS has to offer, working at the kernel level, and they couldn't work their shit out.
    62. Re:Thanks by phyrz · · Score: 1

      Ubuntu Jaunty using Firefox:

      Can I also drop that jpg onto the desktop, and have it sit there as a file?

      Yep

      Or onto a folder in a file manager?

      Yep

      Or into a word processing document (say, Abiword) and have it automatically embed?

      Openoffice would paste the HTML. But if you use the context menu in firefox to choose copy image then you can paste it directly into writer.

      --
      Don't point that gun at him, he's an unpaid intern!
    63. Re:Thanks by Anonymous Coward · · Score: 2, Insightful

      The reason why you call it *BSD is precisely because of politics.
      BSD vastly fragmented over personality conflicts, power struggles, etc.
      In large part that allowed linux to jump to a dominant position.

    64. Re:Thanks by general_re · · Score: 1

      On Windows, you just throw in the disk, click ok, and your hardware is working.

      Unless you're running Vista x64, have 4GB or more of memory, and are trying to install the drivers for a TV tuner. Doesn't matter which manufacturer, they all would tend to fuck up under such conditions. I gave up trying to get TV tuners to work on my rig after wasting close to $250 on various models cuz I found only one commonality amongst them: they don't fucking work.

      Apparently I am imagining that I am sitting in front of a Vista x64 box with 6GB of memory, and the HVR-1250 happily playing the Colbert Report in the background :/

      (I hate "works for me!" posts, actually, but your statement was so absolute that I couldn't help but post one data point to the contrary...)

      --
      ABSURDITY, n.: A statement or belief manifestly inconsistent with one's own opinion.
    65. Re:Thanks by blue+trane · · Score: 1

      Better for the individuals themselves to realize who is being unreasonable. Cox could have replied to Linus's questions with his reasons, he could have verbalized his emotions. The advantage of verbalizing one's emotions is that the explicit words can be analyzed for logical flaws.

      For example another post breaks down Linus's comments, highlighting the words with high emotional content that seem to be intended to provoke. Cox could make use of that poster's work to craft a reasonable, rational response to Linus.

      But it's best if Cox realizes that himself, not by having it imposed on him. Freedom is essential!

      (Posted as code because I couldn't get line breaks between paragraphs any other way!)

    66. Re:Thanks by Pyrion · · Score: 3, Informative

      Hauppauge still hasn't moved from their stance of being completely unwilling to write functional x64 drivers for the WinTV series of cards. They still insist the cards won't work with x64 systems with more than 4GB of memory. Until my Hauppauge card works without me having to gut myself of more than 80% of its memory, they can go die in a fire.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    67. Re:Thanks by smash · · Score: 1
      OS/X is written in Objective-C and hence it can just pass around handles to objects, that can be cloned, etc...

      eg, Browser has an image open to display, drag drop = new object in the other app, cloned from the image object in the source app...

      At least, thats my understanding of how it would work, I'm just starting out in Objective-C./cocoa...

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    68. Re:Thanks by smash · · Score: 1
      Same here.

      The best technical solution is chosen and there is way less "not invented here" attitude among the developers.

      For an example, see Dtrace... :D

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    69. Re:Thanks by Pyrion · · Score: 1

      "gut my system," that is. Needless to say, all the frustration and contempt towards Hauppauge that I had thought I had successfully buried has risen to the surface once again. So they support x64 with their "newer" cards? Fuck them. They'll get no points for that in my book. Every single card that they advertised as "supporting Windows Vista" should damn fucking well support Windows Vista.

      Though I appreciate the "works for me" post, I just wish it wasn't a fucking Hauppauge card. Or Avermedia, though their card actually worked, it just ran too fucking hot and died from poor placement (smack dab between two 8800GT's) five minutes after installation.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    70. Re:Thanks by dudpixel · · Score: 1

      On Windows, you just throw in the disk, click ok, and your hardware is working.

      hmmm yes, the disk. you mean the one for the network card? now where did i put that again? hmmm i hope i didn't throw that one out...

      might hafta just fire up my ubuntu machine and download the driver...heh that worked!

      --
      This seemed like a reasonable sig at the time.
    71. Re:Thanks by vcompiler · · Score: 1

      I am not sure how much the probability that FireFox change an image from a server. According to my experience it rarely change the original images. Does GIMP always download the image from the server? If so, either FireFox or GIMP is not very smart. In most cases, they should exchange the information of local copy of the images as long as the image is not changed.

    72. Re:Thanks by Meumeu · · Score: 1

      On Windows, you just throw in the disk, click ok, and your hardware is working.

      Unless you're running Vista x64, have 4GB or more of memory, and are trying to install the drivers for a TV tuner. Doesn't matter which manufacturer, they all would tend to fuck up under such conditions. I gave up trying to get TV tuners to work on my rig after wasting close to $250 on various models cuz I found only one commonality amongst them: they don't fucking work.

      FWIW, I've had no problem with this tuner under Windows 7 RC1 x64 and 6GB, although I didn't try using the driver from Asus, the one bundled with Windows just works.

    73. Re:Thanks by Anonymous Coward · · Score: 0

      So who does this Linus think he is anyway? From what I hear maybe he's the one who should get the hell out!

    74. Re:Thanks by someonehasmyname · · Score: 1

      Everyone left FreeBSD for Linux over the bell lawsuit.

      --
      Common sense is not so common.
    75. Re:Thanks by Pyrion · · Score: 2, Interesting

      Because Windows is so widely used, H/W manufactures have to make passable drivers in order to get their product sold.

      No they don't! They just have to advertise that it works, it doesn't actually have to work! This is exactly the sort of crap I went through with Hauppauge in my prior posts below. They can advertise functionality all they damn well please, and once you pay for it, bring it home and void most store return policies by unpacking the damn things, you find out that *gasp* the damn things don't work as advertised and, much later, you find out that they never will! Once they've got your money though, what do they care? You can complain all you want, but if they're not going to provide support, then they're not going to provide support, and short of a class-action lawsuit, you're screwed.

      Heck, chances are you wouldn't get your money back anyway even if you won a class-action suit.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    76. Re:Thanks by dotgain · · Score: 1

      While I don't disagree particularly with anything you've said, I think it's idealistic. They could have behaved in that manner, but at the end of the day they didn't and neither would a lot of people. I'm sure by now Cox realises that Linus was technically correct, but my point is this wouldn't have been allowed to happen if there was a 'boss'. I've seen stacks of this type of discussion (that between Alan and Linus) on all the OSS forums I've visited over the years, and to see this between Linus and the de-facto 2nd in charge is the icing on the cake for me - it's why I genuinely believe Linux+OSS is doomed, not because of no money, but no leadership - hell, a seeming resentment of it.

      PS: It seems you now need to enclose paragraphs with <p> </p> pairs rather than following each with the old-school <p> tag. Failing that, 'Plain text' format avoids the monospace font and lets you put line breaks in without HTML

    77. Re:Thanks by Pyrion · · Score: 1

      Then it mangles the image to fit - losing resolution and pixel depth along the way.

      No it doesn't. The resize is done in memory and the result is not committed to cache, so it's perfectly reasonable to assume that the local copy in cache would be, bit-for-bit, identical to the copy that the GIMP would get from the server.

      No, the reason why the GIMP would have to grab the image off the server itself is that all you're really "grabbing" from Firefox is a reference to a remote image, ergo, the image's URL, rather than the raw bits of the image itself. Also, it's much more efficient to copy-paste a string of text than it is to copy-paste a decoded sequence of raw bits, especially as it cannot be assumed that the target application will correctly interpret what it's being handed. The GIMP interprets the text string as a source to open from, and grabs the image from the remote server.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    78. Re:Thanks by Reziac · · Score: 1

      I tried it on this venerable Win98 box... an amusing croggle indeed: Tried to drag the Google logo from Seamonkey's browser window into Photopaint. Found myself with 25+ copies of the text "http://www.google.com/intl/en_ALL/images/logo.gif" but no image.

      It works from pretty much any other app, but not from a browser window. [scratching head]

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    79. Re:Thanks by im_thatoneguy · · Score: 3, Interesting

      You volunteer hundreds of hours of your time, without pay, and all you hear from the members is complaint-after-complaint-after-complaint.

      You eventually reach a point where you say, "What am I doing this for? No one's appreciating it or saying thanks. I could be out having fun instead of this shit," and then you stop volunteering.

      You just described why I mostly use commercial software. Because they take all my complaining with a smile and a nod and get to work.

    80. Re:Thanks by Anonymous Coward · · Score: 0

      How about this: FUCK LINUS TORVALDS.

      Seriously, how many people does this douschebag have to piss off before Linux separates itself from its creator.

    81. Re:Thanks by Pyrion · · Score: 1

      Mmhmm. Tried it with Firefox and the GIMP for Windows on the Google logo and get an error about being unable to open a bitmap file in my Temp directory as the file "doesn't exist." Works fine with Paint.NET (though it still treats the logo as a Windows Bitmap.)

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    82. Re:Thanks by lgw · · Score: 1, Flamebait

      Err, that seems incredibly tame for a conversation between two developers on a contentious topic. The way I'd speak to a volunteer (or a new college hire who's sprirt I didn't want to crush today).

      Here's an actual email snippet from a frustrated architect to a frustrated developer at my last job (with dozens of devs CCd) "and if you can't understand even this simple concept, you should give up programming as a career because you're not smart enough to do it". And that wasn't even crunch time. Crunch time produces actual shouting matches (no sleep for a week sort of surpresses appropriate social responses). But then, we're paid to put up with one another.

      People who are passionate about their work have impassioned coversations about technical issues, and when the other guy seems to simply be ignoring you, you escalate your tone.

      Of course, this is Linus. My favorite Linus quote "if you're still using CVS, you're stupid .. and also ugly."

      --
      Socialism: a lie told by totalitarians and believed by fools.
    83. Re:Thanks by Yfrwlf · · Score: 1

      Open source drivers do have the potential to be higher quality than closed source. Utilizing communities to aid in fixing and writing drivers will always be an added benefit. However, this does not require force.

      One of the choices most everyone has, for instance, is between Opera, Firefox, and Chrome for your browser. While the existence of Opera may pull some users away from the two which are open source, thus slightly slowing their development and progress (which is your point, and I agree that that is a legitimate real-world factor), the attractiveness of open source and the freedom and power that it gives communities will still always be a feature and users will always find that attractive. If someone wants to buy a piece of hardware that only comes with closed source drivers, that's their choice. Linux should mean freedom in every way. Everyone should always be cautious of systems which remove freedom. For instance now with several businesses latching onto Linux, you have to make sure that the ways they intend to profit off Linux are in your best interest as well.

      I also think that ultimately the world would be better with no copyright or patent laws. ^^ Would probably be like Star Trek by now. :P

      --
      Promote true freedom - support standards and interoperability.
    84. Re:Thanks by Plunky · · Score: 1

      That's not Linux, that's KDE or Gnome you are talking about.

      Pedantry like this, which willfully ignores the issue at hand, is a kind of passive-aggressiveness which is an example of the attitude problem the parent was referring to.

      Going back to the car analogy, Linux is the people who made the car engine and you are blaming them for the queue at the traffic lights? Dude, talk to the city management if you have a good idea to synchronise the traffic lights around the city..

    85. Re:Thanks by Pyrion · · Score: 1

      Or you turn it into a means of extracting amusement from those that are giving you grief. Grief them in return. Though even that gets old after a while.

      Still though, I think everyone placed into such a situation should at least attempt to salvage something from it (even/especially at the expense of others) instead of just dropping everything to say "screw it."

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    86. Re:Thanks by Reziac · · Score: 1

      Something here must be app-specific rather than OS-specific. Witness:

      Tried dragging the Google logo from Netscape3 to Photopaint -- nothing. Nada. Ignored me entirely.

      From Seamonkey to M$Paint -- a variety of not-found and access-denied errors, mostly involving "F:\Win98\Desktop\F not found" (which doesn't exist) and "F:\Win98\Desktop\: not found" (yes, with a trailing colon). "Access to F:\ was denied." And so on. Appeared to be trying to stuff the paste buffer with chunks of the various locations involved.

      However -- dragging the Google logo from IE5.0 (on google.com) to Photopaint worked perfectly.

      And it tried to work with IE to M$Paint, but this is an old version of Paint that doesn't know GIFs, so it whined about an invalid bitmap. But it got the cache location right.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    87. Re:Thanks by DamnStupidElf · · Score: 1

      There is a difference between the kernel and the userspace apps. If Apple had a lot of time on their hands, they could get OS X running on a Linux kernel with great drag and drop support. Specifically, the kernel is one development team with one leader and the userspace apps that run on X (which provides a perfectly fine clipboard) are all made by independent teams with no real incentive to support perfect drag and drop.

      It's kind of like wishing you could drag and drop things from a Mac to a Windows PC.

    88. Re:Thanks by xtracto · · Score: 1

      You eventually reach a point where you say, "What am I doing this for? No one's appreciating it or saying thanks. I could be out having fun instead of this shit," and then you stop volunteering.

      The moment you stop having fun while doing a hobby it stops being a hobby and starts being a chore.

      Different people can handle different amounts of pressure until they find dissatisfying what they once thought was cool.

      Of course, the "connected with users" nature of open source software means that, people that are using your software get to believe that you are working for them and, some of those users get *really* annoying.

      From the team-developers side, if doing a hobby means you've got to swallow orders and insults from guys that thing they are better than you (at what YOU do, they certainly are better at other stuff) then, sooner or later it will stop being funny.

      The first poster quote says a lot:

      Thanks for all the hard work. Good luck to the next maintainer. Not much else to say./quote

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    89. Re:Thanks by xtracto · · Score: 2, Interesting

      You just described why I mostly use commercial software. Because they take all my complaining with a smile and a nod and get to work.

      Nah, they take the complaining with a smile, nod and go back to their "dev center" to laugh out loud about the whining guy who will pay another $100 for the next improved, more synergic version.

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    90. Re:Thanks by h4rm0ny · · Score: 1


      That sounds familiar. I've been in cases where I've volunteered perhaps nearly a hundred hours over a period of time, and then people turn round, criticize and demand more. It seems for some people, that if you do nothing at all, then nothing is expected, but if you do something, then everything is expected. You see it again and again, especially with public figures who get torn down for not doing enough by people who've done nothing. Some folks are just selfish, I reckon. Now I don't know enough about this issue to say who is right and who is wrong in what they were actually arguing about. But reading those emails, Cox certainly maintains a reasonable tone and I know that he has contributed a great deal over the years. So I think the earlier post has the right of it. All we can do is express many thanks for all his freely given time over the years and wish luck to the new maintainer. If Alan Cox is reading this (and who wouldn't read a Slashdot story about themselves), then good luck mate. Don't get choked up by this. You've done a lot, it's known you've done a lot, and your freed up energy will undoubtedly end up channelled into something else worthwhile whether professional or personal. So sit back, take a breather, and wait for perspective to re-settle.

      Cheers,
      H.

      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    91. Re:Thanks by Pyrion · · Score: 2, Insightful

      Why would it be any different in practicality? Complaining to a commercial entity ultimately means you're complaining to someone who is paid to field your complaint. The "smile and a nod" is what you get before they hang up and move on to fielding the next complaint, whereas nothing of consequence gets done. Not unless a lot of complaints roll in. With commercial entities, it's not about the seriousness of the issue, it's all about how many people complain in a given span of time, so if you're one of their few complainers, they'll write you off as a statistic and continue doing whatever it is they're doing (wrong) despite your better judgment.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    92. Re:Thanks by Pyrion · · Score: 1

      Yeah, I think with Firefox, since it doesn't preserve the filename of the image when it stores it in the cache, it has to convert it into a temporary bitmap and point the copy-paste to that temporary bitmap, under two assumptions. 1, that the other application wouldn't be able to tell what kind of file it's opening if it doesn't have the appropriate file extension, and 2, that if the other application is designed to process images, it should at very least be capable of processing a Windows Bitmap.

      With IE, it preserves everything in its cache such that you're just doing a normal file open through drag-dropping.

      But yeah, it's app-specific. Has to be, since drag-dropping doesn't involve the system clipboard like copy-pasting does.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    93. Re:Thanks by Pyrion · · Score: 1

      And I apologize in advance, I tend to get drag-dropping and copy-pasting mixed up.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    94. Re:Thanks by ShakaUVM · · Score: 1

      I can understand his frustration. I've walked-away as well from various clubs. You volunteer hundreds of hours of your time, without pay, and all you hear from the members is complaint-after-complaint-after-complaint.

      Yep. Happens in every sort of social network (real life social networks as well as virtual). People have an amazing ability to be ungrateful. I've organized roleplaying conventions with 100 tables going off smoothly, and people bitch. I've spend hundreds of hours working on open source code, and people bitch. Etc., etc.

      To be fair, some complaints are valid, so I carefully listen to everything people say. Sometimes they're right (and I'll admit it) and sometimes they're idiots (which I also point out). My skin is tough enough to deal with most of it, except the roleplaying convention stuff -- took way too many hours out of my life for the abuse. Plus I got tired of calling on my 10 closest friends over and over to volunteer because everyone else was too lazy to step up to the fucking plate.

    95. Re:Thanks by Threni · · Score: 1

      He's working for the money, so it would only be wasted time if it were time spent not making money.

    96. Re:Thanks by ls671 · · Score: 1

      Hey ! I though about posting on this with the same spirit that you used when I saw this coming up.

      For some reason I did not do it. Now I know why ! ;-)

      You have expressed it better than I would have. Thanks to you and thanks to Alan, the guy has been contributing for a while...

      --
      Everything I write is lies, read between the lines.
    97. Re:Thanks by smash · · Score: 2, Insightful

      Everyone left FreeBSD for Linux over the bell lawsuit.

      For values of everyone that exclude apple and many of the top machines in the netcraft uptime surveys...

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    98. Re:Thanks by hairyfeet · · Score: 1

      Did it come with XP X64 drivers? The only reason I boot into XP32 anymore is because my 8 year old cap card only works in xp32.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    99. Re:Thanks by Elshar · · Score: 1

      I've actually had this happen to me with two different computers and two different drivers. On one, the drivers for an ATI card I was using no longer worked after upgrading my ubuntu dist from 8.x to 9.04. On the other, my wireless card suddenly became flakey after a kernel upgrade and no amount of recompiling anything helped. (Well, getting the newest code from the madwifi svn helped some, but it was still pretty much unusable for anything other than email/light surfing).

      I see there's people saying windows' drivers are horrible, and compared to linux's drivers, windows' drivers are fantastically inescapably awesome in this regard. I don't remember the last time a service pack had rendered some random bit of hardware nearly unusable or kept my computer from properly booting.

    100. Re:Thanks by yoyhed · · Score: 1

      Works for me on XP between Firefox 3.5 and Photoshop CS4, although in Photoshop it came through as 3j3h1akp.bmp, when on Google's site it was originally logo.gif - Firefox in this case does not pass a URL, but rather creates a temporary bitmap (not sure if that's already how it was stored in cache, or if it created that copy for the drag-n-drop).

      --
      WHO NEEDS SHIFT WHEN YOU HAVE CAPSLOCK/ DAMN1
    101. Re:Thanks by Anonymous Coward · · Score: 0

      Thanks for your post. I thought I was the only person who believes that some Gentoo maintainers behave like total a$$e$. Last time I had a desktop downtime of ~2days because of a broken package. I pinpointed the bug and provided an ebuild patch which was refused by the maintainers because of some ill-conceived policy they have. Their policy essentially translated to: "We decided not to support your configuration therefore we won't accept this patch even if it fixes an issue and is safe for the rest of the world. Screw you and all the others who don't have the specific configuration we like to support."

      Such behaviours have pushed me on the verge of abandoning Gentoo after ~8 years. When you have work to complete using your Linux desktop you can't afford a 2 days downtime because some maintainer-wannabe decided that your "exotic" configuration is not supported for the specific package he maintains.

    102. Re:Thanks by tenco · · Score: 1

      It doesn't. But most people are forced to do stuff they don't care about. It's called work, you insensitive clod!

    103. Re:Thanks by Hal_Porter · · Score: 1

      With commercial entities, it's not about the seriousness of the issue, it's all about how many people complain in a given span of time, so if you're one of their few complainers, they'll write you off as a statistic and continue doing whatever it is they're doing (wrong) despite your better judgment.

      I'm not sure this behaviour is irrational. Basically commercial companies tend to either fix the bugs everyone is complaining about or go bust. Of course there are lots of commercial companies that have picked the second option and just don't know it yet - they don't know how to pick the patterns out of customer complaints and prioritize their development, or the developers are totally out of control and working on the next version but one and ignoring bugs in what is shipping.

      Still there are commercial companies out there that can ship code that most people will never have a problem with. Just not very many. The others are dieing slowly or have been born so recently it is not clear if they will learn enough to survive. Then again when people buy commerical software they do it based on reviews and word of mouth. These tend to help them mostly buy from the companies that work.

      Capitalism and commercial pressures are not a panacea though - lots of companies burn through their startup capital without ever producing anything that is usable by anyone other than their developers.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    104. Re:Thanks by Anonymous Coward · · Score: 0

      I can't name a browser which doesn't save the fetched original image to it's cache. So it could hand over that, or the path to the cached image file.

    105. Re:Thanks by evilandi · · Score: 2, Insightful

      After 10 years, it is paying for my, my wife's and my daughter's entire lives, and will shortly pay for my newborn twins entire lives too.

      I spend half my waking hours doing stuff I don't care about, and most of the rest of my waking hours doing stuff I care about but don't necessarily enjoy; changing nappies/diapers, trying to persuade a 3-year-old to go to bed, reading the same damned favourite fairy tale over and over again, pretending that I enjoy playing "Doctors" and being poked with plastic implements, unblocking the septic tank after my daughter emptied a whole bottle of anti-bacterial cleaner down it.

      But then for a few hours a week I have moments which I enjoy more than anything else I could imagine. Taking my family to the safari park, that was amazing watching my daughter interact with a giraffe. A birthday party. Making sandcastles on the beach. A long boat trip. Playing with my daughter in the swimming pool.

      Grow up. Not everyone wants to be a loner with no responsibilities for their entire life. Being the breadwinner for your family of dependants is the role of the vast majority of adult males in the world. Just because you and your small community of like-minded folk choose to do otherwise won't change that majority.

      --
      Andrew Oakley - www.aoakley.com
    106. Re:Thanks by hab136 · · Score: 2, Interesting

      So you spend about half your waking hours doing stuff you don't care about? Let us know how that strategy works out for you after 10 or 20 wasted years.

      I'm on year 11. The previous 5 years were spent working really hard, and caring about how projects at work went. When projects at work succeeded, I was ecstatic. When they failed or were cut due to outside business demands, I was mad and hurt. Then I poured my heart and soul into a project for 3 months, only to have it canceled on the day it was being rolled out. It turned out later this was a good decision, but at the time I was upset because all I could see was that they had killed my pet project. So I stopped trying to achieve satisfaction and status in life from work, and instead started treating work for what it is - a means to an end. My self-worth comes from things I do outside of paycheck hours, and I've been much, much happier.

      I still try to do my best; I just don't get emotionally invested. Think of taking out the garbage or washing dishes. You need to do these things, and it's good to do them well, but you don't need to *care* about these things. You also don't have to hate them. Is it fun and exciting? No, but it's also not bad. It's just kind of there.

      What's funny is that when you become emotionally detached from your work, it's easier to make decisions that would have otherwise been painful. Compromising on or sacrificing your "baby" (project) for the good of the company? No problem. Doing something that is technically atrocious but makes sense for the business? No problem. You start to think about ways to do what the business wants instead of what would bring you personally the most satisfaction - which ironically makes you a better employee. Way too many people get caught up in doing what they think is the right thing technically, regardless of what the business needs or wants. There's always the argument of what the business wants right now and what it needs long term, and you can still argue that - in fact it's your job to examine requirements and try and do what's best for the business both in the short and long term - but you don't have to be emotionally invested in the outcome.

      Now for the math!

      Let's assume the standard "Eight hours for work, eight hours for sleep, eight hours for what we will", so 40 hours a week of work. Not 60, because after all, we're talking about someone who doesn't care about work.

      There are about 260 weekdays in a year. Subtract 12 for holidays, 25 for vacation, and you're down to 223.
      There are 365*24 = 8760 hours in a year.
      Sleep: 365*8 = 2920 hours (33% of total)
      Waking hours = 8760-2920 = 5840
      Work: 223*8 = 1784 hours (20% of total, 30% of waking)
      Free time: 8760-2920-1784 = 4056 hours (46% of total, 70% of waking)

      You spend more time sleeping than you do working! Even if you had no holidays or vacation, work would still only be 23% of your time and 35% of your waking.

      If you sleep 7 hours a night like me:
      Sleep: 365*7 = 2555 hours (29% of total)
      Waking hours = 8760-2920 = 6205
      Work: 223*8 = 1784 hours (20% of total, 29% of waking)
      Free time: 8760-2920-1784 = 4056 hours (50% of total, 71% of waking)

      So for 29% of my waking hours, I'm doing something that I neither love nor hate - and my happiness during the other 71% of my waking hours depends on what happens during those "me" hours, not on what happens in my workplace.

      P.S. I wrote all of this at work. Even spreadsheets can be fun when you're using them to calculate silly things like waking hours.

    107. Re:Thanks by squiggleslash · · Score: 1

      If you'd said you'd switched to a specific BSD, then I could probably understand you, but *BSD? Really?

      Politics in *BSD is so bad there are at least four different kernels, two (NetBSD, DragonFlyBSD) the results of massive disagreements about the direction BSD was heading in, and one (OpenBSD) the result of infighting and massive egos.

      I don't think Linux or GNU are really all that bad for open source projects. The only advantage, say, FreeBSD has, is that the wars have been sufficiently bad many of the hotter heads have left already.

      --
      You are not alone. This is not normal. None of this is normal.
    108. Re:Thanks by noname444 · · Score: 1

      For the record, it works in Jaunty ;)

    109. Re:Thanks by Antique+Geekmeister · · Score: 1

      No, he's not. He wants to see Alan's git repository, or a recent upload of it, with the last set of patches on it. That's not necessarily in the public repositories at www.kernel.org, although I'll bet there's a published location for it. I've not needed to play with pre-release code for years now, but things have changed, and the switch to git for source control for code management means it may not have been committed to what is the public master repository, or it may be in a git branch, which can be a bit trickier to find and review.

      I'm really impressed with git, by the way. After CVS, subversion's improvements but still flawed attempt to fix CVS, and working with Perfore and Bitkeeper and other source control systems with corporate partners, I'm happy to use git. But it does have a learning curve.

      With that all said, I'm afraid that Linus was right on this: this commit should be rolled back until it can be fixed with the various userland cases, because chasing it down is taking so long and so much time with the flaw incompletely addressed. It's a problem with big projects: reasonable ideas get blocked until weird, client-land border cases can get addressed, and the result slows progress a lot on both performance and security issues.

    110. Re:Thanks by KangKong · · Score: 1

      Yes, I switched to OpenBSD and FreeBSD for different machines. Since then I've moved away from OpenBSD and have used FreeBSD on all machines, mainly because of OpenBSD development not being that active, lacking some features I wanted and FreeBSD getting some features from OpenBSD that I wanted.

      FreeBSD and NetBSD were basically started at the same time in parallel as forks off of 386BSD, not as one forking off of the other.
      OpenBSD split from NetBSD and DragonflyBSD split from FreeBSD because of two people Theo and Matthew Dillon.

      Obviously you can't completely avoid hot heads anywhere in life, but atleast life is much better for me on the BSD-side.
      Perhaps life was different in BSD 10 years ago, I don't know, maybe the developers have matured and/or the hot heads left. I couldn't care less. I care about the current state, and the FreeBSD community is a LOT less elitist and friendly than my experience with the linux one. Perhaps all the hot heads start developing on linux now a days.

    111. Re:Thanks by ciggieposeur · · Score: 1

      So you spend about half your waking hours doing stuff you don't care about? Let us know how that strategy works out for you after 10 or 20 wasted years.

      If the GP doesn't, millions more people will. They'll have managed to survive that entire time in relative comfort: house, cars, sending kids off to college. And they'll contrast that with the life of pursuing their real passions: perpetual unemployment, living off friends' and relatives' couches, inability to financially support children.

      There are only so many decently paying gigs for musicians, painters, sculptors, poets, computer game players, sports players, etc. Most of the stuff people "care about" pays squat. So those of us living in the Real World figure out how to tolerate or even marginally care about things like accounting, finance, management, sales, logistics, and even customer support in order to fund those 30-40 hours a week of actual living time. Sadly, even the stuff you DO "care about" -- such as computer programming -- might become blah after 10-20 years being paid to do it.

    112. Re:Thanks by julesh · · Score: 1

      I remember a sort of userland breaking point: I tried to drag and drop a jpg in a browser window (Firefox) to some photo editor. It didn't work. Macs and Windows have been able to do this since at least the mid-90s.

      I just tried dragging from Firefox to Photoshop 5 (released 1998) on Windows XP and it didn't work. It accepts drags of files, but not images from a browser window. And the OS is irrelevant to this, anyway: all the relevant OSs provide a datatype-independent method of dragging and dropping from one application to another. If two applications don't support the same datatypes (and it seems Firefox [which provides only URLs, I believe] and Photoshop [which seems to accept only files] don't) then they can't communicate.

    113. Re:Thanks by sa666_666 · · Score: 1

      You know, you were doing fine up until that last paragraph. Before that, I completely understood your attitude. I don't share your goals, but I respect that it's a valid life choice, and accept that many other people have the same goals. But then you have to launch into personal attacks against those who choose not to live that way.

      Why do some people have to put down how others choose to live their life? Is it not enough that they themselves are happy? No, not only do you have to be happy, but you have to make sure everyone else who doesn't share your outlook is considered abnormal. Let's turn this around. Perhaps you should be considered a sheep since you're doing what so many other 'adult males in the world' do. Perhaps you don't have the courage to break away from what society expects of you. I suspect that by putting down people on the other side of the fence, you subconsciously wish that you could be like them.

    114. Re:Thanks by Antique+Geekmeister · · Score: 1

      _Which_ BSD? OpenBSD has Theo at its helm. If you think Linux gets cranky, oh dear, you've got some fun experience ahead of you.

    115. Re:Thanks by Anonymous Coward · · Score: 1, Interesting

      Just tried it, GIMP connected to the server and pulled the image from there. Not sure if that's how you want it to work though.

      I'm wondering if someone does this with an image from a more...adult.....website.....

      will GIMP order some hookers ?

    116. Re:Thanks by Anonymous Coward · · Score: 0

      You know, you were doing fine until, well really not at all. Read 'Shimmer's comment again: IT WAS THE JUDGMENTAL WISE-ASS COMMENT! The GP is just responding to somebody else who first declared that the standard working life is invalid. You're aiming your invective at the wrong target.

    117. Re:Thanks by Ginger+Unicorn · · Score: 1

      I think the point was that the guy had sunk to the GP's level and thus undermined his response which up to that point had avoided pettiness.

      --
      (1.21 gigawatts) / (88 miles per hour) = 30 757 874 newtons
    118. Re:Thanks by Spacelem · · Score: 1

      Yes, it does default to digital, but it is a trivial change to switch to analogue, and it's a sensible default for people who are new to GNU/Linux and have a digital out on their card. Having said that, it's the change I always forget when I install a new distribution.

      Much worse than that is the new reliance on PulseAudio that distributions like Ubuntu seem to have. PA always seems to set the number of speakers to 2, and requires editing a config file to set it to 4.1 (my own setup), which I would certainly not expect a new user to know about (not to mention the latency it produces and the CPU time it hogs). PA is always the first thing I remove if it's installed with the distro. However, for some people, PA offers more options and features than they'd get under Windows, so there are a few upsides.

    119. Re:Thanks by TheRaven64 · · Score: 1

      You seem to be confusing several issues. Linux does have a stable ABI for userspace programs. Any Linux program from any previous release of Linux will work on a modern Linux kernel. None of the system call number have been replaced, none of the arguments have changed and the old calling conventions are still supported. GNU, however, does not have a stable ABI. GNU libc and GNU libstdc++, for example, have changed their ABI several times and applications that link against these need to either include an old version or be recompiled against the new one.

      X11 has not just a stable ABI, but a stable network ABI. The X11 protocol, which is used for clients (applications) to communicate with the X server is backwards compatible right back to the original version. You can not only run X applications from the first version of Linux on a modern X server, you can display applications written for - and running on - operating systems that pre-date Linux on a modern X server.

      The Linux kernel ABI is not stable, but this is purely a Linux issue, not an issue related to distributions. If you are writing a driver, you have to make sure that it is using the ABI (and API, which is also not stable) from the version of the kernel that you want to target, but you don't have to (as you state) test it with different kernel and distribution combinations, because a drive doesn't interact with anything other than the kernel.

      I am not a huge fan of the Linux policy with respect to kernel API/ABIs. Their reasoning is that it encourages people to get their code into the main kernel tree (at which point it becomes the responsibility of whoever changes the API to make sure it is updated correctly), but this is not always possible. Anyone writing a kernel module for an in-house bit of hardware, for example, won't want to submit it to the main kernel because the code is of no use to anyone else.

      --
      I am TheRaven on Soylent News
    120. Re:Thanks by TheRaven64 · · Score: 1

      I switched for *BSD at around the same time (maybe a couple of years earlier), but for different reasons. One was the documentation. I still hate developing on GNU/Linux, because the man pages say the headers you need to include for the various functions but don't list the magic macros you need to define actually make them work. Porting code from FreeBSD to Linux is always a painful process of defining the various standards macros to say 'yes, really, I do want to be using standard UNIX functions'. The other was working sound. Being able to output sound from several applications concurrently, without any of them needing to do anything more clever than open /dev/dsp and write sound data there, was something that FreeBSD had working back around 2001. From all of the discussions I hear about PortAudio, it seems like Linux still has problems with this.

      I'm sure Linux must have a compelling feature or two, but I've yet to find it.

      --
      I am TheRaven on Soylent News
    121. Re:Thanks by TheRaven64 · · Score: 1

      You realise, I hope, that Alan isn't doing this as a volunteer, he's employed by Intel to work on the Linux kernel.

      --
      I am TheRaven on Soylent News
    122. Re:Thanks by Chirs · · Score: 1

      "Sorry, but that wasn't my impression."

      If you'd ever read a really good flaming on the kernel mailing list, you'd know that this was a pretty straightforward discussion.

      Generally speaking, when Linus gets annoyed at someone for not thinking clearly, Linus is correct. Alan may have been correct about the locking issues, but Linus is certainly correct that emacs is doing nothing wrong.

    123. Re:Thanks by BobMcD · · Score: 1

      Or you slap together a Myth box out of junk parts and put the card in there. You could even do this WHILE wishing they would die in a fire. More efficient.

    124. Re:Thanks by Anonymous Coward · · Score: 0

      Well, I just tried it for you on Kubuntu 9.04 (dragged an image in a slashdot article and dropped it onto gimp), and it does work :-)

    125. Re:Thanks by commodore64_love · · Score: 4, Insightful

      >>>You just described why I mostly use commercial software. Because they take all my complaining with a smile and a nod and get to work.

      Yeah well it's easy to smile when you're getting paid $2000 a week (or more with overtime). When you're not being paid as a volunteer for Linux or officer of a club, you start to wonder if there are better things you could be with your $0.00/hour payment. The answer is usually "yes" like laying on a beach, or watching TV, or partying with friends.

      Heck even working at Walmart for $8/hour would be an improvement than listening to all the bitching club members/users. At least Walmart pays.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    126. Re:Thanks by commodore64_love · · Score: 1

      If he's employed by Intel to work on Linux, then how come his boss let him just walk-away from doing his job? Sounds like grounds for termination (firing) to me. You get paid to do a job; you keep doing it as long as they keep paying you, even if you don't like it. You can't just "quit" and sit-around doing nothing.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    127. Re:Thanks by ukyoCE · · Score: 3, Insightful

      It doesn't matter how smart you think you are, whether it's crunch time, or anything else -- if you're that rude at a real job, you should be fired.

      Assholes like that give programmers a bad name. They're are also the reason that many companies have gotten in the habit of "hiding" their developers from the rest of the company and users.

    128. Re:Thanks by commodore64_love · · Score: 1

      >>>wouldn't the answer be to download the TTY source code?

      Yes that would be the answer. But that doesn't answer the question "where". I guess I'll go google for it and hope I stumble on the correct website.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    129. Re:Thanks by commodore64_love · · Score: 1

      >>>stuff you don't care about? Let us know how that strategy works out for you after 10 or 20 wasted years.

      Well let's see. I already have 0.3 million, and in another 20 years that will rise to 3 million dollars in my bank account. I'll be able to retire at age forty or forty-five, and then just work part-time on whatever technical jobs I enjoy. Ya know, like Benjamin Franklin did back in the 1700s.

      As I said my job is just a means to an end - that being money and a big bank account.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    130. Re:Thanks by KangKong · · Score: 1

      Agreed, the BSD man pages were miles ahead of the GNU ones, atleast at that time. The GNU man pages basically a little bit of description, followed by something along the lines of "These man pages are not maintained, please see the GNU info pages for more information". OpenBSDs man pages were really good with a lot of coding examples, it seemed about half of the commits to the repo was to the man pages. FreeBSD is a little bit behind on the number of examples, but are otherwise really good.

    131. Re:Thanks by marcosdumay · · Score: 1

      You know, I'm working on in-house software, and I do that. You only have a limited amount of resources, if you don't note the complaints as statistics and work on the most important problems, you'll get a POS out of the depelopment process.

      Now, FOSS has another degree of freedom here. If a problem is very important for a single complainer, he can fix it himself. Otherwise, FOSS projects are probably doing exactly the same thing, taking notes of the problems and fixing the worst ones.

    132. Re:Thanks by TheRaven64 · · Score: 1

      Because he didn't quit kernel development, he just stopped maintaining the TTY stack. My guess is that other things he's working on are a lot closer to Intel's core business, so his boss is probably quite happy about his decision to focus on them instead.

      --
      I am TheRaven on Soylent News
    133. Re:Thanks by zorg50 · · Score: 1

      You can't return hardware to the store after you've opened it? I returned a video card to Newegg and a power supply to Best Buy that had no problems whatsoever; I had bought them to try to diagnose the problems I've been having with my machine, and didn't intend on keeping them. Both companies were perfectly happy to take opened and used hardware back for a full refund.

    134. Re:Thanks by Shakrai · · Score: 2, Insightful

      With commercial entities, it's not about the seriousness of the issue, it's all about how many people complain in a given span of time, so if you're one of their few complainers, they'll write you off as a statistic and continue doing whatever it is they're doing (wrong) despite your better judgment.

      Umm, that really depends on how much money you've paid for the software/support agreement, doesn't it? When I worked in the insurance business I had a direct line of communication to the programmers who wrote our agency management software. When I found bugs I could report them directly to the people who could fix them and would usually have a patch by the end of business. I had similar experiences working with Cisco back when I worked in the ISP business, although you did have to navigate more bureaucracy with them to get the desired result.

      Mind you, we paid tens of thousands of dollars for that software and those support contracts. You won't get that kind of response out of Microsoft when you find a bug in the copy of Office that you paid $120 for. But I still think it's disingenuous to claim that commercial entities don't care about the seriousness of the issue.

      --
      I want peace on earth and goodwill toward man.
      We are the United States Government! We don't do that sort of thing.
    135. Re:Thanks by abigor · · Score: 1

      Nice, things have certainly improved. What if you tried to drop it into a KDE app (given that you're running a Gnome desktop and all)? Or Abiword? If any of them fail where they should work, then it's still broken.

    136. Re:Thanks by Anonymous Coward · · Score: 0

      That's because the Gentoo devs are more interested in bashing top posters on their mailing list, than doing productive tasks like upgrading Portage to the current version of Python.

    137. Re:Thanks by jcr · · Score: 1

      OS/X is written in Objective-C and hence it can just pass around handles to objects, that can be cloned, etc...

      That's a bit of an exaggeration. OS X uses Objective-C in many of its frameworks. Those apps that use Cocoa or Carbon can exchange data via the system pasteboard, which is used for drag and drop. Data on the pasteboard isn't necessarily an Objective-C object.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    138. Re:Thanks by Reziac · · Score: 1

      I wonder if this is a related peculiarity:

      I use Spacejock's yBook as an eBook reader. Its "Load file" function stalls on very long filenames, and on longer paths that have a lot of spaces and whatnot in them. However, I can drag and drop the same file into yBook without a problem. (Well, most of the time. I've hit one that I had to move to a shorter path, otherwise drag-and-drop stalled too.)

      I'm not sure this isn't a Windows bug that yBook happens to tickle -- I vaguely recall having a file-open-dialog and long-path issue somewhere else, tho don't recall what the apps involved were. (BTW this is not the DOS effectively-62 character path limit.)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    139. Re:Thanks by Killotron · · Score: 1

      Having worked in sales for a small software company, i can speak first hand as to the volume of complaints and requests that come in from customers. Talk to any customer for more than 10 minutes and you have a dozen feature requests and complaints, half of which are unique to that customer. In open source, the response "do it yourself" is quite suitable to deal with oddball concerns, but obviously that can't work in a closed source environment. The problem isn't that companies ignore customers. It's that so many requests come in, it's just plain impossible to satisfy the great majority of them. To appease the greater number possible, companies simply must address the most common concerns first, and only address smaller ones when it fits into their development plans and future goals. I remember meetings where sales and tech support would sit down with the dev team and we'd prioritize every existing request, bug, and fix. From lists hundreds of items long, we'd end up with 10 or 20 things above the line, and everything else would be ignored by necessity.

    140. Re:Thanks by Yunzil · · Score: 1

      Creative's SB Live drivers do not work at all in Vista.

      Um, yes they do. I have an old SB Live card at home and the drivers work fine with Vista Ultimate 64.

    141. Re:Thanks by Xtravar · · Score: 1

      You need to strike a balance. Getting burned out because you're too passionate and constantly fighting the man is not the best strategy, either.

      --
      Buckle your ROFL belt, we're in for some LOLs.
    142. Re:Thanks by psm321 · · Score: 1

      Really? I've had Windows driver updates break network card drivers multiple times. And unlike Linux where I can just go back to the previous version, these Windows updates are usually "permanent system updates" that can't be reverted.

    143. Re:Thanks by deadkennedy · · Score: 1

      One of the few downsides to open source software.

    144. Re:Thanks by Pyrion · · Score: 1

      Not if you destroy the packaging it came with in order to open the damn thing, or if you lose the other materials it came with. It's also not all that cost-effective if you have to pay a shipping company to get the card only to pay for shipping again to return it.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    145. Re:Thanks by Pyrion · · Score: 1

      Yeah, good idea, waste more time and money to get something that is advertised to work on my system to work on something I neither understand nor want.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
    146. Re:Thanks by BobMcD · · Score: 1

      Don't be pedantic. I agree with you, it should work.

      That fact alone, however, doesn't have to be a waste of money. You could choose to put the card to use.

      Yes, it would compromise your attitude, but the outcome would be getting something you presumably do want - value for the dollars you spent in the way of a card capturing video frames.

      In the end those are the two factors you're deciding between: the value of those dollars and the value of being pissed off at the vendor.

      Presumably, you've weighted the latter higher than the former. This is your right, but it isn't your only option.

    147. Re:Thanks by Seumas · · Score: 2, Insightful

      I tend to respect and admire Linus, but his attitude reminds me too much of dealing with all the prima-donas I have to deal with on a regular basis. An entire project may hinge on you. You may be the most prolific, genius, brilliant, fantastic, productive person on the entire project or in an entire company. That does NOT excuse your behavior.

      Don't get me wrong, I'm all for people who are succinct and simply don't have time for bullshit. That's not what we're talking about here, though. But rather than the dickhead responses a lot of coders have (not just toward people outside of coding, or their own project, but even directly to those that participate on a one-to-one basis with them), they could have a little tact. It doesn't take any additional energy or effort to accomplish and it keeps people from avoiding working with you. I would rather work alongside someone with 98% of your skill who has a better attitude.

      For example, in this response on the same thread to someone who admits they are not terribly familiar with the internals of TTY but is clearly trying to contribute however they can, Linus responds as follows:

      On Tue, 28 Jul 2009, OGAWA Hirofumi wrote:

      > If I read that part of emacs correctly, it seems to be assuming the data
      > was already sent to master side if the child process was exited.

      That sounds like a rather obvious assumption.

      (...)

      So at what point do we just admit that the commit that caused all this was
      a buggy pile of sh*t and just revert it?

      Is it really too much to ask for someone like Linus to respond with something like "I agree" rather than insulting the guy for making what appeared to the almighty godly genius as "obvious"? What is to be gained by making someone else feel like a tool? All you've done is given them reason to pause next time they try to contribute and change their mind during that pause. They'll decide "why should I bother trying to help in anyway when even my best effort is going to be dismissed and possibly with a snide insult?". And then people like this complain that "not enough people contribute to this open source project". Of course not, because you aren't receptive to them and make them feel unwelcome! You don't have to coddle them at all, but for fuck's sake at least try to be decent.

      Otherwise, you'll eventually not just keep new blood from trying to help out in whatever ways they're capable or willing, but you'll drive away long-standing contributors who have given a LOT to the project and the community. Like Alan Cox.

      Hell, it's hard enough justifying tolerating that kind of treatment when you're paid well for it. Much less when you're volunteering your time and intellect. And as was demonstrated here, if you just spend all your time criticizing the process and the people and not contributing a lot to the resolution, people will get tired of your shit and drop the problem in your lap so they can move on.

    148. Re:Thanks by Seumas · · Score: 1

      Actually, that seems to be the attitude you assume *after* wasting ten or twenty years trying to be excellent and dedicated and realize that it's never appreciated, valued, or rewarded in any way whatsoever.

    149. Re:Thanks by SomeKDEUser · · Score: 1

      Uhhh, see, he is Alan Cox. He is the one doing intel a favour. So basically, yeah, they can terminate him. It'll be bad for them (can't retain great engineers) and he'll be employed again within the week.

      This "do what you're told, or else" only applies to the mediocre employees. You depend too much on the really good ones -- and if you can't realise that, you'll go bust.

    150. Re:Thanks by tiberus · · Score: 1

      > Heck even working at Walmart for $8/hour would be an improvement than listening
      > to all the bitching club members/users. At least Walmart pays.

      True but, that would be very near that fine line between getting paid and being insulted to your face. Can't say that I could put up with much of being bitched at for $8.00/hr.

    151. Re:Thanks by Unoti · · Score: 2, Interesting

      Your thesis just demonstrates that assholes are somewhat commonplace. It doesn't disprove that they are in fact assholes. I've commonly encountered people like you describe as well. I do what I can to not work with them. Sometimes that means eschewing entire teams or entire companies. Sane, happy people should try to stay away from total assholes. Sometimes people legitimately committed to excellence do step squarely into the realm of being assholes. But they should try not to be total jerks to their friends and coworkers. This quest to be a better person is often called "consideration", "tact" and "self-control"-- attributes that are generally considered good in our society.

    152. Re:Thanks by Ant+P. · · Score: 1

      Jeez, even new Creative cards don't work in Vista?

      And I thought I got to act like an elitist prat with my 1998 Aureal card.

    153. Re:Thanks by Anonymous Coward · · Score: 0

      > Because he didn't quit kernel development, he just stopped maintaining the TTY stack.

      Ah, so he can expect more abuse from Linus over whatever kernel development he's now going to be doing?

    154. Re:Thanks by Anonymous Coward · · Score: 0

      I think you are not interpreting that comment correctly. Emacs makes the assumption, Linus seems to agree that it is a perfectly sensible assumption for Emacs to make.

      Not to say that all of his other comments were justifiable though.

    155. Re:Thanks by tholme · · Score: 2, Informative

      It sounds like you doesn't understand what Linus is saying. He isn't insulting OGAWA by telling him that what he found out is obvious. He is just saying what _emacs does_ is an obvious assumption and therefore the commit in question is "a buggy pile of shit" and argues that it should be reverted.

    156. Re:Thanks by Anonymous Coward · · Score: 0

      8 years!? I heard it took a while to compile, but damn.

    157. Re:Thanks by smash · · Score: 1

      cheers for the clarification. as i said, just getting started, but from what i've seen, i like :)

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    158. Re:Thanks by kelnos · · Score: 2, Informative

      Is it really too much to ask for someone like Linus to respond with something like "I agree" rather than insulting the guy for making what appeared to the almighty godly genius as "obvious"?

      Actually, the bit you reference isn't Linus being a dick to the person he's quoting. He's merely stating that the assumption *in the emacs code* is obvious, in that he believes that the assumption they make (that when a child writes data, then quits, the master should get the data buffered by the time the master hears about the child quitting) is reasonable (or, as he says, "obvious"). That wasn't a flippant dismissal of the person he was replying to.

      --
      Xfce: Lighter than some, heavier than others. Just right.
    159. Re:Thanks by Anonymous Coward · · Score: 0

      That's cute. You think Walmart pays $8/hr.

    160. Re:Thanks by cowens · · Score: 1

      If you think people don't quit commercial jobs because of what they see as unreasonable demands then you haven't paid attention to the news.

    161. Re:Thanks by Seumas · · Score: 1

      I hope you're right, but the problem is that when you write for a large audience, you have to have some tact. I can't be the only one who interpreted the response as "No shit, Sherlock".

      As much as I would love to, I would never *EVER* respond to someone with "that seems obvious" unless I meant it as a gentle slight, because the moment I wrote it I would think "oh crap, that's going to come across as me being a total dick".

      More, in the context of his exchange in the rest of the thread (and his reputation), it gives such an interpretation even greater weight.

      Like I say, I hope it was misinterpreted, but others of his comments are quite clear and I think my general point of egotistical prima-donas stands. As others have pointed out, the most accomplished and capable people I know are constantly striving to measure-up and treat everyone with a lot of respect in every situation, because the best people usually suffer from the belief that they're *NOT* great or special and that they just lucked into it and will be "found out" any day.

      I dig Linus. Occasional ass or not, I have a great deal of respect for him and have benefited greatly from his work. He was obviously rather frustrated in his ongoing discussion in those threads and it clearly could have been a lot worse than it was, but at a certain point you have to stand back and reassess things.

      Anyway, I do appreciate the clarification that I seemed to have misread his intonation with his reply to that guy. (And I've obviously been on the receiving end of my fair share of dickhead responses to have instantly read it as such, so I won't deny that either).

    162. Re:Thanks by DeVilla · · Score: 1

      I did that and got ignored. The code I did to fix a security exposure was a bit waste of time. I now have my own work around so I don't run crossfire as root. The rest of Gentoo still doesn't.

    163. Re:Thanks by Risen888 · · Score: 1

      Grow up yourself. Not everyone wants to live on someone else's clock for the rest of their lives.

      Okay, that was deliberately inflammatory and not how I actually feel, but I wanted to show you how you sounded there. I feel like people who choose the "breadwinner/family man" path in life often (defensively?) take the attitude that you express in your last paragraph, summarily dismissing any other possible life choices. It's great that you want to do the family thing. You enable the propagation of the species and all that, for which I'm grateful, and you sound like your choices give your life a sense of fulfillment, which is great. But don't assume that anyone who's taken a different path in life, one that offers them the same feeling of fulfillment that you've acheived, just needs to "grow up." Not everyone should get married and have kids.

      --
      Hey, I finally got my first freak! Took you long enough!
    164. Re:Thanks by brainboyz · · Score: 1

      In California, they do.

    165. Re:Thanks by kelnos · · Score: 1

      No, I'll certainly agree with you that there's a lot about that thread that seriously lacks tact.

      I don't really know what to make about people like Linus Torvalds. Obviously I've benefited greatly from his work, and he's clearly a talented engineer, but from what I've read, it seems like he's not a particularly nice guy (and he admits this readily). I suppose it's fine to respect someone for their contributions without that really saying anything about them as a person.

      --
      Xfce: Lighter than some, heavier than others. Just right.
    166. Re:Thanks by Anonymous Coward · · Score: 0

      Yes you can

    167. Re:Thanks by yuhong · · Score: 1

      "Agreed, the BSD man pages were miles ahead of the GNU ones, atleast at that time. The GNU man pages basically a little bit of description, followed by something along the lines of "These man pages are not maintained, please see the GNU info pages for more information"." Which says it right there. Info pages are the primary docs for the GNU project, not Man pages.

  2. RAGE!!!! by Icegryphon · · Score: 1, Flamebait

    QUIT!, Can't blame him.

  3. Linus by Enderandrew · · Score: 5, Interesting

    Linus is brilliant. He is funny. Most days I really agree with anything he has to say.

    However, he has butted heads with people in the past. Perhaps this is just human nature and unavoidable from time to time. Linus isn't perfect, nor always right. I thought he was really unfair to Con Kolivas when he drove Con away.

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    1. Re:Linus by DissociativeBehavior · · Score: 0, Flamebait

      The quality of a programmer is often proportional to his ego.

    2. Re:Linus by ushering05401 · · Score: 1, Offtopic

      Con drove Con away. Someone update me if this news is stale - but Kolivas blamed hacking for all of his woes and didn't just quit kernel development when he left. Even if he is still hacking - the statements he made at the time are worth branding the guy over.

      He was not a maintainer, he was something of an artist. He could not control himself once emotions became involved and this is a fatal flaw with the maintainers.

      Everything I saw at the time these things went down suggested that Con had decided he wanted a particular thing from his involvement in the kernel - and it was the one thing he was not well suited to receive.

    3. Re:Linus by Anonymous Coward · · Score: 5, Insightful

      I'm tired of that silly myth.

      The best programmers I have met were nice people and they were very easy to get along with and work with.

    4. Re:Linus by kriston · · Score: 5, Insightful

      You forgot to use the word "inversely" in that statement.

      --

      Kriston

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

      Maybe the fact that they were nice to you affected your judgement?

    6. Re:Linus by TheWanderingHermit · · Score: 5, Insightful

      I've worked with programmers, actors, and people in many other groups where some think they can get away with being a prima donna. I have yet to meet anyone who was in top form in their field that I had to work with who really did have that attitude. I know some are out there, but overall, those that want to do something right are too concerned about what they're doing to pump up their own ego. Generally the best are the ones that know more than others, but because of that, they realize how much they DON'T know and that tends to keep them from getting those ego highs.

    7. Re:Linus by Freetardo+Jones · · Score: 1

      Then you never saw the flamefests that happened on lklm

    8. Re:Linus by Jurily · · Score: 4, Insightful

      Bullshit. The best programmers don't know if they're awesome. They just think everyone else is stupid.

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

      Maybe the fact that they had a big ego affected your judgement?

    10. Re:Linus by Enderandrew · · Score: 4, Informative

      Con wrote some fantastic code that benchmarks over years constantly showed to be a huge improvement. Linus refused to incorporate good code.

      Con maintained his patches separately, Even better, he took criticism on his work and sought to improve it. Time after time he made changes to his work to try and make it more acceptable to Linus. Linus rebuked Con and said not nice things. Con kept working.

      This continued for years. Eventually Linus realized that Con was right on scheduler philosophy. But Linus couldn't admit that he had been an overbearing ass for the past three years on a technical issue where he was clearly wrong. He asked someone else to write a new scheduler from scratch rather than use one that has been tested for three years. When the new scheduler was hastily written, and Con's was faster, Linus said he only cared about superior code and making the right decision for the kernel. But he made sure to make several personal attacks on Con for good measure.

      Logically, Linus inserted untested code that was still being developed in as the new scheduler. It didn't matter if it was technically inferior and unstable. His justification was that he felt the new code would be supported, where as Con would never support his code. This assertion flies in the face of Con supporting and improving his patches for years. I've contacted Con on his mailing list. He was always cordial, and willing to support people who wanted to use his patches. Nobody made Con support those patches. But he had the mailing list none the less.

      There is no logical justification for taking inferior, untested, unstable code over superior, stable, tested code. Even worse, there was no reason for Linus to repeatedly attack Con personally and lie about him.

      It is one thing to suggest Hans Reiser would abandon reiser4 the way he did reiser3. It is another to make baseless accusations at good developers.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    11. Re:Linus by Anonymous Coward · · Score: 0

      http://74.125.155.132/search?q=cache:http://lkml.org/lkml/2009/7/28/373&hl=en&strip=1

      Wow, the Hate just pours from the words on that page ;-)

    12. Re:Linus by cnettel · · Score: 2, Insightful

      Yeah, and although this invalidates the original statement (that brilliant programmers have great egos), your statement still means that great programmers give everyone else a hard time. Especially when that belief that someone else is stupid ends up being wrong once in a while.

    13. Re:Linus by Lord+Ender · · Score: 4, Interesting

      Serious question: what percentage of the current Linux kernel was actually written by Linus?

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    14. Re:Linus by Anonymous Coward · · Score: 0
    15. Re:Linus by Anonymous Coward · · Score: 3, Funny

      Is that you Theo?

    16. Re:Linus by Anonymous Coward · · Score: 2, Informative

      About 2% (enormous amount)

    17. Re:Linus by Jurily · · Score: 2, Insightful

      your statement still means that great programmers give everyone else a hard time

      Alright, I'll rephrase: great programmers think they're slightly above average, and they don't understand why other people can't solve problems that easily.

      They won't say "use this algorithm because I'm the greatest". They'll say "use this because it's 20% faster and only uses half the memory". And if they're wrong, they're smart enough to realize it.

    18. Re:Linus by Joe+Snipe · · Score: 1, Flamebait

      This sounds like another good reason to switch to BSD. Strike two linux!

      (FWIW strike one is linux's sound architecture)

      --
      Sometimes, life itself is sarcasm...
    19. Re:Linus by geekboy642 · · Score: 5, Funny

      Being smarter is a big factor in programming well. Being obviously smarter than those around you is, well, a major cause of huge ego syndrome.

      Don't you get a swollen head when you walk amongst dullards? Every time I see somebody pushing at the 'pull' on a door, I feel my disdain for others rising. When I stand behind a dunce in line, and hear him ask how many eggs in a dozen, I grow more sure of my position among the intellectual greats. When a waiter is unable to figure sums on his pad to give me a total, that I might reimburse him fairly for his service, I scoff at the fools that populate this world. In fact, in every day, in every way, the imbeciles I walk around cause my ego to grow nigh unto titanic proportions, certain I must be nearly akin to God Himself in my intellectual powers.

      And I can only program in Basic. Imagine those towers of mind that must be a C programmer!

      --
      Just another "DOJ fascist authoritarian totalitarian bootlicker" -- Zeio
    20. Re:Linus by Anonymous Coward · · Score: 0

      So let it be known that Linus does not take kindly to anyone mucking up the kernel. He takes kernel maintenance quite seriously, even though it's not solely his own. As he has stated before: A maintainer may have been alright yesterday or last week, but did they take their meds today?

    21. Re:Linus by Bill+Dimm · · Score: 5, Informative

      That's called the Dunning-Kruger effect

    22. Re:Linus by Bill,+Shooter+of+Bul · · Score: 1

      Yeah, but in this case he doesn't come off looking too bad. Basically it boils down to this summary

      Cox -> submits code with a bug in it
      User -> reports bug in code
      Cox -> blames other code, doesn't acknowledge bug
      Linus -> blames Cox for ignoring bug
      Cox -> states that he's been working hard to fix bug, not easy. He quits.

      Can't tell from the selected communication, how much Cox had ignored the bug, blaming other people or if he explained in a email the complications of the fix.

      Tough to judge, based on the limited communication presented in public.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    23. Re:Linus by n3v · · Score: 1

      Directly proportional or inversely proportional?

    24. Re:Linus by mwvdlee · · Score: 1

      And, apparently, the quality of a project leader is inverse proportional to his ego.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    25. Re:Linus by Metasquares · · Score: 3, Informative

      Big ego != nasty

    26. Re:Linus by dgatwood · · Score: 1

      I've always described this effect with the axiom, "People who feel the need to call themselves experts rarely are. The same can be said for those who call themselves professionals." I'm glad somebody finally got around to studying this effect and giving it a name.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    27. Re:Linus by mwvdlee · · Score: 1

      Linus wrote roughly 100% of the original kernel, which was then roughly 100% replaced by other programmers.

      Basically, Linus' main role in Linux has been to initiate the project.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    28. Re:Linus by Grishnakh · · Score: 3, Interesting

      BSD has terrible driver support compared to Linux.

      If you don't like the way Linus maintains the Linux kernel, then fork it and maintain your own branch. That's a lot easier than messing around with a different kernel that doesn't have half the driver support that Linux has. All you have to do is take what's there in Linux, then change the things you don't agree with (like dumping ALSA and moving back to the new OSS).

      It'd really be interesting if someone seriously made a Linux fork to compete with Linus.

    29. Re:Linus by Enderandrew · · Score: 0, Flamebait

      If you refuse to use software developed by a person who flamed someone else, then I assume you're not familiar with Theo de Raadt?

      And frankly if you prefer BSD, more power to you. Use what you want.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    30. Re:Linus by Enderandrew · · Score: 5, Interesting

      I'm reading the thread. This is my take.

      Cox -> submits code which apparently caused a bug
      User -> Reports breakage
      Cox -> Can't replicate breakage and asks user for debug info so he can fix it.
      User -> Says they don't know what to debug for, but is willing to work with Cox.
      Linus -> Jumps in and calls Cox's code a buggy piece of shit before any debugging took place, and before it is established if the code is buggy or not.
      Cox -> Continues to troubleshoot the issue.
      Linus -> Flames Cox personally and says Cox is unwilling to work on the issue.
      Cox -> Takes his ball and goes home, except in this case, it is OSS so he doesn't really take any ball with him. He just leaves.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    31. Re:Linus by Capt.DrumkenBum · · Score: 1

      Don't let your head swell so much you can't get through the door.
      We all have these moments, I call them moron moments, where we will do truly stupid things.
      Using myself as an example: I have a (Tested) IQ of 151, and just this morning, I found myself pulling on a door clearly marked Push.

      --
      If I were God, wouldn't I protect my churches from acts of me?
    32. Re:Linus by TheWanderingHermit · · Score: 4, Interesting

      Harry Truman used to say he didn't want to talk to experts because an expert was just someone who didn't want to learn anything more on a subject because if he did, then he'd find out he didn't know it all and wasn't an expert any longer.

    33. Re:Linus by iluvcapra · · Score: 4, Interesting

      The quality of a programmer is often proportional to his ego.

      Be careful: Humans confuse cockiness with expertise.

      --
      Don't blame me, I voted for Baltar.
    34. Re:Linus by orkybash · · Score: 2, Insightful

      A programmer with a big ego is more likely to write code that only they can maintain. So, I would have to disagree with your statement.

    35. Re:Linus by BorgHunter · · Score: 1

      This sounds like another good reason to switch to BSD. Strike two linux!

      (FWIW strike one is linux's sound architecture)

      I think more than a few people would be willing to use BSD, if the driver situation weren't so bad for it. It's worse than the situation Linux is in, and Linux has some severe driver problems as well (just look at ATI video cards).

      --
      "Excuse me, did you say 'Trekker'? The word is 'Trekkie.' I should know; I created them." -- Gene Roddenberry
    36. Re:Linus by cheftw · · Score: 1

      Perhaps there was a decimal error on your IQ score?

      (yes thank you I knew they were integers)

      --
      Always back up, never back down. ---- Think you're cool 'cos your uid is prime? Take mine, modulo the one digit integers
    37. Re:Linus by BlackSabbath · · Score: 1

      That's exactly how I recall it playing out. And I must add that my perception of Linus was permanently altered by those events. I too found Con eminently approachable and helpful. The initial flakiness with Ingo's scheduler and the sour taste left by Linus's self-righteous excuses for behaving like a complete c*nt put me off Linux for good (FWIW I switched to Macs - good enough for work and play).

    38. Re:Linus by diegocgteleline.es · · Score: 3, Informative

      You just need to change in your article the name "linus" by "ingo" and then your post may have some sense. Which shows how much you "know" about the topic.

      Linus didn't even bothered with the scheduler, Ingo was the maintainer and it was him who was in charge of deciding what should replace it. It was him who argued, not linus. It was him who ended up admitting that the ideas from Con were good and he wrote the scheduler which is now into the kernel. One that, according to Con, was better than his own scheduler.

    39. Re:Linus by LWATCDR · · Score: 1

      I agree the best programmers are the ones that are secure enough with their abilities to be modest and easy to work with. Those that have overinflated egos also tend to have a over related reputation.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    40. Re:Linus by Enderandrew · · Score: 5, Interesting

      I read the LKML for years.

      Ingo did write the new scheduler, at the request of Linus. Ingo didn't make personal attacks on Con.

      Linus was the one for years who said Con was wrong about scheduler theory. Ingo admitted Con was correct, but Linus wouldn't admit he was wrong. Linus asked Ingo to write a new scheduler, basically ignoring the one Con had submitted.

      When several people pushed to include Con's scheduler (which at that point was called Staircase) Linus made more personal attacks and wrapped it up saying that Con couldn't be trusted to support his work.

      Ingo had nothing to do with that.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    41. Re:Linus by Scragglykat · · Score: 1

      KHAN!!!!!!!!!!!!!!!!! ... wait, that was a different person entirely.

    42. Re:Linus by lazy_playboy · · Score: 1

      If you're head swells when you hear someone ask how many eggs are in a dozen, you're setting a very low bar for yourself.

    43. Re:Linus by sgage · · Score: 1

      But when a very competent person is trying to help further your project (and has done so effectively for years), it's not very smart to give them shit. But some people would rather be "right" than effective. Oh well, human nature and all that.

    44. Re:Linus by HappySmileMan · · Score: 1

      Being obviously smarter than those around you is, well, a major cause of huge ego syndrome.

      Actually this has been studied, look up the "Downing effect" and you'll find that studies have shown that most intelligent people are likely to under-estimate their own intelligence, and most unintelligent people are likely to think that they're very smart.

      Same goes for specific fields, people who do well and people who think they're great are usually not the same people.
      I've seen this myself when doing exams to be honest.
      People who come out of exams thinking they've aced it often end up getting worse marks than the people who came out worrying.

    45. Re:Linus by ioshhdflwuegfh · · Score: 1

      Generally the best are the ones that know more than others, but because of that, they realize how much they DON'T know and that tends to keep them from getting those ego highs.

      oh, I know that I know nothing? Socrates? The one who does not write? Not even computer code?

    46. Re:Linus by ioshhdflwuegfh · · Score: 5, Funny

      Harry Truman used to say he didn't want to talk to experts because an expert was just someone who didn't want to learn anything more on a subject because if he did, then he'd find out he didn't know it all and wasn't an expert any longer.

      Yeah, Harry was a real expert on experts.

    47. Re:Linus by diegocgteleline.es · · Score: 2, Informative

      I read the LKML for years.

      So do I, and I won't ask you to search proofs of what you say because it's just lies. Try to find just one single phrase where Linus tells Ingo to wrote a new scheduler. You won't find it because it was Ingo who decided to write it, as he explained in the initial announcement.

    48. Re:Linus by stim · · Score: 1

      Not sure if you were going for a funny mod, but you sound like a complete tool to me. Somebody please mod this guy down.

      --
      Browse at -1 to keep an eye out for abuses.
    49. Re:Linus by caerwyn · · Score: 3, Insightful

      A tested IQ of 151... and you think IQ is related to intelligence?

      --
      The ringing of the division bell has begun... -PF
    50. Re:Linus by ioshhdflwuegfh · · Score: 3, Funny

      Using myself as an example: I have a (Tested) IQ of 151, [...]

      Howdy Forest!

    51. Re:Linus by tyrione · · Score: 4, Funny

      You just need to change in your article the name "linus" by "ingo" and then your post may have some sense. Which shows how much you "know" about the topic.

      Linus didn't even bothered with the scheduler, Ingo was the maintainer and it was him who was in charge of deciding what should replace it. It was him who argued, not linus. It was him who ended up admitting that the ideas from Con were good and he wrote the scheduler which is now into the kernel. One that, according to Con, was better than his own scheduler.

      Ingo might as well the be the secret lover of Linus or his offspring from a parallel universe. The guy talks so fondly of him you'd think they run through the fields in slow motion towards one another as the Sound of Music is playing in the back drop.

    52. Re:Linus by Applekid · · Score: 1

      Using myself as an example: I have a (Tested) IQ of 151, and just this morning, I found myself pulling on a door clearly marked Push.

      I think getting that right would have netted you an extra point. :)

      Note to self: purchase some quantity of Push and Pull stickers and apply the inverse sticker over each I see in everyday life.

      --
      More Twoson than Cupertino
    53. Re:Linus by Anonymous Coward · · Score: 0
      There were very legitimate concerns about Con's code. It was large, somewhat complex and it had some bad fail cases. his schedulers didn't fix everything, they did create a nice feeling desktop experience though.

      We have an even better scheduler now and the code is substantially better than the staircase scheduler.

      As with Reiser, benchmarks don't mean the code is good. This is something associate developers learn early on, benchmarks are nice and often needed but they alone are not an indicator of quality. It's not like they won't tell you what concerns them when you submit a patch and simply resubmitting it with new benchmarks doesn't fix it. I get it, it hurts the ego and for some introverted developers it's quite a risk to put yourself out there like that, but you either grow or you shrink and go away.

    54. Re:Linus by GrievousMistake · · Score: 3, Insightful

      Basically, Linus' main role in Linux has been to initiate the project.

      And manage it, that's huge. He still has the final say on any code that goes into the main line. Any serious kernel developer will have to at least tolerate him, which shapes the direction of Linux immensely.

      --
      In a fair world, refrigerators would make electricity.
    55. Re:Linus by Hikaru79 · · Score: 5, Informative

      By his own measure, he says about 2% of the code in today's kernel is written by him, but about 80% of it goes through him before being included. It's unrealistic to expect any one person to have a significant percentage of Linux code literally belong to them, so it would be disingenuous to use that 2% figure as some sort of argument to undermine Linus' authority with regards to the kernel.

      Like him or not, Linus is still the man in linux kernel development circles, and for good reason.

    56. Re:Linus by nomadic · · Score: 1

      Every time I see somebody pushing at the 'pull' on a door, I feel my disdain for others rising.

      Hey, I've done that...

    57. Re:Linus by Tacvek · · Score: 4, Informative

      The whole thing is publicly available. See This Google Groups thread

      The big problem is that there where multiple issues, at least one of which was a userspace bug. Cox originally questioned the Emacs code on one half of the bug, although he seems to have since taken that back. At first Cox seemed insistent on solving the issue one way which appeared to work but was not technically sound. But now he and Linus appear to agree on the basic solution, although a few issues sound like they still need to be hashed out.

      Overall a classic miscommunication flare-up.

      --
      Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
    58. Re:Linus by nine-times · · Score: 2, Insightful

      I would go further than that and say that there's something about "having a relentless ego" that tends to work against "being great". Having some kind of an ego can help. It can make you more bold and assertive and willing to pursue your own good ideas even when others are unconvinced. On the other hand, being unwilling to acknowledge your own mistakes and shortcomings leaves you prone to repeat mistakes. Also, having such a large ego that you're prevented from working well with others often ends up with sub-standard output-- because let's face it, we generally can't do it alone, whatever "it" is.

      In this example, Torvalds may be brilliant, but he certainly hasn't built Linux all by himself, and it's very unlikely that he could have built it himself. In order to produce the Linux kernel, he had to work with others. And he must not always be too awful to work with, or someone would have forked the kernel a long time ago.

    59. Re:Linus by Brian+Feldman · · Score: 1

      Sorry, but I don't think you know what you're talking about. Are you confusing esoteric hardware with common hardware?

      --
      Brian Fundakowski Feldman
    60. Re:Linus by ioshhdflwuegfh · · Score: 1

      This sounds like another good reason to switch to BSD.

      And why not SunOS?

    61. Re:Linus by Zancarius · · Score: 2, Interesting

      If you refuse to use software developed by a person who flamed someone else, then I assume you're not familiar with Theo de Raadt?

      The OP wasn't specific about which BSD variant he would switch to; neither is de Raadt representative of how all the BSDs are managed. FreeBSD's governance structure has worked marvelously well over the years, so I would say it's unfair to implicitly lump every BSD under the same umbrella as OpenBSD and its management.

      (I realize that may not have been your intent, but you used the same generalizations as the OP. Just being fair here. :)

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
    62. Re:Linus by Enderandrew · · Score: 1

      I was merely trying to suggest it is hard to boycott an entire OS because of one developer flaming someone. I could have just as easily asked if he was going to boycott the GNU userland because of Stallman.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    63. Re:Linus by Anonymous Coward · · Score: 0

      Strike one is "Linux software's ability to work with other Linux software", sound being a part of that.
      BSD (for desktop use, which is assumed as you mentioned sound) is generally the same software or less-developed versions of similar software. BSD is not the answer.

    64. Re:Linus by dvice_null · · Score: 5, Interesting

      > I found myself pulling on a door clearly marked Push.

      That is actually just an UI bug in the door. If you want people to push a door, you should use a handle that is like a plate, where you can easily put your hand against and push it. If you want people to pull the door open, you need to use vertical rod as a handle, where people can easily grab on to pull it. With this very small change, you don't even need to push/pull texts on the doors.

      Also, doors should be always pulled when you go in and pushed when you go out. That makes exiting the building easier in case of emergency (people don't rush to the door and jam it, preventing anyone from pulling it open.) and also when people are trying to get in and out at the same time, the person outside is more capable of keeping the door open for the person going out (it is better that people first get out, before new people get in, because inside there is a limited space, while outside contains usually a lot more room). Also outside usually contains more room for pulling, while the inside often has a wall that limits the space for pulling, especially if you want to keep the door open for someone else.

    65. Re:Linus by speedtux · · Score: 1

      So what do you want Linus to do? Commit harakiri? Stop kernel development?

      People who run big projects regularly make bad calls and piss off people; that just comes with the territory. Do you seriously think you'd do any better than Linus in his position?

    66. Re:Linus by Zancarius · · Score: 1

      BSD has terrible driver support compared to Linux.

      First, I don't intend to suggest you're wrong. I am curious as to why you have arrived at this conclusion. My own personal experiences have been a bit different. (Although, I have only used FreeBSD on servers and under a very limited capacity on the desktop--I assume that's where your gripe exists.)

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
    67. Re:Linus by blind+biker · · Score: 1

      This sounds like another good reason to switch to BSD. Strike two linux!

      (FWIW strike one is linux's sound architecture)

      Wow. I couldn't agree more, on both points.

      --
      "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
    68. Re:Linus by FishWithAHammer · · Score: 2, Informative

      The kernel still contains about two percent Linus-code, which is a staggering amount for one person on a project so large.

      --
      "You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
    69. Re:Linus by J+Story · · Score: 1

      This is off-topic, but the new OSS is quite decent.

      Issues with pulse (cpu-hog + buggy) and ALSA made me re-evaluate OSS and it has turned out to be very workable. A second look at what OSS is today would not be a bad idea.

    70. Re:Linus by socz · · Score: 1

      That's what I say, use what works best for you! I of course run junk so GhettoBSD is the way for meeeeeeee

      But too bad what happened, i've been under similar circumstances where i've poured my heart into my work and have been burned (or felt i was burned). It's just how it goes sometimes.

      --
      My abilities are only limited by my imagination
    71. Re:Linus by Grishnakh · · Score: 0, Flamebait

      That's exactly the issue. Servers don't need much driver support: just for things like chipsets, RAID cards, ethernet cards, etc. Servers don't need drivers for things like 3D video cards, sound cards, USB gadgets, video capture cards, etc.

      Does FreeBSD even have any 3D video drivers for Nvidia or AMD? If not, then it's not worth even thinking about using it on the desktop for most people.

    72. Re:Linus by Jamu · · Score: 1

      Me too. Simple mechanical tasks require so much less attention than actually reading what's on the door.

      --
      Who ordered that?
    73. Re:Linus by Anonymous Coward · · Score: 0

      Your humor and satire recognition circuits need work. Please recalibrate.

    74. Re:Linus by Anonymous Coward · · Score: 0

      I don't think it's all that simple. Linus is an ASM hacker par excellence. He's utterly brilliant in that area.

      Problem is, he thinks he's brilliant everywhere else. And I think there's the real problem with claimed expertise -- the claimants usually have far less ability to know where it actually ends.

    75. Re:Linus by JumpDrive · · Score: 1

      You know this thread is heading the way of the argument of FreeBSD for servers and Linux for laptops and desktops.
      This isn't the first time I've heard this in the last year.
      But, it sounds awfully similar to the arguments that were being made 20 yrs ago about Windows and Linux.

    76. Re:Linus by billcopc · · Score: 1

      Where are my mod points when I need them ? :P

      That is awesome, and yet the /. of 2009 is so full of jealous pseudo-intellectuals that yours and most other insightful posts will likely be downmodded.

      --
      -Billco, Fnarg.com
    77. Re:Linus by mcpkaaos · · Score: 4, Funny

      That's okay, intelligence is simply potential you don't always use. I take pride in this fact, as I'm saving all my smart moments up for when I finally meet Hawking in person and frickin' own him.

      --
      It goes from God, to Jerry, to me.
    78. Re:Linus by Bill,+Shooter+of+Bul · · Score: 4, Funny

      Ok, I see now what happened. Linus won the technical battle, but wasn't satisfied at Cox's capitulation. Cox wanted to lose the argument with grace, Linus wouldn't let him.

      A classic moment in arguing. A sly technique in the midst of an argument when you realize that despite everything you said to the contrary, you are really, really wrong. But, you don't want to admit it and the other person hasn't figured out that you know you're wrong. So you say something deliberately confusing that could be interpreted as supporting your opponent's argument, or your previous one. He assumes you are supporting the same side as ever and continues to hammer the point. You continue to make misleading statements, until you've slowly started to argue his side a little clearer. At this point he's really confused and asks you if you support your original statement, you say that's absurd and would never believe such a stupid thing. He's won, but you don't agree you were ever wrong. Just a "miscommunication" and "we were both right".

      My younger brother used to do that to me all the time. Drove me nuts.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    79. Re:Linus by raddan · · Score: 5, Informative

      BSD has terrible driver support compared to Linux.

      My experience has been exactly the opposite. It wasn't until Ubuntu 8.10 came around (having also tried Red Hat and Gentoo) that I found Linux's driver support to be acceptible. By contrast, my OpenBSD installs always worked for me out of the box. The only driver issue that's ever irked me there were USB-serial adapters. But the ease of configuration in OpenBSD has always been great, especially for wireless.

      Anyhow, it probably depends on what you're doing, and with what hardware. Just thought I'd throw that out there, though.

    80. Re:Linus by ross.w · · Score: 1

      Does FreeBSD even have any 3D video drivers for Nvidia or AMD? If not, then it's not worth even thinking about using it on the desktop for most people.

      Yes

      --
      If my call is important, why am I talking to a recording?
    81. Re:Linus by Tubal-Cain · · Score: 1

      If you are going to repeat yourself so much, could you at least provide links?

    82. Re:Linus by hobbit · · Score: 4, Insightful
      --
      "Wise men talk because they have something to say; fools, because they have to say something" - Plato
    83. Re:Linus by CorporateSuit · · Score: 1

      This describes everyone who argues with me on slashdot!

      --
      I am the richest astronaut ever to win the superbowl.
    84. Re:Linus by MoeDrippins · · Score: 4, Informative

      He's obviously read "Psychology of Everyday Things" (later reprinted as "Design of ..."), where this door UI issue is discussed in several case studies. "POET" is a classic must-read for anyone that designs anything that anyone might be expected to use.

      http://www.amazon.com/Design-Everyday-Things-Donald-Norman/dp/0465067107/ref=sr_1_1?ie=UTF8&qid=1248908564&sr=1-1

      --
      Before you design for reuse, make sure to design it for use.
    85. Re:Linus by raddan · · Score: 1

      There's quite a bit of code-sharing between the BSDs. I wouldn't be surprised if you found Theo's name stamped all over parts of FreeBSD. Then again, maybe they dislike him intensely enough that they would rather roll their own than import his code.

      I've been flamed by Theo before. IIRC, he accused me of 'having ADD' the last time I spoke with him. It doesn't much change my opinion of the project, or of his abilities, but it suffices to say that talking to him doesn't exactly give me a warm, fuzzy feeling.

    86. Re:Linus by CarpetShark · · Score: 1

      Con wrote some... Linus rebuked Con... Con kept working... Con was right... Con's was faster... several personal attacks on Con... Con would never... I've contacted Con... Nobody made Con support those... to repeatedly attack Con personally

      Reading all that was really horrible. I can't believe you'd deliberately avoid his proper name just because he's been in prison.

      (Just kidding. Even just from my small involvement in patching apps, I suspect the comments about Linus being an ass are more than correct, and that Alan and Con and others deserve our thanks).

    87. Re:Linus by Grishnakh · · Score: 1

      I disagree. You could make lots of valid arguments for FreeBSD vs. Linux on servers. But on desktops, unless you have some kind of counter-argument for the fact that FreeBSD doesn't have any 3D drivers (nor drivers for many other desktop-only gadgets), then there's no valid argument to make in favor of FreeBSD on the desktop.

      Now this doesn't mean that you can't run FreeBSD on your own desktop. I started running Linux on my desktop way back in 1999 when a lot of things in the Linux world were much worse than they are now, such as drivers. But if you do, you'll be missing out on a lot of things that are commonplace or easily achieved on a Linux desktop, such as playing 3D games (like TuxRacer, Neverball, etc.), running 3D apps (like Google Earth or Compiz), using various devices like video capture cards, and also having easy access to software repositories like Ubuntu's or Debian's with tens of thousands of pre-compiled apps. If you're ok with missing out on that stuff, then more power to you. But this clear difference does seem to make Linux the winner on the desktop in this open-source race. And this is quite different from any Windows vs. Linux arguments, since Windows isn't open-source.

    88. Re:Linus by Grishnakh · · Score: 2, Insightful

      Interesting. My information seems to be outdated then, and this invalidates most of my arguments.

    89. Re:Linus by fred+fleenblat · · Score: 2, Insightful

      Well said. About the only counterpoint is that a door which opens outward will tend to have hinges on the outside, making illegal entry easier.

      Where I live, commercial establishments usually have outward opening doors for the safety of the large number of people that might need to exit in an emergency; whereas residential doors will have inward opening doors so that the hinges are not exposed.

    90. Re:Linus by Anonymous Coward · · Score: 0

      "If you don't like the way Linus maintains the Linux kernel, then fork it and maintain your own branch. "

      *bangs head on table*

    91. Re:Linus by Anonymous Coward · · Score: 0

      On a side note:

      Every time I see somebody pushing at the 'pull' on a door, I feel my disdain for others rising.

      Zoning ordinances in most cities, in most parts of the world, require all exterior doors to open OUT. So that people don't crush themselves trying to get out during a panic. I always pull on those doors, and if they only open inward, I do it VERY loudly and sometimes even break them. It's something that simply pisses me off, and when the employees get mad I simply tell them I'll call the fire marshall, which shuts them up fast.

      When I stand behind a dunce in line, and hear him ask how many eggs in a dozen, I grow more sure of my position among the intellectual greats.

      Hopefully, you don't also do that at the bakery. I get really angry when some moron at the bakery tries to tell me that there are only 12 items in a baker's dozen. There are 13, not 12.

      My point being, just because you think you're smart, doesn't mean you are. Chances are you are just too dumb to realize that you are, in fact, the one in the weeds.

    92. Re:Linus by recoiledsnake · · Score: 2, Informative

      I'll do that.

      http://apcmag.com/interview_with_con_kolivas_part_1_computing_is_boring.htm

      http://apcmag.com/why_i_quit_kernel_developer_con_kolivas.htm

      http://linux.slashdot.org/article.pl?sid=07/09/01/1853228&from=rss
      vhttp://linux.slashdot.org/linux/07/09/14/156234.shtml
      http://linux.slashdot.org/article.pl?sid=07/09/18/131240

      From my own post here http://linux.slashdot.org/comments.pl?sid=301061&cid=20655809

      Re:No you can not (Score:4, Informative)
      by recoiledsnake (879048)
      on Tuesday September 18 2007, @01:35PM (#20655809)
      That is a gross over-simplication of what happened and almost qualifies as revisionist history and brushing things under the carpet. Let me summarize my understanding of what happened and someone please correct me if I am wrong.

      Con Kolivas had been shouting from rooftops about slow desktop performance and was submitting feedback and bug reports. One of the kernel devs apparently said "I do not notice the issue on my quadcore machine with 4GB RAM". Rightly or wrongly, this lead Con to believe that the kernel devs do not care about desktop performance and only give priority to issues that big corporates complain about.

      In the true open source style, he took upon himself to learn kernel programming and released a whole set of -CK patches and various versions of benchmarking tools and schedulers. On the other side, Ingo Molnar was the maintainer of the scheduler portion of the kernel and maintained that the O(1) scheduler(and the one before it?) is good enough and has no problems. Con conclusively started proving this wrong with his benchmarks. At this point, everyone assumed the -CK branch would be merged into the kernel at some point and Linus says he had been considering it.

      At some point, Ingo starts making his own scheduler, which later evolved into the Completely Fair Scheduler. A number of posts claim that it was kind of rip off of the ideas behind Con's scheduler with which it was in a race to get included in the kernel. Then Linus decides to include CFS into the kernel instead of Con's scheduler. The reason he gave was that Con thought SD was perfect and that he ignored and flamed the users on the CK mailing list and that he(Linus) was far more comfortable working with Ingo since he knew him well. He also admitted that he might have formed this opinion on a single incident on the mailing list and he didn't have the time to follow the CK mailing list.

      Some people on Con's side in the LKML tried to explain this by saying that the single incident was in response to a troll who submitted faulty bug reports and ignored the reasons for why they were rejected and that Linus was playing favorites. Con couldn't take the non-inclusion of -CK and plugsched(which would have given users a clean way of using a custom scheduler) and quit kernel development totally.

      The latest twist in the story was reported on Slashdot here [slashdot.org]. The gist of it was that another hacker(Roman Zippel) was trying work on CFS. He had asked questions about what some parts of the code did, and also made some patches that considerably simplified the code and mathematically proved his patches made things better. In response, Ingo came out with a big patch that ripped out the code that was questioned and included Roman's Zippel's ideas(another rip off?) with hardly any discussion and a tangential acknowledgement of including his changes. Roman complained that talking in patches without explanation is detrimental to collaborative OSS development. /quote

      --
      This space for rent.
    93. Re:Linus by Grishnakh · · Score: 1

      It worked for XFree86, maybe Linux needs a fork too.

    94. Re:Linus by Sancho · · Score: 1

      Actually, a lot of code from OpenBSD ends up in FreeBSD. Look at the PF firewall, many WLAN drivers, etc.

    95. Re:Linus by fnord_uk · · Score: 1

      I didn't exactly meet him, but he did nearly run me over in his dalek undercarriage when I staggered out of a pub, pissed, in Cambridge one night. I remember thinking that his wife was quite fit, but that could have been the beer goggles.

      fnord

      --
      In theory, theory and practice are the same. In practice, they're not.
    96. Re:Linus by Enderandrew · · Score: 2, Informative

      The only problem with this accounting is that it makes it seem like there wasn't much time between the -ck patches and the CFS. There was a three year period in there, in which Ingo reviewed the -ck patches repeatedly.

      Ingo did publicly admit that he took the concept from the Staircase scheduler in writing his own CFS.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    97. Re:Linus by Enderandrew · · Score: 1

      Please see my parent post where I say most of the time I really agree with him, and that nobody is perfect. Everyone has a few personality conflicts.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    98. Re:Linus by Anonymous Coward · · Score: 1, Interesting

      big ego = alone

    99. Re:Linus by FireFury03 · · Score: 2, Informative

      Does FreeBSD even have any 3D video drivers for Nvidia or AMD? If not, then it's not worth even thinking about using it on the desktop for most people.

      I think you'll find that most people actually don't really care about 3D. So long as the graphics drivers can run their desktop then most people are happy (Compiz Fusion runs just fine on Intel GPUs).

      A minority of people are gamers and therefore do care about 3D. These people will be running Windows since thats where most PC games are.

      An even tinier minority actually work in the field of 3D graphics.

    100. Re:Linus by commodore64_love · · Score: 1

      Why not Amiga OS?

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    101. Re:Linus by Dan9999 · · Score: 2, Informative

      part of this reminds me of how annoying it is to have people try to get into the elevator before everyone has gone out

    102. Re:Linus by Anonymous Coward · · Score: 0

      He basically yelled, "DISREGARD, I SUCK COCKS!"

                 

    103. Re:Linus by Anonymous Coward · · Score: 0

      > I found myself pulling on a door clearly marked Push.

      That is actually just an UI bug in the door.

      That's what you get for not buying Apple.

    104. Re:Linus by Zancarius · · Score: 1

      Actually, a lot of code from OpenBSD ends up in FreeBSD. Look at the PF firewall, many WLAN drivers, etc.

      Indeed it does, and if you were to have read my comment, you might note that I was careful to point out project management. Whether the product is shared or not is largely moot since the entire objective of this thread was over how a project is managed.

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
    105. Re:Linus by Zancarius · · Score: 1

      There's quite a bit of code-sharing between the BSDs. I wouldn't be surprised if you found Theo's name stamped all over parts of FreeBSD. Then again, maybe they dislike him intensely enough that they would rather roll their own than import his code.

      I sincerely doubt that they'd be so silly as to let the abrasiveness of someone's personality dictate whether they include code or not. For other OpenBSD spin-off projects (OpenSSH), they seem to be included most everywhere.

      But again, as I pointed out to someone who replied to me (below), my statements were explicitly about project management, not the actual product. Hence why I wanted to indicate that Theo is not representative of all the BSDs as he is the head of OpenBSD. Whether FreeBSD or NetBSD shares code with them is incidental; the management is entirely different.

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
    106. Re:Linus by eudaemon · · Score: 1

      Buy a flush hinge for your outward opening door. Problem solved.

    107. Re:Linus by Zancarius · · Score: 1

      And this is quite different from any Windows vs. Linux arguments, since Windows isn't open-source.

      No, it's not. The spirit of the argument is that--at the time--Linux had limited support. It's true. Developers were focusing on Windows.

      Now, while that may not have changed all that much, developers for the enterprise cannot help but pay attention to Linux. So really, the poster you're taking issue with has a point; to a certain extent the idea of FreeBSD v. Linux is analogous to Linux v. Windows.

      But, back to your earlier comment, I think you pretty well inadvertently displayed your bias against BSD for whatever reason by suggesting 3D video cards weren't supported. That may be true for ATI, but NVIDIA releases drivers specifically for FreeBSD. I also know of a gentleman who managed to get WoW working under Wine in FreeBSD, too, on (at the time) very new hardware.

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
    108. Re:Linus by Phoenix138 · · Score: 3, Informative

      Also, doors should be always pulled when you go in and pushed when you go out. That makes exiting the building easier in case of emergency (people don't rush to the door and jam it, preventing anyone from pulling it open.) and also when people are trying to get in and out at the same time, the person outside is more capable of keeping the door open for the person going out (it is better that people first get out, before new people get in, because inside there is a limited space, while outside contains usually a lot more room). Also outside usually contains more room for pulling, while the inside often has a wall that limits the space for pulling, especially if you want to keep the door open for someone else.

      Your door would suffer from issues if installed in an environment where it snows a lot.

    109. Re:Linus by Velaki · · Score: 1

      When people who tell me, "Programming is hard. I could never program," I respond with, "If you can make out a shopping list, buy the groceries and cook dinner, serve it on the table, and enjoy a good meal; then, you can design, write, implement, and deploy a program. Only the language is different."

      Basically, I'm a c programmer. I tell people, "If I can do it, anyone can do it."

      I leave out the part where I tell them I've been doing it for almost 30 years. :-) Most programmers I know, who happen to be really good at programming, lack that superficial ego. They have fun doing it, and love to share.

      But that's just my experience.

    110. Re:Linus by Anonymous Coward · · Score: 0

      Cox -> Takes his ball and goes home, except in this case, it is OSS so he doesn't really take any ball with him. He just leaves.

      Except, from my reading, he continued to discuss the issue and replied to someone asking what was needed to pick up where he left off. He just stopped being team captain for the St. Louis TTYs.

    111. Re:Linus by Anonymous Coward · · Score: 0

      Watch this: Linus on git at google

      It's Linus talking about git. He's so far up himself in this talk, and so unfunny it's tragic. I'm sure his boasting is intended as humour, but he just has no 'feel' for how he comes across. I respect him for his technical chops. He's does great work ... ... but he's an arse hat.

    112. Re:Linus by ioshhdflwuegfh · · Score: 1

      Where I live, commercial establishments usually have outward opening doors for the safety of the large number of people that might need to exit in an emergency; whereas residential doors will have inward opening doors so that the hinges are not exposed.

      I believe there's a federal law to build public buildings doors so that they open outwards because of the fire in Chicago theater from the early 20th century when lots of people died jammed at the entrance/exit doors trying to get out...

    113. Re:Linus by causality · · Score: 1

      your statement still means that great programmers give everyone else a hard time

      Alright, I'll rephrase: great programmers think they're slightly above average, and they don't understand why other people can't solve problems that easily.

      They won't say "use this algorithm because I'm the greatest". They'll say "use this because it's 20% faster and only uses half the memory". And if they're wrong, they're smart enough to realize it.

      I don't think this is specific to programming at all.

      If you are really good at something, it's because you did not give up easily and were willing to test your own boundaries and limits, to see what you are capable of and to reject self-imposed limitations. In its purest form, you do this not to impress anyone, but because you value excellence and because you want to explore your own capabilities. When you can do this for one thing, you are presented with the question of why the majority of people don't do this in the areas where they are talented, why they are content with mediocrity and why they seldom deviate from the path of least resistance.

      If you really look into the issue, my personal belief is that you will be forced to conclude that other people certainly could do this. That they could means this is not about inherent superiority, clearly showing the error of arrogance. Those other people just don't care to; they are choosing not to though this may not be a deliberate, conscious choice. Instead of a joy of discovery and a worthy challenge, or even a sense of adventure and exploration, they just see extra effort and they decide it isn't worthwhile.

      I think that what makes the difference is that those who value excellence really love what they are doing. The others just do what they do for a paycheck, or for status, or so others think they're a great guy or a hard worker. I believe that not only does the former approach produce better tangible results, it also contributes to a joyful outlook and removes much of the toil from things that do involve a great deal of effort. Effort doesn't feel so much like work when you are grateful that you get to do something like this.

      --
      It is a miracle that curiosity survives formal education. - Einstein
    114. Re:Linus by akintayo · · Score: 1

      Doors that open outward will not work well when walls are opaque. If there is a corridor with foot traffic, it will not be safe to open the door if you cannot see if anyone is passing by. For obvious reasons.

      --
      Woe be on to them, all who rise against poor people, shall perish in a the end. Buju Banton
    115. Re:Linus by pbhj · · Score: 1

      Also, doors should be always pulled when you go in and pushed when you go out.

      Because everyone likes to be smashed in the face with a door when they walk down the corridor or along a pavement?

      If your main door pushes out (probably applies to student accommodation most!) you can't barricade it but you can be stockaded in.

      Pushing with a handle is more comfortable as it allows for more natural rotation of the wrist, particularly with heavier doors.

      You can pull the door to as well [to too!] if it has a handle on the pushed side, plus you can usually use the handles to secure a pair of doors closed (eg with rope or a plank).

    116. Re:Linus by Anonymous Coward · · Score: 0

      I'm curious how this applies to dating. If someone acts seemingly confident asking someone out, isn't probable that they just don't know the scope of their deficiencies?

    117. Re:Linus by pbhj · · Score: 1

      Cox -> Takes his ball and goes home, except in this case, it is OSS so he doesn't really take any ball with him. He just leaves.

      He leaves us his ball to play with.

      Saying "takes his ball and goes home" suggests an immature solution to conflict in which the offended party prevents the offender from continuing to play - Cox isn't stopping anyone from benefiting from his work in the past, is he?

    118. Re:Linus by dbIII · · Score: 1

      With respect, Con didn't even run the platform and he collected patches from others which he did not entirely understand what each did. The drama unfolded because Con as a professional expected his word to be taken as more than a newbie in a different feild to his profession. I think the main criticism is that because he didn't run linux as his working platform he wouldn't really know if those patches submitted to him (and some modified by him) really ran as intended over time - the "chef has to taste their own cooking" argument.
      Thus, we ended up with a storm in a teacup when a guy that could see a small part of the design ranted at the guys that had been working on the design for years for being too conservative. Meanwhile those others thought he was taking a bit too much of a cowboy approach with delicate parts.

    119. Re:Linus by Anonymous Coward · · Score: 0

      I completely disagree with what you said, unless you mean 'Experimental' code in the kernel, then yeah, that's a Linux thing to have in production.

      Otherwise, I find most non-desktop drivers to be much better in OpenBSD and FreeBSD than Linux. Especially non-binary, closed sources, proprietary, NDA drivers that Linux fragments into it's kernel... Linux is not really OSS friendly anymore.

    120. Re:Linus by petermgreen · · Score: 1

      For interior doors opening outwards means they end up partially or even completely blocking the corridor.

      There is also possiblly a security/weatherproofing aspect to consider which is that the cracks arround a door are generally open to the side the door opens towards. On the other hand a door that opens inwards is probablly easier to open by brute force so maybe it balances out.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    121. Re:Linus by severoon · · Score: 3, Interesting

      Agree 100%. Something as simple as a door should not require an instruction manual, even if it is a single word ("push" or "pull"). A good designer ought to be able to design any device as simple as a door so that it is easy to use correctly and difficult to use incorrectly, even for users that are minimally observant.

      I recently thought about this when I entered a bathroom stall, and the flip lever near the top of the stall door had a coat hook on it as well. When the stall door was unlocked, the coat hook was up against the stall divider and impossible to use. When it was locked from the inside, the coat hook was available for use. Furthermore, if you did decide to hang something on it such as a coat, a purse, even a key, it would take actual effort to ignore the item as you tried to exit the stall. Simple, straightforward design that is functional and eliminates the possibility of leaving an item behind.

      (Unfortunately, the toilet paper dispenser gave one lone, see-thru, single-ply sheet at a time and was positioned behind your left ankle. wtf.)

      --
      but have you considered the following argument: shut up.
    122. Re:Linus by Jstlook · · Score: 1

      Don't let your head swell so much you can't get through the door. We all have these moments, I call them moron moments, where we will do truly stupid things. Using myself as an example: I have a (Tested) IQ of 151, and just this morning, I found myself pulling on a door clearly marked Push.

      See myself, I just delight in putting Stickers labeled 'Push' on doors that must be pulled to open. I also enjoy emptying the ballpoint pens found in banks of ink, and taking eleven items to the nine items or less grocery line. While I readily admit that reality is pretty straightforward, I think people who stop questioning even the most basic tenets of reality will never accomplish anything of value.

      --
      ---jstlook ---For that is the way of Elves, for they say both yes AND no, and mean every word of it. --- J.R.R.T.
    123. Re:Linus by Lemming+Mark · · Score: 1

      Linus is brilliant. He is funny. Most days I really agree with anything he has to say.

      However, he has butted heads with people in the past. Perhaps this is just human nature and unavoidable from time to time. Linus isn't perfect, nor always right. I thought he was really unfair to Con Kolivas when he drove Con away.

      I remember the mess with Con Kolivas resulting from something vaguely similar: Con was saying that, no, the correct place to fix the problem at hand was in userspace not the scheduler. Linus went a bit crazy and said that Con was refusing to admit a bug existed and that he therefore had the wrong attitude. Fast forward to this discussion with Alan Cox and it comes down to Linus going off the deep end over a discussion about where a bug is.

      OK, so it takes strong leadership to keep a big project on track and Linus has had to take a tough line on ABI stuff (and various other things that make life harder for developers) from time-to-time. Usually he's extremely level-headed and pragmatic but every so often he seems to cross the line a bit. But as you say, he's doing a tough job managing lots of people - and he does it all in public for us to scrutinize. He does very well. But in this instance (ditto the incident with CK) he's being unexpectedly unreasonable.

    124. Re:Linus by shutdown+-p+now · · Score: 1

      Curiously enough, a lot of people actually mean "graphics driver support" when they speak of driver support in general.

    125. Re:Linus by severoon · · Score: 5, Funny

      Let me take a shot at summarizing the summary...

      cox: have sum code lol!!!

      user: ur kung fu is weak my pooter crashed and it's all ur fault lame! :-/

      cox: i feex! i feex! -starts furiously working-

      A hush falls over the land, just then...

      linus: RAWR! I SMASH!!! -flames shoot out of every orifice; a baby is heard crying in the distance-

      cox: zOMG!!! -fills pants; amazingly, continues working furiously to "feex"-

      linus: BRAWR! YOUR SLAVISH DEVOTION TO OTHERS ANGERS ME forabsolutelynoreason BRAWR!!!

      user: wtf.

      cox: -terrified of linus-beast, with singed eyebrow hairs- I leev! -boogies out, stage left-

      bill gates (barely visible in background, deep stage right): -twirls mustachio-

      all users: srsly, wtf.

      me: -bows-

      --
      but have you considered the following argument: shut up.
    126. Re:Linus by machine321 · · Score: 2, Informative

      BSD has terrible driver support compared to Linux.

      Wrong. BSD has excellent driver support, but doesn't allow in binary-only black-box drivers nobody can maintain. Instead the developers reverse-engineer the hardware and make drivers anyone can maintain.

      I checked this with Netcraft, and they confirmed it.

    127. Re:Linus by Grishnakh · · Score: 1

      Examples?

    128. Re:Linus by Enderandrew · · Score: 1

      If you're not careful, Michael Bay will use that as the script for Transformers 3.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    129. Re:Linus by rliden · · Score: 1

      I've seen that before. Why can't the guy just say, "Hey! Okay, I was wrong. Do you have to be such a prick about it?"

      --
      Don't think of it as a flame, more like an argument that does 3d6 fire damage.
    130. Re:Linus by imgumbydammit · · Score: 1

      Don't you get a swollen head when you walk amongst dullards?
      No. I just get tired.

      --
      That's right: I'm gumby dammit.
    131. Re:Linus by rs79 · · Score: 1

      "Why not Amiga OS?"

      Guru meditation errors, that's why not.

      --
      Need Mercedes parts ?
    132. Re:Linus by AtariKee · · Score: 1
      --
      "You're getting brutal, Sark. Brutal and needlessly sadistic."
      "Thank you, Master Control"
      -Sark and the MCP
    133. Re:Linus by Anonymous Coward · · Score: 0

      "Also, doors should be always pulled when you go in and pushed when you go out."

      Always? A door that opens out is easier to block from the outside. It also usually means putting the hinges on the outside.

    134. Re:Linus by rs79 · · Score: 1

      " Bullshit. The best programmers don't know if they're awesome. They just think everyone else is stupid."

      Consider this: if you're of perfectly average intelligence then half the world is more stupid than you.

      If you're in the top 1% of programming prowess, then, by definition, pretty much everybody else is stupid.

      Q.E.D.

      --
      Need Mercedes parts ?
    135. Re:Linus by Anonymous Coward · · Score: 0

      No, *thinking* you're smarter than those around you leads to ego issues.

      Actually being smarter / more knowledgeable means you have no one to ask when you've run into a wall.

      I don't think I'm smarter than my coworkers-- I'm just more determined to solve the problem.

    136. Re:Linus by martin-boundary · · Score: 1

      Linus is brilliant. He is funny. Linus isn't perfect, nor always right.

      How fucking dare anyone out there make fun of Linus after all he has been through.!

      He lost his Bitkeeper, he went through a Transmeta. He had two fuckin desktops.

      HE'S A HUMAN! What you don't realize is that Linus is making you all this money and all you do is write a bunch of crap about him.

      LEAVE HIM ALONE! You are lucky he even performed for you BASTARDS! LEAVE LINUS ALONE! ..Please.

      Speaking of professionalism, when is it professional to publicly bash someone who is going through a hard time.

      Leave Linus Alone Please . ! Leave Linus Torvalds alone! right now! .I mean it.!

      Anyone that has a problem with him you deal with me, because he is not well right now.

      LEAVE HIM ALONE!

    137. Re:Linus by kfhickel · · Score: 1

      Bullshit. The best programmers don't know if they're awesome. They just think everyone else is stupid.

      Heh, then I MUST be F***ING BRILLIANT!

      -Me

    138. Re:Linus by kjs3 · · Score: 1

      > The quality of a programmer is often proportional to his ego. Bullshit, and irrelevant for programming teams of more than one person. For every Theo De Raadt, et. al., there are dozens of senior folks who've delivered large scale, sophisticated, quality, widely used software projects that didn't feel that it was their personal prerogative to shit mercilessly on any contributor who they decided to abuse that day. My life became vastly easier and much more successful when I quit believing the hype that you had to put up with the self-absorbed, egomaniacal, abusive, "superstars" to do great work. I figured out that there were really large numbers of supremely competent, team-oriented, consummate professionals that were more interested in getting the job done well than their own personal ideology to the detriment of those around them. I got rid of the prima donnas and hired guys with a track record of leading teams to success. They delivered; got the projects done. Noone had to beg them for deliverables, documentation or to treat others as human. The bonus was that the professionals (unlike the "superstars"), would actually spend time mentoring the "stupid" junior folks instead of shitting on them, turning them into competent professionals and the next generation of solid developers. A culture of success evolves. If it suits your personality be rewarded with "I'm recognized because I put up with the most crap from the more recognized names", good for you. But recognize there's a bunch of folks, just as "quality", who said "I don't need this" and found real, supportive teams to work on.

    139. Re:Linus by Anonymous Coward · · Score: 0

      Damn straight. Drives me bananas when I see doors designed by morons.

    140. Re:Linus by Crunchie+Frog · · Score: 1

      Does it make me shallow that I found this post profound and fascinating?

      --
      --- Never attribute to malice that which can be adequately explained by stupidity
    141. Re:Linus by lennier · · Score: 1

      "> I found myself pulling on a door clearly marked Push."

      It's even worse in Brazil. Doors are clearly labeled 'Push' and Pull' in Portuguese... ... but the Portuguese word for 'pull' is 'puxe', pronounced 'push'.

      Gringo entering Brazil == immediate 50 pt IQ drain!

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    142. Re:Linus by iluvcapra · · Score: 1

      I think you're missing the post I'm responding to. And, do yourself a favor and take deep breaths while typing.

      --
      Don't blame me, I voted for Baltar.
    143. Re:Linus by Anonymous Coward · · Score: 0

      This man speaks the truth. May his words be heed.

    144. Re:Linus by Dirtside · · Score: 2, Insightful

      whereas residential doors will have inward opening doors so that the hinges are not exposed.

      ...and also so that it's easier to break the door down from the outside in case of fire or police emergency. This is not a coincidence.

      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
    145. Re:Linus by Mr.+Roadkill · · Score: 1

      That is actually just an UI bug in the door. If you want people to push a door, you should use a handle that is like a plate, where you can easily put your hand against and push it. If you want people to pull the door open, you need to use vertical rod as a handle, where people can easily grab on to pull it. With this very small change, you don't even need to push/pull texts on the doors.

      Not necessarily a bug...it's a feature that the user doesn't know how to use properly, much like the much maligned "Any" key. If you're inside an outward-opening door that has a pull handle on the inside rather than a plate, you can pull on it to stop others getting in. If there's a double-set of such doors, you could slide a pair of skis or a cricket bat or some other object through them so you won't need to stand there holding them shut to stop people getting in. Whether the door is on your side of its jamb or the other, or the positioning of other hardware like automatic closers, gives the user sufficient cues to indicate the opening direction. You also get reduced building complexity by being able to re-use a single kind of handle instead of having to have two differernt ones. Don't blame the implementation for the fact that the user isn't up to understanding the advanced options or the context in which the function is being used.

    146. Re:Linus by Anonymous Coward · · Score: 0

      Forking means divergence of drivers and you will have more and more trouble keeping up with linux driver developments.

      Trust me, I know. (BSD project fork)

    147. Re:Linus by sarkeizen · · Score: 2, Insightful

      Something Feynman said about working with "Monster Minds". The story goes that he's working on a lecture and progressively it gets revealed that some really important people (in physics and math) are going to show - including Einstein. So he starts worrying about what to do if these people start asking questions. Pauli is the first to stand up and say why he thinks the theory Feynman is presenting is wrong and ending with "Don't you agree Professor Einstein?". Einstein essentially says that the only problem he can see is that it doesn't agree with his theory about relativity but that's okay since there isn't much experimental evidence to support his theory.

      This story has stuck with me about how criticism of ideas and especially criticism of ones own ideas are the hallmarks of the very intelligent. That said...any idea of this kind is bound by the "tyranny of small sample" ;-) Still I like it as a rule of thumb.

    148. Re:Linus by raddan · · Score: 1

      Ah, good insight. That makes a lot of sense. And by "graphics drivers", they probably don't mean "any ol' driver that will work" but "accelerated drivers".

      I never really demand much from my graphics hardware (I'd say that 95% of the OpenBSD machines I set up don't run X... some don't even have graphics capability), so I would have never thought of this.

    149. Re:Linus by Grishnakh · · Score: 1

      I'm not so sure about that. It really depends on what you change in your fork.

      For instance, if you don't have a problem with Linux's drivers and don't want to make any changes there or in its driver subsystems, then the drivers should all stay the same and you shouldn't have any trouble just applying the same patches.

      I imagine that if someone really wanted to fork the Linux kernel, the things they'd want to change might be 1) the scheduler(s), and 2) the audio subsystem (i.e., ALSO -> OSS). Other than people complaining about binary code in drivers, I haven't seen anyone complain about the driver subsystems themselves. If you don't like the binary-blob drivers, it's simple enough to just leave those out.

    150. Re:Linus by Anonymous Coward · · Score: 0

      Those doors have always been a bit buggy.

    151. Re:Linus by Grishnakh · · Score: 1

      What binary-only black-box drivers are you talking about, that are actually part of the Linux kernel? I've never heard of any.

    152. Re:Linus by Dash-o-Salt · · Score: 1

      These days all businesses are required to have doors that open outward, primarily due to the Cocoanut Grove fire way back in 1942, which killed 492 people.

      Effectively what occurred is many of the exit signs were obscured, and there were no doors that opened outward. This caused massive traffic jams as people futilely attempted to escape the fire.

      Quite a sad story.

      Here's the wikipedia link:

      http://en.wikipedia.org/wiki/Cocoanut_Grove_fire

      Here's an example of such a law from the Oregon state fire code: https://www.oregonlaws.org/ors/479.150.html

    153. Re:Linus by speedtux · · Score: 1

      Why would it make any difference to me whether Linus is a nice person? I can't stand the guy myself. But as long as Linux is open source and gets the job done, it can be developed by Jesse Helms and Michael Vick for all I care.

    154. Re:Linus by Anonymous Coward · · Score: 0

      The only driver issue that's ever irked me there were USB-serial adapters.

      ...and to be fair, those are a bitch regardless of what OS you're using.

    155. Re:Linus by twistedcubic · · Score: 1

      The difference between Theo and Linus, is that Theo will call you a dick if you're acting like a dick, but Linus will call you a dick if you politely disagree with him.

    156. Re:Linus by Anonymous Coward · · Score: 0

      Ubuntu didn't really do anything to the kernel (ie drivers) more than any other distro, and especially not Debian. They added some better detection and cleaned up packages for closed binary drivers, such as those needed for some wireless cards and graphics cards, but, hardware wise, one distro generally isn't any better than another unless one is using a newer kernel.

    157. Re:Linus by Anonymous Coward · · Score: 0

      It's Alan cox: there is no experience or expertiese issue at all. Really, no way to confuse cockines with plain raw mean hacker. It's hard to imagine, or I didn't follow up through enough, what drove Linus to that point where he would publicaly have this kind of rant.

    158. Re:Linus by Anonymous Coward · · Score: 0

      Yeah, and all doorknobs should be on the left.

    159. Re:Linus by Meumeu · · Score: 1

      I've always described this effect with the axiom, "People who feel the need to call themselves experts rarely are. The same can be said for those who call themselves professionals." I'm glad somebody finally got around to studying this effect and giving it a name.

      ob. link

    160. Re:Linus by Anonymous Coward · · Score: 0

      Fact: OpenBSD is dying.

      Get over it; Grow up; Move on.

    161. Re:Linus by dubl-u · · Score: 1

      (like dumping ALSA and moving back to the new OSS).

      Speaking of which, what is up with Linux sound? I'm just an OS consumer these days, so normally I don't bitch about Linux issues. But for years sound has been at best a bit wonky, and often entirely fucked. And that's on mainstream hardware.

      I ask because it sounds like you know some of the story.

    162. Re:Linus by Anonymous Coward · · Score: 1, Funny

      > Also, doors should be always pulled when you go in and pushed when you go out.

      It's fools like you that'll be the death of us all when the zombie apocalypse arrives and everyone jams the doors running *into* malls.

    163. Re:Linus by dubl-u · · Score: 1

      As if he'd use a script. I hear his plan is just to take prints of all his previous movies, blow them up with a lot of C4, and then take the frames that flutter down as the initial storyboards. Kind of like trusting to God, but Michael Bay believes only in Michael Bay.

    164. Re:Linus by blue+trane · · Score: 1

      Socrates was the first or among the first to place a strong emphasis on definitions, which laid the foundations for formal languages.

    165. Re:Linus by Anonymous Coward · · Score: 0

      It's arguably the best psychological test for intelligence we have. I don't want to be an asshole, but I tend to think that people such as yourself have ulterior motives for your postulation: namely you're dealing with the cognitive dissonance you experienced when you scored low on the IQ test...

    166. Re:Linus by pearl298 · · Score: 1

      I think the level of discussion and explanation needed in what is really a very simple problem serves to illustrate why people have such a lot of problems with more complex problems!

      Add in some emotions like frustration and impatience and you have a ticking time bomb.

      Defused more than a few of those and missed a few as well, haven't we all?

    167. Re:Linus by Anonymous Coward · · Score: 0

      Hahaha you had me going for a minute there

      Clearly you have never tried wireless drivers in BSD.

      BSD belongs in the stone age

      You're welcome!

    168. Re:Linus by Anonymous Coward · · Score: 0

      Linus made it clear he didn't want Con's code, and Con didn't take "no" for an answer and kept trying to prove that his code was superior. That's primarily a problem with Con, not with Linus.

    169. Re:Linus by Edmund+Blackadder · · Score: 1

      Let me guess ... it was one of those internet IQ tests, wasn't it?

    170. Re:Linus by Edmund+Blackadder · · Score: 1

      A lot of modern office buildings have higher air pressure inside the building than the air pressure of the outside air. This is done to keep outside smells out of the building and to ensure higher AC efficiency by preventing hot outside air from coming in.

      Thus, if the doors push open to the outside, the higher inside air pressure may just open the doors by itself, which would not be desirable.

      Furthermore, a lot of office building doors open on busy walkable streets (imagine manhattan offices, for example). If the doors push to the outside there you can easily hit a pedestrian in the face with an opening door.

      So things are not that simple.

    171. Re:Linus by Anonymous Coward · · Score: 0

      Also, doors should be always pulled when you go in and pushed when you go out. That makes exiting the building easier in case of emergency (people don't rush to the door and jam it, preventing anyone from pulling it open.)

      You assume here that in case of emergency, people always want t rush outside, but what of bears?

    172. Re:Linus by Anonymous Coward · · Score: 0

      Im so swollen right now because I found a mistake in you're use of apostrophe's!

    173. Re:Linus by Andrei+D · · Score: 1

      This seems to be influenced by Socrates, the Greek philosopher, the one who first said I know that I know nothing..

      --
      We often refuse to accept an idea merely because the tone of voice in which it has been expressed is unsympathetic to us
    174. Re:Linus by Eivind · · Score: 1

      You're right. The sensible thing to do, when you notice the one you're debating with has changed his position is offering him a way out. That assumes you notice it in the first place, offcourse.

    175. Re:Linus by Anonymous Coward · · Score: 0

      Actually, it's exactly the opposite. Porting a driver is something you do once. Keeping up with the wild stream of patches, on the other hand, is something that can take lots of time. That's one of the problems companies have with Linux - it takes lots of manhours to stay up to date. In case of BSD, it's much easier.

      Also, the driver support is much more complicated. For example, FreeBSD sound subsystem has features Linux ALSA doesn't have and probably won't have, like per-channel volume control and resampling, without the need for another layer in userland.

    176. Re:Linus by kamochan · · Score: 1

      The original version? 100%. The current version? Significantly less.

    177. Re:Linus by Anonymous Coward · · Score: 0

      I have a (Tested) IQ of 151, and just this morning, I found myself pulling on a door clearly marked Push.

      I have an (untested) IQ of above 200, and I never pull a push door.

    178. Re:Linus by 5of0 · · Score: 1

      I patched this bug at my school once. They had handles on both sides of the one-way doors in the lounge. Early one morning, I took a screwdriver to them and removed the "pull" handles, stashing them in my room. No one (including security/maintenance) noticed for a few weeks, or if they did, they were pleased by it. The general consensus was basically good riddins. Eventually though, security noticed (and started banging on the remaining handles with their maglites, as if it would do anything). I got fined, and my patch was reverted. Some people just don't understand.

      --
      You all have Oo.o and Firefox, so get World Wind.
    179. Re:Linus by Anonymous Coward · · Score: 0

      Con actually put up a scheduler related patch last month, though he placed it in the crap category:

      sched-weight-io.patch

      I was hoping that he will come back and fix bug 12309, i.e. the bug that appeared on slashdot 6 months ago and still has no resolution. However, after reading this, I will just wait for FreeBSD 8 and make the switch.

    180. Re:Linus by Anonymous Coward · · Score: 0

      It is very well correlated yes. True, no one can really tell how I.Q. works, and it's also true that correlation is not causation.

      But check the correlation between I.Q. and jail-time, I.Q. and salery/wage, I.Q. and education level, I think it's beyond a boubt that high I.Q. makes it easier to "succeed" in society.

    181. Re:Linus by Brownstar · · Score: 1

      > Also, doors should be always pulled when you go in and pushed when you go out.

      Depends where you live.

      If you live in climates that have heavy snowfall, and your door only opens out, you're probably going to get locked in on occasion.

    182. Re:Linus by Anonymous Coward · · Score: 0

      As already mentioned in The Apology of Socrates by Platon. Some things fundamentally never do change

    183. Re:Linus by jimicus · · Score: 1

      Certainly in most businesses that's the case because most businesses don't want to hire people and then tell them exactly what to do. They want to hire people with whom they can discuss what the business needs, thrash out an appropriate solution and then those people they've hired go off and do it.

      (On a side note, I recently interviewed at a company and a question I asked was "what's the business driver for this team?". I was rather surprised to find that the manager interviewing me didn't know.)

    184. Re:Linus by smash · · Score: 1
      At the end of the day, that point is irrelevant. If people can not be easily sourced to maintain it, it is unmaintainable. OR, alternatively; you are stuck as the sole maintainer for the life of the product. Some may call that job security. I call it a pain in the arse; maintenance is boring, playing with new stuff is where it's at.

      A *good* coder will ensure that the code is sufficiently documented so that it is easier to follow.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    185. Re:Linus by smash · · Score: 1

      Any idea how much that rises to when you strip out the drivers? Or is that only counting the kernel core, not hardware drivers?

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    186. Re:Linus by smash · · Score: 1
      I have, and had wireless working before I had it working on Linux.

      In any case, the "project evil" stuff for BSD allows use of NDIS windows drivers via a wrapper.

      Any more misinformed bullshit about BSD to post up?

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    187. Re:Linus by drizek · · Score: 1

      Theres this one door that has a pull sign that actually goes both ways. One day I went, pushed it like usual, and it didn't open. It was locked and I started to walk away, but some guy behind me came and pulled it really hard while looking in my general direction; didn't open for him either, and he just stood there looking like a douche.

    188. Re:Linus by hab136 · · Score: 1

      I had a boss who phrased this during my (positive) performance review as "it's not that you're that great, it's that everyone else sucks".

    189. Re:Linus by Anonymous Coward · · Score: 0

      In that environment removing the snow shouldn't be neglected, otherwise even getting to the door won't be easy.

    190. Re:Linus by dominious · · Score: 4, Informative

      In case you haven't noticed IQ is the acronym for Intelligence Quotient and the mean score 100 is the mean of the Normal Distribution for a large enough population.

      Personally, that tells me something!

    191. Re:Linus by Cosmic+AC · · Score: 1

      If you think IQ isn't related to intelligence, then it shouldn't matter what his IQ is.

    192. Re:Linus by Anonymous Coward · · Score: 0

      cbatli, but your statement made me think.

      If IQ is not related to intelligence, why would he be more likely to realize it if his IQ is 151?

    193. Re:Linus by Anonymous Coward · · Score: 0

      Hans Reiser abandoned reiser4 for, uhm, non-technical reasons

    194. Re:Linus by Anonymous Coward · · Score: 0

      Or that intelligence is related to usefulness or value? :-)

    195. Re:Linus by Anonymous Coward · · Score: 0

      hired!

    196. Re:Linus by Anonymous Coward · · Score: 1, Interesting

      and what does the "I" stand for, moron

    197. Re:Linus by SoupIsGood+Food · · Score: 1

      Don't you get a swollen head when you walk amongst dullards? Every time I see somebody pushing at the 'pull' on a door, I feel my disdain for others rising. When I stand behind a dunce in line, and hear him ask how many eggs in a dozen, I grow more sure of my position among the intellectual greats. When a waiter is unable to figure sums on his pad to give me a total, that I might reimburse him fairly for his service, I scoff at the fools that populate this world.

      Dunno. I usually look at it as an opportunity to be helpful. I usually reserve my snarling, sneering rage for those who are about as smart as I am, but refuse to think a problem through. It feels good to help someone figure out something new, or remember something they have forgotten, like how many eggs in a dozen... but it feels just as good to leave someone a gibbering, sniveling wreck after crossing swords over which BSD would make the best foundation for a small-scale web-app server. Ego is its own reward. I mean, don't start none, and there won't be none, but if you decide to bring it, you better bring it by the bucket, all I'm saying.

    198. Re:Linus by Anonymous Coward · · Score: 1, Interesting

      and you don't think IQ is related to intelligence?
      It might not be a good measure of intelligence, but it is surely related to it.

    199. Re:Linus by TheRaven64 · · Score: 1

      Does FreeBSD even have any 3D video drivers for Nvidia or AMD?

      All three of the major BSDs have a DRI implementation, so run exactly the same X.org drivers as Linux. In terms of proprietary drivers, nVidia has been shipping drivers for FreeBSD and Solaris for several years, using the same code with slightly different kernel shims as the Linux driver.

      A number of WiFi drivers that were recently added to Linux are based on code from OpenBSD which was ported to FreeBSD and NetBSD a year before Linux got support.

      I tried running Linux on my ThinkPad a little while ago. It had no support for the WiFi card (although, apparently, if I went to some third-party site, I could get a tarball that I could then compile to a kernel module that may or may not work with my kernel) and occasionally the trackpoint would go crazy in X and shoot to the corner of the screen clicking a large number of times per second, then become sane again after about 5 seconds. Sleep mode caused the machine to sleep and never wake. I installed FreeBSD on it and everything worked correctly, including proper suspend / resume.

      So, nice troll. Keep up the cognitive dissonance.

      --
      I am TheRaven on Soylent News
    200. Re:Linus by TheRaven64 · · Score: 1

      But on desktops, unless you have some kind of counter-argument for the fact that FreeBSD doesn't have any 3D drivers

      Here are two arguments:

      First, FreeBSD has a full DRI implementation, and has proprietary drivers from nVidia. I've run FreeBSD with hardware acceleration using ATi, Intel, nVidia, and Matrox cards (although the Matrox one barely counted as acceleration).

      Second, sound actually works on FreeBSD. The OSS implementation support software sound mixing if the hardware doesn't support it, so you get multiple applications playing sounds without having to mess around with the sound daemon de jour.

      --
      I am TheRaven on Soylent News
    201. Re:Linus by gnugnugnu · · Score: 2, Funny

      >> I found myself pulling on a door clearly marked Push.

      > That is actually just an UI bug in the door.

      I found myself trying to lift a door clearly marked LIFT.

    202. Re:Linus by Anonymous Coward · · Score: 0

      Quote from Idiocracy:

      Rita: You think Einstein walked thinkin' everyone was bunch of dumb shits?

    203. Re:Linus by BobMcD · · Score: 1

      Linus won the technical battle, but wasn't satisfied at Cox's capitulation. Cox wanted to lose the argument with grace, Linus wouldn't let him.

      Someone else said this to me the other day, but I find it fitting:

      The times when a person needs patience and understanding the most, are often those when they deserve it the least.

      It seems to me that Linus might make a better leader if he'd just learn to recognize these times and forgo the battle to win the war.

      Not that I fault him specifically. Few, if any, people are good at doing this all the time.

    204. Re:Linus by BobMcD · · Score: 1

      The ability to score well on a given test is not NECESSARILY the ONLY indicator of intellect. Human minds are complex things. It would be impossible to create even the largest battery of tests to truly, fully measure their capabilities.

    205. Re:Linus by thePowerOfGrayskull · · Score: 1

      I'm tired of that silly myth.

      The best programmers I have met were nice people and they were very easy to get along with and work with.

      It's all part of the ego trip. If a programmer gets people to say "He's such a nice guy! And talented too!" he goes into nerdgasms.

    206. Re:Linus by ukyoCE · · Score: 1

      Absolutely not.

    207. Re:Linus by BitZtream · · Score: 1

      Jesus christ, thats one of the most well thought out responses I've seen to an engineering/UI issue. I generally find myself feeling the same way as the GP, but seeing this sort of response puts me back in my place. I wish I was lucky enough to work around more people with that sort of attention to detail and knowledge.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    208. Re:Linus by Anonymous Coward · · Score: 0

      And some of us DO boycott anything and everything GNU because of Stallman.

    209. Re:Linus by mikael · · Score: 1

      Those giant wheel dispensers of toilet paper are probably the most annoying. You have spin the wheel in two directions to figure out whether the roll of paper has been installed clockwise or anticlockwise by the cleaner/janitor.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    210. Re:Linus by TheWanderingHermit · · Score: 1

      My experience is that many of the woman I've gone out with that exhibit an abundance of self confidence may do well professionally or in their hobbies, but often are a mess personally. Even more, I find that they may show a lot of self confidence in the first few dates, but once you get past that, they're quite insecure and just hiding it.

    211. Re:Linus by skeeto · · Score: 1

      BSD has terrible driver support compared to Linux.

      My experience has been exactly the opposite.

      Especially for wireless card drivers! That's something OpenBSD does really well, and they seem to work right out of the box. Linux usually takes a bit of work. I find this funny because an OpenBSD system, being less flexible as a desktop or laptop, is much less likely to need a wireless card than a Linux system.

    212. Re:Linus by afidel · · Score: 1

      This is my favorite test taking shirt for that exact reason =)

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    213. Re:Linus by Anonymous Coward · · Score: 0

      I want to use the OS that Con maintains, not the other one. Where can I find that?

    214. Re:Linus by caerwyn · · Score: 1

      Of course. But *he* clearly does. I found the contradiction amusing.

      --
      The ringing of the division bell has begun... -PF
    215. Re:Linus by caerwyn · · Score: 1

      Yeah. I know what the test is. I've tested a 163.

      I still think it's complete bunk. Have you *taken* the test? Hell, there are parts on the test that measure hand-eye coordination more than anything else. Hope you didn't have enough coffee to make your hand shake that day...

      --
      The ringing of the division bell has begun... -PF
    216. Re:Linus by Anonymous Coward · · Score: 0

      Like him or not, Linus is still the man in linux kernel development circles, and for good reason.

      And these reasons are...?

    217. Re:Linus by Killotron · · Score: 1

      Your door would suffer from issues if installed in an environment where it snows a lot.

      Only if the damn neighborhood kids forget to shovel the walk.

    218. Re:Linus by Ixpath · · Score: 1

      How very lucky we are that there is a continuous bijection mapping "intelligence" to the positive reals and not R2.

    219. Re:Linus by severoon · · Score: 1

      Yes, you should always offer a way out. Otherwise, how can you guarantee that they'll do it again next time? And if they don't do it again next time, your show goes off the air and the only way people can get their Three's Company fix is to get it on DVD.

      --
      but have you considered the following argument: shut up.
    220. Re:Linus by ifknot · · Score: 1

      This behaviour is common to all organizations, and commonly results in pathology within the team. What is uncommon is the open nature of Linux kernel development results in the internal dialogue being public & recorded. This level of transparency and raw material is interesting and potentially powerful. What seems to be missing is some mechanism to harness it through a reflective feedback process. Has it been considered? The self organizing nature of open source developement is powerful but not immune. I also note that given '80% of the kernel development' goes through Linus, despite his 2% actual contribution, the kernel development is, therefore, very brittle. Being vulnerable not only to the 'hit-by-bus' effect but simply to the emotional whims of the conduit of that 80% - as exampled by Conus & Cox.

      --
      we are all cosmic nuclear waste
    221. Re:Linus by Talennor · · Score: 1

      A tested IQ of 151... and you think IQ is related to intelligence?

      His counterexample to IQ==intelligence (the entire post you replied to, I don't know how you missed it) didn't give away what he thinks?

      --

      //TODO: signature
    222. Re:Linus by dominious · · Score: 1

      I agree that it's not the ONLY indicator of intelligence, but what im saying is that the scores are not bogus, an IQ test is adjusted so most people can score 100. From that you can reason about something.

      For example if I want to draw a formula on a graph, how would I represent it? Is it going to be human readable? I could gather 100 people and see if they understand it, I would draw it in such a way such that most people can understand it. And that's an indicator of how people understand graphs so I can go on and use it (i.e. as a standard way of representing formulas)

      Understanding spacial or temporal events and able to coordinate or reason about is indeed one form of intelligent behaviour.

    223. Re:Linus by Anonymous Coward · · Score: 0

      Hmm,

      Going from "I am smart at this and that" to "I am great and worthy in all respects" is an interesting conclusion. It may not be the smartest conclusion - perhaps it's the kind of conclusion a BASIC programmer would make...

    224. Re:Linus by Joe+Snipe · · Score: 1

      It wasn't so much the nice person part, it was the blocking the use of good code.

      --
      Sometimes, life itself is sarcasm...
    225. Re:Linus by caerwyn · · Score: 1

      You've never heard of a rhetorical question?

      --
      The ringing of the division bell has begun... -PF
    226. Re:Linus by caerwyn · · Score: 1

      That's not necessarily a correlation with intelligence, though. I can't quote sources at the moment (don't feel like looking them back up), but there's a strong argument that a good portion of the IQ test involves things that are really *knowledge*, not intelligence.

      If true, that would explain all the correlations you mention without requiring the IQ test to actually be correlated with *intelligence*.

      --
      The ringing of the division bell has begun... -PF
    227. Re:Linus by ciderVisor · · Score: 1

      It's not often I genuinely 'Laugh Out Loud' at a Slashdot post but that my friend was an epic ! +6 Funny

      --
      Squirrel!
    228. Re:Linus by buster_dog · · Score: 1

      Seems like Slashdot is full of the Best Programmers!"

    229. Re:Linus by manifoldronin · · Score: 1

      Consider this: if you're of perfectly median intelligence then half the world is more stupid than you.

      If you're in the top 1% of programming prowess, then, by definition, pretty much everybody else is stupid.

      Q.E.D.

      That better?

      --
      Tyranny isn't the worst enemy of a democracy. Cynicism is.
    230. Re:Linus by Anonymous Coward · · Score: 0

      Also, doors should be always pulled when you go in and pushed when you go out. That makes exiting the building easier in case of emergency (people don't rush to the door and jam it, preventing anyone from pulling it open.) and also when people are trying to get in and out at the same time, the person outside is more capable of keeping the door open for the person going out (it is better that people first get out, before new people get in, because inside there is a limited space, while outside contains usually a lot more room). Also outside usually contains more room for pulling, while the inside often has a wall that limits the space for pulling, especially if you want to keep the door open for someone else.

      Building doors opening outward is part of the building code for many types of commercial buildings, so it's no longer a design choice. And the lesson was learned because people got killed when a building needed to be evacuated.

      To give an example, my college had a new building with a large staircase in the center. At the second floor, the stairs ended at a door. The door opened towards the stairs. People started complaining that it felt like they were falling down the stairs and wanted the door installed the other way, because of the additional room for the door to sweep. Building codes made it impossible to do so.

    231. Re:Linus by kelnos · · Score: 1

      Compiz Fusion is an OpenGL compositing manager. If you don't have 3D acceleration, Compiz will run like crap. XRender-based compositing managers such as xfwm4, metacity, and xcompmgr will run fine with only 2D acceleration, though.

      --
      Xfce: Lighter than some, heavier than others. Just right.
    232. Re:Linus by FireFury03 · · Score: 1

      Compiz Fusion is an OpenGL compositing manager. If you don't have 3D acceleration, Compiz will run like crap.

      Which is why I explicitly said "Compiz Fusion runs just fine on an Intel GPU" - you don't need your fancy super powerful nVidia or AMD GPU (with its lack of decent drivers) to do what most people care about, which is running the desktop.

      And to be frank, most people probably don't use a compositing window manager anyway, so don't even care about that.

      xfwm4, metacity

      Since when did XFWM4 and Metashitty do compositing?

    233. Re:Linus by JumpDrive · · Score: 1

      Ahh the analogies never end.
      I just went to the vmware site to look into running Vmware on FreeBSD. They have a thread from 2005 where users wanted to migrate vmware hosts from Linux to FreeBSD for stability reasons.

    234. Re:Linus by lee1 · · Score: 1

      "In case you haven't noticed IQ is the acronym..."

      I noticed that you are wrong already.

    235. Re:Linus by Athanasius · · Score: 1

      Indeed, my reading of the whole thing was that the Linus/Alan problem can be summed up by:

      1) Linus being concerned only with fixing the reported regression even though this still left other nasty bugs in the code.

      2) Alan trying to fix those other things as well.

      So when Linus took Alan to task for trying to fix other things as well Alan took it as criticism of the whole patch and it took a while for them both to realise where the other was coming from (Linus has since said he'll accept patches for the other changes in post-2.6.31 release time, not now we're in the 2.6.31-rc4 phase).

    236. Re:Linus by kelnos · · Score: 1

      Well, you did say most people don't really care about 3D. People running Compiz clearly do, even if they don't realize it. Intel GPUs really aren't that bad. If I misunderstood your intent, I apologize.

      xfwm4 has had compositing since September 2004. Not sure about metacity, but it's probably been at least half that long.

      --
      Xfce: Lighter than some, heavier than others. Just right.
    237. Re:Linus by Anonymous Coward · · Score: 0

      Con was approachable if you first approached with praise. However, he was one of those personalities who sometimes reacts too personally to criticism, especially from a source which hadn't previously given praise. He really did sometimes try to argue down bug reporters rather than deal with the bug report. Linus wasn't just making that up, I looked in the archives back when this was a fresh story and found the evidence for it myself.

      Con had this ego trip thing going about being The Guy who was going to push Linux desktop interactive responsiveness forward. He tended to view everything through a 'me vs the world' filter based on this, as if the 'establishment' actively disliked interactivity and before he came along, everybody was only interested in batch server throughput. I believe this attitude (subtle though it might have been, I'm not saying he ever explicitly came out and said "I am the only prophet of interactivity") was responsible for a lot of the problems he had in getting along with other kernel developers. When people criticized his patches or insisted that he provide more objective proof of their goodness, he'd often get angry and subtly (or not so subtly) attack them as stick-in-the-muds.

      I just skimmed archives again and found a Torvalds message where he relates that he was probably going to integrate Con's scheduler despite this, but when Ingo, someone he already knew as a reliable maintainer with the thick skin to take criticism the right way, came up with a patch which seemed equivalent in performance, the choice was obvious.

      (You mentioned flakiness with Ingo's scheduler. There's ample evidence in the LKML archives that Con's had some flakiness too. That isn't really a valid criticism of Linus' decision. He was choosing the one he felt would be maintained better, especially in the long term.)

    238. Re:Linus by the+grace+of+R'hllor · · Score: 1

      Late, but hey:
      Also, a house door opening outwards is good for smacking guests in the face, who tend to be waiting close by. And perhaps passers-by, in case of appartments.

    239. Re:Linus by Anonymous Coward · · Score: 0

      Also, doors should be always pulled when you go in and pushed when you go out.

      Places where heavy snowfall is expected are an exception to this. Pushing open a door from inside when there's 1.5 meters of snow stacked against it is non-trivial.

    240. Re:Linus by Zancarius · · Score: 1

      I just went to the vmware site to look into running Vmware on FreeBSD. They have a thread from 2005 where users wanted to migrate vmware hosts from Linux to FreeBSD for stability reasons.

      That doesn't really surprise me. On the whole, my experience with FreeBSD has been that it is much more stable than most varieties of Linux. The only reason I'm running Gentoo on my file server at home is due to the fact that my printer was poorly behaved with CUPS + FreeBSD. That was back in 2004, so I'd imagine things have probably changed since then, but I haven't had the motivation to change OSes again. (However, I did have FreeBSD on my home router/file server for many years prior to that.)

      But, I admit my attempt to defuse the parents' rotten analogy regarding Linux v. Windows was poor and largely wrong. I've never personally had much trouble except in one edge case with FreeBSD's driver support (and that was with a relatively recent onboard NIC back in 2003--nothing a little change of code couldn't fix along with a makeworld, though!).

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
    241. Re:Linus by Anonymous Coward · · Score: 0

      Alan was being the primadonna, walking of the stage in a tantrum. Maybe Linus doesn't know the TTY code, but he was right that you can't break important apps. However, Alan doesn't get the prestige (and monetary compensation) that Linus does, so he doesn't have to put up with Linus's crap either. Truth is, Linux has outgrown both of their abilities. Alan uderstands the old low level crap and the dead end the new "optimizing" crap has brought them to. Emacs doesn't work with what Linux has become. That's not a bug, it's an incompatibility. Linus feels (rightly) that Linux can't make that decision, but Alan's trying to tell him it already has -- it's too late, and the fix is too painful. And that there's just no moen

    242. Re:Linus by Anonymous Coward · · Score: 0

      No? That would only hold true for a bounded set.

    243. Re:Linus by nobodyknowsimageek · · Score: 1

      > I found myself pulling on a door clearly marked Push.

      Also, doors should be always pulled when you go in and pushed when you go out.

      Note that, with standard door hardware, this would introduce a security hole. A locked door which opens outward is trivially easy to open without the key, because you can slide a credit card or other jimmy over the latching mechanism. When the door opens inward, you can't get to the latch because the door jam protects it.

  4. Should I? by downix · · Score: 1

    I wonder if I should prep my resume to step up for this, but then I realize my bear is nowhere near long enough.... 8)

    --
    Karma Whoring for Fun and Profit.
    1. Re:Should I? by HomerJ · · Score: 4, Funny

      How long does a bear have to be? Is it proportional to long cat?

    2. Re:Should I? by jalet · · Score: 2, Funny

      > but then I realize my bear is nowhere near long enough

      so you call it your bear ? then I suppose it's thick enough.

      mine is call "my rat", as it's neither long nor thick.

      --
      Votez ecolo : Chiez dans l'urne !
    3. Re:Should I? by jav1231 · · Score: 4, Funny

      Are we talking tail-to-nose or is that a phalic reference? OTOH, how you would know your bear's penis length is something that should probably go unsaid.

    4. Re:Should I? by CarpetShark · · Score: 1

      OTOH, how you would know your bear's penis length is something that should probably go unsaid.

      Clearly, you've never faced an angry bear waving its appendages at you.

    5. Re:Should I? by Anonymous Coward · · Score: 0

      Yes, most of us aren't interested in beastiality.

    6. Re:Should I? by Draek · · Score: 1

      I believe if he's waving his appendages at you, "anger" isn't exactly the emotion he's experiencing. I hope you have some vaseline, though.

      --
      No problem is insoluble in all conceivable circumstances.
    7. Re:Should I? by WaywardGeek · · Score: 2, Interesting

      I once had a bear do exactly that! We were camping at Merced Lake in Yosemite, and had six-man-weeks of food for three of us to take a two week backpacking trip. We put it 20' up a tree, on the end of a 10' limb. In the middle of the night, we heard loud stomping sounds, a bunch of scrapping sounds, then a rope-through-pulley sound, and a loud crash. A damned black bear had jumped from the tree, caught our food bag on the way down, using our rope to slow his crash, and squashed a small tree when he landed.

      My friend had a great idea. "Let's go get our food back." I don't know how I let him talk me and my other buddy into it, or why I was the one in front with a dying flash light, as we followed the munching sounds into the woods. Suddenly, the bear stood up on both back legs with his arms out, and I don't know if the roar I heard was the bear, or just the blood rushing to my head. I turned around to ask if we should run, but there was no one there! I caught up to my brave friends at the lake, where we discussed wading into the freezing cold lake vs. making a stand there.

      I must say, it didn't occur to me to check out the bear's penis, but he was waving everything else at me!

      --
      Celebrate failure, and then learn from it - Nolan Bushnell
    8. Re:Should I? by croddy · · Score: 3, Interesting

      Once we camped out near a river, in known bear territory somewhere in central California. We hadn't seen any bear tracks, but put our food up in a nearby tree anyway (because that's just what you do in bear territory).

      At around 2 AM that night, we awoke to hear the sound of large animals moving in our campsite, accompanied by the rustling of what sounded very much like our bear bag. Getting a fire going as quickly as possible (meaning, a liter of white gas poured onto the nearest thing that looked like wood and then set ablaze), we didn't find a bear. We found a team of TWO bears attacking our bear bag.

      The big one climbed up the trunk of the tree, just under the branch from which we'd hung the bag. The little one, presumably a cub of the big one, had climbed out on the branch, and in a series of small steps, had pulled the bag along the branch with one arm toward the larger bear, who could now reach it from her spot on the trunk, and who was shredding the bag to bits as all our food dropped out. The fire, of course, chased the thieving duo away after a couple of minutes, and they thankfully only got away with some sausages and most of a bottle of pancake syrup.

      Of course, what we hadn't noticed was that this tree had basically no leaves or branches or bark on it anywhere. Based on the number of large scratches and claw marks all over the tree, we surmised that we weren't the first ones to try to hang our food from this tree, which was essentially a food collection station operated by the bears to tax any humans foolish enough to camp there.

      The damn bears are smarter than you'd think.

    9. Re:Should I? by 427_ci_505 · · Score: 1

      Oh come on. We're humans, and can one up the bears.

      Put food on said tree, wait till the bears come calling.

      Set up two people with M249 SAWs and two riflemen to back them up. When the bears start working on getting the bait food out of the tree, open up on them.

      The resulting meat should feed your band for at least a week. Longer, if salted.

    10. Re:Should I? by socsoc · · Score: 1

      Yeah and the humans are idiots. Bear bags aren't what people use these days. Use bear canisters. Using a bear bag is like using salmon eggs to hide your hook from trout.

    11. Re:Should I? by value_added · · Score: 1

      The fire, of course, chased the thieving duo away after a couple of minutes, and they thankfully only got away with some sausages and most of a bottle of pancake syrup ... The damn bears are smarter than you'd think.

      Smarter than I think would generally be OK, but two smart bears prowling for sausages or pancake syrup not so much. ;-)

      Great story!

    12. Re:Should I? by GrahamCox · · Score: 1

      The damn bears are smarter than you'd think

      Smarter than the average bear. Booboo.

  5. Interesting... by wandazulu · · Score: 3, Interesting

    I'm curious about how projects, in general, fare after someone with rather intimate knowledge leaves for whatever reason. I'm not being specific to Linux; you gotta think some of the kernel developers of Windows have left over the years. That's gotta be hard on the next person regardless of project; "here's his code, all three million lines of it. Oh, he seemed to like Pascal syntax so he wrote all these macros to make his C++ code look like Pascal. Good luck!"

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

      Have you heard of the BlueBrain project? It was a linux driver that allowed you to completely control the computer with your brain. After Dr. Magnus Braun left the project, it fell into disuse and is no longer maintained or even widely available.

    2. Re:Interesting... by Monkeedude1212 · · Score: 4, Funny

      Remember Windows ME?

      Bingo.

      (Just kidding I have no idea WHAT went wrong there)

    3. Re:Interesting... by jerep · · Score: 4, Interesting

      Indeed, ive jumped into quite a few projects replacing a previous programmer. Some were experienced and reading their code was really interesting, others were fired for being incompetent and I ended up rewriting most of their code.

      In any cases, the first few days, weeks or months depending on the size of the code are spent studying the structure rather than actually coding.

    4. Re:Interesting... by jtshaw · · Score: 3, Insightful

      That is why you have to have coding standards...

      I'd also hope you never have 1 person in charge of 3M lines of code.

    5. Re:Interesting... by $RANDOMLUSER · · Score: 5, Funny

      Everything.

      --
      No folly is more costly than the folly of intolerant idealism. - Winston Churchill
    6. Re:Interesting... by schon · · Score: 5, Interesting

      ive jumped into quite a few projects replacing a previous programmer. Some were experienced and reading their code was really interesting, others were fired for being incompetent and I ended up rewriting most of their code.

      In any cases, the first few days, weeks or months depending on the size of the code are spent studying the structure rather than actually coding.

      The differences here are that A) this is an open-source project, B) this is a *HIGH PROFILE* open source project, and C) Alan was the maintainer, not sole coder (so he both coded, and accepted patches from others.)

      It's possible that Alan was the only one who knew anything about the TTY code and how it worked, but I'd doubt it. I'd be really surprised if the new maintainer comes into the role cold.

    7. Re:Interesting... by dltaylor · · Score: 1

      Must have worked at Wind River in the past.

      I still have nightmares of looking through their old code, which had BEGIN and END replacing the block definitions and a very non-K&R (or any other reasonable) indent style.

    8. Re:Interesting... by amorsen · · Score: 2, Insightful

      It's possible that Alan was the only one who knew anything about the TTY code and how it worked, but I'd doubt it. I'd be really surprised if the new maintainer comes into the role cold.

      The tty layer in Linux is really old. Not all of it, of course, but I would guess it's one of the oldest bits left in Linux. It doesn't need to be high performance, so noone has rewritten it for that. It is a bit brittle in general, and it interacts with e.g. hundreds of serial port drivers on almost as many architectures. Also, lots of applications use it, some of them with a long history on their own. POSIX and the Single Unix Specification have tried to standardize it all, but there's just too much ancient history.

      In other words, slowly rewriting it as Alan was doing it WILL break things (which users will notice) and most of the improvement is just in prettier code and therefore less work for the kernel maintainers (which users won't notice). It will probably prevent the occasional OOPS as well, but those are pretty rare already.

      Anyway, I'm not really a coder, I just read LKML.

      --
      Finally! A year of moderation! Ready for 2019?
    9. Re:Interesting... by Anonymous Coward · · Score: 0

      Indeed, ive jumped into quite a few projects replacing a previous programmer. Some were experienced and reading their code was really interesting, others were fired for being incompetent and I ended up rewriting most of their code.

      I regularly inherit code written by my boss. I don't remember a single file that I didn't have to rewrite. He seems to hate functions, so what he does is use global variables that a function reads, then writes the result to another global variable; it's sometimes hard to keep track what writes where, because a variable called "x" is being used by two or three different functions. His HTML is atrocious, on the level of WYSIWYG designers from last decade. His design choices are horrible, from "ddmmyyyy" format for log files (because "yyyy-mm-dd" is obviously wrong), over using random numbers for storing some other files (yes, there have been collisions; no, there weren't any checks for "file exists?"), to stored procedures with parameters named "@p1".."@p10" and tables without primary keys and indexes. It's a small miracle when a query doesn't do a table scan.

      *sigh*

      Hm, I'd better post this as AC.

    10. Re:Interesting... by QuoteMstr · · Score: 1

      So quit. Life is too short to keep working at a job you've come to hate.

    11. Re:Interesting... by mwvdlee · · Score: 1

      I actually know somebody who used COBOL with a preprocessor to emulate Pascal syntax! Obviously, it didn't look anything like Pascal except the keywords, the syntax was very badly defined and everything was terribly inefficient. Don't know what happenned to him, but I'm guessing he's probably CTO now.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    12. Re:Interesting... by Anonymous Coward · · Score: 0

      I will, very, very soon. The salary was okay, but they've slashed it due to recession, just when I was expecting a raise...

      I'm not a star programmer. I'm decent, but I put a lot of thinking into what I do, my HTML validates, I don't do "select * from table" and I read The Daily WTF without saying "whoops, I once did that"... But seeing things that my boss does makes me wonder if I'm better than I think I am.

    13. Re:Interesting... by MichaelSmith · · Score: 1

      Yeah I wrote a serial interface to an SMS modem. I wanted it to work on Linux and BSD. I spent a lot of time copying if statements out of uuucp. There is not a lot which is standardised in that area.

    14. Re:Interesting... by MichaelSmith · · Score: 2, Funny

      My first job was working in Pascal, but the boss was an old FORTRAN guy and he banned any constructs which couldn't be done in that language.

      In another job my boss would write code like this:

      int CARSPD; /* Speed of car */
      int CARPOS; /* Position of car */

      And I would write

      int speedOfCar;
      int positionOfCar;

      ...and he would get stuck into me for not writing comments.

    15. Re:Interesting... by Anonymous Coward · · Score: 0

      And I would write
      int speedOfCar;
      int positionOfCar;

      ...and he would get stuck into me for not writing comments.

      You should put comments in there. But they should look something like:
      int speedOfCar; /* in miles per hour */
      int positionOfCar; /* in meters from starting point */

    16. Re:Interesting... by Anonymous Coward · · Score: 0

      Miles and meters? WTF?

    17. Re:Interesting... by rs79 · · Score: 1

      ...and he would get stuck into me for not writing comments."

      "Comments lie. Code never lies." - Keith Doyle, 1981.

      --
      Need Mercedes parts ?
    18. Re:Interesting... by Anonymous Coward · · Score: 1, Insightful

      > Miles and meters? WTF?

      You get the point - until it's specified, your guess is as good as mine.

  6. No gratitude? by isd.bz · · Score: 5, Insightful

    I see the tags 'butthurt' and 'whaaaaaaaaa', but no 'thanksforyourtime'. Why won't anyone show any gratitude for the years of work he's generously offered to the project?

    1. Re:No gratitude? by babywhiz · · Score: 1

      looks like it's changed now......

    2. Re:No gratitude? by castironpigeon · · Score: 4, Funny

      Hello and welcome to /.

      --
      mmmm...forbidden donut
    3. Re:No gratitude? by Chris+Burke · · Score: 4, Informative

      I see the tags 'butthurt' and 'whaaaaaaaaa', but no 'thanksforyourtime'. Why won't anyone show any gratitude for the years of work he's generously offered to the project?

      If you really want to know, google up the "Greater Internet Fuckwad Theory" and the Penny Arcade comic that comes up will explain it for you, though you can probably guess the gist from the name. Sad but true.

      --

      The enemies of Democracy are
    4. Re:No gratitude? by binary+paladin · · Score: 5, Insightful

      Because the slashdot crowd is composed mostly of whiner douche-bags. The rest of us are masochists so far as I can tell.

      After getting my head ripped off for mentioning that I liked operator overloading the other day, I'm trying to figure out why I still post here. I dunno if the crowd is getting nastier or now that I'm far removed from being a teenager, I see how bad it always was. I can't have a reasonable discussion on this site anymore without some asshat hijacking it and turning it into a flame fest.

    5. Re:No gratitude? by SCPRedMage · · Score: 2, Insightful

      Because the Internet is composed mostly of whiner douche-bags.

      FTFY.

      --
      My sig can beat up your sig.
    6. Re:No gratitude? by Anonymous Coward · · Score: 0

      You just don't know how hard it is being a teenager because you've never bee...

      Well, anyways, what is this here linux community?

    7. Re:No gratitude? by binary+paladin · · Score: 4, Insightful

      Ha. Yes. You did indeed fix that for me.

      (And I got modded insightful for my own whining? WTF?)

    8. Re:No gratitude? by tsstahl · · Score: 1

      Dude, I LOVE operator overloading. Seriously though, you are not alone.

    9. Re:No gratitude? by mustafap · · Score: 3, Funny

      >After getting my head ripped off for mentioning that I liked operator overloading the other day

      Is this the 5 minute argument or the full half hour?

      --
      Open Source Drum Kit, LPLC deve board - mjhdesigns.com
    10. Re:No gratitude? by SuurMyy · · Score: 2, Insightful

      You know, it doesn't hurt to have us adults around. Sometimes you can raise above the stupid comments and sometimes not. When you can't, just take a break and come back when and if you feel like it. I've been gone and back quite a few times already. These days I rarely get pissed off about stuff because I know that some of us just can't or won't bother to act like decent human beings. I come back despite these people because this is a good place to come to easily get an overview regarding what's going on in the tech world.

      --
      The lyf so short, the craft so long to lerne
    11. Re:No gratitude? by Anonymous Coward · · Score: 0

      After getting my head ripped off for mentioning that I liked operator overloading the other day, I'm trying to figure out why I still post here.

      If you want abuse and to get modded to subterranean levels, try saying that you detest console games and prefer PCs. That seems to step on a lot of toes on /.

    12. Re:No gratitude? by orzetto · · Score: 1

      After getting my head ripped off for mentioning that I liked operator overloading the other day [...]

      You wanted an argument? Oh, I'm sorry, but this is abuse. You want room 12A.

      (Stupid git.)

      --
      Victims of 9/11: <3000. Traffic in the US: >30,000/y
    13. Re:No gratitude? by xaxa · · Score: 2, Insightful

      I dunno if the crowd is getting nastier or now that I'm far removed from being a teenager, I see how bad it always was.

      I had the same thoughts a while ago. There seems to be more to argue (rather than discuss) now, maybe it's the articles -- there are more about the environment, transport, politics and censorship than there were a few years ago [citation needed], where anything less than +4 isn't worth my time reading.

      I can't have a reasonable discussion on this site anymore without some asshat hijacking it and turning it into a flame fest.

      There's haven't been any reasonable discussions on the Internet since September (or so I'm told, I was 3 years too late).

    14. Re:No gratitude? by db32 · · Score: 1

      Given that this post is just a complaint is it safe to assume that you ar ein the whiner douche-bag bunch and I am a masochist for responding?

      --
      The only change I can believe in is what I find in my couch cushions.
    15. Re:No gratitude? by chrylis · · Score: 3, Insightful

      Because humanity is composed mostly of whiner douche-bags.

      FTFBOY

    16. Re:No gratitude? by electrosoccertux · · Score: 1

      The key is just learning to hear/read things without getting frustrated at the anonymous person. I used to get all irritated about it all, but now I just accept that the world/people is/are broken, that this is especially clear on the internet, and move on. It's not worth losing your blood pressure over.

    17. Re:No gratitude? by Anonymous Coward · · Score: 0

      This is one of the most wise things I've read on this site. Kudos.

      Captcha: instruct. How apt.

    18. Re:No gratitude? by SCPRedMage · · Score: 1

      I find your ideas intriguing, and wish to subscribe to your newsletter.

      --
      My sig can beat up your sig.
    19. Re:No gratitude? by GodfatherofSoul · · Score: 1

      If you weren't already complaining about getting flamed, I would have flamed you for using operator overloading.

      --
      I swear to God...I swear to God! That is NOT how you treat your human!
    20. Re:No gratitude? by Anonymous Coward · · Score: 0

      I stopped posting here around ten years ago or so, when Malda thought it would be cool to punk the readership with a phoney april fool's joke, done in coordination with a few other sites, having to do with microsoft suppressing free speech on the web.

      When Malda failed to apologise, I failed to return to /. for several years.

      I read it again now once in a while, but very seldom read any of the comments. And even more seldom do I post.

      When the maintainer of something loses respect for the customers, it's time for that maintainer to move on. And I do NOT mean Cox. Malda showed bad judgement with the "joke." He made a much worse mistake compounded on top of that lapse: He arrogantly refused to say "I'm sorry." to his readership.

      AFIAC, he can take a long walk off a short pier. The sense of betrayal never fades when compounded by arrogance.

    21. Re:No gratitude? by Kjella · · Score: 1

      After getting my head ripped off for mentioning that I liked operator overloading the other day, I'm trying to figure out why I still post here.

      I'm sure you're one of those using the functionality sensibly, but it's one of those features that many misuse horribly. Too many people here are scarred from the OMG WTF WTF code you can find out there in real life software outsourced to India or other uncommented spaghetti code. Because all features are "flat" you can get people with little more than C++ for dummies using it. It's almost so I think languages should have two levels, where you have to explicitly unlock advanced features. With a warning like "This is usually not the right way of doing it, if you an experienced developer and really sure this is necessary go ahead, but this is like taking a unicycle down a mountainside. Only do it if you're really sure there's no better way."

      --
      Live today, because you never know what tomorrow brings
    22. Re:No gratitude? by toby · · Score: 1
      --
      you had me at #!
    23. Re:No gratitude? by Anonymous Coward · · Score: 0

      The answer is; They ARE. Where are you reading?

      These are the tags for the summary;
      linux programming thankyou slashdotted drama linux programming story

      And many replies are "thanksforyourtime"-themed.

      Why did you indirectly claim that everyone was complaining by your leading question?

    24. Re:No gratitude? by KrimZon · · Score: 1

      I got bitten by operator overloading when my calculations kept going inexplicably wrong. It turned out that the operator precedence was different to how I expected. Rather than quit, I took note and continue to use the feature.

    25. Re:No gratitude? by An+Onerous+Coward · · Score: 1

      After getting my head ripped off for mentioning that I liked operator overloading the other day, I'm trying to figure out why I still post here.

      ::spurts coffee everywhere::

      You like what?

      --

      You want the truthiness? You can't handle the truthiness!

    26. Re:No gratitude? by CrosseyedPainless · · Score: 1

      It's pretty much always been that way. People feel strongly about things, and the "discussions" get brutal at times. It isn't personal (usually!), but there's no reason you should put up with it if you find it distasteful.

      Really? Operator overloading??!? What a moron! Worst Idea Ever.

    27. Re:No gratitude? by The_Other_Kelly · · Score: 1

      Excellent point.

      Alan Cox wants a break, after many, many years of extremely hard work.

      He has earned, and deserves, better.

      I thank him, salute him and wish him the best with whatever new project
      he chooses to spend his time on.

      Thank you Alan.

      --
      (R)ule in Hell or (S)erve in Heaven [R]?
    28. Re:No gratitude? by cryptoluddite · · Score: 1

      I dunno if the crowd is getting nastier or now that I'm far removed from being a teenager, I see how bad it always was. I can't have a reasonable discussion on this site anymore without some asshat hijacking it and turning it into a flame fest.

      USENET died. Where else are we supposed to have tech flame wars?

      There's too many mod points on reddit so you can't even have reasonable discussions... if you're being the devil's advocate you just get hidden. At least on /. you can post a contrary view and unless you invoke Hitler nobody wants to waste their few mod points burying your post.

      Also, it's not operator overloading that's the problem, it's implicit conversions and lack of multi-methods... ;-P

    29. Re:No gratitude? by raddan · · Score: 1

      You also got modded insightful for your meta-whining. I suspect it's because lots of us have had your same experience. For me, the scales are still weighted toward "worth it", because even though one is often instantly labeled an asshole for having an opinion around here, every now and then someone says something really great. I know that it's popular among certain geeks to pooh pooh the Slashdot crowd, but I've really learned some life-changing things around here. I know, it sounds cheesy, but I'm not kidding.

      Unfortunately, the habitual trolls are probably more likely to stick around (because they're ill or something) than the rest of us. Maybe some smart Slashdotter will tell me what that phenomenon is called.

    30. Re:No gratitude? by lewiscr · · Score: 1

      After getting my head ripped off for mentioning that I liked operator overloading the other day...

      I applaud operator overloading, when the symbol has been defined elsewhere to mean the same thing. I really like Fortress for it's unicode support when providing operators to overload. Finally, set operators using set notiation.

      I applaud anybody that beats the shit out of newb programmers that overload every single object method because they can.

    31. Re:No gratitude? by lewiscr · · Score: 1

      Quit yer whining. It was funny.

    32. Re:No gratitude? by geniusj · · Score: 1

      I was curious to see your operator overloading post, so I took a look at your profile. I found the post, but no replies to it. Am I missing something?

    33. Re:No gratitude? by SpinyNorman · · Score: 2, Insightful

      That's an awful argument for not putting useful features into a language, because poor programmers will always write bad code, regardless of language. There's yet to be designed a language that protects you from writing bad code. Maybe one day there will be. The only protection from bad programmers is not to hire them.

      What a language can do is provide features that allow good programmers to write good readable code.

      There are certain things that you just expect to be implemented by certain operators, regardless of whether the underlying types are built into the language or not. Integer addition, Real addition, Complex addition, Set union, String catenation, List append. Internally we think of these things as "adding" and it's only natural to use the "+" operator for them.

      Not only does operator overloading allow the programmer to implement code that maps naturally to out mental models, but it also allows more readable code to be written since it uses infix (operator) rather than prefix (function call) notation. How much easier it is to visualize the set expression (s + t) * (p + q) as opposed to Intersection(Union(s, t), Union(p, q)), or worse yet it's object orientated equivalent s.Union(t).Intersected(p.Union(q)).

      The poster you relied to certainly has a point. The level of technical knowledge and experience of the average slashdotter has gone down the toilet in recent years. It used to be a mostly highly technical crowd, but now half the people here have never even programmed, or just done so for a year or two, yet have outspoken opinions on things they know nothing about.

    34. Re:No gratitude? by Zancarius · · Score: 1

      I'm friend'ing you, because this is almost exactly what I was thinking this morning. I've noticed that many comments are growing increasingly more abrasive and generally angry; even over relatively petty things (like you mentioned)!

      Though, I've observed that the real obnoxious comments fall into two (very general) groups:

      1) The person who feels the need to point out the painfully obvious but does so with a condescending tone. This person typically either repeats what you said--almost verbatim--or argues a point you've already addressed. Both circumstances are indicative of poor reading comprehension skills (more accurately: laziness). There's also an inkling of what I can only describe as the "I'm writing this in the hopes I make you look stupid since I'm so very, very smart."
      2) Just plain asshatery.

      Posters in camp #1 tend to get modded up and in worse circumstances, your comments get modded down, even if they raise a good point. Subsequently, anyone else who comes in to defend you is either modded down or has a repeat of the same tactic performed against them. Posters in camp #2 tend to get modded Flamebait or Troll. Though, there's also a great deal of vacillation between these two for most posters.

      Now, I will confess that on days I've been especially grumpy, I've said things in a manner that was most definitely not objective. But... I think that's true for most of us.

      Oh, and there's a slight corollary to #1. There's a distinctive subset of that group which brings up a point that's not completely related to the post they're replying to, but they feel the need to argue it in the hopes of somehow disproving the original poster. Typically, this has little impact on their karma (positive or negative), although there is some tendency to be modded up.

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
    35. Re:No gratitude? by Anonymous Coward · · Score: 0

      I've observed the same thing with linux in general (especially debian users) and to a lesser extent, computer programmers in general (especially the younger ones)

      It is frustrating, the biggest impediment to the desktop market at this point isn't the GUI, it's the attitude.

      Good luck Alan Cox, I do hope you join a more mature project some day, like one of the BSD's.

      BSD doesn't have as many possibilities on the desktop, but it does have a bright future in servers, I hope you'll find a home there.

      The crowd over there tends to be a bit older, too. :-)

      But for now.. you'll probably just want a break... no one can blame you.

    36. Re:No gratitude? by Anonymous Coward · · Score: 0

      or now that I'm far removed from being a teenager, I see how bad it always was.

      I would guess from the high percentage of "I hate [popular thing], [popular company] is evil" posts that most /. posters really are teenagers.

    37. Re:No gratitude? by rs79 · · Score: 1

      " USENET died. Where else are we supposed to have tech flame wars?"

      Twitter.

      Start with #dns and work up to #icann.

      --
      Need Mercedes parts ?
    38. Re:No gratitude? by vidnet · · Score: 1
    39. Re:No gratitude? by jimicus · · Score: 1

      (And I got modded insightful for my own whining? WTF?)

      Simple. Different discussions on /. tend to attract a different group of people - and some are more prone to attracting the "armchair expert" than others. This discussion has clearly attracted a number of experienced developers who know there's more to developing code than just sitting down churning it out and going out of your way to offend anyone whose viewpoint is even remotely different from yours.

    40. Re:No gratitude? by Anonymous Coward · · Score: 0

      True that - but that's just human nature. You're more compelled to do something about something you don't like than something you do like.
       

      ... by the way I love operator overloading :-)

    41. Re:No gratitude? by Antique+Geekmeister · · Score: 2, Funny

      You meant "spewed Java everywhere", didn't you?

    42. Re:No gratitude? by TheRaven64 · · Score: 1

      It's a question of user interface. Anyone who tries hard enough can use a tool badly, but a good tool makes good use easier than bad use. A good programming language, and a good set of libraries (which is usually more important) makes it easier to write good code than bad. If you don't realise this, then I suggest that you have spent your programming career struggling with bad tools - the fact that you may have written good code with them is a credit to your ability as a programmer but reflects poorly on your choice of tool.

      --
      I am TheRaven on Soylent News
    43. Re:No gratitude? by jsalbre · · Score: 1

      There's haven't been any reasonable discussions on the Internet since September (or so I'm told, I was 3 years too late).

      +5, Awesome usenet reference.

    44. Re:No gratitude? by BitZtream · · Score: 1

      I post here because I can be an arrogant cocky son of a bitch who shows how brilliant I am, only to come back the next day and see that someone pointed out how wrong I am.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    45. Re:No gratitude? by Leafheart · · Score: 1

      I get the impression that if Linus says it is right, all the others, including his praisers are wrong. The guy may be smart be he is such a douchebag that I think Linux, as of now, would be better with a better "leader".

      --
      --- "When you gotta do something wrong. You gotta do it right. (Fighter)"
    46. Re:No gratitude? by isd.bz · · Score: 1

      At the time I posted the comment (4:09 PM, about 15 minutes after the original post), only the negative tags were there.

    47. Re:No gratitude? by SpinyNorman · · Score: 1

      Sure, there are languages like Perl and APL that encourage good programmers to write bad code, but that's not what we're talking about here.

      If you want a library that expresses common operations with intuitive operators, then that requires the languange to support it.

      The kind of neophyte programmer that misapplies language features isn't going to limit it to one particular feature. The same person who abuses operator overloading because he wants to try it out, or thinks it's cool, is also going to be (in C++, for example) abusing inheritance, virtual functions, templates and everything else for the exact same reason - they want to try it out, or they want to try to look cool by using advanced features they don't actually understand. I've seen plenty of code like this, and operator overloading is the least of your problems; this is code that needs to be rewritten it it's ever to be production quality. The problem is the programmer, not the language.

      Thanks for your concern over my career choices, but I'm doing fine. Maybe you learnt to program using the Pascal I implemented 25 years ago! ;-)

    48. Re:No gratitude? by magbottle · · Score: 1

      mentioning that I liked operator overloading the other day.

      There's another one! Grab him before he gets away!!!!

    49. Re:No gratitude? by imac.usr · · Score: 1


      You don't seem that arrogant to me. Guess that means you were wrong then. And it didn't even take a day! :P

      --
      I use Macs for work, Linux for education, and Windows for cardplaying.
    50. Re:No gratitude? by Magic5Ball · · Score: 1

      Clippy: It looks like you're implementing a Duff's Device. Would you like help?

        Get help with implementing the Duff's Device

        Just type the construct without help

      --
      There are 1.1... kinds of people.
  7. On slashdotting... by nweaver · · Score: 5, Interesting

    WHY can't lkml.org's mailing list retriever handle a slashdotting?

    Its not like the flashcrowds are all THAT big.

    --
    Test your net with Netalyzr
    1. Re:On slashdotting... by Enderandrew · · Score: 1

      There are other sites that mirror the LKML, right? Can someone please post other links?

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    2. Re:On slashdotting... by TopSpin · · Score: 4, Informative

      Try Google Groups.

      That's the entire thread, supposedly.

      --
      Lurking at the bottom of the gravity well, getting old
    3. Re:On slashdotting... by Anonymous Coward · · Score: 0

      yea, it's on groups.google.com ~ aka usenet

    4. Re:On slashdotting... by maxume · · Score: 3, Informative

      39 and 40 are the first two messages from the summary.

      The third message linked in the summary seems to be from a different thread.

      --
      Nerd rage is the funniest rage.
    5. Re:On slashdotting... by quantum+bit · · Score: 1

      They should've run it on BSD... :P

    6. Re:On slashdotting... by stevied · · Score: 1
    7. Re:On slashdotting... by sys.stdout.write · · Score: 1

      39 and 40 are the first two messages from the summary.

      True, but don't refrain from reading a few posts prior to that. It's interesting to watch how the anger builds between Linus and Alan.

    8. Re:On slashdotting... by Anonymous Coward · · Score: 0

      Wow, seriously, again a hero dissappoints (my highlights):

      You claim that emacs sh*ts itself when it gets EAGAIN, and you think
      that's an emacs bug. And I think you're full of crap. We should NEVER EVER
      get EAGAIN (due to the SIGCHLD, at least) if the app on the other side
      wrote data that could be read.

                                                      Linus

      I hope they're really good friends for him to say that. That's some lack of social skills there - perhaps the phrase you wanted was "I think you're mistaken"? Torvalds already says up-thread he thinks Cox work [on this] is crap. I know you don't want to get all fey and over sensitive but is such abusive talk necessary? I thought Torvalds was an engineer not a highschool student.

      Presumably Torvalds was Cox boss in a business relationship, he certainly lays into Cox like he's paying Cox to listen, IMO.

  8. Slashdotted - Google Cache. by Anonymous Coward · · Score: 5, Informative

    In before the Karma-Whores.

    "stern criticism" -> http://74.125.155.132/search?q=cache:http://lkml.org/lkml/2009/7/28/373&hl=en&strip=1

    "decided to walk away" -> http://74.125.155.132/search?q=cache:http://lkml.org/lkml/2009/7/28/375&hl=en&strip=1

    "quite clear that he is serious" -> http://74.125.155.132/search?q=cache:http://lkml.org/lkml/2009/7/28/378&hl=en&strip=1

  9. Requisite XKCD answers your question by Enderandrew · · Score: 5, Funny
    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
  10. *It happens by stox · · Score: 5, Informative

    Time for all to give Alan a sound round of applause and thanks! The TTY subsystem is a gem thanks to his work.

    --
    "To those who are overly cautious, everything is impossible. "
    1. Re:*It happens by godrik · · Score: 2, Insightful

      It has been said by a lot of people already. But anyway, thank you Alan for your work in the linux kernel.

    2. Re:*It happens by stox · · Score: 1

      I would, but thanks to the wonders of modern laser technology, I was able to have the "Sucker" tattoo removed from my forehead. More so than most subsystems. maintaining the TTY subsystem is particularly thankless and a very large target for abuse. In addition, it just isn't sexy. My ego could not take it for long. ( long being measured in femto-seconds )

      --
      "To those who are overly cautious, everything is impossible. "
    3. Re:*It happens by TheBig1 · · Score: 1

      Why would you fix a gem?

    4. Re:*It happens by Anonymous Coward · · Score: 0

      ...you clearly didn't read the whole thread. The TTY subsystem ISN'T a gem, it's a turd...and everyone involved has an opinion regarding the best way to fix it. But the real problem is that the fix can go one of several ways:
        - Fix the code so this bug goes away
        - Fix the code so it works correctly
        - Fix the code so it works correctly now and in the future

    5. Re:*It happens by Ant+P. · · Score: 1

      That feature that went in one or two releases ago, the one that displays bold in a different colour on the console, (where only one font is usable) was a nice touch IMO. Makes manpages much more readable. I know Linux didn't do it first, but I appreciate little things like that.

  11. Please mod parent up by Enderandrew · · Score: 1

    Please mod parent up

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    1. Re:Please mod parent up by ioshhdflwuegfh · · Score: 0, Troll

      Please mod parent up

  12. Re:Slashdotted - Google Cache the real links by sugarmotor · · Score: 3, Informative

    "stern criticism" -> link 1

    "decided to walk away" -> link 2

    "quite clear that he is serious" -> link 3

    --
    http://stephan.sugarmotor.org
  13. so much for a "benevolent dictatorship" by Anonymous Coward · · Score: 0

    so much for a "benevolent dictatorship"

    1. Re:so much for a "benevolent dictatorship" by lbalbalba · · Score: 3, Insightful

      No, this pretty much *is* a definition of a "benevolent dictatorship".

    2. Re:so much for a "benevolent dictatorship" by Tetsujin · · Score: 2, Insightful

      Benevolent or not, a dictatorship is a dictatorship. It can be a great way to get things done (really, I think clearly establishing leadership is essential for establishing a coherent direction for a project...) but of course people won't always be happy under such circumstances.

      --
      Bow-ties are cool.
  14. Not diplomatic by rlp · · Score: 3, Insightful

    This could have been handled much better via a private message (or phone call) than in a public forum.

    --
    [Insert pithy quote here]
    1. Re:Not diplomatic by Anonymous Coward · · Score: 1, Interesting

      Thats the way open source is, 'out-in-the-open', no private messages, all is for all to see, all is public.

    2. Re:Not diplomatic by tsstahl · · Score: 1

      Seriously, you should read some of the LKML history. This here ain't nuttin. :) As other reply said, this is the way it is done. Note, however, that does not make your advice unsound.

    3. Re:Not diplomatic by Anonymous Coward · · Score: 0

      It's not just about open source, it's about personal relationships. These guys have known each other for a long time.

    4. Re:Not diplomatic by Hairy1 · · Score: 1

      It looks like there was no private conversation between Linus and Alex. Alex says in his email that he was working on it, so it would seem that he did recognise that the regression was an issue. I know how he feels - sometimes you just need a break. Besides, developers like new challenges, nothing worse than maintaining the same codebase year in year out. Linus on the other hand was right to insist that regressions get fixed.

    5. Re:Not diplomatic by ribuck · · Score: 2, Insightful

      This could have been handled much better via a private message (or phone call) than in a public forum.

      No I disagree. Doing this in public means everyone understands exactly what's going on. No room for misunderstandings.

      And thanks Alan for all your hard work for Linux over the years.

    6. Re:Not diplomatic by CannonballHead · · Score: 1

      No room for misunderstandings.

      And public mistakes or temper-losses make public embarassments and broken relationships instead of apologies.

      Some things are good to do in private. Heated arguments and insults are probably one of them. If they did it in private and still were mad at each other, it'd become public. It's easier to work out when you're not publically criticized and publically humiliated and then publically responded to and publically state "I'm leaving."

    7. Re:Not diplomatic by Anonymous Coward · · Score: 0

      Get real.
      Alan Cox is not leaving Linux development, he's just not the maintainer of the TTY layer anymore..

    8. Re:Not diplomatic by jimwelch · · Score: 1

      Just like Obama's "police acted stupidly" remark.

      --
      Never trust a man wearing a coat and tie!
    9. Re:Not diplomatic by Anonymous Coward · · Score: 0

      You're new to this, aren't you. :-)

    10. Re:Not diplomatic by blueskies · · Score: 1

      Yeah, police should always arrest people that they don't like for disorderly conduct even if the charges won't stick.

      The police did act stupidly by harassing someone with the means to legally and politically fight back. Smarter police have been harassing thousands of people a year without coming under scrutiny. He screwed up by being a bully to the wrong person.

    11. Re:Not diplomatic by jimwelch · · Score: 1

      Your comment shows a *bias* against the police. I have meet both "power drunk" police and courteous police. Therefore we see the situation differently. What I see, from the news reports is as follows: The officer was *called* to the scene of a "possible" break-in. He did *not* go looking for a black to harass. It was his duty to determine reality. The angry, biased (whether against all cops or white cops) professor, over reacted and caused the situation to escalate. I have been in similar situations, when a false burglar alarm, triggered the police arrival. I was courteous, respectful, and showed my id, no big deal. I was also in the opposite situation when a cop was verbally abusive to a teen that drove his car into my house. I waited till it was over, before I complained to the cop.

      --
      Never trust a man wearing a coat and tie!
    12. Re:Not diplomatic by CannonballHead · · Score: 1

      police should always arrest people that they don't like

      I'm glad you have such insight into the officer's mind and intentions. Some people would pay a lot of money for that kind of "knowledge of the heart." [/sarcasm]

      On a non-sarcastic (and off topic) note, if Obama wanted to "fix" a "nationwide" police situation/racism/whatever, it probably was not the best time to do it. Let's see. Personal friend of the "racially profiled" black man? Yup. Former student of the school? I think so. Same race? Yup. Multi-ethnic police force on the scene? Yup.

      I'm not denying racism, but trying to force racism on someone to prove a point is ridiculous. Unfortunately, it seems many that are more liberal in their political views (which is fine, I respect the honest liberal's opinion just as I respect the honest conservative's opinion ... and generally don't respect either one's dishonest opinion) think racial discrimination is something only white's practice... in other words, that it is a fundamental issue with a certain race, instead of a fundamental issue with the human race. Blacks, hispanics, latinos, whites, Asians... all of the above can and do evidence "racism." It's not like the minorities are somehow immune to racist thinking.

      The cure for racism is not racism. The cure for racism in college enrollment is not to force colleges to enroll students based on race.

    13. Re:Not diplomatic by Anonymous Coward · · Score: 0

      There was a great writeup at time magazine where an author said that the police report very clearly revealed a crime did occur that night--and that the report proved it. After going on for a while they basically said "The crime committed was false arrest by officer Crowley--and the police report is a written, signed confession"--and they're right.

      The reported behavior didn't match the act as defined by law--now I wouldn't say an officer should know this--but when they're arresting somebody for the fuzziest, worst-defined offense there is...they ought to at least have a clue.

    14. Re:Not diplomatic by blueskies · · Score: 1

      I'm not suggesting racism. I'm suggesting that there are more bullies as cops than good people as cops. (and the good ones start becoming dirty when they cover for the bad ones)

      And even if the citizen is being a complete asshole, i DON'T PAY the citizen, i pay the salary of the cop. Part of his pay covers the part that he will have to deal with assholes and not take it personal.

      Since they carry GUNS, I am highly critical when they act as bullies.

      (when i'm safely on the internet and i know they can't track me down and arrest me on trumped up charges that is)

  15. FTA: by Wally4u · · Score: 2, Informative

    > Quite frankly, I don't understand why I should even have to bring these > issues up. You should have tried to fix the problem immediately, without > arguing against fixing the kernel. Without blaming user space. Without > making idiotic excuses for bad kernel behavior. > > The fact is, breaking regular user applications is simply not acceptable. > Trying to blame kernel breakage on the app being "buggy" is not ok. And > arguing for almost a week against fixing it - that's just crazy. I've been working on fixing it. I have spent a huge amount of time working on the tty stuff trying to gradually get it sane without breaking anything and fixing security holes along the way as they came up. I spent the past two evenings working on the tty regressions. However I've had enough. If you think that problem is easy to fix you fix it. Have fun. I've zapped the tty merge queue so anyone with patches for the tty layer can send them to the new maintainer. --- MAINTAINERS~ 2009-07-23 15:36:41.000000000 +0100 +++ MAINTAINERS 2009-07-28 20:09:32.200685827 +0100 @@ -5815,10 +5815,7 @@ S: Maintained TTY LAYER -P: Alan Cox -M: alan@lxorguk.ukuu.org.uk -S: Maintained -T: stgit http://zeniv.linux.org.uk/~alan/ttydev/ +S: Unmaintained F: drivers/char/tty_* F: drivers/serial/serial_core.c F: include/linux/serial_core.h

  16. Open-Source developers are jerks by kriston · · Score: 2, Insightful

    I maintained an open-source project for several years. Open-source developers are jerks. They never accept it when their code just isn't going in. I know they're all smart and I get really good contributions, but sometimes you aren't meeting the need. The overwhelming majority of open-source developers I have encountered are just that: jerks.

    --

    Kriston

    1. Re:Open-Source developers are jerks by Hatta · · Score: 5, Insightful

      The overwhelming majority of people I have encountered are jerks. That's nothing open source developers, or any kind of developer, has a monopoly on.

      --
      Give me Classic Slashdot or give me death!
    2. Re:Open-Source developers are jerks by OrangeTide · · Score: 3, Insightful

      I find the same behavior from programmers of closed source applications too. Any bug or question is taken personally or they run with a bad decision forever because doing otherwise would admit fault. I have the most respect for the rare developer that changes his/her stance and does the right thing in the end. Typical developers are very defensive and need a lot of ego stroking to get useful work out of them.

      --
      “Common sense is not so common.” — Voltaire
    3. Re:Open-Source developers are jerks by kriston · · Score: 1

      That's a great point. Too bad nobody is going to see what you replied to.

      --

      Kriston

    4. Re:Open-Source developers are jerks by kriston · · Score: 3, Insightful

      Sometimes is works the other way. How many times have good developers been beaten-down by inferior, more senior, co-workers who think a "code review" session is really a "watch me brilliantly rewrite your code in front of you" session?

      --

      Kriston

    5. Re:Open-Source developers are jerks by tsstahl · · Score: 1

      Mod parent up. Welcome to life in the cubicle farm.

    6. Re:Open-Source developers are jerks by Skuld-Chan · · Score: 2, Insightful

      I've run into this on closed source internal projects - the difference is you rarely see the emails in public. Most developers take crucial app breaking bugs as a personal affront to their skill or ability, where in reality its just the way things work in big projects. In other words - every product out there has loads of awful bugs, please get over yourself and help me fix them.

    7. Re:Open-Source developers are jerks by Anonymous Coward · · Score: 0

      Too bad nobody is going to see what you replied to.

      i just used my last point to mod parent up, so hopefully someone will see it...

    8. Re:Open-Source developers are jerks by Lisandro · · Score: 1

      Preach on, bro.

    9. Re:Open-Source developers are jerks by Anonymous Coward · · Score: 0

      The overwhelming majority of people I have encountered are jerks. That's nothing open source developers, or any kind of developer, has a monopoly on.

      You might want to look at the common factor in all these meetings. Perhaps you turn people into jerks.

    10. Re:Open-Source developers are jerks by hey! · · Score: 5, Insightful

      When I was in college, I was in a volunteer group. I took a project leadership position, and I was warned that the people volunteering for us were unreliable and unpleasant to work with. Later I was pleasantly surprised to find that not to be the case. Of course people did mess up from time to time and sometimes people found themselves over-committed, but on balance I found the volunteers cheerful, eager and reliable as I could reasonably expect under the circumstances.

      I found other project leaders would talk about *the same people* I worked with successfully as if they were totally unreliable. What was mystifying is that I am so *not* a nice guy. I'm not a *bad* guy, either, but I'm kind of gruff and impatient, and I don't mince words either.

      So I watched how *they* managed volunteers, and compared to how *I* managed volunteers.

      I'd say, "Can you do such and so on Saturday? You'll need to show up at noon and stay until four. You can? Good. Do you want to scare up some helpers or would you like to take care of that? Great, thanks. Give me a call if anything changes."

      They'd say, "Look, we really, really need somebody to do such and so. I know you're *so* busy, and I really hate to ask you to do this, but nobody else can and we're desperate. Can you, PLEASE? Really? Are you *sure*? It'll be a disaster if nobody shows up so I really need to know for sure. Really? OK I know this is a HUGE sacrifice for you."

      The conclusion I came to was that the other guys were trying way too hard to be nice, and so they were failing on an epic scale. It didn't even *occur* to me to try to be nice, and so I didn't commit any of their horrible mistakes.

      I think the problem with the phony "nice" approach was it demonstrated lack of respect in so many ways. First of all their attitude practically radiated their lack of confidence in the volunteer. They assumed the volunteer didn't want to volunteer, and would volunteer just to shut them up (probably true) and then not show up (also often true). They assumed the volunteer would be swayed by flattery (you're so busy), guilt (it'll be a disaster if you don't show up), twisted pride (this is a job so horrible nobody but you would consent to do).

      It's hard not to step on that disrespect third rail now and then, but these guys were jumping up and down on it from the get-go. It's ALWAYS a mistake. If you want a guy to leave, you should just say, "Sorry, this isn't working out. Let's move on." Getting snarky on them just means they'll stay and work like malcontents.

      Linus's post is perfectly understandable. I don't think it shows towering ego and arrogance. We all get exasperated now and then. He's trying to be nice about it, but he just can't help himself. He's only human. It doesn't *matter* whether he's right or wrong, he let his exasperation show. When you're on the receiving end of that it comes across as disrespectful. Sometimes *trying* to express your exasperation *nicely* is even worse. It's patronizing.

      One thing I learned is that people will do good work for no money before they'll do good work for no respect. And the best people won't work at all without respect.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    11. Re:Open-Source developers are jerks by pbhj · · Score: 1

      The overwhelming majority of people I have encountered are jerks.

      There's a chance it's not them ...

    12. Re:Open-Source developers are jerks by OrangeTide · · Score: 1

      I usually run into the junior engineers who need their code rewritten in a code review session. And get offended because that assume because they were the best programmer in their small circle of friends that what they write is actually any good.

      --
      “Common sense is not so common.” — Voltaire
    13. Re:Open-Source developers are jerks by Anonymous Coward · · Score: 0

      Very well said. Very true.

    14. Re:Open-Source developers are jerks by houghi · · Score: 1

      Sounds like musicians. When they ask what you think of your music and you say you did not like it, they will go about how you don't know anything about music. I know some who don't do that, but many will.
      Or when discussion something with a manager or with an employee or with a person in the pub.

      So basically people will get defensive when you disagree with them. The more personal it is, the more defensive they will become. If it is something they thought up it is very personal.

      Just try to change how people work. Many people will not like to do that, even though it will make life easier, because they feel that if they change, it means they were wrong in how they did it before. People don't like to be wrong.

      --
      Don't fight for your country, if your country does not fight for you.
    15. Re:Open-Source developers are jerks by Anonymous Coward · · Score: 0

      The overwhelming majority of people I have encountered are jerks.

      That says more about you than the people you have met.

    16. Re:Open-Source developers are jerks by xtracto · · Score: 1

      The overwhelming majority of people I have encountered are jerks. That's nothing open source developers, or any kind of developer, has a monopoly on.

      Wow, you must live in the USA. From my personal experience I have found that in general people is good and nice by nature. However I have only lived in Mexico, England, and Germany. And have traveled to France, Netherlands, Bulgary, Spain, Scotland, Ireland (north and south), Wales, Czcech Republic, Canada among others.

      I was in the USA once, I can not judge the people because I was only 8 years old and I only went to Florida attractions (Universal Studios, Epcot Center, Disney World, etc,etc).

      The people I have met who are originally from the USA, did not fall into the "jerk" profile. However, I *do* have seen the typical American (fat, USAteam-baseball cap and Tshirt jerk) trying to get all the attention at the Madame Tussauds museum.

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    17. Re:Open-Source developers are jerks by Anonymous Coward · · Score: 0

      Hmm. You should probably consider the common factor in all those interactions where one of the parties is acting like a jerk.

    18. Re:Open-Source developers are jerks by pz · · Score: 1

      Thanks very much for this post. I'm just starting to solicit volunteer subjects for my experiments (no, not kidding, I am a scientist studying visual perception), and have taken the oh-so-nice approach which hasn't been working all that well. I'll try the cut-and-dry approach for a while to see if it works better.

      (I continue to be impressed at how informative the posts from low Slashdot ID members are.)

      --

      Put my fist through my alarm clock with its ding-dong death inside my ear. - The Blackjacks.
    19. Re:Open-Source developers are jerks by hey! · · Score: 1

      One thing I did not emphasize in my post that might be important to you is this: if you make it sound like a *huge* sacrifice to volunteer, then people take you at your word. If you take the attitude "this is something you can do and you'll find it reasonably interesting and rewarding," people are much more open to that.

      The important point (other than respect) is not to try motivating people by raising stakes. Yes, if you are very charismatic, you might convince a surprising number of people to move with you to Guyana to drink the Kool-Aid, but you're making your job harder than it needs to be.

      It's like Apple's 0.99/track pricing policy. You *hope* you'll love the track, expect it'll most likely be OK, but at under a buck you won't be put out if it sucks.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    20. Re:Open-Source developers are jerks by WuphonsReach · · Score: 2, Insightful

      The bigger thing was that you gave clear expectations and times. So your volunteers knew that they needed to show up at X, what to expect, and that they could leave at Y. People like predictability and knowing that things aren't going to change on a whim (most of the time). It makes them feel like a situation is under their control and allows them to make other plans with certainty.

      (Interestingly, you'll see the same thing if you try to lead / schedule raids or events in a game like WoW. Both situations involve herding cats to achieve a common goal in an environment where your members can easily walk away or not show up. There's a good bit of overlap in the people skills required to succeed.)

      --
      Wolde you bothe eate your cake, and have your cake?
    21. Re:Open-Source developers are jerks by Anonymous Coward · · Score: 0

      Not saying this is the case with you, but sometimes the reaction is due to subtle things like body language or voice tone. A few personal changes with myself and the jerk factor has majorly decreased, although humans will always suck.

  17. In other News . . by Anonymous Coward · · Score: 5, Funny

    Alan Cox announces he will maintain Slashcode: "After this, it will be bloody easy to maintain the Slashcode codebase."

    1. Re:In other News . . by Anonymous Coward · · Score: 0

      I thought slashcode was made by a beowulf cluster that did nothing but multiple variations of cat /dev/random >> slashcode.pl and anything that didn't return an error got commited. Sounds like that'd be easy to maintain.

    2. Re:In other News . . by MartinSchou · · Score: 1

      Maintaining Slashcode is easy. Convinding Slashdot to use the updated Slashcode however ...

  18. Alternative Link by steltho · · Score: 2, Informative

    Here is a link to the start of thread that has not been slashdotted ... yet.
    http://marc.info/?l=linux-kernel&m=124870096801094&w=2

  19. LOL by Anonymous Coward · · Score: 0

    I have nothing to say but "LOL".

  20. Rarely the diplomate by Anonymous Coward · · Score: 5, Insightful

    Yes, indeed it could have been. But unfortunately that's Linus' modus operandi and we all know from long experience that while a great programmer, his ego is far too big to allow him to apologize publicly in the same fashion in which he slammed Alan. Quite unfortunate really since both are quite talented individuals.

    You can't expect to publicly berate people and have them bow to your every demand and not have it backfire on you at some point.

    1. Re:Rarely the diplomate by shovas · · Score: 4, Insightful

      Linus is respected but not liked. I've acted like him in my youth and couldn't get away with it. I learned to be more personable. The only reason Linus gets away with it is partly because he is an intelligent person and partly because of the stature of his position. One day he will be an old man with no friends.

      --
      Selah.ca. Pause, and calmly think on that.
    2. Re:Rarely the diplomate by Lonewolf666 · · Score: 4, Funny

      Yes, he can be pretty abrasive. Consider this: http://thread.gmane.org/gmane.linux.kernel/701694/focus=706950

      Security people are often the black-and-white kind of people that I can't
      stand. I think the OpenBSD crowd is a bunch of masturbating monkeys, in
      that they make such a big deal about concentrating on security to the
      point where they pretty much admit that nothing else matters to them.

      (emphasis mine)

      --
      C - the footgun of programming languages
    3. Re:Rarely the diplomate by Kjella · · Score: 1

      Without defending Linus, I have thought "Well, the most secure computer is disconnected from the network, turned off and enclosed in concrete... but that wouldn't be very useful, would it?" during one of those security rants...

      --
      Live today, because you never know what tomorrow brings
    4. Re:Rarely the diplomate by Anonymous Coward · · Score: 0

      Well perhaps if they stopped whacking off all the time he wouldn't have said that

      captcha = "micron" oh the irony!

    5. Re:Rarely the diplomate by Anonymous Coward · · Score: 1, Funny

      Isn't that the title of the next Ubuntu release?

    6. Re:Rarely the diplomate by sjf · · Score: 1

      Agreed, it's a simple rule of management: if someone is acting earnestly, you don't describe their work as a "pile of sh*t."
      If their work is a "pile of sh*t" as a general rule, then you dismiss them. How you do this for the Linux kernel, I have no idea. How long is the queue of (competent) people begging to be cursed by Torvalds ?

    7. Re:Rarely the diplomate by libkarl2 · · Score: 1

      That simian-masturbatory maniacal focus on security is exactly why I use OpenBSD. If I was a monkey, and jacking off was a primary mission goal, then clear, consistent priorities would have to made and adhered to. All other considerations would have to be shelved. These are necessary and vital preconditions for anyone who lives in a zoo.

      --
      You are where you are at the time you are there.
    8. Re:Rarely the diplomate by Anonymous Coward · · Score: 0

      I think the OpenBSD crowd is a bunch of masturbating monkeys

      The history of my genome shares a common ancestor with modern monkeys, thereby we are related. I masturbate. I have used OpenBSD previously and continue to use it whenever possible. See, he's right!

    9. Re:Rarely the diplomate by Ant+P. · · Score: 1

      Isn't that the title of the next Ubuntu release?

      They're only up to "I" right now, so you'll have to wait until late 2010. I'd vote for it though.

    10. Re:Rarely the diplomate by Anonymous Coward · · Score: 0

      Yep, Linus went too far. I'd be pretty pissed if I was a monkey to be so unfavourably compared to the OpenBSD crowd in this way.

  21. This is terrible by Profane+MuthaFucka · · Score: 3, Funny

    Where can we find another hacker that looks like a yeTTY?

    --
    Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
    1. Re:This is terrible by maxume · · Score: 2, Funny

      Nearly anywhere hackers can be found?

      --
      Nerd rage is the funniest rage.
  22. Could anyone shed some light... by Lisandro · · Score: 4, Interesting

    ...about the details of this argument? I know Linus might not be the easiest person to work with, but he seems to make some sense here.

    1. Re:Could anyone shed some light... by thanasakis · · Score: 1

      Nice touch too, wouldn't you think?

    2. Re:Could anyone shed some light... by Lisandro · · Score: 1

      Yes. The "idiotic excuses" remark was just finesse...

    3. Re:Could anyone shed some light... by bluephone · · Score: 1

      Sometimes after a week of arguing with someone who shifts their weak arguments from one excuse to another, one gets tired of being diplomatic, and lays the truth out baldly. "Idiotic excuses" is sometimes unkind but true.

      --
      jX [ Make everything as simple as possible, but no simpler. - Einstein ]
    4. Re:Could anyone shed some light... by cryptoluddite · · Score: 5, Informative

      The details are that TTYs in general on any *nix are a huge mess with lots of complicated interactions and weird historical behavior that doesn't make sense. The linux tty stack for a long time was a huge clusterfuck. Now thanks to Alan it's just a normal clusterfuck. That's the context for this incident, which basically happened like this...

      Some dudes: there's a bug in the ttys
      Alan: ok lets fix it
      Some dudes: here's a patch
      Alan: that patch breaks a dozen other things
      Some dudes, Alan reject a bunch of solutions
      Alan: we can fix it with a hack, but it breaks emacs. Emacs is relying on unspecified behavior, so it can go suck an egg.
      Linus: well it SHOULD (sic) work like this, and emacs is too holy to break. This problem is easy, are you a retard?
      Alan: look we can hack it and break emacs, or do a huge rewrite
      Linus: hacks suck, linux should be awesome in every way. Also, your code smells
      Alan: it's going to take forever to get this right
      Linus: then revert the patch that introduced the bug
      Alan: that patch was applied years ago and removing it would break a dozen other things. You didn't think I'd think of that? Who's the tty maintainer anyway, jackass?!
      Linus: I don't like your attitude
      Alan: Then fuck off I quit!
      Linus: Oh yeah did I mention your code smells?
      Linus: and let me quote you something you said earlier, so I can show what a bad attitude you have.

      The TTY and serial line code is basically a huge Rube Goldberg machine and Linus was telling Alan to tweak something somewhere in the middle of this huge contraption. Having followed the TTY code a fair bit, I totally side with Alan on this. It's a miracle that it even works, and not something you can just stick your head in and give advice about how to fix. Also, if Linus is so concerned about proper behavior for user space programs maybe he should take a look at ioctl... because it's completely screwed up in linux.

    5. Re:Could anyone shed some light... by xant · · Score: 1

      Yeah, I immediately had sympathy for Linus' position here. Even if one disagrees with the other developer's position, if you can't prove you're right, then you don't have standing to argue over it for a week. At that point, admit you're not going to change their mind, and do it their way. It takes less energy and causes fewer meltdowns.

      --
      It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
    6. Re:Could anyone shed some light... by Anonymous Coward · · Score: 1, Insightful

      so now that you've beggard the question. why does linux have a tty layer?
      i'd bet 3/4 of /.ers have never seen a tty. why emulate them?

    7. Re:Could anyone shed some light... by Anonymous Coward · · Score: 0

      Technically, Alan is 100% correct that EMACs is relying on PTYs to act *different* than real TTYs ... it expects them to see events in a particular order, which isn't possible given all the options for low level races. (I've had to fix similar races in TTY drivers; they're a PITA.) But the pty(7) man page says that's wrong; no matter which side of the PTY is slave, it's got to act like a standard TTY:

      The slave end of the pseudo-terminal provides an interface that behaves exactly like a classical terminal.

      Linus argues in contrast that such a longstanding bug just became an undocumented feature. And then got a bit rude, and refused to accept a patch that worked around the problem, and then blew things up.

      From a technical perspective you might also restate Linus' position as wanting to redefine the TTY layer as a more monolithic blob, inside of which races can't happen. Me, I'd just ask for a pony!!

    8. Re:Could anyone shed some light... by Myrv · · Score: 1

      Except, if I read the rest of that thread correctly Linus's suggestion to use the "nicer" fix wasn't a bad one. Using it didn't require the huge rewrite warned about but looks to only need another 5 lines or so of mutex code to get back to normal (although apparently normal may also have issues but that problem is outside the scope of this particular issue).

    9. Re:Could anyone shed some light... by hitmark · · Score: 1

      in the same reason that the excel file format specification contains references to some of the first spreadsheet apps that ran on apple2?

      or that window 7 will hold a emulated version of windows xp?

      basically, its been like that forever, and is now so entrenched that trying to come up with a whole new system will just break more then it gains in the short term?

      human history is full of these things. even today's nations may well look back to roman decisions when trying to settle a dispute.

      we build on what our parents and grandparents leave us, that they themselves built on ancestral legacy.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    10. Re:Could anyone shed some light... by Ant+P. · · Score: 1

      Windows used to have something like that.

      In attempting to remove it, Windows ME was produced.

      They had a parallel codebase they could jump ship to. Linux doesn't, so it can't afford to fuck this bit up.

  23. Not very responsible either by Lucky_Luke(void) · · Score: 1

    First of all I am very greatful for everything he did. I know he contributed a lot. Hope the handover will be more than this emotional message: "Please talk to the new tty maintainer whoever that ends up. I no longer care."

    1. Re:Not very responsible either by PeterBrett · · Score: 5, Informative

      First of all I am very greatful for everything he did. I know he contributed a lot. Hope the handover will be more than this emotional message: "Please talk to the new tty maintainer whoever that ends up. I no longer care."

      You'll be pleased to hear that not only is Alan helping with the handover, he's been providing some constructive criticism about the way the bug is being fixed now Linus and a few other people have turned their full attention to it.

    2. Re:Not very responsible either by Lucky_Luke(void) · · Score: 1

      Yeah, I finally was able to read some of the other posts in the LKML Lots of fuzz about nothing.

    3. Re:Not very responsible either by HiThere · · Score: 3, Insightful

      It's not nothing. The TTY module has lost a very talented maintainer.

      OTOH, it's definitely not the end of the world, either.

      I ONCE wrote a serial driver for an RS232C port on a CP/M system. This is my only right to criticize. For such right as it gives... Alan deserves full credit for many years of irritating work with a stupid messy standard. And *I* only had to interface three devices. I think that was the project that convinced me to never again touch assembler.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    4. Re:Not very responsible either by Anonymous Coward · · Score: 0

      Since there is no signed-off-by tag for his patch which removes him as the maintainer, the patch cant be applied to vanilla... with him helping
      on this issue, maybe this isnt this serious after all...

    5. Re:Not very responsible either by Lucky_Luke(void) · · Score: 1

      It's not nothing.

      Actually, initially I was under the impression he completely stopped contributing to the kernel, instead he just quit as TTY maintainer and fortunately didn't lose his constructive attitude in the LKML.

    6. Re:Not very responsible either by Big+Jojo · · Score: 1

      It's not nothing. The TTY module has lost another very talented maintainer.

      Fixed that for you.

      Previous maintainer was ISTR Russell King, who does enough other stuff that he never had time to overhaul the TTY stack. It's needed such an overhaul pretty much since it was first written. Most developers who've looked at TTY have broken out in hives, either before or while running away. Which has, previously, been the only sane reaction from anyone who didn't fancy cleaning up those Augeaen stables.

      At some level, it was clearly just Time For Alan To Move On ... since most of the overhaul is done, and he's smart enough not to want to get stuck with TTY forever.

    7. Re:Not very responsible either by Anonymous Coward · · Score: 0

      It just goes to show how much more mature and reasonable Alan is.

      This is one of those things:
      - would not happen over a phone call
      - Linus should not have made it personal
      - should not be made public

      Linus should apologise...anybody actually reading the thread will conclude Alan kept it technical (right or wrong), while Linus escalated it...

  24. It's not just OSS developers. by leoc · · Score: 1

    AKA: "The more people I meet, the more I like my dog."

    --
    STFU about slashdot bias.
  25. Re:More reason to love open source... by blueskies · · Score: 2, Funny

    It's good you never allowed windows network code into your company. You wouldn't want any open source BSD code in your company!

  26. How is this different from the real world? by uss · · Score: 0

    I mean, in the real world that I live & work in -- working on internal software projects...

    It does not matter, how good a coder you are.
    What matters is how well you "work with" the owner/manager, to address intangibles like "transitioning", "being a team player", "sticking to processes & best practices", "aligned with manager's priorities", "not being single-topic focussed", etc...

    In the real world, there are the idea guys, who are invariably different from the implementation guys. Managers have no qualms with taking the idea-guy's idea, and asking someone else to implement it. Most of the time, this is because the idea guy's work ethic or reliability, is not up to snuff, in the estimation of the manager in charge.

    Should I welcome the OSS world to the real-world?

    1. Re:How is this different from the real world? by Enderandrew · · Score: 1

      Which is why I suggested that perhaps this is simply human nature and unavoidable. Personality conflicts are going to happen. People aren't perfect.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
  27. Linux? by n3v · · Score: 2

    Everyone serious uses BSD anyways :)

  28. You Both Still Rule by Bob9113 · · Score: 1, Offtopic

    Alan, Linus, you both still rock in my book. Nearly every day for the past 13 years I have benefited from all you've done -- both personally and professionally. Squabbles happen, and it's not my place to judge -- cuz no matter what you've both given me a helluva lot more than I've given either of you.

    Keep on kicking ass and taking names, however you are happy to do so.

  29. Re:Slashdotted - Google Cache the real links by Anonymous Coward · · Score: 0

    Um, yeah I am going to just click on a link with an IP address. I like the previous poster's method that allows you to see the entire link even if it means I have to cut and paste.

  30. Re:Hey by Anonymous Coward · · Score: 0

    Why is modding the truth considered "a troll". They are both acting like girls.

  31. Thank You by dburkland · · Score: 5, Insightful

    Alan thank you for your contribution to the open source community!

  32. So long and thanks for all the code. by tempest69 · · Score: 3, Insightful
    The TTY code has been pretty decent to me over the years. I've never found a situation that my code could do right with the TTY. Not that Im writing editors.
    Overall I hope Alan finds a new project, I suspect that his experience could really help all sorts of userland code.
    Coders are stubborn and dislike being told how to do anything. No shame in saying shove it when its time.

    Storm

    1. Re:So long and thanks for all the code. by ceeam · · Score: 1

      I was under impression that Alan Cox was more involved recently in FreeBSD matters than with Linux anyway.

    2. Re:So long and thanks for all the code. by tyrione · · Score: 1

      I was under impression that Alan Cox was more involved recently in FreeBSD matters than with Linux anyway.

      Perhaps Alan wants to position himself to putting his talents to work at Apple on OS X which will provide him the financial response his hard work has more than earned?

    3. Re:So long and thanks for all the code. by AuMatar · · Score: 5, Insightful

      If Alan Cox wanted to work at Apple, it would take 1 phone call. Devs like him don't have problems getting hired. I don't know if he's been working on FreeBSD or not, but if so that isn't the reason.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    4. Re:So long and thanks for all the code. by phoxix · · Score: 5, Interesting

      Actually, and bizarrely enough, there is a high level FreeBSD developer named Alan Cox too

      http://en.wikipedia.org/wiki/Alan_Cox

    5. Re:So long and thanks for all the code. by ceeam · · Score: 2

      Wow. They are different people?!
      Mod parent up somebody.

    6. Re:So long and thanks for all the code. by mysidia · · Score: 1

      Yes... [well] I get the sinking feeling that the TTY code may be about to fall into the gutters in the next few years.

      Ousting Alan is just ridiculous.

    7. Re:So long and thanks for all the code. by Lemming+Mark · · Score: 4, Funny

      I was just going to reply and say the same thing as the GP - there is another Alan Cox for FreeBSD.

      I have a theory that all OSes have their own Alan Cox but maybe they sometimes use pseudonyms to keep that secret!

    8. Re:So long and thanks for all the code. by setagllib · · Score: 4, Informative

      There are two Alan Coxes, one for Linux and one for FreeBSD. It's confusing but there you go.

      --
      Sam ty sig.
    9. Re:So long and thanks for all the code. by GrahamCox · · Score: 4, Funny

      I think I need to start writing my own OS...

    10. Re:So long and thanks for all the code. by zonker · · Score: 0

      I wonder where Microsoft keeps their Alan Cox?

    11. Re:So long and thanks for all the code. by Bodrius · · Score: 2, Funny

      Oh crap!

      Now that the first AC is not working on Linux tty code the chances of him leaving his basement and meeting the FreeBSD AC are much higher.

      What happens if they meet? What would happen to the space-time continuum?

      --
      Freedom is the freedom to say 2+2=4, everything else follows...
    12. Re:So long and thanks for all the code. by ahabswhale · · Score: 1

      Yeah, and I'm pretty sure he's the brother of Hard Cox and his sister is Love Cox.

      --
      Are agnostics skeptical of unicorns too?
    13. Re:So long and thanks for all the code. by Anonymous Coward · · Score: 0

      I wonder where Microsoft keeps their Alan Cox?

      Between Alan's legs.

    14. Re:So long and thanks for all the code. by jawahar · · Score: 1

      Coders are stubborn and like being told what to do.

    15. Re:So long and thanks for all the code. by omnichad · · Score: 1

      Alan Smithee does a lot of coding, I hear. Sorry, couldn't resist.

    16. Re:So long and thanks for all the code. by Yetihehe · · Score: 1

      According to code-vector space theorem AC+AC=AC^2 (A is amperes, C is speed of light), so there would be freakin' huge lightning bolt.

      --
      Extreme Programming - Redundant Array of Inexpensive Developers
    17. Re:So long and thanks for all the code. by Anonymous Coward · · Score: 0

      What's even more bizzare, FreeBSD just got a massive TTY layer overhaul. On the other hand, Alan Cox (neither one of them) was not involved.

    18. Re:So long and thanks for all the code. by Anonymous Coward · · Score: 0

      AC+AC=2AC
      AC*AC=(AC)^2

      ? :)

    19. Re:So long and thanks for all the code. by jnork · · Score: 1

      Maybe Alan Cox is the Alan Smithee of open source? :)

      --
      Cleverly disguised as a responsible adult.
    20. Re:So long and thanks for all the code. by Anonymous Coward · · Score: 0

      Well, there are a lot of Cox in the world . . .

    21. Re:So long and thanks for all the code. by Anonymous Coward · · Score: 0

      You didn't know? Some intern accidentally killed him when they were designing ME.

    22. Re:So long and thanks for all the code. by Errtu76 · · Score: 2, Funny

      Wow. They are different people?!
      Mod parent up somebody.

      Ok, i will!

      Ah damn.

    23. Re:So long and thanks for all the code. by sgbett · · Score: 1

      He never recovered from a DOS attack in the 80's. Poor chap.

      --
      Invaders must die
    24. Re:So long and thanks for all the code. by kevingolding2001 · · Score: 1

      I've never found a situation that my code could do right with the TTY.

      Sounds like a pretty damning rejection of the TTY code in question!

      If the TTY could never do right for you with your code, why aren't you looking for alternatives that CAN do right for your situation?

    25. Re:So long and thanks for all the code. by Anonymous Coward · · Score: 0

      There are two Alan Coces, one for Linux and one for FreeBSD. It's confusing but there you go.

      Fix it for ya.

    26. Re:So long and thanks for all the code. by TheRaven64 · · Score: 1

      The one who works on FreeBSD has a PhD, so you can easily differentiate them by referring to him as Dr Alan Cox.

      --
      I am TheRaven on Soylent News
    27. Re:So long and thanks for all the code. by wilx · · Score: 1

      Seriously? I thought they were the same person. This makes both of them somewhat less extraordinary.

    28. Re:So long and thanks for all the code. by hesiod · · Score: 1

      Neither one was not... so both were? Crazy.

    29. Re:So long and thanks for all the code. by timestamp · · Score: 1

      Nah, "Alan Cox" _is_ the pseudonym that they pass on throughout the generations. It's like the "Dread Pirate Roberts".

    30. Re:So long and thanks for all the code. by Hitman_Frost · · Score: 3, Funny

      There are two Alan Coxes, one for Linux and one for FreeBSD. It's confusing but there you go.

      What? Did they fork him or something?

    31. Re:So long and thanks for all the code. by spydum · · Score: 1

      Try to imagine all life as you know it stopping instantaneously and every molecule in your body exploding at the speed of light. ...
      Don't cross the (tty) streams.

    32. Re:So long and thanks for all the code. by mehemiah · · Score: 1

      perhaps you are thinking of this guy who they mention on the wikipedia page on the linux mantainer.

    33. Re:So long and thanks for all the code. by skeeto · · Score: 1

      There's a third one that's a radio personality. This was the first of three Alan Cox's I have heard of.

    34. Re:So long and thanks for all the code. by Pollardito · · Score: 1

      If Alan Cox wanted to work at Apple, it would take 1 phone call.

      or a handful of SMS messages containing hidden characters to the right person's iPhone

    35. Re:So long and thanks for all the code. by Shadowland · · Score: 2, Funny

      GrahamCox says:
      > I think I need to start writing my own OS...

      Only if you change your first name to Alan....

    36. Re:So long and thanks for all the code. by Dragoness+Eclectic · · Score: 1

      Nobody ousted Alan, he threw a mild hissy fit and quit over being told he was wrong.

      BTW, the other branches of that LKML thread show that he and Linus are still arguing over exactly who was wrong about what where. It's too gnarly a problem for me to figure out from casual reading, so I can't say who's wrong. I doubt you can, either, since two of the biggest experts on Linux kernel code are still arguing over it...

      --
      ---dragoness
    37. Re:So long and thanks for all the code. by __aasqbs9791 · · Score: 1

      I think it depends on whether one of them kills the other. The remaining either becomes a god or the Universe ends, doesn't it?

    38. Re:So long and thanks for all the code. by morgan_greywolf · · Score: 1

      A little known fact is that there is a Microsoft developer assigned to the Operating System division also named Alan Cox. ...

      Oh, stop it! Take off that tinfoil hat, right now!

  33. Handbags at 10 paces... by clickety6 · · Score: 4, Funny

    "You claim that emacs sh*ts itself when it gets EAGAIN, and you think
    that's an emacs bug. And I think you're full of crap..."

    I'm sure there's a job waiting in the diplomatic corps for Mr Torvalds...

    --
    ----------------------------------- My Other Sig Is Hilarious -----------------------------------
  34. I knew it by oldhack · · Score: 4, Funny

    The true point of contention? Emacs vs. Vi. Loons.

    --
    Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
    1. Re:I knew it by iplayfast · · Score: 0

      I've been looking through all the posts, and YOURS was the one that I thought summed it up beautifully.

    2. Re:I knew it by oldpond · · Score: 1

      Nano Nano

  35. Re:Alen doesn't give a shit what you think. by Anonymous Coward · · Score: 0

    unlikely. see some of us don't see sex as the only thing worth living for. it's ok man, go back to watchin the game and drinking beer.

  36. probably went like this by FudRucker · · Score: 4, Funny

    Linus: Hey Alan finger my tty

    Alan: No Way! i quit!

    --
    Politics is Treachery, Religion is Brainwashing
    1. Re:probably went like this by Anonymous Coward · · Score: 0

      No coke, a prostitute and witnesses with a camera involved here, this time?

  37. Re:Slashdotted - Google Cache the real links by Shatrat · · Score: 1

    The entire link still just points to an IP address...

    --
    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
  38. Re:More reason to love open source... by Anonymous Coward · · Score: 0

    Yeah, that's it - mod him flamebait! That'll make that awkward truth go away!

  39. caring costs extra(sm) by Pooch+Bushey · · Score: 1

    caring costs extra(sm)

  40. Re:Slashdotted - Google Cache the real links by ChrisMounce · · Score: 1

    It's okay, they're all Google cache links.

  41. Linus... meh by paxcoder · · Score: 0, Offtopic

    LOAD, LKLM, LOAAAAAAAAaaaaaaaaaaaaaaaaaaaaadeh! *breathes*
    Gotta love the simplicity of Cox's message.
    Unrelated Linkage

  42. Re:Alen doesn't give a shit what you think. by Colin+Douglas+Howell · · Score: 1

    For the time in years he's really free! While you sit at home [... doing blah blah blah ...], he's going to go out, get drunk, and finally get some real pussy.

    I rather doubt his wife would be too happy with that.

  43. Linus doesn't get enough by mok000 · · Score: 1

    This is sad. Linus isn't getting enough sex, that must be why he acts very unprofessionally sometimes. Alan Cox, please come back, we really need you.

    1. Re:Linus doesn't get enough by Anonymous Coward · · Score: 0

      Linus fucks crows on a nightly basis.

  44. Maybe it WAS handled by microbee · · Score: 1

    until it was slashdotted. Now Alan couldn't come back could he?

  45. Could someone please help me tag this story... by Keyper7 · · Score: 1

    "!leavingkerneldevelopment"?

    Alan is someone that should be thanked, but as far as I could tell from the list he just left TTY, not kernel development itself.

  46. Re:Slashdotted - Google Cache the real links by maxume · · Score: 1

    Then there is the whole thing where most browsers show link urls in the status bar (there are hover tricks that can be done in javascript, but Slashdot filters comments, so no worry here).

    --
    Nerd rage is the funniest rage.
  47. Re:Slashdotted - Google Cache the real links by dgatwood · · Score: 2, Insightful

    132.155.125.74.in-addr.arpa domain name pointer px-in-f132.google.com.

    That said, who wants to bet we can find a google cache of goatse?

    --

    Check out my sci-fi/humor trilogy at PatriotsBooks.

  48. Re:Slashdotted - Google Cache the real links by ChrisMounce · · Score: 4, Insightful

    "Please talk to the new tty maintainer whoever that ends up. I no longer
    care."

    You know what really gets on my nerves? When people say they no longer care, when in reality they do. If he really didn't care, he would have typed the first sentence and stopped.

    Linux is a great product, and that is the result of the magnificent work of all the coders and contributers. But sometimes they just act like children.

  49. Theo by nurb432 · · Score: 1

    So has Theo, but things do seem to find a way of getting done.

    Perhaps Alan can come over to the FreeBSD camp where we are a bit more friendly. He's a good guy and will compliment any project he latches onto.

    --
    ---- Booth was a patriot ----
    1. Re:Theo by Zancarius · · Score: 4, Interesting

      Perhaps Alan can come over to the FreeBSD camp where we are a bit more friendly. He's a good guy and will compliment any project he latches onto.

      Oh boy, I can't agree more with this statement. I realize this is anecdotal, but here's my own personal experience...

      In the Gentoo Freenode channel, it was difficult to so much as type without bumping into someone's ego. Participants were generally rude, crude, and--perhaps most ironically--threatened to kick people for using swear words. I have no idea if this has changed at all in the 4 or 5 years since I last joined... but it wasn't a pleasant experience.

      Contrasted with the various FreeBSD channels I used to join infrequently, the experience was on the whole much better. People were friendlier, had a sense of humor, were helpful, and didn't get their underpants in a dozen knots over something incidental like a single, mostly unoffensive swear word. Again, it's been years since I participated in that as well and perhaps the FreeBSD channels have changed...

      Personally, I doubt it. It's a cultural difference, I think. The BSD crowds seem more product-driven (let's get Y done) versus some Linux distros that seem process-driven (I don't like how you're doing X and it doesn't matter if we're making Y).

      This, of course, is purely anecdotal. You don't have to agree with it because it was my personal experience, and as such, FreeBSD folks have come off to me as MUCH more friendly and cooperative.

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
    2. Re:Theo by PReDiToR · · Score: 1

      Not sure about how it was back in the day, but being a Gentoo user for about a year and sitting in the help channel (#gentoo) and the chat channel (#gentoo-chat) quite a lot I can say that the no swearing rule is still in effect for both channels and the policy is to not talk about crap in #gentoo.
      Can't say I've seen much in the way of ego, but some guys kick first and ask questions later, same as any other IRC channel.

      --

      Do not meddle in the affairs of geeks for they are subtle and quick to anger
    3. Re:Theo by Zancarius · · Score: 1

      Again, my experience is merely anecdotal and not necessarily something that would be reflected by everyone else. (For what it's worth, I used Gentoo as my primary desktop OS for about 1.5 years, but I seldom participated in IRC much except for the mere curiosity.)

      One thing I find most interesting is, again, the swearing rule. It seems to apply to most Linux distros, yet most BSD-centric channels don't seem to enforce those same sorts of requirements. I'm not sure why. Again, maybe it's culture.

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
    4. Re:Theo by Meumeu · · Score: 1

      So has Theo, but things do seem to find a way of getting done.

      Perhaps Alan can come over to the FreeBSD camp where we are a bit more friendly. He's a good guy and will compliment any project he latches onto.

      Well that's not exactly hard:

      Wow, your project's great, seriously guys, you rock!

    5. Re:Theo by blue+trane · · Score: 1

      Words are just words, arbitrary symbols. The connections to emotions are in the mind of the reader. By banning certain words, ops are saying: I feel X when I see Y, and everyone else has to too. But freedom means that each is free to interpret the symbols in any way they want. Swear words can often loosen people up, make you laugh, release tension. But ops want to impose their private world on the rest of the users, and because they can't persuade ppl with words, they kick and ban.

    6. Re:Theo by WuphonsReach · · Score: 1

      Public chat channels are inherently problematic. Drama / attention whores love to flock to those channels where they can be the king/queen of the channel. Especially if there is no objective moderation going on to slap down offenders. Those people will drive away the more reasonable and level-headed people.

      You'll see this in all types of communities. It has nothing to do with those folks being technically oriented or not, but has everything to do with base human nature.

      --
      Wolde you bothe eate your cake, and have your cake?
    7. Re:Theo by Zancarius · · Score: 1

      At first, I thought this was an OT rambling post... (hey, I didn't sleep well last night!)

      But then I read your post more carefully and realized this sums up marvelously the problem with stupid anti-swearing rules.

      But ops want to impose their private world on the rest of the users, and because they can't persuade ppl with words, they kick and ban.

      Wouldn't you say this could apply to society as a whole, too? Except, instead of kick and ban, it's sue. Ironically, this comes after we here in the US are banning certain words from use in textbooks because they're sexist (caveman comes to mind).

      I don't suppose you'd run for office? ;)

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
    8. Re:Theo by Zancarius · · Score: 1

      You'll see this in all types of communities. It has nothing to do with those folks being technically oriented or not, but has everything to do with base human nature.

      I'm not so sure that justifies ruling a discussion channel with an iron fist, though. For the *BSD crowd it certainly wasn't the case.

      I run a (fairly small) community myself; in some cases, you can get away with one that is fairly self-policing and requires very little "hands on" administration. Of course, that depends largely on the people who participate, and maybe the Linux crowds have had more trouble with problematic individuals than the *BSD folks. Although, that could be argued as culture: Linux tends to be more attractive to certain groups than does BSD.

      Even still, I believe that it is possible to get away with a fairly friendly discussion channel without ruling it with an iron fist. Obviously, this won't work in all circumstances, but I believe it can in some.

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
    9. Re:Theo by PReDiToR · · Score: 1

      If you can't articulate without resorting to words that have been deemed impolite by a society that existed even before IRC (yes, some things did =) then you're not going to go far in life.

      By the same token, if you are too emotional to articulate without swearing you're probably not going to take enough notice of the advice you're given in a help channel.

      I'm not a #gentoo op, I don't agree in principle with the swearing ban, I swear in RW quite often. I do however respect the ops' decision and abide by it.
      Having a bunch of lame kids in who cannot communicate without swearing keeps the legibility of the text at a level you won't find in most blogs and forums.

      Rules are there to be arbitrary, that is their function. I'm all for rules that keep idiots out of other people's way.
      Any form of censorship is always worse than the censored item. (to paraphrase a /. sig I particularly like).

      --

      Do not meddle in the affairs of geeks for they are subtle and quick to anger
    10. Re:Theo by Zancarius · · Score: 1

      If you can't articulate without resorting to words that have been deemed impolite by a society that existed even before IRC (yes, some things did =) then you're not going to go far in life.

      By the same token, if you are too emotional to articulate without swearing you're probably not going to take enough notice of the advice you're given in a help channel.

      I understand your point; I assume it wasn't intended for me, specifically. (You'll notice I generally don't use swear words in my posts--in fact, you'd be hard-pressed to find any.) I do have to take issue with a few things in particular...

      Having a bunch of lame kids in who cannot communicate without swearing...

      Well, here's the thing: It isn't just kids who swear. Kids swear because they think it's cool and pushes the boundaries of what is deemed acceptable by society. It's part of the socialization process to learn what they can and cannot get away with. Likewise, there are plenty of adults who swear but for a completely different reason (in general). Sometimes it's the only way to get the point across. Really, if someone is so easily offended by swear words, they're probably more apt to support strong censorship of movies, media, and various forms of communication. Really, it's a two-way street. There are people who swear too much, and there are people who are so thin-skinned they can't handle even a border-line swear word.

      As an aside, there is some research that suggests swearing might be a form of pain relief. Like it or not, stubbing one's toe and letting loose with a cascade of violent insults directed toward no one in particular really does feel good.

      Rules are there to be arbitrary, that is their function

      No it's not. Rules exist to enforce strict order and to set boundaries. An arbitrary rule would mean simply that it can be applied to any situation to mean anything. Arbitrary rules don't work. Contrast the following:

      Exhibit A: Clear, concise rule. Please don't swear in this channel. Thank you.

      Exhibit B: Arbitrary rule. Please don't do anything that might upset the OPs. Thank you.

      How do you know where the boundaries are in exhibit B? You don't. That's why rules are not arbitrary. I'm sure you remember something from school; can you recall a list of things the teacher didn't want you to do? They were usually quite specific for a reason.

      Any form of censorship is always worse than the censored item. (to paraphrase a /. sig I particularly like).

      Slightly ironic. You allude to individuals who cannot communicate without swearing and support OPs' decisions to enforce what is effectively a form of censorship (swearing is a form of expression) and yet a .sig you like stresses that censorship is a rather bad thing.

      Perhaps you're being ironic; I see a strong disconnect here. Maybe you can clarify.

      --
      He who has no .plan has small finger. ~ Confucius on UNIX
  50. Linus was right by microbee · · Score: 5, Insightful

    As always.

    The argument started when someone found the tty layer had a regression. Linus cares about regression deeply. His basic philosophy is old bug is better than new bug. If a fix introduces a new bug that breaks a real world application, then the fix should be reverted and a better fix should be worked out.

    This ensures predictable behavior of an OS that you can actually rely on, and better release management.

    Alan didn't think so. He thought his fix was too important to be backed out, although it introduced a regression. Linus was frustrated that he had to explain to Alan, a long time Linux hacker, about the rules. And that's where Alan got impatient too.

    1. Re:Linus was right by Anonymous Coward · · Score: 1, Insightful

      I do appreciate Linus being fierce on behalf of the kernel's downstream users, but has it been factually established that emacs code was not doing something broken and just "getting lucky" until now?

      That was Alan's contention, and if true then it would be better to fix emacs than to keep the tty layer broken or crufty for emacs' lazy benefit.

      At this point, I don't know who was actually right, but both had good intentions of one sort.

    2. Re:Linus was right by yossarianuk · · Score: 1

      As usual Linus (I believe) was right - you do not want fixes that break things, Windows updates often introduce new security flaws when fixing the old one...

      Linus didn't need to be that harsh though. I'm sure that Alan Cox will still contribute to Linux or at least open source. Anyone know what Con Kolivas is doing now ?

    3. Re:Linus was right by Anonymous Coward · · Score: 0

      If nothing else Linus was wrong to handle this the way he did. He's a competent (but not great) programmer, but a poor manager.

    4. Re:Linus was right by jez9999 · · Score: 2, Funny

      That was Alan's contention, and if true then it would be better to fix emacs than to keep the tty layer broken or crufty for emacs' lazy benefit.

      Anyway, I think emacs has its own tty layer, doesn't it?

    5. Re:Linus was right by Eravnrekaree · · Score: 1

      I agree that the regression blowing up an application is unacceptable. Who knows what other applications it blew up. Its actually easier, and less problematic for users, to maintain compatibility at the OS level than to change how many apps could have been affected. maybe not for the OS developer, but for the users and app developers. Backwards compatability is a must and its why windows is at 95% market share on desktop.

    6. Re:Linus was right by DarthLogic · · Score: 1

      While Linus may have been right in this case (I really don't know), nobody is "always" right.

    7. Re:Linus was right by microbee · · Score: 2, Insightful

      [quote]has it been factually established that emacs code was not doing something broken and just "getting lucky" until now?[/quote]

      And it's irrelevant. The entire point is not to blame emacs. Yes, yes, technically speaking, it *might* be better to fix emacs, but the fact remains that the kernel broke a widely deployed application. It doesn't matter whose fault it is. And even if the emacs should be fixed, it can't be done over night. Sometimes the kernel has to bent over and keep buggy behavior if someone important actually depends on it. It's just the job of a kernel: to keep applications happy.

      So Linus was frustrated because he wanted Alan to acknowledge the sentiment. But Alan kept arguing something totally irrelevant.

    8. Re:Linus was right by istewart · · Score: 2, Funny

      His basic philosophy is old bug is better than new bug

      Having driven both, I must say that I agree.

    9. Re:Linus was right by Anonymous Coward · · Score: 0

      No, I'm sorry but it *does* matter whether emacs was wrong-but-lucky or not. If Alan was right, the very best he might have done out of user-oriented deference would be to implement a provisional workaround and inform emacs that their software was broken and they had x months to fix it before the workaround was removed.

      Your way of thinking (I can never correct an error if it breaks an existing application) has some really bad fallout and I don't think Linus would defend it. A) you carry around unmaintainable cruft that makes no sense out of codependency with an outside project, and B) you may hurt future app writers who write something correct according to the spec instead of broken according to the demands of history.

    10. Re:Linus was right by drsparkly · · Score: 1

      Reminds me of the leak of the Windows 2000 code base, the subsequent analysis, and all the special cases for apps that relied on bugs or undocumented behaviour.

    11. Re:Linus was right by Anonymous Coward · · Score: 0

      How often do new linux versions get rolled out? Oddly enough, they're not overnight. Only hard-core devs would be using these versions.

      Also, it's not a question of fault - the kernel did not break anything. EMACS made an incorrect assumption.

      It's not the job of a kernel to keep applications happy. It's the job of the kernel to do the right thing. It could come down to 'fixing security vunerablity' vs 'backwards compatablity'. Which is more important? Anyway, if you want to see where the wonderful world of 'maintaining backwards compatablity' ends you, Windows is over there.

      (Seriously, that's why the Win32 API is so bloated.)

    12. Re:Linus was right by hitmark · · Score: 1

      heh, like sim city having a special clause in the dos memory system, as it had a "bug" where it read or wrote to memory it had freed up just moments before? this even tho said behavior is a very big nono and should rightly result in a error message from the os.

      but then i guess it was easier to maintain compatibility at the os end then, as trying to get a patch out there would be hard. This vs today, when just about every program or game has a built in "update" system, and the users seems to act as beta testers. Googles "eternal beta" may well be a very honest approach...

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    13. Re:Linus was right by the+Atomic+Rabbit · · Score: 1

      The behavior of Emacs seems reasonable. When the SIGCHLD handler is called, Emacs tries to read from the child's PTY, and when it receives EAGAIN, it assumes that there's no further data incoming (because the child is dead!). I'd be surprised if there weren't other applications that behave similarly.

    14. Re:Linus was right by Anonymous Coward · · Score: 0

      "He thought his fix was too important to be backed out"

      It fixed an important root compromise, I tend to agree with him. Linus doesn't care if it's a security vulnerability as opposed to any other bug, but the users do.

      Oh, and Linus acts like an ass a lot. For a volunteer project, there is no reason to talk to people the way linus does. A successful fork of the kernel maintained by someone who is civil to all, will be a great step forward for linux.

      If you think a lead developer acting like an ass to volunteers doesn't hold back a project, see OpenBSD.

    15. Re:Linus was right by Jedi+Alec · · Score: 1

      I do appreciate Linus being fierce on behalf of the kernel's downstream users, but has it been factually established that emacs code was not doing something broken and just "getting lucky" until now?

      That was Alan's contention, and if true then it would be better to fix emacs than to keep the tty layer broken or crufty for emacs' lazy benefit.

      Hold on. You're saying that Emacs has been "getting lucky" on a regular basis and therefore needs to be fixed? This is /. remember? Anything that will allow one to "get lucky" regularly needs to be embraced!

      --

      People replying to my sig annoy me. That's why I change it all the time.
    16. Re:Linus was right by Anonymous Coward · · Score: 1, Interesting

      Actually the problem is more complex.
      From what I understand there is an old bug in the TTY code. This, coupled with misinterpretation of what some calls (such as E_Again) should do led to programs using this bug as a feature (Alan Cox vision, which I tend to respect, especially when it comes to TTY).
      Alan Cox tried to fixed the bug, but this led to breakage in some apps, notably Emacs.
      A bug report was submitted. Alan Cox refused to revert his changes and started working on a solution that would both fix the bug AND allow broken apps to work again.
      Linus came in and asked for a revert. Alan Cox replied that it was a bug in userland form the already buggy Emacs. Linus did not approve, and mentionned au _nicer_ fix for the problem at hand that Alan Cox refused. Alan Cox replied that Linus obviously did not understand the bug.

      So Alan Cox point of view is that he corrected a bug in TTY that led userland apps that were using this bug as a feature to have problems. But that is not his problem because he is not responsible for userland. Further more he seems to think that the _nicer_ fix is inappropriate.
      Linus point of view is that Alan Cox introduced a regression in TTY and that therefore he should rollback or adopt the _nicer_ fix and stop accusing userland or Emacs of being buggy.

      Of course I am nowhere near the amount of skill required to know who is right. But I do know TTYs are a complex matter and that a fix that seems nice for one problem can bring thousands of problems elsewhere. My personal opinion is that Alan Cox is more apt to get the big picture than Linus when it comes to TTYs.

    17. Re:Linus was right by Anonymous Coward · · Score: 0

      But Alan was also right. He claims that it is impossible to remove the patch that introduced the bug in the first place.

    18. Re:Linus was right by ciggieposeur · · Score: 1

      and when it receives EAGAIN, it assumes that there's no further data incoming (because the child is dead!).

      I haven't read the thread, but my understanding was that the only time to assume a descriptor is closed is when select() indicates the fd is readable yet read() returns 0, after which I expect read() to return -1.

      Is that wrong?

    19. Re:Linus was right by ciggieposeur · · Score: 1

      very big nono and should rightly result in a error message from the os.

      DOS wouldn't have been able to return an error message as it had no real memory protection. One could do anything they wanted to memory under DOS, you'd just never know if an interrupt came in what someone else's code would do, so you tried to play nice.

    20. Re:Linus was right by Spugglefink · · Score: 1

      While Linus may have been right in this case (I really don't know), nobody is "always" right.

      You just proved you're not married.

    21. Re:Linus was right by DarthLogic · · Score: 1

      I'm married. I'm just not a pussy.

    22. Re:Linus was right by RiotingPacifist · · Score: 1

      Interesting theory, but pure bullshit. Linus in 2.6.30 broke atime and said that userspace applications relying on it be fixed.

      This ensures predictable behavior of an OS that you can actually rely on, and better release management.

      If you want an OS you can rely on then the linux development model is fucked! 2.x+1/2.x produces reliable OSes, but Linus choose to switch to 2.6 only development (a bold move that has had its benefits).

      Alan was still getting to the root of the problem and finding a correct fix, Linus got flamey, Alan got fed up.Linus doesn't know the specifics of how most of the kernel works (by his own admission) yet far too often gets into arguments with maintainers that DO (the scheduling problem, ioscheduling, filesystem behavior, now ttys) sometimes hes right, sometimes hes not, the problem is that not only does he jump in all guns blazing but he also rarely admits his mistakes (to the point of having somebody reimplement a scheduler, just to save him some face). IMO far too much enphasis is put on the linus tree and linux development would be much better off if distros kept their own trees which pulled directly from patchsets, -ac, -next and mainline.

      Personally I'm a much bigger fan of coxs "do things correctly, even if it hurts" mentality than linus's "don't break userspace, unless its something I don't care about, in which case fuck userspace, unless i don't like the maintainer of the patch in which case ill get some peon to redo the whole thing" mentality, but hey if it wasn't for the licenses id probably be on bsd anyway!

      --
      IranAir Flight 655 never forget!
  51. Thank you Alan by khufure · · Score: 0

    Wherever you end up. Your work on TTY has been quite useful. I must say though, my favorite work you have ever done must be the work on carrier pigeon protocol.

    http://en.wikipedia.org/wiki/IP_over_Avian_Carriers

    Regards

  52. Mirror by Anonymous Coward · · Score: 1, Informative

    You can get the whole convo at the lkml mirror:
    http://marc.info/?t=124870111900001&r=1&w=2

  53. Ha! by Anonymous Coward · · Score: 0

    This mis-understanding would never have happened if they'd used Google Wave! :-P

  54. Meh by littleghoti · · Score: 1

    A tested IQ of 151, and you think poor observation is related to intelligence?

    1. Re:Meh by dotgain · · Score: 1

      Read the post in context - it's quite clear that he doesn't

  55. Just guessing .. by roguegramma · · Score: 1

    It appears to me as well that Linus Torvalds makes sense.

    But perhaps Alan Cox makes sense too - he knew the code well, and maybe there are opposite objectives(keeping userland working and keeping the tty subsystem bug-free) which cannot be reconciled.

    When Alan Cox had realized that, he probably should have been hanging a red flag out and not commit the code to his published branches.

    This is assuming/predicting that the other "nicer" patch Linus Torvalds talks about will have drawbacks, like interfering with other fixes. (I'm pulling this out of my magicians hat, to really be able understand the problem you need to be like three persons.)

    --
    Hey don't blame me, IANAB
    1. Re:Just guessing .. by mapsjanhere · · Score: 1

      I thought that's the beauty of open source, everyone can make their own public branches, and the users are free to adopt whichever they choose. In contrast to us MS drones, who have all the choices in the world, as long as it's black. And this from a guy who once was happy getting a box of 20 Windows Me licenses, at least all of his machines were now running the same crap.

      --
      I'm aging rapidly, I bought a new game and had no idea if my machine was good for it.
    2. Re:Just guessing .. by kshade · · Score: 1

      Yes, they both make sense. Alan didn't want to commit the patch favored by Linus because it may lock up. He does admit that the patch seems like the right solution at first glance, though. Linus then tells him that the current patch causes trouble with userspace apps and it's not because they'ra faulty but because another section of the kernel is. Alan never dealt with this part of Linux. So the problem really isn't the bug that Alan tried to fix with a solution Linus didn't like but another portion of code somewhere else.

      Alan didn't realized that and tried to build a patch that works with the current (faulty) part, but Linus also didn't realize that Alan couldn't know the problem really lies somewhere else and got grumpy when Alan insisted on building a less elegant and obvious patch.

      I don't know, maybe they will both cool their heads, sleep it over and play together again :-)

    3. Re:Just guessing .. by TheDugong · · Score: 1

      I assume you are not being sarcastic(?). Linus and Alan are discussing what to do with the roots. People are free as always to branch away as they please.

  56. yeah, well by Anonymous Coward · · Score: 0

    What's Alan done for us lately anyway? /sarcasm

  57. Who the hell uses a teletype these days anyway? by Anonymous Coward · · Score: 0

    Just wondering.

  58. Re:Alen doesn't give a shit what you think. by Anonymous Coward · · Score: 1, Funny

    He's married to himself?

  59. Re:Slashdotted - Google Cache the real links by sugarmotor · · Score: 1

    > But sometimes they just act like children.

    I wouldn't worry about it too much.
    It's remarkable that the incident is so public.

    Stephan

    --
    http://stephan.sugarmotor.org
  60. Re:Slashdotted - Google Cache the real links by krelian · · Score: 1

    Or you can just hover your mouse pointer over the link and see where it goes.

    And BTW the paranoia level here is ridiculous.

  61. Re:Slashdotted - Google Cache the real links by sugarmotor · · Score: 1

    You are talking in two tongues. First you say you're going to click on a link with an IP address; then you say you like the other copy/paste method.

    But why would you trust a link with a domain name more??

    Just use the previous poster's method!

    Stephan

    --
    http://stephan.sugarmotor.org
  62. The butt hurt started with KDESU? by tyrione · · Score: 3, Interesting

    Hi,

    A recent kernel change broke kdesu (from KDE 4.2) on my test boxes. ISTR a
    discussion about that, but I can't find it right now. Any clues?

    Rafael

    Seriously? KDESU is broken, in the first place.

    https://bugs.kde.org/buglist.cgi?quicksearch=kdesu

    1. Re:The butt hurt started with KDESU? by Anonymous Coward · · Score: 0

      DESU DESU DESU!

  63. Re:Slashdotted - Google Cache the real links by smellsofbikes · · Score: 4, Insightful

    To be fair, "I no longer care" is shorthand for the closely related "I no longer care enough to put up with the criticism" which is just a statement of cost/benefit analysis. He does care, but not enough to keep going, and that roughly approximates "I don't care".

    --
    Nostalgia's not what it used to be.
  64. I wanna be a TiTTY inspector. by dicobalt · · Score: 0, Redundant

    I'll take the job!

  65. Sure: by toby · · Score: 1

    If by "often", you mean "never".

    --
    you had me at #!
  66. So Long and Thanks for all the Bits! by Anonymous Coward · · Score: 0

    So Long and Thanks for all the Bits!

  67. Drag'n'drop by HomelessInLaJolla · · Score: 4, Interesting

    Drag and drop is quite convenient. It is also a security chasm. Once you can drag and drop one thing then you want to be able to drag and drop anything. In the case of arbitrary file formats not only must you implement code to check the incoming data stream (thus exposing yourself to all of the security considerations of "how many different ways can someone try to wax my process of checking the incoming data stream?") but you must consider that a data stream which is valid using one codec algorithm may cause a fault using another codec algorithm. Competing algorithms exist for many data format structures and the presumed same data format may have three or four codecs at use between X, the WM, a monolithic app like a web browser, and a devoted data editor (eg. GIMP), and even a devoted data viewer (eg. a multiformat display application). It isn't the simplest consideration.

    With so much of the problem and criticism with the reigning proprietary OS being security related the open source community has tried to remain a little more focused on security related issues. Combine that with the difference in conceptual organization--F/OSS guys don't get paid to go to in house meetings together--and it is completely logical that something as "simple" as drag and drop is not implemented across largely unrelated application development groups.

    Within a particular desktop environment using apps which were written specifically for that desktop environment (often referred to as a desktop suite) there is probably a more consistent end user experience.

    It is the culmination of (years of) similar situations which has brought many rifts in major F/OSS development groups.

    I find myself personally familiar with the situation which caused Alan to leave. The difference is that Alan has enough financial backing and social connections behind him that he likely will not end up living on the streets.

    Can you imagine a headline,"Major developer sick and tired of political crap, leaves development group, will take up a section of cardboard on the sidewalk just down the block from Slashdot's HomelessinLaJolla"?

    --
    the NPG electrode was replaced with carbon blac
    1. Re:Drag'n'drop by Anonymous Coward · · Score: 0

      jerk

    2. Re:Drag'n'drop by blue+trane · · Score: 2

      ad hominem

    3. Re:Drag'n'drop by bhtooefr · · Score: 1

      If we want to get picky, it's only implemented properly and completely in RISC OS, everyone else only partially implements it. (And ROX Desktop apps on Linux have similar behavior, but that's a very small subset.)

      (RISC OS save dialogs don't even have any filing system management in them. You navigate to the folder you want to save the file in in the Filer (very VERY roughly similar to the pre-OS X Finder, but completely different. Hard to explain.) Then, you drag the icon from the save dialog to the directory. You can also type out a full pathname if you want, though.)

    4. Re:Drag'n'drop by lennier · · Score: 5, Insightful

      "Once you can drag and drop one thing then you want to be able to drag and drop anything. In the case of arbitrary file formats not only must you implement code to check the incoming data stream (thus exposing yourself to all of the security considerations of "how many different ways can someone try to wax my process of checking the incoming data stream?") but you must consider that a data stream which is valid using one codec algorithm may cause a fault using another codec algorithm."

      But isn't that precisely what object orientation was invented to solve? To find a way of unifying data transfer between absolutely everything, everywhere, by sending not raw data but objects which could then be queried to ask things like 'what kind of thing are you?' and 'give me your data in Format X, Y or Z which I can read'.

      Drag and drop to me is one of the acid tests of 'do you actually have a functioning object model?' And pretty much every GUI OS, including Windows and OSX, fails this: drag and drop works in many places, if the developers have jumped through hoops to but not all; there's no way to universally query ANY object and do stuff with it. The only exception I can think of is, perhaps, Smalltalk/Squeak (the original OO system) with its direct-object-manipulation interface.

      Why didn't the promise of OO happen? We got COM objects instead which seem to do almost precisely the opposite: be very brittle, add a whole layer of complexity, and only make sense inside huge frameworks which can't be split up into objects. C++ seems to be the anti-Smalltalk in almsot every way and yet it still gets to be called 'object oriented'. How did we allow such confusion of language?

      I don't agree that the answer is 'drag and drop is far too complicated and you shouldn't be trying to do that'. We should say 'hey, this poses interesting questions about why our fundamental operating system models are, in 2009, still broken even by 1979 standards.'

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    5. Re:Drag'n'drop by Anonymous Coward · · Score: 0

      SmallTalk is not the original OO system. Alan Kay is known to have written an object system for Lisp before SmallTalk. An object system is just a fancy function combinator, after all.

    6. Re:Drag'n'drop by Coward+Anonymous · · Score: 4, Insightful

      What drivel. Drag'n'Drop is the shortcut equivalent of 'Save File' in program 1, 'Open File' in program 2. It's a bunch of o' bytes. It makes absolutely no difference if the bytes come through the Drag'n'Drop route or through a file.

    7. Re:Drag'n'drop by dubl-u · · Score: 4, Insightful

      Why didn't the promise of OO happen?

      I wasn't around for it. But I'd say it's just another example of cargo cult programming.

      It's much easier to say you're doing something, and maybe to observe some of the rituals, than to actually do the work. A lot of people working in OO languages don't even know what constitutes real OO. And I don't blame them; most intro Java books, for example, just give little snippets of procedural code with an occasional OO gloss.

      You can see the same pattern happening today with Agile development. Some people get great results by deeply changing how they work. Others hear about it, adopt a fraction of it, and still see improvement. Then a lot of other people jump on the bandwagon, watering it down to the point where it's worthless, but in the meantime turning a big profit on certification, training, and consulting.

    8. Re:Drag'n'drop by Jah-Wren+Ryel · · Score: 1

      subtrac hominem

      --
      When information is power, privacy is freedom.
    9. Re:Drag'n'drop by Anonymous Coward · · Score: 0

      Except it does, because a drag'n'drop recipient should be able to call methods on the object that are defined by the sender. It *shouldn't* just be a bunch of bytes. Treating it as such is part of the problem.

    10. Re:Drag'n'drop by DamnStupidElf · · Score: 1

      Problem: You copy an object from a web page, and its only action is "format hard disk when pasted anywhere".

    11. Re:Drag'n'drop by RegularFry · · Score: 1

      Hm. That was me. Not sure why that posted AC.

      --
      Reality is the ultimate Rorschach.
    12. Re:Drag'n'drop by CrashNBrn · · Score: 1

      An action/simulation of copy/paste would resolve most of this (in Windows at least).

      In nearly any instance I can think of, you are either:
      1) (Works Always ) Dragging a File to another App.
      2) (Works Sometimes) Dragging Selected (Formatted) Text to another App.
      3) (Works Sometimes) Dragging a Selected Object
      )) Either an embedded object like in an Editor.
      )) Or An embedded element, i.e. image in a browser.

      In almost all the cases above, copy/paste will work, and drag&drop may or may not work. When text/objects are copied to the (windows) clipboard a lot of additional information (formatting or mime info) is included - this can be seen in any number of ClipBoard Content viewers.

    13. Re:Drag'n'drop by Anonymous Coward · · Score: 0

      Because you love the Cox

    14. Re:Drag'n'drop by samjam · · Score: 1

      Drag and drop is little more than copy and paste which shares all of the associated problems.

    15. Re:Drag'n'drop by jimicus · · Score: 1

      Which demonstrates oh-so-nicely the state of Linux on the desktop.

      Desktop User: I want to be able to drag and drop between any arbitrary application. Is that so hard?
      Dev: Well, yes it is actually.
      Desktop User: Microsoft and Apple have been doing it for over 10 years.
      Dev: Off you go then. Use one of those.

      (On a side note: I don't debate that it is a security chasm but somehow I doubt Microsoft or Apple really care that much about it. I daresay a determined attacker could find loads of holes in that little aspect of the desktop but they wouldn't be easily remotely exploitable. In the real world, it may be better to worry about security holes which are actually likely to have an impact and to design systems so the impact of any given issue is minimised rather than spending ages fretting over hypothetical issues which haven't even been tested in practise)

    16. Re:Drag'n'drop by Anonymous Coward · · Score: 0

      "Combine that with the difference in conceptual organization--F/OSS guys don't get paid to go to in house meetings together--and it is completely logical that something as "simple" as drag and drop is not implemented across largely unrelated application development groups."

      Do you actually mean to say "F/OSS is not capable of delivering the basic functionality users require? That the organization doesn't work, that the technical challenges are beyond them?

    17. Re:Drag'n'drop by Anonymous Coward · · Score: 0

      Thank you for not attempting to argue "drag and drop" is an unnecessary feature.

      but you must consider that a data stream which is valid using one codec algorithm may cause a fault using another codec algorithm

      Then your codec(s) are broken and should be fixed. Data is either valid, or it is not. The real reason something simple like drag and drop (it is *very* simple if you use a good UI toolkit like Cocoa) doesn't work in Linux has nothing to do with security, and everything to do with X11 not including this functionality in the original design, leaving each user interface toolkit to implement its own method, which of course don't work well (or at all) with other toolkits. Sometimes diversity sucks.

    18. Re:Drag'n'drop by fractoid · · Score: 1

      I think possibly you're confusing the user interface paradigm of 'drag and drop' (ie. you click on something, drag it to another application, and that application should do something semi-intelligent with it like open it) and the programming architecture for 'object linking and embedding' (or ActiveX as the whippersnappers call it these days). Drag and drop doesn't require any kind of intelligent embedding, it's just a different clipboard-type action. Embedding generic objects, of course, requires the sort of architecture that ActiveX uses.

      --
      Rampant carbon sequestration destroyed the Dinosaurs' tropical paradise. I'm here to help repair the damage.
    19. Re:Drag'n'drop by DarkOx · · Score: 1

      You are right about the original promise of OO. The trouble is it really got going about the same time the world started getting connected. Suddenly lots of people had lots of stuff floating around that you really could not trust.

      If you pass me some data structure Its much more manageable for the programmer than an object. Its possible though proven far from trivial, I can write a parser that will not crash and not be exploited no matter what data you send in however badly corrupted, intentionally or otherwise. I can then write a program around it that will no do something the user won't like when it encounters bad data.

      If you hand me an object then I have data and executable code. Its pretty hard for me to know whats going to happen. Even if some MMU and threading tricks were used to keep your code only executing on the data in the object there are still a huge number of risks. One would need to do input validation all the output of all the agreeded upon generic interfaces in the object model. Then if you have a generic that say returns pointers to object specific functions you have to check what those are going to do. Again even if you keep it trapped in some small memory sandbox, you can still get DOSed, how do you know the code ever returns, what if it has a halt instruction? It might be you can get around these and other security issues with a software interrupt to break out after some value of to much time elapses, or built and entire java like VM to run th e object in. It gets really complex really fast, any time you think about bringing outside code under the umbrella of your process.

      COM sorta works like what I described above and as you stated its brittle. Interprocess OO made sense in the LAB its to risky in the real world most of the time.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    20. Re:Drag'n'drop by julesh · · Score: 2, Informative

      But isn't that precisely what object orientation was invented to solve? To find a way of unifying data transfer between absolutely everything, everywhere, by sending not raw data but objects which could then be queried to ask things like 'what kind of thing are you?' and 'give me your data in Format X, Y or Z which I can read'.

      Object orientation does solve this, but only for systems that can share objects with each other. The problem is that, typically at least, objects are represented as a data structure in memory that has, among other things, pointers to code to execute in response to different messages. To execute a method, we find the correct pointer, call that code and pass it a pointer to the object whose method it is. This is by far the most efficient way of implementing objects, so it is almost universally used.

      The downside to this implementation is that objects depend on a specific memory map, i.e. they are process specific. You can't just rip an object out of one process and send it to another, you have to serialize it and deserialize it along the way, and the receiving process has to know about that object's class because it has to have access to its methods' code as well the object's data. There are three general solutions to moving objects from one application to another:

      1. Run all applications in the same address space/virtual machine. This is the approach that Smalltalk took, and is also done today in some research systems (Microsoft's Singularity springs to mind, but there are others too... and I think Singularity prevents objects being transferred between running processes for its own subtly different reasons, IRRC). It isn't done in mainstream operating systems because there are a few serious downsides:
        • All applications must be written in languages that are compatible with each other's object representation. In most cases where systems like this have been implemented, there is only a single language available.
        • In order to meet the process isolation requirements that we have of modern operating systems (i.e. a failure in one application doesn't cause the entire system to fail) the language _must_ be both type safe and memory safe (i.e. memory used by an object of one type cannot be reused by an object of another type while there is a live pointer to that memory in the system). Memory safe languages almost always do not offer explicit memory management, as the two features are extremely difficult to combine. Some operations are less efficient in type safe environments. Consequently, such environments usually offer poor responsiveness and are not suitable for realtime uses. People avoid such environments.
        • If you don't have a type safe environment, or your type system does not offer protection of private elements and a means to prevent subclassing, it is impossible to implement a secure system. Any running application can interfere with any other running application at will. Smalltalk suffers from this problem: any code running on a smalltalk system can perform any operation it is possible to perform on the system. Smalltalk cannot provide isolation of multiple security domains.
      2. Provide a remote method invocation framework. Objects are held in a server process that receives messages from client processes and invokes operations on the object in response to them. Such systems are generally cumbersome to work with, requiring a lot of developer overhead in most cases. COM, which Windows' drag & drop is based on, uses this approach.
      3. Serialize the object, deserialize it in the recipient, and provide a copy of the object's methods in a form which can be linked on demand into the recipient. Windows implements this in the form of OLE, an extension of COM, which some drag and drop applications support (e.g. MS Office). The problem with this is that the requirements are extremely complicated so few developers bother registering their objects as OLE-capable. It just isn't worth the effort.
      4. I'm not sur

    21. Re:Drag'n'drop by TorKlingberg · · Score: 1

      Windows has a lot of security problems, but has any system ever been compromised through drag and drop? Is this a real security concern? Sure, if GIMP has a bug then a malicious image dragged from Firefox could exploit the bug to run code. But how is this different from saving the same file to disk in Firefox and opening in GIMP?

    22. Re:Drag'n'drop by AmiMoJo · · Score: 1

      Add to that OO not really being designed for drag&drop anyway. OO is about being able to treat objects as black boxes in your code, re-using code as much as possible and organising things in a way more like how real world organisations are.

      The solution to drag and drop is for the OS to convert between formats for the applications, and to do sanity and security checking along the way. Say the user drags and image from one app to another, the OS takes the image, if necessary converts it to a baseline format (say raw 24bit/pixel data) which all apps are expected to deal with, sanity checks it (maximum size etc) and passes it to the receiving app. It's not as clever as some solutions but it's robust and as secure as possible. As long as you pick good baseline formats, especially for things like rich text, it does what the user expects.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    23. Re:Drag'n'drop by Anonymous Coward · · Score: 0

      1) (Works Always ) Dragging a File to another App.

      Except that you're not interacting with the application - you're interacting only with explorer.exe, which at the very least, simulates object orientedness in the user interface. When you drop the object, explorer.exe then just generates a command line using the full path of the object and attempts to start the application with that. Couldn't be much less OO in my opinion.

       

      In almost all the cases above, copy/paste will work, and drag&drop may or may not work. When text/objects are copied to the (windows) clipboard a lot of additional information (formatting or mime info) is included - this can be seen in any number of ClipBoard Content viewers.

      I agree, but that's really just metadata, it's not true OO.

      Posting anonymously because I've already moderated.

    24. Re:Drag'n'drop by BitZtream · · Score: 1

      I'm sorry but that has got to be the lamest excuse for something not working I have ever heard of. If 'it might cause someone elses software to have a security issue' is a valid reason for not allowing drag and drop of an image, plain text or any other basic format then you need to get out of the OS business and stop pretending to be in it.

      My software doesn't need to know anything about the software that is providing the input to the drag and drop, it just has to make sure its safe for itself. If GIMP can read a jpeg or a bitmap in from the file system then it can take it from a memory buffer or file for the DnD operation. If there is a bug in the software it can in almost every case be exploited from the file system as well.

      If you want to play with the big boys and be a real OS then this sort of retarded, bullshit, childish excuses won't cut it. You post indicates you've never dealt with drag and drop code on any operating system. The whole copy/paste/clipboard concept is what, 40 years old? Atleast 30. Is text the only thing you can handle?

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    25. Re:Drag'n'drop by ResidentSourcerer · · Score: 1

      I don't understand:

      What is the difference between dropping a file and opening a file? E.g. If I drag and drop a "flibbit" from firefox onto Gimp, or save the flibbit as a file, then try to open it. If gimp understands flibbits, it opens it. If gimp doesn't understand flibbits it gives you a fuss message.

      D&D could be implemented by the receiving application taking any dropped item, save it to a file, then open it.

      Obviously I'm missing something here. Pelase educate me.

      --
      Third Career: Tree Farmer Second Career: Computer Geek First Career: Teacher, Outdoor Instructor, Photographer.
    26. Re:Drag'n'drop by jgrahn · · Score: 1

      What drivel. Drag'n'Drop is the shortcut equivalent of 'Save File' in program 1, 'Open File' in program 2. It's a bunch of o' bytes. It makes absolutely no difference if the bytes come through the Drag'n'Drop route or through a file.

      More or less. There should be something like "Hey, clipboard: give me your stuff as an image/as plain text/as foo" with just one or two data formats for each data type. You would want to paste text from a web browser as a bitmap into a bitmap editor, but as plain text into a text editor.

      This is, IIRC, how the X11 clipboard works.

    27. Re:Drag'n'drop by Zalbik · · Score: 1

      Why don't I get mod points when I want them?!?!

      +1 Informative

    28. Re:Drag'n'drop by Yunzil · · Score: 1

      Once you can drag and drop one thing then you want to be able to drag and drop anything.

      Well, yes.

      With so much of the problem and criticism with the reigning proprietary OS being security related the open source community has tried to remain a little more focused on security related issues. Combine that with the difference in conceptual organization--F/OSS guys don't get paid to go to in house meetings together--and it is completely logical that something as "simple" as drag and drop is not implemented across largely unrelated application development groups.

      So your argument against implementing a feature that people actually want and use on a regular basis is that it's just too hard?

    29. Re:Drag'n'drop by crhylove · · Score: 1

      GUIs are for pussies. Why isn't everyone just using the command line?!?

      --
      I hold very few opinions. I hold information based on observation and fact. If you wish to disagree, please use facts.
    30. Re:Drag'n'drop by Anonymous Coward · · Score: 0

      There is always a tradeoff between security and usability. Nothing new there. The problem is that desktop users want usability. So, why not give it to them in desktop Linux? Server-side Linux can still be quite secure. Other OS protections can prevent malicious code from causing harm before it gets to the point where it exploits drag-and-drop. But if the user can't perform basic actions quickly, what use is the OS to him?

    31. Re:Drag'n'drop by elnyka · · Score: 1

      But isn't that precisely what object orientation was invented to solve? To find a way of unifying data transfer between absolutely everything, everywhere, by sending not raw data but objects which could then be queried to ask things like 'what kind of thing are you?' and 'give me your data in Format X, Y or Z which I can read'.

      C'mon dude, you gotta be kidding me.

      Object-orientation is not by itself the answer to that problem. After all, you can have perfect OO models that exist in parallel, and which are incompatible. Object-oriented models for disparate systems mean squat for interoperability without a common, well-defined domain model. Notice that I say domain model as opposed to object model. There is a very important distinction here. In this particular case, the domain model is in respect to data communication between potentially co-located systems and the visual rendering of that communication. OO models for those systems need to be based on a universal, coherent communication domain model (OO or not). Try to pull that out with disparate teams of developers, where each band works mostly in a distributed fashion, on disparate goals, with different agendas and priorities, with no unifying time line or list of deliverable for all these teams. Furthermore, with time and effort being on a volunteering basis, individual and team drive is based in large part by ego and ideology, and all of that without having a well-defined set of stake holders.

      Object orientation is not intended to solve this. You can't have that in such a largely distributed, volunteer/ego driven environment without establishing rigid communication protocols, time lines and set of deliverables. In the private sector we sometimes (in fact, many times) see failures of implementing functionally sound object models because of a lack of communication between competing groups of stake holders (developers, users, et al.) The F/OSS development model is prone to exacerbate this.

      You are trying to explain the absence of something from the point of view of conceptual models, an object model in this case. But in reality, those models can only come to fruition with the establishment of communication and enforcement models. You can't put the wagon ahead of the oxen bro.

    32. Re:Drag'n'drop by Anonymous Coward · · Score: 0

      Um... how about:

      1. Right click > view image
      2. Right click > copy image
      3. In GIMP: Edit > Paste

      Duh.

    33. Re:Drag'n'drop by Anonymous Coward · · Score: 0

      Drag and drop is quite convenient. It is also a security chasm. Once you can drag and drop one thing then you want to be able to drag and drop anything. In the case of arbitrary file formats not only must you implement code to check the incoming data stream (thus exposing yourself to all of the security considerations of "how many different ways can someone try to wax my process of checking the incoming data stream?") but you must consider that a data stream which is valid using one codec algorithm may cause a fault using another codec algorithm. Competing algorithms exist for many data format structures and the presumed same data format may have three or four codecs at use between X, the WM, a monolithic app like a web browser, and a devoted data editor (eg. GIMP), and even a devoted data viewer (eg. a multiformat display application). It isn't the simplest consideration.

      How is that all different to when you are simply OPENING a document/file (at startup or later from the app UI)? You still have the very same problems of format verification / sanity checking. If you have code to solve those, it's relatively trivial to apply it to the datastream received from d'n'd; if you don't care, the app is borken anyway and d'n'd doesn't make it really worse.

    34. Re:Drag'n'drop by kelnos · · Score: 1

      How does all that solve the problem of a malicious application injecting something nasty into the drop site? It could perfectly well say "I am an image object," and when the app says "give me your image data as a JPEG," it gives it specially-crafted data that exploits a vulnerability in an image decoder. Whether or not the interfaces are OO or not have nothing to do with this.

      Not saying your model doesn't make a whole lot of sense. It does. But it doesn't remove the need to do input validation. (Not that I really buy the parent's claim that lack of a desire to do good input validation is the reason we don't have decent, universal DnD support, but that's another issue.)

      --
      Xfce: Lighter than some, heavier than others. Just right.
  68. Why is the TTY subsystem still in the kernel? by Animats · · Score: 2, Interesting

    I'm surprised that the TTY subsystem is still in the kernel. By now, it ought to be in user space. It's rare today that a serial port is attached to an actual terminal (let alone a real Teletype), and separating the serial port driver from all the backspacing and line handling stuff would make both parts simpler. Most of the time, the TTY stuff in the kernel just gets in the way of other uses of serial ports.

    They've been separated in QNX for a decade, for example.

    1. Re:Why is the TTY subsystem still in the kernel? by Ant+P. · · Score: 1

      It already is, as far as I can tell. Or at least, I couldn't figure out how to access a remote serial console without installing minicom first.

    2. Re:Why is the TTY subsystem still in the kernel? by yuhong · · Score: 1

      It already is, as far as I can tell. Or at least, I couldn't figure out how to access a remote serial console without installing minicom first.

      Well, minicom is the *client*, where the TTY subsystem they were talking about was the *server*.

  69. hmmm... by toby · · Score: 1

    1) Reiser 3 is quite mature
    2) once R3 was complete and production-ready it made perfect sense for Hans to put his resources into the more interesting Reiser 4
    3) why isn't Reiser 4 in the damn kernel already?

    --
    you had me at #!
    1. Re:hmmm... by UnrefinedLayman · · Score: 5, Funny

      3) why isn't Reiser 4 in the damn kernel already?

      I'm ready to scream bloody murder over it not being included yet.

    2. Re:hmmm... by Wonko+the+Sane · · Score: 1

      I was most interested in the universal metadata storage via the "files are also directories" idea but it seems like it's been killed permanently.

      He probably could have gotten that in if he would have agreed to make an xattr compatability layer (also that whole murder thing)

    3. Re:hmmm... by ioshhdflwuegfh · · Score: 1

      3) why isn't Reiser 4 in the damn kernel already?

      ditto ZFS.

    4. Re:hmmm... by TheLink · · Score: 4, Funny

      > why isn't Reiser 4 in the damn kernel already?

      Vendor lock-in.

      --
    5. Re:hmmm... by Anonymous Coward · · Score: 0

      Perhaps because he's a convicted murderer?

      http://en.wikipedia.org/wiki/Hans_Reiser

    6. Re:hmmm... by geminidomino · · Score: 1

      > why isn't Reiser 4 in the damn kernel already?

      Vendor lock-in.

      You asshole. I almost choked to death stopping myself from spewing coffee all over my laptop. :D

    7. Re:hmmm... by True+Grit · · Score: 1

      3) why isn't Reiser 4 in the damn kernel already?

      ditto ZFS.

      For ZFS, its easy: its current license isn't compatible with the GPLv2 that the Linux kernel uses.

      As for R4, well, thats a little more... complicated. :)

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

      Vendor lock-in.

      Err, you mean lock-down.

  70. Re:Hey guys by Anonymous Coward · · Score: 0

    It just takes one heroic mod to prevent casual users or Google searchers from having their time wasted. You can post as much drivel as you want, the Slashdot moderation system is much more effective than your tomfoolery. You're only seen by people who purposely browse at -1 for amusement or to hide you from others. See, you're already gone. Poof! And I make up for my small dick by spending part of my rather large salary on lots and lots of really high class hookers. Come on now, post more like you said - if you're lucky, it'll be seen by someone who isn't looking for it, not me though. Sorry.

  71. Re:Slashdotted - Google Cache the real links by Beetle+B. · · Score: 3, Funny

    You know what really gets on my nerves? When people say they no longer care, when in reality they do. If he really didn't care, he would have typed the first sentence and stopped.

    Please talk to the moderators at Slashdot. I no longer care.

    --
    Beetle B.
  72. wow by toby · · Score: 1

    that formatting sucked.

    --
    you had me at #!
    1. Re:wow by ioshhdflwuegfh · · Score: 1

      > wasn't properly overloaded.

  73. *cough* by toby · · Score: 4, Insightful

    Solaris :)

    --
    you had me at #!
    1. Re:*cough* by TheRaven64 · · Score: 1

      Just because FreeBSD has a solaris.ko kernel module doesn't mean that you're really using Solaris...

      Seriously though, if you're using Solaris, you're using a big chunk of BSD code. If you're running FreeBSD, you may well be using a chunk of Solaris code too.

      --
      I am TheRaven on Soylent News
  74. Hoax? by mrwolf007 · · Score: 1

    Sorry, but i have to ask.
    I'm a subscriber of the lkml. Yeah, i usually delete the msgs after 2 months.
    Why cant i find a single of those messages in my own personal copy of the lkml group?
    Was this in some kind of subgroup or what?

    1. Re:Hoax? by godrik · · Score: 1

      I do not know, but the mails are clearly present on the lkml website. (BTW, the /. effect is gone)

    2. Re:Hoax? by mrwolf007 · · Score: 1

      Hmm, might have aproblem with evolution.
      For some reason i havent got any messages since 28.May 11:44 on lkml.
      Weird coincidence, guess ill have to to check the mta.

  75. The jury's still out on whether he screwed up by pem · · Score: 1

    I know this is off-topic, but:

    He wrangled himself an invitation to the White House for a beer.

    This was his idea, suggested to Obama -- he's not going to apologize, but he says "we should all get together over a beer." He KNOWS that it will be really hard for Gates to proceed with the lawsuit without looking like a douchebag, after sitting down with him. This is a better non-apology apology than Obama's, from someone who really ought to be apologizing.

    He got his union to pay for the trip.

    He'll probably do very well on the right-wing travel circuit, because unlike Joe the non-plumber plumber, he is, in fact, a real cop.

    So, basically, he was as much of an asshole as he ever was, he got the cops to all get together and sing the hymn about how he was a fine, upstanding asshole, and he probably keeps to get doing it, with everybody now KNOWING not to mess with him, or any other cop in Cambridge.

    When I try to look at it from his purely personal, Machiavellian perspective, I'm not seeing the screwup yet.

  76. I'm pretty sure they're already separate... by argent · · Score: 2, Informative

    Surely the TTY code isn't part of the serial driver subsystem? What the tty subsystem handles is line discipline, and that can be applied to any number of serial interfaces, both physical (serial ports) and virtual (sockets). If you talk to the serial port RAW there shouldn't be a line discipline involved.

    (the issue of whether they're in the "kernel" or not is a separate issue, QNX being a microkernel being "in the kernel" there is kind of meaningless)

  77. Re:Slashdotted - Google Cache the real links by Anonymous Coward · · Score: 0

    He probably still cares but doesnt really want to care and is trying to convince himself.......the end result will be that he doesnt care. He's thinking ahead...like all good programmers :)

    If you wanna be a knight, act like one

  78. He's still posting.... by yossarianuk · · Score: 1

    After those 2 emails mentioned in the post he has posted various messages today (29th July) . I'm not so sure he has quit just yet,,,

    http://lkml.org/lkml/2009/7/29/272
    http://lkml.org/lkml/2009/7/29/290

    1. Re:He's still posting.... by yossarianuk · · Score: 3, Informative

      Ignore my post (can I mod myself down ??) .... He has left tty maintainer, but is still posting on the kernel mailing list. I hope he re-considers talent like his is rare .

  79. Re:Slashdotted - Google Cache the real links by lawpoop · · Score: 2, Insightful

    "Please talk to the new tty maintainer whoever that ends up. I no longer care."

    You know what really gets on my nerves? When people say they no longer care, when in reality they do. If he really didn't care, he would have typed the first sentence and stopped.

    You know what I find entertaining? People who are smart enough to see through a fairly transparent dysfunctional coping mechanism, and then continue to let it bother them after they've encountered it for the nth time. "Hey, he really does care! He's *lying* to us..."

    --
    Computers are useless. They can only give you answers.
    -- Pablo Picasso
  80. I'm not surprised.... by CompletelyCluless · · Score: 1

    I'm not surprised. Linus Torvalds comes across as a complete arse-hole (In that email at least).

  81. Re:Slashdotted - Google Cache the real links by Anonymous Coward · · Score: 0

    you know what really gets on my nerves? when people claim people don't mean what they said based only on the fact that they said it.

    the first sentance directs the person away. the second sentance acknowledges that the person was correct in asking him, as he was the person who used to care, but he no longer does...

    you are an idiot.

  82. Especially if he wanted to work on the tty code by tlambert · · Score: 4, Funny

    "If Alan Cox wanted to work at Apple, it would take 1 phone call."

    Especially if he wanted to work on the tty code.

    -- Terry

    1. Re:Especially if he wanted to work on the tty code by Anonymous Coward · · Score: 0

      *golf clap*

    2. Re:Especially if he wanted to work on the tty code by Zaurus · · Score: 3, Informative

      Parent post should be modded insightful or something, not funny.

      Terry Lambert is an actual Apple employee who, if I'm not mistaken, could quite honestly hire people like Alan to work on the "unix" portions of OS X. He's quite active on Apple's Darwin Kernel mailing list.

  83. This is ... by SlashDev · · Score: 2

    ... very common amongst programmers, especially excellent programmers. I can see both points of view, one (Linus) who wants to get this done as quickly as possible, machine-like, because he believes that the fix is quick and simple, the other (Alan) wants to dissect the problem, diagnose, understands it, and fix it. It's unfortunate that Alan made that decision, but I think Linus's last email was pushing him towards making it, he was clearly mad; that being said I have one thing to say, from a programmer's perspective: You cannot force a system programmer to think a certain way, do things the way you want them to do, not Alan Cox anyways. Linus's behavior is reminiscent of corporations who employ programmers to write functions (or sub-routines as some call them), all day long, "just do it, don't argue if it is right or wrong".

    --

    TOP DSLR Cameras Reviews of the top DSLRs
  84. What does this say about Linus? by kilgortrout · · Score: 0, Offtopic

    That he's a Cox shucker!!

  85. Re:Alen doesn't give a shit what you think. by larry+bagina · · Score: 1

    those grapes were probably sour anyway.

    --
    Do you even lift?

    These aren't the 'roids you're looking for.

  86. Re:Slashdotted - Google Cache the real links by Anonymous Coward · · Score: 0

    Just remember, at some point we're all children...

  87. Looks like I'm the dissident by hrimhari · · Score: 2, Informative

    I went to read the thread from around the message pointed by the article.

    What I saw was a nervous breakdown from Mr. Cox because he had too much pressure on him and wasn't able to accept that his proposal was less optimal than that from others. See: http://lkml.org/lkml/2009/7/28/612

    Mr. Cox finally comes to reason: http://lkml.org/lkml/2009/7/29/108

    Considering the discussion going on from http://lkml.org/lkml/2009/7/29/276 , maybe Mr. Cox will reconsider.

    I don't know about other issues, but I wouldn't be too fast to point the finger at Mr. Torvalds in this case.

    --
    http://dilbert.com/2010-12-13
    1. Re:Looks like I'm the dissident by Eravnrekaree · · Score: 1

      Torvalds was probably right. It would be bad to break applications and this creates a huge headache for users and really leads to a nightmare for the OSs users.

  88. Thank you, Alan! by Progman3K · · Score: 2, Insightful

    If everyone contributed as much of their time as you have, the (open-source) world would be a better place.
    Thank you.

    --
    I don't know the meaning of the word 'don't' - J
  89. Re:Slashdotted - Google Cache the real links by jdogalt · · Score: 1

    "Linux is a great product, and that is the result of the magnificent work of all the coders and contributers. But sometimes they just act like children."

    When used in this sense, it is equally valid to say that everyone on the planet acts like children. Really, it is the control freaks that are good at repressing their inner child that worry me the most. They come off as professional, work their way into positions of real power an authority, and then you discover how much they can _really_ screw things up for the rest of us.

    I for one am reassured by Obama's stupid 'stupid' comment. Sure, it was stupid of him, but it convinces me he isn't going to do anything WW3 level stupid because he can no longer repress every natural aspect of his human nature.

  90. both wrong by buddyglass · · Score: 4, Insightful

    Assuming what Linus said is true, about Alan blaming user land code for problems he was responsible for, then Alan was clearly in the wrong. However, Linus is wrong to have taken him to task in such a public forum. If he had any sense, he'd have done it privately, and Alan Cox would probably still be the maintainer. There's more to managing people than simply "being right".

    1. Re:both wrong by segedunum · · Score: 1

      However, Linus is wrong to have taken him to task in such a public forum. If he had any sense, he'd have done it privately, and Alan Cox would probably still be the maintainer. There's more to managing people than simply "being right".

      No. In an open, public project you must have what's going on out in the open for all to see, warts and all. Linus also does not 'manage' anyone. Once you start having private discussions and disagreements about what was a public bug and a public problem involving others in the name of political correctness then that whole process starts to break down.

    2. Re:both wrong by syphax · · Score: 1

      Maybe Linus wanted a new maintainer. It's hard to fire people from volunteer posts, so one must resort to other methods...

      --
      Simple Unexpected Concrete Credible Emotional Stories
  91. Re:Slashdotted - Google Cache the real links by ioshhdflwuegfh · · Score: 1

    To be fair, "I no longer care" is shorthand for the closely related "I no longer care enough to put up with the criticism" which is just a statement of cost/benefit analysis. He does care, but not enough to keep going, and that roughly approximates "I don't care".

    I think you are right, I mean not exactly right, just roughly. You are basically not enough wrong to be wrong, just enough right to take your analysis almost seriously.

  92. Re:Sounds like Linus T. was being Edison (to Tesla by Anonymous Coward · · Score: 1, Funny

    +1 Barking Mad?

  93. He's left the kernel before (2003) by yossarianuk · · Score: 2, Interesting

    In 2003 Alan cox stopped kernel development for a year whilst he learnt Welsh.

    http://kerneltrap.org/node/759

    It seems he left with little notice then (although he was maintaining the older kernel - 2.2) . Kernel development still continued in his absence....

    1. Re:He's left the kernel before (2003) by syphax · · Score: 1

      If I were him, I would've resigned in Welsh, just to screw with people.

      --
      Simple Unexpected Concrete Credible Emotional Stories
  94. Re:Slashdotted - Google Cache the real links by squizzar · · Score: 5, Insightful

    I sometimes wonder if it's the very public nature of Linux (and much open source) development that gives that creates this impression of everyone acting like children. I've heard plenty of people describing working environments (no matter the expertise) that sound exactly the same as this, it's just that no one outside the company will ever see it. It's kind of a software development soap opera...

  95. That should be settled over a Beer by droopycom · · Score: 1

    This just seem like a misunderstanding, what they really need is to talk it over a beer. President Obama is already busy with its own beers tomorrow, so we need to find another host ... any volunteer ?

    Theo ?
    RMS ?
    Eric Raymond ? ...

  96. Re:Slashdotted - Google Cache the real links by moderatorrater · · Score: 1

    When people say they no longer care, when in reality they do. If he really didn't care, he would have typed the first sentence and stopped.

    You know what I hate? People who get on soapboxes and criticize others when the criticism is obviously not valid.

    Mr. Cox no longer cares about the TTY bugs; he still cares about being polite to those who address him. The statements are in no way contradictory.

  97. Re:Slashdotted - Google Cache the real links by Anonymous Coward · · Score: 0

    Maybe he s just telling the truth, you know, like when one stop smoking or using MS products.
    Also, he may keep on contributing.

    And stop telling ppl they act like children when they do smth you don t approve, it s stupid
    Thank you very much

  98. Different Alan Cox by Rix · · Score: 1

    That is another person with the name Alan Cox.

  99. Interpersonal problems derail projects by skeptictank · · Score: 4, Insightful

    far more often than technical challenges. This incident provides an enlightening view into Linux development. Working for someone with the social skills of a 13 year old girl, who doesn't actually pay you, never ends well.

  100. back in 1938 by transporter_ii · · Score: 4, Funny

    Back in 1938, a massive alien invasion took place in Grover's Mills, New Jersey -- during Orson Welles' famous "War of the Worlds" broadcast about Martians. Maybe it wasn't a hoax? Applications were discovered for social security cards from a list of men with no backgrounds -- all named Cox:

    Alan Cox
    John Big Cox
    Dewey Cox
    Dixon Cox
    Ima Cox

    .

    --
    Doctors destroy health, lawyers destroy justice, universities destroy knowledge, religion destroys spirituality
    1. Re:back in 1938 by gbarules2999 · · Score: 1

      Doctor Perry Cox

    2. Re:back in 1938 by Anonymous Coward · · Score: 0

      Rambone "Cableguy" Cox
      Laundry Cox
      Perty P. Cox
      Belladonna Westly Cox
      Haggley Cox
      Snape Cox
      Ivan Blumensmart Cox
      Beeble Cox
      Linus Toreballs Cox ...

      Kathleen Coxalot Fent-Malda

    3. Re:back in 1938 by raju1kabir · · Score: 1

      Also found:

      John Smallberries
      John Whorfin
      John Bigbooté

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    4. Re:back in 1938 by vintagepc · · Score: 1

      What about Ima's russian sister, Yura Cox? (Dont get me started... too many bad jokes here...)

      --
      Evolution - Est. 4500000000 B.C. Don't piss in the gene pool.
    5. Re:back in 1938 by ekimminau · · Score: 1

      Back in 1938, a massive alien invasion took place in Grover's Mills, New Jersey -- during Orson Welles' famous "War of the Worlds" broadcast about Martians. Maybe it wasn't a hoax? Applications were discovered for social security cards from a list of men with no backgrounds -- all named Cox:

      Alan Cox John Big Cox Dewey Cox Dixon Cox Ima Cox

      .

      May I pass along my congratulations for your great interdimensional breakthrough. I am sure, in the miserable annals of the Earth, you will be duly enshrined. Laugh-a while you can, monkey-boy.

      --
      Armaments, 2-9-21 And Saint Attila raised the hand grenade up on high, saying, 'O Lord, bless this Thy hand grenade' N
  101. Re:Hey by causality · · Score: 1

    Why is modding the truth considered "a troll". They are both acting like girls.

    I often see some very low-quality moderation but I don't think this is an example of it. I'll explain why the GP was trollish.

    Perhaps because to say that is to dismiss the basis of the conflict, not by showing it to be invalid or by proposing a means of reconciliation but by trivializing it.

    I'm a man so I have to use guesswork to answer another aspect of this question. I would guess that the above would look quite trollish to any woman who can conduct herself in a mature and intelligent fashion, due to the implication that the only reason why two men would have a conflict is because they resemble females. Although, I balance that with the knowledge that the intelligent women I have known all had one thing in common: they had more contempt for the petty/catty behavior exhibited by less-intelligent women than any man I have ever met, sometimes going so far as to say that they give all women a bad name by living up to stereotypes.

    --
    It is a miracle that curiosity survives formal education. - Einstein
  102. Some people are jerks. by Junta · · Score: 1

    Not all Open Source developers are jerks. In fact, I would say the proportion is no worse than closed source.

    In every thing, I would say the 'big names' often have a tendency to be a jerk at times (after all, a strong personality and great confidence plays no small role in typically becoming a 'big name', in programming or anything else for that matter).

    In the case of submitting patches, it closed source world, the argument dies out and the rejected dev has no where to go. The code dies and the developer moves on (perhaps keeping the changes and looking for things to go horribly wrong to vindicate himself with the facts play out, not that *I've* ever done that . . . ). In open source, forks can happen. forks can be good (if both sides track and take what they want, both stay of quality and the community decides ultimate viability). However, in human nature such an act is kind of taken too personally more often than not. This is part of the reason open source in general is more flexible if you pick up a distribution and roll with it. It's got all the code complexity the community could give, united behind a cohesive vision that a distributor implements. Do any of them get everything right to me, no, but some get more right than others, which is more than I can say for the completely closed stacks.

    I think in this case, Linus got carried away with initial cries of 'revert revert' without letting Alan work the problem for a reasonable time (3 days is way too soon to forcefully interject if you are truly delegating and trusting your delegation decisions). As soon as Alan pointed out the problem that was would be brought back by the revert, Linus probably should have conceded that it was worth it to invest more effort in getting it right, but it looks like it was too late and mood more than logic took over.

    One thing I will say for Linus, is that some of the arguments I've seen him engage in he is the voice of practicality. I.e., sometimes a developer gets too wrapped up in their small world of code and loses touch with what is important for the end user. I think Linus has done a decent job of not falling into that trap (too easy to do), and his initial impression reflected that. It's just that Linus hadn't realized the point of the change in the first place and underestimated the value of it.

    --
    XML is like violence. If it doesn't solve the problem, use more.
  103. Well, actually... by Anonymous Coward · · Score: 0

    Pascal is far easier to read than C (or C++).

    C/C++ won because they cared not about humans but about the processor/hardware -- which led to faster programs (at run-time).

    But Pascal was far faster to compile.

    It was designed so it would be easier to understand and superb at compilation.

    Wirth was simply a genius.

    Just to be on-topic, Alan needed a rest, so perhaps he would stop anyway; Linus needs a vacation, too -- he's been working non-stop since ever; we can't really rely on just a few people...

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

      Here's a recent interview with Mr. Wirth:

      http://www.simple-talk.com/opinion/geek-of-the-week/niklaus-wirth-geek-of-the-week/

      Though he's retired, I find his views very sensible and inspiring of new ideas.

  104. Push-out doors bad for snow and other egress by Anonymous Coward · · Score: 1, Interesting

    Also, doors should be always pulled when you go in and pushed when you go out.

    I *absolutely* agree with you when it comes to many types of doors, especially public restroom doors -- why, in the devil's briefcase, do most public restrooms have doors that you have to pull when your hands are wet from washing them? Hygienically brain dead.

    Anyway, various kinds of doors that open to the outside should not generally be push-out types. Consider residential doors opening to the outside, particularly in cold climates: if there is substantial snow on the ground, the occupants will be trapped inside. Even in not-so-cold climates, push-out doors to the outside can be too easily barricaded, again trapping people inside. Plus, as others have noted, such doors perforce have the hinges on the outside, allowing too easily for forced entry.

    Meanwhile, public buildings usually have push-out doors mandated by local fire codes, for precisely the reasons you note -- but they generally also have awnings or some other means of ensuring that snow build-up does not block the doors from opening.

    (NB: Posting anon for modding purposes.)

    Cheers,

    1. Re:Push-out doors bad for snow and other egress by mrcaseyj · · Score: 1

      High winds can generate surprisingly large forces on a door, and thereby make outward opening doors much more challenging, or even dangerous, especially for small people. The hydraulic dampers found on many commercial doors can help keep doors moving slower and safer when caught by the wind.

    2. Re:Push-out doors bad for snow and other egress by codeButcher · · Score: 1

      why, in the devil's briefcase, do most public restrooms have doors that you have to pull when your hands are wet from washing them?

      Then do as most of my colleagues do, and DON'T wash your hands - then you don't need to pull with wet hands.

      (Yeah, I know. I keep a bottle of alcohol in my drawer to wipe my keyboard and mouse whenever someone else has worked on my computer. And I avoid shaking hands.)

      --
      Free, as in your money being freed from the confines of your account.
    3. Re:Push-out doors bad for snow and other egress by manifoldronin · · Score: 2, Funny

      (Yeah, I know. I keep a bottle of alcohol in my drawer to wipe my keyboard and mouse whenever someone else has worked on my computer. And I avoid shaking hands.)

      I keep a bottle of alcohol in my drawer too!

      --
      Tyranny isn't the worst enemy of a democracy. Cynicism is.
    4. Re:Push-out doors bad for snow and other egress by codeButcher · · Score: 1

      That's what they get for telling me about "reuse" when I was taught OO. But you must admit, the part about wiping the keyboard is a good alibi.

      --
      Free, as in your money being freed from the confines of your account.
  105. And that's not all... by Anonymous Coward · · Score: 0

    Alan's work on the IP stack at Swansea made linux the network ruling monster it is today. In some ways (multi-homed hosts with multiple default routes anyone?) the SUCS stack was superior to the current stack.

    His work on the SCSI subsystem is also worthy of great respect.

    Thanks for all your hard work, Alan, I hope you will keep coding forever!!!

  106. Re:Slashdotted - Google Cache the real links by phybere · · Score: 1

    That's because in most companies (and software projects in general), there are programmers who act like children (usually due to over sized egos). Most programmers aren't like this, but those who are tend to be the most visible.

  107. MS broke backward compatibility... by tjstork · · Score: 1

    Windows H/W support from my POV is abysmal, and that is even with MS' at-all-cost backward compatibility culture.

    Didn't MS actually broke backwards compatibility with Vista, which is what pissed so many people off? They introduced a new driver system and expected hardware vendors to write to it. Many did, but legacy stuff isn't there.

    --
    This is my sig.
    1. Re:MS broke backward compatibility... by smash · · Score: 1
      They took a lot of it out of the kernel, and also re-wrote it to be multi-channel (per-app) aware.

      Given that an SB-Live for example is now about 10+ years old, Vista is not designed for 10 year old PCs, and a compatible sound card is all of about $20 - I don't see the big problem.

      Yes, yes you need to buy a new sound card. if you want to cry about it, complain to Creative.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    2. Re:MS broke backward compatibility... by tjstork · · Score: 1

      Yes, yes you need to buy a new sound card. if you want to cry about it, complain to Creative.

      Just out of curiosity, what do you really need out of a Creative sound card that you can't get out of the resident sound on a PC? I would think a quadcore PC these days could mix a mountain of channels in software...

      --
      This is my sig.
    3. Re:MS broke backward compatibility... by Rockoon · · Score: 1

      Just doing some back-of-the-envelope calculations here.. 48000 samples/second (DVD quality) * 6 channels (5.1 surround sound) * 200 sources (absurd #) = 57.6 million samples per second.

      That could be handled in a scripting language, run under an emulator. Thats right.. 200 "5.1 surround sound" channels is *trivial*, and when you consider that most anything other than movie players outputs only 2 channel sound...


      This is why hardware mixing died over 10 years ago. I remember the glory days of the Gravis UltraSound. They were short. By the time Win 3.1 rolled out, software mixing programers could do hundreds of channels on a 486.

      --
      "His name was James Damore."
    4. Re:MS broke backward compatibility... by Rockoon · · Score: 2, Interesting

      They broke it on purpose, yes.

      Remember that they were also introducing a new security model, which is one of the reasons they HAD to break it. They made that choice, for better or worse.

      --
      "His name was James Damore."
    5. Re:MS broke backward compatibility... by drsmithy · · Score: 1

      Remember that they were also introducing a new security model, which is one of the reasons they HAD to break it.

      Vista did not introduce a new security model, it improved the UI around the same security model that it's had since 1993 - and it was most certainly not the reason the audio stack was rewritten.

    6. Re:MS broke backward compatibility... by smash · · Score: 1
      Not saying you do. However, whatever processing power mixing uses, could be diverted to other purposes. Besides, simple mixing channels these days isn't all there is to audio - you've got positional 3d audio, effects processing (pitch bending, reverb, etc), etc that takes a fair bit more.

      But yes, of course - like any specialised hardware, it will eventually be replaced by quick busses and the main cpu.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    7. Re:MS broke backward compatibility... by Rockoon · · Score: 1

      Vista did not introduce a new security model, it improved the UI around the same security model that it's had since 1993

      ..you mean.. before Windows 95? Windows 3.1?

      Thats a mighty big typo.. or you're stupid (for commenting) and uninformed (for being extremely wrong.)

      and it was most certainly not the reason the audio stack was rewritten.

      Didn't say it was. Didn't mention the audio stack at all. THe person I replied to didn't mention the audio stack either. The person he had replied to did go on about SB Live drivers. Even if the audio stack wasn't rewritten, the drivers wouldn't work. New security model, you see. No drivers survived.

      --
      "His name was James Damore."
    8. Re:MS broke backward compatibility... by fuzzix · · Score: 1

      Just out of curiosity, what do you really need out of a Creative sound card that you can't get out of the resident sound on a PC? I would think a quadcore PC these days could mix a mountain of channels in software...

      I installed an old SB Live! in a new machine last year as the on board card had at least a half second latency during gaming.

      The board chipset is ATI SB600 for anyone interested. Not great.

    9. Re:MS broke backward compatibility... by drsmithy · · Score: 1

      ..you mean.. before Windows 95? Windows 3.1?

      Windows NT 3.1 was released in 1993.

      Even if the audio stack wasn't rewritten, the drivers wouldn't work. New security model, you see. No drivers survived.

      Several types of XP drivers will work in Vista - printers, video (in a compatibility mode), etc.

      The (audio) driver breakage had nothing to with a changing security model and everything to do with significant subsystems (like the audio stack) being completely redesigned.

      What do you think changed in the security model that broke drivers ?

    10. Re:MS broke backward compatibility... by Chris+Mattern · · Score: 1

      Remember that they were also introducing a new security model, which is one of the reasons they HAD to break it.

      No, the reason they HAD to break it was that they were introducing a new DRM model. Not the same thing.

    11. Re:MS broke backward compatibility... by Chris+Mattern · · Score: 1

      Remember that they were also introducing a new security model, which is one of the reasons they HAD to break it.

      No, the reason they HAD to break it was that they were introducing a new DRM model. Not the same thing at all.

  108. You're off-topic as usual, Mr. Troll by Anonymous Coward · · Score: 0

    "+1 Barking Mad?" - by Anonymous Coward on Wednesday July 29, @07:09PM (#28875201)

    WoW - I must have REALLY gotten to you @ some point, & with your own technical mistakes in some techno debate, which I'd guarantee you only brought on yourself no less, & totally did so, & you made yourself look like "$heet" here, is all I can figure, & this is your sick game of "pay back", lmao - 'enjoy it', lol!

    (Also? Well - I really don't think you understand 1 thing - Face it: You can't "pi$$ on my parade" or "rattle me in MY game", & that's that - it's "TOO easy")...

    BOITOM-LINE, is this:

    I've been watching you "track me" for weeks now, posting replies as AC, & what w/ your constant "modding me down" via your registered sock puppet account(s) you use to do so... (& even your impersonating me as well in various postings also).

    (AND, as-per-usual? Just more posting your wise-ass off topic replies as AC, after your registered account mod down of my posts quite frequently... others here see it as well)

    LOL: Hey - right now? Well - I am TRYING to figure out your "end game" (which, it appears to myself thusfar, that you're trying to collect up as many "mod downs" as you can on me, which YOU often "administer" yourself no doubt) What a colossal WASTE of time, & your mod points, on your part - That won't help you much, considering I have way, Way, Way over 120++ or so by now (&, anyone can see your "points" are pure b.s. that's off-topic, every time).

    Good luck w/ that, IF that's your "plan" here - I say that, simply because anyone can read the replies before & afterwards (relative to YOUR b.s. posts), & figure out your psychotic/sociopathic near constant stalking of myself, for almost a month or more here now. I have you bookmarked in a special folder in fact, if this is your "master plan"? LOL... so, that ought to be "good for a laugh", when it all "comes to a head"... & eventually? It will.

    (Who do you think you are fooling?)

    APK

    P.S.=> 10 steps ahead of you, everytime... you would be a LOUSY "Field General" or Chess Player imo @ least... you're VERY predictable, obvious, & always, off topic! apk

  109. Linus' Attitude by bsdhacker · · Score: 1

    Linus' responsibilities require him to be very strict. If he wasn't so hard-nosed about regressions and code quality, Linux wouldn't be where it is today. Unfortunately, he's also a jerk (or "git" if you'd rather). I've worked with similar people, and they make you want to pull your hair out. There is no excuse for Linus to be so inconsiderate. Alan has contributed an enourmous amount of work to Linux, and the least Linus could do is show him a little courtesy when conversing with him.

  110. music first by epine · · Score: 1

    I'm tired of that silly myth.

    I guess that explains why you didn't stop to extract the grain of truth in your pique of ennui.

    Bonhomie is greatly increased in collaborations where little harm results from momentary lapses or honest mistakes. Software security is not one of those things. Likewise, deep sea divers are notorious for having a short fuse over charging a cylinder with the wrong gas at the wrong pressure. That kind of thing.

    Personally, I'd like to dig up some tape recordings of the choice language involved while setting the pilings that resulted in the Pont du Gard standing for 2000 years.

    Reminds me of a joke I came across in a relatively lame joke book in someone's basement.

    A women overhears some offensive language from two linemen working at the top of a telephone pole in front of her yard. She calls up the foreman at the power company and complains about the foul language. The supervisor contacts the two work men and demands an explanation. Joe explains: "Me and John were working up on this pole. He was up above me soldering some wires and dribbled some solder down the back of my shirt. So I yelled up 'Hey John, could you be a bit more careful up there'".

    I've encountered a couple of civility-at-all-cost programmers in my day. The kind of guy who would ring you up from behind half a cement wall in downtown Mogadishu and go "hey, I didn't want to interrupt anyone but we're having a spot of trouble here ... oh, the commander is taking lunch ... no problem I'll call you back later". Needless to say, we didn't hit many deadlines.

    Mihaly Csikszentmihalyi on TED talks about achieving flow states. He says a person enters a flow state in a situation when both challenge and skill are way above average (relative to the norms of that person), but the skill available is known to be sufficient to the challenge, even if the challenge is very high.

    When I get deep into the top-right quadrant I don't have much patience with elementary errors, such a failing to free a pointer allocation, or a buffer overflow caused by misuse of the abysmal C string functions. If your standards are high, it's not that difficult to train yourself not to make this kind of mistake. In some ways I find the STL more difficult to achieve 100% correctness, since I can't keep Scott Meyer's oeuvre in my forebrain all at once.

    How many buffer overflows are committed by people who are tying spongy ropes to their ankles and jumping off bridges? Is that figure elevation or altitude? Whatever. Let's just tie it and jump. That's how many people code. There's absolutely nothing about the terrible C string API more difficult than converting meters to feet, altitude to elevation, etc. The extra hoop is ominous and darned annoying, but it doesn't take a PhD to work it out correctly.

    On some levels, there's not nearly enough brittleness among programmers. More brittleness among the community might have put the C string/buffer functions out of their misery twenty years ago.

    When I'm deep in my flow quadrant, I truly resent the 1% of my brain allocated to safeguarding myself against abuse of the C language clstrfck() API. And I resent the other 500 paper cuts in the typical OS/programming language that confine my increasingly rare flights of inspiration to a depressingly paltry low-earth orbit. (And let's not kid ourselves that Java brings much to the table in the inspiration department. A flight of inspiration under a hermetic dome is not the life experience I'm seeking here.)

    In "Man Without a Country" Vonnegut wills himself the following epitaph: "The only proof he needed for the existence of God was music".

    He also says "What do men want? They want a lot of pals, and they wish people wouldn't be so mad at them."

    If some day I arrive at a flow state where Art of the Fugue pours out of my keyboard, the very notion of palhood will lapse from my psyche, as will any concern I might otherwise feel for the emotional states of thin-skinned beer drinking leprechauns. Music first, pals second.

    1. Re:music first by sonamchauhan · · Score: 1

      I think that you wrote this post in a Flow state. :) Sorry but you're still wrong.

      Its true that some of the best workers (knowledge industry or otherwise) are also the nicest people. Nice does not mean they never get angry. It just means they are patient and don't snap your head off when someone fumbles something minor.

      The real reason why so many talented programmers are egotists is because they are arrogant: they let their knowledge and achievements define their self-worth.

      It's the rare - and better person - who's both skilled and humble.

  111. Time for a beer by Anonymous Coward · · Score: 0

    Maybe President Obama will invite Linus and Alan over for a beer.

  112. Re:Hey by Mistshadow2k4 · · Score: 1

    As a woman, I find that an insulting and sexist thing to say. We women don't sit around and say things like, "Come on, ladies, this arguing is stupid and pointless. Stop acting like men!" Though judging from the fact that this is what happened here and from the content of your comments, I guess we should start.

    --
    I dream of a better world... one in which chickens can cross roads without their motives being questioned.
  113. Sheryl Crow TP dispenser by Latent+Heat · · Score: 1
    One squat . . . one square.

    No disgust . . . my backside.

  114. You missed one point: Linus was right by MikePlacid · · Score: 5, Insightful

    >Cox -> submits code which apparently caused a bug
    >User -> Reports breakage
    >Cox -> Can't replicate breakage and asks user for debug info so he can fix it.
    >User -> Says they don't know what to debug for, but is willing to work with Cox.

    Here they have found the bottom issue: emacs was expecting some reasonable behavior from the kernel: data delivery before notification of producer's termination. The behavior was broken.

    >Linus -> Jumps in and calls Cox's code a buggy piece of shit before any debugging took place, and before it is established if the code is buggy or not.

    Hello? The code broke a reasonable expectations of its users. Not buggy? That's technically is a DEFINITION of a bug.

    >Cox -> Continues to troubleshoot the issue.
    >Linus -> Flames Cox personally and says Cox is unwilling to work on the issue.

    Cox was proposing some strange solutions.

    >Cox -> Takes his ball and goes home, except in this case, it is OSS so he doesn't really take any ball with him. He just leaves.

    Then they had a technical discussion, and it appeared that Linus was right.

    1. Re:You missed one point: Linus was right by JonJ · · Score: 1

      Here they have found the bottom issue: emacs was expecting some reasonable behavior from the kernel: data delivery before notification of producer's termination. The behavior was broken.

      So emacs was broken, and that's Alan's fault?

      --
      -- Linux user #369862
    2. Re:You missed one point: Linus was right by Chirs · · Score: 1

      You misread. The behaviour of Alan's new code in the kernel was broken.

      Emacs was being reasonable and is unbroken.

  115. Best of luck in the future Alan by democrates · · Score: 1

    And Linus, maintainer hatred is a disease.

  116. Thx again Mr. Cox for the Linux Kernel .... by DrLov3 · · Score: 0

    Happy retirement Mr. Cox, my guess is that you deserve it more than anyone. Thanks for all the hard work, you may just have saved us all, and one day in the future, when we are all free, I, for one, will think of you.

  117. Re:Hey by lucifer_666 · · Score: 1

    Women have plenty of collective generalisations about men....

  118. fixed that for you by Anonymous Coward · · Score: 0

    Like him or not, Linus is still the main() in linux kernel development circles, and for good reason.

    (not as Finnished as the Spannish main, love, but the whole ocean...I'll shutup)

  119. Re:Hey by sco08y · · Score: 1

    We women don't sit around and say things like, "Come on, ladies, this arguing is stupid and pointless. Stop acting like men!"

    Probably not, but at the same time there's much less social stigma attached to a woman acting in a masculine manner, so it's a pretty pointless comparison.

    Though judging from the fact that this is what happened here and from the content of your comments, I guess we should start.

    So basically, if I want to be sexist too, all the justification I need is to have listened to Rosie O'Donnell for five minutes. Gotcha.

  120. OpenBSD by br00tus · · Score: 1
    Diplomatic? No

    Correct? Yes

  121. Holy shit. by Anonymous Coward · · Score: 0

    Seek help from a mental health care professional. Your posts have a rambling quality and an air of paranoia which does not seem healthy.

  122. Re:Slashdotted - Google Cache the real links by laejoh · · Score: 0

    Perhaps he was dictating?

  123. Then are you doing your job? by Ritchie70 · · Score: 2, Insightful

    Here's my theory....

    I get paid WAY too much to just shut up and do stupid stuff. If they wanted someone who would just shut up they could find someone much cheaper.

    So if my boss (or her boss, or her boss's boss) tells me to do something I think is stupid, I do my best to explain to them exactly what is wrong with that plan.

    So I'll argue about it. I'll disagree with them. I'll be difficult. But the whole time I'm telling them I'm just being difficult because I think it's a bad plan, not because it's personal.

    And there may be some reason I don't see that it's actually the right answer.

    In any case, once I'm sure they've gotten the concept I'm trying to express, I let them decide - them being the boss - and I go do what they said. Sometimes they change their mind. Sometimes they tell me the reason it's the right answer. Occasionally they tell me that they agree, but their boss says do it.

    Always fight the stupidity. Don't take the fight personally - but if you're in technology, the fight is part of your job.

    --
    The preferred solution is to not have a problem.
    1. Re:Then are you doing your job? by commodore64_love · · Score: 1

      >>> I get paid WAY too much to just shut up and do stupid stuff. If they wanted someone who would just shut up they could find someone much cheaper....So I'll argue about it. I'll disagree with them. I'll be difficult...
      >>>

      Yes but if your boss would rather argue than listen to your ideas, then he's also made clear that he just wants you to be a cog in a machine and do the work. I had a boss like that on my previous job, and I was all stressed-out (like him) because we keppt butting heads. Eventually I decided I'd rather be happy and unstressed, even if that means acting like a Walmart employee and simply saying, "Yes sir" all the time.

      Like I said if the boss recommends something exceptionally stupid, then I'll propose an alternate idea, but I'm not going to shorten my life with fighting & high blood pressure. I'm not paid enough to bring-on heart disease and an early death.

      Especially for something as trivial as a circuit card that will be obsolete in ten short years. If it was something that mattered, like rewriting the Constitution, then yeah I'll argue and debate and fight. But not for some dumb CCA. I'll just say "yessir" and collect my money like a good cog.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
  124. Door open by ZarkDav · · Score: 1

    Note that sometimes there is a good reason for pulling doors to get out: if the door opens on a frenquently circulated area then pushing it to get out might generate accidents.

  125. big compliment of my career by Salk · · Score: 1

    I worked with Alan a long time ago. Never quite understood how he could cope with a shimmering wallpaper.

    Anyway, the biggest compliment I've ever had was when he said my code was "fixable".

    Sadly at the time I didn't know him from a bar of soap. Only that he locked out all out customers fixing an intentional spelling mistake in my code ;)

  126. Another famous quote by DavidApi · · Score: 1

    First we had "All your base are belong to us", and now this beaut: "Please talk to the new tty maintainer whoever that ends up. I no longer
    care.". I love it. In so many levels this can be interpreted.

    Who's first to make this your new sig?

  127. Re:Slashdotted - Google Cache the real links by Anonymous Coward · · Score: 0

    What it often means is "I do care, deeply, and it is hurting me, so I am trying to stop".

  128. what we need is "firewalls" in front of big guns. by 3-State+Bit · · Score: 1

    And by firewalls, I mean secretaries, or at least someone to check and occasionally massage quite abrasive and personalizing correspondence. It's very simple: Linus was right. He had reason to be pissed. But Cox is important. ANYONE who knows who Cox is would have looked at Linus's letter and saw immediately that it needed some small changes, if nothing else to let Cox save face.

    The problem is made even worse by drugs that leave important academic users super-focused (not saying Linus is on any) -- the more clearly you see "idiocy" the more important it is to have a firewall take out words like that.

    Actually, Linus's e-mail includes the word "idiotic" explicitly.

    I doubt what I'm saying will have many takers around here, but posting at +2 in case anyone has any interesting responses for me.

  129. Care to show us your PHD in Psychiatry? by Anonymous Coward · · Score: 0

    "Seek help from a mental health care professional. Your posts have a rambling quality and an air of paranoia which does not seem healthy" - by Anonymous Coward on Thursday July 30, @01:49AM (#28878005)

    Care to show us your PHD in Psychiatry, along w/ your license to practice, & your formal analysis of my mental state? Oh, that's right - YOU don't have any of those, now do you? It's also not my fault you forgot to take your meds for dyslexia or that you have ADD/ADHD, & because of that, you are unable to read the written word, Hooked on phonics might be the answer for you.

    APK

  130. oh linus... by Anonymous Coward · · Score: 0

    Linus is not Alan's boss and does not have the right, specifically, to ask these sorts of "why didn't you do your job" questions. We can see how productive those questions are, when you aren't signing the paychque of the person you're asking.

    Way to get to the bottom of things, Linus!

  131. He said she said bullshit by Anonymous Coward · · Score: 0

    If you don't like the way Linus maintains the Linux kernel, then fork it and maintain your own branch

    Jesus Christ. This is exactly the attitude that splinters the OSS community - and it's a core philosophy of its central man. It needs to stop. Can't we all get along, resolve our differences and collaboratively create fantastic software? No, instead, we have to have petty arguments and fork and end up with mediocre rubbish. Why are there hundreds of distros that nobody uses, instead of one that seriously challenges Windows/MacOS?

    If there's one thing certain in technology, it's that different people will have different opinions. This needs to be a source of innovation and quality, not friction. As engineers we need to find better ways to solve these interpersonal problems, than resorting to ego, insults, disrespect, intolerance, argument and he-said/she-said bullshit.

    -- "Fine! I'll go get my own lunar lander. With blackjack... aaaand hookers. In fact, forget the lunar lander and the blackjack. Ah, screw the whole thing." - Bender

  132. Re:Hey by Skye16 · · Score: 1

    True, but that's sexist as well. And just because the GP is a woman, we can't necessarily conclude that she, too, holds the same generalizations (at least until she displays them, then we can yell at her for being hypocritical and whatnot.)

  133. Re:Hey by Anonymous Coward · · Score: 0

    That's because it's better to behave like a man than a woman. So saying "stop behaving like a man" would be a complement to a woman. That's why women are always copying men. They know men are better, and they want to emulate that. Can't blame them for trying. But since women are inferior, they generally fail to emulate men successfully and come off as noisy, pointless, butch blobs. Unless they are emulating useless girly-men who, being useless as men, are about average for women. But I have to ask, "what's the point?". But then, being a man, I can understand the pointlessness of it all. Women can't I guess, because they don't have the perceptive powers. In women's minds it's all fluffy teddy bears and singing blue and pink elephants dancing in circles in the air playing trumpets and fluttering their coiffured eyebrows. Oh, to live in la la land. The unreality of everything, the escape, the estrogen.

  134. It's human psychology by argStyopa · · Score: 2, Insightful

    What I find interesting from a psychological perspective is the baseless optimism of the participants.

    Do they think that in 1979 (or some specific date since) that Bill Gates stroked an imaginary 'Snidely Whiplash' mustachio and cackled over how he'd dominate the computer market and exploit people for his own wealth?

    Do they really think that any corporate/government organization that represents the polar opposite to the Linux 'paradigm' - highly bureaucratic, stifling, top-down organizations - didn't START with a font of goodwill, like Linux?

    What, precisely, did they think made their effort unique? Why did they actually think that Linux, as it becomes more relevant, wouldn't ALSO become a balkanized playground of ego, power, and territory-marking?

    How many distros of Linux are there? And how many of them have forums filled with not just people who are talking about the postive aspects of this distro or that, but who display the fanboi-attack piranha behavior toward anyone that dares preferentially support some other distro?

    Hey, I congratulate the guy for putting up with it as long as he did. He made a valiant effort, regardless of its futility.

    But as far as what he was fighting? Q.E.D.

    --
    -Styopa
  135. Confusion Amongst Kernel Developers? by mcoon · · Score: 1

    In reading the Linux kernel thread devoted to this emotional outburst of frustration amongst the Linux kernel developers, it quickly becomes apparent that neither Linus, nor Alan, have clear understandings of what exactly is going on in the kernel with the stated bugs. Indeed, neither of them seem to be working of a set of interaction diagrams, or other architectural diagrams. Both of these guys are just lost in the code and angry with each other.

    1. Re:Confusion Amongst Kernel Developers? by ifrag · · Score: 1

      Indeed, neither of them seem to be working of a set of interaction diagrams, or other architectural diagrams.

      Welcome to the real world?

      --
      Fear is the mind killer.
    2. Re:Confusion Amongst Kernel Developers? by mcoon · · Score: 1

      I develop commercial software for a living and am required by our auditing department to have documentation, and to provide it for review, on-demand. What world do you program on? Planet academia?

  136. basics by fulldecent · · Score: 1

    On Fri, 24 Jul 2009, Alan Cox wrote:
    > On Fri, 24 Jul 2009 17:21:45 +0200
    > "Rafael J. Wysocki" wrote:
    > > ...
    > > Well, I thought we were expected to avoid breaking existing user space, even
    > > if that were buggy etc.
    >
    > I don't know where you got that idea from. Avoiding breaking user space
    > unneccessarily is good but if its buggy you often can't do anything about
    > it.

    Alan, he got that idea from me.

    We don't do regressions. If user space depended on old behavior, we don't
    change behavior. ...

                            Linus

    ---------------------

    I think this is a pretty fundamental misunderstanding...

    --

    -- I was raised on the command line, bitch

  137. Re:Slashdotted - Google Cache the real links by BobMcD · · Score: 1

    I agree and concur. People like this also tend to pick at words like loose strings in a garment. You damn well KNOW you understood the meaning. Use your context clues and move on.

    It makes me wish we could communicate via thought. Of course, they would probably just start criticizing which thoughts you chose to transmit.

  138. Linus phone home! by Anonymous Coward · · Score: 0

    What if Linus took a phone call directly to Alan to discuss it instead of sending that "This is CRAZY! Why do you ...? WHY, WHY, WHY?" email that seems to be the final drop that made Alan decide to drop it.

    I know -- that's not how you normally work, besides most of them stick to mail-only. However, I bet it could have solved their misunderstandings with a possibly other outcome. Anyway, it's history now... we move on.

  139. Why is this news? by n7kv · · Score: 1

    Honestly, it's Alan's right to walk away, and it's Linus' prerogative to make whatever observations he'd like to. I don't see the drama, or why people are so exercised about it.

  140. Re:Slashdotted - Google Cache the real links by magbottle · · Score: 1

    To be fair, "I no longer care"

    To be even fairer, "I no longer care" is an emotional anagram for "and not only that, fuck off"

  141. cough cough by Anonymous Coward · · Score: 0

    well women certainly do...

  142. "What am I doing this for? by Anonymous Coward · · Score: 0

    Your doing it for free you idiot! H HA AHA HA AHA AH AHA AH

    Free means your only gonna go until "REALITY BITES"

  143. Hauppauge WINTV HVR 1600 digital TV tuner card by gbrayut · · Score: 1

    I have a Hauppauge WINTV HVR 1600 digital TV tuner card running on a Windows 7 RC x64 box with 6 GB of memory. Works fine in GBPVR. I did however have issues getting the onboard RAID controller working, but thats another story.

    1. Re:Hauppauge WINTV HVR 1600 digital TV tuner card by Pyrion · · Score: 1

      Which is entirely beside the point, since I'm most assuredly not going to give them more of my money just for something that would actually work in my system when they already got away with selling me something that was advertised to work in my system and didn't. If you bought a lemon from a company and got burned by them, would you willingly give them more money for another product?

      No, I think the rational response is to hate their guts for all eternity, or until they reverse their ridiculous policy of not supporting operating systems they advertise their hardware as capable of running on. As I don't ever see them doing that, I'll stick with hating their guts for all eternity.

      --
      "There is much pleasure to be gained from useless knowledge." - Bertrand Russell.
  144. Eh? by SEWilco · · Score: 1

    Sua TTY esta en Argentina.

  145. AberMUD? by the_arrow · · Score: 1

    Maybe he can go back and improve AberMUD again?

    --
    / The Arrow
    "How lovely you are. So lovely in my straightjacket..." - Nny
  146. How to step down as a maintainer ? by i-neo · · Score: 1

    The most interesting point is missing from the article quote: a patch was provided by Alan Cox to commit his decision:

    --- MAINTAINERS~ 2009-07-23 15:36:41.000000000 +0100
    +++ MAINTAINERS 2009-07-28 20:09:32.200685827 +0100
    @@ -5815,10 +5815,7 @@
      S: Maintained

      TTY LAYER
    -P: Alan Cox
    -M: alan@lxorguk.ukuu.org.uk
    -S: Maintained
    -T: stgit http://zeniv.linux.org.uk/~alan/ttydev/
    +S: Unmaintained
      F: drivers/char/tty_*
      F: drivers/serial/serial_core.c
      F: include/linux/serial_core.h

    It is pretty explicit, maybe more than words.
    It's a sad that such conflicts happen, but its usual in larger projects.
    Sometimes the LKML and Linus especially lack the delicatness to say things,
    even if they may be right, saying things in a way that do not offend people
    is often the best way to keep their attention and motivate them going toward
    the direction wished.

    Let's hope Alan will continue its work on other areas for the benefits of the community.

  147. Linus sucks by Anonymous Coward · · Score: 0

    Linus : You're a brat and and an asshole.

    Please grow up (that includes stopping doing 13yr old jokes like talking like a pirate).

  148. Alan Cox/Linus by Anonymous Coward · · Score: 0

    So, in essence, Alan yet again shows his ass, Linus *finally* gets tired of Alan's arrogance and smacks him, whereupon Alan acts like the typical six-year-old and walks away in a huff.

    Suck it up, Alan, and grow up. Linus is right and you are wrong, and you got pissed off because someone bigger than you finally stood up and told you that you were wrong. Intellectual maturity and emotional maturity obviously don't go hand-in-hand.

  149. Re:Linus (off topic) by Anonymous Coward · · Score: 0

    Also, doors should be always pulled when you go in and pushed when you go out. That makes exiting the building easier in case of emergency (people don't rush to the door and jam it, preventing anyone from pulling it open.) and also when people are trying to get in and out at the same time, the person outside is more capable of keeping the door open for the person going out (it is better that people first get out, before new people get in, because inside there is a limited space, while outside contains usually a lot more room). Also outside usually contains more room for pulling, while the inside often has a wall that limits the space for pulling, especially if you want to keep the door open for someone else.

    Nah, door shouldn't "be always pulled when you go in and pushed when you go out".
    In many countries such as the Scandinavian countries and also Canada, that's a bad design due to snow. Also, having a door open outwards is a risk to people walking past the door should it be opened right in their path.

    So - not wanting to start a huge debate over this, this simple example proves the problem any design decission has (also Linux): there are often more diverse circumstances to cater for than there are possible standards.

    PS: never bothered to answer a post before, so I skipped creating an account for this one time

  150. I understand where Allan is coming from... by oldpond · · Score: 1

    I did the Gentoo thing for a few years until I got sick of being abused on the forums and chat rooms. The reality is that open source is a social endeavor. For some it's about showing everyone else how smart you are, but for the rest of us it's about working together with people who are intelligent, friendly, and fun to be with. If you are at a party and you come across a rude and offensive person, you turn away and find another group to chat with. I don't know Linus, and the only thing I've seen is that Google talk he gave on git, but if he's like that in real life, and if Linux was a dinner party, the only people standing beside Linus would be the ones who want to be seen with Linus.

  151. USB is related to TTY ? by free2 · · Score: 1

    USB? I thought we were talking about TTY here.