Advanced

Novell: 'No One Can Stop Us From Selling Linux'

Posted by Scott_Ruecker on · 96 comments
InformationWeek; By Paul McDougall
Mail this story
Print this story

Responding to a report that its right to sell Linux is under scrutiny by a group that controls key parts of the open source operating system, a spokesman for Novell on Monday said the company does not expect to make any changes to its product line as a result of the tiff. "We're telling customers that no one can stop us from selling SUSE Linux," the spokesman said.

Full Story

  Nav
» Read more about: Story Type: News Story; Groups: Linux, Novell

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments (96)

well, yes they can

The FSF controls the GNU toolchain. If they license it under GPL3, and GPL3 is written in a way that does not let Novell use Linux the way they want to, they're hosed. Then they either have to fork their own toolchain, or change their business practices.

I'm not having any opinion on how likely this is, or if it would result in good or ill for Linux and FOSS in general. I'm just saying that the FSF does control some key elements of Linux, and wields a good bit of power because of it. Novell is dumber than they already look if they don't realize this.
TC -

Well, no they can't.

1. Currently, the GNU toolchain controlled by the FSF is GPLV2 or later. If need be, Linux distributors -- and I seriously doubt Novell will be alone here -- can pull an X.org or a Joomla.

The X.org and Mambo folks might be able to share their experiences with you.

If V3 makes life difficult for Novell, it will almost certainly make life for difficult for Red Hat, whose indeminfication includes a promise to license patented code if they can't rewrite infringing code in a way to meet customer's need. It's sure to make life difficult for a number of others. The toolchain will be, at most, an inconvenience.

2. Ain't no indication the Linux kernel is moving to V3, which might make it a teensy bit harder to strand Novell.

The FSF is dumber than they already look if they don't realize this.
TC-

Actually, no they (the FSF) can't.

If push comes to shove, Novell could maintain a GPL v2 tree of software forking from the FSF maintained versions that we expect to go to GPL v3.

A grant of license under v2 would not be revoked by v3 for current versions of any GPL'ed software. And we already know that Novell has not infringed on copyrights for any software licensed under GPL v2.

Would this be practical? Hard to say, but considering that there are still a lot of users out there running on the 2.4.x branch of the Linux kernel, it may well be.

From my POV, the FSF have painted themselves into a corner: When GPL v3 comes out, they'll *have* to take legal action or it will show that they were just "blowing smoke" with regards to the MS-Novell deal. And in order to take legal action, they will have to be very specific with regards to what infringements Novell has committed.

If they make some sort of announcement to the effect that "Novell's infringements have been cured" and we don't see any sort of change in the MS-Novell deal, then that will raise the question: "How exactly has the situation been resolved?"

My prognistication: Pamela Jones, Mr. Moglen, and Mr. Stallman will end up with egg on their face over this whole thing.
I agree with tuxchick that I don't know either whether this will be good for Linux in general or not.

Also, I think the FSF can do some damage if it wants. Like someone commented about problems for Red Hat, I would respond that this has happened before also where Internet Explorer was made to change its activeX behavior but Firefox, Opera were spared from that patent (sorry at work and a bit hazy on the details). Could happen again. Just saying.....

FSF does not have to sue anyone if they release under GPL v3. Novell just won't be able to continue operations in its current form.

Although I must admit that I like the fact that the the sell outs (yes, I call them sell outs just as from time to time I write M$), are on the defensive. How did that quote go, "Where Zen ends, ass kicking begins".
I think it's a question of practical vs. possible. The jury's still out as to whether it would be feasible to continue selling Linux. My guess is that tuxchick is correct but whatever.

> Red Hat, whose indeminfication includes a promise to license patented code if they can't rewrite infringing code in a way to meet customer's need

As far as Red Hat goes, I don't understand how that wouldn't violate GPLv2 if it ever happened. A Google search returned no helpful information on the topic.
The reality is, history is full of predictions, and, few of them end up being correct. This issue is convoluted enough so that I think that I'll wait for the realtime outcome.
Quoting:If V3 makes life difficult for Novell, it will almost certainly make life for difficult for Red Hat, whose indeminfication includes a promise to license patented code if they can't rewrite infringing code in a way to meet customer's need.


Possibly, but not necessarily. There's one big difference between the Novell and Red Hat situation. With Red Hat, it's Red Hat doing the indemnification. With Novell, it's MS doing the indemnification. So it all depends on how FSF is going to formulate it.

