Linus Torvalds

https://social.kernel.org/users/torvalds

Public Key

npub14knehrr0x8hur9r33af36y65r0cmar09yjwlklnj8dnu9dt6jqwqkgg4dc

NIP-05 Address

Profile Code

nprofile1qqs2mfum33hnrm7pj3cc75cazd2phud73hjjf80m0eerke7zk4afq8qpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg5waehxw309aex2mrp0yhxgctdw4eju6t05s7al6

Publishing to

relay.primal.net

relay.damus.io

nos.lol

Author Public Key

npub14knehrr0x8hur9r33af36y65r0cmar09yjwlklnj8dnu9dt6jqwqkgg4dc

Show more details

Last Notes

2025-12-24 21:58:27 UTC

GPLv2 affirmation...
I don't generally post here as people have probably noticed, but here's a pdf of a recent court ruling, and this turns out to be the easiest way for me to link to a copy of it, since I don't really maintain any web presence normally and I don't want to post pdf's to the kernel mailing lists or anything like that.
And the reason I want to post about it, is that it basically validates my long-held views that the GPLv2 is about making source code available, not controlling the access to the hardware that it runs on.
The court case itself is a mess of two bad parties: Vizio and the SFC. Both of them look horribly bad in court - for different reasons.
Vizio used Linux in their TVs without originally making the source code available, and that was obviously not ok.
And the Software Freedom Conservancy then tries to make the argument that the license forces you to make your installation keys etc available, even though that is not the case, and the reason *why* the kernel is very much GPLv2 only. The people involved know that very well, but have argued otherwise in court.
End result: both parties have acted badly. But at least Vizio did fix their behavior, even if it apparently took this lawsuit to do so. I can't say the same about the SFC.
Please, SFC - stop using the kernel for your bogus legal arguments where you try to expand the GPLv2 to be something it isn't. You just look like a bunch of incompetent a**holes.
The only party that looks competent here is the judge, which in this ruling says
> Plaintiff contends the phrases, “machine-readable” and “scripts used to control compilation and installation” support their assertion in response to special interrogatory no. 4 that Defendant should “deliver files such that a person of ordinary skill can compile the source code into a functional executable and install it onto the same device, such that all features of the original program are retained, without undue difficulty.”
>
> The language of the Agreements is unambiguous. It does not impose the duty which is the subject of this motion.
>
> Read as a whole, the Agreements require Vizio to make the source code available in such a manner that the source code can be readily obtained and modified by Plaintiff or other third parties. While source code is defined to include “the scripts used to control compilation and installation,” this does not mean that Vizio must allow users to reinstall the software, modified or otherwise, back onto its smart TVs in a manner that preserves all features of the original program and/or ensures the smart TVs continue to function properly. Rather, in the context of the Agreements, the disputed language means that Vizio must provide the source code in a manner that allows the source code to be obtained and revised by Plaintiff or others for use in other applications.
>
> In other words, Vizio must ensure the ability of users to copy, change/modify, and distribute the source code, including using the code in other free programs consistent with the Preamble and Terms and Conditions of the Agreements. However, nothing in the language of the Agreements requires Vizio to allow modified source code to be reinstalled on its devices while ensuring the devices remain operable after the source code is modified. If this was the intent of the Agreements, the Agreements could have been readily modified to state that users must be permitted to modify and reinstall modified software on products which use the program while ensuring the products continue to function. The absence of such language is dispositive and there is no basis to find that such a term was implied here. Therefore, the motion is granted.
IOW, this makes it clear that yes, you have to make source code available, but no, the GPLv2 does *not* in any way force you to then open up your hardware.
My intention - and the GPLv2 - is clear: the kernel copyright licence covers the *software*, and does not extend to the hardware it runs on. The same way the kernel copyright license does not extend to user space programs that run on it.
https://media.social.kernel.org/media/7423738b6977f73678ca7f996227fecf171a09d691f1a0f737e4d8e7e556b850.pdf

2023-07-09 21:28:49 UTC

I'm clearly a master of SEO.
When I google for "cold dark place filled with sadness and despair" right now (with the quotes), google gives me exactly one result - my Linux kernel github repository.
I will call my new hobby "Reverse Emo Googlewhacking".
You're welcome.

2023-03-14 22:51:11 UTC

Random first trial post: today, March 14th, is the 29th anniversary of the Linux 1.0 announcement.
Of course, there are other arguably more important dates in Linux history, but this is *one* of them.