4 ms·
I do not see on what grounds you can classify in this case Linux as a victim and NVIDIA as an attacker. There are many people who want to use on their computer
by adrian_b 3y ago
I do not see on what grounds you can classify in this case Linux as a victim and NVIDIA as an attacker.
There are many people who want to use on their computers both the Linux kernel and NVIDIA GPUs. NVIDIA maintains their Linux drivers only for the benefit of the NVIDIA GPU owners who desire this, they do not get any direct revenue from this activity.
So at most you might say that Linux is a victim of the GPU owners that want to use Linux, despite the fact that some kernel developers hate the owners of NVIDIA GPUs and try to discourage them to use Linux.
The problem is that Linux does not have a clear license that would enumerate what Linux users are allowed to do, and even if it would have such a list, that would be somewhat ridiculous, because one of the main claimed objectives of the Linux development has always been that its purpose is to remove the restrictions imposed by the commercial operating systems.
If Linux would have a license forbidding the Linux users to use it in weapons of mass destruction, that could be justifiable on moral grounds. On the other hand, a license that would forbid the Linux users to buy NVIDIA GPUs or any other piece of hardware cannot have any justification. While some kernel developers did not attempt to do something so pathetic, they still do not find anything better to do than to find new ways to make the life harder for those Linux users that have good reasons for using something like NVIDIA GPUs or the ZFS file system.
It is normal for the kernel developers to not do anything to contribute to proprietary device drivers, but it is ugly and mean to try to sabotage them by actively preventing them to link to the symbols that must necessarily be used by a device driver in order to accomplish its function.
- TheDong 3y ago> I do not see on what grounds you can classify in this case Linux as a victim and NVIDIA as an attacker. The linux kernel is respecting it's user's rights to know what code they run, and to be able to modify it. nvidia is not extending that courtesy to their users, even though the linux kernel's possibly-legally-enforceable copyright insists that nvidia has to extend such a right. nvidia can release their source code as GPL if they want to use the GPL parts of the kernel. Are you just as mad at nvidia for having a proprietary driver but not letting users apply patches to the driver? I assure you, the license nvidia distributes its drivers under is much more restrictive than linux's GPL license. Like, if you're mad that the linux developers are making it harder for nvidia to violate linux's license and make a derivative work of the linux kernel, surely you're even madder that nvidia's developers have made it even harder for anyone to make a derivative work of nvidia's proprietary driver blobs, right?
- adrian_b 3y agoI do not agree with the theory that linking one program to another makes the former a derivative of the latter, therefore I do not agree that a kernel module is a derivative of the kernel, when it just uses the interfaces that must be used to accomplish its function. If this theory, which is the only point of disagreement between me and Richard M. Stallman, would be accepted to be true, then what would stop Microsoft to claim that every program that has ever been written to run on Windows is the property of Microsoft? When there are two hardware vendors, one who offers open-source device drivers and one that offers proprietary drivers, I would always choose the one with open-source device drivers. Unfortunately, in the case of NVIDIA there are applications for which no other vendor attempts to provide competitive products, so there is no alternative choice. Therefore it does not matter if I would be "mad" at NVIDIA, as that could change nothing. On the other hand, I am "mad" at this kind of kernel developers, because I do not accept that they have any right to dictate to the Linux users what kind of hardware they should buy. Obviously, they should not support NVIDIA, but inventing methods to sabotage the Linux users that have NVIDIA GPUs is not a justifiable activity.
- TimeBearingDown 3y agoIf a kernel module is not derivative of the kernel, what use does it then serve once separated from any Linux GPL code?
- adrian_b 3y agoThis argument is lame. If a Windows program is not a derivative of the Win32 libraries owned by Microsoft, what use does it serve once separated from the Microsoft libraries? If an Android application is not a derivative of the Android OS owned by Google, what use does it then serve once separated from the Android base system? If any C program that has ever been written (except those written for freestanding environments) is not a derivative of the C Standard Library, what use does it serve once separated from libc? If your argument were right, with the exception of the very small number of programmers who write programs for bare-metal embedded systems, all the other programmers have written all their lives only derivative programs, so none of them (or of their employers) has any right to claim copyright ownership on what they have written.
- matkoniecz 3y ago> I do not see on what grounds you can classify in this case Linux as a victim and NVIDIA as an attacker. NVIDIA deliberately violates GPL license. > The problem is that Linux does not have a clear license are you sure about that?
- adrian_b 3y agoAs one who has used only Linux on all desktops and laptops for more than two decades, I am pretty sure that Linux does not have a written license that enumerates what a Linux user can do with the computer on which Linux is installed, e.g. whether they may use NVIDIA GPUs. The GPL is not that kind of license. While GPL includes some use restrictions, they are logically contradictory. GPL says: "This License explicitly affirms your unlimited permission to run the unmodified Program." So anyone can run the Linux kernel without any restrictions imposed by GPL. The GPL then has a convoluted specification of how it should forbid a GPL program to be combined with other programs, so that copies of the combination would be transferred to others. However those restrictions do not apply to kernel modules like those distributed by NVIDIA, which are not "combined" with the GPL Linux kernel until the end user loads the NVIDIA kernel module. Because the GPL cannot be applied to such kernel modules, the anti-NVIDIA kernel developers take advantage of the fact that when a kernel module is loaded dynamically, in order to work, it must discover the entry addresses for the kernel symbols, exactly like a user-mode executable must discover the entry addresses for the libc shared library. So they attempt to make difficult for the NVIDIA module to obtain the addresses for the kernel symbols that it needs. This is exactly like if in user space the libc shared library would attempt to not provide e.g. the entry address of "printf", if it would not like the name of the executable file from which "printf" is invoked. If anyone breaks the GPL, these kernel developers break it, because instead of providing "unlimited permission to run", which means "unlimited permission to" invoke any of the interfaces provided by the kernel, they attempt to hide many of the interfaces when they discover that the Linux users own NVIDIA GPUs, with the purpose of crippling the performance of such GPUs.
- Zigurd 3y agoIf a driver with intrusive telemetry included with a product made in Russia or China was a widely used binary blob in Linux installations, the banhammer would come down pretty hard on that and kernel devs would be heroes for protecting the public, including security-sensitive users. Sauce, gander, goose.