FSF's best course would be tp write a clause that would extend MS's indemnification to all of Free Software land. In that case it's MS that would want to end the deal swiftly, leaving Novell relatively unscathed (except for some scorch marks)
Must say I agree with tuxchicks assessment, i believe life can be made very difficult for Novell regardless of whether the kernel moves to GPL3 or not, Linux is a whole package not just the kernel if the rest of it goes GPL3 and kernel remains GPL2, IMO Novell will have no choice but to maintain a completely GPL2 based fork and folks that is a very big enterprise for one set of developers its certainly possible I have no doubt about that but just how likely is it?

In the case of FSF and Novell, i think its a case of Dumb and Dumber and could actually hurt linux more than SCO ever achieved, i believe based on the unlikeliness of Novell managing their own GPL2 fork that both sides will actually eventually sit down and talk regardless of the current dissing going on from both camps.



Legal: All opinions are my own unless they are wrong in which case they belong to my brother.
>FSF's best course would be tp write a clause that would extend MS's indemnification to all of Free Software land. In that case it's MS that would want to end the deal swiftly, leaving Novell relatively unscathed (except for some scorch marks)

That would be sooo fun! Then Novell could continue blundering along its merry way, collecting fresh new scorch marks.
Dino, you actually think Novell could handle the costs of forking the entire GNU base and maintaining it forever after, including fixing all the incompatibilities in software that will arise due to their base diverging, and still be competitive? And that RedHat would help them do it? What color is the sky in your world?

What Novell+Microsoft will do is just change their deal to exclude 'covering' GPL3 code. And hey, that's what we wanted them to do.
>With Red Hat, it's Red Hat doing the indemnification

Makes no never mind with regard to the license.

Red Hat promises to secure patent licenses, an act that is squarely in violation of GPLV2.

Besides, nothing in any language I've seen cares who does the indemnification...and it shouldn't. The actual indemnifier in business is most often an insurance company specializing in such things.
ino, you actually think Novell could handle the costs of forking the entire GNU base and maintaining it forever after,?

Hey Einstein, last I looked, Novell wrote and maintains its own operating system, and has for years.

Besides, they won't have to. If things are bad enough that Novell will need a fork, they will have plenty of company.
> Hey Einstein, last I looked, Novell wrote and maintains its own operating system, and has for years.

And if they're basically back to having to write and maintain their own operating system like with Netware when RedHat is getting a huge amount of development done for free and doesn't have compatibility problems brought about from using wildly differing software.. how does Novell compete with RedHat?

I don't even know why I'm having to point this out, given the idea of Novell forking and maintaining the entire GNU base forever after is ridiculously stupid when they could just add a "except GPL3 stuff" to their deal. Microsoft isn't going to want to kill its wedge against RedHat (yet) so will be perfectly fine with that modification.

> If things are bad enough that Novell will need a fork, they will have plenty of company.

Hey Einstein, who other than Novell is in the patent agreement with Microsoft? Did you forget the issue?
>how does Novell compete with RedHat?

Any license the FSF creates that will keep Novell from distributing Linux will cause the same problem for Red Hat.

Added in an edit:

The FSF faces a real problem here. How do they stop Novell without threatening IBM, Oracle, Red Hat and others? I think there is a real threat of forking the tool chain -- or some combination of contributing non-GNU tools and forks -- under an open project counting IBM, etc among its contributors. Major players have invested too much in Linux to see it all go up in smoke.

And..they wouldn't have to fork everything...just a subset of the enterprise stuff.

For all of RMS's bluster about GNU/Linux, lots of that stuff isn't GPL'd. Apache isn't, Postgres isn't. I serously doubt that QT will move to V3 if it's a Novell killer, and if QT doesn't mover, neither will KDE, etc, etc, etc.

Look on the bright side...If the FSF insist on doing something stupid, we might finally get that court test everyone's been waiting for.
According the FSF, there are currently only 5,273 "free software" packages indexed. Not all of those are actually GNU packages, meaning they are not controlled or owned by the FSF, such as Samba and the Linux kernel. http://directory.fsf.org/all/

Out of that 5,273, there are *only* 365 GNU software packages. And many of those are LGPL, as are many of the GPLed packages that are not GNU. http://directory.fsf.org/GNU/

In that list of GNU packages, I'm not certain that even all of them are under the control of the FSF, such as gCompris.

Something to think about when you say "Novell couldn't possibly fork all this stuff."

>Something to think about when you say "Novell couldn't possibly fork all this stuff."

Absolutely.

Novell would most certainly have help from others, and lots of that stuff won't be GPLV3.

If FSF wants to craft an improved license, more power to them. Cleaning up the language and dealing with international problems that weren't considered before is great. Making a real move for more freedom is also great.

