Slashdot Mirror


Theo de Raadt Discusses OpenBSD and Beyond

emil writes to tell us that NewsForge (Slashdot Sister Site) is running an interview with OpenBSD project leader Theo de Raadt. In the interview Theo explores the upcoming release of OpenBSD 3.9, continuing financial difficulties, and some of the tension between the OpenBSD team and other businesses that some feel are taking advantage of the free software without giving anything back. In related news the Jem Report has an interesting writeup that expounds on widespread difficulties that could be faced if the OpenBSD project continues its downward spiral because of their parallel development of OpenSSH.

476 comments

  1. Re:Iff..... by Segfault666 · · Score: 1

    http://www.openbsd.org/ might even be a better source yet.

  2. Re:Iff..... by brilinux · · Score: 1
    Can anyone tell me why BSD with it's enhanced security isn't incorporated into most Linux distros?

    Because BSD is an Operating System, and GNU/Linux is an operating system... try reading that article again.

    How Unix like is it actually?

    Well, it traces back to BSD, unlike Linux, which was a kernel written to go with GNU, which in turn is written from scratch. While the free BSDs have changed a bit since they forked in the early nineties, they still are descendants of UNIX, and are much more close than GNU is, for better or for worse. (NetBSD is probably the closest of Free,Net,Open,&c.)

  3. stay on topic by r00t · · Score: 3, Funny

    Finally, for real, today's topic is: BSD is dying

    All other posts are off-topic. Enjoy!

    1. Re:stay on topic by Anonymous Coward · · Score: 0

      Are you sure? Does Netcraft confirm it?

    2. Re:stay on topic by fluxindamix · · Score: 0, Offtopic
      Finally
      it happened to me
    3. Re:stay on topic by betso.net · · Score: 1

      This should be a real long agony since I read such debile postings for years, Mr. Ballmer.

      --
      xoda.org
  4. Hmm... by Eightyford · · Score: 2, Insightful

    ...that some feel are taking advantage of the free software without giving anything back.

    Damn. I wonder if there was anything they could have done about that?

    1. Re:Hmm... by dtfinch · · Score: 4, Informative

      I'm pretty sure he's heard of it. While they do appreciate source code contributions, what they're really asking now for is money.

    2. Re:Hmm... by Eightyford · · Score: 1

      I'm pretty sure he's heard of it. While they do appreciate source code contributions, what they're really asking now for is money.

      And a dual license, like the one that MySQL uses may have worked great for them.

    3. Re:Hmm... by AHumbleOpinion · · Score: 5, Informative

      ...that some feel are taking advantage of the free software without giving anything back.

      Damn. I wonder if there was anything they could have done about that?


      No there wasn't, BSD as in Berkeley Software Distribution, as in University of California Berkeley, as in "Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved.", as in paid for by California taxpayers including corporations and individuals who should not be denied access to what they paid for.

      BTW, you shouldn't confuse BSD with a very talented but potentially mismanaged team that has a tendency to piss off lucrative sources of income.

    4. Re:Hmm... by Eightyford · · Score: 1

      No there wasn't, BSD as in Berkeley Software Distribution, as in University of California Berkeley, as in "Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved.", as in paid for by California taxpayers including corporations and individuals who should not be denied access to what they paid for.

      BTW, you shouldn't confuse BSD with a very talented but potentially mismanaged team that has a tendency to piss off lucrative sources of income.


      True enough, but they could have separated the old code and the new code, and licensed the post 1991 stuff under the GPL.

    5. Re:Hmm... by arivanov · · Score: 4, Informative

      Not really applicable.

      They started with a fork of the NetBSD codebase and maintained compatibility for a long while. Many drivers in the Net/OpenBSD tree used to be ifdef-ed for specific OS related parts. In fact one of the reason for OpenBSD to survive for so long especially on obscure architectures has been the fact that it used to rely heavily on Net for low level hardware specific code (disclaimer - I do not know if this is still the case as I have not looked at their source since 3.3).

      As a result GPL-ing is not an option. Your codebase is heavily dependant on somebody's else's codebase which is BSD.

      As far as the financial difficulties, all business and businesslike entities using GPL rely on support, custom code and consulting for their day to day living expenses. You do not get that money if you have this attitude:
      http://www.securityfocus.com/archive/1/428749/30/9 0/threaded. This is just one fresh example (this week).

      Another essential factor is that if you write software in the real world you have to go out of your ivory tower on a daily basis and check what your competitors doing. OpenBSD tends to believe its own PR about their security prowess and does not follow Linux, FreeBSD and other OS development as much as it should. One example for this is how it missed the appearance of hardware RNG in AMD hardware for several years. They simply did not know it is there (I actually pointed it to Theo myself a year ago). I bet that they have missed other stuff in a similar fashion as well.

      Frankly, the days when Open Source OS projects were PFY jobs and flaming each other out of existence on mailing lists was business as usual are long gone.

      Time to grow up or face the dark stairway down down and down towards oblivion.

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    6. Re:Hmm... by Anonymous Coward · · Score: 0

      And a dual licence like PostgreSQL could have worked for them, if they were looking to make a business out of this.

      How dense are you GPL people? This comes up at every BSD story, you are trolling by bringing up the GPL in a BSD thread.

      OpenBSD isn't trying to make money, they're asking that the companies which save millions by not licensing SSH.com's codebase via use of OpenSSH help pay for the continued improvement of the suite they use, they're not asking for advice from random dipshits that don't know their ass from a hole in the ground.

    7. Re:Hmm... by 0racle · · Score: 2, Informative

      They don't like the GPL and are currently removing GPL only licensed code from the base install. The GPL is not an option for OpenBSD.

      --
      "I use a Mac because I'm just better than you are."
    8. Re:Hmm... by Eightyford · · Score: 1

      And a dual licence like PostgreSQL could have worked for them, if they were looking to make a business out of this.

      How dense are you GPL people? This comes up at every BSD story, you are trolling by bringing up the GPL in a BSD thread.

      OpenBSD isn't trying to make money, they're asking that the companies which save millions by not licensing SSH.com's codebase via use of OpenSSH help pay for the continued improvement of the suite they use, they're not asking for advice from random dipshits that don't know their ass from a hole in the ground.


      I'm a GPL person? Please, if your going to get all pissy at least have the decency to not post anonymously.

    9. Re:Hmm... by IgnoramusMaximus · · Score: 3, Insightful
      They don't like the GPL and are currently removing GPL only licensed code from the base install. The GPL is not an option for OpenBSD.

      Subsequently, their moaning about how their self-inflicted mortal wounds hurt horribly is going to rightfully fall on deaf ears, if they are lucky, or will become a butt of jokes, if they are not.

      This is what happens if someone is given good advice not to drive their car off the road and into a bog and which they derisively reject and proceed at "what can possibly happen?"-speed into the mud. Following which they sit on top of their sinking vehicle, far into the swamp, waving frantically and complaining loudly about "selfish" people who fail to stop to pull them out of there. So that they can ignore good advice, as soon as rescued, derisively, again.

      I say onto Theo: Tough Cookies! You made your bed, you sleep in it! Perhaps placing product placements into the BSD code or performing in a clown outfit at conferences will bring the required revenue, now that the commercial interests do what you have always encouraged them to do: take, take and take ... whatever they can get in return for as least as possible. Its called "business", Theo. Look it up sometime.

    10. Re:Hmm... by Quantum+Fizz · · Score: 2, Interesting
      As a result GPL-ing is not an option. Your codebase is heavily dependant on somebody's else's codebase which is BSD.

      Dumb question, but if you can take BSD-licensed open-source code and put it in closed-source code, why can't you take the same code and GPL it (maybe make slight trivial modifications to make the software unique before GPL'ing)? I mean, it would most likely piss the BSD team off if someone did this, but legally speaking, is there a reason it cannot be done?

    11. Re:Hmm... by Anonymous Coward · · Score: 0
      OpenBSD isn't trying to make money


      Well it sounds like they're doing pretty well for that goal.
    12. Re:Hmm... by dingen · · Score: 1

      If Theo wants money, he should get a job and not trust that an open-source project will pay his bills.

      --
      Pretty good is actually pretty bad.
    13. Re:Hmm... by cstoner · · Score: 1

      I don't believe that there is any legal problem with this, but then again IANAL.
      The problem with this is the same problem that was (and still is) seen in the emacs vs Xemacs debate: primarily that the code contributions made to the non-compatable codebase can't be ported back without a hassle.
      I'm not 100% of my communication skills at 3 in the morning, so I'll give an example.
      Someone contributes to the GPL liscenced OpenBSD. The BSD liscence is NOT backward compatable in this case, and those changes can't be automatically applied back to the BSD liscenced OpenBSD, they have to get the author's permission to simply use that patch. This might not seem like a huge issue, but there is the chance that the author of the patch doesn't like BSD and doesn't want his/her code liscensed that way, or that the author simply can't be gotten ahold of.
      Besides, if you're releasing code under a BSD liscence, what are the benefits of ALSO having a GPL version. It would only seem to cause lots of headaches.

    14. Re:Hmm... by aCapitalist · · Score: 1

      Damn. I wonder if there was anything they could have done about that?

      I'm sure they considered it, but then decided to use a free license instead.

    15. Re:Hmm... by Anonymous Coward · · Score: 0

      Well he could always get a military contract for development, I'm sure that...

      Oh, wait. Yeah, that's right. De Raadt is an unpersonable prick, and as a result no businesses really want to deal with him. Almost forgot.

    16. Re:Hmm... by Anonymous Coward · · Score: 0
      I'm pretty sure he's heard of it. While they do appreciate source code contributions, what they're really asking now for is money.

      Maybe Theo is finally realizing he's burned too many bridges in the software community. Don't get me wrong, there are people that have undying devotion to the guy and his project, but many of us think he comes off as a bit of a pompous douchebag like Dan Bernstein.

      /still use OpenSSH

    17. Re:Hmm... by jbailey999 · · Score: 3, Funny

      GPL people are cool. I like to make copies of them. The only problem is that everytime I give one a way, I have to give the damned cloning formula away...

    18. Re:Hmm... by kv9 · · Score: 2, Funny

      nice troll. however i do believe that he wants money to support the project and not his drinking habits.

    19. Re:Hmm... by zerocool^ · · Score: 1, Insightful

      From the link you provided:


      I did not decide that OpenSSH should become a critical part of the
      internet, or that it should become a virtual monopoly. We made it
      free. Again, the community decided to make it Internet infrastructure.

      Now you want to tell us that because the Internet community made
      decisions like these, that we should be held responsible. That we
      have to follow YOUR procedures. That we have to answer to YOU.

      What if we ignore your procedures? What if we say no? What will you
      do then? Continue to verbally attack us? To what end? To show that
      you are thankless dogs?


      And they wonder why they don't get any support.

      Bravo; you've made the most secure operating system available today. But, then, you have this firmly held belief that the rest of the world owes you something? That you're gracing the rest of the world with your glorious presence and regal software? That attitude is not welcome here.

      ~Will
      --
      sig?
    20. Re:Hmm... by Ontology42 · · Score: 1

      Well, I can understand Theo's point, all of this software is given away for free and bam! The popularity and marketing contests are won hands down. As to that Thread, well he's a programmer not a marketing guru. Everyone here maintains some aspects of the stereotypes that programmers have social issues involving thier ego's espically infamous ones. Personally I beleive Checkpoint, Nokia, Apple, Red-Hat and any organization which sustains a profit from OpenSSH should contribute, I'm not about to dictate corporate morales; as they generally don't exist and I don't like carrying a shovel with me. However since OpenSSH/SSL is such an integrated part of the net, it would be unwise to loose such an important part of your own business models foundation. Myself as a consultant whenver I sell an OpenBSD based firewall (which is what I love using it for) I purchase some CD's for my clients and bill them for it, my clients understand that yes the liscence is free but selling the media is how they make a profit. It's a small gesture but if everyone did it then there wouldn't be any issues now would there?

    21. Re:Hmm... by rhavenn · · Score: 3, Insightful

      I don't get why people dump on Theo all the time. Yeah, he really could use a PR manager at times, but all the threads I've read he usually is right or standing up to what he believes is right. Can Theo be a dick about it? Yeah. Can Linus and Stallman be dicks about the kernel and the GPL? Yeah. Get over it and maybe send them some money for this OpenSSH thing we all use.

    22. Re:Hmm... by infinityxi · · Score: 1

      Quit being a trollish prick. They created something and the community uses it. Now there is no demand that the community pays the OpenBSD/OpenSSH project back but if you donate you're paying for new features and new code. All you GPL fan boys talk about Theo's attitude but just read various posts on slashdot. Many of you aren't exactly amicable. Unlike a lot of Linux vendors they do stick behind their principles and it is a very hard thing to do for things like support and finances. You aren't paying them to put money in their pockets you're donating to them so their project can get better. If you use OpenBSD/OpenSSH common sense would dictate that you would want this. Go back to your Gentoo distribution, should finish compiling in 3 hours. (If you don't run Gentoo insert fanboy Linux distribution in its place and don't reply to me on little nitpicks)

      --
      Turn based strategy game that runs over XMPP. Phalanx
    23. Re:Hmm... by Doctor+Memory · · Score: 2, Insightful

      you have this firmly held belief that the rest of the world owes you something?

      No, his point is that he's not being paid for this, so people should stop treating him like an employee. Part of the freedom of writing FOSS code is that you don't have to bend over backwards to accomodate people, because they aren't paying customers. If somebody thinks some software I wrote should have some feature, or should work in a certain way, and whines because it doesn't, I can tell them to take a hike, because I provide the software at my whim and convenience. If I'm a good, conscientious developer, then I'll listen and add their request to the "future directions" list, but I certainly don't have a mandate to do so.

      To paraphrase Al Capone, "You can get better support with polite e-mail and a $100 check than with polite e-mail alone".

      --
      Just junk food for thought...
    24. Re:Hmm... by aesiamun · · Score: 1

      How would making anyone give source code back help financial issues?

      The GPL trolls are out on slashdot and osnews about this one...

    25. Re:Hmm... by man_of_mr_e · · Score: 1

      The GPL would not have helped them at all. The GPL only enforces freedom of the code. It does not ensure compensation for your work. OpenBSD's problems are financial, not Freedom based.

    26. Re:Hmm... by zerocool^ · · Score: 1, Interesting


      But to bring up the same points I posted about previously when Theo was trying to extort money by holding a gun to the head of the cute little OpenSSH puppy... I'm not treating him like an employee.

      I don't use OpenBSD. I actually have used it in the past, and to be honest, I find the OS as a whole to be convoluted, illogical, and pretentious (and this from someone who doesn't mind Solaris). So, I don't give a rat's ass about OpenBSD. What I am sick of is people saying "But but but but OpenBSD contributed OpenSSH, which you use", and trying to guilt trip me into giving money based on that. Eat me. Someone would have written an open source SSH server eventually anyway, and OpenSSH is built on code that's older than OpenBSD. I'm greatful for it's existance, but I'm not going to donate money to OpenBSD because they wrote OpenSSH.

      It's my money; Theo released the code under the BSD license. I don't expect anything from Theo, I appreciate what he's done, but the guy is a cock. OpenSSH is just a tool to me, it's not a life changing expierence, and if RHEL or whatever shipped with a different SSH server, I wouldn't give a goddamn - I just expect it to work. It's a means to an end, not a religion. And I'm not treating him like an employee. I don't appreciate a guilt trip is all.

      If I walked into JC Penny's and went to use the restroom, I wouldn't be very receptive to some manager dude standing right outside the stall, telling me how he PERSONALLY designed and built the restroom, and the store lets me use it for free, and how everyone who takes a shit on his property is a "thankless dog", and how I don't have to donate, but that I should. Fuck him.

      ~Will

      --
      sig?
    27. Re:Hmm... by Lennie · · Score: 1

      They wanted to get rid of people using telnet instead of something secure, so they made it better, more secure, etc.

      If they'd had made it GPL, no1 would have incorporated it in their products.

      --
      New things are always on the horizon
    28. Re:Hmm... by Anonymous Coward · · Score: 0

      +1 Cinical (but still, quite true)

    29. Re:Hmm... by Bing+Tsher+E · · Score: 1

      The GPL version would become a dead fork, unless a whole new community became involved in the project. The original community seem to like the BSD license, so they're not gonna wander off onto the new GPL licensed fork.

    30. Re:Hmm... by clymere · · Score: 1
      One of the complaints many have is that you can't actually send money to support OpenSSH. What you can do is support OpenBSD, by sending a check to Theo's personal checking account.

      I've bought CDs and t-shirts in the past, and likely will continue to do so. I have no problems supporting the OpenBSD project, its something that i do use myself. But i do see how the multitudes who are using strictly OpenSSH, OpenBGP, or one of their other related projects would prefer to be able to donate money specifically earmarked for that project.

      The lack of either a recognized corporation or non-profit to accept donations is also going to be a big sticking point for and business interested in donating. When the check is written to Theo de Raadt, and not OpenBSD, it makes it a lot harder to write it off on taxes.

      The big boys don't play that way. I've worked on the Ohio Linuxfest this past year, which is 100% free to attend due to corporate donations. The big players like Novell and IBM would not work with us without a non-profit to write their checks to. For that matter, even small businesses tend to feel the same way. Once we had that in place they were more than happy to send us nice big bags of cash so that 1000 or so people could enjoy a nice free event.

      There are plenty of open source projects that are doing quite well with soliciting donations. There are well-defined methods of eliciting this. I see the porblem here as less that corporations are being greedy, as much as it is that the OpenBSD camp are bending over backwards to make themselves unattractive for corporate interests

      They have very strong opinions about the way they do things, and thats fine. But if you're not willing to compromise on some things, you have to accept the fact that not as many people are going to be there to hold your hand and help you out.

      --
      once you go slack, you never go back
    31. Re:Hmm... by Anonymous Coward · · Score: 0

      So what you're is that Theo de Raadt should implement every stupid idea that gets floated past him, or else it's his own damn fault when none of the major corporations donate to OpenBSD/OpenSSH ?

    32. Re:Hmm... by IgnoramusMaximus · · Score: 1
      So what you're is that Theo de Raadt should implement every stupid idea that gets floated past him, or else it's his own damn fault when none of the major corporations donate to OpenBSD/OpenSSH?

      No, Theo should just stop being Theo, and start behaving like a human being, with some humility and understanding of others. The problem is not with "implementing any idea floated by him" but with his attitude towards those who do the floating. And yes, it is his damn own fault as he managed to successfully scare a lot of potential donors away with his antics. He is exceedingly lucky that Mozilla and others chose to look past his wonderful personality and donate anyhow in response to his baseless accusatory finger pointing and illogical demands. In Theo's world, nothing ever is Theo's fault, you see.

  5. Classic Theo de Raadt by QuantumG · · Score: 1

    Nvidia did not give anyone documentation. Instead, they expect people to load a gigantic blob of binary code into their kernel, and just be happy with that. Some Linux people in Germany reverse-engineered the driver years ago, but the rough story I heard is that Nvidia asked them to stop, and they did. This just astounds me!

    Gee, I don't know, maybe they had lives they didn't want to sacrafice for the cause Theo. He then goes on to slag linux developers in general but maintains that he doesn't really go into advocacy.

    --
    How we know is more important than what we know.
    1. Re:Classic Theo de Raadt by Tweekster · · Score: 2, Informative

      from what i read was that he didnt like the binary drivers...fair enough that is his belief. some people did do a reverse engineer job and were asked to stop. it is germany on the other hand, not the US, they probably have a bit saner laws regarding that (depending on the method of course) maybe they did it out of respect and not fear. who knows. it could be a number of reasons. however, theo wasnt exactly an asshole on that concept, he is suprised they would stop (again we dont know why they stopped) he wished they didnt, he takes issue that they did stop. his opinion mismatched with someone elses. oh well it happens but its not like you said, he didnt slag linux. oh and he does do a lot of advocacy...wireless drivers for instance.... man I never thought I would defend theo

      --
      The phrase "more better" is acceptable English. suck it grammar Nazis
    2. Re:Classic Theo de Raadt by Anonymous Coward · · Score: 0

      You're so worried about his attitude. The question is, is he *right*?

    3. Re:Classic Theo de Raadt by LurkerXXX · · Score: 2, Insightful
      He said he found it crazy that folks who always want 'open' software, even forcing anyone using it to keep it open, would accept closed binary blobs in their software. That sounds like a pretty specific point he was talking about. Not 'slagging linux developers in general'.

      If you disagree with his point, how about stating why you think it's wrong rather than just bitching about 'classic theo'.

  6. SunSSH by dtfinch · · Score: 2, Interesting

    "I will say it here -- if an OpenSSH hole is found that applies to SunSSH, Sun will not be informed. Or maybe that has happened already." - Theo de Raadt

    I'm sure they'll find out when everyone else does.

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

      Well, duh. It's probably the symbolism that he's talking about.

    2. Re:SunSSH by lintux · · Score: 1

      But what if they find a bug that "accidentally" got fixed already two/three years ago already? Maybe they won't announce it, since they always recommend to run recent versions anyway. (They do, right?)

    3. Re:SunSSH by MichaelSmith · · Score: 1
      But what if they find a bug that "accidentally" got fixed already two/three years ago already?

      Sun just need to track OpenSSH cvs to get all the fixes.

    4. Re:SunSSH by Homestar+Breadmaker · · Score: 1

      They don't do that though. SunSSH is based on years old code, with security features (like privsep) disabled. Sure, Sun could track CVS if they wanted to, but they don't. And them having to track CVS is not the same as being notified in advance and given time to fix the bug.

  7. what a whiner by penguin-collective · · Score: 2, Insightful

    Some of the OpenSSH freeloaders, like Apple Computer and The SCO Group, are notorious for reaping financial rewards from selling open source software bundled with their proprietary products.

    What part of the BSD license does Theo not understand? Apple and SCO aren't "freeloaders", they are using the software under the intended license.

    Furthermore, what makes Theo think that people want to run OpenSSH? At this point, it's as entrenched as Windows--nobody has a choice.

    For our work on OpenSSH, companies using OpenSSH have never given us a cent. What about companies that incorporate OpenSSH directly into their products, saving themselves millions of dollars?

    No, they haven't been saving themselves "millions of dollars". If OpenSSH didn't exist, people would implement some other free ssh client or switch to a different standard.

    If you release something under a FOSS license, figure out your business model beforehand. Of course, Theo actually did: his work on BSD has given him plenty of exposure and celebrity status, which many would consider ample reward for his work, and something he wouldn't have gotten if he had founded a small software company instead. And I'm sure he could (or could have) translated this into consulting opportunities and other business, without even changing the license on anything. But, like many celebrities, it's just never enough.

    1. Re:what a whiner by Schraegstrichpunkt · · Score: 3, Insightful
      Some of the OpenSSH freeloaders, like Apple Computer and The SCO Group, are notorious for reaping financial rewards from selling open source software bundled with their proprietary products.

      What part of the BSD license does Theo not understand? Apple and SCO aren't "freeloaders", they are using the software under the intended license.

      That part wasn't written by Theo, as far as I can tell.

    2. Re:what a whiner by QuantumG · · Score: 2, Insightful

      Let's face it, the reason why Theo de Raadt can't maintain his unpaid work on OpenBSD/OpenSSH is because he's an impersonable jerk. You can't make money as a consultant if your response to everyone is just to tell them to shut the hell up. You may be able to make money from speaking tours (like RMS does) but you actually have to have enough patience and dedication to stand up deliver a talk that people who are willing to pay to hear (i.e., not talks that people give to developers). Theo reminds me of people who like to play folk music or surf all day. They run around looking for sponsors but they're not interested in putting on shows or entering competitions.

      --
      How we know is more important than what we know.
    3. Re:what a whiner by hhw · · Score: 5, Interesting

      Just because the BSD license doesn't force companies to give back, doesn't mean they can't do it anyway.

      For a business that uses OpenBSD code, it would just make good business sense to support the project at a fraction of what it would cost to develop the same code in-house. It is ridiculous that Sun wouldn't even cover the travel expenses of an OpenBSD developer to go their conference, because the value of the developer's hours would have far exceeded such travel expenses. That's just simply bad business.

      --
      http://astutehosting.com/
    4. Re:what a whiner by Anonymous Coward · · Score: 1, Insightful

      What part of the BSD license does Theo not understand?

      The part he understands, and the part that you do not, is the part that's not written in the letters, but the part that's written into the human soul.

      specifically the virtues of responsibility, community, and generosity. especially the least that provide the most.

    5. Re:what a whiner by Tweekster · · Score: 1

      You are completely correct.... however, you simply cannot become pissed off by the fact that some company followed the license to the letter.

      --
      The phrase "more better" is acceptable English. suck it grammar Nazis
    6. Re:what a whiner by kg4czo · · Score: 1

      "specifically the virtues of responsibility, community, and generosity. especially the least that provide the most."

      Since when have any of those "virtues" been included in business practices of large corporations? While it may be written into the human soul, corporations are different souless beasts. There have even been problems getting corporations to release code derivatives of GPL's programs.

      If a corp doesn't have to release anything, most likely they won't.

    7. Re:what a whiner by Anonymous Coward · · Score: 0

      That part wasn't written by Theo, as far as I can tell.

      Shouldn't matter. The BSD licence allows people to create derived works and not have to give anything back. How could anyone be surprised that a corporation wouldn't capatalize on this free meal ticket?

    8. Re:what a whiner by pherthyl · · Score: 4, Insightful

      Furthermore, what makes Theo think that people want to run OpenSSH? At this point, it's as entrenched as Windows--nobody has a choice.

      What are you talking about? People use OpenSSH because it's by far the best out there. Nobody is locked into using it, the specs are open, anyone can code a replacement. It's just not easy to produce something of the same quality and security as OpenSSH. People are locked into Windows because of proprietary file formats and closed source applications; how is that in any way similar to OpenSSH?

      But, like many celebrities, it's just never enough.

      Sorry. CELEBRITIES? Hmm.. yeah sure, Theo is a celebrity. I'm sure he has paparazzi knocking on his door every day.

      Sure Theo can be abrasive, but it's weird to see how gleefully people at the receiving end of his charity will attack him. It's always easy to be an armchair critic.

    9. Re:what a whiner by lintux · · Score: 4, Informative

      Furthermore, what makes Theo think that people want to run OpenSSH? At this point, it's as entrenched as Windows--nobody has a choice.

      Actually, it isn't. You can also use LSH or Dropbear, and for SSH clients there are even more alternatives (PuTTY is available for Linux, for example).

      This article almost makes me consider using one of them...

    10. Re:what a whiner by penguin-collective · · Score: 0, Redundant

      Nobody is locked into using it, the specs are open, anyone can code a replacement. It's just not easy to produce something of the same quality and security as OpenSSH.

      And there is also no need to because of its liberal license. The only problem is that Theo is now complaining, after OpenSSH has become ubiquitous under the current license.

      If OpenSSH didn't exist, the ssh 1.3 source would probably have been picked up by GNU and we'd have free GnuSSH, without Theo's whining. Or, maybe, people would be running telnet-over-SSL.

    11. Re:what a whiner by cyberjessy · · Score: 5, Insightful

      What part of the BSD license does Theo not understand? Apple and SCO aren't "freeloaders", they are using the software under the intended license.
      Furthermore, what makes Theo think that people want to run OpenSSH? At this point, it's as entrenched as Windows--nobody has a choice.


      Dear friend, herein lies the indelible mark of your misunderstanding of the free software _Movement_, and will live on even after you are dead and gone.

      The help he is asking is pocket change for the companies which use OpenSSH. For the work done in making it compatible with major projects of those companies. __If you read the article__ you will also note how IBM sends customer complaints to the OpenSSH team. And how Sun refused to pay for travel!

      I find it painful.

      --
      Life is just a conviction.
    12. Re:what a whiner by pherthyl · · Score: 4, Insightful

      If OpenSSH didn't exist, the ssh 1.3 source would probably have been picked up by GNU and we'd have free GnuSSH, without Theo's whining.

      I'm sure you're right, it's not like we wouldn't have another SSH client, but would it be as good? The fact is that Theo and his team writes really good, really secure code. Someone who does security "for fun" is very rare and valuable. Most developers are quite naturally more interested in cool features than tedious code review.

    13. Re:what a whiner by giorgiofr · · Score: 3, Funny

      the ssh 1.3 source would probably have been picked up by GNU and we'd have free GnuSSH

      which would suddenly turn off encryption on your channel and pop up RMS's face saying "You are using this software for something *I*, his Imperial Majesty RMS, happen not to like today or maybe in the future, therefore I will stop it. I also hope your OS crashes and burns because it's not running HURD."
      Thanks, I'll keep using the *really open* OpenSSH.

      --
      Global warming is a cube.
    14. Re:what a whiner by seifried · · Score: 1

      In theory they'd be smart enough to feed the golden goose once in a while rather than just taking the eggs and running. I use OpenBSD for a number of firewalls at my sites and client sites, I've got every CD going back to 2.1, and given cash to the project in past, next week at CSW06 I'll be handing Theo a cheque. Why? Because I'd be really up the creek without OpenBSD for my firewalls (active failover on commodity hardware is a lot cheaper than the commercial alternatives).

    15. Re:what a whiner by jlar · · Score: 1

      "Just because the BSD license doesn't force companies to give back, doesn't mean they can't do it anyway."

      But it is bad business sense to rely on it. A license states what you expect people to do with your software. If you want people to pay for using it in proprietary products - then you should choose a license that ensures just that using e.g. a dual licensing scheme (copyleft/proprietary).

      I haven't paid for any of the great open source products that I have used but I have made some of my own code available under an open source license. Similarly Sun has not paid for OpenSSH code but they have released a lot of other code under open source licenses. I don't blame them for their choice.

    16. Re:what a whiner by Gleemonex · · Score: 1

      __If you read the article__ you will also note how IBM sends customer complaints to the OpenSSH team.

      PFY: "Shit, this multi-million-dollar client is fuming mad! How do I appease them?"
      BOFH: "Send them to the rudest prick you can think of, of course."

      ****

      In all seriosity, that's pretty disgusting. I'd have some choice words for the IBM, and their client in question (to send the message home to IBM) if I were in that situation.

      -Glee
      --
      Many a true word hath been spoken in jest -- mod funny posts "Informative".
    17. Re:what a whiner by BruceCage · · Score: 1

      I completely agree with you on this, just because a license doesn't force you to contribute (i.e. it allows you to be free) doesn't mean you shouldn't follow good ethics and support a project anyways. Saying the license excuses you from any moral obligations is imho just silly.

      However I have noticed that a lot of FLOSS projects I use don't accept monetary donations e.g. Gaim, Gantt Project, Scintilla, 7-Zip. They're just glad if people help them in building a better product and I think this is what free software is truly about.

      --
      Perfect is the enemy of done.
    18. Re:what a whiner by just_another_sean · · Score: 1

      Never the less, this is the License Theo chose for OpenBSD. If he doesn't like it maybe he should consider choosing a different license for upcoming releases. I hope he doesn't or if he does he chooses another "free" license but he does have the choice.

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    19. Re:what a whiner by Jussi+K.+Kojootti · · Score: 1
      Dear friend, herein lies the indelible mark of your misunderstanding of the free software _Movement_
      That's a little condescending, isn't it? Especially as you seem to misunderstand the legal restrictions companies operate under... If I understood you correctly you think that companies have a moral obligation to support free software that they use. That would clearly be against the interests of shareholders, and makes the company liable.

      It's fine to lambast Sun for making a bad business decision (as in, the plane tickets would have generated shareholder value), but implying that they should pay because it's morally right, is surreal. Saying "but it's just pocket change for them!" even more so.

    20. Re:what a whiner by cortana · · Score: 1

      Like LSH? :)

    21. Re:what a whiner by DieNadel · · Score: 1

      I'm an OBSD user, have bought some CD's and I think that the quality of the code the developers put out is amazing.

      O DO believe that companies like Sun, IBM and Apple should contribute to OpenSSH, just like Red Hat and other Linux vendors. Not because the are required (they are not), but it makes sense to keep the development of this high-quality tool at the fraction of the cost of a full-blown development team.

      But calling names won't help advocacy. Really! Please try not to attract more hate against our beloved project, it hurts any effort we do to raise funds from OpenSSH users. It's enough that misc@ scares most newcomers away.

      --
      Utinam logica falsa tuam philosophiam totam suffodiant!
    22. Re:what a whiner by hahiss · · Score: 1
      That would clearly be against the interests of shareholders, and makes the company liable.

      Actually, that claim is a bit too quick, in at least three ways:

      1. Not all companies are publicly traded. Since non-corporations use free software, your comment overshoots its mark. (Though of course many of the companies we're talking about are corporations; but your comment is about companies that use free software generally.)

      2. The claim that the only interest that a corporation has is to its shareholders is at least controversial; there are other theories of corporate responsibility (c.f. stakeholder theory), and it is tendentious at best to flatfootedly assert that corporations have duties only to shareholders.

      3. Even if you think that corporations only have duties to shareholders, it doesn't follow that paying for gratis free software violates that duty. If the corporation relies on free software and the donation would promote the development and improvement of this software, that seems to be a benefit to the corporation and its shareholders. That is, if such donations increases the quality and availability of the software to the corporation, then the shareholders benefit---especially if doing so increases the quality and availability of the software in a way that is more cost effective than buying proprietary software.

      --
      "Every decent man is ashamed of the government he lives under." - H.L. Mencken
    23. Re:what a whiner by kv9 · · Score: 2, Interesting

      it's just bad business. lately lots of companies got big on open source and seeing how SUN (and others) has openssh based products, it would be freakin common sense to give something back to the developers. "well shit, they threw all that code in the wild, we're using and profiting from it, why not drop them some dosh so we motivate them to keep up the good work, so we don't have to".

      some recent examples:

      HP donated a 20 node blade monster to the FreeBSD project last year in december "We at HP recognize the important role of FreeBSD in the Internet's global network infrastructure, and we are happy that the HP BladeSystem cluster can contribute to the on-going success of the FreeBSD Foundation"

      i was listening to a LUGRADIO episode recently and there's this propylon company which specializes in legal products, and they are the fourth largest contributor to OO.o -- nothing small either, they got like 60 devs on top of shit.

      and i'm sure the list can go on and on. so before you blame big bad theo for expecting something back from the `freeloaders' why don't you look around at what other `big bad souless companies' are doing?

      --EORant

    24. Re:what a whiner by Anonymous Coward · · Score: 0
      In theory they'd be smart enough to feed the golden goose once in a while rather than just taking the eggs and running.


      In theory? Give me a break. My spouse works for a major UNIX vendor and claims that the horizon is always the next quarterly statement, everything else be damned. If they thought it'd improve next quarter's profits they'd kill the golden goose, cook it and eat it.
    25. Re:what a whiner by schon · · Score: 1

      Saying the license excuses you from any moral obligations is imho just silly.

      Sorry, but what moral obligations does the BSD code impose?

      Please show me where, in the the BSD license, it says that you should pay the developers. Show me where it says "we're doing this for free, but we need to eat, and so would appreciate some money."

      The people using BSD code are following not only the legal requirements, but the spirit of the BSD license - this means that they are already excused from the "moral" obligations.

    26. Re:what a whiner by schon · · Score: 1

      you will also note how IBM sends customer complaints to the OpenSSH team.

      Ahh, sorry, what?

      I read the article, and it said that *ONE* IBM customer was sent to OpenSSH.

      It did not say it happens on a regular basis. It did not say whether they were sent there by a manager, a contractor, or a frustrated developer. It did not say what the problem was. It *did* say that it was quoted by one of the biggest asshats in the OSS field today.

      I'll take his anecdote with a grain of salt.

    27. Re:what a whiner by Anonymous Coward · · Score: 0
      2. The claim that the only interest that a corporation has is to its shareholders is at least controversial; there are other theories of corporate responsibility (c.f. stakeholder theory), and it is tendentious at best to flatfootedly assert that corporations have duties only to shareholders.


      After having just completed a course on corporate ethics, I can say that this agrees completely with the academic mentality. Being a working adult I can also say that this has very little if any bearing on reality.

      The bottom line is as long as the corporation doesn't cross the line into "illegal" territory it sure as hell isn't going to sacrifice shareholder profits for "doing what's right." I know that if I lost money due to a company not optimizing itself for profits I'd be on the next shareholder filed lawsuit.

      Back to free software, I think Theo is a dick. It would be amusing to see a Springer-like episode in which he mouths off to or shoves the wrong person and gets flattened (see: Glenn Danzig). That being said, the consensus is that his team's code is excellent and I think that certain large entities could pony up a few bucks for OpenSSH as it would be in the interests of profits with respect to their products. Then again with the way Theo has pissed off certain companies like Sun and Adaptec in the past I'm not holding my breath.

      What kind of money would OpenBSD be looking for, anyway? If Sun, Redhat, IBM, and say HP all threw in 15k a year a piece would that give them a sufficient base from which to work? Other contributions would be accepted too, of course.

      And for the record I buy the OpenBSD CD set sporadically.. along with Slackware.

    28. Re:what a whiner by Anonymous Coward · · Score: 0

      Have you met him?

      Let me tell you a little secret. Theo does not get paid to speak. He refuses that kind of money.

      You people should really not try to pretend that the internet is the real world. Get laid, it helps with stress.

    29. Re:what a whiner by poot_rootbeer · · Score: 1

      For a business that uses OpenBSD code, it would just make good business sense to support the project at a fraction of what it would cost to develop the same code in-house.

      It makes better business sense to spend zero dollars, and take the OpenBSD Group's code free of charge.

      Sure, there's a risk that Theo will run out of money and shut down development of the code -- but that risk exists even if companies DO send him money.

    30. Re:what a whiner by Kadin2048 · · Score: 1

      The part he understands, and the part that you do not, is the part that's not written in the letters, but the part that's written into the human soul.

      Wait, my soul came with a license?

      Damn this clickwrap...I knew I should have read that agreement a little more closely.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    31. Re:what a whiner by Anonymous Coward · · Score: 0

      ``After having just completed a course on corporate ethics, I can say that this agrees completely with the academic mentality. Being a working adult I can also say that this has very little if any bearing on reality." And being an uninformed idiot also means that you can comfortably talk out your ass as an anonymous coward . . . Compare, for example, fair trade coffee, pharmaceutical companies distributing free meds to those cannot afford them, corporations that give time off to employees to volunteer in their communities, and the like. Each of these things doesn't contribute directly to the bottom line, and some take away from it. Yet they exist--in reality. Just because you're a fan of the prevailing sociopathic corporate mentalities doesn't make those mentalities correct; it just makes you a jackass.

    32. Re:what a whiner by Syberghost · · Score: 1

      If OpenSSH didn't exist, people would implement some other free ssh client or switch to a different standard.

      Evidence that you're right.

      Currently we use OpenSSH because it's the best free one. If it didn't exist the people working on it wouldn't all suddenly stop needing it, and if it had a different license some people who work on it would no longer be interested and others who aren't suddenly would be. It's currently a well-scratched itch, but the moment it isn't, it'll be scratched another way.

      Fortune 500 companies rely on OpenSSH a lot more than they do OpenBSD; if nothing else, all the major Linux distros would collaborate on a fork of OpenSSH before they'd let it die. Or, more likely, jump-start lsh.

    33. Re:what a whiner by Shanep · · Score: 1

      What part of the BSD license does Theo not understand? Apple and SCO aren't "freeloaders", they are using the software under the intended license.

      What part of the BSD license do YOU not understand? Does the part that disclaims all WARRANTIES confuse you? The CODE is free to use and open. SUPPORT of the code on the other hand is not in any way an obligation on the heads of the OpenSSH or OpenBSD projects. Theo is asking for financial support so that they can continue to support the code. They are NOT asking for money for the code itself. I am seeing this ridiculous "Theo's fault due to BSD licence" attitude around a lot of places at the moment. So very many people don't seem to be able to grasp the huge distinction between the code itself and the support of the code. If the OpenSSH code were instead under the GPL, those corporations would be obliged to fund it's development? No. Sure if it were GPL, then the companies would have to give back changes. However in this case, we can do without them giving back changes, because they SUCK at it. Sun with all their might, can keep their crap additions to OpenSSH in SunSSH.

      Furthermore, what makes Theo think that people want to run OpenSSH? At this point, it's as entrenched as Windows--nobody has a choice.

      People DO have choices. It's just that OpenSSH seems to be the best option. Regardless of whether it's free or not, open or closed, people are choosing OpenSSH over the other choices for good reason. OpenSSH became dominant long ago and continues to close the gap, also for good reason.

      Yet big corporations who SELL it, do not seem to think that they should throw in some small change (for them) and help to maintain it the best way anybody other than the excellent OpenSSH coders can... money. Sure they don't have to, but they also don't have to get new features and quick bug fixes either.

      If the big corporates want OpenSSH to remain of a high quality with quick and PROPER fixes, they can choose to help. Or they can choose to just ignore the problem and then deal with the disaster of finding that even though they are Sun, Apple or Cisco, they DON'T have the expertise in house who can maintain OpenSSH as well as the OpenSSH team. They might think they do, but Sun themselves have shown how little they understand the code and security implications, with their SunSSH branch.

      --
      War crimes, torture, lies, illegal spying... Would someone give Bush a blowjob, already, so he can be impeached?
    34. Re:what a whiner by micromuncher · · Score: 1

      You contradict your argument. The fact that the free software movement *does not* work is exactly why OpenBSD is having financial difficulties. Most of the people and businesses that reap the benefit of free software do not support it financially nor contribute. It is, after all, not a requirement! And operating systems and like tools are very niche markets. There is no money in giving away free product. Its free. The fact that you open it up for people to tweak and enhance is irrelevant. People need to eat; and as such the only real successful "business" off "open source" is consulting pursuant to the software. Distribution charges feed the distributors; not the contributors.

      So... until Theo drops notoriety and infamy for actually working with business to meet a need (and get consulting revenue), OpenBSD is about as useful as "a cock flavored lolly pop".

      --
      /\/\icro/\/\uncher
    35. Re:what a whiner by TheRaven64 · · Score: 1
      It's simple game theory, which tends to work a lot better than most morality-based ethical systems. If you benefit from something (e.g. OpenSSH being developed), then it is in your interests to ensure that this continues to happen. If the cost[1] of ensuring that something that benefits you continues to happen is greater than the cost of it stopping happening, then it is in your interests to ensure that it continues to happen.

      Theo's problem is that he expects people to act in their own long-term interests, when history has shown time and time again that very few people are capable of thinking in anything other than the immediate term.

      [1] Financial or otherwise.

      --
      I am TheRaven on Soylent News
    36. Re:what a whiner by TheRaven64 · · Score: 1
      the ssh 1.3 source would probably have been picked up by GNU and we'd have free GnuSSH

      On most UNIX-like systems, the su command only allows people to become root if they are in the wheel group. This makes your system slightly more secure, since a remote attacker[1] needs to compromise both the root password and the password of someone in the wheel group (rather than just any user, including the secretary who leaves her password on a post-it on her monitor).

      GNU su does not have this feature, since it would make it much easier to deny people root access to a system, which is an infringement of their basic freedoms (according to RMS).

      Would you really trust a GNU version of SSH with a security record like that?

      [1] I am assuming you have disabled remote root logins, like a good little admin.

      --
      I am TheRaven on Soylent News
    37. Re:what a whiner by Anonymous Coward · · Score: 0
      And being an uninformed idiot also means that you can comfortably talk out your ass as an anonymous coward . . .


      Ah, I see you've taken a page from my playbook there AC...heheh. And speaking of uninformed:

      Compare, for example, fair trade coffee, pharmaceutical companies distributing free meds to those cannot afford them, corporations that give time off to employees to volunteer in their communities, and the like. Each of these things doesn't contribute directly to the bottom line, and some take away from it.


      Got news for you: check the portfolio of a dipshit that invest in these (probably a real go-getter like you) and then check the portfolio of somebody who has a goddamned clue. The wakeup will be rude. Pharma firms that engage in this are running pure PR spin, and if you look at the aggregate dollar amount you'll see it's a pittance. Behind every giveaway are actuaries, statisticians and accountants calculating the damage that will be done if patent law is trashed, and thus recommend making donations to avert this, as well as buying the proper politicans and hiring the right lawyers. Don't even go there with the so-called "fair trade coffee" which taste like shit yet is still purchased by brain damaged left wingers. The funny thing is that in many cases the additional money is going straight to big agribusiness firms who prey on well-intentioned idiots. I do have to agree with time off to volunteer in the community where the company resides. This contributes to a more effective and cohesive work unit in the case of employers with a large presence in a given locale.

      Yet they exist--in reality. Just because you're a fan of the prevailing sociopathic corporate mentalities doesn't make those mentalities correct; it just makes you a jackass.


      No, it makes me self-interested. You're just like the assholes running around in Iraq right now who are working for various "charities".. a doe-eyed non-combatant just waiting to get slagged for "the greater good"..

      You assume that I endorse the current climate of nastiness in the business world, and once again you're wrong. I'm a survivor in a given environment. Do I wish we could be more compassionate? Sure. Am I going to risk my own ass for it? No way.

      I'm on the glidepath to retire in a few years in my 40's through careful planning and global investing. You tell me how things are at the coffee shop when I order my morning java from you. And don't forget the cream.
    38. Re:what a whiner by Anonymous Coward · · Score: 0

      Do I wish we could be more compassionate? Sure. Am I going to risk my own ass for it? No way.

      With an attitude like that, don't be surprised if your "cream" is a little, shall we say, heavy. Prick.

    39. Re:what a whiner by turbidostato · · Score: 1

      "In theory they'd be smart enough to feed the golden goose"

      Or they would make the best for the quarterly report (does *exist* anything else?) which is take the meal for free.

      Maybe this could kill the golden OpenBSD goose. So what? They don't use OpenBSD, do they?

      Oh! but then OpenSSH development would halt. So what? It is still uncertain that this will happen. And *if* happens, they still can hire de Raadt *then* (as opposite to "start paying *now*"), and have free meal while they can.

      Maybe it is not the world I'd prefer to live in, but I have to say it makes perfect sense to me.

      "I'd be really up the creek without OpenBSD for my firewalls (active failover on commodity hardware is a lot cheaper than the commercial alternatives)."

      As if there were no other free choices.

    40. Re:what a whiner by turbidostato · · Score: 1

      "Let me tell you a little secret. Theo does not get paid to speak. He refuses that kind of money."

      Then the previous poster must be right: there goes "Founding Opportunity #101".

    41. Re:what a whiner by Anonymous Coward · · Score: 0

      You mean like the gnu HURD !

    42. Re:what a whiner by turbidostato · · Score: 1

      "Theo's problem is that he expects people to act in their own long-term interests"

      Really? Maybe that's only what de Raadt *think* are their long-term interests.

      Maybe they think (a quite sustainable position) that their long-term insterest if leave de Raadt go for free as long as he can/want and then pay him peanuts once he is starving. To date, de Raadt is humming, but he is still coding... for free! Maybe those companies' best interest, while seeming a bit rude, is in fact allowing de Raadt code for free for as long as he will. Once de Raadt effectively stops coding, then and only then they will look for the alternatives: why start paying if only a day too early?

    43. Re:what a whiner by turbidostato · · Score: 1

      "it's just bad business. lately lots of companies got big on open source and seeing how SUN (and others) has openssh based products, it would be freakin common sense to give something back to the developers"

      So for any given company give some money in order for Sun (and others not them) go bigger is somehow "freakin common sense", uh?

      It seems to me that it is common sense for just a single (group of) company: Sun (and such named others). But then, Sun (and such named others) gives money every week to quite a big bunch of developers. It is only that, as per paragraph#2, giving money away doesn't really seems "freeking common sense" after all, so Sun doesn't give it away; it gives it to certain people which accord to certain ammount of obligations in regard, in order for Sun to insure their expenditure. These people are called "employees". Since de Raadt is not a Sun employee, well, I think you can follow the reasonement.

    44. Re:what a whiner by kv9 · · Score: 1

      ok, perhaps i should have used `the freakin neighborly thing to do' instead of `freakin common sense'. will that do? and project support/donations have nothing to do with being an employee.

    45. Re:what a whiner by turbidostato · · Score: 1

      "and then deal with the disaster of finding that even though they are Sun, Apple or Cisco, they DON'T have the expertise in house who can maintain OpenSSH as well as the OpenSSH team"

      The "whole OpenSSH team" is, how many? seven guys? It is still "small change" for Sun *OR* HP *OR* IBM. Please remember that there's no such chymera as "Sun and HP and IBM" (that would be the kind of beast that would benefit from supporting de Raadt et al.); it is more on the lines of "Sun against HP against IBM".

      Then, please, consider this: currently Sun giving support to the de Raadt team means giving support to HP and IBM, you know, the guys in the "against" phrase. And while de Raadt is humming, the fact is *today* de Raadt is still coding for free and Sun (and IBM and HP, each one by its side) still can get OpenSSH for free and, what it is much more important, without founding advantages to their respective competitors.

      Tomorrow *if* de Raadt et al. stop coding and *if* they can't find an appropiate OpenSSH substitute *maybe* one of them would consider hiring de Raadt et at. still for (comparatively) peanuts and, what is again more important, taking them away from their competitors (specially since we are talking about BSD-licensed software here).

      *That* does make sense for those corporations.

      Oh, and by the way, were OpenSSH licensed under the GPL, then *maybe* there were some chance for the "Sun and HP and IBM" beast comming to live, knowing each of them that the others wouldn't be able to "jump from" the "code base line" add some bells and whistles and make a competitive advantage from it, since immediatly the other parties would know they'd have access to those "bells and whistles". That *maybe* would soustain the needed common ground so they would want to found those "guys out the company control".

      Under the BSD? No way!

    46. Re:what a whiner by Shanep · · Score: 1

      Then, please, consider this: currently Sun giving support to the de Raadt team means giving support to HP and IBM, you know, the guys in the "against" phrase.

      Don't forget, this is just a small part of the systems which those vendors ship. I fail to see how having a better SSH implimentation is going to give some vendor any worthwhile advantage. I would have thought that the much bigger features like for example the big Sun virtualization stuff and powerful machines are the types of things that give worthwhile competitive advantage over some other competing vendor. A small tool used for textual secure remote access that everyone else has? No, I don't see it.

      And while de Raadt is humming, the fact is *today* de Raadt is still coding for free and Sun (and IBM and HP, each one by its side) still can get OpenSSH for free and, what it is much more important, without founding advantages to their respective competitors.

      How can you be founding *advantages* to your competitors, when in reality what you are doing is simply keeping the playing field level in that one respect, but also providing your customers indirectly with better features and continued security.

      --
      War crimes, torture, lies, illegal spying... Would someone give Bush a blowjob, already, so he can be impeached?
    47. Re:what a whiner by turbidostato · · Score: 1

      "How can you be founding *advantages* to your competitors, when in reality what you are doing is simply keeping the playing field level"

      Because you don't know where that path reaches. As you already said, you don't see how a better secure shell program can make any difference when we are talking about such big companies (nor do I). What those companies do know is that somewhere there *is* a competitive advantage (they know it best, since they found the "hired competitive advantage" in the past). For the best they know, it migth be just some steps right or left of even current OpenSSH whitout them figuring it yet; the more powerful OpenSSH comes, the more chances there exists that "short derivative that will somebody earn millions", so to say. Under the GPL, they know that such derivation will be accesable for them at the very moment any of their competitors discovers it (ie: interesting new features on the Linux kernel), and even then, greed, fear to the unknown, or percieved advantages on other fields may avoid them sharing resources (not even water to the enemy). Under the BSD, they won't pay for the chance of others discovering it (ie: the competitive advantages on MacOSX over its BSD licensed foundation).

      Please note that I am not telling you are wrong. You are rigth... under the asumption that is the society as a whole the one that benefits from de Raadt development. But the fact is that it is not the "society" the one who pays, but each given company. It's a classical "prisioner dilemma" situation.

    48. Re:what a whiner by Jussi+K.+Kojootti · · Score: 1
      1. Ahh, language problem -- I didn't know the difference of a corporation and a company in english. You are right of course.

      2. Well, I do believe that just about any stakeholder theory can be based on shareholder value... Keeping your employees happy may increase shareholder value and so on. Stuff that isn't easily converted to shareholder value (like protecting the environment) should be regulated, in my opinion -- stakeholder theories just don't seem to work there in practice.

      3. Agreed. I'm amazed this doesn't happen more.

    49. Re:what a whiner by penguin-collective · · Score: 1

      Regardless of what motivations RMS has, there is no evidence whatsoever that restricting su to wheel helps security; it may actually hurt it. But that's the problem with computer security: most people don't know anything, they just make things up. Like you.

    50. Re:what a whiner by Shanep · · Score: 1

      Under the BSD, they won't pay for the chance of others discovering it (ie: the competitive advantages on MacOSX over its BSD licensed foundation).

      I'm not sure what you are getting at. Are you saying that companies would not want to support a BSD licenced project because it allows other companies to discover the fruits of that support? And thus gain for free from the supporting companies investment?

      I see it the opposite...

      I thought that big businesses would be more likely to support a BSD licenced project, than a GPL'ed one, because, take Sun for example, they can help to keep OpenSSH finances healthy pretty easily, continue to develop their own SunSSH and then just back-port fixes and any new features they like from OpenSSH into their own SunSSH. They would get a solid foundation, continued expertise from the developers of that foundation (directly through peronal updates or indirectly by watching the changes) and not have to give back their own changes to OpenSSH and thus the competition.

      Of course, the reality seems to be much more different, with GPL'ed software seemingly getting most support from companies.

      I don't know. I just hope OpenBSD and OpenSSH will be around for at least another 10 years.

      --
      War crimes, torture, lies, illegal spying... Would someone give Bush a blowjob, already, so he can be impeached?
    51. Re:what a whiner by Bing+Tsher+E · · Score: 1

      Theo still makes his name by hacking code. Peek into an OpenBSD mailing list, and you'll see him actively involved in the discussions with the other developers.

      Stallman seems to have retired to a career of giving speeches. When did he last hack any code that runs in the main body of any significant project?

      Personally, though I don't use OpenBSD at present, I am glad that Theo keeps the priorities that he does.

    52. Re:what a whiner by Bing+Tsher+E · · Score: 1

      there is no evidence whatsoever that restricting su to wheel helps security; it may actually hurt it.

      Huh? You're going to hand-wave like that and assume you've made your point?!?

      RMS has historically deplored passwords. Back in the day at MIT he actively campaigned against passwords on the timesharing system. He is an anti-password ideologue. The GP was citing an instance.

  8. Bitchy by Schraegstrichpunkt · · Score: 1

    Wow, is Jem ever whiney...

  9. You doity raht by The+Famous+Brett+Wat · · Score: 4, Funny

    Is it just me, or does anyone else always feel the urge to pronounce "Theo de Raadt" as "Theo da Rat" with a mafia godfather style accent?

    --
    proof, n. A demonstration that a conclusion is implied by certain premises and axioms.
    1. Re:You doity raht by Anonymous Coward · · Score: 1, Informative

      It's pronounced "theo de wrought", he's dutch.

    2. Re:You doity raht by udippel · · Score: 1

      Crap.
      AFAIK, he's of South-African descent. And probably by now a Canadian citizen.
      Ask him. Try Google.
      Whatever. Don't post things you have no clue about.

    3. Re:You doity raht by Anonymous Coward · · Score: 0

      Although he himself is probably a South African national, he's obviously of Dutch descent. In case you don't know, SA was colonized by the Dutch in the seventeenth century.

      In your own words, try Google.

      Whatever. Don't post things you have no clue about.

    4. Re:You doity raht by T-Ranger · · Score: 1

      And South Africa was at least partial settled by the Dutch. (see Boer War)

    5. Re:You doity raht by udippel · · Score: 1

      In case you wanted to support the AC, think a bit harder: Does SA being settled partially by the Dutch hundred years ago make Theo a *Dutch* ?

      Ridiculous. Of course, if I wanted to write big BS, I'd also go for AC.

    6. Re:You doity raht by Anonymous Coward · · Score: 0

      nationality is in Blood, Spirit and Culture, not in the country you're currently residing

    7. Re:You doity raht by pafrusurewa · · Score: 1

      So Americans are Brits? Really, the US and Britain have more in common than the Netherlands and South Africa.

  10. Problem with BSD licencing by PAPPP · · Score: 4, Insightful

    This is a perfect example of the problem with BSD licencing. Under the various BSD licences, its perfectly OK to take a piece of code and sell it, either modified or exactly as found, without in any way recognising or contrubuting to the project. Run "strings c:\windows\system32\ftp.exe" on a WinXP box and you'll see a perfect example of uncredited work. At least under the GPL if someone sells an unmodified program, the project will get recognition (since it will have to remain open source, and thus the origion of the code will be obvious), and if they sell a modified version the project will get the source for the modifications back. Neither directly equates to funding, but publicity and a better code base both help to attract financial support. Both arrangements depend somewhat on the cooperation and altruism of the entity using the code for a profit, but the GPL isn't quite so hopelessly naive.

    1. Re:Problem with BSD licencing by AHumbleOpinion · · Score: 1

      This is a perfect example of the problem with BSD licencing. Under the various BSD licences, its perfectly OK to take a piece of code and sell it, either modified or exactly as found, without in any way recognising or contrubuting to the project.

      And BSD developers know that, accept that, and often want corporations to use their stuff. With easier corporate acceptance there is more opportunity for consulting. Unfortunately with someone like Theo scaring away corporations his pet projects suffer, I'm thinking the DARPA incident.

      I've mentioned this in another post but be careful with words like "contributing". As California corporations and taxpayers companies like Apple and SCO paid for BSD's development. Apple have every moral and ethical right to use it.

    2. Re:Problem with BSD licencing by Blurgle · · Score: 1
      This is a perfect example of the problem with BSD licencing. Under the various BSD licences, its perfectly OK to take a piece of code and sell it, either modified or exactly as found, without in any way recognising or contrubuting to the project.

      You must have missed this page: http://technet2.microsoft.com/WindowsServer/en/Lib rary/fcfb3f7d-b209-4bb8-a1ca-f5259b6d57191033.mspx

      --
      slashdot := Object clone do(forward := method(self); removeAllProtos)
    3. Re:Problem with BSD licencing by Lisandro · · Score: 1

      This is a perfect example of the problem with BSD licencing. Under the various BSD licences, its perfectly OK to take a piece of code and sell it, either modified or exactly as found, without in any way recognising or contrubuting to the project.

          It is NOT a problem with the license. It's the way it is, and if it doesn't suit you, you shouldn't be developing software under the BSD license at all - there's a number of open source licenses to choose from. You can even write your own one and set your terms.

          Expecting financial contributions for useful projects such as OpenBSD/OpenSSH is more than reasonable - one could even argue about the moral obligation of large companies using (and sometimes even depending on) OSS software developed by third parties. Demanding cash just because companies followed to the letter the license that came with your software though, is plain insane. If the OpenBSD folks need some cash, i'm sorry to say this, they'll need to come with another buisness strategy.

    4. Re:Problem with BSD licencing by bhima · · Score: 1

      Actually to me this sounds like a fundamental flaw in the nature of businesses and capitalism...

      If businesses were required to act more responsibly and more in the civic interest none of this would be an issue, but capitalism as it is implemented in the western democracies does not allow for this.

      --
      Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
    5. Re:Problem with BSD licencing by Darby · · Score: 4, Interesting

      I've mentioned this in another post but be careful with words like "contributing". As California corporations and taxpayers companies like Apple and SCO paid for BSD's development. Apple have every moral and ethical right to use it.

      They paid for ancient BSD development. However after the court cases were over, that went away.
      They have every *legal* right to use it.
      They have an ethical responsibility to contribute but this is in no way required.
      Morality is individual, so were you talking about a person it would be their choice as to what their morality is. As you're discussing corporations, they inherently and as required by law are entirely amoral.

      This is certainly about as clear a demonstration as you can find of the difference between the BSD license and the GPL, but other than that, which wasn't explicitly in there, there really isn't anything to your post.

      Is Theo justified in calling the people who used his code without giving anything back asshats? Absolutely.
      Can he force them to? Absolutely not.

      That's the license he chose and he's well aware of the ramifications.

      The thing to me that most sucks was that Stallman and the BSD folks basically made a bet on human nature.
      The optomists are losing badly.

    6. Re:Problem with BSD licencing by AHumbleOpinion · · Score: 2, Insightful

      They paid for ancient BSD development. However after the court cases were over, that went away. They have every *legal* right to use it. They have an ethical responsibility to contribute but this is in no way required.

      It's not so ancient: "Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved". An this code remains at the heart of the *BSD projects.

      Morality is individual, so were you talking about a person it would be their choice as to what their morality is. As you're discussing corporations, they inherently and as required by law are entirely amoral.

      Completely false. They are permitted by law to be amoral in some respect, they are not required to be. A corporation can choose to act in a moral fashion. In any case Apple satisfies the "open source morality" issue since they have also made recent contributions, for example their formerly closed source HFS+ code.

      The thing to me that most sucks was that Stallman and the BSD folks basically made a bet on human nature. The optomists are losing badly.

      Untrue. We've seen various GPL based projects in financial trouble and begging for donations as well, including Linux distributions. Also, in general profit with open source is often said to be from consulting. Whether a project is GPL or BSD based has little effect, you could even argue that BSD has an advantage since it is easier to get into a corporation and a corporation may not want to share the changes they paid for.

    7. Re:Problem with BSD licencing by Plunky · · Score: 2, Funny
      The thing to me that most sucks was that Stallman and the BSD folks basically made a bet on human nature. The optomists are losing badly.

      You might consider me one of those optomists, since I release software under the BSD licence.

      How have I lost anything? I gave what I had away, with no expectation of rewards..

      In fact I gained something. I gained the smugness I am showing to you now.

    8. Re:Problem with BSD licencing by localman · · Score: 1

      The thing to me that most sucks was that Stallman and the BSD folks basically made a bet on human nature. The optomists are losing badly.

      Are you kidding? Anyone who has any real sense of how the computer landscape changed over the past decade knows that the optomists won big time. The vast majority of the internet is interoperable despite the best efforts of the pessimists. Free software, and the free exchange of ideas between developers has flourished and fostered this. Communication channels are open now that were never open before. There is a greater breadth of content at your fingertips than anyone could have imagined back then.

      The original motivation of the free software movement was not to make money. It was to make the tech world a better place. This has happened, and it happened mostly because of free software.

      Pessimist indeed.

      Cheers.

    9. Re:Problem with BSD licencing by DNS-and-BIND · · Score: 1
      Yes, more government restrictions would "cure" capitalism. Great idea.

      The businesses are complying with the conditions of the BSD license. Where's the problem?

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    10. Re:Problem with BSD licencing by Anonymous Coward · · Score: 0

      At least under the GPL [...] they sell a modified version the project will get the source for the modifications back.

      This is a common misconception about the GPL. There is no contract between the
      project and the developer of the modifications. The obligation of disclosure
      only goes to the recipient of the modified product, not to the original developers.

      It is perfectly possible that the only way the project can get the modifications is by
      buying the product and requesting the sources explicitely. The vendor doesn't have the obligation to supply the sources when not asked for it. And only the buyer has the right to ask.

    11. Re:Problem with BSD licencing by Jussi+K.+Kojootti · · Score: 1
      Completely false. They are permitted by law to be amoral in some respect, they are not required to be. A corporation can choose to act in a moral fashion.
      Huh? That's bull.

      If management makes a "moral decision" knowing it will lower shareholder value, the shareholders may sue (and win). So, yeah, companies are required to act amorally as long as it's best for their shareholders.

    12. Re:Problem with BSD licencing by Antique+Geekmeister · · Score: 1

      I suggest you look into the South African boycotts, and how many shareholders in fact successfully forced their investment companies to participate in the boycott. I also suggest you look into the various non-profit companies, and commercial company charters, to see that the actual goals of the company may not be shareholder profits.

      It's a common belief, taught in many early level MBA courses and management training meetings, that shareholder profit is all. But it's simply not true in law, in theory, or in real life.

    13. Re:Problem with BSD licencing by justins · · Score: 1
      As you're discussing corporations, they inherently and as required by law are entirely amoral.

      One of the dumber things I've read this week.

      The thing to me that most sucks was that Stallman and the BSD folks basically made a bet on human nature.
      The optomists are losing badly.

      Now that is a bit more interesting.
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    14. Re:Problem with BSD licencing by Darby · · Score: 1


      Are you kidding? Anyone who has any real sense of how the computer landscape changed over the past decade knows that the optomists won big time. The vast majority of the internet is interoperable despite the best efforts of the pessimists.


      In many ways you're right. The "best efforts" weren't by the pessimists in question though. The interoperability is due to the efforts of both the BSD folk and the GPL folk. It's largely MSand in part some of the big Unix vendors who were trying to eliminate interoperability.


      The original motivation of the free software movement was not to make money. It was to make the tech world a better place. This has happened, and it happened mostly because of free software.


      True as well. I should have been more specific about what I meant. It isn't "the BSD folk" in general for which that is true. Just those who put their work out with no requirement for anything in exchange and then are surprised when they get nothing for it.

    15. Re:Problem with BSD licencing by Anonymous Coward · · Score: 0
      If management makes a "moral decision" knowing it will lower shareholder value, the shareholders may sue (and win). So, yeah, companies are required to act amorally as long as it's best for their shareholders.


      Bullshit. See: Johnson and Johnson during the Tylenol scare. The recall they pulled was about 100x larger than required.
    16. Re:Problem with BSD licencing by Shanep · · Score: 1

      The businesses are complying with the conditions of the BSD license. Where's the problem?

      The problem, is that people equate the code as released to be free of charge, without considering that the maintenance of that code costs money and the future of that maintenance and thus the future of the quality of that code is not in any way guaranteed. Then some companies stake their reputations partially in that code and then choose not to support it at all, yet the best way to support it turns out to be very cheap? Theo is just as free to ask for financial support, as the users are free to deny him that support. But, Theo and crew are also free to just stop maintaining the code.

      People need to realise that although the code is released free and open, the maintenance of that code can stop at any time due to the simple fact that the developers need to eat and also according to the licence they are in no way obliged to continue maintaining the code (warranties disclaimed).

      So, with all of that in mind, ultimately the future is in the hands of the users, big and small. They can choose to ignore the problem that the developers of this excellent software need to eat and then suffer the consequences. The problem is not the BSD licence, the project developers or Theo, the problem is the users. Especially the big ones which can easily help and have the most to gain.

      --
      War crimes, torture, lies, illegal spying... Would someone give Bush a blowjob, already, so he can be impeached?
    17. Re:Problem with BSD licencing by Shanep · · Score: 1

      This is a perfect example of the problem with BSD licencing. Under the various BSD licences, its perfectly OK to take a piece of code and sell it, either modified or exactly as found, without in any way recognising or contrubuting to the project.

      Attribution in this case would not help. Everyone knows that OpenSSH is developed by the OpenSSH project and the people who stand to gain the most and be in a position to give back the most for the code that is in SunSSH for example, is Sun themselves. Sun chooses not to. The GPL would not have got the OpenSSH team money out of Sun. All it could get in that case is a guaranteed minimum of recognition in an obscure bit of software which sane people choose to replace with the real thing anyway (OpenSSH proper) and the ability to take back some really crappy code which the OpenSSH team would not want.

      The users use the code for free. But apparently just expect without a second thought, that updates to the code in the form of bug fixes and new features, will continue to come, which they also will not have to pay for. The users fail to realise that although the code is free, it did actually cost money to make. If they want that software to be maintained well, they can choose to donate. It's a choice, where the quality of software they choose to use can either be retained or suffer.

      The BSD licence is about providing great freedom. The users are free to support that great freedom or let it rot. Considering how great OpenSSH and OpenBSD are, I find it really amazing that users big and small are mostly fine with just sitting on the sidelines and watching the projects suffer, when a lot of people gladly use all that software.

      The generosity should not be one-way just because it can be.

      --
      War crimes, torture, lies, illegal spying... Would someone give Bush a blowjob, already, so he can be impeached?
    18. Re:Problem with BSD licencing by TheRaven64 · · Score: 1
      I would hardly consider paying to ensure that a product from which your company derives a significant amount of value continues to be actively developed to be a 'moral' decision. It seems to me to be a fairly simple business decision.

      There is a big difference between 'maximising shareholder value' and 'maximising shareholder value today at the expense of shareholder value tomorrow.' Short term thinking has caused significant problems for several corporations, not to mention companies, in recent years.

      --
      I am TheRaven on Soylent News
    19. Re:Problem with BSD licencing by smithtodda · · Score: 1

      The optomists are losing badly.

      So are the English teachers.

      --
      Why Vegan? No other food choice has a farther-reaching and more profoundly positive impact on all of life on Earth.
    20. Re:Problem with BSD licencing by Jussi+K.+Kojootti · · Score: 1
      I would hardly consider paying to ensure that a product from which your company derives a significant amount of value continues to be actively developed to be a 'moral' decision. It seems to me to be a fairly simple business decision.
      ...which is why I didn't object to that in any way.
      There is a big difference between 'maximising shareholder value' and 'maximising shareholder value today at the expense of shareholder value tomorrow.' Well, no. Value today includes the value tomorrow (just discounted).
    21. Re:Problem with BSD licencing by know1 · · Score: 1

      "Run "strings c:\windows\system32\ftp.exe" on a WinXP box and you'll see a perfect example of uncredited work"
      F:\Documents and Settings\wysiwyg>strings f:\windows\system32\ftp.exe 'strings' is not recognized as an internal or external command, operable program or batch file.

      er, i love me unix (got a debian box too) nad would love to actually see this mythical output...what did you mean exactly? maybe i typed it wrong...

    22. Re:Problem with BSD licencing by know1 · · Score: 1

      ok, i did manage to make that command work in cygwin by changing it a little to :
      $ strings /cygdrive/f/windows/system32/ftp.exe
      and see the copyright 1983 cally stuff on it. Did xp ever have this command? maybe bill removed it after hearing about people seeing this stuff (i have heard this statement before but didn't try it out).

    23. Re:Problem with BSD licencing by nihaopaul · · Score: 1

      nihaopaul@mean-bitch /cygdrive/C/windows/system32
      $ strings *.exe | grep Copyright | grep -e "University of California" | wc -l
      6

      ^_^

  11. Re:Iff..... by Theatetus · · Score: 3, Informative
    Can anyone tell me why BSD with it's enhanced security isn't incorporated into most Linux distros? How Unix like is it actually?

    Where to start?...

    BSD is an operating system. It consists of a kernel (like linux), a userland (like GNU), and a bunch of applications which are largely source-compatible with Linux.

    The BSDs share the fundamental gcc/gas/ld toolchain with GNU, but pretty much everything else (particularly the C library and make) they have their own version of. It is *possible* to run the BSD system on Linux (though not very easy), and actually very easy to run the entire GNU system on BSD. But they are different projects.

    OpenBSD was the result of a squabble between Theo and the NetBSD team. This was a felicitous squabble for the rest of us, because OpenBSD is a great operating system.

    --
    All's true that is mistrusted
  12. Re:Iff..... by Eightyford · · Score: 2, Informative
    Can anyone tell me why BSD with it's enhanced security isn't incorporated into most Linux distros?
    Because BSD is an Operating System, and GNU/Linux is an operating system... try reading that article again.
    And you should probably try to understand what the original poster actually meant. How about, "why doesn't linux implement parts of BSD into it". Understand now?
  13. I bought the T-shirt by fossa · · Score: 1

    I bought the T-shirt; does that count?

    1. Re:I bought the T-shirt by bhima · · Score: 2, Interesting

      I hope so! I did to and I did it because OpenBSD is rapidly becoming the only OS I trust enough to mount a rented DVD on and be absolutly sure I don't wind up with any sneaky malware...

      --
      Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
    2. Re:I bought the T-shirt by cafard · · Score: 1

      So did i, it's not a lot, but it's still a small individual support. I never ran OpenBSD, but i'll eternally grateful for OpenSSH.

      --
      This post is awesome.
    3. Re:I bought the T-shirt by parasonic · · Score: 1

      Yes it does, but until everyone buys a shirt, the funds from it are a drop in the bucket. I was thinking about getting the one with the "prostitute solicitor" with the cane and the hat and a girl on each side..."Chicks Dig OpenBSD"...I could ward off the remaining few girls that I get here at my tech school...

  14. Re:Iff..... by ArbitraryConstant · · Score: 3, Interesting

    "Can anyone tell me why BSD with it's enhanced security isn't incorporated into most Linux distros?"

    It's not a simple matter of importing code, to duplicate the changes in the Linux kernel and the GNU toolset would be prohibitively difficult. Also, much of the improved security comes at the expense of performance or functionality.

    --
    I rarely criticize things I don't care about.
  15. Job interview question by Anonymous Coward · · Score: 2, Insightful

    I was recently asked in a job interview "If Theo de Raadt and Dan Bernstein were locked in a room with knives, who would you want to come out alive?"

    (and my interviewer is probably reading this, in which case, "Hi there!")

    I said I wanted Dan Bernstein to come out alive, because I actually use his stuff in production as opposed to OpenBSD... but after thinking about it for a while I realised that OpenSSH is perhaps more important that Dan Bernstein's stuff. I mean, Dan never updates qmail and any of his tools... Theo may as well bump him off for all I care. ;P

    1. Re:Job interview question by IgnoramusMaximus · · Score: 3, Funny
      I was recently asked in a job interview "If Theo de Raadt and Dan Bernstein were locked in a room with knives, who would you want to come out alive?"

      At which question I would have gotten up, broken off a leg table, and proceeded to ask "Where are they?!" so that I can proceed to give Dan a hand, musing to myself that it is at times like these that I wish I were a gun nut.

      I am afraid this kind of a reaction would have been rather popular amongst those who had a pleasure of reading Theos' "conversations" with people on some of the USENET groups of old. Theo is just such a charming, loveable guy that swiss army knives open spontaneously in people's pockets at the very mention of him.

    2. Re:Job interview question by Koutarou · · Score: 0

      Hi Nathan,

      The exact reply to the question didn't really matter. The amount of time you think about it is what I look for.

    3. Re:Job interview question by Anonymous Coward · · Score: 0

      While Dan writes great code, his greater contributions fall within the realm of Cryptography and Mathematics. In that context, arguably Dan has contributed far more to man kind than Theo.

      I like Theo's ethics more, though. Dan's software licenses are lamentable (you write provably correct code; WE GET IT. Now can we just use it for w'ever we please!?)

    4. Re:Job interview question by lintux · · Score: 1

      Hmm, now I'm getting curious. I know this is off-topic, but I can't resist. ;-) What does that amount of time mean to you exactly? I would certainly need some time to answer it, because I hate both guys. :-)

      Although in the end I'd go for Theo, since at least he isn't helping in making the spam problem bigger by writing crappy MTAs.

    5. Re:Job interview question by IgnoramusMaximus · · Score: 4, Insightful
      The exact reply to the question didn't really matter. The amount of time you think about it is what I look for.

      Was it me, you would have found out that it takes only 0.3 seconds to have a horrible accident with your coffee spilling all over your lap. Applogies and all that, why, I am just such a horrible klutz!

      Joking aside, but that sort of question would have me thanking you for the lovely opportunity to get interviewed by you, followed by a mental note not to ever do business with you, under any circumstances.

      Has it ever occured to you that these types of smart-ass, self-congratulatory questions, main purpose of which is to show who is the smart alpha-dog in that interview room, are absolutely useless in ascertaining someone's workplace abilities? Oh, what am I talking about, if it had, you would not be asking that and all the other ridiculous "logic" puzzles I am sure you are inflicting on your poor hapless, victims ... err ... applicants.

    6. Re:Job interview question by Anonymous Coward · · Score: 0

      GrouchyGuyWare(tm) - I love both of them for that - It is a nice change of pace - they aren't warm and fuzzy, they have unusual rules (no compiling yer own customer kernel, rrraaahhh - no changing file locations, grrrr) and people want to discount their fine work for that stuff?

      I say I'd rather have the great code and deal with a few quirks (and people probably say they should do both - be warm and fuzzy and write great code, next people will say you should be a nobel prize winner _and_ a super model)

      --- I'd bust down the door and take both of them out for ice cream (now then... what flavor, cup or cone, sorbet or tofutti...

      Captcha: common

    7. Re:Job interview question by Anonymous Coward · · Score: 0

      If Theo de Raadt and Dan Bernstein were locked in a room with knives, who would you want to come out alive?

      Both of them being locked in a room is enough for me.

    8. Re:Job interview question by Anonymous Coward · · Score: 0

      The exact reply to the question didn't really matter. The amount of time you think about it is what I look for.

      Yes, I remember you saying that at the interview. It was a funny question though and gave me a laugh, so I guess I thought about it longer than I needed to. :D

    9. Re:Job interview question by DNS-and-BIND · · Score: 1

      Man, I'm glad I don't have to put up with snippy little gotcha job interview questions that have absolutely nothing to do with the job at hand.

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    10. Re:Job interview question by ettlz · · Score: 1
      Theo is just such a charming, loveable guy that swiss army knives open spontaneously in people's pockets at the very mention of him.

      That's about the funniest damn thing I've read all week!

    11. Re:Job interview question by wild_berry · · Score: 1

      I'm horrified by the question and its sentiments. Both Dan and Theo are human people. Never can one justify wishing one person dead in another's place. Were I an employer, I'd be careful not to send the wrong message out to people being interiewed by asking this question.

    12. Re:Job interview question by Anonymous Coward · · Score: 0

      >Theo is just such a charming, loveable guy that swiss army knives open spontaneously in people's pockets at the very mention of him.

      Ouch, i feel sorry for all those that lost a testicle.

    13. Re:Job interview question by Kjella · · Score: 1

      I was recently asked in a job interview "If Theo de Raadt and Dan Bernstein were locked in a room with knives, who would you want to come out alive?"

      My answer would be "Both of them so barely, but hopefully a lot humbler." One of the nice things about OSS is that you don't have do actually deal with them, unless you want to. So I want them both alive and productive so it can show up in an apt-get repository near me. And if that's all the "contact" I need to have with them, that's fine with me.

      --
      Live today, because you never know what tomorrow brings
    14. Re:Job interview question by Anonymous Coward · · Score: 0

      Theo de Raadt at least acknowledges that other people have other ways to do things, and licenses accordingly, and his minions write flexible tools accordingly. I'd much rather work with OpenBSD binaries and integrate them into UNIX or Linux than almost anyone else's basic stuff because it's universally good. Dan's brilliance has played out. Somebody put him out of our misery, please.

    15. Re:Job interview question by Anonymous Coward · · Score: 0

      Have you ever tried to negotiate a fight between open source mavens? It's not a dumb question at all.

      Now, my answer is "Oh, here's the long form of my resume. See that job right there in college, which included breaking up fights between gangpunks in a lockup? Here, let me jot down the references for that on my reference form." Followed up by the comment "I have a few knife scars: do you need to see them?"

      I'm a scary man to interview: the best scars are under my pants, thought, so it could get awkward showing them.

    16. Re:Job interview question by kv9 · · Score: 1
      I'm horrified by the question and its sentiments. Both Dan and Theo are human people.

      ooooh so it's all right when Superman and Batman need to engage in mortal superherous combat in some nerd conversation, but *never* FOSS heroes? personally, i'd like to see RMS and ESR have a go at it, but i also think that theo could kick everyone's ass.

    17. Re:Job interview question by Anonymous Coward · · Score: 0

      wanker

    18. Re:Job interview question by Myrrh · · Score: 1

      Yeah, but then Ballmer would show up, start jumping and dancing around the stage like a lunatic, screaming "I LOVE THIS COMPANY!!!! DEVELOPERS DEVELOPERS DEVELOPERS!!!!!!1one!" and then proceed to throw chairs at Theo, knocking him out and possibly killing him.

    19. Re:Job interview question by raddan · · Score: 1

      Interviewer: Goodnight, ding-ding-ding-ding-ding.

    20. Re:Job interview question by IgnoramusMaximus · · Score: 1
      Interviewer: Goodnight, ding-ding-ding-ding-ding.

      Perfect illustration of my point. This "joke" is unclear to a vast majority of people, i.e. everyone who does not happen to have the same frame of empirical or cultural reference as you. It case you wonder, that does not make you into a master of sublime humour, and only demonstrates a lack of ability to communicate in universally understood terms, in favour of obscure self-centered riddles.

    21. Re:Job interview question by raddan · · Score: 1

      Why are you reading /. if you can't find enjoyment in obscure jokes? Fucking lighten up, man. Read this and realize that I was agreeing with you.

    22. Re:Job interview question by IgnoramusMaximus · · Score: 1
      Why are you reading /. if you can't find enjoyment in obscure jokes?

      Sometimes I do wonder.

      Fucking lighten up, man. Read this and realize that I was agreeing with you.

      You had me there, I do not religiously study the whole of the Monthy Python's career, and I am afraid quite a lof of other people had no clue what you were refferring to, either.

  16. It's not just openSSH by Theatetus · · Score: 5, Informative

    If you're a Linux user and you like your madwifi driver, you can thank the OBSD ath driver. Also if you ever want a RALink driver, OpenBSD is the only OS that has one right now and it seems almost certain any ports will be based off it. Anonymous CVS? Theo came up with it after NetBSD kicked him off the commit list. Randomized mmap, stack protection ... there's a lot of development being taken from openbsd. We've all got an interest here.

    --
    All's true that is mistrusted
    1. Re:It's not just openSSH by Baki · · Score: 1

      If the people writing those drivers would not be working on OpenBSD, they would probably write those drivers for FreeBSD or Linux.

    2. Re:It's not just openSSH by Anonymous Coward · · Score: 0

      That's just crap. Linux has had ralink drivers for a long time already:

      http://www.ralinktech.com/supp-1.htm
      http://rt2x00.serialmonkey.com/wiki/index.php/Main _Page

    3. Re:It's not just openSSH by pherthyl · · Score: 1

      That's not how it works. People do open source development because they enjoy it. Obviously these people liked working on stuff for OpenBSD and not for Linux. For whatever reason that's what they liked best. If they couldn't do that, it is far from guaranteed that they would write for Linux/*BSD instead. The prospect of writing for Linux might not entice them enough to bother starting at all.

      Would all the KDE devs be Gnome/Fluxbox/XFCE/etc devs if KDE didn't exist? Not bloody likely. Programmer resources in open source can't just be shuffled around like that.

    4. Re:It's not just openSSH by Anonymous Coward · · Score: 1, Informative

      If you're a Linux user and you like your madwifi driver, you can thank the OBSD ath driver.

      Completely wrong. The madwifi project uses code written by Sam Leffler for FreeBSD and Linux. madwifi does currently *not* implement the ath OpenHAL from OpenBSD, it uses the blob ath_hal that Sam provides under NDA.

    5. Re:It's not just openSSH by Theatetus · · Score: 1

      Well, no, that driver is still in beta, and it wasn't even around 2 years ago when I switched to OpenBSD (which at that point fully supported RT2500).

      --
      All's true that is mistrusted
    6. Re:It's not just openSSH by kv9 · · Score: 1
      If the people writing those drivers would not be working on OpenBSD, they would probably write those drivers for FreeBSD or Linux.

      so basically, you don't have any appreciation for anyone? if Torvalds wouldn't have sat down to create his own little UNIX, RMS overdosed on LSD and never got the GNU movement off the ground, BSD never got started *probably* other people would have done all those things anyway.

      right. fuck recognition, that is like soooo overrated.

      unfortunately for you, and fortunately for me the reality is that all those people *did* their great things that changed the `it landscape'. and even if i may dislike the attitude of some, i still respect them for what they achieved and not dismiss them with a big fat `meh'.

  17. I love OpenBSD by maelstrom · · Score: 1, Troll

    But this guy is an ass. There are plenty of Open Source products that people don't pay for. Does Google pay for Linux and Apache? Does Yahoo pay for FreeBSD, does Apple? Nope. If you don't like it, don't use the license.

    Someone would probably give OpenBSD a grant, but Theo has already proven he doesn't know when to shut up and has problems playing with others. Cry me a river.

    --
    The more you know, the less you understand.
    1. Re:I love OpenBSD by Anonymous Coward · · Score: 0

      Google donates heavily to those projects (and more), FYI.

    2. Re:I love OpenBSD by AHumbleOpinion · · Score: 1

      Does Yahoo pay for FreeBSD, does Apple?

      As California taxpayers they *paid for* BSD in the first place.

    3. Re:I love OpenBSD by Noksagt · · Score: 4, Insightful
      Does Google pay for Linux and Apache?
      Google does submit patches to these projects and has sponsored interns and employees work on various open source projects.
      Does Yahoo pay for FreeBSD
      Yahoo! hosts the freebsd.org cluster. They pay bandwidth and power and most of the hardware. They even give hardware to developers and employ several coders for the project fulltime.
      does Apple?
      I don't know Apple's financial commitment. They do give code back. Furthermore, they have really forked FreeBSD, so aren't directly using all of the "upstream" support, maintenance, development, etc. of FreeBSD.
    4. Re:I love OpenBSD by Darby · · Score: 1


      As California taxpayers they *paid for* BSD in the first place.


      Look, you keep spouting that crap.
      They paid for BSD.

      That is different than FreeBSD, OpenBSD, NetBSD, BSDOS, or any of the other things that forked off it long long ago.

    5. Re:I love OpenBSD by AHumbleOpinion · · Score: 1

      Look, you keep spouting that crap. They paid for BSD. That is different than FreeBSD, OpenBSD, NetBSD, BSDOS, or any of the other things that forked off it long long ago.

      Not really, the code Apple and others paid for is still at the core of those projects. Apologies if reality conflicts with your politics.

    6. Re:I love OpenBSD by ak3ldama · · Score: 1
      All you damn Apple freaks need to shut the hell up about saying that Apple somehow paid for BSD licensing. The BSD work was only partially paid for by taxes/government funds. Open Source developers even back then were contributing of themselves to the free Unix world we now know and love, and they didn't get paid. Apple sort of does help now by hiring various people, but that's common practice and is nothing out of the ordinary. The pure zealousness of you mac people scare me.

      And secondly we're talking about OpenBSD all of whose relevant code happened after the funds were cut off and Cal. Berkeley wiped their hands clean.

      --
      "but money is the God of Algiers & Mahomet their prophet." - Rich. O'Bryen June 8th 1786
    7. Re:I love OpenBSD by AHumbleOpinion · · Score: 1

      All you damn Apple freaks need to shut the hell up about saying that Apple somehow paid for BSD licensing.

      No, I said Apple helped pay for the original BSD development and some of that code remains at the heart of OpenBSD today.

      The pure zealousness of you mac people scare me.

      You're stupidity frightens me, although calling me a Mac zealot is personally quite amusing given the arguments I've had with real zealots. I mention Apple because they were cited as a company who leeches off of BSD. Now I do own a Mac, but I also own several PCs that boot Windows, Linux, FreeBSD, and OpenBSD. I even support OpenBSD by purchasing a set of CDs every year.

    8. Re:I love OpenBSD by dodobh · · Score: 1

      They hire quite a few open source developers. The money might not be very obviously going to the project itself, but the contributions exist.

      --
      I can throw myself at the ground, and miss.
    9. Re:I love OpenBSD by MemoryDragon · · Score: 1

      Google even has employees sitting in the Apache Board of Directors... Overall the climate in the Apache projects regarding the mixture of people contributing privately and from companies is quite good.

    10. Re:I love OpenBSD by vhogemann · · Score: 1

      While Google doesn't directly pay for Apache, it employs some developers that work on Apache code... I think that this is a valid form to support an OSS project.

      --
      ---- You know how some doctors have the Messiah complex - they need to save the world? You've got the "Rubik's" complex
    11. Re:I love OpenBSD by Anonymous Coward · · Score: 0

      Theo may be an ass, but, like RMS, he was forced by circumstances into an ideological position, and kept his postion. Because he was _RIGHT_, and he never, ever let up. I don't blame him, but ppl see you as an ass after a while.

      In Theo's case even before that, because he was _RIGHT_ (well, from perusing historical docs I get that impression anyway). He was just not very political or tacful about it.

      Personally, I welcome our new truthful, clear, adn steadfast overlords.
      Oh yeah, and I am one of those linux weenies, too, BTW. Linus is not overly tactful, policital either.

    12. Re:I love OpenBSD by Darby · · Score: 1


      Not really, the code Apple and others paid for is still at the core of those projects. Apologies if reality conflicts with your politics.


      As is the code many people contributed as is the code many corporations contributed. It is nowhere near as simplistic as you're trying to make it sound.
      What this has to do with politics exists solely in your own mind.

      If what you're saying made any sense, then anybody who ever worked on any BSD code would owe all of their work on it back to anybody who paid anything toward the development of any of it. This is complete nonsense. It is more similar to the GPL, but even that comparison isn't 100% accurate.

    13. Re:I love OpenBSD by justins · · Score: 2, Insightful
      Someone would probably give OpenBSD a grant, but Theo has already proven he doesn't know when to shut up and has problems playing with others.

      A careful reader of the interviews that come up with Theo occasionally will note that he's pretty good about endorsing the companies who actually support the project. Just in that short interview he mentioned a couple of wifi chipmakers who actually share information. The expectation is that the open-source concerned reader will support those companies in favor of the ones which are mentioned who do not share information.

      Past experience suggests that the average Linux kiddie is more likely to take the binary driver and run, particularly if there's game playing to be done. But it seems Theo's doing a reasonable job of supporting the supportive vendors.
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    14. Re:I love OpenBSD by kv9 · · Score: 1
      Someone would probably give OpenBSD a grant, but Theo has already proven he doesn't know when to shut up and has problems playing with others. Cry me a river.

      i fail to see how the head honcho's attitude is relevant here. he proved that he and his team can code a damn secure system and that's his main `mission' -- to write good secure code. he doesn't want you to be his friend, hold your hand and all that. you should respect him for what he does, not from what you expect he should do.

      maybe the OpenBSD project should hire a perky PR person to handle all these matters in a friendly and non-violent manner, so it won't scare any donations away. would that make you happy?

    15. Re:I love OpenBSD by Fweeky · · Score: 1

      "Does Yahoo pay for FreeBSD, does Apple?"

      Both have a long history of supporting FreeBSD, yes. As far back as 2002 (about as long as my commit logs go) I see Sponsored/Submitted by: Yahoo! and Apple, in addition to DARPA, Sophos/ActiveState, McAfee, LSI, Isilon, Dell, The Weather Channel, Advanis, Vernier Networks, even Google via SoC.

      It's not as if it makes bad business sense; you use something, you need something adding to it, why not pay someone to do it now and let others use, test and support it instead of the hassle of maintaining your own private branch? The costs are a drop in the bucket compared to the alternatives.

  18. As a California Corp Apple helped pay for BSD by AHumbleOpinion · · Score: 2, Interesting

    Some of the OpenSSH freeloaders, like Apple Computer and The SCO Group, are notorious for reaping financial rewards from selling open source software bundled with their proprietary products. What part of the BSD license does Theo not understand? Apple and SCO aren't "freeloaders", they are using the software under the intended license.

    No, it's far simpler than that. Apple and SCO *paid for* BSD. BSD was paid for by the taxpayers of California, including corporations like Apple and SCO. Perhaps Theo noticed a "Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved" somewhere in his review of the source code. Perhaps Apple and SCO believe they have contributed more than Theo. Besides cash Apple has also contributed formerly closed source, for example the HFS+ support in Darwin. Self serving, so what, Theo, RMS, and a host of others aren't?

    I use OpenBSD and despite Theo's nonsense I support it by buying a CD every year. If Theo want's his pet projects funded he needs to learn to stop pissing off large potential contibutors, DARPA for example.

    1. Re:As a California Corp Apple helped pay for BSD by Tweekster · · Score: 1

      Basically. are you gonna seperate your code from your politics.

      --
      The phrase "more better" is acceptable English. suck it grammar Nazis
    2. Re:As a California Corp Apple helped pay for BSD by ONOIML8 · · Score: 1
      paid for by the taxpayers of California


      But that's California. You've completely missed the point.

      It's all about Theo. It's always been about Theo. It always will be about Theo.

      When people start paying attention to Theo and start sending cash his way.....well, I'm not sure what then. But it will be a start.

      --
      . Quit playing Monopoly with Bill. Switch to one of many non-Microsoft products today.
    3. Re:As a California Corp Apple helped pay for BSD by Shanep · · Score: 1

      No, it's far simpler than that. Apple and SCO *paid for* BSD. BSD was paid for by the taxpayers of California, including corporations like Apple and SCO. Perhaps Theo noticed a "Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved" somewhere in his review of the source code. Perhaps Apple and SCO believe they have contributed more than Theo. Besides cash Apple has also contributed formerly closed source, for example the HFS+ support in Darwin. Self serving, so what, Theo, RMS, and a host of others aren't?

      This is about OpenSSH, not BSD the software. OpenSSH does however fall under BSD the licence. There's a huge distinction there. Apple did not pay for OpenSSH, which is the point of contention in that specific jab at Apple. Sun, Apple, Cisco, IBM, Redhat, etc are all happy to use the excellent OpenSSH code, but are not willing to donate a single cent to help keep it maintained and developed by the people who are most qualified to do so? The free software nature of the BSD licence is beside the point too. Sure you can technically take it and do with it what you like for no cost, but if you really actually want to use it for something important to you and your customers, it is in your best interests and that of your customers to help to support OpenSSH financially. Especially when you are charging customers for products which include OpenSSH as a key feature.

      IBM has problems with one of their implementations and refuses to fix it for their customers, citing that the responsibility falls on the OpenSSH project. They're happy to sell it, but they're not happy to support it for their customers or even support the people who are willing to maintain it for a pitance.

      --
      War crimes, torture, lies, illegal spying... Would someone give Bush a blowjob, already, so he can be impeached?
  19. Holy Crap! by iamdrscience · · Score: 1, Troll

    Some companies use open source software and they don't pay for it??!! I for one am shocked.

  20. Re:Corps take but don't give back? by nacturation · · Score: 1

    I've got three letters for you: G-P-L.

    Should have believed Stallman...


    But given that it's the money they want and not the code, GPL wouldn't help in this instance. Unless of course they dual license it, in which case they simply put a price tag on the freedom and sell out once somebody pays enough.

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  21. Sounds almost like a threat by Baki · · Score: 2, Interesting

    Especially "or maybe that has happened already". Is the great diplomat Theo de Raadt now resorting to extortion?

    1. Re:Sounds almost like a threat by Valar · · Score: 4, Insightful

      No. It would be extortion if he were threatening to put security holes in SunSSH. He's just saying that without Sun's support, he can't be expected to analyze and warn them of bugs in their product. Or are you saying I have a legal requirement to disclose every bug I notice in every piece of software I use to the developer?

    2. Re:Sounds almost like a threat by Anonymous Coward · · Score: 0

      If that was to become a legal requirement, Microsoft's bug databases would end up crying in the corner like a whipped dog...

    3. Re:Sounds almost like a threat by wild_berry · · Score: 1

      Isn't this what Open Source is about: Sun can take the code and release their own fork; it's never been OpenSSH's job to fix the problems in the code that other people package and use, unless Theo is so paternally protective of his program code that he must make sure it's perfect anywhere it's used (cue cartoon of Theo appearing from nowhere to correct someone walking down the street talking with a friend about configuring OpenSSH, saying "It's not 'ssh host port password -md5', it's 'ssh host port password --md5', you idiot!"). I'm nonplussed by Theo's words in TFA shaming IBM for asking them to fix problems for a client: isn't the standard process that IBM and Sun have to follow to write and file a patch to the project hosts?

  22. OT:Who's running OpenBSD on Dell poweredges? by Abstract · · Score: 1

    OT: Who's running OpenBSD on Dell poweredge servers?

    1. Re:OT:Who's running OpenBSD on Dell poweredges? by kosh · · Score: 0

      build a firewall out of a dell poweredge 750 here

    2. Re:OT:Who's running OpenBSD on Dell poweredges? by chrysalis · · Score: 1

      I do. On almost all models of Poweredge.

      --
      {{.sig}}
    3. Re:OT:Who's running OpenBSD on Dell poweredges? by Abstract · · Score: 1

      Do you also use SMP? How does it perform?

    4. Re:OT:Who's running OpenBSD on Dell poweredges? by Hal_Porter · · Score: 1

      Mod parent down!

      The topic is flaming Theo, not talking about the wonderful OS that is OpenBSD.

      Now can someone tell me what he did to piss off those nice guys from the military/industrial complex?

      --
      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;
  23. More importantly: by mcc · · Score: 1, Interesting

    If Apple doesn't already pay for NetBSD (which they use), then why on earth should they be expected to pay for OpenBSD (which they don't use)?

    Because if they don't, then Theo de Raadt will shoot this adorable rabbit with "OpenSSH" written on it? Meh.

    I mean, I'm sure that the loss of OpenBSD would be a sad thing for the open source community, but this entire fundraising drive just smells like the old Oral Roberts "if I don't raise 8.7 million dollars, God will call me home" thing. It seems rather unbecoming of a pillar of the open source community like OpenBSD to undermine the "the marketplace of ideas created by copylefted code means we can give our product away and still support ourselves" message of open source by floating this "WE CAN'T JUST GIVE OUR PRODUCT AWAY AND STILL SUPPORT OURSELVES!! YOU, GIVE ME MONEY!!" message on top of it.

    1. Re:More importantly: by chrysalis · · Score: 1

      > If Apple doesn't already pay for NetBSD (which they use), then why on earth should they be expected to pay for OpenBSD (which they don't use)?

      Uh-oh.

      Grep for "OpenBSD" identifiers on MacOS X. You will find more occurrences of OpenBSD than NetBSD and FreeBSD.

      Microsoft also uses the OpenBSD libc for its Services for Unix package.

      --
      {{.sig}}
    2. Re:More importantly: by mcc · · Score: 2, Informative
      That is interesting. I did not know that.

      However, I do notice that when I actually test on my Mac OS X machine here:
      $ cd /usr
      $ grep -ri "freebsd" . | wc -l
              2889
      $ grep -ri "openbsd" . | wc -l
                663
      And it seems that besides there being more of them, the freebsd matches are more "real"-- if i look at the actual matches the FreeBSD ones consist to a great extent of matches in actual basic binaries and libraries, whereas the OpenBSD matches that aren't actually matching OpenSSH binaries seem to mostly be compatibility code in crossplatform UNIX apps-- "#ifdef openbsd" blocks in X11 headers for example (right before the #ifdef amiga ones), which clearly are not an indicator of OpenBSD crosspollination in OS X.

      And then trying again, in the source for Apple's libc:
      $ cd Libc-391.2.5
      $ grep -ri "freebsd" . | wc -l
              1179
      $ grep -ri "openbsd" . | wc -l
                63
      And even here again most of the occurances of OpenBSD maybe shouldn't count to the total, since they are, well, in some big directories named "FreeBSD/". It looks like a lot of those 63 matches were patches that were ported upstream to FreeBSD, then sucked into Darwin from there.

      So these were just the first two things I thought to check, and in both cases FreeBSD strings show up more often than OpenBSD by a very significant majority. I can totally believe that Apple is making much more direct use of OpenBSD code than I was aware of, but if you do not mind me asking, exactly *where* in OS X am I supposed to be finding this effect you claim of "grep... you will find more occurrences of OpenBSD than NetBSD and FreeBSD"? Because so far I'm not seeing it at all.
    3. Re:More importantly: by justins · · Score: 1
      It seems rather unbecoming of a pillar of the open source community like OpenBSD to undermine the "the marketplace of ideas created by copylefted code means we can give our product away and still support ourselves" message of open source by floating this "WE CAN'T JUST GIVE OUR PRODUCT AWAY AND STILL SUPPORT OURSELVES!! YOU, GIVE ME MONEY!!" message on top of it.

      Then I suppose it's a good thing Theo isn't saying anything like that.
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
  24. Folks are completly missing the point... by John+Whorfin · · Score: 4, Informative

    It's not that the Foo Corp is using OpenSSH w/o paying Theo or the OpenBSD/OpenSSH crowd. No one (including Theo) has a problem with that.

    It's that some companies *cough*Sun*cough* make all kinds of noises about being "open" and "supporting open source" and market the crap out of it purely because it's the latest buzzword, when in reality they just don't give a shit.

    That's what gets to Theo... and others.

    1. Re:Folks are completly missing the point... by cant_get_a_good_nick · · Score: 2, Interesting

      I won't comment on the money issue, i think a lot of people should be contributing for OpenSSH. The problem is that the BSD license doesn't require it. You can say that it should have, but i bet OpenSSH wouldn't be as ubiquitous as it is now. We have a bunch of hardware devices that we connect to with ssh. The fact out of all those devices, Theo only got a grand really surprises me.

      But as far as buzzword jumping - Sun has given a lot of things to open source, more than IBM in fact. NFS was developed by Sun, was always free as far as i know. Bill Joy, one of the Sun founders, was heavy into adding things to BSD (the original, from UC Berkeley) which were released for free. They jsut released their entire OS. They gave away ZFS and dtrace recently. They aren't on it because it's the latest buzzword. They've been doing it for years.

  25. Anti-Theo sentiments are muddying the point here by twigles · · Score: 5, Interesting

    Theo may be a jerk, but that's not the point here. The OpenBSD team does great work that gets ported to other platforms or just flat out embedded, but no one wants to lend a hand. This interview did not strike me as whiney or greedy; Theo never came across as wanting to get rich, with his grand aspirations of paying travel expenses for poor developers.

    His request is very reasonable - everyone is benefitting, and those who are in a position to give a little back should do so. He didn't say fund the project, he said contribute a little. Jeez, anything really.

    This whole Slashdot anti-Theo movement is lame, it's like watching jocks push the nerdy quiet kid around in high school, which is a bit ironic considering that many of us *were* those nerdy quiet kids. Stop trying to be part of the "in" crowd by bashing this guy and read the article with an objective eye.

  26. ... and licenses by John+Whorfin · · Score: 4, Informative

    A while back -- pre-SCO -- OpenBSD did a "license audit". I don't have the list in front of me but a sizable number of reasonably well-known open source projects had questionable licences. Theo really did ask nicely and got most of them changed.

    TCP Wrappers IIRC was one of them, pppd another (again IIRC).

    Like Theo or hate him, he's done more for the Open Source community than just piss people off.

    1. Re:... and licenses by justins · · Score: 2, Informative
      A while back -- pre-SCO -- OpenBSD did a "license audit". I don't have the list in front of me but a sizable number of reasonably well-known open source projects had questionable licences. Theo really did ask nicely and got most of them changed.

      TCP Wrappers IIRC was one of them, pppd another (again IIRC)

      I'm pretty sure Wietse Venema saw the value in updating the licenses for TCP wrappers and (perhaps more importantly) Postfix when approached by Theo and did so without any drama whatsoever. Of course, when there's no drama it doesn't make front page geek news...
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
  27. Pony up by Graabein · · Score: 4, Insightful

    An OpenBSD CD set is $49. If you've ever used OpenSSH or x.org X11 (read the article), you've already got your money's worth. In addition, chances are that somewhere in your organization (or at your house?!?) there's an OpenBSD-based firewall happily chugging away with PF and CARP.

    So cut the anti-BSD crap and get over Theo's personality for like 10 seconds and pony up. Some day you'll be glad you did. If for no other reason, do it in your own best interest.

    --
    And remember kids: Never trust a computer you can actually lift.
    1. Re:Pony up by Architect_sasyr · · Score: 1

      I for one do something at the moment that always seems to rile my co-workers

      I actually buy FreeBSD and OpenBSD CD's from a local re-seller. Rarely use the CD's I must say, but have no problems supporting the community. Me, I use OpenSSH every day, there are alternatives, but none cut it as well. OpenSSH is derived from proprietry software you will remember, but the alternatives are just shit. I agree with parent, cut the shit and pay up. It's fucking good software, and just because your a poor technician (hell I still am) doesn't mean you can't flog $50 from your parents/spouse/neighbour [when they're not looking] and buy a CD fer fucks sake.

      ANTI FLAME DISCLAIMER: Everyone is entitled to their opinion. This is mine. Don't like it. Try this command to stop reading my posts: dd if=/dev/random of=/dev/hd0

      --
      Me failed English...
      FreeBSD over Linux. If my comments seem odd, this may explain...
    2. Re:Pony up by awing0 · · Score: 2, Interesting

      I know OpenSSH has saved me more than $49 on gas alone. Even though I don't use OpenBSD as often as Linux or FreeBSD, it's well worth it to fund such a polished software project. I'm ordering 3.9 right now.

      --
      Cthulhu Saves.
  28. It's not about code but MONEY by paugq · · Score: 5, Insightful

    What's so difficult to understand for those GPL zealots out there?

    Theo is NOT talking about code. He couldn't care less about the code!

    He's talking about MONEY. OpenBSD and OpenSSH need money to pay Theo's (and other's) income, bandwidth, servers, etc. How does the GPL help when you need money? It does NOT help!

    1. Re:It's not about code but MONEY by MichaelSmith · · Score: 1
      How does the GPL help when you need money? It does NOT help!

      Vendors who extend the code and sell it along with their products will have to either release their modifications or pay $$$ for an LGPL or BSD licensed version.

    2. Re:It's not about code but MONEY by paugq · · Score: 1

      That's in case they could get a dual-licensed version of that code. Most times there is so many people involved in a project it's impossible to get everybody to agree on another license, much less on selling that code.

      Remember when some company tried to get a one-time BSD-licensed Linux kernel? No way, and it had nothing to do with the amount of money being offered: they were plainly said 'no'.

      And what about Wine? Don't you remember about the change from X11-license to LGPL and Transgaming trying to start the Rewind project?

    3. Re:It's not about code but MONEY by MichaelSmith · · Score: 1
      That's in case they could get a dual-licensed version of that code. Most times there is so many people involved in a project it's impossible to get everybody to agree on another license, much less on selling that code.

      As far as I know you can do literally anything with BSD licensed code with the possible exception of removing copyright notices.

      It may not be the polite thing to do, but I think it is legal.

    4. Re:It's not about code but MONEY by paugq · · Score: 1

      Yes, but this does not address the problem we were talking about: the GPL gives you nothing when your problem is you need money. You are equally fucked either you are BSD or GPL.

    5. Re:It's not about code but MONEY by shish · · Score: 1
      How does the GPL help when you need money?

      It gives you the option to say "pay us for a separate licence if you want to use our code in your closed source app".

      --
      I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
    6. Re:It's not about code but MONEY by Anonymous Coward · · Score: 0

      As far as I know you can do literally anything with BSD licensed code with the possible exception of removing copyright notices.

      To clarify what the other guy said, the bit you quoted was about moving away from the GPL to another licence *not* moving away from the BSD licence to another licence.

    7. Re:It's not about code but MONEY by Anonymous Coward · · Score: 0

      In which case no company would be useing OpenSSH. There where other ssh implementations out there before OpenSSH. The only reason OpenSSH became big was the BSD license. Without that it would never have see the widespread use it has now

    8. Re:It's not about code but MONEY by orzetto · · Score: 1
      How does the GPL help when you need money?

      You can dual-licence code with GPL for open development and other agreements for people who want to develop closed source. That's what Trolltech does, and I never heard them whining for money—in fact they boast successes. If Apple had to pay up for using BSD as a basis for their Mac OS X, say one little dollar per sold copy, now that would be some cash flow.

      --
      Victims of 9/11: <3000. Traffic in the US: >30,000/y
    9. Re:It's not about code but MONEY by goofyheadedpunk · · Score: 1

      If they need money so badly why not become a not-for-profit entity? A lot of people, and companies, are uncomfortable giving money to a group if that money might not directly go to coding. At least as a not-for-profit entity the openBSD guys could point and say "Hey, look, here's where our money is going. By the way, enjoy writing that half million off as a tax donation." I understand his objections--basically it's inconvenient--but surely it's less convenient to run out of money.

      --

      What if the entire Universe were a chrooted environment with everything symlinked from the host?
    10. Re:It's not about code but MONEY by Sithgunner · · Score: 1

      Then he better come up with some better business solution than keep BSD license and keep begging money, because apparently 'asking' business model doesn't work.

      Doing a great free product doesn't make them special. He has to go the way of getting money by business just like ANYONE on earth. That's what some open source guys gets wrong. They are nothing special period. If you need money, do the required process.

  29. SunSSH by MichaelSmith · · Score: 1
    I will say it here -- if an OpenSSH hole is found that applies to SunSSH, Sun will not be informed. Or maybe that has happened already.

    If OpenBSD find a bug in OpenSSH they will surely post a notice and release a fix. I don't see how they can keep the information from sun.

    I understand that Theo is still Theo, and that they should get some help from Sun, but I don't think his approach is very realistic.

  30. Money doesn't come by itself by Sithgunner · · Score: 1

    > tension between the OpenBSD team and other businesses that some feel are taking advantage of the free software without giving anything back

    Since when are people who use OpenBSD without giving anything back has to get some tension from the developers? It sounds like now it's a payware. I'm not against a payware, just that if you have to give tension to people without giving code or money back, then really, make it payware or respect the BSD license.

    I for one thank all the great work done on OpenBSD project, but if they need money, they should establish some way of making money than just gazing at the people who use by the license and expect something in return as that's the rule.

    I mean, world isn't that easy to get money by waiting and expecting people to pay. OpenBSD is not something special. To make money, you do something about it.

  31. Re:Corps take but don't give back? by MichaelSmith · · Score: 1
    Unless of course they dual license it, in which case they simply put a price tag on the freedom and sell out once somebody pays enough.

    This approach seems to work for MySQL.

  32. BSD vs GPL is not relevant by AHumbleOpinion · · Score: 3, Informative

    I say onto Theo: Tough Cookies! You made your bed, you sleep in it!

    BSD vs GPL is not relevant. Theo's bed was made by driving away potential sources of income like DARPA.

    1. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 4, Insightful
      BSD vs GPL is not relevant. Theo's bed was made by driving away potential sources of income like DARPA.

      Yes it is, as a part of a very long list of good advice he received over the years on a lot of things, and all of which he proceeded to sneer and snicker on, as only Theo can. DARPA's help is just one item on that very, very long list.

    2. Re:BSD vs GPL is not relevant by AHumbleOpinion · · Score: 3, Informative

      "BSD vs GPL is not relevant. Theo's bed was made by driving away potential sources of income like DARPA."

      Yes it is, as a part of a very long list of good advice he received over the years on a lot of things


      No, that's a fallacy. In general under open source the money is in consulting, not in the development. A BSD based project is more likely to get inside a corporation and possibly more likely to create consulting work. Whether a project is BSD or GPL, if someone doesn't want to code themselves, they can hire others to do the work. The only difference is whether that work goes back to the community at large and for the company that needed specialized changes that is irrlevant and it may even be counterproductive to the company. The GPL is not some magic pill. We've seen numerous GPL based projects in financial trouble and begging for donations around here as well.

    3. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 3, Insightful
      No, that's a fallacy.

      Oh, really? You mean it does not depend on what the purpose of the project is?

      In general under open source the money is in consulting, not in the development.

      Oh I see, making money for Theo was the whole idea of OpenBSD? NOW you tell us!

      A BSD based project is more likely to get inside a corporation and possibly more likely to create consulting work.

      Which is a good thing if you are planning to make people appropriate, modify and sell your code while not letting you look at it ever again, in hopes that somehow your celebrity status will make some of them hire you.

      Whether a project is BSD or GPL, if someone doesn't want to code themselves, they can hire others to do the work.

      True enough, that is why BSD offers no advantage over GPL in this area.

      The only difference is whether that work goes back to the community at large and for the company that needed specialized changes that is irrlevant and it may even be counterproductive to the company.

      Which, in most cases, as Theo is finding the hard way, is the only type of return expected from commercial involvment in your project. Hoping to get hired by someone using your code is wishful thinking in vast majority of cases. GPL folks understand that, and operate accordingly.

      The GPL is not some magic pill. We've seen numerous GPL based projects in financial trouble and begging for donations around here as well.

      Of course it is not. But it was never its purpose. The purpose of GPL is to ensure that regardless of who is using or contributing to the code, and regardless of financial circumstaneces of a project, the code remains the property of the community and cannot be stolen and then sold back to us. That is all.

    4. Re:BSD vs GPL is not relevant by AHumbleOpinion · · Score: 2, Interesting

      Oh I see, making money for Theo was the whole idea of OpenBSD? NOW you tell us!

      Unless they are academics and thereby have their open source development efforts subsidized they have to generate some sort of income to keep their pet projects going and avoid having to get "real" jobs.

      "A BSD based project is more likely to get inside a corporation and possibly more likely to create consulting work."

      Which is a good thing if you are planning to make people appropriate, modify and sell your code while not letting you look at it ever again, in hopes that somehow your celebrity status will make some of them hire you.


      Not celebrity status, expertise with the code. It takes time for a 3rd party to learn and become proficient with someone else's code. The most cost effective way of getting the changes you want may easily be to hire the original author.

      Which, in most cases, as Theo is finding the hard way, is the only type of return expected from commercial involvment in your project. Hoping to get hired by someone using your code is wishful thinking in vast majority of cases. GPL folks understand that, and operate accordingly.

      In part that is another fallacy. Most work on GPL'd code is never seen by the original authors or the community. Most software is internal, it is not distributed outside the company, and the GPL does *not* require the changes to be returned to the community unless thers is public distribution. Technically you only have to share the changes with those you distribute executables to, so two companies could share work and keep the community in the dark. FWIW, the majority of software being for internal consumption is the real lock Microsoft has on the market.

    5. Re:BSD vs GPL is not relevant by Anonymous Coward · · Score: 0

      You really are retarded, you realise this correct? You cannot steal BSD licensed code, once created it is there foreever, and freely given. You GPL monkeys really aggravate me.

    6. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 2, Interesting
      Unless they are academics and thereby have their open source development efforts subsidized they have to generate some sort of income to keep their pet projects going and avoid having to get "real" jobs.

      Vast majority of FOSS projects are either after-work hobby efforts or side-effects of some other paid work. It is a testimony to Theos' ego, for him to assume that he will be funded just because his project is sooooo much more important then all the others.

      Not celebrity status, expertise with the code.

      Proficency with code can be acquired, and most of the time other factors play the primary role, such as geographical locations, existing teams, well proven employees and managers, corporate politics and what not. Again, as Theo is finding the hard way.

      It takes time for a 3rd party to learn and become proficient with someone else's code. The most cost effective way of getting the changes you want may easily be to hire the original author.

      You could hire whole armies of programmers, have them dine at 5-star restaurants, be enterntained by live performances by the most expensive actors, while on one of their 20 scheduled breaks during the day, and still not arrive anywhere near the financial and psychological cost of having Theo "work" for you. People have jumped off tall buildings to escape far less aggravating situations, such as hammer-totting mafia debt collectors.

      Seriously, you have a horrible propensity to massively oversimplify things. Vast majority of FOSS programmers never gets approached by commercial interests, even though they are using the projects extensively, as most companies would rather use an existing in-house development team or local, proven consultants. That is how businesses work.

      It case of the project contributors seeking to be hired, their options are the same as those of any other software maker: self-promotion and salesmanship. Which requires inter-personal skills. Which Theo is utterly devoid of.

      In part that is another fallacy.

      You are fond of saying "fallacy", in an effort to pre-emptively discredit your opponent, and yet lack any ability to demonstrate any such "fallacies". Not a very respectable debating tactic.

      Most work on GPL'd code is never seen by the original authors or the community. Most software is internal, it is not distributed outside the company, and the GPL does *not* require the changes to be returned to the community unless thers is public distribution.

      In which GPL is indistinguishable from all the other licenses. And which internal work is again performed by internal, pre-existing teams, with an occasional posting on a project's mailing list being the only indication of any desire for external input. None of which of course alters my points in any way, as the resulting code cannot be sold to anyone, or distributed in any way externally, without running afoul of the GPL.

      Technically you only have to share the changes with those you distribute executables to, so two companies could share work and keep the community in the dark.

      Err, no. As soon as you begin any external "distibution", any old clown who gets the whiff of this can show up and demand both binaries and source. Such is the way of the GPL.

      FWIW, the majority of software being for internal consumption is the real lock Microsoft has on the market.

      Microsofts position has a myriad of reasons, and is another, wholly off-topic, conversation.

    7. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      You cannot steal BSD licensed code, once created it is there foreever, and freely given.

      Sigh.

      Really? You mean you've got all of these companies, like Apple, to give you their modified version of the OpenBSD code, which is the very thing Theo seems to be complaining about? How about you go tell him that he must be mistaken because "the code is there forever" and one "cannot steal it". For us "the GPL monkeys" it looks very much like Apple and SCO are selling the OpenBSD code back to the OpenBSD people. We "GPL monkeys" laugh much at this. And incidentally, at you.

    8. Re:BSD vs GPL is not relevant by Sique · · Score: 1

      None of which of course alters my points in any way, as the resulting code cannot be sold to anyone, or distributed in any way externally, without running afoul of the GPL.

      This is not directly true. According to the GPL you are not allowed to sell the compiled binaries without adding the offer to provide the code under GPL for the cost of the copy of the code. So there is no one hindering you to charge someone huge amounts of money for giving out the binaries, but if you do it, the written offer to put up with the code under GPL has to be there.

      And it is still possible to create your own programs running on top of GPLed code. As long as your code doesn't reuse GPL code, and your binaries run in separate tasks from binaries compiled from GPL code, your binaries are free for you to license at wish.

      --
      .sig: Sique *sigh*
    9. Re:BSD vs GPL is not relevant by PietjeJantje · · Score: 2, Interesting

      Me, I don't see a particular difference between the two licences for programmers.
      It will be you and your buddies coding, anyway.
      If you want to earn money, buy a lottery ticket. You can earn money with open source, if you're the one in 1 million coders who's lucky.
      Me, I don't mind if EvilCorp takes my stuff and tries to sell it with their added value to monkeys on Mars, as far as I'm concerned. I don't see how this effects my life, or makes my code less free. BSD is for strong people who believe in themselves.
      What gives the MIT/X/BSD licenses the edge for me is that there are no hippies or fanatics around (see: above) telling me what to think and do or otherwise trying to sell me their truth. Really. I find it particularly disturbing that according to Stallman, if I'm a hairdresser or a butcher I can sell my services, if I'm a programmer I must be a hippie for the good of mankind and sell T-shirts. This view is outdated, and was out of this world to start with. Although I agree I can think up an argument why humanity needs a free operating system, for 99,9% of the open source projects, humanity will fair just fine without it. Besides that, try to sell this hippie story to a victim of war, poverty or aids in Africa, just to alter that perspective. Last but not least, humanity got out of the situation where they sit around fires and slept in caves, by specializing and inventing money as a means of exchange. For Stallman, programmers need to step out of that. That's fine, but the rest of the world doesn't. My hairdresser doesn't have the same attitude, he wants my money.

    10. Re:BSD vs GPL is not relevant by petard · · Score: 1

      Really? You mean you've got all of these companies, like Apple, to give you their modified version of the OpenBSD code, which is the very thing Theo seems to be complaining about? How about you go tell him that he must be mistaken because "the code is there forever" and one "cannot steal it". For us "the GPL monkeys" it looks very much like Apple and SCO are selling the OpenBSD code back to the OpenBSD people.

      RTFA. Source code is not "the very thing Theo seems to be complaining about." It's money. The project needs money and he'd like some of the vendors that profit from the project to ante up with some support. The GPL would not make any difference here. Apple uses gcc. SCO uses gcc, Linux and thousands of other GPL'd packages.

      The GPL makes no difference in Apple's behavior:
      Apple OpenSSH code
      Apple GCC code

      So how would the GPL help the project?

      --
      .sig: file not found
    11. Re:BSD vs GPL is not relevant by Antique+Geekmeister · · Score: 1

      OpenSSH seems to be the only component of OpenBSD development that most people care about. The old BSD licensing creates a legal problem to port the code over to GPL or another more common modern license. And since so much absolutely essential modern code is GPL, such as gcc and glibc and zlib and bash, and the most commonly used versions of sed and ls and mkdir and rm, there's no support for going to a BSD licensed OS.

      Linux has won this market share battle. Take the solid programmers off of OpenBSD and move over to the Linux world where their expertise can be respected and they can actually make a bit of cash doing custom deployments: I know several companies that would have been happy to dump the F-Secure versions of SSH if they could have gotten good support agreements to make customized installations and 6-hour turnaround on support calls. And the tools generated for those would have gone into the public pool of good tools. Integrating SSH properly into Perforce within a month would have been a $50,000 paycheck. An scp server that didn't require users to have valid local shells and used actual chroot cages to prevent clients from being able to probe system files would ahve been another $50,000. (I had the buy-in from management to make an offer: I couldn't get the OpenBSD developers of the time to take my calls, they weren't interested in doing Linux support.)

      Instead, they wasted their time on the "privsep" features that destabilized the product, didn't work right on many OS's, didn't fix any existing approaches. And now they're whining about how Sun turned it off in SunSSH? And because they didn't use GPL, Sun can keep their source for SunSSH closed.

      If OpenBSD is sputtering, it's time to fork OpenSSH.

    12. Re:BSD vs GPL is not relevant by ragefan · · Score: 1

      I find it particularly disturbing that according to Stallman, if I'm a hairdresser or a butcher I can sell my services, if I'm a programmer I must be a hippie for the good of mankind and sell T-shirts.


      What is disturbing is how this misconception continues. There's is nothing in the GPL that says you have to give away your services. To use your analogy, if you create a new hairstyle, the GPL says any other hairdresser can use your style but they can't stop others from copying the style from them either, even if they make a minor change to the style. So while you've let other hairdressers copy a haircut style you have come up with, you can still charge people to get that haircut.

    13. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "Err, no. As soon as you begin any external "distibution", any old clown who gets the whiff of this can show up and demand both binaries and source. Such is the way of the GPL."

      Err, no. Only those that recieve binaries from *you* can ask for the source code to *you*.

      And, of course, you can ask for your binaries any amount you deem reasonable.

    14. Re:BSD vs GPL is not relevant by turbidostato · · Score: 2, Insightful

      "according to Stallman, if I'm a hairdresser or a butcher I can sell my services, if I'm a programmer I must be a hippie for the good of mankind and sell T-shirts."

      Outstanding bullshit. It is *exactly* the opposite!!!

      According to Stallman, if I'm a hairdresser or a butcher, I can sell my services, if I'm a programmer I can sell my services too!

      The question is that since the hairdresser won't ask you for money each time somebody see your hair, or a butcher will ask you for money when you buy the meat, but he won't ask for more money if you use it to invite your friends (multiuser license), or if you resell it, the programmer should ask for money against their services (coding) but shouldn't add any kind of extortion about further usage of what you coded, just the same the hairdresser or the butcher won't ask for more than the fair value of their services (cutting hair or selling meat).

    15. Re:BSD vs GPL is not relevant by PietjeJantje · · Score: 1

      That's nice. In the real world the hairdresser earns money, the open source programmer doesn't. Perhaps that's because the hairdresser isn't occupied 99,9% of the time with inventing new styles, with the actual hairdressing part only to pay for his style creation? This is exactly the GNU out-of-touchness with reality, inflicted upon themselves to spindoctor their fanatic points, that bothers me.

    16. Re:BSD vs GPL is not relevant by Anonymous Coward · · Score: 0

      A BSD based project is more likely to get inside a corporation

      Yeah, right. That's why Linux and MySQL have less marketshare than *BSD and Postgres, right?

    17. Re:BSD vs GPL is not relevant by dadragon · · Score: 1

      FYI, zlib is not GPL.

      --
      God save our Queen, and Heaven bless The Maple Leaf Forever!
    18. Re:BSD vs GPL is not relevant by Anonymous Coward · · Score: 0

      The contract was going to expire in a few months anyways. What the hell did it matter? It's not like they were going to renew it or anything.

    19. Re:BSD vs GPL is not relevant by AHumbleOpinion · · Score: 1

      According to Stallman, if I'm a hairdresser or a butcher, I can sell my services, if I'm a programmer I can sell my services too!

      And if you are BSD or GPL you still sell your services, there is not GPL advantage here.

    20. Re:BSD vs GPL is not relevant by Anonymous Coward · · Score: 0

      so making poor ethical choices is good for business?

      sigh, with idiocy like this, it's no wonder commerce is so screwed up

    21. Re:BSD vs GPL is not relevant by Antique+Geekmeister · · Score: 1

      My goodness, you're right! I thought it was. OK, substitute "gzip" for "zlib" everywhere I wrote it.

    22. Re:BSD vs GPL is not relevant by Anonymous Coward · · Score: 0

      Sigh ...

      First off, I'd just like to say that you do seem to go on, and on with personal attacks upon Theo, which, from my perspective, only serves to deeply weaken your arguments by making them appear as if you're biased. Actually, in my experience, Theo tends to focus on the code, and yes, it may seem that he does so the expense of others concerns. However, this is exactly in keeping with the spirit of the project and with his continued and supported leadership. Indeed, many people respect his position, I among them. You said, "any old clown who gets the whiff of this" Of course, it seems as if you're ignoring the fact the closed source is "closed". As well, you're conveniently overlooking the fact that a lot of open source code is used as a framework by closed code shops, most of which never share back. Furthermore, let me guess, I'd bet you work on closed code, no? Sir, with all due respect, is there any chance you're suffering from some self justification yourself?

    23. Re:BSD vs GPL is not relevant by Anonymous Coward · · Score: 0

      Vast majority of FOSS projects are either after-work hobby efforts or side-effects of some other paid work. It is a testimony to Theos' ego, for him to assume that he will be funded just because his project is sooooo much more important then all the others.

      Well that's kind of the point. Apparently it is sufficiently (no, not "sooooo") important that some very big players adopted the code. No they don't have to give anything back. But you'd think that they would realize it's in their interest to do so. Consider it a tiny R&D investment. ($100,000/(IBM+HP+Cisco+RedHat+Novell) = $20,000 each) Maybe they'd get something else they can use too.

    24. Re:BSD vs GPL is not relevant by Anonymous Coward · · Score: 0

      You really are retarded, you realise this correct? You cannot steal BSD licensed code, once created it is there foreever, and freely given. You GPL monkeys really aggravate me.

      I hear ya man! These GPL guys don't know the meaning of free or maybe they just don't know the meaning of gift. BSD licensed code is a gift to humanity whether they are individuals or corporations. It doesn't matter, it's for all to use however they so choose to use it.

    25. Re:BSD vs GPL is not relevant by DrSkwid · · Score: 1

      > And since so much absolutely essential modern code is GPL, such as gcc and glibc and zlib and bash, and the most commonly used versions of sed and ls and mkdir and rm, there's no support for going to a BSD licensed OS.

      Don't fool yourself that these pieces of code are "essential". The GNU part of GNU/Linux is wholly replacable. The *ONLY* reason that gcc is still used in OpenBSD is that Theo (and other OpenBSD people) feel that they can't bind users to the terms of the license for the plan9 compilers.

      Does Apple use GNU ls ?

      If not then your assertion is already out of the window without even looking at the actual GNU penetration of Un*x userland.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    26. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      Source code is not "the very thing Theo seems to be complaining about." It's money.

      No, its the fact that they are using the code and not paying Theo. In case of GPL, there would be at least some return, in form of code. As I explained to someone else already, expecting a FOSS project to make money is the apex of silliness as only very few, far and between, get so lucky. But that's Theo and his ego for you.

      So how would the GPL help the project?

      See above.

    27. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      Err, no. Only those that recieve binaries from *you* can ask for the source code to *you*.

      GPL section 2.b:

      You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
      Which part of "third parties" you do not understand?
    28. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      First off, I'd just like to say that you do seem to go on, and on with personal attacks upon Theo, which, from my perspective, only serves to deeply weaken your arguments by making them appear as if you're biased.

      Guilty as charged. Theo's antics and attitudes rub me the wrong way.

      Actually, in my experience, Theo tends to focus on the code, and yes, it may seem that he does so the expense of others concerns.

      Its how he does it which is causing my "bias".

      You said, "any old clown who gets the whiff of this" Of course, it seems as if you're ignoring the fact the closed source is "closed".

      Not GPL derrived code which is being distributed. I already pointed out the relevant GPL section to someone on this thread.

      As well, you're conveniently overlooking the fact that a lot of open source code is used as a framework by closed code shops, most of which never share back.

      As long as they do not distribute it anywhere else, they are entitled to it and it is no skin of anybody's nose.

      Furthermore, let me guess, I'd bet you work on closed code, no? Sir, with all due respect, is there any chance you're suffering from some self justification yourself?

      Not at all. I am a contributor to a few GPL projects myself, but my coding days are otheriwse long over.

    29. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      Apparently it is sufficiently (no, not "sooooo") important that some very big players adopted the code.

      Many, many manufacturers of appliances use embedded Linux in their products, yet no one is moaning and bitching on lklm about them not ponying up. Its all in Theo's head.

    30. Re:BSD vs GPL is not relevant by petard · · Score: 1

      Did you see my links? Companies are returning code for both the BSD-licensed OpenSSH and the GPL-licensed gcc. Theo is not complaining about that form of return. He's complaining about not getting money. The GPL still doesn't help him there.

      --
      .sig: file not found
    31. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      Did you see my links? Companies are returning code for both the BSD-licensed OpenSSH and the GPL-licensed gcc. Theo is not complaining about that form of return. He's complaining about not getting money. The GPL still doesn't help him there.

      And as I keep explaining, Theo is in a rut of his own making, and the GPL is only one of the many things that could have assisted his project, all of which did not suit Theo's tastes. While it is true that some will contribute back even to a BSD licensed project, they are not in any way obligated to do so. Theo whining about them not doing so flies directly in the face of the very notion of the BSD license. You can't encourage people do "do what they like" with your code and then complain that they "do what they like" with it. With the GPL they would at least be forced to be contributing the code. Is it enough for Theo? Probably not. But BSD is worse, from his own perspective, as he not only gets no money, but even code is subject to someone's whim.

      Also as I explained already, many times, expecting to get money for a FOSS project, even GPLed, is just pure megalomaniac nonsense. Code contributions are the most one can expect and the GPL ensures at least that form of return. And also prevents people from just taking what you made and then selling it back to you.

      Only if you get very lucky, or if you use your head to work the periphery of the project as a consultant or what not, you will get some financial return.

    32. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "Which part of "third parties" you do not understand?"

      Which part of "licensed at no charge" do you translate as "you have to provide me with some tangible element, be it source or binary"?

      Well, if you think "licensing" and "giving it" is the same thing, maybe you can ask the State for a new car, since they got you a driving license.

      The meaning of that paragraph is crystal clear: if you get the code under the GPL to somebody you thereby are licensing that code under the GPL to anyone else that gets legal access to such code (but this doesn't mean that *you* will be the one that will get access to the code). This avoid the situation where you license the code to somebody under the GPL but somehow you try lo limit his ability to further distribute it under the GPL (or, conversely, for him to gain any kind of right of exclusivity so you can't distribute it under the GPL to anyone else).

    33. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "And if you are BSD or GPL you still sell your services, there is not GPL advantage here."

      Who said there were differences in this regard? Not me, so your point was?

    34. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      Which part of "licensed at no charge" do you translate as "you have to provide me with some tangible element, be it source or binary"?

      Right, so I am a (no fee) licensee of source code to which I have no access? Your logic is mind boggling.

      Well, if you think "licensing" and "giving it" is the same thing, maybe you can ask the State for a new car, since they got you a driving license.

      Right, you see many people not entitled to driving with driving licenses? Nice mis-direction there bud, but the license in question is to drive a class of vehicles, which is different from owning one, whereas a license discussed in that provision of GPL is to use the specific source code in question, which is synonymous with having access to a copy. Code and cars do not exist in the same domains and do not behave in comparable ways.

      thereby are licensing that code under the GPL to anyone else that gets legal access to such code (but this doesn't mean that *you* will be the one that will get access to the code)

      Yes it does. GPL clearly states so. You can mis-read it in as many ways as you want, but it will change little. Otherwise a trick proposed upthread would be possible: a large network of corporations distributing code to each other and excluding everyone else, including the original developers of the code from the process. That is precisely why this clause exists in the GPL, to prevent greedy tricksters from coming up with the very scheme you are desperately attempting to come up with.

    35. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      " the license in question is to drive a class of vehicles, which is different from owning one"

      And as such, I give you license to *use* my source code if/when ever you put your hands on it, which is different from me *owning* a given copy of it, much less me having to pass you one. If and only if you got binaries from me, you may ask me for the correspondant source code (which, on the other hand, is nothing but logical: since *I* never met in bussiness to you, how is it logical you coming to me asking for something?)

      Now: I grant you a license to use whatever money you find in my pocket.
      Does this mean I'll send to you my pocket's content? alas no. But if *you* manage to legally get access to my pocket, hereby I grant you a license to use what you find in it at your convinience.

      "Yes it does. GPL clearly states so"

      Where? Me letting you use my code *if* you get legal access to it is nothing more than the State letting you drive a car *if* you legally get such a car. I am in no more obligation to pass you the binaries than the State about providing you with a car, just because it allowed you to drive.

      "Otherwise a trick proposed upthread would be possible: a large network of corporations distributing code to each other and excluding everyone else, including the original developers of the code from the process"

      That's not a trick. That's simply legally possible, and it is happening *now*. There are voices asking for this to be changed on the future; there are licenses that ask for any change published or not to be sent to the original author, but that's simply not the case for the GPLv2.

    36. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      And as such, I give you license to *use* my source code if/when ever you put your hands on it, which is different from me *owning* a given copy of it, much less me having to pass you one.

      That would make your "license" markedly different from the GPL, or as a matter of fact, any other software license in existence. You would be specifically going into contortions to purposefully dis-associate the licence to use that software from the software itself. And I am not sure if that sort of contortion would stand up in court, even if explicitely made, as no other case exists in which software was licensed that way.

      If and only if you got binaries from me, you may ask me for the correspondant source code (which, on the other hand, is nothing but logical: since *I* never met in bussiness to you, how is it logical you coming to me asking for something?)

      GPL is different because it specifically mentions "third parties", in an effort to avoid a formation of essentially a conspiracy between companies to distribute GPL-ed code between themselves, while denying anyone else access. If you do not like that provision, you are welcome not to modify GPL-ed code or not to distribute it after you modified it and thus avoid such problems. You can still use unmodified code and by doing only so, you will never run afoul these provisions.

      Now: I grant you a license to use whatever money you find in my pocket.

      As I already mentioned, software and physical objects do not obey the same rules. Software licenses are used exclusively to control what people can do with copies of software they already have access to.

      I am in no more obligation to pass you the binaries than the State about providing you with a car, just because it allowed you to drive.

      Again, quit harping on cars, as they have nothing to do with software, and their licensing to drive is in no way related to a wholly different concept of licensing software. To be specific, you are obligated, under the GPL, to pass the source code to any "third party" that requests so, providing that you were modifying and distributing GPLed code in any way. You can even ask for a reasonable fee to cover the expense of the data medium. But you are obligated to provide it.

      That's not a trick.

      It goes against the whole spirit and the purpose of the GPL, ergo: a slimy attempt to bypass its provisions. A con-man's trick.

      That's simply legally possible, and it is happening *now*.

      If you could kindly give us examples so that we could go after these people, I would very much appreciate it.

      There are voices asking for this to be changed on the future; there are licenses that ask for any change published or not to be sent to the original author, but that's simply not the case for the GPLv2.

      Again, "sending any change to the original author" is wholly impractical (as there could be thousands of co-authors of any piece of code) and I am not aware of any license that states so. GPL accomplishes this effect much more efficiently: any third party (including the original author or any of the subsequent contributors) can demand the source code from a distributor of modified GPL code.

    37. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      As an addendum.

      Your confusion about driver's licenses and software licenses can be summarized thusly:

      A license to drive a vehicle, or even your hypothetical license to the "money in your pocket" are different from software licenses because they are not specific enough. Software licenses have one-to-one relationships with a unique piece of code. The licenses you mentioned do not, they cover a whole class of things: passenger cars, an unspecified amount of coins, etc. To cast a software license in the terms of cars or money, you would have to rephrase a driver's license to say "a license to drive a Ford 150, VIN:126178631783 and no other vehicle" or "a license to use a $100 bill serial number 123214124 minted in 1992" or some such similar thing. In these cases, those licenses would be then associated with a specific, unique object, just as a particular version of source code is. And in such case, adding "if you can get your hands on one" makes absolutely no practical sense and is an dishonest, empty, rhetorical device.

      But even these contrived examples still do not fully match the nature of software licenses, because, again, they have no exact equivalent in licensing of physical objects.

    38. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "And I am not sure if that sort of contortion would stand up in court, even if explicitely made, as no other case exists in which software was licensed that way."

      What!? *ALL* licenses are granted that way. Just try to buy a NFM license (non physical media) from, say, Microsoft (or Red Hat, or whoever) and then ask for such media. *ANY* software license, in fact, *ANY* intellectual property-related contract or license is implicitly and explicitly disengaged from any physical meaning, and that's their only base of existance. The moment you start thinking an intelectual property right management is somehow engaged with any kind of "physical" object (like a CD, or a given copy of a software program) is the moment you *really* go into very deep problems (then, am I the owner of any given "object", or am I the owner of some non-exclusive rights to do this and that?). Again: the right to *use* the thing and the right to gain access to the thing are very, very different things, no matter if "the thing" is a physical object or a given collection of ones and zeroes.

      Even more, the proper "when and why" you can gain access to the thing because you have rights over the thing, is by itself a whole subject on law studies.

      "GPL is different because it specifically mentions "third parties", in an effort to avoid a formation of essentially a conspiracy between companies to distribute GPL-ed code between themselves"

      And now you, please, summum just a single reputed opinion (say, Stallman) backing your assertion.

      "you are obligated, under the GPL, to pass the source code to any "third party" that requests so"

      And you please, can literally produce such a point in the license. The more I look at it the more I see that, by the GPL, I have to GRANT RIGHTS, but nothing is said about PASSING THE SOURCE.

      There:

      b) You must cause any work that you distribute or publish, that in
      whole or in part contains or is derived from the Program or any
      part thereof, to be licensed as a whole at no charge to all third
      parties under the terms of this License.

      You see? TO BE LICENSED. Were the clever lawyers at the FSF meaning that you should pass a COPY OF THE CODE to any asking so, don't you thing they WOULD SAY SO? Remember this is not the typical EULA where can be argued that the licenser has a contorted aim at seeming to say A when saying B, but just the opposite: they want to be as mean and lean and possible and, heck, they got it.

      "You can even ask for a reasonable fee to cover the expense of the data medium. But you are obligated to provide it."

      Yes. But only if I previously passed to *YOU* explictly a copy of the binaries. Just grep for "copy" and you will EXACTLY see what and when copies of what must be passed along. You see, the FSF lawyers say copy when they mean COPY and say license when they mean LICENSE:

      * On each COPY you must include (as per point 1):
      1/ an appropriate copyright notice
      2/ a disclaimer of warranty
      3/ intact instances of all the notices that refer to this License and to the absence of any warranty
      4/ a copy of this License along with the Program.

      * You may copy and distribute modified versions of the executable program provided that:
      a/ Accompany it with the complete corresponding machine-readable source code
      b/ OR Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code
      c/ OR Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

      You see? There is EXPLICIT coverage for the case you were tr

    39. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "A license to drive a vehicle, or even your hypothetical license to the "money in your pocket" are different from software licenses because they are not specific enough"

      Yeah, well, and looking at your name you surely will be able to produce the old Roman iure basis that states when a license is "specific enough" and when it isn't.

      "But even these contrived examples still do not fully match the nature of software licenses, because, again, they have no exact equivalent in licensing of physical objects."

      While it is a recurring meme talking about how PROPERTY with regard of physical objects can't and shouldn't be compared to PROPERTY on the intellectual realm, you are really misleaded here: we are not talking here about physical or intellectual PROPERTIES; we are talking here about licensed RIGHTS, and sorry yes, are RIGHTS with quite essentially independent about the nature of what are they applied to.

      I can give you license to drive, in which case I have no obligation to produce a car.
      I can give you license to drive *my* car on monday to friday, and then I'll probably will be implictly bound to produce the reasonable means within context for you to gain access to my car those days.
      But I can give you license to drive my car whenever you come to my country; obviously that doesn't mean I'll have to pay for your plane tickets. And if it happens that you never come to my country, thus never exploding your right to drive my car, the license I gave to you is no less "licensing" than if it happens that you come here monthly.

      But then, you probably will say again that cars are objects while software is software. OK; I hereby license you to use my very specific copy of Konqueror any time you visit me. Have I to pay your trip? Or maybe I am somehow under obligation to send you a tarball with the program or what? Well, I didn't develop Konqueror, maybe this makes a difference. There: this morning I hacked a short script (nothing fancy, almost a "Hello World", still my own code). I hereby grant you universal rights for usage, modification, redistribution, whatever, from the moment you gain legal access to it onwards, and grant exactly the same rights to whatever third party you distribute the script be it the original, a copy, or a modification. What do you say? Am I under obligation to send the script to you? Even more: Am I under obligation to send the script to anyone else *even* if you manage to legally gain access to it and redistribute? I bet not.

    40. Re:BSD vs GPL is not relevant by tricorn · · Score: 1
      a written offer, valid for at least three years, to give any third party

      There has been some disagreement about what exactly that phrase means. It could mean that if you are aware that such an offer exists, you can ask the original distributor for a copy of the source, code, or it could mean that you can get a copy of the source code only if you have such a written offer, or a copy of said written offer in the case of a non-commercial distribution as per subsection c:

      the information you received as to the offer to distribute corresponding source code
      Clearly the intent is that if someone gets a copy of the binary with a written offer, they are allowed to redistribute it non-commercially, along with "the information", and clearly that information must be something that can be acted upon by the third-party recipient in order to get a copy of the source from the original distributor. What isn't clear is if the original recipient of the binary/offer DOESN'T pass it along, is anyone else entitled to get a copy of the source code from the original distributor simply by knowing that it exists and was distributed as a binary-only w/offer. Some people have tried to interpret it as meaning the only obligation the original distributor has is to those that directly received a binary-only distribution from them, but I think that is a flawed understanding.

      IIRC, Stallman/FSF sided with a distributor who was making "private" pre-releases, under a restrictive license that said they'd cut you off if you re-distributed it, in other words you had the right to re-distribute, but if you did they'd terminate your paid-for access to such releases in the future. I think this was an ADA compiler? I don't recall the details; there was something similar with a company modifying firmware for a Linksys router.

      The easiest way out of all this is to always distribute the source along with the binary; at that point you have no further obligation to anyone. Even easier is to not even distribute the binary, just the source! Pretty difficult to run afoul of the GPL if all you ever distribute is source code.

    41. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "a written offer, valid for at least three years, to give any third party
      There has been some disagreement about what exactly that phrase means"

      Yes, I know. I didn't go that path because it was irrelevant to the thread. For me, I think it's clear, but not obvious.

      "What isn't clear is if the original recipient of the binary/offer DOESN'T pass it along, is anyone else entitled to get a copy of the source code from the original distributor simply by knowing that it exists and was distributed as a binary-only w/offer"

      Yes, that's the problem. The point here is the cabal definition about what exactly a "third party" is.

      I am the first party; you are the second party; anyone reading this thread is a third party. But my mother, who don't even know Slashdot exists is not a third party regarding this thread's matters; she is no party at all.

      I see clear that "any third party" in regards of distribution of source code is anyone that manages to legally reach the binaries not being you and me (or the source by that matter, but that's not what we're talking now); people without neither the binaries nor the source is not a party in this bussiness, so they cannot ask "the sourcerer" for the code if they cannot produce a binary under their control.

      Let's dramatize it:

      The Asker: Hey, Mr programmer, I learnt that you developped some program and distributed only the binaries as per GPL 2b option.
      The Programmer: So what?
      A: Well, I want the source code; it's GPL, you know...
      P: Sure, of course I'll give'm to you! ...as soon as you show me the written offer to do so, of course. You know... my memory has become a bit fuzzy lately and I don't remember to have made such an offer.

      A1: You know... I, I think I lost the written offer
      P1: Then, you don't have any document that demonstrates that I'm legally bound to give you the code, do you? You know how judges tend to be... No contract, no bounds.

      A2: Sure I have it! there
      P2: Now I remember... I wrote TWO programs that I distributed under GPL 2b. After all, this is wet paper unless is bound to the code it fits. Do you have the binaries, so I can know what sources I am bound to give you?

      A3: Errr... nope.
      P3: Sorry, man; since we can't know for sure what that offer fits with, I can't give you anything.

      A4: Yes, of course, here they are.
      P4: Everything is OK; here come the sources.

      Of course this is an oversimplyfication, specially P2; but just think about it: unless the license (the GPL) is bound to a given binary which it innequivocally referes to, it means nothing:

      (from the paragraph 0 of the GPLv2):
      "0. This License applies to any program or other work which contains
      a notice placed by the copyright holder saying it may be distributed
      under the terms of this General Public License."

      The key is *THIS* License (...) *THIS* program. While we tend to think (and rightly so) that licenses like the GPL are abstractions (they are: that's why you can talk about "The GPL", "The BSD", "The Microsoft EULA"...), its legal effectiveness comes from the very piece of paper (or legally equivalent device) it comes written down and applies no less no more than to the object originally bound with.

      So, when you ask the developer for the sources alleging you have some rights over them, the developer will rightly ask where those rights of you come from; the only "object" that can grant you those rights is the very "...program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License".

      Unless you can show him (or to the judge, in last instance) that program, you haven't gained any rigths, since "nobody" (no-thing, since the offering "body" here is the binary program) has passed them to you.

    42. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "IIRC, Stallman/FSF sided with a distributor who was making "private" pre-releases, under a restrictive license that said they'd cut you off if you re-distributed it, in other words you had the right to re-distribute, but if you did they'd terminate your paid-for access to such releases in the future"

      I think that this, while quite a bit "dirty" is perfectly legal (but quite stupid too, as we'll se later): the license is offered regarding the binaries its bound to, neither the previous nor the ulterior versions, I think that's obvious.

      Telling that you will loose access to *future releases* of such code line is not properly a condition of the license, but an advise regarding how the license will be for *other* programs (it really doesn't matter if such "other" programs come from the same code baseline or other).

      Remember I am not bound to give you the source *unless* I gave you the binaries (with the 2b exception). Since I gave you the binaries for version 1.0 I'm under obligation of giving you the sources, and maybe, to any other that has a copy of the 1.0 program if I distributed under 2.b provision.

      But then, if you (as I promised I'd do) didn't get from me my flashing 2.0 version, I'm under no obligation to give you the sources.

      Of course, you can "overule" this limitation very easily: you can get 2.0 from anyone else and, provided I distributed under 2.b provision I am obligated to give you the sources, disregarding what I previously said, because the version 2.0 is GPL too (well, we suppouse the case where version 2.0 was released under the GPL, of course), which explictly states that "4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void"

      So, I can forbid you to gain access to the binaries v2 FROM ME if you do this or that with v1, but I can't negate you the sources provided that you legally got the v2 binaries anywhere else, and I can't legally force anyone recieving v2 binaries from me to not redistribute them, even to you, since the proper license I chose to distribute my binaries clearly states that he can and I can't do nothing to avoid it.

    43. Re:BSD vs GPL is not relevant by Bing+Tsher+E · · Score: 1

      ....the property of the community and cannot be stolen and then sold back to us. That is all.

      Good. Now stop preaching to everybody about it, then.

    44. Re:BSD vs GPL is not relevant by tricorn · · Score: 1

      The ambiguity here is whether a negative consequence for exercising a right that you have under the GPL constitutes an "additional restriction" - if it is, a contract that terminates access to future releases if you do exercise your rights under the GPL would be incompatible with the GPL itself. Myself, I can't see how a negative consequence could be considered anything but a restriction, but I can see how it could be interpreted the other way. It sure seems to violate the spirit of the license, though.

    45. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      What!? *ALL* licenses are granted that way.

      Very well, show me an example of a Microsoft license granted on any Microsoft software to an individual to which code that indivudual is subsequently never granted access.

      And now you, please, summum just a single reputed opinion (say, Stallman) backing your assertion.

      I already quoted you the relevant section, where "third parties" are mentioned explicitely.

      And you please, can literally produce such a point in the license. The more I look at it the more I see that, by the GPL, I have to GRANT RIGHTS, but nothing is said about PASSING THE SOURCE.

      One is equivalent to the other, as you keep refusing to understand. You may charge a fee for the media on which the source code resides, but that's about it.

      Were the clever lawyers at the FSF meaning that you should pass a COPY OF THE CODE to any asking so, don't you thing they WOULD SAY SO?

      They apparently failed to foresee the lengths to which someone as you would go in order to deny the obvious. I am sure they will work on more explicit spelling IN BIG LETTERS, in the next revision.

      You see, the FSF lawyers say copy when they mean COPY and say license when they mean LICENSE:

      Sigh, someone obtaining the copy is the direct outcome of granting the licencse. The requirements then stipulate what should happen with that copy. You are really grasping here.

      What the heck would mean this point if you *always* were under obligation of giving a copy of the source to anyone that would ask for it???

      As per your quoted text, if you distribute the code commercially you are obligated to offer the source as well, unless you are a non-commercial distributor who can mooch of an upstream source archive. I am not sure what your point is. In the case of corporations distributing source to each other, they clearly fall into the category "b" in your quote. The time limitation is intended to limit the burden on distributors of obsolete code which is no longer distributed.

      Obviously, point 3 covers the case of the recieving end of point two: you DON'T HAVE TO PRODUCE THE SOURCE AT ALL, if all you recieved was the binaries, which is an acceptable practice, but only in the case of non-commercial redistribution.

      That is intended for a case where you do not modify the code and are merely distributing it, and in a case of non-commercial situation, you are then allowed to pass the buck upstream to the original location from which you got that unmodified code so that you can avoid setting up your own repository. This desperate "reasoning" of yours is getting pathetic.

      No, it doesn't. Even Stallman was for a while *selling* copies of Emacs.

      I am beginning to wonder if there is something wrong with your mental faculties. Yes, one can sell Emacs but once the recipient receives it, he too can sell it to further recipients and so on, under the terms of GPL. None of which releases him from the requirement to provide source code on demand. Stallman's "selling" idea was intended as a means of funding open source projects. That is precisely what RedHat does. Yet you can still obtain all RedHat's GPL-ed code, for free, from their Fedora Core distribution, as the GPL obligates them to. Even though they keep on selling the same code as part of their RedHat Enterprise edition.

      It is about giving the four liberties to the USERS of the program. If you are not a USER (like in the case you talk about regarding a network of companies sharing modifications not shared with you), then we are not talking about YOU. But if you are a USER, you already have ALL the means to reach to the source code FROM THE ONE THAT PASSED THE BINARIES TO YOU (with the already mentioned exception 2b).

      No, it is about both the users and the authors/contributors i.e. the general community of users of software. That is why "third parties" are specifically mentioned. To wit, GPLv3 expands

    46. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      But I can give you license to drive my car whenever you come to my country; obviously that doesn't mean I'll have to pay for your plane tickets. And if it happens that you never come to my country, thus never exploding your right to drive my car, the license I gave to you is no less "licensing" than if it happens that you come here monthly.

      Yet that decision, to fulfill such license, is then completely up to me. I can decide not to come to the country, or not. In effect, it is no different to granting me control of the vehicle, as it is me, exclusively, not you, who decides when such license is fulfilled. That is the crucial distinction which you keep on missing. Same occurs with the GPL, which grants the third parties just such an ability.

      But I can give you license to drive my car whenever you come to my country; obviously that doesn't mean I'll have to pay for your plane tickets.

      No you dont, similarly the GPL provides for the cost of the medium on which you are obliged to deliver the source, to be paid for by me.

      And if it happens that you never come to my country, thus never exploding your right to drive my car, the license I gave to you is no less "licensing" than if it happens that you come here monthly.

      Again, such license grants me the discretion when to arrive, and thus the control, of the vehicle. Which was my point all along.

      I hereby license you to use my very specific copy of Konqueror any time you visit me. Have I to pay your trip?

      See above (bypassing the fact that you have no right to be granting any licenses to an already GPL-licensed code). Should I show up over there (which is now at my discretion exclusively) you better be home and have that Konqueror ready.

      There: this morning I hacked a short script (nothing fancy, almost a "Hello World", still my own code). I hereby grant you universal rights for usage, modification, redistribution, whatever, from the moment you gain legal access to it onwards, and grant exactly the same rights to whatever third party you distribute the script be it the original, a copy, or a modification.

      Again, you have put in an additional clause, not existant in the GPL, indicating "from the moment you gain legal access to". Which makes your license specifically designed to dis-associate the code from it. And which a scenario would have to be tested in court as I would argue your definition of "gaining legal access" to be synonymous with "granting a license" and thus putting yourself in a position of being obligated to delvier the code.

      Am I under obligation to send the script to you?

      Yes.

      Even more: Am I under obligation to send the script to anyone else *even* if you manage to legally gain access to it and redistribute?

      Your license does not formulate that you yourself have to grant access to third parties, only me. You are thus excluded from that obligation. However anyone else would be entitled to obtain it from me, once I had the code (again, unlike the GPL, you make no provisions to distinguish mere possession from distribution).

    47. Re:BSD vs GPL is not relevant by Anonymous Coward · · Score: 0

      Not only you reply with arguments that have been taking care of *days* before your reply in other parts of the thread, but you try to introduce uncertainty and false claims, in an intent to distort the reality.

      I'll just point out the obvious facts:

      1/ "I already quoted you the relevant section, where "third parties" are mentioned explicitely."

      I ask you for opinions sustaining your interpretation for some lines in a license, and you answer that you already quoted the lines of the license I meant to. Great.

      2/ I tell you that currently you won't gain access to Trustix source code from Trustix (operated by Comodo IP Limited), unless you become a Trustix client and you point me to a sources repository operated by DFK Systems Limited, a different company, and your point is? At least you could hide your intent a little bit more by pointing to the community effort (www.trustix.org) instead!

      2/ I tell you that you won't gain access to the sources for the boxed Zimbra product (which is most of it, if not all, GPL-based) while you can get the Community version, and you have the guts to point to... the community version itself! as a prove... of nothing.

      3/ "Very well, show me an example of a Microsoft license granted on any Microsoft software to an individual to which code that indivudual is subsequently never granted access."

      Ask Microsoft for a Windows 95 copy. To the best of my knowledge you won't be able to get it from them. Ask Microsoft for a legal license to use Windows 95: you can get it (while at current XP prices), at least if you are a big account.

      4/ "They avoid exposure based on their obscurity alone. As soon as any of them becomes prominent, such demand [people without the binaries asking for the sources] arrives and is fullfilled like clockwork."

      Of course you can provide any example, can't you? Or better yet, you surely can point out a case where the FSF asked for the sources for software they didn't access to the binaries, don't you?

    48. Re:BSD vs GPL is not relevant by Anonymous Coward · · Score: 0

      "Sigh, someone obtaining the copy is the direct outcome of granting the licencse."

      How can I pass over this first time I read the post?

      Again, it is exactly the opposite: in the case of the GPL it is not that you are granted a license, then you got some code, but you get the binaries, *then* you are granted a license over the sources *because* you got the binaries and the license that accompanied them, and *finally* you get the sources. No binaries, no granting license. No granting license, no source (of course, that's because we are talking about the case where somebody is not giving the sources upfront; you can gain direct access if the one holding them so likes, but that's quite different of he *having* to get you the sources, even if you didn't get the binaries *first*).

    49. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      Not only you reply with arguments that have been taking care of *days* before your reply in other parts of the thread,

      Oh, I am sooo terribly sorry for not reading the whole damn thread with its hundreds of posts in a timely manner, to your satisfaction, every time some anonymous goofball replies to one of my posts. It might come as a great shock to you, but for me, unlike for some here, Slashdot is an amusing past-time, to be enjoyed whenever I have time and driven mainly by automated email notifications of replies to me. If this does not suit you, Mr. Coward, Anonymous, you can kiss my hairy ass, and then get lost along with the presumptuous attitude your rode on in.

      I ask you for opinions sustaining your interpretation

      Oh, wait, is this "turbidostato"? I see that ever increasing confidence in your arguments led you finally to the bold move of posting as an AC. In keeping with this progression of assuredness, threats if violence can't be far behind now.

      for some lines in a license, and you answer that you already quoted the lines of the license I meant to. Great.

      Err, "interpretation"? What is there to "interpret" about the term "third parties"? That they are "third"? As in not the distributor nor the recipient? Is there any other way to look at it? Or "parties"? Are you implying that this term needs interpretation? To, say, avoid confusion with a birthday gathering?

      I tell you that currently you won't gain access to Trustix source code from Trustix (operated by Comodo IP Limited), unless you become a Trustix client and you point me to a sources repository operated by DFK Systems Limited, a different company, and your point is? At least you could hide your intent a little bit more by pointing to the community effort (www.trustix.org) instead!

      I hope this will not cause you some unhealthy mental fireworks, but the repository I pointed to is what Trustix.com download section links to. There are many mirrors which store the code of the "official" Trustix archives. Although I am sure I am going to hear now endless hair-splitting moaning as to how "mirrors" do not truly qualify, even though their official status and direct feed by Trustix directly contradicts your claims.

      I tell you that you won't gain access to the sources for the boxed Zimbra product (which is most of it, if not all, GPL-based) while you can get the Community version, and you have the guts to point to... the community version itself! as a prove... of nothing.

      You could be somewhat more sneakily disingenuous, your maneuvering as it stands is too obvious. There is no other way for Zimbra to provide access to sources, otherwise the closed source portions would have to be also included. Zimbra's staff operates the so-called "community" sourceforge site (just click on sourceforge project "home" page). Again you demand that Zimbra store the files on their servers, and provide the source code in a way that you approve of. No such clause exists in the GPL. GPL does not even mention you once, no doubt to your great annoyance.

      Ask Microsoft for a Windows 95 copy. To the best of my knowledge you won't be able to get it from them. Ask Microsoft for a legal license to use Windows 95: you can get it (while at current XP prices), at least if you are a big account.

      In which case you can also get the product. Microsoft sells "media packs" for Open License customers (I assume this is what you are referring to). You can obtain media packs for any of the products you have a valid license for (some licenses expire). The cost of the pack is the media+shipping. For example Enterprise Sever 2003 Media Pack was around $25 last I looked.

      Of course you can provide any example, can't you? Or better yet, you surely can point out a case where the FSF asked for the sources for software they didn't access to the binaries, don't you?

      A random case. One of many. In most cases on gpl-violations.org, FSF did not have access to binaries as they were not the customers of these products.

    50. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      Again, it is exactly the opposite: in the case of the GPL it is not that you are granted a license, then you got some code, but you get the binaries, *then* you are granted a license over the sources *because* you got the binaries and the license that accompanied them, and *finally* you get the sources.

      This is getting bothersome, I already quoted you the exact GPL passage witch makes an explicit exception to this chain of events, granting licenses before the delivery of the code implied by such a grant.

    51. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "This is getting bothersome"

      Yes, that's getting boresome.

      So why don't we ask to the very sources ( http://www.gnu.org/licenses/gpl-faq.html#TheGPLSay sModifiedVersions )?

      "The GPL says that modified versions, if released, must be "licensed ... to all third parties." Who are these third parties?

      Section 2 says that modified versions you distribute must be licensed to all third parties under the GPL. "All third parties" means absolutely everyone--but this does not require you to *do* anything physically for them. It only means they have a license from you, under the GPL, for your version."

      Now, I'll ask you again: Can you bring some authority to your interpretation about what "must be licensed to all third parties" means? I bring to you the interpretation from the FSF (which backs up the GNU Project). After all, maybe even you will accept this phrase is open to interpretation, since you and the GNU Project seem to have a different one. I am not a judge so I don't know what the outcome of a sue about this very point would be, but I can tell that neither the GNU Project (the author of that very paragraph) nor me (which is much less important, of course, but I wanted to point it out: I'm not echoing the GNU interpretation; I only looked for theirs after the fact you adopted a different one, or else I'd mentioned it much sooner), nor anyone else I had the chance to talk about this topics.

      I think that although quite childish you diserve a "take that" now.

    52. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      Section 2 says that modified versions you distribute must be licensed to all third parties under the GPL. "All third parties" means absolutely everyone--but this does not require you to *do* anything physically for them. It only means they have a license from you, under the GPL, for your version."

      Indeed, you don't have to do anything at all until someone shows up and asks for the source. In order to avoid the hassle however, most companies and individuals simply post the source somewhere public, like Sourceforge, and thus avoid even the need to pay the cost of hosting. This action alone fulfills all of the requirements of the GPL. Its easy, painless, and precisely what the companies in your own examples did.

      Some, whose whole business depends on good relations with FOSS commmunity, like RedHat, go much further and host the files themselves.

      The truly lazy ones, on the other hand, don't even post the whole source code, just the patches, as in the output from "diff". And that is good enough too, providing that the original source is available somewhwere else.

      Now, I'll ask you again: Can you bring some authority to your interpretation about what "must be licensed to all third parties" means?

      Obviously, I am not a lawyer or a judge, so my interpretation does not have any legal force. This clause in fact will have no established legal interpretation in force until someone makes a challenge in court. However I base my interpretation on both the "spirit" of the GPL, as elaborated on multiple occasions by RMS, and the very activities of FSF, which is, and which I gave you an example of, demanding that source code be made available for many commercial pieces of GPL-ed code embedded in various devices, even though it is very unlikely that the FSF itself is a "customer" for any of those devices, thus making the FSF a "third party" in those cases.

    53. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "Indeed, you don't have to do anything at all until someone..."

      Ha, ha, ha!!! You are great, man, you are great!

      I bet that even if Stallman and Moglen went personally to your home to explain what their intent was, and what the FSF lawyers think the legal value of that clause is, you still would go telling "yes, but the *real* meaning is...".

      "...the very activities of FSF, which is, and which I gave you an example of, demanding that source code be made available for many commercial pieces of GPL-ed code embedded in various devices, even though it is very unlikely that the FSF itself is a "customer" for any of those devices"

      That's because it is just not the case: when the FSF go after that companies to ask for explanations, they don't go as users of the binaries asking for the sources, but as copyright holders of the embedded code asking them to comply with the license they gave to such code (they don't go as users; they go as authors).

      Listen: you are just negating reality. It is not only the case that what I told you is the obvious meaning of that clause, but even the GNU people went far enough to re-explain it without legaleese, just por people like you to understand. They even highlighted the "this does not require you to *do* anything physically for them" part, still *do nothing* (highligthing in the original) means "do something" for you...

      OK; I won't follow that path: you are either stupidly stubborn or a troll; both ways I don't think there's any value on this thread anymore.

    54. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      That's because it is just not the case: when the FSF go after that companies to ask for explanations, they don't go as users of the binaries asking for the sources, but as copyright holders of the embedded code asking them to comply with the license they gave to such code (they don't go as users; they go as authors).

      OK, let's pretend that this is indeed so, for the sake of amusement. That would mean that any contributor, to any GPL code is entitled to go after any corporation which somehow internally distributes some GPL code, or at least is suspected of doing so, on the very principle you just outlined, as it is unknown what GPL code is being used, until fully disclosed (read: source posted somewhere). Which essentially, on its own (forgetting about the "interpetations" of "third parties" and "doing something" based on that clause I quoted), is preventing the very scenario of "closed" method to distribute GPL between some companies, to exclusion of all others. Here I am giving you another, for all intents and purposes a stronger reason, which prevents such secret distribution, a reason fully compatible with the "third parties" clause, as "third parties" is a super-set of an already gigiantic set of "copyright holders" of any GPL code which somehow might, be involved in the distribution, a fact which will not be known until the source of the product in question is examined. So on one hand you have a full avoidance of any such assaults by simple posting of the source on Sourceforge, and on the other you have both the "third parties" clause (with whatever interpetations and mind-bendig word parsing you come up with) and also any of the vast hordes of any GPL code contributors, be it a 3-liner change in the README file, coming after you, along with the FSF, which has no choice but to assist, based on the copyright aspect alone.

      OK; I won't follow that path: you are either stupidly stubborn or a troll; both ways I don't think there's any value on this thread anymore.

      Indeed, as you stubbornly refuse to accept the phillosophical purpose of the GPL, that is to protect the whole community of both users and authors from corporate (and other) abuse and are instead attempting to desperately figure out ways to circumvent this purpose.

    55. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "OK, let's pretend that this is indeed so, for the sake of amusement."

      Why "pretend" when we can *stablish*?
      There: http://www.gpl-violations.org/

      "That would mean that any contributor, to any GPL code is entitled to go after any corporation which somehow internally distributes some GPL code"

      (http://gnu.teleglobe.net/licenses/why-assign.html )
      "only the copyright holder or someone having assignment of the copyright can enforce the license. If there are multiple authors of a copyrighted work, successful enforcement depends on having the cooperation of all authors.
      by Professor Eben Moglen, Columbia University Law School"

      "...as it is unknown what GPL code is being used, until fully disclosed"

      (http://lwn.net/Articles/73848/)
      [the FSF way of enforcing GPL]
      "First, they (the bad guys) release an infringing product. Second, SOMEBODY HAS TO FIND OUT THAT THY USE GPL LICENSED CODE. Then, one of the original authors has to push for license compliance.
      [Editor's note: the following article was sent to us by Harald Welte, the leader of the Netfilter project.]"

      (http://www.gnu.org/philosophy/enforcing-gpl.html)
      "So what happens when the GPL is violated? With software FOR WHICH THE FREE SOFTWARE FOUNDATION HOLDS THE COPYRIGHT (either because we wrote the programs in the first place, or because free software authors have assigned us the copyright, in order to take advantage of our expertise in protecting their software's freedom), the first step is a report, usually received by email to . We ask the reporters of violations to help us establish necessary facts, and then we conduct whatever further investigation is required.
      by Eben Moglen"

      (http://www.gnu.org/licenses/gpl-violation.html)
      "...But, WE CANNOT ACT ON OUR OWN IF WE DO NO HOLD COPYRIGHT. Thus, be sure to find out who the copyright holders of the software are before reporting a violation"

    56. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      "only the copyright holder or someone having assignment of the copyright can enforce the license. If there are multiple authors of a copyrighted work, successful enforcement depends on having the cooperation of all authors. by Professor Eben Moglen, Columbia University Law School"

      Not to rein on the good professor's parade here, but if that were true, no copyright of any complex GPL code ever could be enforced. Some projects have thousands of contributors, many of them no longer accessible, alive, what not. Very few projects assign their copyright to the FSF. The professor is essentially saying: give all your copyrights to FSF because otherwise you can never enforce them. Which is obvious bullshit.

      [Editor's note: the following article was sent to us by Harald Welte, the leader of the Netfilter project.]"

      He is as much an authority as I am.

      So what happens when the GPL is violated? With software FOR WHICH THE FREE SOFTWARE FOUNDATION HOLDS THE COPYRIGHT (either because we wrote the programs in the first place, or because free software authors have assigned us the copyright, in order to take advantage of our expertise in protecting their software's freedom), the first step is a report, usually received by email to . We ask the reporters of violations to help us establish necessary facts, and then we conduct whatever further investigation is required. by Eben Moglen"

      That is a procedure for getting the FSF legal team involved, not for what individual authors can do.

      "...But, WE CANNOT ACT ON OUR OWN IF WE DO NO HOLD COPYRIGHT. Thus, be sure to find out who the copyright holders of the software are before reporting a violation"

      See above. FSF is saying: want our help? Assign the copyright to us.

    57. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "The professor [Moglen] is essentially saying: give all your copyrights to FSF because otherwise you can never enforce them. Which is obvious bullshit."

      So, exactly as I stated, even if professor Moglen (remember he is the one that gave legal form to the GPL, and the one that successfully defended its usage from FSF's part for over a decade) went to your home to explain the GPL's pretended meaning, you'd question him, just as you are doing now.

      You are either a stubborn moron or a troll (QED).

    58. Re:BSD vs GPL is not relevant by turbidostato · · Score: 1

      "Microsoft sells "media packs" for Open License customers (I assume this is what you are referring to)"

      Can you tell me where at Microsoft can I get media packs for Windows 95?

    59. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 1
      Can you tell me where at Microsoft can I get media packs for Windows 95?

      Do you have a valid Open License for Windows 95? My understanding is that all Open License programs older then Windows 2K have expired, other then on special contract. If you bought Win 95 retail or with a PC, you are entitled (according to the EULA) only to that copy. In case you do have a valid license, the Microsoft part # for the Windows 95 media kit is: 050-031-917 with a list price of $18. For Windows 98 media kit, the SKU is: 730-01345 with the same price. Microsoft does not publish these on their website as the Open License programs are run through authorized volume resellers, you would have to get the kit from one of them (many change these part numbers to their own SKUs). Again, assuming you have a valid license.

  33. Well, by Joseph_Daniel_Zukige · · Score: 5, Insightful

    I have thought along similar lines, but it really demonstrates something that we must quit ignoring.

    "Free" is an illusion.

    When we use "free" software, we pay for it one way or another. Time or money, and, no, time is not money.

    Money is green stuff that you through around on the crops to make things grow, as somebody in some famous musical once said, quoting somebody else, I'm sure. When you collect too much money in one place, it goes fetid.

    Time is the true currency, although too much time can go fetid as well.

    The licenses are gentlemen's agreements. It's a trade of time for time, with rules of courtesy. (EULAs are _not_ gentlemen's agreements, I am not taking about those licenses, they don't deserve to be called licenses.) The licenses form the ground rules for the community that forms around the software. It's very much like the old guilds, although much more open in a very good way.

    With the GPL, some of the rules of courtesy which are important for maintaining the infrastructure of the guild are explicit. We might assume that this is because Stallman is a cynic, or because he is a realist, but must people are still confused and think he is an idealist.

    With the BSD license, the rules are implicit, derived from the external society, the (Christian, though not entirely uniquely so in the current view of history) principle of casting one's bread on the water. It is expected that the waters will bring the bread back, multiplied. And this is where things have broken down.

    Even under the BSD license, the rules of giving back are natural laws, and are not suspended. Humans whose primary product are sales presentations have no idea that they have to give back or the resource will be depleted. Stallman recognized that, Theo has not yet.

    People have to be reminded to be courteous, and that's why an idealist and general nice guy like Theo ends up making enemies. The license doesn't remind people, so he has to spend his energy reminding them.

    Putting new source under GPL would be one solution, but, as is well known, it is not one that can really be considered yet. A new modified BSD that contains a non-binding reminder that the resources don't renew themselves may be what's in order right now.

    1. Re:Well, by Plunky · · Score: 3, Insightful
      With the BSD license, the rules are implicit, derived from the external society, the (Christian, though not entirely uniquely so in the current view of history) principle of casting one's bread on the water. It is expected that the waters will bring the bread back, multiplied. And this is where things have broken down.

      You imply that things have broken down because the bread never came back, but I would point out that the broken part was expecting it to.

      I write software and release it under the BSD licence because I dont care to lock it up. I dont care if somebody makes millions out of it, I wrote it because I wanted to, and released it because I wanted to.

      My opinion is that if the BSD licenced OS project that I am using goes belly up, it doesnt really matter. The code is still there and the people who write it are still here (if not the original ones, new programmers are born every minute) and the principle is still here. BSD4.4 is dead, but XxxBSD is not. If XxxBSD dies, YyyBSD will come along shortly.

      Now, I can see Theo's point about companies not giving anything back, but that is simply their bad karma and one day it may bite them.

    2. Re:Well, by Anonymous Coward · · Score: 0
      "Free" is an illusion.
      When we use "free" software, we pay for it one way or another...

      Someone else gets to tell Joseph_Daniel_Zukige about the beer/speech thing.
    3. Re:Well, by Anonymous Coward · · Score: 0

      Money is green stuff that you through

      Incorrect word usage something you throw around too to make trolls grow.

  34. Time to merge OpenBSD with NetBSD by ad454 · · Score: 1

    Both NetBSD and OpenBSD are great platforms and each have their benefits. Prehaps it is time for OpenBSD to join into NetBSD.

    I realized that people said and did bad things in the past, but come on, let by-gones be by-gones. We are all adults and time heals old wounds.

    There must be a way to convince the OpenBSD and NetBSD core developers to work together.

    Maybe I am just a wishful thinker.

    1. Re:Time to merge OpenBSD with NetBSD by bhima · · Score: 1

      As a user of both OpenBSD and NetBSD I don't see the utility of this. OpenBSD supports all the architectures commonly used in the way people use OpenBSD. And I'm not altogether sure all of the various platforms that NetBSD supports would benefit from the differences in development requirements & style... maybe so but I don't think so.

      Perhaps FreeBSD & OpenBSD could merge... but I'm not so familiar with FreeBSD so I probably shouldn't comment.

      --
      Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
    2. Re:Time to merge OpenBSD with NetBSD by Anonymous Coward · · Score: 0

      Not wishful, woefully ignorant, boardering on stupid even. There are fundamental security enhancements in OpenBSD, the code audit cannot be merged into NetBSD. You'd have to add NetBSD's code into OpenBSD, which OpenBSD developers do anyways for the most part.

    3. Re:Time to merge OpenBSD with NetBSD by Anonymous Coward · · Score: 0

      Well, at that rate you just might as well as say that all the BSDs just merge and be called AllBSD or TheBSD.

      Please, just keep it the way it is.

    4. Re:Time to merge OpenBSD with NetBSD by nblender · · Score: 1

      Nope. No way. Trust me, I was there. Besides, NetBSD isn't interested in running security audits using awk scripts only to accidentally re-introduce security holes that were fixed in the early 80's by CSRG. (yes, happened in OpenBSD).

  35. Let's Add Some Context Here by Noksagt · · Score: 5, Insightful
    First, I think the OpenSSH question was baited. Even disregarding that, you excluded an insightful caveat from Theo's reply:
    Of course we did not set out to create OpenSSH for the money -- we purposely made it completely free so that the "telnet infrastructure" of the 1980s would die. But it sure is sad that none of these companies return even a fraction of value in kind.
    He acknowledges that not only was there no obligation for these companies to donate money, but that OpenSSH wasn't created to make money. I don't think it is unreasonable for him to ask for money, particularly when he has pointed out that some of the vendors selected OpenSSH after they were quoted high fees (multi-millions of USD) from the commercial SSH vendor.

    OpenBSD has done good work & currently depends on receiving financial donations. Enlightened companies should notice that OpenBSD needs some funding right now & that it would be cheaper to fund them than to have to adopt the support and development of the OpenBSD products they use.
    1. Re:Let's Add Some Context Here by Anonymous Coward · · Score: 0

      So, he wanted it free so telnet would die. He wanted his own product to displace another. Then after it had done so, he wants everyone to start paying him for the privilege of using that software. Sounds like bait and switch to me.

    2. Re:Let's Add Some Context Here by penguin-collective · · Score: 1

      Enlightened companies should notice that OpenBSD needs some funding right now & that it would be cheaper to fund them than to have to adopt the support and development of the OpenBSD products they use.

      Or, more likely, enlightened companies have done the math and decided they don't care.

  36. Re:Anti-Theo sentiments are muddying the point her by Anonymous Coward · · Score: 1, Insightful

    Regardless of what work the OpenBSD team does or doesn't do, Theo de Raadt is the one who will be receiving, and managing, the money. Theo de Raadt, as the public face of OpenBSD, is the only sign we have of why this money is needed and what will be done with it. Thus it is quite reasonable, if the person serving as the public face and cash collector for this funding drive is publicly handling the drive in such a way that he seems to be making unreasonable demands or unreasonable threats, for this to reflect badly on the funding drive itself.

    It is as simple as this: OpenBSD is not asking for everyone to just get along with them and not pick on them. If they were, they would be meeting with a much better response. They are asking for money. People tend to have somewhat higher standards of someone who approaches them asking for money than they do the rest of the time, especially when that person is mostly asking for that money to fund a product that most of us don't want or use. The OpenBSD project can't continue to support SSH development on their own? Well, honestly my first response is "well, then let's find someone who can". It has not been at all made clear to me why OpenSSH development is not a task which can be continued by someone else, nor why OpenBSD development must necessarily be tied to OpenSSH development.

    Your bizarre comparison to high school social dynamics is a complete non sequitur and I think says more about your mindset regarding the situation than it says about the actual situation itself.

  37. Re:Iff..... by Anonymous Coward · · Score: 0

    Not really, the Wikipedia article is one of the best singular sources of information on OpenBSD available, it's even one of the best articles on Wikipedia (just click the star on the top right corner of the article).

  38. GPL based distributions have to beg too by AHumbleOpinion · · Score: 1

    GPL based distributions have to beg too. I have rough recollections of several such requests appearing on slashdot in recent memory, I don't recall the details but a quick google finds:

    "The first public signs of financial trouble at MandrakeSoft appeared in March 2002 when Mandrake began asking users for donations and changed their support structure to get a new revenue stream."
    http://geek.com/news/geeknews/2003Jan/osg200301160 18188.htm

    Theo's bed was made by driving away potential sources of income like DARPA, not his choice of BSD over GPL.

  39. uhm, yes, by Joseph_Daniel_Zukige · · Score: 1

    google pays for linux and apache.

  40. Be fair by grahamsz · · Score: 3, Informative

    Sun bought and open sourced both StarOffice and Netbeans, they've open sourced Solaris and the UltraSPARC processor core.

    I'm sure there are plenty other projects, but Sun have donated what must amount to many millions of dollars of code to the community.

    Sure they use other open source projects (in line with their licenses) and while they presumably aren't throwing money at Theo it seems unfair to brand them as anti-opensource when they've done a lot of good.

    1. Re:Be fair by marcovje · · Score: 1


      Afaik _paid_ Sun engineers did quite a lot of work on Gnome/GTK2 localisation and disability support

      Still, 1000 Dollar grants in total for OpenSSH is meagre. Very meagre. So despite that I take everything what Theo says with a grain of salt, there seems to be some point in it.

    2. Re:Be fair by justins · · Score: 1

      Ooooh, good point. What is OpenSSH compared to Netbeans?

      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    3. Re:Be fair by John+Whorfin · · Score: 1

      Wasn't OO open before Sun bought them? (Honest question, I don't remember)

      As far as Sun opening UltraSPARC, have you actually tried to get UltraSPARC documentation? You have to (or had to, it's been a while) sign an NDA. Folks that isn't "open".

      Sun also donated code to OSS projects and forced decidedly non-open license changes (ECC code to OpenSSL comes to mind).

      OSS, Sun is not your friend.

    4. Re:Be fair by Tony · · Score: 1

      Wasn't OO open before Sun bought them?

      No; there was no OpenOffice until Sun purchased StarOffice and created the OpenOffice organisation.

      Sun has done a lot for the Free / Open-Source community. They have been kinda wishy-washy at times, but they have done quite a bit.

      Now if only they would open up the official Java code base.

      --
      Microsoft is to software what Budweiser is to beer.
    5. Re:Be fair by Anonymous Coward · · Score: 0

      Sun, is a funy animal. They many times get it, and many times don't. McNealy was/is a coder/hacker at the core of it all. Sure it's the latest buzwords. On the other hand what do they have to gain? They definatly came through when it came to hardware (750 USD for a dual core system?) The real question for them is have they given thought to migrating to being a foundation?- I know this sounds nuts- but few Tech companies are doing all that well, (Microsofts Windows fiasco for instance) It might just be as good a time as any to go NGO, they have a hard time even breaking even. Might be a good time to decide that it's ok to rest on their laurels and go into nothing but R'n D.

    6. Re:Be fair by Anonymous Coward · · Score: 0

      For those millions of developers who use Netbeans but wouldn't touch OpenBSD (or ANY BSD) with a 10 foot pole, it's far more important.

  41. Amusing indeed by h2odragon · · Score: 1
    Why was OpenSSH created in the first place?
    Later licenses restricted the use of ssh in a commercial environment, instead requiring companies to buy an expensive version from Datafellows.

    (from the OpenSSH History page)

    I have to wonder how long it will be before the commercial SSH folks are talking to apple and sun and so on about really cheap bulk licenses.

  42. Re:Iff..... by mcrbids · · Score: 0

    OpenBSD was the result of a squabble between Theo and the NetBSD team. This was a felicitous squabble for the rest of us, because OpenBSD is a great operating system.

    Come again? Definition for felicitous.

    Perhaps you meant fallacious? or perhaps flagitious?

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
  43. Check your dates by Noksagt · · Score: 2, Informative
    "Some of the OpenSSH freeloaders, like Apple Computer..." Apple and SCO aren't "freeloaders", they are using the software under the intended license.

    No, it's far simpler than that. Apple and SCO *paid for* BSD. BSD was paid for by the taxpayers of California, including corporations like Apple and SCO. Perhaps Theo noticed a "Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California.
    OpenSSH development began in 1999. So, no Apple didn't pay for OpenSSH. Yes, tax payers paid for the original BSD, from which NetBSD borrows from (and OpenBSD forked from NetBSD). (Though I think it was probably mostly funded under a federal grant, rather than state taxes.)

    In any case: development and maintenance costs don't magically stop when there is no tax-funding of the project. If people want it to survive, they do need to continue sponsoring it.
    1. Re:Check your dates by ak3ldama · · Score: 1

      don't confuse him with the truth!

      --
      "but money is the God of Algiers & Mahomet their prophet." - Rich. O'Bryen June 8th 1786
  44. Doesn't Theo understandf the BSD license? by ChrisKnight · · Score: 1

    Theo forked a BSD licensed project to create OpenBSD. If he wanted money, then he should have forked into a proprietary license. He forked and kept the BSD license. Since this was a choice, I assume it was made with some forethought. After all, just try to suggest that Theo has made a mistake and he will argue you to death that he knew what he was doing...

    So, he OpenBSD and OpenSSH are BSD licensed by choice. That means that NOBODY needs to give them money if they use the source code. The BSD license spells this out, in less than a page of text, so it is hard to say this was buried in the small type...

    Theo IS OpenBSD/SSH, and THAT is the real problem. Theo pisses people off, and alienates corporations that would donate to a OpenBSD/SSH project. He needs to incorporate OpenBSD/SSH and give himself a little abstractionb from the process if he wants someone else to help with the bills. Until then there is no 'corporate veil' between Theo and OpenBSD/SSH, and that in itself is hurting the 'movement'.

    -Chris

    --
    -- This sig is only a test. If this were a real sig it would say something witty. --
    1. Re:Doesn't Theo understandf the BSD license? by toufeeq · · Score: 1

      I can't complain, but sometimes I still do. -- Joe Walsh The saying-for-the-day for this poic.Isn't it apt ?

    2. Re:Doesn't Theo understandf the BSD license? by bhima · · Score: 1

      Over the past 20 years of my professional career I can't tell you how many times I've had to deal with CEOs (or other upper management types) of small companies who are so egotistical and such amazing assholes it boggles the mind how such people can go on in their day to day life.

      Theo isn't that bad, nor is he unique, nor do businesses frequently make strategic decisions based on single personalities. I don't think the problem is Theo or even the license but rather the inappropriate way businesses react to the license (and in this respect the GPL has some advantages).

      I'm sure Theo clearly understands the BSD license and all of its nuances... if you read the article his desire isn't a house in Costa Rica it's for businesses to help fund OpenSSH developers participate in that businesses development of things that use OpenSSH and for some assistance for poorer developers. None of these requests are unreasonable, or without benefit to the company which was requested to contribute.

      This is a sort of tragedy of the commons scenario... because it's in *everyone's* best interest to have tools like OpenSSH available.

      --
      Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
    3. Re:Doesn't Theo understandf the BSD license? by MichaelSmith · · Score: 1
      He forked and kept the BSD license. Since this was a choice, I assume it was made with some forethought.

      This was in the days before cheap broadband, when you really had to buy the CD's.

  45. yes by subtropolis · · Score: 1

    It's just you.

    --
    "Our interests are to see if we can't scale it up to something more exciting," he said.
  46. Re:Problem with BSD licencing?? by giorgosts · · Score: 1

    BSD licencing would be more appropriate for government or university funded programes where the funding issue is resolved and the benefits of the developers' work go directly to the public, whether commercial or otherwise.

  47. Misleading linking by Anonymous Coward · · Score: 0

    The submitter of the story should learn to link. The link leads to the interview, not to a page describing Theo, so the word interview should have been marked as a link.

  48. BSD Unification the Savior? by JRGhaddar · · Score: 1, Funny

    I'm not a developer, but I sort of understand the BSD world.

    OpenBSD - led by Theo (whom apparently has a lot of enemies) is a BSD based distribution with the core focus being security

    FreeBSD - A BSD distribution based on making it really fast

    NetBSD - A BSD distribution based on optimizing Network Configurations

    [Please correct any of that so I personally can understand the flavors of BSD better]

    Okay why don't the individuals from all three get together and create AllBSD?

    I mean take the best parts and make a speedy secure network optimized distro?

    I mean what is the point of open source if its not about individuals working together to make the optimum software based on peer review? Is this for the glory of one individual distro? That seems to go against the very mindset of opensource. I understand each distro brings something different to the table, but why not have a centralized distro that everyone contributes to AND have your special spinoff version. The main distro could be licensed out(making $) which then the proceeds could be divided equally among the other distros, and they can make extra money hawking shirts/cds dontations etc.

    The very instance one individual(distro) thinks it's better than the cause itself is when things began to decay. Linux is different because they don't squabble (SCO doesn't count they aren't human but monsters grown in a M$ petri dish) and each one provides its own niche in the linux market. BSD is its own tiny market, and consequently can't afford that luxury...yet. A unification for the cause of BSD would instantly put BSD as a forefront as a major OS alternative, and definitely has a lot going for it due to OSX showing that an OS derrived from BSD can be successful.

    Like I said I'm not a developer, but I really believe that a BSD deserves a chance to move away from the individual bickering and crying I see currently going on.

    Please feel free to reply and shed some light on this situation so I can better understand.

    [I appologize for any grammar/spelling mistakes]

    1. Re:BSD Unification the Savior? by Bojan+Zivanovic · · Score: 0

      FreeBSD aims to produce a good desktop system,

      NetBSD aims to be portable across many platforms..

      They can't all unite because of their very different focuses (and ego issues..)

    2. Re:BSD Unification the Savior? by Anonymous Coward · · Score: 0

      NetBSD - A BSD distribution based on optimizing Network Configurations
      [Please correct any of that so I personally can understand the flavors of BSD better]


      No, it's net as in 'developed across the internet'. NetBSD's primary aim is portability though clean code.

      See the NetBSD 'about' page.

      Okay why don't the individuals from all three get together and create AllBSD?

      Because they have different design philosophies: it's impractical. But they do merge code between each other as and when.

    3. Re:BSD Unification the Savior? by Anonymous Coward · · Score: 0
      I'm not a developer, but I sort of understand the BSD world.

      You obviously don't understand the BSD world. The BSD projects aren't different because they are better at different things; they're different (and better at different things) because they have different priorities and goals that are largely incompatible. FreeBSD targets high-stress server environments where performance and reliability are paramount, so FreeBSD can do some bizarre stuff to improve performance--a while back someone did a benchmark between Linux and the three main BSDs, and the socket() graph shows you the kind of hacks FreeBSD does to improve performance.

      NetBSD makes a clean, clear codebase a top priority, and its portability is kind of a feedback loop that both results from that decision and motivates it. NetBSD also tries to be very research friendly, and its high-performance networking stack is frequently used to set Internet2 records. They are also the least vociferous about software Freedom, as they were the last of the major BSDs to adopt X.org, and the only one to still use the "four-clause" version of the CSRG license.

      OpenBSD also strives for clear code, but places much greater emphasis than the others on security and strong cryptography. OpenBSD periodically audits code, checks for bugs proactively, and the same kinds of bizarre hacks FreeBSD uses to improve performance are used in OpenBSD to improve security (such as making structuring vm pages out of order to prevent malicious buffer overflows. OpenBSD is also the most strongly advocating Free Software, as they spearheaded (along with Debian) the campaign to dump Xfree86, maintain a version of Apache 1.3 because the 2.x license was less free, and include no binary drivers or otherwise unfree in the base distribution. They're kind of like a BSD version of the FSF.

      DragonFly[BSD] is the newcomer of the bunch, a fork of FreeBSD. So far the over-arching goals are to improve modularity and to replace bulky structures and processes with lighter, quicker versions. The plan to replace the usual syscall table with a messaging api (apparently like a lightweight Mach-type thing, but evidently not microkernel design) make it very different from its cousins.

      It's important to note that these are not just the result of a few random patches to the system approved by a czar, as in Linux, but explicit decisions by the core developers to follow a particular blueprint, to make a particular improvement, or to support (or not) an obsolete API/ABI. If you want to submit a patch out of the blue, you certainly can, and if it's competently coded it will probably be accepted, but the overwhelming majority of code contributions come from the core developers following architectural guidelines. If you tried to combine all 3-4 codebases, the incompatibility of several design decisions would end up combining a stable OS, a lightweight OS, a portable OS, and a secure OS into something that managed to preserve none of these features.

      That said, however, because of the similar licensing requirements, the BSD projects all share code extensively, and are frequently source (if not binary) compatible with each other. So it's not like Linux, where packaging systems are completely different but the OS features are all the same (because they use the exact same codebase). In an odd way, the members of BSD family are both more closely related and more different from one another than the various Linux distros are.

    4. Re:BSD Unification the Savior? by JRGhaddar · · Score: 0

      Thanks for filling me in on this. I now understand a little bit of what is going on. I appreciate you taking the time to explain everything so well.

    5. Re:BSD Unification the Savior? by Anonymous Coward · · Score: 1, Informative

      I don't think so, NetBSD just doesn't agree with the FSF's definition of free software - FreeBSD on the other hand seeks out binary blobs and NDA covered source code for the ease that comes with it, while quite violently protesting OpenBSD's attempts to get documentation to make open source code. DragonFly is more pragmatic, it will use the binaries and such if no other option is available, but will assist in attempts to get open documentation for things after they are done with their fundamental base restructuring, or that's what Matt Dillion said once.

      OpenBSD is the only one of the four that refuses to make use of the ndis, or "project evil", binary network driver support layer.

    6. Re:BSD Unification the Savior? by Anonymous Coward · · Score: 0

      I never meant to imply that NetBSD didn't care about software freedom, but the fact of the matter is that they use a license which contains more (admittedly trivial) restrictions, and in my book more restrictions=less freedom. But I didn't know that about FreeBSD's approach to documentation; I'll certainly look into that.

  49. Re:Iff..... by tarp · · Score: 1

    No, he meant felicitous. Read it again. It makes sense.

  50. OpenBSD must grow up by BigFootApe · · Score: 1, Insightful

    I know that Theo spouting off does him no good with the corporate world. Has he ever thought of getting someone else on his team to do the PR stuff?

    Theo is a brilliant engineer, but he has no tact and (seemingly) no restraint. If he allows a more diplomatic member of his team to act as a buffer and sounding board in relations with the press and sponsors, he might avoid burning some bridges in the future.

    I'm not saying OpenBSD needs a change in direction, policy, or anything like that. I just think that Theo needs to find a way to stop kicking people in the balls any time he has a knee-jerk reaction.

    1. Re:OpenBSD must grow up by MichaelSmith · · Score: 1
      I know that Theo spouting off does him no good with the corporate world. Has he ever thought of getting someone else on his team to do the PR stuff?

      Football clubs here in Melbourne get funds partly by selling annual memberships. With your membership you get a sticker for your car saying that you are a paid up member for year such and such. People get a kick out of displaying evidence of their contribution.

      Perhaps OpenBSD could sell something similar: paid up OpenBSD user for 2006 for example and you could link to it in your sig if you wanted to.

      And I totally agree with you about Theo and PR. Technically he is exactly the right person to run OpenBSD. Its just that he is not a people person.

    2. Re:OpenBSD must grow up by Anonymous Coward · · Score: 0
      Football clubs here in Melbourne get funds partly by selling annual memberships. With your membership you get a sticker for your car saying that you are a paid up member for year such and such. People get a kick out of displaying evidence of their contribution.

      Or they could sell tees... oh wait

  51. Oh really? by Deorus · · Score: 3, Informative

    > Also if you ever want a RALink driver, OpenBSD is the only OS that has one right now and it seems almost certain any ports will be based off it.

    I thought RALink supported Linux themselves, otherwise, what's this?

    1. Re:Oh really? by cortana · · Score: 1

      I wish that driver was in the kernel. Well, I wish the rewrite that makes it not shit was finished and therefore in the kernel.

    2. Re:Oh really? by malloc · · Score: 3, Insightful

      *that* is called a binary blob driver. It means if you're willing to give control of what kernel you run to this company then you can use their driver. Essentially this boils down to them controlling your whole machine and is why Linus refuses binary drivers. ("No, you can't use this new kernel feature", "no, you can't debug this crash", "sorry, we're out of business, you can't upgrade your kernel ever again") There's nothing to praise about that.

      Malloc

      --
      ___________________ I want to be free()!
  52. Re:Iff..... by Flagran · · Score: 1

    Why would you think that he didn't mean felicitous? His opinion is that OpenBSD is a great operating system; therefore, the event that lead to its creation is an event marked by good fortune. So, from his point of view, the squabble was indeed felicitous.

    --
    Make love, not sigs
  53. This is why GPL is so popular. by miffo.swe · · Score: 0, Redundant

    If you release something under a license(BSD) that lets people screw you over what do you expect? Companies will take whats good and give back nothing, not money, developers or anything. Change the friggin license already!

    --
    HTTP/1.1 400
    1. Re:This is why GPL is so popular. by Anonymous Coward · · Score: 0

      "If you release something under a license(BSD) that lets people screw you over what do you expect? Companies will take whats good and give back nothing, not money, developers or anything. Change the friggin license already!"

      Idiot.

      Where OpenBSD/OpenSSH released under the GPL, the companies that use it would be no more compelled to give money back to the OpenBSD crew.

      Use your fucking head.

    2. Re:This is why GPL is so popular. by miffo.swe · · Score: 1

      Thanks for the insult =)

      Then please explain why so many of the developers of Linux is full time employes of various companies out there? Much of the infrastructure and meetings and so on is also paid by outstanding corps. I dont think Linux is better than *BSD in any way so i assume its the GPL license that makes corps more inclined to help Linux development than *BSD.

      --
      HTTP/1.1 400
    3. Re:This is why GPL is so popular. by Anonymous Coward · · Score: 0

      'GPL your code now and Sun Microsystems, Redhat, Linus Torvalds and the Tooth-Fairy will chip in to pay the massive electric bills that result from running multiple servers 24/7.'

      Do you yet see a flaw in your logic, or is sarcasm not enough to show you the error of your thinking?

    4. Re:This is why GPL is so popular. by someone1234 · · Score: 1

      Reading TFA i saw the openssh project got a whopping $1000.00 from individuals, not companies. I believe Linus got more pocket money last month.

      --
      Patents Drive Free Software as Hurricanes Drive Construction Industry
    5. Re:This is why GPL is so popular. by Anonymous Coward · · Score: 0

      Correlation != Causation.

      People are dense.

    6. Re:This is why GPL is so popular. by miffo.swe · · Score: 1

      I really do believe the reason is the GPL license and not that Linux in any way are sexier or better than *BSD. Can you describe in a better way why Linux is so much more popular than *BSD?

      As i see it corps and many developers think that if you give something away to *BSD you give your competitors a free lunch they probably wont return. In fact they could just take your code, implement it in an incompatible way in a larger userbase rendering your implementation worthless. GPL prevents that kind of behaviour and doesnt give anyone with a larger userbase the upper hand, like for instance Microsoft. With the GPL they have to reveal the changes. That way you cant take someone elses code and screw the originator from here to mars.

      --
      HTTP/1.1 400
    7. Re:This is why GPL is so popular. by MemoryDragon · · Score: 1

      Actually it is less BSD, the bsd license works for Apache (well Apache is not BSD but close enough) really well as does for PostgreSQL.

    8. Re:This is why GPL is so popular. by LurkerXXX · · Score: 1
      Because in the early 90's when Linux was taking off, the BSDs were tied up in a lawsuit (eventually decided in their favor) and that kind of halted the expansion of their userbase for a few years, right at the time when the whole internet thingy was taking off.

      New poor geeks all over the place were rapidly getting internet connections for the first time. They could either start playing with Linux, or BSD... which might go away if the lawsuit went badly. Lots of folks started playing with Linux that might otherwise have started playing with BSD.

      That's not the whole reason for the current distribution of the userbase, but it certainly played a role.

  54. This is a money debate, not chiefly about licenses by jbn-o · · Score: 1

    From what I read, this isn't really a licensing complaint. I'm sure de Raadt is fully aware of what happens when one doesn't look out for preserving software freedom for derivative works. His is a complaint about money and the enormous disparity between those who have a lot of money and those who don't; licensing OpenSSH under the GNU GPL wouldn't have gotten the OpenSSH developers the money they seek.

    de Raadt noted that "Twice we asked them [Sun] to cover the travel and accommodation costs for a[n OpenSSH] developer to come to their event, and they refused.". That's Sun being greedy and other big businesses (Apple, Cisco, SGI, HP, Siemens, and various commercial GNU/Linux distributors including Red Hat and IBM) not doing anything to lighten the OpenSSH developers' load despite having billions of dollars between them.

    It also points out how the marketplace has yet to make right any of this—no doubt Sun can go on treating their unpaid workers at OpenSSH poorly. I hope more people and organizations will recall de Raadt's words when considering doing business with Sun. We have the power to try and shame them into doing something they can each afford, we should use it. Along this line, interesting how individuals have contributed all of the money the OpenSSH team has made from this, despite that amount being under a paltry $1,000.

  55. What value free speech and human life versus code? by jbn-o · · Score: 1

    "Pissing off" DARPA by speaking out against the invasion and occupation of Iraq?

    And any organization that distributes proprietary software is more self serving than an organization that distributes software I have the right to run, share, and modify.

  56. There's a saying by theolein · · Score: 1

    Trust is good but control is better. Theo de Raadt trusting that developers will handover money out of the good of their hearts for the free work done by the OpenBSD crowd is naive at best and downright stupid at worst. One of the reasons that Apache/PHP/MySQL are so popular is that people don't have to pay for them. That's the way it goes. People/Companies, it doesn't matter.They all will always be looking for a bargain. Even IBM is not supporting Linux because it thinks Linux is so good. It's doing it because there's money to be made.

    TdR needs to give companies an INCENTIVE to give him money to develop. Making childish threats is one way, sure, but probably not the most effective. Pointing out to the various companies that there will be no future ssh if OpenBSD goes under would probably help more.

  57. Re:Anti-Theo sentiments are muddying the point her by DNS-and-BIND · · Score: 1

    If Theo wasn't such a horrible asshole, he would have a much easier time getting grants. I certainly would never give the man a dime, no matter how talented he is. That's the point.

    --
    Shutting down free speech with violence isn't fighting fascism. It IS fascism!
  58. seems like IBM sent the customer directly by Lanboy · · Score: 1

    Lazy move on a helpdesker's part. If the OPEN BDSers don't want to work on it, send a form letter or ignore it. Or stew in indignation, whatever.

  59. Oblig by upside · · Score: 1

    It's official, BSD is dead! TdR discusses OpenBSD and the Beyond!

    Oh, not *that* Beyond. Never mind.

    --
    I'm sorry if I haven't offended anyone
  60. BSD license is the greatest asset, merge all BSDs by Anonymous Coward · · Score: 0

    The biggest mistake is forking of BSDs. The BSD initiative should not have financial difficulties. Its license is the greatest asset. GPL is not business friendly. Don't you guys see this? It is only the BSD initiative can get blessing from companies. Why don't you guys use the opportunity. As the first step, merge all BSDs into one project, may be to the FreeBSD. Sell the importance of BSD license to companies and attract their funding for the project.

    I'll give one example, currently I'm evaluating a Linux OS named Tomahawk Desktop designed for multimedia, entertainment and office use. Its pathetic they don't have important drivers for printers, top end graphic cards such as ATI, 3D Labs, Intel Core-Duo WiFi, etc. Why? Its because of Linux is under GPL. It is illegal to develop and distribute closed source drivers for Linux. No manufacturer wants to release the source of their drivers. That is the nature of business. In business you need a competitive advantage. Its ONLY BSD can give that competitive advantage to business.

    See Apple has drivers for all important printers, scanners, fax, graphic cards, wifi cards, etc. Why? It is completely legal to develop and distribute closed source binary drivers.

    See who financially benefit from the BSD initiative. Those are the companies the BSD project should deal with, keep in touch and get funding. Do you think they will refuse to fund the project?

    Just list the commercial users of the BSD in your website (eg. FreeBSD) for whole the world to see. It is not unethical to even list their contributions in the website.

  61. Re:Iff..... by upside · · Score: 1

    BSD /is/ Unix, not Unix-like. There's System V and then there's BSD.

    BSD doesn't have a special security model, they're just very very conservative. BSD has a lot less code, the pace of change is a LOT slower so the code is mature, and OpenBSD have extensive code reviews. OpenBSD didn't even have SMP support until recently.

    Linux puts stress on keeping up with the bleeding edge, lots of features and broader hardware support. Linux does everything from supporting the latest graphics and video cards to supporting dozens of CPUs on enterprise hardware. If you want enhanced security on Linux, go for SELinux or GRSecurity.

    --
    I'm sorry if I haven't offended anyone
  62. Apparently... by nurb432 · · Score: 0, Redundant

    OpenBSD has no value to the world.

    Now, before you mod me down, or flame me to death: If a project cant get enough funds to keep going, it says something about its worth to the public. If you find somethig of value DONATE, and it keeps going.. If you dont find it of value, then dont dontate and it wil die out.

    Pretty simple math.

    Personally, i have donated and will be saddened to see it go, but seems not enough of us that do appreciate it are out there.

    --
    ---- Booth was a patriot ----
    1. Re:Apparently... by Anonymous Coward · · Score: 0

      OpenBSD has no value to the world.

      No offence, but that's a narrow-minded point of view. And you only say that because you really have no idea where OpenBSD code is being used. OpenBSD is a very important part of our security infrastructure. Our governments use it (and no, it doesn't matter which government you belong to because somewhere OpenBSD will play a role). Just because you don't know about it doesn't mean that it isn't there.

      I believe the real problem is that time is expensive, and that the easiest way to solve a problem is to simply download the fix and deploy it. There isn't always time to walk the extra mile and donate as a "thank you", even if you are extremely grateful.

    2. Re:Apparently... by nurb432 · · Score: 1

      You missed my point totally.

      --
      ---- Booth was a patriot ----
    3. Re:Apparently... by Dehumanizer · · Score: 1

      I think it's simply a case of people being stupid, and only realizing the value of things after they've lost them. OpenSSH is still around, and it's free - therefore, it's "worthless", even though all of them use it, and would have to spend millions if it wasn't available.

      --
      The Tlog - a technology blog
  63. Re:Anti-Theo sentiments are muddying the point her by IcePic · · Score: 1

    Why aren't someone already doing a SSH of their own then?
    Apart from the proof-of-concept-type ssh clients out there (good or bad)
    there is *nothing* to stop anyone from taking the same ssh1-code and
    reimplementing all the goodies OpenBSD got in there.
    Or write a GPL'ed own ssh for the linux crowds. The specs are there,
    the protocol isn't secret.

    It's not like it isn't possible, its just that building up that kind
    of trust seems harder than you'd first imagine. These guys have made
    it, others may not.

    --
    -- I'm as unique as everyone else.
  64. just donate by rap-engineering · · Score: 1

    Come on guys. Just donate $5. Can you imagine life without openssh? I shure can't.

    1. Re:just donate by /dev/trash · · Score: 1

      you mean if I don't pay the code goes away and my binary stops working???

  65. Re:Iff..... by IcePic · · Score: 2, Insightful

    like why glibc wont have strl*()-functions which may improve security:
    http://lists.debian.org/debian-devel/2002/03/msg00 309.html

    It's not like the whole linux world would fall apart if there was some more
    string functions which would not go ape on weird inputs.
    I know strl*() isn't a magic bullet to prevent all kinds of badness, but they
    really can't be worse than the same functions without bounds checking.

    Still, better to bash some BSD...

    --
    -- I'm as unique as everyone else.
  66. Fork it! by scarolan · · Score: 2, Insightful

    Our company would be more inclined to donate if we knew that the money we gave would go directly to support OpenSSH. We have no interest in supporting OpenBSD. Fork OpenSSH into it's own project with separate financing and management, and we'll send you some money.

    1. Re:Fork it! by rap-engineering · · Score: 1

      I don't care much about openbsd either. However openbsd is used to develop openssh and the developers will not be happy without. You can't have openssh without developers. If everyone were to donate $5, that could cover the costs. Don't tell me you're that greedy

    2. Re:Fork it! by merdaccia · · Score: 4, Insightful

      Then people wonder why de Raadt behaves the way he does. When I read this post, my first reaction was to send you to hell with enough bad language to put you in a first class seat. Maybe that's why de Raadt gets his stigma, by not taking a pause from his first reaction.

      So you want to know that the money you give would go directly to support OpenSSH? According to de Raadt, there are six developers that focus on OpenSSH. These developers also work on other aspects of OpenBSD. What exactly do you want them to do? Divide your money between the six of them according to how many hours each works on OpenSSH? Do you want them to have separate network connections and hardware, and pay for it with your donation? How do you compensate the other OpenBSD developers when their ideas and contributions inevitably end up in the OpenSSH codebase?

      The OpenBSD developers are a group of people working together. OpenSSH is the fruit of their work. The way to contribute directly to OpenSSH is to contribute funds to its developers. That's exactly what contributing to OpenBSD does, because the developers of OpenBSD and the developers of OpenSSH are one and the same.

      So contrary to your second sentence, you have every interest in supporting OpenBSD. Saying otherwise is a disingenuous and pathetic attempt at justifying your reluctance to reward the people whose work you claim to respect.

      --

      *blinking cursor*

    3. Re:Fork it! by scarolan · · Score: 1

      My, touchy aren't we? It's early, maybe you haven't had your coffee yet this morning.

      We use Linux and we support Linux development with our money, bugfix suggestions, and by encouraging other companies and clients also to use Linux. We don't use OpenBSD, and the only part of it that is useful to us is OpenSSH. Why should we pay to support an entire operating system that we have no use for?

      Cable companies would also rather we pay for 100 channels of stuff we don't watch, but that is finally starting to change. You can now purchase individual shows or movies, and not have to pay for things you don't want. This is a good thing, because it puts more control in the hands of the end-user.

      OpenSSH works fine on Linux or other flavors of Unix and could easily stand alone as it's own product with it's own management team. You might even get a corporate sponsor like IBM or Sun to 'adopt' the project.

      Theo needs to A. Figure out a way to provide a service or product people are willing to pay for or B. Go work for someone else. Begging and whining about freeloaders is not the way to win support for your project.

    4. Re:Fork it! by adamofgreyskull · · Score: 1

      Err..you're acting as if this is the hardest thing in the world. It's not hard to log the amount of time you spend working on project X, I'm sure enough people have to do it in the Real World. If a group of people then donate money for openSSH the money could be divided between the developers working on the project to recompense them for time/resources. If someone else comes up with a natty idea for openSSH and it ends up in, you could book them for a nominal amount of time on the project and recompense them.
      If I don't use product X, why should I fund it? It's not really unfair to want to contribute only to projects that you use...

    5. Re:Fork it! by Myrrh · · Score: 2, Informative

      Theo mentions in the interview how it would not be advantageous to become a non-profit organization. I'm not sure where he and his developers operate, so I can't speak to the specific laws of his country.

      But, incorporating (for-profit or otherwise) is not difficult and needn't be expensive, either. Were he to do so, he could adopt articles of incorporation and bylaws which would clearly state the divisions of the company. He could create an "OpenBSD" division and, similarly, an "OpenSSH" division.

      Maintaining some documentation that would be open to review by interested parties would likely go a long way toward placating companies who would like to contribute financially, but are loath to do so because they have no assurance their funds won't be going directly to OpenBSD development. There should be a way for interested parties to earmark their funds for one or both projects, and have some assurance that their funds will be used properly.

      Theo refuses time and again to accomodate such requests, and therefore he is forever grousing about how so many companies refuse to provide financial support in exchange for OpenSSH, which supposedly significantly enhances these companies' bottom line.

      I really believe that if he were to take a bit of time off from coding to contact a CPA or attorney (heck, he could probably get it pro bono if he turned off the vitriol for a little while), formulated a sound business plan and filed articles of incorporation, and then presented his case to these companies he is so fond of complaining about, he just might see some funds come his way.

      I think, though, that he would rather complain than actually get something done about it.

    6. Re:Fork it! by Anonymous Coward · · Score: 0

      "We have no interest in supporting OpenBSD"

      Oh get over it. You have an intrest in secure communications to a friggin OS, any OS, pick one, they pick OpenBSD to develope on. WTF you care about what OS they develope SSH on?

    7. Re:Fork it! by merdaccia · · Score: 1
      We don't use OpenBSD, and the only part of it that is useful to us is OpenSSH. Why should we pay to support an entire operating system that we have no use for?

      Did you bother reading my post? You should pay to support the entire operating system because the part that is useful to you wouldn't exist without it. It's that simple. By your logic, why pay taxes if the money is going to be used to fix somebody else's street? Because if you don't, your street won't get fixed either.

      You can now purchase individual shows or movies, and not have to pay for things you don't want.

      So say you purchase a movie you want to watch. The money goes to the cable company to do with as it pleases, including the purchase of rights to broadcast shows you don't want to watch. So yes, you're paying for things you don't want.

      OpenSSH works fine on Linux or other flavors of Unix and could easily stand alone as it's own product with it's own management team. You might even get a corporate sponsor like IBM or Sun to 'adopt' the project.

      It works fine on Linux and other platforms because it is written very well and can be easily ported. What do you think will happen to OpenSSH if it ends up in the hands of separate management, and god forbid, separate developers? Have you seen the mess that is SunSSH?

      The bottom line is that OpenBSD has clever and dedicated internal developers writing very good code. Some of the good code they write is OpenSSH, which you can support by supporting its developers. Whether or not those developers work on other things is completely irrelevant. Either reward the developers or don't.

      --

      *blinking cursor*

    8. Re:Fork it! by Just+Some+Guy · · Score: 1
      We don't use OpenBSD

      Yes, you do. If you use any software that ships in the OpenBSD base installation, such as:

      • X.Org
      • Gcc
      • Perl
      • Apache, mod_ssl, DSO support
      • OpenSSL
      • Groff
      • Sendmail
      • Bind
      • Lynx
      • Sudo
      • Ncurses
      • KAME IPv6
      • Heimdal
      • Arla
      • Binutils
      • Gdb

      then you're using software audited and patched by OpenBSD.

      --
      Dewey, what part of this looks like authorities should be involved?
    9. Re:Fork it! by Shanep · · Score: 1

      Then people wonder why de Raadt behaves the way he does. When I read this post, my first reaction was to send you to hell with enough bad language to put you in a first class seat. Maybe that's why de Raadt gets his stigma, by not taking a pause from his first reaction.

      So you want to know that the money you give would go directly to support OpenSSH? According to de Raadt, there are six developers that focus on OpenSSH. These developers also work on other aspects of OpenBSD. What exactly do you want them to do? Divide your money between the six of them according to how many hours each works on OpenSSH? Do you want them to have separate network connections and hardware, and pay for it with your donation? How do you compensate the other OpenBSD developers when their ideas and contributions inevitably end up in the OpenSSH codebase?

      The OpenBSD developers are a group of people working together. OpenSSH is the fruit of their work. The way to contribute directly to OpenSSH is to contribute funds to its developers. That's exactly what contributing to OpenBSD does, because the developers of OpenBSD and the developers of OpenSSH are one and the same.

      So contrary to your second sentence, you have every interest in supporting OpenBSD. Saying otherwise is a disingenuous and pathetic attempt at justifying your reluctance to reward the people whose work you claim to respect.


      It's posts like these which make me realise that scoring between -1 and 5 is not enough. Because a post like this is so much more insightful than most other "Score:5 Insightful" posts that it should be held out on it's own for hitting the mark so very well. I wish I had mod points and could take back everything I've said under this story, just to give this one post one more Insightful point, so that it has a better chance of being noticed and considered.

      --
      War crimes, torture, lies, illegal spying... Would someone give Bush a blowjob, already, so he can be impeached?
    10. Re:Fork it! by justins · · Score: 1
      Our company would be more inclined to donate if we knew that the money we gave would go directly to support OpenSSH. We have no interest in supporting OpenBSD. Fork OpenSSH into it's own project with separate financing and management, and we'll send you some money.

      Right. That would be really meaningful, what with OpenBSD and OpenSSH being the same people and all.
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
  67. Absolutely by theolein · · Score: 4, Funny

    This whole Slashdot anti-Theo movement is lame

    I agree wholeheartedly.

    -Theo

  68. Why single out Sun??? by Temkin · · Score: 1



    I'm not sure why he's singling out Sun here. I bet he hasn't sent Sun a donation for continued NFS development. In case he hasn't noticed Scott McNealy isn't swimming in a vault like Scrooge McDuck these days. Sun is loosing money. It has been loosing money for years. If an employee asks a 1st level manager at Sun to pony up some travel money, the answer is "no". According to insiders I know, it's been that way for years. They're in business to make money, and they're aggressively managing their expenses. If you ask an upper level manager for some travel money, and then publicly kick them in the balls... I'm guessing even tactless Theo can guess what the answer is!!

    Theo's personallity defects are coming home to roost... His project is having financial problems because he doesn't have the people skills to succeed. It should serve as a lesson to other coders. Coding skill only gets you so far. Spend some time at a Toastmaster's. Learn to analyze the motivations of others without tainting them with your own desires/wishes/motivations. Sadly... This is where most coders fail.

    1. Re:Why single out Sun??? by Anonymous Coward · · Score: 0

      He's lying. Sun has donated servers to the project!

      Basically, he is just yelling at Sun for the publicity.

  69. people splitting hairs by Danathar · · Score: 1

    I've read a bunch of posts talking bout the BSD license and debating the finer points of ethics and morality and what people are required to do vs what they should do.

    Well..

    I'll throw in my 2 cents (and another 10 bucks to OpenSSH).

    Contributing some $$$ to a good cause like the work that the OpenBSD and OpenSSH organization does just seems like the right thing to do. I'd hope that other people feel the same. If not, then it's a shame (my opinion of course)

  70. Is it bad business sense if it's done anyhow? by Chemisor · · Score: 1, Insightful

    > For a business that uses OpenBSD code, it would just make good business sense to
    > support the project at a fraction of what it would cost to develop the same code
    > in-house.

    I disagree. If the company pays the OpenBSD team, the code gets written, but if it does not pay, the code still gets written. As long as the OpenBSD team is writing code without requiring payment, it makes far more sense for the company to not pay. After all, what's the point? Only in the free software world is there that "giving back" mentality. In the business world, nobody pays for what they already get free.

    Now, if OpenBSD team stopped development due to financial difficulties, would it make sense for a business to pay them to resume? Perhaps. But a typical manager would make a different choice; he would hire in-house programmers to fork the project and continue development without sharing the source. A good manager does not give away what he dearly paid for.

    > It is ridiculous that Sun wouldn't even cover the travel expenses
    > of an OpenBSD developer to go their conference

    Why would Sun want to go out of their way to have a competitor come to their conference?

    1. Re:Is it bad business sense if it's done anyhow? by Trelane · · Score: 2, Insightful
      If the company pays the OpenBSD team, the code gets written, but if it does not pay, the code still gets written.
      Excellent point, although not quite completely true:
      As long as the OpenBSD team is writing code without requiring payment, it makes far more sense for the company to not pay.
      By short-term metrics, this is certainly true. However, your above statement isn't 100% correct. So long as someone (or a group of someones) is supporting the development, the code will get written. As (I believe) you've said before, programmers gotta eat. So they will first seek subsistance (their job), and once that's been satisfied, they'll be coding for their own use and for the greater good. Maslow's hierarchy of needs and all that.

      So while it makes sense on the short-term microeconomic level to not pay anything to a project you use, it makes no sense on the long-term macroeconomic level--just as a single family saving money is a wise investment, all families saving money is a recession.

      The optimal solution here is for users to pay some money to projects they wish to use. This is a modest, compromise amount, causing the greatest good in the short- and long-terms, and in the micro- and macroeconomics.

      Sadly, it seems that the corporate world (and most of the average user world too) is only too happy to sacrifice long-term gain for short-term gain. So conventional modern business practices would likely be in agreement with your statement.

      --

      --
      Given enough personal experience, all stereotypes are shallow.
    2. Re:Is it bad business sense if it's done anyhow? by Chemisor · · Score: 1

      > So long as someone (or a group of someones) is supporting the development, the code will get written.

      But that someone does not have to be you, does it? As long as there are enough suckers willing to pay, there is no need for you to do so.

      > The optimal solution here is for users to pay some money to projects they wish to use.

      No; the optimal solution here is to wait until the programmers just start to starve from lack of money, and only then to give them any. And then, only enough to keep them alive. They would be grateful enough no matter how much you give them. This way you would expend the minimum amount of your own money for maximum effect, while having bled to the bone all those suckers who kept paying for nothing.

      > This is a modest, compromise amount, causing the greatest good in the short- and long-terms

      You are still in the free software mode of thought. In my mind, no good ever comes from giving charity, and I would not consider it good to sponsor a project that is being given away for free. (And no, I would not beg people for money for my own free projects either) The greatest good you can do is justice, which is to trade value for equal value. By setting the software's price at zero, they have declared it worthless, and by not paying them I am simply fulfilling our contract. Remember, the price of the seller's wares is determined by his estimation of their worth, not mine. My own estimation simply determines whether he makes the sale or not, and just as I would not insist on paying more for my groceries when hungry, I would consider it fair and just to pay the seller the price he is asking. Neither would I consider myself under any further obligation. The free software fanatics are under the delusion that I would accept their implicit open-ended contract that states that I am required to pay for their software with some unspecified (read "unlimited") amount of work for done them. A businessman scorns implicit contracts, and will equally scorn any idea of obligation after a transaction is complete, seeing it as only fair and just. Likewise, I would never help any free software projects because of some obligation I feel toward "the community". If I do help someone, it will be on my own initiative, for fun or out of curiousity, and I would be most vehement in disabusing any free software communists of the idea that I would even consider following their vile implicit open-ended service contract.

      > Sadly, it seems that the corporate world (and most of the average user world too)
      > is only too happy to sacrifice long-term gain for short-term gain.

      You should consider that it may be because they are right. Communism always dies in the long run. It died in the Soviet Union, and it will die in the free software world even faster since, as is frequently bemoaned, there is no way to force people to write software for nothing. Slavery can not exist without the slavedriver's whip and, while the communist state can employ force to keep people in line, the free software fanatics can only whine, and without much effect.

    3. Re:Is it bad business sense if it's done anyhow? by Trelane · · Score: 1
      But that someone does not have to be you, does it? As long as there are enough suckers willing to pay, there is no need for you to do so.
      Quite right. This is true of a great many things. You have the ability to not pay, but I'd argue that it's not a wise tack to take.

      It's also apparent that we have radically different definitions of "sucker".

      No; the optimal solution here is to wait until the programmers just start to starve from lack of money, and only then to give them any.
      Then we disagree. To me, this is a distinctly suboptimal solution.
      This way you would expend the minimum amount of your own money for maximum effect, while having bled to the bone all those suckers who kept paying for nothing.
      This is quite true in the short-term, microeconomic picture. It fails utterly in the macroeconomic picture.

      Also, paying for software is not paying for "nothing."

      The greatest good you can do is justice, which is to trade value for equal value.
      You have a weird definition of "justice".
      By setting the software's price at zero, they have declared it worthless, and by not paying them I am simply fulfilling our contract.
      No; this is not at all correct. Price != value. They are certainly correlated, but not isomorphic.

      Love is free; is it worthless? You even have to put forth effort to keep it going!

      Now it's becoming clear: you warp the definitions so that you can feel good (or, at least, not bad) about your actions. You're "merely"

      My own estimation simply determines whether he makes the sale or not, and just as I would not insist on paying more for my groceries when hungry, I would consider it fair and just to pay the seller the price he is asking. Neither would I consider myself under any further obligation.
      Would you pay more to a local store if they were going out of business? How about if they're your friend?
      The free software fanatics are under the delusion that I would accept their implicit open-ended contract that states that I am required to pay for their software with some unspecified (read "unlimited") amount of work for done them.
      No; there is no contract. That's precisely the point. Nothing is required . If you can't pay; that's fine. If you can pay, it would be a good idea to, so that the software can continue to be developed. Yes, you have the option of not paying, but by not doing so, you prevent further development--your piece of the support framework is missing, and others must make up for it or else development stops.
      Communism always dies in the long run.
      Whoa, doggies!

      Where did communism sneak in here?! At best, you miiight have been able to argue implicit socialism (which I'd argue that it's not). Price is only a piece of capitalism, as evidenced by boycotts of various things for various reasons. Else all is nothing more than a race to the bottom.

      Slavery can not exist without the slavedriver's whip and, while the communist state can employ force to keep people in line, the free software fanatics can only whine, and without much effect.
      Wow. That really sums up your post neatly. Making unwarranted assumptions and then tilting at those windmills with full force.
      --

      --
      Given enough personal experience, all stereotypes are shallow.
    4. Re:Is it bad business sense if it's done anyhow? by Chemisor · · Score: 1

      > Quite right. This is true of a great many things. You have the ability to not pay,
      > but I'd argue that it's not a wise tack to take.

      I have not yet heard your argument. All I have heard is the statement that "it is not a wise tack to take". How about explaining why you think so?

      > It's also apparent that we have radically different definitions of "sucker".

      sucker = "a person easily cheated or taken in; dupe; simpleton" (Webster's; #4 among other meanings irrelevant in this context) Since when you pay for things you already get free you give something for nothing, I would fit that under the category of being cheated. You might argue that the giving was in the spirit of charity, in which case I would simply change my evaluation to "simpleton", since most people who give charity have not thought hard enough about its consequences nor its message.

      > Also, paying for software is not paying for "nothing."

      Let me rephrase that: "paying for free software is paying for nothing". If you still have difficulty understanding this, compare the situation when you have paid with the situation where you have not. In either case, you have the software, so clearly you are not paying for it. You may be paying for something else, the community goodwill, the developer's friendship, or whatever else you want to acquire, but it certainly is not the software itself.

      > To me, this is a distinctly suboptimal solution.

      Depends on what you are trying to optimize, does it not? I am optimizing for value accrued to me, and after seeing that, my rationale should become chrystal clear. You probably will say that it is a bad goal, but that is a different debate.

      > You have a weird definition of "justice".

      I use it because it fits. If you know a better word, feel free to suggest it. Yes, to some degree I do

      > warp the definitions

      but it I do so for utility rather than deception. I am more than happy to define my terms. Words are, after all, only a tool of communication; as long as both parties can agree on a definition, communication takes place. You might object to me calling it justice, so feel free to substitute it with sdfouiythhh and apply my definition to it. The important part is that I consider it to be the supreme moral good.

      > you warp the definitions so that you can feel good (or, at least, not bad) about your actions

      It matters little what words you use to describe your actions. It is the meaning that matters, and the meaning is very clear to me. I feel good about my actions because I know they are right, no matter how you define the words used to describe it. Even if you force me to describe them as "vile and despicable", doing so would merely change the meaning of those words in my mind to mean the good things I intend to say. Language is a tool of communication. The words matter little; their meaning is the only thing that matters.

      > No; this is not at all correct. Price != value. They are certainly correlated, but not isomorphic.

      Very well; I'll rephrase: price is the declared value. Declared by the seller as the value he wants to receive for his item in a fair trade. If the buyer disagrees, bargaining begins until a compromise can be reached in valuation. Remember that value is specific to the valuer, and therefore differs from person to person; there is no such thing as an absolute value of a thing. Every time you ask after a value of a thing, you must also ask "to whom, and for what?"

      > Love is free; is it worthless? You even have to put forth effort to keep it going!

      You have just answered your own question. Love is most definitely not free. It is given for a reason, and what you get, you pay for dearly, in like coin. You might not explicitly list "you owe me $100 worth of kisses", but in that situation you would certainly be thinking something vaguely like it. Love is about fairness too; if you give more love than you get back, after a time you would be left feeling resen

  71. Flexible ethics by Syberghost · · Score: 0, Flamebait

    He accuses Linux developers of having "much more flexibility to their belief systems than I have", but then goes on to make an exception to their core belief regarding Full Disclosure for Sun, because they pissed him off.

    They don't call him Theo The Rat just because it's an obvious pun.

    1. Re:Flexible ethics by Anonymous Coward · · Score: 0

      You're an idiot. He's not saying that things will not be fully disclosed. He's just saying that Sun will not recieve any special or prior notification. FreeBSD, NetBSD, and the Linux distros, yes, will get some warning and time to make patches. Sun can read about it when everyone else does.

      What's funny about the anti-Theo hate-on everyone seems to be rolling in today:
          - the criticism of him for pissing DARPA off by stating his principles and his belief that the US is wrong in Iraq, basically saying he should be more opportunistic;
          - the attacks when it appears that he is being opportunistic.

      Actually, he's usually quite consistent. (But of course, not completely, as humans aren't).

      What's rather disgusting about it is all the anti-Theo from people who not only have never met him, but have never been even subject to a flame from him.
      In my view, if you've been flamed, or had a good argument with him, you're entitled. Otherwise you're entitled to disapprove, dislike, want to avoid, but you're not entitled to spread crap. Especially with all the half-truths, partial readings, and even down-right calumny in many of these posts.

    2. Re:Flexible ethics by Syberghost · · Score: 1

      He's not saying that things will not be fully disclosed. He's just saying that Sun will not recieve any special or prior notification. FreeBSD, NetBSD, and the Linux distros, yes, will get some warning and time to make patches. Sun can read about it when everyone else does.

      Here's the quote that shows you're wrong:

      "Or maybe that has happened already."

      There's no such thing as "secret" notification to the Linux distros. They deal with things via an open process. Further, Sun is a huge client of RedHat and SuSE, would would inform them IMMEDIATELY if they did get "secret" notification. In order to actually make this happen, he'd have to leave all the Linux distros in the cold, too.

      And since he's suggesting this has already happened, and the Linux distros haven't been notified, there you have it.

    3. Re:Flexible ethics by Anonymous Coward · · Score: 0

      Actually there are warnings. Perhaps I misremember, but I recall that the last big SSH bugs, the security contacts and core members of various groups were notified in advance. Full disclosure does not mean instantaneous disclosure. Yes, eventually it is all open, but responsible people try to lessen the impact. Giving distros a window in which to prepare and patch is responsible.

      Perhaps though, bugs have been patched, and picked up by the various Linux distros, but not by Sun's lagging implementation? Or perhaps it's a vague threat from an irritated person, to get them thinking, or as FUD (depending on your view).

    4. Re:Flexible ethics by Syberghost · · Score: 1

      Giving distros a window in which to prepare and patch is responsible.

      Yes, it is. And refusing to give a very popular OS that same window is, conversely, irresponsible. Even assuming that's what Theo meant.

      Companies like Fedex and UPS rely on Sun software for projects that, among other things, make sure terrorists aren't sending bombs to schools. That's what Theo is impacting when he refuses to disclose information.

    5. Re:Flexible ethics by Anonymous Coward · · Score: 0

      That's what Theo is impacting when he refuses to disclose information.

      Well, first of all, *if* he refuses to disclose information.

      Second, I'm quite sure the information will be disclosed; just, as mentioned above, perhaps not early. You're sliding the case again from "late disclosure" to "non-disclosure". Perhaps because of your rather emotional (to judge by the "rat" comment) Theo hate-on. Absolute worst case: the changes *will* make it into the source tree.

      Third: bomb-detection machines? WTF? People using those network those to the outside? Anyone who connects a control system network to larger networks is just asking for it. (And I know it happens all the time. I tell people not to do it all the time.) If you've got something critical and you're just relying on just SSH (from any source) for the security, you're f**ked. Firewall and IPSec would be a minimal starting point. (I sure hope they do a lot more to those machines, considering the state of the default Solaris install!)

      Humm, maybe put an OpenBSD FW and IPSec box in front of them :-)

    6. Re:Flexible ethics by Syberghost · · Score: 1

      You're sliding the case again from "late disclosure" to "non-disclosure".

      Yes, based on evidence that I cited and explained. He either meant non-disclosure or the whole thing was BS posturing.

      Third: bomb-detection machines? WTF?

      No.

  72. Re:Iff..... by ebvwfbw · · Score: 0, Flamebait
    BSD /is/ Unix, not Unix-like.

    No, BSD is a Unix hybrid much like Linux is. BSD started life out as SYS V and then many people feel they messed it up. Some say they greatly improved it. The point is, it has moved far enough I don't consider it to be Unix anymore. Certainly Open BSD, that isn't Unix by definition. That is the FREE things Berkeley did and they rewrote all the stuff that USL owned. I remember it, 43 3.5" disks as I recall. Linux took SYSV standards, BSD, merged them intellegently. That is why it is very popular. I remember the 1980s when we had the SYS V - BSD wars. It was sort of like getting avid war demonstrators and avid anti-war demonstrators in the same room. The BSD project brought us a lot of good things - like Sockets, IPC and other things. It is just the base OS, where they put things were.... well different. People didn't want to look all over tim-buk-too to find a freaking config or binary file. Used to drive me crazy. People picked one - SYS V and called it a day. The unfortunate thing is I see this BS starting up all over again with Linux. Stuff in different places. Wars over distros - Suse/RedHat/(other).

    My advice to the BSD crowd was to simply admit they are beating a dead horse and migrate to Linux like the rest of us did over a decade ago. There is no shame in it. We have a bigger sandbox, more toys and more people to play with. Their sandbox is old, has scat in it and nobody wants to play over there any more. Bring their toys over and enjoy. Otherwise they face having their sandbox taken away from them entirely. Bankruptcy.

    The security issue is funny too. I remember them saying in 1999 that they were so secure, couldn't be broken into because of their code reviews and such. I said they were delusional. They said I was crazy. The next three months the exploits for Linux were ported to BSD. So much for code review and "security".

    The unfortunate part is I think it will get ugly from here. Some very good researchers and coders may decide to simply stop coding all together.

  73. no worries.... by quetzalco · · Score: 1

    if OpenBSD will close, someone else will continue working on OpenSSH. Deja vou. I don't believe those people who says that a 900Kbyte software can be worked only by those people. It's just a project like anyone else, even if it's a project about security. You probably remember Helix/Eazel/Ximian/Nautilus. Well, Nautilus is not like openssh, but perhaps there have been more complicated software that have been continued by other teams. Let's think to Netscape DS, a huge and complete software, worked now by Sun/RedHat/HP and whoever is still alive and better then never. Genius don't work only for BSD or Netscape...

  74. Jerry A. Taylor, call Theo today! by NXIL · · Score: 3, Insightful

    Jerry A. Taylor
    City Manager
    Tuttle, OK

    Dear Jerry,

    you like secure operating systems. So does Theo de Raadt: he loves them!

    Please contact Theo directly at *deraadt@cvs.openbsd.org*

    Be firm: Theo will help you, but only if you are make it clear that you expect help, and you want it now. (I think that when you contacted CentOS's team, you were sort of beating around the bush. That won't work with the OpenBSD team. Be direct!)

    Theo will respect your 22 years of IT experience. And, I think he will be impressed that you worked at Raytheon--wow!

    No need to call the FBI to get a response from Theo and his boyz. Enjoy!

    --A concerned citizen

  75. Always happy to feed a troll by Anonymous Coward · · Score: 0

    This isn't bait & switch, as people got the very product they were promised. At worst, it would be "fill and bill," which is to say OpenBSD provided OpenSSH for the order & then started charging people after the fact.

    But really: they're begging, not billing. Asking for donations is not a scam.

  76. Re:This is a money debate, not chiefly about licen by Tweekster · · Score: 1

    It is all tied up in the license, if you do not ask for money upfront, you cant complain later that no one paid up.

    should some of these companies pay, definately. Should Theo be mad that people are following the license (ie, you dont HAVE to pay)

    You give something away for free, then later complain they should pay for it...I dont think so

    --
    The phrase "more better" is acceptable English. suck it grammar Nazis
  77. Re:Iff..... by Anonymous Coward · · Score: 0

    "Linux puts stress on keeping up with the bleeding edge, lots of features and broader hardware support. Linux does everything from supporting the latest graphics and video cards to supporting dozens of CPUs on enterprise hardware. If you want enhanced security on Linux, go for SELinux or GRSecurity."

    ...Or you could just load Solaris 10 x86/x64, lock the mofo down in less than 10 minutes (actually more like five, but I'm being conservative), add your preconfigured IPFilter ruleset package, and plough on without having your head hurt from Linux.

    Oh, no wait! That would actually mean that it's easier / safer to deploy Solaris than Linux, and of course WE CAN'T HAVE SOMEONE ELSE BE BETTER THAN LINUX DISTROS ON slashdot.org.

    Never mind.

  78. It's hard for a company to support OpenBSD by Ritchie70 · · Score: 2, Interesting
    In a company of any size, there are a million checks and balances before money gets sent out.

    To donate to OpenBSD you write a check to Theo. There's no OpenBSD foundation, no non-profit, nothing. So I'm supposed to go to my boss, who has to explain it to his, who has to explain it to his, to get a check cut to some guy in Canada because he does good stuff? I might be able to get a CD on the corporate AmEx, but a donation of any real size? No way!

    If Theo wants money, Theo needs to set up a non-profit, preferably US-based, get tax exempt status, and see what happens. It isn't nearly as hard, complicated, or expensive as he thinks.

    --
    The preferred solution is to not have a problem.
    1. Re:It's hard for a company to support OpenBSD by Triumph+The+Insult+C · · Score: 1

      you must not have read the article. he comments on that directly

      --
      vodka, straight up, thank you!
    2. Re:It's hard for a company to support OpenBSD by Anonymous Coward · · Score: 0

      No, he does not comment on this topic for squat. He basically side steps the whole issue with major handwaving. Theo needs to just bite the bullet and setup a non-profit. If it's expensive (it isn't), then he should start taking donations for the purpose of setting up the non-profit! This will get him some real traction.

      I dunno, he just does not want to do this it seems. Teenage angst?

    3. Re:It's hard for a company to support OpenBSD by Ritchie70 · · Score: 1
      Actually, I did RTFA. He whines that it's too hard and not worthwhile, as I recall. He's wrong.

      Companies don't just give money to people because they do good things. That isn't how it works most places.

      --
      The preferred solution is to not have a problem.
    4. Re:It's hard for a company to support OpenBSD by Triumph+The+Insult+C · · Score: 1

      We have investigated becoming a non-profit organization, but the margins and savings really do not make sense for our project, especially since most of our donations do not come from the country where we operate. Also, there are numerous other constraints and rules.

      that's not commenting on the issue?

      but, then again, you probably don't run an organization the size of openbsd, or more importantly, that operates like openbsd, but you do know that it wouldn't be expensive (i am assuming you are talking just $$, not time, labor, or distraction from developing openbsd)?

      --
      vodka, straight up, thank you!
    5. Re:It's hard for a company to support OpenBSD by Anonymous Coward · · Score: 0

      Well, if you're gonna keep bitching about how hard it is to open a non-profit (it is NOT!), then stop bitching about how you're not getting any money!! WTF, you expect companies to write checks out to your personal name?! Have you no clue what so ever?!

    6. Re:It's hard for a company to support OpenBSD by Anonymous Coward · · Score: 1, Interesting

      Why does it have to be US-based? Are you so xenophobic that you won't send money to CANADA? Thats pretty lame.

    7. Re:It's hard for a company to support OpenBSD by Anonymous Coward · · Score: 0
      I'm gussing you come from a smaller company than Sun. Frankly I think they'd be happy if you just bought a handful CDs. If every company using OpenBSD bought a few CDs of each release, I think they'd easily make the money they need to keep the servers running and buy some plane tickets to hackathons.

      The problem is lots of companies aren't doing that, but are keeping their FTP server busy.

    8. Re:It's hard for a company to support OpenBSD by Anonymous Coward · · Score: 0

      Sure, setting up an NPO is difficult. That's why SPI, Apache, and Collab (and probably others) have "incubators" so that projects can take advantage of NPO fundraising without needing to spend $3000 and hundreds of hours to get it set up.

      I would happily cough up $$ to support OpenSSH/BSD. I certainly use SSH enough. But I can't make a donation to OpenSSH, only to Theo. All of the money goes into his personal bank account.

      That may be good enough for collecting $10 and $20 donations from fellow geeks, but it's futile to even ask for corporate support under those conditions. If Theo really wants to raise $100,000, then get a darned NPO attorney and set up a fund. Otherwise, the project isn't serious and doesn't deserve the money.

    9. Re:It's hard for a company to support OpenBSD by Ritchie70 · · Score: 1

      I said US-based because I assumed that would make it easier (possible?) to achieve 501(c)(3) status, which means the donation is tax deductible in the US, and there are probably more US companies than Canadian companies that would/could/should donate.

      --
      The preferred solution is to not have a problem.
    10. Re:It's hard for a company to support OpenBSD by Ritchie70 · · Score: 1
      Nope, not even close.

      It's been a joke around my department that we should just buy SCO rather than keep buying licenses from them, especially once they lose the IBM lawsuit.

      As I recall, our total revenue was around $20,000,000,000 last year.

      --
      The preferred solution is to not have a problem.
    11. Re:It's hard for a company to support OpenBSD by Ritchie70 · · Score: 1
      I don't really know what it means, "an organization the size of openbsd" or "that operates like openbsd." As far as I can tell, it's a benign dictatorship with Theo running the show.

      I ran a company with 15 employees and 1.25 million in annual sales for around 5 years.

      I currently work for a 20-billion dollar company as part of a team that deploys software routinely to 13,000 remote locations in the course of a few months. I think I know a little about organizations.

      I've seen my mother run a NPO in her spare time (which isn't very spare) with a little help from some undermotivated volunteers.

      WTF is the big deal? If Theo wants $100,000 Theo is going to have to jump thru some hoops. It's either IRS hoops or DARPA hoops or someone else's hoops, but there's going to be hoops, because I seriously doubt he's going to make it a geek at a time.

      Either that or someone else needs to jump thru the hoops for him. Are there any volunteers here to set up a US-based OpenBSD Foundation?

      --
      The preferred solution is to not have a problem.
  79. BSD vs GPL vs LGPL by molarmass192 · · Score: 1

    The thing to me that most sucks was that Stallman and the BSD folks basically made a bet on human nature. The optomists are losing badly.

    Sad but true, that's why my preferred license is the LGPL, it's a decent combination of both worlds. You want to incorporate my work unmodified? Fine, nobody loses, the source is still "out there". You want to modify my code and redistribute it? Well, either release those changes or pay me to relicense my code. BSD and GPL are both extremes. With BSD, expect the worst, people will use your work and flip you the bird. With the GPL, expect the worst, people will shun your code if they're forced to open code they want to keep closed. Don't get me wrong, BSD and GPL are both morally superior to the LGPL, but based on human nature, the LGPL offers a good compromise between encouraging use and forcing retribution.

    --

    Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
  80. Re:License choices by woah · · Score: 1

    Not necessarily. Theo just has a crap business model. Red Hat and the like seem to be doing fine.

  81. Go Theo Go! by Anonymous Coward · · Score: 0

    Well said, sir. Please, send this guy a donation, or submit some code. How about some corporate guys step up to the plate, eh? Personally, I can't think of a more deserving technical cause or a more ethical OS. AFAIAC, people like Linus & Theo demonstrate real humanity and real commitment. Would I trust these guys? Hell, yah. Do I trust corporations? Never! Why would I want to deal with greedy unethical companies when I could support and be part of an environment with integrity.

    Thanks again Theo, I for one, greatly appreciate the good work.

  82. Re:Iff..... by Anonymous Coward · · Score: 0

    You are wrong and right at the same time.

    No we won't come over. The linux sandbox is full of crap and has a crowd that is incompatible with OpenBSDs. There is a fundamental difference between the development cycles. I'd prefer to eat shit than code for Linux. I can promise you that sentiment is true for many developers.

    The good news is that there is plenty of room for all of us. Linux does its thing, OpenBSD does its thing etc etc. Great, go at it!

  83. Let's be Objective about this, was Re:Hmm... by bourne · · Score: 3, Insightful
    Bravo; you've made the most secure operating system available today. But, then, you have this firmly held belief that the rest of the world owes you something? That you're gracing the rest of the world with your glorious presence and regal software? That attitude is not welcome here.

    Actually, no, he's not claiming that the world owes him something. He's claiming that his act of creation and contribution does not cause him (well, specifically, the OpenSSH developers) to be owe anything further to the people who take advantage of their contribution.

    That is an entirely different issue.

    "From the beginning of history, the two antagonists have stood face to face: the creator and the second-hander. When the first creator invented the wheel, the first second-hander responded. He invented altruism.

    "The creator - denied, opposed, persecuted, exploited - went on, moved forward and carried all humanity along on his energy. The second-hander contributed nothing to the process except the impediments. The contest has another name: the individual against the collective." - Howard Roark in The Fountainhead by Ayn Rand.

    1. Re:Let's be Objective about this, was Re:Hmm... by coolGuyZak · · Score: 2, Funny
      From the beginning of history, the two antagonists have stood face to face: the creator and the second-hander. When the first creator invented the wheel, the first second-hander responded. He invented altruism.
      At least the first second-hander was still being original--before that, theft didn't exist. What we really should be careful of are those second second-handers.
  84. better idea by Triumph+The+Insult+C · · Score: 1

    donate the $49 and do an ftp install. if you really want 3.9 right now, grab it from CVS and do a make release

    --
    vodka, straight up, thank you!
  85. Business-friendly by Tony · · Score: 1

    GPL is not business friendly.

    True, that. Double-true.

    The BSD license is business-friendly. But apparently, business is not BSD-friendly.

    The GPL was born of the realisation that, without encouragement, businesses will simply take, and not give anything back. Theo is just learning this, it seems.

    --
    Microsoft is to software what Budweiser is to beer.
    1. Re:Business-friendly by Anonymous Coward · · Score: 0

      There are companies in that do give back to communiteies. Some are good citizens like that. Theo is just pointing out the ones who aren't.

    2. Re:Business-friendly by Anonymous Coward · · Score: 0

      There is a saying the baby has to cry for the mother to generate milk.

      Just looking at the sky till somebody put some food in the mouth is not enough, you have to make an effort. Must promote it, must forge business partnerships, must have an infrastructure for people to contribute, that is like a proper charity, must have an official address, bank account preferably in an internationally known bank, board of directors, annual audits and reports, etc.

      People needs to know what happens to their donations. They need to feel the confidence that their donations are not gone into some individuals pockets.

      What you need is a business acumen and professional approach to run as a successful charity. Open your eyes and see how charities raise millions of dollars. Most of these people are just programmers and have no idea about business or professional expertise in fund raising. That's why their projects fail. Begging is definitely not the way. What is your strategy to attract donations?

      One suggestion drop that FREE from your openBSD.org website. If you are rich enough to give things free, don't expect anything in return, not even in next birth :)

      Who are the people behind this? Where are their photos and credentials? Are they respectable people or set of crooks?

      Drop your FTP offerings, turn to BitTorrent. Its only rich companies use FTP.

      Where is the official address in your website? Do you issue a receipt for tax deductions?

      Think like this. It looks like you guys need a big infrastructural change before collecting money. Nobody wants dump their hard earned money into an abyss. Earning money by working is lot easier than earning money by running a business.

      Rather than fighting individually, merge all BSDs together and make a super BSD.

  86. Right. by Tony · · Score: 1

    Prove it.

    If that were the case, *BSD operating systems would be bigger than Linux. Since that's not the case, your argument is a non-starter, at best mere speculation; at worst, self-delusion.

    --
    Microsoft is to software what Budweiser is to beer.
    1. Re:Right. by nacturation · · Score: 1

      The grandparent was mentioning companies which use OpenSSH. The proper comparison, then, is operating systems that have incorporated BSD code vs. operating systems which have incorporated Linux code. From that perspective, Windows and OS X have both used BSD code more than they've used Linux code. And given that those are the most popular operating systems today, I'd say your argument is the one lacking.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  87. I think you are way behind the times. by assantisz · · Score: 1

    Pretty much everything around the UltraSPARC processors is out and in the open.

  88. Re:Iff..... by Anonymous Coward · · Score: 0

    " If you didn't know what BSD is... until now..."

    Glad to see you finally crawled out from under your rock.

  89. Facts about OpenBSD by Anonymous Coward · · Score: 0
    It is now official. Netcraft confirms: *BSD is dying

    One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

    You don't need to be the Amazing Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.

    FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, OpenBSD is dead.

    Fact: *BSD is dying

  90. Re:Anti-Theo sentiments are muddying the point her by GreyWolf3000 · · Score: 1

    His request is very reasonable - everyone is benefitting, and those who are in a position to give a little back should do so.

    RMS would agree...which is why the GPL mandates making changes public.

    For all that BSD'ers criticize the GPL for not being 'truly free,' it is of particular interest to everyone to note Theo de Raadt's irritation concerning having his code used for commercial ventures without contributing the changes back.

    It's like..um..dude.....the whole GPL vs. BSD license debate.

    --
    Slashdot: Where people pretend to be twice as smart as they really are by behaving like children.
  91. Theo makes an interesting point by J.R.+Random · · Score: 1
    TdR: We are having more success getting documentation, but I am not sure if it is due in any way to our user base size. Part of it might be that many more products are coming from Asia (where business sense still applies -- the customer gets the documentation he wants). I think that the Asian businesses are just being smarter about this. When it comes to documentation requests, an Asian company that says no is rare. An American company that says yes is rare.

    It looks like the Asian companies are run by engineers and the American companies are run by lawyers. No wonder our trade deficit is out of control.

  92. Please be more original. by Homestar+Breadmaker · · Score: 1

    Eventually, even the dumbest loonix users will figure it out if you just keep repeating the same old crap. If you keep your BSD is dying trolls original and unique, then they will think its true and keep using loonix. Please do your part to keep brain damaged loonix users off the BSD lists, thanks!

    1. Re:Please be more original. by RedHatLinux · · Score: 1

      Ha Ha, I use windows 98se, not Linux.

  93. Re:Iff..... by Anonymous Coward · · Score: 0

    You want to know how Unix-like it is? Well maybe you should read the following link so that you know the history of BSD. It should answer your question quite well.

    http://www.oreilly.com/catalog/opensources/book/ki rkmck.html

  94. sow. reap. repeat. by nazarijo · · Score: 1

    as someone who a) used to run an openbsd site (deadly.org) for years, b) written a book on openbsd (secure architectures ...) c) used openbsd for five years d) had commit access and e) was kicked out (for shutting down deadly.org), i've seen theo and the rest of the project up close and personal. my subject line says it all: you reap what you sow.

    theo's constantly been adversarial, even to his supporters, and no one likes that. shitting on your enemies is one thing, shitting on people who are trying to be friends is another. while theo's not the sum and substance of the project, he's a) it's more forefront spokesman and b) reflecting poorly on the project and c) responsible for driving away many talented developers over the years. the project is suffering for this.

    pounding adaptec, sun, and many other vendors publicly and privately just gets you only so far in a positive direction, but a lot further in a negative direction. anyone who has watched openbsd over the years knows what i'm talking about.

    while i see openbsd suffering financially and lots of people using the code without contributing anything substantial back, the license allows this (and even encourages this) and the project itself has really suffered for theo's mistakes in the past. don't like it? change the license to force people to contribute money or code or something.

    example: the company i work for implemented TCP MD5 and agreed to share it with the project. it took a while to clear management, but eventually it did. harassing emails (from theo) for weeks on end were unwelcome and no way to say "thanks" for what is a donation. this is typical theo. openbsd project members work here and contribute fixes we find to the project, and i think we all expect that will continue.

    if this is how the project reacts to people trying to help, why should anyone bother?

    1. Re:sow. reap. repeat. by Anonymous Coward · · Score: 0

      As someone who a) has run OpenBSD since 2.3, b) read deadly.org even before you got involved, c) bought your book "Secure Architecures" and d) bought plenty of CDs/made donations/bought shirts let me say a couple of things:

      -Thanks so much for your work, on undeadly, and in the book and in the source.
      -It's too bad shutting down deadly.org happened so quickly, an unexpected announcement on April 1st, what did you expect, thanks for the slap?
      -Your viewpoint has credence, due to your association with the project, unlike the majority of pundits here.
      -I continue to buy/use OpenBSD because it is the best. While I don't agree with the way Theo stirs up things, his software works, and that is what counts at the end of the day.

      I'll next be contributing to OpenSSH because I use it every, every day.
      (oh, by the way, I once posted something on misc@ and Theo wrote me a gentle rebuke privately because I didn't understand the question. My personal experience was different than yours.)

  95. Well then, if they don't like the license ... by Tetard · · Score: 1

    ... maybe they should make a new project for a new license ?
    After OpenCVS, OpenBGPD, OpenSSH, maybe we get (drumroll...)
    OpenLicense ? It would be, like, this really totally cool
    concept, like, you know, you could reuse all the code you want,
    but - and this is the really cool bit - you'd have to - get ready! -
    GIVE BACK the changes to the community if you redistributed the binaries!
    Wouldn't that be cool ? And you could, you know, make a manifesto or
    something, and - now this is really catchy - call it the BPL! YEAH!
    The BSD Public License!! And you could start all kinds of really gnarly
    software projects under that license!
    And Theo wouldn't even have to grow a long beard, wear a toga and go around with an old hard disk platter on his head -- cause it wouldn't be like this would be about calling to people's moral obligation to share software, cause, you know, software should be free, no, this would be to finance OpenBSD! W00t!

  96. Re:Iff..... by Anonymous Coward · · Score: 0

    Dood, you're on crack.

    You seriously need to read the following link:

    http://www.oreilly.com/catalog/opensources/book/ki rkmck.html

    There you will learn that BSD did NOT come from SYS V, but from an earlier version of AT&T Unix. Also, with Linux you might have a bigger sandbox, but what good is it when it's full of shit and kids that are constantly pissing in it? Also, what good is it to have 100 different sandboxes especially when it contains the same shitty, pissed on sand. ;)

    As far as security goes, we both know that software is written by humans that are prone to error. Errors happen, but I'd take fewer errors over a multitude of errors anyday. With OpenBSD at least you know there are fewer errors and at least they try to reduce the amount of errors.

    OpenBSD is well engineered. The system feels solid and stable. The security and networking tools are available. The documentation is pretty decent as well. It's a pretty good tool whether you have a webserver, edge router, firewall, or even workstation.

  97. ditch OpenBSD, just focus on OpenSSH by v3xt0r · · Score: 0

    I don't mean to hate on the OpenBSD Project, I just don't use it as an OS.

    OpenSSH however, is a great application, and is far more widely used than OpenBSD.

    If they want to minimize their development efforts, I suggest they simply move away from OpenBSD. I know this will be a great loss for those who actually use it (most of them are die-hard openbsd fans, and will be pretty pissed).

    If you want to develop free software, you have to expect that people will want to use it for free.

    --
    the only permanence in existence, is the impermanence of existence.
  98. OT: Your sig by Just+Some+Guy · · Score: 1
    Be a patriot: Murder a Republican.

    You immediately lose all credibility, regardless of topic, when you advocate violence against people you disagree with. Did you think everyone would say, "gee, what an enlightened, thoughtful person - I wonder what else he'll have to say?" Do you think you're doing non-Republicans a favor by confirming Republicans' suspicions that you and your co-believers are nuts?

    On behalf of everyone who isn't in your club: screw you and grow up.

    --
    Dewey, what part of this looks like authorities should be involved?
    1. Re:OT: Your sig by Anonymous Coward · · Score: 0

      You immediately lose all credibility, regardless of topic, when you advocate violence against people you disagree with.

      So, um, that would apply to George Bush too, right?

    2. Re:OT: Your sig by Perky_Goth · · Score: 1

      you know, the sig is at the END of a post for a reason.
      if it was in the begining, it would still be like descriminating someone because he is/isn't a geek. hogwash.

  99. Bad manners are unjustified. by jbn-o · · Score: 1

    Clearly you have much to learn about being nice and putting things in perspective; how little it would have cost Sun, for instance, to do as the OpenSSH developers twice asked versus how selfish, greedy, and thankless it makes Sun look today. Another reminder of how big businesses should not be conflated with individuals in any sense.

    Or perhaps you're really affirming power like a sycophant; you wish to continue to wield the power of thanklessness over those that choose to license under non-copylefted free software and open source licenses. You see a chance to justify using their works as you see fit by giving us an overly expansive interpretation of licensing, as if licensing covers everything. Saying thank you isn't a part of any license, nor could you enforce such a clause. But it sure looks bad when you don't thank anyone who helped you like Sun isn't thanking the OpenSSH developers.

    1. Re:Bad manners are unjustified. by Tweekster · · Score: 1

      or maybe the problem is of attitude. You seem to share a similar attitude as Theo. Which basically makes me not want to help out. I know if I was in a position at Sun and was flamed like theo has a habit of, well I would tell him thanks for the code, now kiss off. if you are a jerk to people, no one will want to help you. You ever notice how a lot of other projects ask for donations and it is fulfilled rathr quickly. gee I wonder if it is the developers attitudes that make a difference there.

      --
      The phrase "more better" is acceptable English. suck it grammar Nazis
    2. Re:Bad manners are unjustified. by jbn-o · · Score: 1

      No, it's not flaming, it's fact-based observation. Accurate, on-point criticism shouldn't be waved away as "flaming" no matter how uncomfortable it makes your greedy friends at Sun feel.

      And no, I have not noticed "how a lot of other projects ask for donations and it is fulfilled rathr[sic] quickly". I will look forward to your information showing a high number of projects getting donations rather quickly. To be even more on-topic, it would help if you could pick examples where businesses are donating, because de Raadt said that all of the OpenSSH donations to date were from individuals.

    3. Re:Bad manners are unjustified. by turbidostato · · Score: 1

      "...versus how selfish, greedy, and thankless it makes Sun look today"

      To whom? I don't think Sun owes nothing to de Raadt; still they owe fidelity to their shareholders. Maybe the shareholders rest better knowing that Sun doesn't spend money where not strictly needed.

      "You see a chance to justify using their works as you see fit by giving us an overly expansive interpretation of licensing"

      What the hell!!!??? The BSD license is *pristine*. There's really no place for "expansive interpretation". Not at all!

      What Sun did is a *direct* result of the license choosen. I remember something said here at Slashdot about what was the "inner philosophy" of open source for begginners. It was three points:
      *You can do it yourself, or
      *You can pay other to do it for you, if you can't/don't want

      *...But if you won't do it yourself nor will pay others to do the job, just take what you can for free and, please, shut up.

      I can only think it is the best concise explanation about what open source is and is not.

      But then, it work both ways: if you want to release your work under an open source license, think about it cautiously, and do it if you really want to. But, please, don't cry about how the bad guys have taken advantage about what it is explicitly stated within your choosen license: you will only look like a consented child or, directly, like a moron.

    4. Re:Bad manners are unjustified. by jbn-o · · Score: 1

      It's not a question of Sun owing OpenSSH developers anything, nor did I say it was. Please read what I wrote, not what you'd like me to have said instead.

      Everyone agrees that Sun may build on OpenSSH code, even to make a proprietary derivative, that was never in question. The question is not legalistic and trying to frame everything in terms of who owes what to whom means you're missing out on a lot of what people do in polite society. The issue has to do with giving thanks and recognizing what made Sun's OpenSSH-based project work, particularly when giving thanks costs Sun so little. These are factors contained in no license. Nobody is saying OpenSSH has been taken advantage of. They chose their license carefully, cognizant of the consequences a non-copylefted free software license carries. One ought not forget to acknowledge the assistance of those who helped one get where they are.

      It's a shame Sun behaves the way they choose to do, de Raadt put his finger right on it. And we can remember how Sun treats the OpenSSH team (and their own customers, since Sun distributes a proprietary derivative) when we decide whether we want to place our trust in a black box controlled by ungrateful people. Since other wealthy organizations also failed to help out, we can apply the same logic to them too (hence, it's worth keeping IBM, Red Hat, Apple, HP, and others in mind).

      Your understanding of what "open source" means is also remarkably incorrect as that movement has more to do with programmatic convenience than you describe.

    5. Re:Bad manners are unjustified. by turbidostato · · Score: 1

      "you're missing out on a lot of what people do in polite society"

      You said it: "people" and "polite society". Last time I checked, Sun was not "people", nor current occidental society was a polite one.

      So, yes, you are saying that Sun owes something indeed, if only it is not written down on a contract. Now: surprise, surprise, companies have nothing to refer to but contracts, and companies are anything but polite human beings.

      But that's obvious and disregarding such big hard facts aren't going to make you look like a clever guy.

      "Your understanding of what "open source" means is also remarkably incorrect as that movement has more to do with programmatic convenience than you describe."

      If you re-read what I wrote, you will see I say nothing about what open source migth mean for open source *developers*: it is what open source *is* for *users*. And it can seem or mean for them whatever you want, but *is*, down to the facts, exactly what I said: do it yourself; or pay others to do it (not in every case *money* payment is needed); or please shut up, since gruntling to the one that gave something for free is not the clever way to take from him something else.

  100. Grow up! by phliar · · Score: 2, Insightful
    Jesus Christ, all this TdR flaming is getting ridiculous. His philosophy is clear: he cares about the code, and only about the code; he's not interested in marketing or market share or advocacy. He's a smart guy who doesn't suffer fools gladly, and the Internet makes it possible for every fool to contact him. Small wonder the fools think he's an asshole. (The pity of it is: he really is a pretty nice guy who even has interests other than OpenBSD.)

    Since it's obvious that many here haven't actually read what they're flaming about, here's the last question of that interview:

    NF: Lots of hardware vendors use OpenSSH. Have you got anything back from them?

    TdR: If I add up everything we have ever gotten in exchange for our efforts with OpenSSH, it might amount to $1,000. This all came from individuals. For our work on OpenSSH, companies using OpenSSH have never given us a cent. What about companies that incorporate OpenSSH directly into their products, saving themselves millions of dollars? Companies such as Cisco, Sun, SGI, HP, IBM, Siemens, a raft of medium-sized firewall companies -- we have not received a cent. Or from Linux vendors? Not a cent.

    Of course we did not set out to create OpenSSH for the money -- we purposely made it completely free so that the "telnet infrastructure" of the 1980s would die. But it sure is sad that none of these companies return even a fraction of value in kind.

    If you want to judge any entity particularly harshly, judge Sun. Yearly they hold interoperability events, for NFS and other protocols, and they include SSH implementation tests as well. Twice we asked them to cover the travel and accommodation costs for a developer to come to their event, and they refused. Considering that their SunSSH is directly based on our code, that is just flat out insulting. Shame on you Sun, shame, shame, shame.

    I will say it here -- if an OpenSSH hole is found that applies to SunSSH, Sun will not be informed. Or maybe that has happened already.

    Sounds completely reasonable -- just calling a spade a spade and not trying to sugar coat anything.
    --
    Unlimited growth == Cancer.
    1. Re:Grow up! by micromuncher · · Score: 1
      From the quote I get the following

      Sun doesn't want to pay for me to come and play. Why don't they worship me? Wah wah wah wah.


      There is no good reason for any company to treat a competitor to a vacation, is there?
      --
      /\/\icro/\/\uncher
    2. Re:Grow up! by Anonymous Coward · · Score: 0

      He's out of line; Sun has donated hardware to the project.

  101. No surprises here. by jbn-o · · Score: 1

    I'm not surprised, I understand that the OpenSSH license allows this to happen. I'd go further than what you say: multinational corporations have long proven their greed knows no bounds and they've done so in far more important situations than this. But this is not a licensing concern. At this scale of importance it's more an issue of manners, how people and organizations ought to behave in polite society. I think people are expressing disappointment that Sun has repeatedly turned down easy opportunities to be friendly with people who have helped them; the amount of money it would have cost Sun to do the nice thing here is many orders of magnitude less than the amount of money made from building on and commercially distributing OpenSSH.

    Sun isn't the only organization in this position either, this isn't a bad apple situation. This is part of a pattern of big business policy decisions to behave in this fashion. Big businesses have a chance to look like they aren't rapaciously greedy. They're choosing to throw that chance away (for widely understood reasons which many protest daily in anti-corporate movements around the world) and it's our job to make sure these businesses know that we won't forget the choices they have made.

    1. Re:No surprises here. by Schraegstrichpunkt · · Score: 1
      . . . it's our job to make sure these businesses know that we won't forget the choices they have made.

      But we will forget.

  102. Letter to Theo by Anonymous Coward · · Score: 0

    Dear Theo,
    My name is Mr.$$$$ I would happily donate to you- but I think you forgot somethings: NGO status. A foundation. A business plan. These to my untrained mined are seemingly fundimental steps to live. Do you have a NGO I'd I can use as an excuse to get a tax cut, cause god damn getting reamed for being rich is no fun.

  103. Correct Topics by Bleeblah · · Score: 1

    Actually, what is on-topic depends on the specific flavor of BSD being discussed.

    If FreeBSD then post a "FreeBSD is dying" troll.

    If NetBSD then post a "does it run on a toaster" joke

    If OpenBSD then post about Theo being an asshole.

  104. Re:Iff..... by Theatetus · · Score: 1

    No, I meant "felicitous", as I wrote

    --
    All's true that is mistrusted
  105. The natural effect of using BSD-style licenses? by Anonymous Coward · · Score: 0

    For projects that choose a BSD-style permissive license for a software project, the priority is to have the software used as widely as possible, period.

    For projects that choose a GPL-style license, the priority is to ensure that people can't take from the community without giving something back.

    It's puzzling how people who choose a BSD-style license can be baffled by companies taking from them without giving anything back in return. That's what the license is geared for; that's what it encourages. Companies have incentive to take from the community, but there's no incentive for them to contribute something back.

    In a sense, BSD-style licenses encourage software to thrive at the expense of the community, while GPL-style licenses encourage communities to thrive at the expense of the software (limiting the usage of the software).

    In a tiebreaker, I'd favor GPL-style licenses for the simple reason that software doesn't build communities, communities build software.

    If communities are encouraged, sustainable software will naturally follow. But if software is encouraged at the expense of communities, there's no mechanism for sustaining either the software or the community that created it.

    In general, I'm interested in learning what helps to encourage sustainable communities.

    -Flash

  106. Every /.er send the man a buck. by dxminxs · · Score: 0

    ...and the project will be ok, for awhile.

  107. Re:Anti-Theo sentiments are muddying the point her by TheRaven64 · · Score: 1
    Writing an SSH implementation is easy.

    Subjecting an SSH implementation to the same level of auditing as OpenSSH has had and building it up to the same level of confidence is much harder.

    --
    I am TheRaven on Soylent News
  108. Re:That wasn't even written by Theo by Senzei · · Score: 1
    Some of the OpenSSH freeloaders, like Apple Computer and The SCO Group, are notorious for reaping financial rewards from selling open source software bundled with their proprietary products.

    that was written by Jem Matzan, not Theo. Learn to read.

    Even if the community would have found another SSH solution, is it really too much to say thank you about it? What about not being popular as a personality makes Theo's work not useful to the community? OpenSSH is a useful tool. Theo is just trying to point out that, as citizen of the open source world, a lot of big names are taking and not giving. Yes, it is their right, no, they are not obliged to help out in any way whatsoever, but it still is a crap way to treat the people around you.

    --
    Slashdot: Where anecdotes and generalizations can be freely substituted for facts, logic, or intelligence
  109. Fork it yourself by Anonymous Coward · · Score: 0

    Really. Anyone who's using OpenSSH and *not* OpenBSD doesn't really need Theo's team at all. You have all the code.

    The real problem is that OpenSSH is a de-facto standard, much like the mp3 format. So by creating your own fork, you're going to depart from what the rest of the world is using.

    Solution? Just do nothing for now. OpenSSH will continue along as it always has. And if/when OpenBSD dies, someone else will continue work on the OpenSSH code when it becomes neccessary.

    I see no reason to send Theo money out of the goodness of my heart, considering his boorish behavior and general abrasiveness. Apparently many companies feel the same way.

    1. Re:Fork it yourself by Shanep · · Score: 1

      Really. Anyone who's using OpenSSH and *not* OpenBSD doesn't really need Theo's team at all. You have all the code.

      And then watch that fork get a bad reputation because of all the new bugs and security issues which crop up because few people have a really good understanding of crypto and security implications. People will ignore the fork. Sun Microsystems know how to code, right? They've got the coders and they've got money to pay them. Yet they have messed up SunSSH, a fork of OpenSSH, royally.

      Solution? Just do nothing for now.

      Wow, how very enlightening. This is so very pro OSS!

      The people who brought us OpenSSH, people who matter, did not "just do nothing". If everyone outside of corporations "just did nothing", then we would all still be using Windows or MacOS 9 (or a lesser OSX).

      People who do nothing, don't matter. You, don't matter. So why should anyone listen to such crap that you spew?

      --
      War crimes, torture, lies, illegal spying... Would someone give Bush a blowjob, already, so he can be impeached?
    2. Re:Fork it yourself by Anonymous Coward · · Score: 0

      Wow someone wake up on the wrong side of the bed? The whole point flew about a mile over your head.

      Quick summary:

      Theo is abrasive.
      People don't want to help Theo.
      Theo whines about no money to continue work on OpenSSH.
      Yet Theo continues work on OpenSSH.
      People say "ok...".

      Let's face it, there is *no* reason to pay this retard a cent. Nor is there any reason to work on OpenSSH separately while his team still maintains it. When it stops being maintained, someone else will pick it up (corporate or otherwise). Theo knows this means he would lose control of the project AND get no money. By whining while not actually discontinuing work, he hopes to get some donations.

      You are incredibly egotistical if you think that no one in the world is capable of maintaining that code. In fact, if that's true, it says far more about the substandard quality of the code than anything else.

      Your whole rant about "people who matter" is meaningless. The OpenBSD team is not special any more than any other group of coders out there. SSH (the protocol, not the commercial product) matters. OpenSSH is merely filling a void. If it wasn't there, or if it went away, the need still exists, and people would do something about it.

  110. No, it's not about BSD vs GPL licensing by bgalbrecht · · Score: 1

    No, BSD vs GPL licensing has nothing to do with this. Theo's irritation is that OpenBSD is having financial problems, and nobody using applications original from the OpenBSD code base, like pf and OpenSSH, is stepping up to the plate and paying OpenBSD's bills. If OpenBSD had been developed entirely under the GPL, OpenBSD could still be having financial problems, because a commercial application using GPL'd code is under no obligation to pay a portion of their proceeds to the developers of the GPL'd code.

    Other BSD licensed open source projects, like Apache and FreeBSD are doing much better financially because they have large corporations using their products who are willing to contribute money and/or services like web hosting in addition developer time. So OpenBSD's real problem is that either they haven't found a corporate sugar daddy, or Theo's managed to sabotage any deals that might have happened in the past.

  111. moral issue by Anonymous Coward · · Score: 0

    I'm really shocked about the lack of moral ethics people are displaying here. All this: "Theo stop whining, you should have used the GPL, why should Sun, Cisco ... pay?" is really just showing the lack of any moral values of these posters. Sure Sun et al are not required by law to pay anything to OpenBSD. Think about a say Salvation army kitchen giving out free dinner to poor people. Now you have some rich guy driving a big car coming in every day and getting a free dinner, without ever giving something back. Is he doing something illegal? No, but is behavior is still morally wrong. The people at the shelter might not legally prevent him from coming they would however be right to tell him that he really should be giving something back, and maybe even to make the thing public. This is exactly the same issue with Theo saying shame on Sun. I'm sure he is well aware of the implications of choosing the BSD license, however I totally agree with him pointing out that Sun and others are freeloading.

  112. The Obvious Direction for OpenBSD - Users by Anonymous Coward · · Score: 0

    Posting AC to focus on the issue, not personalities or toot my horn.

    I guess it is obvious, but lets state the facts:

    The funding model that OpenBSD has been using for the life of the project has worked well, but not perfectly for the last two years.

    CD Sales are down, but FTP uploads are up.

    Plenty of posts here of OpenSSH users willing to contribute only to OpenSSH

    Big Corporations take the code, make money, give nothing back, have done so for the last 5 years. No change expected there.

    For OpenBSD to generate a $100k revenue stream, it is going to take three things.

    Those that want to should purchase CDs,
    Those that FTP the software shoudl be prodded (nicely) to donate.
    Take OpenSSH donations, sell "I support OpenSSH" shirts to the masses.
    Ask for donations, but don't expect much from the big greedy corporations.

    That is it. Don't waste time or energy on the big corporations, work on making your users happy.

    If you run the numbers, OpenBSD could do fine with 3000 to 4000 CD sales each release or spectacularly with 5000 CDs sold each release. What's so hard about that? Are there 1000 users who can get their company to buy 5 copies each release? Seems likely to me.

    Now since you want to know if I have put my money where my mouth is, I have had our office get at least 5 CDs each release for the last 14 releases, and bought shirts, made a personal donation.

    Here is a quote: OpenBSD continues because of user support, and the Internet is better for it.

    Make it so.

  113. Re:Anti-Theo sentiments are muddying the point her by LurkerXXX · · Score: 1
    GPL is the answer to it eh?

    They wants donations so that he can fly his develops to hackathons to make more code. Do you think putting it under a GPL license would fix the problem by forcing the companies to donate money? Nope.

    Instead I'm sure you think the companies will do the coding in place of the known good developers and then the project would get the code (of unknown quality) that way.

    The company 'might' give code changes back.

    *IF* they made any changes to it.

    *IF* they were distributing the software.

    And *IF* they were sure they would get caught if they didn't. (lots of companies have broken the GPL until sued or threatened to be sued)

    It's like.. um .. dude.. nothing at all to do with the whole GPL vs BSD license debate.

    It's reminding folks that if they find some open source software useful, it would be a nice thing if they contributed back a tiny fraction of the benifit that they recieve from it in some way. The GPL doesn't stop someone from using it a ton with no payback as long as they aren't changing and redistributing it.

  114. Actually... by Svartalf · · Score: 1

    I wouldn't bill per hour on this- in reality, I'd contribute to an OpenSSH project (Never mind that they work on OpenBSD as well- what they do so long as they support OpenSSH is none of my business...kind of like my GPL/LGPL based projects versus work...) if they got a salary and _supported_ OpenSSH proper. If it doesn't need much work, that's fine, they still get the salary and support- because they were there when they're really needed.

    Sure, donating to OpenBSD's analogous- but with all the off pronouncements from Theo over time has soured that idea in many people's minds, myself included. It's a tough sell right now.

    And Theo's current screed that we're discussing makes it just that much harder- the companies he's commenting about are perfectly within their rights per the license the stuff's under and all. Sun's just taken the team's offer up and privitized the codebase- per the license they chose to put the codebase under. Sorry, can't feel sorry about any of the team in that regard. Same goes for anything else, including IBM sending people their way for support (They didn't write it, the OpenBSD team did...)- they could have said, "Hey, want priority support from us? Donate to the project...", but apparently it occurs to Theo that complaining about it all and doing nothing about it himself directly will get better results.

    Honestly. Change the tone and tune and you might be surprised. I'm sure Theo would get better traction for things if he wasn't QUITE so abrasive. Stallman's almost as bad as Theo in this regard. Both of them would get better results if they weren't QUITE so adversarial about things.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  115. Obligations ... by Joseph_Daniel_Zukige · · Score: 1

    Obligations are ultimately not between man and man, but between man and God.

    But that does not mean that the shirking of an obligation causes no one problems.

    I don't know Theo's thoughts. I don't know God's thoughts in this matter. Maybe openbsd has filled its purpose and it's time to move on.

    But maybe there is nothing wrong with Theo pointing out that, should a changing of the guard be forced before its time, those who have been making money from the obsd team's largess will find themselves severely inconvenienced.

    And, yeah, the bad karma is exactly the point. Maybe it's a little awkward for the warning to come from Theo, but some people need to be warned they are breeding a wart on their own noses, erm, generating bad karma for themselves.

  116. ror

  117. Badly Squeeezing for Dollars :) by Anonymous Coward · · Score: 0

    !!!

    I have posted that in another thread but, here I go:

    BSD

    Bad Sofware Developpers

    Badly Squeeezing for Dollars :)

    Sorry, I could not help it!

    or

    Beware! Some Despicable

    BaStarDs sons of UNIX

    Begging for Some Dollars!

    --

    This one was bad at all neither !

    ---

    Yep... it's true... No exuse!

    Only perhaps these:

    - Montepulziano d'Abruzzio " Denominazione d'Origine Contallata", La Rinalda 2004 - 1 Bottle

    - Vitoria "Gran Reserva" 1997, Valdepenas, denominacion de Origen, Tempranillo - 2 Bottles

    - Cotes du Rhone 2004, Denomination d'origine - 2 Bottles

    - some still to come...

    that we are finishing here !!!

    It is being a great night here! We have also been trying the DesktopBSD 1.0 distro. Pretty good actually... Not all the good stuff is Linux...

    !!!

  118. Follow Wikipedia's lead by Raenex · · Score: 1
    He acknowledges that not only was there no obligation for these companies to donate money, but that OpenSSH wasn't created to make money. I don't think it is unreasonable for him to ask for money, particularly when he has pointed out that some of the vendors selected OpenSSH after they were quoted high fees (multi-millions of USD) from the commercial SSH vendor.

    It's all in the attitude and presentation to the public. He certainly acts like there is a moral obligation for companies to give him money. It's also not clear where all the money will go to. Checks are to be made to Theo personally. I can't tell, is there a charitable organization behind OpenBSD? If so, then they need to run it like one. If not, then Theo has no right to act like one.

    Now compare this to Wikipedia. There's none of this "you owe us" business. There's a very transparent budget and list of contributions. And there's a non-profit organization behind it all.

  119. Ultrasparc by grahamsz · · Score: 1

    Hmmm yeah the ultrasparc hdl has that pesky Gnu Public License.

    http://opensparc-t1.sunsource.net/download_hw.html

  120. Re:Iff..... by ebvwfbw · · Score: 1
    No we won't come over.

    You may not have much of a choice soon. Unless you want to be like the people still trying to keep BeOS going.

    The linux sandbox is full of crap and has a crowd that is incompatible with OpenBSDs.

    Why do you say this? What make you think it is full of crap? Linux runs the biggest machines in the world, some of the most important networks and business systems. I have coded for both and I can tell you OpenBSD is NOT that far from Linux. Indeed, look at the little differences between the BSD version of openssh and the portable version.

    The ONLY reason I switched from BSD to Linux all of those years ago was that Linux was leaving BSD behind. That is true today.

  121. Re:Iff..... by ebvwfbw · · Score: 1
    There you will learn that BSD did NOT come from SYS V, but from an earlier version of AT&T Unix.

    If you read what I wrote you would see I mentioned that it is the earlier version plus the socket, semphore and other stuff that we know as SYS V today. My original statement is still true and you don't dispute it, OpenBSD is NOT Unix.

    with Linux you might have a bigger sandbox, but what good is it when it's full of shit and kids that are constantly pissing in it? Also, what good is it to have 100 different sandboxes especially when it contains the same shitty, pissed on sand. ;)

    Like sounding like an idiot I see. Everyone knows there is only ONE linux, not 100. Controlled by one guy - Linus Torvolds. There are different distros however. The base is the same. You also confused BSD with Linux, BSD is the sand that is pissed on and shitty. Linux's sand has been cleaned and sifted through the efforts of people around the world. You know, once we got rid of the shitty pissed on BSD code. BSD's code is so bad that even Microsoft had to abandon it and re-write their TCP/IP stack that they ripped off. That was reported on /. years ago.

    OpenBSD is well engineered.

    Your the one on crack. As I mentioned, Linux exploits have been ported to BSD and work just fine. There is NOTHING superior to BSD. I find it comical that you even try to explain the security problems away as human error, then say it is superior engineering. Make up your mind first.

    I loaded OpenBSD's latest version about 2 months ago just to see if it had come forward any. I had a tough time getting it in the first place and then I saw no reason to keep it. It still sucks. It is like your trying to say horse and buggy is better than a car. Go ahead, keep your horse and buggy.