Perens Rains on Novell's Parade 277
unum15 writes "This week is Novell's Brainshare conference. They are touting the Microsoft covenant not to sue as 'good for consumers'. However, Bruce Perens decided to take this opportunity to 'rain on Novell's parade'. Perens read a statement from RMS affirming the GPLv3 would not allow companies to enter deals like this and continue to offer GPLv3 software. Perens even goes as far as to suggest this move is an exit strategy by Novell. There are also audio and pictures of the event available."
On Novell being obtuse (Score:5, Interesting)
Is it just me, or did Hovsepian intentionally misunderstand that statement? Feel free to correct me if I'm wrong, but I read your statement to mean that Novell would effectively become a subsidiary to Microsoft without actually being bought out. Much in the same way that Microsoft "Partners" tend to exist only so long as it amuses Microsoft. When Microsoft grows tired of them, they do something that completely undermines the trust and business model of those partners. (See: PlaysForSure, OS/2, Sybase, Spyglass, Citrix, etc.)
It amazes me that companies still fall for that trick, but there you go. Embrace, Extend, Extinguish. Bye Novell, it was nice knowing you.
Re:On Novell being obtuse (Score:5, Insightful)
Re:On Novell being obtuse (Score:5, Interesting)
Re: (Score:2, Informative)
Would've or would have, but never would of. Jesus.
Re: (Score:2)
I guess to some, it doesn't matter as long as they get their 15 minutes of fame!
Re:On Novell being obtuse (Score:5, Interesting)
Forget about GPL3 introducing major forks. There will be a few small spats. The license is in the interest of the Open Source developers who would use it, and that's all of the developers who want a share-and-share-alike form of licensing rather than an outright gift as in BSD. The folks who mainly would be opposed to it are those who want to benefit without sharing, and to say the community doesn't need them would be an understatement.
If you believed that GPL3 would prohibit Linux from being used in a system with DRM, you can stop now. There are four places where you can put DRM in a system with a GPL3 kernel and have it work well and not have to give away your keys: in hardware as in a chip that mediates access to the display or audio output, in a coprocessor as with the separate chip that runs the GSM stack in cell phones, in a kernel under the kernel as with Microsoft's "nib", and in a user mode program. Those are also the best places to put the DRM from a technical standpoint. I am currently working on a paper on this, maybe I'll have it out tomorrow evening.
Thanks
Bruce
Re:On Novell being obtuse (Score:5, Interesting)
No, it wouldn't work this way. In a compliant system, you'd be able to change the kernel as you liked, the system would still boot, but the DRM would still decrypt and play media correctly without offering access to the unencrypted data stream. The key is that the GPL3 DRM terms mean that the DRM must not lock down the GPL program, and the DRM functionality of playing the media must keep working if you change the GPL program. GPL3 does not say that you have to be able to break the DRM, it only restricts what the DRM can break.
This isn't going to keep users away from the program. Users don't generally care about licensing as long as they have a clear right to run the program, and they do. Look at the nasty EULAs they sign from MS, much worse than ours. It may keep certain developers away, but historically the GPL share-and-share-alike terms have helped, rather than hurt, to build a large developer community.
Bruce
Re: (Score:3, Insightful)
Re:On Novell being obtuse (Score:5, Funny)
When the story is about me and my comments get lost in the noise, I really get to think that Slashdot might not value information right from the horse's mouth as much as that from the other end of the horse :-)
Re: (Score:3, Informative)
Of course. Here's the legal language you're asking for: "Do what I mean, not what I say." :-)
So, this illustrates the fundamental problem in law. Law does not require ethical behavior. This is because there is no canonical definition of ethical
Re: (Score:2)
It would only prohibit them from conveying something they owned a right to this way. When you download a distro, you have to pass the rights they gave you along with the right you have to the code/software with it. The novell-microsoft deal doesn't count unless the covers pattented work is submited by Novell. The microsoft-novell deal doesn't give novell the rights that microsoft owns. Otherwise, you are giving all the rights you hold over it.
Re: (Score:2)
Maybe Novell is looking for a $10-billion pay-day ten years down the line when they eventually sue Microsoft for breach of contract or anti-trust violations.
Re: (Score:3, Interesting)
Re: (Score:2)
Re:On Novell being obtuse (Score:5, Interesting)
With Novell owning the original Unix IP, Microsoft may then eventually have the upper hand. That's a SCARY thing...
Re: (Score:3, Informative)
1. If Novell's Unix IP had much leverage against Linux, then Microsoft buying Novell would be almost certainly very problematic, antitrust-wise.
2. But, the Unix IP in fact doesn't bear much up
Re:On Novell being obtuse (Score:5, Interesting)
Will MS buy them? MS tends to work through proxies these days. Is 330 Million a good starting investment? Sure.
Bruce
I'm out (Score:3, Interesting)
GPLv3 (Score:2)
If the software owned by the FSF moves to GPLv3, will *any distributor of a complete OS be able to enter into a deal like the Novell/MS one? Does it really matter whether linuz remains v2 when so many critical components will be v3?
Re: (Score:2)
Re: (Score:2)
Yes it will. As pieces outside of the kernel migrate to GPLv3 Novell will hit a roadblock having to rely on GPLv2 branches. Someone might still maintain those, but maybe not, making that much more work for Novell. Novell will still have to share its code with the community, but the community won't have to share their code with Novell. Which makes me happy a little.
Re: (Score:2)
so? (Score:3, Informative)
Re: (Score:2)
I was correcting that, and only that.
Re: (Score:2)
"Rain on the parade" ?? (Score:2, Funny)
Sounds to me that Perens showed up at the parade under bright, sunny skies and attempted to use a half-broken toy squirt gun. "No, really, its rain, trust me!"
People hold high expectations on Novell (Score:5, Interesting)
And that's the beauty of Free Software. They can dump Linux and Free Software all they want, if they do, as fast as it takes, a fork for all projects that they are personally involved (Suse, Gnome, Mono, from the top of my head) will pop up and continue almost as nothing has happened.
And I really wish that happens. I don't like the way they are handling Gnome, ignoring completely the community in order to satisfy Novell's aims and goals (mostly, appease to Windows "converted" users. The recent created Gnome Control Panel is a copy of Windows Control Panel, except that it is slow and cluttered like Win 3.11 Program Manager). That, and things like bundling Mono, pfff. But that's another subject, that doesn't belong here.
Just a heads up. Novell has done nothing to deserve your trust. Don't look surprised when they finally misbehave.
That's the problem with Novell. (Score:5, Interesting)
They paid $210 million for SuSE. Why?
The more intelligent approach would be to hire developers who would submit patches that you wanted to the various projects that you're interested in.
Then you Open the protocols that you control that you want to see more widely adopted. And pay developers to incorporate those protocols.
Novell had the idea that it can acquire Linux by buying Linux distributions and projects. When this didn't pay out, Novell decided to "partner" with Microsoft in search of some more money.
Re: (Score:2)
Investors seem to think Novell (NOVL) was wise to buy SuSE. Novell stock spiked to $8.80 soon after the purchase announcement hit the wires, and closed the day at $7.33, up 21.16% from the previous day's $6.05 close.
Not that different than when AOL and Time Warner merged. Company makes a risky move, investors like, shares go up, someone sells and profits, company sinks, board changes, company makes a risky
Re: (Score:3, Insightful)
If you look at it's history it has a spectacularly bad record of buying software and technologies for no apparent reason and then selling them at a loss when they don't know what to do with them.
It's really one of the most badly managed companies around.
Re: (Score:2)
Re:People hold high expectations on Novell (Score:5, Insightful)
I have to disagree with ya there. Sure, they are a commercial company and their goal is to make money. Big Surprise! However, in this effort, they have contributed a substantial amount of code to the kernel, gnome, and numerous other projects. I'm as uneasy about a deal with MS as anyone, but to start bashing them because they are a commercial company and they contribute to Linux is a bit short sighted.
If you do not like, what they have done with gnome, then you can contribute or use KDE, XFCE, twm, etc.
Are you kidding me? Softening the transition (which is an option btw, you can change this), would be a smart move for all linux developers. If we create a completely foreign system, then it is that much harder to get people to use, promote and contribute to linux. Otherwise we are left with a select few and linux stays in the basement.
I hate to break it to you, but there are a lot of users that are locked in because they rely on .NET apps. If you supply mono, then there is a better opportunity they can transition their current custom apps and use linux.
Novell may not be my favorite Linux company, but you can't discount the contribution because of unfounded "fears" about "some day they will ruin linux". If they walked away today, I would at least say "Thank you for all that you had contributed". Without companies like, IBM, Novell, RedHat, Canonical and others, linux would still be where it was at 5-6 years ago. Today it is a viable alternative to MS Windows for the desktop, and is replacing Solaris, AIX and HP-UX in record numbers.
Re: (Score:2)
One of my pet peeves, regardless of distro, application, whatever, is when a decision is made to ease the transition of "foreign" users in detriment of the already faithfu
Re: (Score:2)
While I think
It's all about .NET, C# and the CLR (Score:5, Informative)
People hold high expectations on Novell, and I really don't know why. Of course they "bought" Suse in 2003, the Mono project, and some other free software projects. but Novell was, is and will always be a proprietary software company.
It's all about Mono.
While C# certainly doesn't have nearly the installed code base that Java has, ".NET" is pulling even with [and might even have surpassed] "J2EE":
As much as everybody loves to hate the guy, Ballmer was 100% correct when he said that it's all about "developers, developers, developers", and if you think ".NET" isn't the hottest thing in the programming market right now, then, well, you've been asleep at the wheel for the last five years.
Mono is the ace up Novell's sleeve; with the Microsoft agreement, they are assured that they've got something that Red Hat doesn't have, that Oracle won't have [with the upcoming "Oracle" Linux], and that even IBM or Sun wouldn't have, if they were to roll their own Linuxes, which is to say: An ironclad guarantee that their flavor of Linux will play nice with
Obligatory Groklaw Link (Score:3, Interesting)
Re: (Score:2)
Is anything Novell offers under GPL3? (Score:2, Insightful)
- Crow T. trollbot
Re:Is anything Novell offers under GPL3? (Score:4, Informative)
Re: (Score:3, Interesting)
No alternative currently exists for gcc which is free software.
I find it hard to believe there are no other OSS/free C/C++ compilers. Yes, I know GCC does more than C/C++, but what more would you need to build the kernel and userland? If the hammer came down, I'm sure it wouldn't be too much trouble to pick up some other compiler and put the work into it to get it to fit in the spot GCC left behind. I mean, GCC's an impressive piece of software, sure, but it's not like you couldn't get another compiler if you had to.
Actually, now that I think about it, why even wor
Re: (Score:2)
http://www.open-std.org/jtc1/sc22/wg21/docs/paper
Re: (Score:2)
It isn't a matter of what the GPLv3 says, it is a matter of what the current GPLv2 says. They cannot exempt around this with wording in a new license!
Re: (Score:2, Interesting)
Re: (Score:2)
Re: (Score:2)
If Sun goes GPLv3 I'm there (Score:2, Insightful)
I've worked with GPL'd code since the early 90's, have made contributions to the kernel (and other projects). My problem is that I'm currently in an area where Software Patents (and patent trolls) are a serious concern.
I know I'm not the only one either.
Sun could make serious inroads in a lot of places if they went the GPLv3 route with Solaris. And I'd be delighted to help get them there ASAP.
GPL 3 (Score:2, Insightful)
So what? Novell just goes ahead and forks all the FSF stuff now and leaves the licensing as GPL 2 they're well within their rights not to accept a more restrictive (to them) license.
Re:GPL 3 (Score:5, Interesting)
Re: (Score:2)
So, lets say we have a GPLv2 comercial fork. Is that bad? I mean competition is good right?
This doesn't even goto mention that the GPLv3 doesn't ocme close as it is currently writen to doing this. Novell has nothing to worry about useing the GPLv3 software. Likewise the FSF and anyone who uses the GPLv3 have more to worry about the GPL
Re: (Score:2)
I'm pretty sure that FSF's software is distributed under the "GPL v2 or later". Which means that any commercial fork would have to keep using "GPL v2 or later". FSF would then be free to take any changes to the commercial fork, apply them to the FSF version and then release it under the GPL v3.
I mean competition is good right?
Especially when your competition can take your changes and incorporate them into their version, but not the other way aro
Re: (Score:2)
Re:GPL 3 (Score:4, Interesting)
The copyrights to the gcc toolchain belong to the FSF -- they ARE the owners of the work! It has long been a condition to work on the official fork: if you want your patches to go everywhere, you assign copyright. Developers that don't like that are free to make their own forks (as with Emacs vs. XEmacs), but FSF has had enough developers who are OK with it to now have the definitive version of gcc.
And if you think GPLv3 is a recent "game" from a "faction" in the FSF, you haven't been paying attention for about 20 years. FSF has ALWAYS been about copyleft. They predate the OSS movement by a decade and Usenet is littered with the ashes of long flamewars about the GPL license.
Re: (Score:2)
Because you're not looking close enough?
Samba seems like they'll be moving and even Sun has sounded positive. Most anyone who's made an informed decision to use the GPLv2 is likely to move as v3 is merely a continuation of the exact same policy, updated to handle new issues.
The linux kernel is an exception; not particularly surprising as Linus has never been particularly aligned with the FSF ideas (witness the former choice of a non-free versioning system...).
Novell is
Re: (Score:2)
It's far more than FSF, it is everyone who has seriously considered the GPL and found that it is appropriate for their needs. For me, I chose GPL because I want to retain the option to get paid for closed-source forks of my work. (No takers yet.
All it takes is ONE GPL "V3 or later" userland program to be essential and the whole house of cards falls down. C++ is gaining new language features soon. Samba will nee
nothing good? (Score:2, Interesting)
My understanding is that, as part of the deal, Microsoft is actually distributing SuSE Linux.
Doesn't this mean that they themselves are distributing the software they might be claiming patents on? And doesn't that mean that, for practical purposes, have given up their right to assert the patents against any GPL'ed software that is part of SuSE Linux?
I'm sure this wasn't Microsoft's intention, but it looks to m
Re: (Score:2)
No - you don't "give up the right to assert a patent" through inaction. You are thinking of trademark where if you don't vigorously defend your trademark, you can and often will loose it.
A patent can only become unenforceable by either reexamination from the USPTO, federal court decision, or definitive action from the patent holder itself (like a covenant not to enforce or a donation to a third party, etc).
You can hold a patent and do nothing with it for years, then all of a sudden decide to enforce it.
Re: (Score:2)
Re: (Score:2)
But does the GPL3 really prevent these deals? (Score:2, Informative)
The current GPL3 draft doesn't seem to prevent this type of agreement.
Re: (Score:2)
Re: (Score:2)
Sigh! One GPLv3-hating troll surely understands another.
Anyone wondering if Novell is.. (Score:4, Interesting)
Microsoft lackey Novell Exec "My bad, Here is the papers that say we did give them all UNIX licenses"
Re:Anyone wondering if Novell is.. (Score:5, Interesting)
They will no longer come to the defense of open source projects if MS sues them and that's what MS was after all along. MS has already gotten the same kind of deal from Sun. If they can get IBM they will be done.
Re: (Score:3, Insightful)
Re:War is peace (Score:5, Informative)
It is simple as that. Without GPL, fair use aside, you cannot (legally) use, you cannot derive, you cannot distribute. With GPL, as long as you grant the same rights when you distribute, you can. Now tell me again, how GPL restricts any freedom? How can a license to restrict a freedom that you didn't have in the first place?
Re: (Score:2)
Re: (Score:3, Insightful)
Well said.
It is simple as that. Without GPL, fair use aside, you cannot (legally) use, you cannot derive, you cannot distribute.
Actually, you don't need a licen
Re:War is peace (Score:5, Insightful)
A lot of people would disagree with that. Hell, the GPL [gnu.org] disagrees with that:
See? "restrictions". Just because they are lesser restrictions than the default case of "no rights at all", that doesn't mean they ain't restrictive.
I'm a big fan of the GPL myself, but let's try not to sacrifice accuracy to zealotry here.
Re:War is peace (Score:5, Insightful)
That's semantics. GPL doesn't restrict anything that you would be able to do with standard copyright law. Copyright law says you can't do A, B, C, D and E. GPL says you can now do A, B, C. How is that restricting?
Notice, I'm not denying GPL has more conditions than BSD or Public Domain. All I'm saying is that has one goal, to make sure any software and all its derivatives under that license will be able to be freely run, studied, derived and distributed. They never hid that goal, it is the GNU manifesto, for god sake. If they could simply say that, in a clear and unambiguously way, such confusions would never exist in the first place. But because of the likes of Tivo, Novell and others, that will try to find a loophole and release derivative works without granting those rights, FSF has to created this tangled network of legalese, to close as many holes as they can.
Re: (Score:2)
Yes, of course. The law is semantics. Programming is semantics. Semantics are important.
It's restricting because the concept of restriction is an analogue value, and it's possible for something to be more restrictive than one thing, and at the same time less so than some other thing. For example, GPLv2 is less restrictive that a Microsoft EULA, but more so than the BSD licence. As you point out yourself.
Re:War is peace (Score:5, Insightful)
I am not free to own slaves. Am I restricted, or is everyone else more free? The answer is everyone is more free because nobody can own slaves.
Similarly, the GPL only restricts your ability to restrict others. This means the fewest restrictions for all. Isn't that the most freedom possible? Free to do anything but take freedom from others.
The GPL's restrictions are only anti-free to those who think only of themselves. The GPL is not for them.
Re: (Score:2)
Where are my mod points when I need them? Well said!
Re: (Score:2)
It's not an either/or proposition. Total freedom means I can rape murder and enslave to the limits of my capability. Total restriction means I have to seek permission in order to breathe. Clearly neither extreme is desirable.
And just because some tossers are making the argument that "less than perfect freedom" implies "absolute restriction", that doesn't mean we should play into their hands by arguing the opposite extreme whe
Re: (Score:2)
Not what I'm saying. I'm saying it's orthogonal, and that maximum freedom requires certain restrictions, namely the restriction that you can't take freedom.
Don't know what extreme you thought I was arguing (total absence of restriction? definitely not in my post), but I'm not.
Re: (Score:2)
My whole point is that "restriction" is NOT the opposite of "freedom". "Oppression" is the opposite of "freedom", and to be free of oppression would-be oppressors -- which includes you and me -- must be restricted.
I should have said "I am not free to own slaves. Am I less free because of this, or is everyone more free? The answer is everyone is more free because nobody can own slaves."
Re: (Score:2)
It governs how you use the product,
No it does NOT. Go read the GPL. It governs distribution, you can use it any way you like as long as you don't distribute it. (Contrary to e.g. an EULA)
Re: (Score:2)
If you use a GPL product as part of a wireless router product, for example, and make changes to the source support your wireless router, and you do not release those changes you can be in violation of the GPL.
Sorry for the confusion.
Re:War is peace (Score:4, Informative)
Then you are distributing the binary inside the router. That is distribution. You can modify it without releasing the sources as long as you only use it in-house. Microsoft could run Linksys Routers with a heavily modified Linux firmware and would not be required to release the source as long as they don't sell/distribute it.
Re: (Score:2)
No, you're in violation of copyright, and you can't invoke the GPL as a defense. If the product was released under standard copyright without the GPL, you'd still be in violation and you wouldn't have the option to comply by releasing your code.
Re: (Score:2)
I don't think that's an appropriate analogy. The Bill of Rights restricts the government, not me. The Bill of Rights prevents the [federal] government from passing laws on certain things. The GPL, on the other hand, most certainly does restrict the ind
Re: (Score:2)
Assuming you're American (and my most humble apologies if you aren't), you've been brought up to believe that you have freedom, which is why I think you're making this statement. Anarchy is freedom, what you have is certain freedoms tempered by rules. I'm not saying this is a bad thing - one man's freedom is another man's oppression, so rules are necessary for the f
Re: (Score:3, Insightful)
Re: (Score:2, Informative)
unum
Software Patents in US are the problem (Score:5, Informative)
Copyright law is the mechanism by which GPL works, but SOFTWARE PATENTS are the real issue here, as Bruce explains very well in his talk.
The "protection racket" is about the patents that MS implies Linux infringes on. And as Bruce points out, pretty much any non-trivial software probably infringes on someone else's software patents.
That's because software patents in the USA have been doled out too easily. They are absurd.
What's worse, Bruce explains, there is actually a _penalty_ for trying to figure out if your own software infringes. Because if you can be shown to have infringed on a patent you actually know about, the damages are tripled.
Small companies and individual software developers are at the biggest risk. Because big companies have portfolios of patents that they routinely cross-license, thereby protecting themselves from each other. The small guys are locked out. And of course, little guys don't have the money to maintain a legal defense even when they are totally in the right, forcing them to settle.
Software patents in the US are the problem.
Re: (Score:2)
Of course not. Well, someone might, but no one here. First of all, perhaps 1/10% of all slashdotters understand the ramifications of GPLV2, let alone V3. Second, mentioning that Microsoft will be involved with Linux in some way creates such overpowering waves of cognitive dissonance in most slashdotter's minds that all reason is overwhelmed and the mind is reduced to repeating a mantra of "bad...bad...bad..."
Is the hidden "all your base" clause not
Re: (Score:3, Interesting)
The GPL says you can't distribute anything covered by its terms unless the people you distribute to have the rights to distribute passing on all the rights you passed on to them. So whatever benefits I confer when I give you a GPL program, they have to also apply when you give a copy to someone else. It's to stop some sneaky tricks that could otherwise be used to effectively take a project proprietary.
So, under this clause, Novell couldn't buy a licence from MS
Re: (Score:2)
corect nbut used entirly wrong in supporting the GPLv3 novell problem. You can only give rights you have
Re: (Score:2)
The two licenses are incompatible, but that will not create problems for any projects except the Linux kernel. Most GPL code out there is licensed under "V2 or later", meaning with each additional version of the GPL released by the FSF the code can automatically be released under the new license.
When GPLv3 is ready, the FSF is going to fork all of the code they have copyright to and make the fork "V3 or later". Since "V3 or l
Re: (Score:2)
Not disagreeing as such, but you could probably find some substantial portions of the code where the ownership w
Re: (Score:2)
My copy of GPLv2 says: "Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope." So my reading would have been that patent infringement lawsuits were not covered. As for whether Novell can buy a license which protects their customers from infringement lawsuits, that's one for the lawyers.
My copy of the GPLv2 says nothing about "passing on" rights. In fact, it says that the people who get a copy from you get their license to distribute from
Re: (Score:2)
mmm... my mistake. I got that from Stallman's address to the 5th international GPLv3 conference [fsfeurope.org]. Sadly, he's talking about phraseology already in the GPLv3 draft at the time of the Novell-MS announcement, and not how v2 works as I had originally thought. So my bad.
On the other hand, it's not a million miles away from this:
Re: (Score:2)
Forgive my obvious stupidity, but doesn't putting any restriction, including the GPL make the software not free?
And no, I am not trying to troll. I just can't figure out why this is such a hot issue.
Re:War is peace, Novell is Minitrue (Score:2, Interesting)
Complete freedom is impossible. If you have free speech, I can't have the freedom to duct-tape your mouth closed and break your typing fingers just because I don't like what you're saying.
Just like the US Constitution, as amended, enshrines some rights (like freedom of speech) and bars others (arbitrarily duct-taping mouths shut), the GPL enshrines some rights and not others. The freedoms the FSF are interested in are the freedoms to use and modify software, and redistribute as you like. If you receiv
Re: (Score:2, Insightful)
Even free speech involves responsibilities.
^ Why is parent modded flamebait? ^ (Score:4, Insightful)
Why is the parent modded flamebait? This seems pretty reasonable to me. When the constructors of the US Constitution drafted the first amendment, I'm sure that yelling "fire!" maliciously in a crowded public building wasn't what they had in mind. Instead, it's a specific type of freedom which has a few limitations. However, these limitations are important to preserve the function and spirit of said rights. The same goes for the GPL.
By releasing code under the GPL, I'm saying effectively, "you can have my code for free, and even change whatever you want, provided you don't restrict anyone else from doing the same." The BSD license allows the author to say, "use whatever you like, and you can close up my source code and not share with anybody if you want to." If that license is more attractive to you, than by all means, release your code under the BSD license instead of GPL. But like me, many people want the guarantee of the continuing freedom of the code they release. For those of us who feel that way, the GPL is exactly the right license.
Re: (Score:2)
Doesn't seem so ridiculous to me.
Indemnification: "If the bully tries to beat my friends up I will come to their defense."
Covenant: "If you become my friend the bully promises not to beat you up."
Re: (Score:3, Insightful)
Er, no. Bruce's fecal matter smells just as bad as the next human being's; of this I am entirely certain. Take him down off that huge marble pedestal in your mind. Once you start perceiving him as just another pathologically flawed human being like the rest of us, you then cease to be so amazed when he behaves accordingly.
Re: (Score:2)
You mean distributing the software. The GPL's terms don't govern use.
It is explicitly and methodically being written to be as anti-business as possible.
Multiple assertions without any supporting evidence... Can you provide any foundation for your argument, at all? It seems to me that Linus one of the few voices really opposed to the changes in the third revision of t
Try substituting "Rome" for "Microsoft" (Score:2, Insightful)
Re: (Score:3, Insightful)
Precisely correct. Anyone with a brain knows that Microsoft are not going to exist for more than another 15 years, tops. Why?
1. No concrete long-term strategy after Windows NT 4, and no substantially new products since then. Windows 2000, XP, and Server 2003 are all incremental upgrades to NT 4. Vista is Mi