I suspect one reason why V3 is so long in the birthing is that FSF wants to increase the freedom available to everyone and, contrary to what many believe, would desperately like to do so without killing free software in the process.
> would desperately like to do so without killing free software in the process.

I find that cold comfort. History is so full of failed projects that began with good intentions.
Quoting:The reality is, history is full of predictions, and, few of them end up being correct.
Right you are
Quoting:This issue is convoluted enough so that I think that I'll wait for the realtime outcome.
I am doing the same.
> And..they wouldn't have to fork everything...just a subset of the enterprise stuff.

Which is what everything is built on. So then all the rest of the software they distribute starts using new features in the 'real' stuff as time passes, and Novell is constantly fighting to fix compatibility problems in /everything/, and having to make parallel implementations of all the features (and replicating the bugs) without copying the GPL3 code. You essentially end up with WINE for GNU. Couple that with new, exciting projects getting released as GPL3-only and.. wow, I'm still amazed you and Darren think this is feasible.

Why do you think them adding "except GPL3 stuff" to the license is way less likely than them taking on a perpetual maintenance and compatibility nightmare for them and their customers? And if they did go the fork route, how could they possibly be competitive 5+ years from now?

WINE for GNU.

I must say Novell is wrong:

57 earlier comments in the full thread.

> ...the agreement involves and covers GPLed software specifically...

On Novell's end yes. But Novell would be making no agreement concerning GPL'ed software. They would be agreeing not to sue users of Microsoft Windows and Office. Thus, they would not be infringing the proposed GPL 3 license.

Microsoft's agreement would concern GPL'ed software (namely SuSE), but since they won't have any GPL 3 code to distribute, they won't care. All of the GPL'ed code Microsoft has released has been GPL 2, and I think we can expect it to remain that way.

So, how would either party be violating the proposed GPL 3? And if they wouldn't, is there any way to prevent this? I can't think of one. I'm not sure it's even a good idea to try. There's a legal saying that goes something like "fringe cases make bad law". I think that's what we're dealing with here. Dino probably knows the exact quote.

> Part of the money exchange was royalty payments from Novell to MS and according to MS lead lawyer, it was payment for MS IP in Linux.

As far as we know, the agreement does NOT specify what the payments are for. Microsoft may say whatever they want, but if it's not in the agreement, then it's not legally binding. Since Novell disagrees, I think it's safe to assume those terms aren't in the agreement.
> If it walks like a duck...... it is a duck.

Abe, I agree, but I don't think a court would. Nor, given the facts as we know them, do I think they should. There is no valid legal reason to assume that the payments are for any particular purpose. Legally, they are merely an agreed upon exchange between the two companies. They could be because the Novell CEO has the hots for Ballmer for all we or the court knows (hopefully that thought doesn't cause everyone to lose their supper).
Quoting:You didn't read his scenario very carefully, did you?
Oh yes I did and multiple times. He was removing Suse Linux from the picture even though the whole contract was about it. Hear me again, the contract was mainly about Linux, not interoperability nor virtualization like Novel & MS want us to believe.
Quoting:Let me offer a hypothetical not very different from the actual Novell-Microsoft deal:
No hypothetical is necessary when we are dealing with an existing contract.
Quoting:How do you do it without seriously impeding other companies who may wish to test the open-source waters?
You do it exactly what I stated before but with more appropriate language than I used. IANAL, but Lawyers can do that.
Quoting:it would kill the use of GPL'd software in public corporations.
No it wont.
Quoting:I'm betting on workable, but it wouldn't be the first time I've been wrong.
I am glad you still have some confidence in FSF.

Quoting:Umm, Abe, I don't know how to tell you this, but Linux is only one part of Novell's business. It isn't even the biggest part.
Come on Dino, we both know that the old Novell products are D E A D dead. What is left of it is maintenance and support only. If Novell didn't purchase Suse, they would have been dead already.

Quoting:but since they won't have any GPL 3 code to distribute, they won't care.
May be it is good idea to read the previous posts. I am not arguing GPL2, I am taking about GPL3 to fix the loop hole in GPL2 that MS & Novell are taking advantage of. Both RMS & Moglen already said that. Sure they don't care about GPL2 but they will care when the code is GPL3.
Quoting:So, how would either party be violating the proposed GPL 3?
Read again the text I proposed before. "You can't enter an agreement that involves patents and GPLed Software", period. GPLed software has a license and it supersede any agreements involving GPLed software between any companies. It is as clear as a whistle.
Quoting:On Novell's end yes. But Novell would be making no agreement concerning GPL'ed software. They would be agreeing not to sue users of Microsoft Windows and Office. Thus, they would not be infringing the proposed GPL 3 license.
You are saying "Novell agrees not to sue Windows user, in return, MS agrees not sue Linux Users", fine. But the agreement involves GPLed software, you just can't do that because of the above restriction. Is that hard to understand? why wouldn't stand in court?



