lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.0.98.0706151322070.14121@woody.linux-foundation.org>
Date:	Fri, 15 Jun 2007 13:34:03 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	David Woodhouse <dwmw2@...radead.org>
cc:	Daniel Hazelton <dhazelton@...er.net>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Alexandre Oliva <aoliva@...hat.com>, Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>, david@...g.hm,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3



On Fri, 15 Jun 2007, David Woodhouse wrote:
> > 
> > What is a DVD? It's just a "blob" of a UDF image, potentially containing 
> > the Linux kernel.
> > 
> > How is that different from a "blob" of some other kind of image (say, a 
> > cramfs or similar image) on a rom?
> > 
> > What makes UDF so different from cramfs? What makes a DVD so different 
> > from a ROM chip? Why would copyright law care about one and not the other?
> 
> The differences are subtle, but they do exist. They're not really about
> whether it's iso9660 or cramfs; it's about whether what you put on them
> is a coherent work in its own right or just a bunch of bits which happen
> to be thrown together onto the same medium.

I think that's a somewhat valid argument, although I'm not really sure 
whether there is any difference between, say, a Fedora 7 "livecd", and a 
router with a cramfs filesystem in rom.

Both really work the same way, and both really are very much targeted 
towards a specific hardware platform.

Yes, it's true that a small router migth be a more *coherent* hardware 
platform than the Fedora 7 livecd is, but that's more a factor of the wild 
and crazy PC hardware culture than of the small router.

For example, what about a livecd for PPC-based hardware? Those tend to be 
much more uniform (read: I think the livecd's generally work on mac 
clones).

So it's a question of degrees of separation. Does it make a difference 
that some of these embedded images work across a whole range of (rather 
similar, but still.. not identical) routers? 

I don't really have any point, except that there is no real *technical* 
difference, and in many respects the only difference in the end really 
seems to be about "intended target device or audience" rather than 
anything else.

How can you make hard licensing decisions in situations like that? I don't 
think you really can. In fact, the OSI rules even forbid making licensing 
decisions based on things that get rather close to the differences you are 
describing (both the "not specific to a product" and "license must not 
discriminate against fields of endeavor").

It's also really really *hard* to make a choice based on a gradual scale. 
Where do you put the limit? Wherever you put it, it's going to be 
arbitrary. Is that really a good thing?

So I would at least *personally* suggest that people not look into the 
license for these kinds of things, and also that you really need to have a 
very specific case, and just basically put it in front of a judge.

At some point, *somebody* has to decide in a gray area, and I'm not saying 
that a judge is really _technically_ any better really to decide the 
issue, but at least he is hopefully _independent_ of both parties, so when 
a judge makes an arbitrary decision, the "arbitrariness" is hopefully at 
least somewhat "fair".

Hmm? 

			Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