Linux For Losers According To De Raadt
elohim writes "Theo has some scathing comments about Linux in his new interview with Forbes Magazine. From the article: 'It's terrible...Everyone is using it, and they don't realize how bad it is. And the Linux people will just stick with it and add to it rather than stepping back and saying, "This is garbage and we should fix it."'"
"Linux For Losers According To De Raadt"
Nowhere in that article does he say "Linux is for losers" or use that label. The headline of the story rhetorically asks that question, way to generate flamebait, Forbes & Slashdot editors!
Now I'm going to get a coffee and enjoy the comments which will probably not differ much from "Theo is teh ghey! L12nux r00lzzzzzz!!!"
Trolling is a art,
You mean for once I am not a loser? I never thought I'd see the day when running Windows was... cool.
Help Brendan pay off his student loans
From the article:
Torvalds, via e-mail, says De Raadt is "difficult" and declined to comment further.
I must say, Linus really comes across as a classy, quality person. It takes mature restraint to deal with "difficult" people like Theo, and Linus does so with class.
-5 Flamebait
Talk about throwing gasoline on the fire...why would DeRaat say such hateful things?
From TFA:
Ahh.
Here's another quote from TFA:
Apparently, you also do what you do because you hate Linux...
Don't be hatin'...
____
~ |rip/\/\aster /\/\onkey
Theo De Raadt Abrasive and Opinionated! Film at 11
The funny thing is he has never run Linux. Quoting this interview:
Theo de Raadt: I don't know. I have never run Linux.
#!/
I'd be angry too. About how the Forbes article portrayed me as a raving lunatic out for blood, after giving what was probably a thoughtful interview.
All the article consisted of was trotting Theo out for choice quotes about how Linux sucks, and a tiny bit of BSD history. Only 2 out of the 16 paragraphs even started to cover *why* Theo thinks the way he does. The rest is tabloid-style trash-talk and what seems to be an ADD-inspired history lesson. There's nothing approaching a coherent argument.
I'm giving Theo the benefit of the doubt on this one- he probably gave a fleshed-out argument then Forbes eviscerated it. Even if that's not the case, they should have written a better article. This is awfully shitty journalism.
In a NewsForge interview a couple of days ago de Raadt was asked about technical comparisons between Linux and BSD and replied, "I don't know. I have never run Linux."
? tid=152&tid=8&tid=2
http://os.newsforge.com/os/05/06/09/2132233.shtml
Suddenly, he's an expert on how bad Linux is?
Theo is openbsd's greatest strength (a fanatical security coder) and their worst handicap (a PR nightmare)
"Weapons should be hardy rather than decorative" - Miyamoto Musashi
I think that goes for OS's too
Dan's Resume
I think the coverage for the BSDs is great. Really. I think it will help them in the corporate mindset. But, Dan Lyons, the person who has the byline, really should have had someone technical proofread his article. Only three open source BSDs? When did Solaris switch back to using a BSD kernel? That last one is particularly embarrassing given the amount of coverage Sun is getting with the whole opensolaris thing.
Doing this on the older Sun hardware they claim to support is incredibly painful. Until Theo changes this one way or the other (preferably towards providing security patches in the same form as releases) I have to consider them a developer-only product, not a use-in-the-real-world one.
Oh yeah, and there's the wipe-and-reinstall mentality for each release too.
Ah, bitter dregs.
Sure, I'm not a linux or BSD guy. I run OS X, I'm out of all these loops. But get this quote:
I've tried never to say this on slashdot, but: LOL.
lorem ipsum, dolor sit amet
Remember folks, UNIX was fragmented and dying before Linux became mainstream. BSD and GNU were nothing but obscure academic projects. The popularity of Linux brought UNIX to a whole new generation of users, and BSD has benefited from the uprising as much as anyone. Even the big boys, like Solaris and AIX, are trying to be more like Linux.
And the whole quality thing is a myth. Linus approaches the kernel with the approach of an engineer, and the rest of Linux mirrors this approach. It doesn't have to be perfect, it just has to work. Theo thinks of himself as an artist, and his arrogance does as much to hurt BSD as it does to help it.
please.. it is really way too early for anyone to be taking my post seriously. I read tfa. I still stand by the well known fact that De Raadt has never used unix in his life.
1. /usr/local. Everything that you add afterwards goes in there. It's just extra to type. And is apache config in /usr/local/apache/conf or /usr/local/etc/apache/conf ?
/usr/local is exactly where additional software, not included in the base OS, should be installed. More typing?? For what? /usr/local should be in your path and manually going to this directory should be rare.
Maybe a more experience sys admin can chime in here, but
There are many reasons why one might _not_ want to use BSD, but this is the silliest yet!
And that's about as much sense as this conversation makes.
Luck favors the prepared, darling.
Ah, grasshopper... take a bath. Data hygiene is a good thing.
/usr/local, you can re-install the OS(e.g. partition corruption, junior admin fubar'ing, etc) without having to re-install your apps.
/usr/local , /opt is a good thing.
Funny, the default mixing of apps and OS in linux distros is what I dis-like the most about linux.
Keeping added apps seperate from the OS highlights the beauty of *nix over windows. With everything you installed after the OS in
Trust me, I've been there. Windows admin hoses OS, I re-install OS and I'm done. The needed apps are already in place & configured.
If the govt becomes a lawbreaker, it breeds contempt for law, it invites man to become his own law, it invites anarchy
Lok Technologies, a San Jose, Calif.-based maker of networking gear, started out using Linux in its equipment but switched to OpenBSD four years ago after company founder Simon Lok, who holds a doctorate in computer science, took a close look at the Linux source code.
"You know what I found? Right in the kernel, in the heart of the operating system, I found a developer's comment that said, 'Does this belong here?' "Lok says. "What kind of confidence does that inspire? Right then I knew it was time to switch."
So this guy switched from Linux to BSD not because he saw some poorly implemented code, but because of a comment?
That is absolutely insane.
All you touch and all you see is all your life will ever be
Simply put I think Forbes has a teensy little bias.
From the other Linux related stories box on the page:
Wind River Gets Smart
Peace, Love and Paychecks
Linux Scare Tactics
Kill Bill
Linux Loyalists Leery
Linux's Hit Men
IBM Refuses To Indemnify Linux Users
Red Hat's Mad Matt Vs. Humongous SCO Lawsuit
IBM Takes Linux To A New Level
Why You Won't Be Getting A Linux PC
The Limitations Of Linux
PeopleSoft Jumps On The Linux Train
The Cult Of Linux
Honestly, Forbes obviously is FUD central when it comes to Linux.
cat sig >
No matter what your endeavor is, blabbing about how bad your competitors are shows a lack of professionalism and class. If this is the prevailing mentality of the *BSD guys, I'll stick with Linux just BECAUSE they think it sucks.
"And now, Frank N. Furter, your time has come. Say 'goodbye' to all of this, and 'hello'... to oblivion!"
Disclaimer: I love Linux.
.com boom. We were in such a rush to get everything set up.. hurry hurry! we must get connected!!! hurry!..that we forgot about security. Now we're paying for that mistake, but it's quite interesting.
He has a point. We keep adding functionality and then we'll worry about going back and improving the code. Such is human nature however..
Look at the
But I think we should work in both directions. Old code, and new code. But who wants to fix someone else's code?
it seems that the interview itself is not linked :? tid=152&tid=8&tid=2
;)
http://os.newsforge.com/os/05/06/09/2132233.shtml
while reading it, it seems so strange how polite both linus (in previous interview) and Christos Zoulas (netbsd) can be - especially in contrast to raadt.
well, there are some poeple in companies that are never ever again allowed to speak publicly after a single sentence - not so if you own the company, i suppose
Rich
As I understand it: stuff you contribute to BSDs can be pirated by msft, and others, and put into their binary code.
The code is not pirated. The BSD license allows for distribution and modification of the code w/o the restrictions that the GPL places on code (namely that you must keep the code open).
OpenBSD's approach reminds me of "regular" CPU development, where all elements of the CPU have to just work. Linux's approach reminds me more of the new CPUs being worked on which are fault-tolerant, simply because there are many, average quality pieces in it, and the system as a whole can recover from some pieces failing.
I guess what I am saying is, what happens if a few of "Theo's 60" don't pull their weight anymore? What if some knock off? He has a problem. Linux does not have the same issues simply because there are so many people who are allowed to step in and fix things, even if they are not aces like "Theo's 60". I think in the long run, the Linux development model is better, and will enable Linux to survive long after the high-quality OpenBSD is dust.
BTW, I get to be the guy who coined the "Theo's 60" phrase ;)
naeem
This guy is one of the people behind Open BSD which wants to fill the gnu/linux niche and for various unfair ( and fair ) reasons missed the boat.
This is coming off as jealous in the article, like the girl ignored at the high school dance who decides to talk trash about the girl the guys are dancing with.
He comes off looking bad and were I involved with OpenBSD it would be my wish for him to stop talking as his behavior is a bad reflection on that good project.
He is acting like a child.
"GPL offers a little more protection"
What?? Mac OS X is one of the mose secure OS's around, and it wouldn't exist without FreeBSD and their associated BSD license. Now if everyone used Mac OS X, the computing world be much safer as a whole.
In fact, if you contribute code to BSD project and "msft, and other" use this code, that use is encouraged and not considered "pirated"!
What will Simon Lok do? He doesn't like what he finds buried in the Linux comments, so he switched to OpenBSD; will he now switch again because of Theo's public comments? Does Theo actually inspire confidence, that he is so angry all the time, and that he has time to spare to disparage the competition?
Sour grapes indeed.
Infuriate left and right
Of course it is... like FreeBSD, it's a core set of tools that are updated as a whole. And OpenBSD is even more focused, with less clutter than FreeBSD, which is already quite tight.
Of course it's more coherently engineered.. BSD is about updating a core set of libraries and tools. When we say "OpenBSD" we don't just mean a kernel.. we mean the entire package.. similar to if we say "Debian Linux".
Linux isn't "well architected" because there is no "Linux".. there is a kernel, developed by some people, and a bunch of tools and libraries develoepd by a bunch of different people, which are together rolled into distributions by yet OTHER people.
Is this the seafaring, raping, murdering pirate ?
Or the copyright infringement pirate ?
Or the license infringement pirate ?
You do realize that none of the above apply, right ?
If you contribute to a BSD under a BSD-style license then yes... others can use your code in their closed-source products.
Don't like it ? Don't release under that license.
As for the GPL.. crikey - which one ? which version ? There's too many of them out there already. You mean GPL 2.0, I take it - which doesn't stop a company from "pirating" your code by using it only internally on a webservice and just spitting out the results of the code. That's one of those things GPL 3.0 is supposed to address, I guess ? whatever
For the record, I agree with parent; /usr/local is a very good thing. Now, then. I'd just like to point out that the situation is worse in Windows. "But," you say, "Anything I install goes in C:\Program Files!" And this is true. Except for the configuration, which goes into The Registry (cue evil-sounding organ music). This here is probably the worst idea ever. "Hey, let's have a single place to throw all of the configuration data that needs to be completely parsed repeatedly (I.e., when right-clicking on the desktop), and have no simple, clean way to differentiate who owns what so that entries can be removed when the software is! GRRRRRRRRRRR-EAT!
We all know the guy is a bit off. Why is it that the Linux community can't listen to criticism, tho?
You talk about usability. The Linux people come out with "just because it isn't like Microsoft doesn't mean it's wrong."
The excuses are rampant in the Linux world. Do I use Linux? Sure. When I can get it running. Even modern distros are kludgey and clunky. Half the time the GUI does nothing but provide useless and cryptic error messages. I have a Win2k print server. I have tried (easily) a dozen distros to get things working. One will see the network. One won't without downgrading Samba. One will, but can't access anything. One sees everything and accesses everything but can't print. Sound is the same way. Some have issues with setting resolutions on the video side, others have other problems.
There are too many distros all in it for themselves. Even the ones that use one of the main distros as their base. Debian, Red Hat, what have you, all are kludgey and unrefined.
I want Linux to work. Desperately want it to get out there and do good. But it isn't going to, especially if every response to criticism is not "okay, let me see if I can work on that" and continues to be "Its better than Crapple and Microshit!"
No one wants another Microsoft Windows, but some friggin' usability isn't going to hurt your cause, and you may even be able to swing it without giving up your anti-Microsoft rhetoric. You can be different and still be intuitive and intelligent.
I started using FreeBSD three weeks ago on my desktop at work. Every day I use it I become more and more impressed by it, the integrated userland and kernel are like a breath of fresh air compared to linux. In fact, I'm having such a good experience with it, I already put it on a few sparc64 machines I'm setting up for an NSM platform. For anyone who's frustrated by the million linux distros and their slight incompatabilities, I'd suggest giving FreeBSD a try - it's really easy to get into, and you might just like it!
"What kind of music do pirates listen to?" -Paul Maud'dib
"Yeeeaaarrrrr n' Bee!!" -Stilgar, Leader of Sietch Tabr
...was who is this clown on Forbes bashing Linux? Then I saw it was an OpenBSD thing... and went, oh, nothing new there.
Then I felt dumb when I realized it was *the* OpenBSD guy. But I still didn't feel so bad.
The best part of the article was the mention of "In a sort of hacker equivalent of the Ford-versus-Chevy rivalry..." which is exactly what it boils down to.
So to add to the petty bickering, I've decided I like Linux more only because I've had more exposure to it, and I like the mascot more. Of course, here I was thinking it was the little Devil thing, but I guess thats just my confusion of the BSDs, eh?
FLR
Actually the worst part is that Theo is often right, which means you do have to actually listen to him rather than the easier just ignore him.
Reguardless of whether Theo is right or wrong he should not be such an asshat. Honestly have you ever dealt with the guy? If you don't see eye to eye with him he treats you like a giant turd. WTF? This is why it is good to have social skills and to know when to keep your mouth shut and when to open it. Theo from my experiance appears to have niether.
The title I submitted this with was "de Raadt Blasts Lunix in Forbes Interview"... Blame Zonk for the "Lunix For Losers" title.
"It's terrible," De Raadt says. "Everyone is using it, and they don't realize how bad it is. And the Linux people will just stick with it and add to it rather than stepping back and saying, 'This is garbage and we should fix it.'"
The bottom line is that it works better than commercial software. Anyone can look at the source code and see the comments, which are blunt about what needs fixing and how crappy the hardware is. Even commercial Linux rocks next to popular alternatives. For ease of installation, use, relative protection from mal and spyware, you can't beat a distribution like Mepis. Winners can step up to pure Debian, "losers" can fall all the way down to Caldera Open Linux and still do better than what 90% of the world uses.
There's also a difference in motivation. "Linux people do what they do because they hate Microsoft. We do what we do because we love Unix," De Raadt says. The irony, however, is that while noisy Linux fanatics make a great deal out of their hatred for Microsoft (nasdaq: MSFT - news - people ), De Raadt says their beloved program is starting to look a lot like what Microsoft puts out. "They have the same rapid development cycle, which leads to crap," he says.
That's what Micrososoft would have everyone believe, and so Microsoft is worth hating. People use Linux for freedom and the superior performance it brings. Study after study show this. Why people like Dan Lyons don't get it is beyond me, except that he might be a Fanboy.
Let's look back at other nasty junk he's written:
Dan Lyons, you are a shill. I dare you to make the entire tapes of your interview with Theo available. Anything less is second hand BS and the kind of thing the web makes obsolete.
DMCA, Hollings, Palladium. What might have sounded like paranoia is now common sense.
"You know what I found? Right in the kernel, in the heart of the operating system, I found a developer's comment that said, 'Does this belong here?' "Lok says. "What kind of confidence does that inspire? Right then I knew it was time to switch."
Damn. Somebody remove that comment.
Banu
The exception to this is on OpenBSD, where Apache is run from a chroot environment by default, and so everything related to Apache is in /var/www, which adds to security.
I personally prefer having interfaces named after the driver, because it makes it easier to identify a particular interface. On Linux, you have to read the dmesg output (or similar) to know whihc eth0 and eth1 are. With *BSD, I can tell that rl0 is the cheap RealTek card I bought to connect to the cable modem, while fxp0 is the Intel card that connects to the Internal network. I previously had to tweak something on a Linux gateway which sat between 4 networks, and I had no idea whether it was eth0, eth1, eth2, or eth3 that connected to the outside world. Of course, as others have mentioned, it is possible to change the names to more sensible ones.
I am TheRaven on Soylent News
Bravado is never being wrong, even when you'd say someone else was if it were anyone else but you. It's never bothering to be introspective, to question yourself or your actions.
Confidence is knowing you'll get there eventually, even if you aren't there yet. You're allowed to ask questions along the way like "Should this be here?".
I would much rather rely on software that is like the latter, than I would the former.
Besides, I bet Simon Lok maintains a few hundred windows machines too, but since he can't read those comments at all...
This would be like Bill Gates saying linux is for losers.
Let's face it, Raadt is pissed off that linux has supassed OpenBSD in terms of userbase. A little resentment? I think so.
If the developer isn't confident about even *where* some part of the code should be, and code from that confused developer actually made it into the kernel despite that confusion, why should a user have confidence in it?
A specific feature may be implemented in many ways. If there are several equivelent or nearly-equivelent ways, it makes sense to question your implementation decision. It does not necessarily imply the developer was unsure if "it" really belonged in that particular location; it is far more likely that the developer was unsure if there wasn't a better way of doing it that he was overlooking.
Sometimes writing code, something just doesn't feel right, even if you know your implementation is just fine. You have the feeling there's a better way. Usually, when you come back to it later, the better way is apperant. Often, the better way is simply cleaner code, not a better algorithm.
Comments like that are markers that welcome improvement, not an indication of lack of developer confidence.
Microsoft is to software what Budweiser is to beer.
If this were a windows fanboy thread, you'd have 20 dozen MCSE bootcamp graduates screaming that you should spend the next 6 months using regmon to figure out which keys are for the app, which aren't. You're also supposed to sacrifice a chicken or something during the folly.
Give me txt file configs any day of the week.
If Linux just "happens to run", how come it knocks out OpenBSD when it comes to performance? I very much doubt that Linux would win tests like these if "many parts" of its code were low quality and badly designed.
Granted, the test linked to above is soon two years old, and De Raadt refers to style of coding or general code quality rather than raw performance -- which other prominent people also have commented (in a perhaps more balanced way), but the fact that Linux runs is not merely a coincidence, as De Raadt seems to insinuate.
I think that points up one of the basic philosophical differences between the GPL crowd and the BSD crowd;
To me, the BSD position is more in line with natural selection; if you write better stuff, you win.
<disclaimer>
</disclaimer>
I want all of the power and none of the responsibility.
I can't tell if you're trolling or not.
"However, the difference with linux comes from the unified community behind it: Thousands of distros, hundreds of companies, one kernel."
Thousands of distros, all with their different quirks and slight incompatabilities. I wouldn't call that unified. In FreeBSD, the kernel is quite unified with the userland.
"Maybe its just my perseption but I don't see the same kind of unity from BSD"
From the FreeBSD Handbook: The goals of the FreeBSD Project are to provide software that may be used for any purpose and without strings attached...We believe that our first and foremost "mission" is to provide code to any and all comers, and for whatever purpose, so that the code gets the widest possible use and provides the widest possible benefit. This is, I believe, one of the most fundamental goals of Free Software and one that we enthusiastically support
That seems pretty focused to me, does Linux have a corresponding mission statement or focus?
"What kind of music do pirates listen to?" -Paul Maud'dib
"Yeeeaaarrrrr n' Bee!!" -Stilgar, Leader of Sietch Tabr
"I don't know. I've never used Linux"
It should also be noted that Torvalds isn't unduly harsh about Windows either. On a couple of occations he has claimed an apathetic view of Windows. Torvalds works on Linux because of Linux and not because of Windows.
Is this stuff really what TdR said or is it Forbes trying to generate click-through by scandal? I can let some of it slide but I would be worried if the leader of an OSS project has a lot of venom for another project. It clouds their decision making.
He blames Linux marketshare on the BSD lawsuit. I'm sorry, but in this case, he sounds foolish. The way BSD was developed and promoted a decade ago had far more to do with Linux' acceptance than the BSD lawsuit.
At the time, *very* few businesses used Linux. Well under 1%, probably more like 1% of 1% of 1%. At any rate, if you wanted to use a free *nix OS, you had three choices besides Linux:
1) Paying a commercial BSD license fee (BSDi). This was a bit expensive for an individual, and even the commercial version didn't have drivers for a lot of the better hardware (like reasonably new Dell servers).
2) Writing your own device drivers for anything unsupported.
3) Sending a BSD vendor equipment so they could write your driver.
I wish I could remember which prject was which for #2 and #3. Whichever group was #2, when I asked on the net about a SCSI driver for our server (a friend and I were starting a business on the side), I was flamed by a core BSD developer for not just writing a driver. HELLO! I need to run a business, not write drivers!
I tried really hard to make BSD work on our hardware. I finally gave up and tried Linux at another friend's suggestion. It just worked.
Linux caught on with individuals, then with startups and small projects in larger companies, and only in the past 3-4 years has started to matter in the corporate marketplace at large.
The BSD community chased people away (that's not an indictment of the community, it's just the effect of how things were handled).
There's an old adage that says, "Build a better mousetrap and the world will beat a path to your door." Even if that were still true (it's generally not), when you start beating them in the head with the mousetrap, don't complain when tehy don't buy it.
I'm not sure if Theo is merely ignorant of history, or is simply choosing to ignore it. Either way, he's in trouble. Those who ignore or forget the lessons of history are doomed to what? Repeat it. Theo's helping screw up BSD's chances all over again.
This could have been a very interesting article if a little detail was given concerning what issues he has with Linux.
Instead the article relies on vague opinions, sweeping accusations, a bit of bragging and a quote by a computer professor that he dropped Linux because of a single comment he saw in the code.
So much promise, too pathetic.
We need articles that can really generate interesting dialog and journalists that write better than Jerry Springer transcripts.
Theo does not take that path. He's a zealot... but he's not just a zealot. He's a clear-eyed, effective zealot who manages a solid project that produces the result he intends: a highly secure OS. If you'll recall from that other interview:Here we have a NetBSD guy saying, essentially, "I don't agree with Theo's approach, but it does work better than ours and we may all need to adopt it one day."
CZ is saying that Theo may be forging the path that many will need to follow before long. Theo was a security fanatic a long time ago, and I think events have proven that he made a good call on that. Events have yet to say if his abrasive approach to documentation will turn out to be a good call. CZ clearly recognizes that Theo may be ahead of the curve again, although it's too soon to say.
It seems to me that there exists a diversity of approaches to driving open-source and free software forward. At one extreme is Good Cop Linus, at the other is Bad Cop Theo, and everyone else is arrayed somewhere in the middle. A company being asked to provide documentation hears "It's in your best interest to get broad support from Linux" and on the other "Give me the goods or support for this device will be dropped." This is an effective combination, and the two together work better than either alone.
Theo is abrasive, yes... but the collective endeavor of free and open software needs someone abrasive, just as much as it needs a benevolent dictator.
With reasonable men I will reason; with humane men I will plead; but to tyrants I will give no quarter. -- William Lloyd
Man this guy sounds bitter and angry. How big of an ego do you have to have to say that your product is better, even when you admit considerably fewer vendors support your product? Buddy, if you happen to read this (which I know you won't because you probably wouldn't touch Slashdot with a ten foot pole cause it runs on a Linux box) do some growing up. Code doesn't get accepted by users because its uber-secure. If that were the case I'd put 'Hello World' on a CD and sell it for ten bucks a pop. People buy code for usability, plain and simple. Even hardcore Unix (yes, UNIX) admins like a little usability.
The GNU project also produces gcc, which is used by all of the free *nixes to compile their code.
Linus, yes, perhaps. GNU/GPL, no. Well, he could remove his compiler entirely, but then it wouldn't be a very useful system. (And technically, some of the code in gcc ends up in the executables it createsssh did not start with OpenSSH. ssh started as ssh, and it was good. But then they changed the license, and people did not like that, so they took the last release that was under the old license, and released it as OpenSSH. They then added ssh2 support and generally maintained it in parallel, and now OpenSSH is more used than the original ssh -- but the original ssh is still around. Perhaps Theo did contribute some code to the original ssh (it was open source, after all), but it still wasn't OpenSSH until rather late in the game.
As for using an `alternate, less tested sshd', are you sure you don't work for Microsoft's FUD department or something?
The problem with BSD is not the technology, it's the license. The BSD license offers no protection for companies who want to work with them. The BSD license basically says "anything you give to us may be taken by your competitors, put under a closed-source proprietary license, extended to make it incompatible with your original version (a la MS Kerberos), and used against you." The GPL, on the other hand, encourages a culture of equality. What IBM donates under the GPL stays under the GPL, thus Microsoft can't close it up and use it against IBM. They have to keep it open, and release their improvements when they release their new code. GPL'ed code has got to stay as open as when the original author wrote it, and thus isn't a tool of unfair leverage for the mega-corporations of the world. The GPL at least offers companies who want to encourage openness some assurance that they are levelling the playing field; the BSD license offers them nothing in return for their work except the certainty that their generosity will fuel proprietary software which may compete with their own offerings.
I love OpenBSD, but I've never understood their addiction to their "weak" license. I've thought about it, and it's business suicide. They have no chance of ever getting a foothold in the market based on their featureset because anything they do can just be co-opted by Microsoft, Apple, and whoever else wants to take their code, close-source it, and sell it with a pretty front-end. To contribute through the GPL, however, is to make a capitalistic deal with the world: "I have created this product, and on these terms. If you want to deal fairly with me on these terms, and reciprocate, then good. We have a deal." The creator stipulates the terms that the code is to be used: open, free, fair, and transparent. The BSD guys stipulate pretty much nothing, save an ego stroke attribution line.
So, Theo, if anyone's an "unpaid workforce", it's the BSD guys. The GPL guys get code back when theirs is used. You get nothing. The GPL guys are expanding the size of the pool of GPLed software out there in proportion to the amount of proprietary software. For every piece of BSD licensed software, 10 corporations probably take their code and use it to strengthen the proprietary software world. So if I have my choice between the excellent technology of OpenBSD or the pretty good technology and the code freedom security that comes with GPL-licensed Linux, I'll contribute to Linux. At least I know my code won't strengthen my competitors -- unless they seek to become more open as well and accept the terms of the GPL.
Here's my take on how the licenses play out in "real life":
BSD Versus Proprietary
It's high noon on Bootable Hill. Tumbleweeds are floatin' by and the sun beats down. In the middle of the street, Chuck Berkeley faces off with his arch-enemy, Billy Proprietary (I know, I know. The names suck. So sue me). They stare off for a moment, then Chuck remembers his ideology. Chuck lowers his guns in true Gandhi style. BANG! Billy takes the opportunity Chuck offered, and shoots Chuck in the head. Yay. The bad guys win again. Our hero didn't think it was "ethical" to protect himself against the bad guy and is now dead. Evil reigns supreme and Cthulhu consumes the earth.
GPL Versus Proprietary
It's high noon on Bootable Hill. Tumbleweeds are floatin' by and the sun beats down. In the middle of the street, our hero, Richard M. Tuxman, Esquire faces off with his arch-enemy, Billy Proprietary. They stare off for a moment, then Tuxman remembers his ideology. Tuxman calls out: "Billy, I'll lower my guns if you lower your guns in return. It's your choice." Proprietary
Hehe. This guy is obviously a great coder. Too bad he's such a total dickhead.
This article really highlights Theo's personality problems, and may shed some light on why NetBSD summarily kicked him out on the street. Here's the first email he got from the core developers after he complained that they shut down his CVS access:
Over the past year and a half, we have received a considerable number of complaints about the fact that you seem to harass and abuse both users and developers of NetBSD. At various times, some of us have suggested (with varying levels of severity) that you cease this behaviour, but this has been ineffective. Indeed, you have given us scant reason to believe that your behaviour is ever going to change for the better.
Your abusive actions have seriously impaired the success of the NetBSD project in several ways. Your actions have driven away developers or potential developers, and have alienated many users. They have also squandered much of the good will that various people have directed at the project.
Finally, it is clear that for the project to be a success, we must promote a positive environment for both users and developers. If we continue to allow you, an official representative of the NetBSD project, to behave in this manner, we create the perception that we approve of your behaviour. That perception is damaging to the project and cannot be allowed to persist.
Because of these things, we believe that it would be in the best interest of the NetBSD project if you were to resign all official association with the project. We request that you resign from the NetBSD core team, resign as the maintainer of the NetBSD SPARC port, and post a message to the "netbsd-users", "current-users", and "port-sparc" mailing lists announcing your resignation. If you choose not to post such an announcement within one day (by 9:00AM, 12/21/94), we will be forced to inform the public about your removal from the organization ourselves.
We regret having to do this, because you have done a significant amount of very good work for the project. In spite of that, we can no longer condone your behaviour. We wish for this parting to be as painless as possible; we have disabled your accounts on the NetBSD development machines and have removed you from the "core" and "port-masters" mailing lists, but have left your subscriptions to other NetBSD mailing lists untouched. We have no objection to your further participation in NetBSD, as long as you participate in a mature manner and make clear the fact that you no longer officially represent the NetBSD Project.
Of course, now no one can kick him out of OpenBSD, so I guess he's found the one role that'll work for him. Luckily, it's irrelevant during the 364 days this year when some idiot at Forbes didn't decide to upchuck a completely assinine, one-sided bullshit flame from a proven asshole, and then call it a news story.
Given a choice between free speech and free beer, most people will take the beer.
Theo is a paranoid, perfectionist, peckerhead. I say this in the most kind, loving manner possible, as I've got half a dozen OBSD boxes running on the internet right now, along with many more FreeBSD boxen and a few SuSe Linux machines that I'm learning to love.
BSD and Linux are different animals - on the development side BSD is like an American funeral home lawn - not a blade out of place, while Linux is more of an English garden, with all sorts of wild experiments happening.
I prefer BSD for server work because I like the discipline that exists in both development and maintenance, but I love the steady flow of GPL software that comes from Linux into the FreeBSD ports tree.
Both have an ecological niche to fill
I am very easy to get along with, but I don't have time to waste being nice to people who are being stupid. -Theo
There is a genuine weakness to the open source world when it meets the mass market.
90% of computer users do not have the knowledge necessary to evaluate whether a piece of software is garbage or not. Because open source software can be forked and kept around by anyone, garbage often can't be removed. No matter how awful the code, someone will keep it alive.
This problem applies somewhat to the BSDs too; except that there aren't as many BSD distributions, so it's more likely that they'll all decide to remove a given piece of crap that should be removed. With Linux, there's practically no chance of getting something godawful removed from every distribution, because they all compete with each other for completeness. I mean, we still have sendmail, and RPM was even made part of the LSB. There are still IMAP servers that use mbox format, and one of them has such shitty code that it doesn't even check malloc return values for failure.
Actually, if we're talking about fundamental flaws in OSs, perhaps Theo could spend some of his time fixing BSD's syslog before he turns his attention to ranting about Linux.
GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
I jumped ship from the windows camp in 2000, and when I did I evaluated FreeBSD, OpenBSD, and 3 Linux distros to decide which one I would run on my home systems, which ones I would recommend to clients for solutions, etc.
I had 3 spare x86 boxes, and tinkered with all three OSs for at least 6 months.
I'm sorry Theo but the reason I use Linux instead of BSD has nothing to do with hating MS. I needed a better solution that was cheaper, I went looking, and Linux ran on 99% of my available hardware. FreeBSD while better than OpenBSD in the hardware support regard only supported about 60-70% of what I had at the time, and I could only get OpenBSD to even install on 1 of my spare machines, of course without sound or USB and I had to try 4 different NICs before I found a supported one.
Sure, the BSDs have better design, I agree, and I would love to run them, but if I'm limited to 10% of the available hardware and every time I need a new NIC I have to snoop around the store looking for that one magic NIC with the right chipset revision well I consider that a larger burden freedom-wise than MS places on its users. Stop yapping Theo and go write some firewire drivers, or whatever technology came out 5 years ago that your system still doesn't support.
What stands out in my mind: better documentation, cleaner code, more structured filesystem layout, less distribution fragmentation, more informative kernel/log/error messages, "base" OS seperated from packages better.
BSD gets some things first, Linux gets other things first. IMHO, more often than not, when the BSD stuff comes out later, its generally because it was done the "right way" rather than the "quick and dirty way" and then re-written with an incompatible interface 3 months later :D
smash.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
This article has really made me see the light. It is full of unwaivering logic and factual critique of the Linux OS. I am now switching to OpenBSD. In fact, I will now be switching the entire Datacenter to run OpenBSD, and find a picture of De Rat to use as my desktop background.
Thank you Forbes magazine, once again you proved to mold and shape the direction of my life.
1) Your analysis is based on bad assumptions so your result is way off. 2) You're a sick bastard for fucking a horse.
which was quoted on another discussion of this article elsewhere on the Net:
"On December 20 [1994], Theo de Raadt was asked to resign from the NetBSD Project by the remaining members of 'core'. This was a very difficult decision to make, and resulted from Theo's long history of rudeness towards and abuse of users and developers of NetBSD. We believe that there is no place for that type of behaviour from representatives of the NetBSD Project, and that, overall, it has been damaging to the project.
This decision was difficult to make because Theo has a long history of positive contributions to the project. He was the principal caretaker of NetBSD's SPARC support, and has written too much code to mention.
We are certainly willing to accept (and would very much like to see) future contributions from Theo, but we believe that it is inappropriate for him to be an "official" representative of the project any longer."
I'd say that pretty well takes care of that. Theo is apparently an asshole. That he prostitutes himself to Daniel Lyons, a know anti-OSS/Linux FUD merchant, seems to make it clear that this rant is to be ignored by anybody with a brain, whether you like the BSDs or not.
Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
OpenSSH flaws are pretty much entirely in the portable version, which is done by a seperate team of people that add the so-called portability goop - things like PAM support are not in the OpenBSD version.
OpenSSL is done by other people under an apache-like license and OpenSSH is done by OpenBSD under a modern BSD license. If you want another SSL make your own, if you want another SSH use lsh.
And your true free comment is something that doesn't belong here, take it to a GNU discussion - BSD users don't care.
I'm sick of following my dreams - I'm just going to ask them where they're going and hook up with them later.
Actually, I'd blame Dan Lyons for inventing "linux for losers," because he titled his article that way. Only a Microturd could even think that way.
The whole article is flamebait by a known shill. You might also note he describes BSD as "a rival OS," and tries to build up as much animosity as possible. Linux and BSD are both free software and the whole notion of "rivalry" makes no sense. I'd suggest that no one ever talk to the loser again. It's like being interviewed by SCO, you can't win.
DMCA, Hollings, Palladium. What might have sounded like paranoia is now common sense.
"Does this belong here?" is in OpenBSD too.
It would be a real scream if the comment that prompted the PHB to swtich from Linux to BSD was cloned from BSD to Linux. B-)
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
I was having a hard time deciding between *BSD and *nix, but kissing girls sounds like so much fun I'm gonna have to choose *BSD.
"Dan Lyons" is where I stopped reading. He's proven himself to be somewhat lacking in journalistic ethics before, and I won't give him the satisfaction of me reading his articles.
Brain kills internet cells.
Here is the link to Theo's archive on the matter:
Theo's side of the story
and a shorter commentary:
seems reasonable to me
The truth suffers more from convictions than from lies.
I made myself a bet before I ever clicked on the article. I thought "wow, sounds like a Lyons piece" then I clicked on it:
Is Linux For Losers?
By Dan Lyons
So the Linux is for Losers part is from Dan Lyons. That's no surprise. He's still smarting from the thorough debunking PJ of Groklaw did. Speaking of which, I'd advise checking over there to see if PJ has made any comment on this story.
Lyons has to know he could get some flamebait out of Theo (not to difficult, but try comparing this interview to the one Theo gave to NewsForge).
This is just a troll for hits. Nothing more, nothing less. Lyons has just been studying up on how to rile people up. Please ignore him.
I mean look: Lyons chose that headline, Lyons chose to interview Theo, Lyons helped Theo look bad (not hard, given Theo's reputation).
This is nothing more than a cynical bid to sell ads on Forbes. Just like when Dvorak said that Maureen O'Gara should've gotten a medal for increasing readership when she stalked PJ of Groklaw, this is flamebait from an idiot meant to rile you into mindlessly clicking a Forbes story and generating ad revenue.
Lyons is laughing at you all the way to the bank. Have the last laugh; blackhole Forbes and their advertisers in your DNS and tell others to do the same.
I had exactly the same ephimamy as the parent's parent. I was given a choice in 1995 on what to run on a spare machine. I went to the Uni's computer lab with a box full of floppys and started downloading BSD, went home and started installing.
Well part of the installation worked. Once I got past some of the quirky installation issues BSD (I don't recall why but partitioning hard drives seemed to be a bitch), some hardware simply didn't work the most glaring was the video card and network card. VESA was supported but it was clearly lacking in performance and without a network card what is the point? I poked around on Yahoo on another machine (what is Google?) for more information and even tried a BSD irc channel. I was basically told in so many words "if you aren't a hardcore coder, you don't deserve our help". That is just "great" since my interest was getting the machine working not coding and their elitist attitude finally caused me to give up.
So back to the lab to download another piece of software called Linux (Slackware I believe!). The rest is history because it just worked. When it came to configuration questions, for instance X had to be configured by hand, I found people willing to give me hints. I worked through it and ended up with a functional machine video, NIC, and all.
To this day I point to this initial impression of BSD as the reason why I shy away from BSD as my first choice in machine deployment. The attitude of the BSD community has probably changed a lot in 10 years but I still can't shake the feeling I'm going to be slapped with elitism again if I run into a problem with a BSD installation.
OpenBSD was pretty obscure, despite everyone using openssh. As Theo has been more and more provocative, openbsd has gotten more and more publicity. The number of people using OpenBSD is WAY up in the last few years. Believe it or not, any publicity really is good publicity, and alot of people use products based on the product, not the person who made it, so people find out about openbsd because of this stuff, and then ignore this stuff and use openbsd because its good.
NetBSD kicked him out because they thought him being mean to users would scare away their userbase. OpenBSD long ago surpassed NetBSD for number of users, so maybe speaking your mind isn't the worst thing in the world huh?
Theo is really good at making people angry. Sometimes, that's angry enough to get out and fix a problem (such as security issues) but just as often they'll tell him to fuck off.
But he's a good attack dog for the open source movement: He can yell and scream at vendors and make the Linux people look calm and collected by comparison.
Just for the record, I use both OpenBSD and Linux (and other OS as well). There's some really good stuff in OpenBSD. There's also some things that Linux does better. Or, I should say, operating system using the Linux kernel.
Theo says that the BSD lawsuit made people flock to Linux. Nope, that wasn't it for all of us: when I was getting involved back in '92, it was the fact that Linux would run on lesser hardware. Specifically, it was that I needed a math coprocessor to run BSD but Linux would run fine on my 80386SX at 16 mhz. I remember seeing somewhere that Alan Cox chose to work on Linux for the same reason. More broadly speaking, Linux was more egalitarian in its hardware support.
I think that Linux success has been largely due to the social impact of the GPL license.
It speaks for itself.
I want Xen support before BSD has anything like it
Funny thing of it, primary reason I use FreeBSD for my servers is that Linux doesn't have jail support. I am NOT talking about a chroot jail either.
The Xen stuff would be pretty cool too, but I personally don't have much interest in running a bunch of virtual OS machines.
The line must be drawn here. This far. No further.
Linux users know what it's like to run Linux. Lecturing to them about what Linux is like, using OpenBSD as a standard, is
Tell people about what OpenBSD does right, using Linux as the standard, and maybe you'll get somewhere.
Those are LUSERS.
They have a two-bit wisdom, thinking that socialism is good, corporations are bad. Thinking is alien for LUSERS. The only source for morale they got are Ten Commendments. There is DO NOT STEAL commendment, so they don't know software might be shared...
BSD understands Freedom as freedom for people to do anything with software.
GPL understands Freedom as freedom for the software.
Those points of view are SO different...
Theo wants exactly what OpenBSD is; OpenBSD is an operating system that works how Theo says it is to work, thus it shall remain how he likes it.
Automatically? You mean you want it to come with a virus? Hmmm, OpenBSD already allows one to surf the web with it's default install and it's drivers are already installed as a part of the kernel. man ports if you want to watch videos, if you cannot read then that's not the fault of the programmers. Your nonsense about posting websites I do not understand, ftp, scp, and sftp are available, is there anything else you would ever need?
Theo has not worked on Linux for two reasons that I know of.
1. Because Theo started working with BSD code before there was a Linux and has not stopped since then.
2. Because he does not believe in the complete bullcrap that the Free Software Foundation touts to the masses - however, he is perfectly fine with Linux people using his code. So the question may be more like, "why hasn't Linus looked into OpenBSD to see the better solution in action?"
I think you needed to proof read your post Dave, cause you didn't come off making too much sense.
I'm sick of following my dreams - I'm just going to ask them where they're going and hook up with them later.
de Raadt has no interest what so ever in toadying up to idiots, if the person cannot understand how to use the operating system they are to learn or use another, hand holding leads to the idiocy that is the average Windows user.
Theo doesn't care about media plugins, which are a concern for the programme using the plugin, not the underlying operating system.
He doesn't care about the end user, the end user is nothing to Theo de Raadt, nothing . He also doesn't seem to really care about his status in the press or the public opinion - else he would not be so blunt and coarse with people who piss him off.
de Raadt could probably make Linux more secure, but that isn't something he cares about, he has his own operating system to work on. He doesn't propose to change Linux code, he proposes that Linux developers learn from the successes of OpenBSD and change the code based on those successes.
I'm sick of following my dreams - I'm just going to ask them where they're going and hook up with them later.