> I am not arguing GPL2, I am taking about GPL3 to fix the loop hole in GPL2 that MS & Novell are taking advantage of. Both RMS & Moglen already said that.

And I'm pointing out that there doesn't have to be any agreement in place to exploit this "loophole".

> "You can't enter an agreement that involves patents and GPLed Software", period.

There doesn't have to be an agreement.

> You are saying "Novell agrees not to sue Windows user, in return, MS agrees not sue Linux Users", fine.

No. I'm saying that they each, INDEPENDENTLY, state that they won't sue each other's users.

> But the agreement involves GPLed software, you just can't do that because of the above restriction.

In my scenario, THERE IS NO AGREEMENT.

Now, you know and I know that such independent statements won't happen without backdoor negotiations. Fine, prove that in court. Without such proof, there is no agreement to attack, but we'd be in the same situation we are now.

Quoting:And I'm pointing out that there doesn't have to be any agreement in place to exploit this "loophole".
The contract exists already. A "gentlemen" hidden agreement, MS wouldn't do it, Novell wouldn't do it. They can't trust each other. They don't want it hidden. If they declare it in the open, then it is legal and could stand in court.
Quoting:There doesn't have to be an agreement.
Do we still live on plant Earth?
Quoting:No. I'm saying that they each, INDEPENDENTLY, state that they won't sue each other's users.
Come on now, let us be realistic. We are taking about business here. Who would believe either of them?
Quoting:Now, you know and I know that such independent statements won't happen without backdoor negotiations. Fine, prove that in court. Without such proof, there is no agreement to attack, but we'd be in the same situation we are now.
Novel & MS going underground? What is the use? The whole purpose and benefit of it is to let their customers about it.
>Oh yes I did and multiple times

I'm sorry. I misunderstood you, then. You read and simply decided to ignore it.

I must admit, your faith in lawyers is impressive. Having spent a lot of time around a lot of lawyers (including the one who drafted the lotus 1-2-3 license), and having been one myself, I am a bit less worshipful than you.
> A "gentlemen" hidden agreement, MS wouldn't do it...

There's nothing gentlemanly about it. And if it would put to screws to Linux, I guarantee you Microsoft would jump at the chance.

> Who would believe either of them?

Nobody with any sense ever believes Microsoft, but it doesn't matter. An official document declaring such a position would be legally binding on the corporation.

> The whole purpose and benefit of it is to let their customers about it.

And how would such independent announcements not achieve that?
jdixon -

A legally binding agreement requires consideration from both sides. Consideration is a legal term, but, essentially, it means both sides must put something into the pot.

So..they would need an agreement that customers could see and understand. A mutual agreement not to sue would handle the consideration nicely, as each is offering up a promise.

But..it would in no way have to reference any patents, any software, much of anything to be binding.
Quoting:There's nothing gentlemanly about it. And if it would put to screws to Linux, I guarantee you Microsoft would jump at the chance.
No doubt about it. And as a matter of fact, MS are already doing that as Jeremy Allison said. And they are collecting fees for it.

But the fact of the matter is, there is a contract in place between MS & Novell. MS offered Red Hat the same deal as Novel but was rejected. MS also said that they will go it alone whether Red Hat agrees to it or not. So they can and those who are willing to pay, it is up to them to do so. It is their money. Can any one stop another from being stupid? There is nothing that can be done about it unless someone with enough money wants to take them to court for racketeering.
Quoting:And how would such independent announcements not achieve that?
it sure can achieve that, but it wouldn't be as effective as when Novell gives it credibility like they did by entering the agreement.

Hay, I am gland we are having this discussion and I hope, FSF, RMS, Moglen are reading this to use it in putting an iron clad GPL3 together. I believe we ought to sacrifice some for the survival of the whole (FOSS).
> it wouldn't be as effective as when Novell gives it credibility like they did by entering the agreement.

Agreed. But it would still give us the same situation we have.

> Hay, I am gland we are having this discussion and I hope, FSF, RMS, Moglen are reading this to use it in putting an iron clad GPL3 together.

Well, that was my point. Are the current proposals going to be effective or not? Is an effective solution even possible? The FSF has to consider the possibility that a determined effort to undermine the GPL by someone willing to break the law to do so is something that's outside the scope of the license.

Quoting:Agreed. But it would still give us the same situation we have.
Not exactly, now there is still a contract in place. If that didn't exist, yes we would be in the same situation like always was.
Quoting:Is an effective solution even possible?
Yes there is, but we have to strike a balance to make sure we don't lose more than we gain.

The bottom line is, Novell shouldn't have made the agreement. And in a way, it is a good thing they did because it brought up many issue that are better addressed now than later.
Quoting:to do so is something that's outside the scope of the license.
There are other areas that need to be addressed in the GPL3 license that weren't addressed in GPL2. Entering a patent agreement like the one between Novell-MS is one example.
>Yes there is, but we have to strike a balance to make sure we don't lose more than we gain.

Yes sir.

> Entering a patent agreement like the one between Novell-MS is one example.

The Novell agreement is a little trickier than it looks on the surface, and hints as to why a satisfactory license solution may be elusive.

In a way, it wasn't exactly a patent agreement. No licenses were specifically named, and neither side claims to be using the others' patents. I don't recall either side even claiming that they want to use the other's patents. A patent agreement normally covers use of patents. This situation isn't very far removed -- at least in terms -- from my hypothetical of two companies saying "Let's be friends and not sue each other's customers". The agreement does have a hook that a license could work with, and that is the per-copy payments. It seems reasonable to expect that a license could prevent that. It also seems to me that Mcrosoft and Novell could have worked out the exact same agreement, with nearly identical financial terms, that omitted per-copy payments placed themselves outside of what the FSF could reasonably draft against.
Quoting:The Novell agreement is a little trickier than it looks on the surface, and hints as to why a satisfactory license solution may be elusive.
that is why I strongly take it against Novell but not MS. MS is what it is, but Novell is supposed to be a FOSS user, participator, advocate and supporter. They intentionally made it so opaque, vague, and elusive.
> In a way, it wasn't exactly a patent agreement.

I view this as Novell providing patent protection to its customers. I honestly don't know the answer to this, but wouldn't GPL 3 have to be written in such a way as to prevent patent protection? How would you write a license in such a way that you don't eliminate all forms of patent protection? Wouldn't such a license require that all companies using Linux are on their own if they get sued, such that Microsoft could threaten a suit (directly or indirectly as with SCO) against any small business using Linux, and that small business would be on its own?
>ut wouldn't GPL 3 have to be written in such a way as to prevent patent protection?

The question is how do you do that without becoming unusable?

It certainly must create in businesses the image of a bunch of hippie/commie wackos that anybody would see evil in seeking to protect your business against suit by a nasty animal like Microsoft.
> It certainly must create in businesses the image of a bunch of hippie/commie wackos that anybody would see evil in seeking to protect your business against suit by a nasty animal like Microsoft.

So what do they think about a covenant that can be canceled at any time, isn't perpetual, expires in a couple years, isn't transferable, and implies guilt? Or are businesses routinely in the habit of paying for nothing but liability?

Btw, the 90's ended a few years ago, as did Microsoft propaganda of us being unamerican, cancerous, communist hippies. Today, we have the previously unbelievable reality of the likes of Sun's CEO gushing about the GPL3. Times have changed.
swbrown -

Ummm....

From a PR perspective, telling business execs that you are determined to keep them from protecting their business is not a good way to win friends and influence people.

And..WRT Sun's CEO...

If he's gushing, I'm afraid.
swbrown -

Went back to the report on Sun making nice with GPLV3.

Hmmmm.

They are dual-licensing. They already indemnify their customers. They already have technology licensing agreements with Microsoft. They already have received hundreds of millions of dollars from Microsoft.

For them, GPLV3 makes a great wedge.
> From a PR perspective, telling business execs that you are determined to keep them from protecting their business is not a good way to win friends and influence people.

So how do you win friends and influence people by telling them they're now paying the royalty fee on each copy for an effectively non-binding defense that's likely a liability? I'd think to 'win friends' you'd have to /actually/ protect your customers, not force them to buy snake-oil. The latter seems kinda abusive.

Also, 'from a PR perspective', it probably doesn't look all that great when negotiating a deal to have to answer questions as to why many of your 'suppliers' currently see you as a pariah. I'd imagine for the client it'd be a bit like walking through picketing teamsters to hire a shipping company.

> For them, GPLV3 makes a great wedge.

He's planning to make Java, their crown jewel, available by it in addition to its current licenses, and wants OpenSolaris to go the same way, which certainly speaks to his confidence that the GPL3 won't eat his babies. And what extremely valuable (tasty? This analogy kinda breaks down) babies they are. The ideology isn't being hidden in a back room, and multi-billion dollar corporations are ok with it. Times have changed.
>o how do you win friends and influence people by telling them they're now paying the royalty fee on each copy for an effectively non-binding defense that's likely a liability?

What do tangerines have to do with carp?

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post