all 8 comments

[–]Myocarditis-Man[S] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (5 children)

So yeah, they're breaking production systems now. This is not a bleeding-edge development or experimental environment. It is supposed to be reliable and stable. Honestly I'm tired of this bullshit squabble between a select few kernel developers trying to sabotage NVidia and fuck over us users. It has not been determined by any court of law that use of proprietary modules breaches any license, so from my perspective, what you are doing, is straight-up sabotage, trolling and subterfuge, and it's really no different than some punk-ass teenager going around breaking other peoples' windows.

Therefor, the Linux maintainers should ban and reject these select few developers from submitting further patches to the kernel, as has been done with University of Minnesota. To the developers who are breaking this, you are obviously not that high and mighty when it comes to free software ideals, otherwise you would not have allowed your code to make it into proprietary corporate shit-boxes that are swimming in closed source garbage/DRM such as smart TVs, set-top boxes and Android phones.

Patches (not) welcome.

References: https://www.theverge.com/2021/4/22/22398156/university-minnesota-linux-kernal-ban-research

[–][deleted]  (1 child)

[removed]

    [–]Canbot 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (2 children)

    It is not about being high and mighty, those developers likely work for Nvidia.

    [–]DUMB-FUCK 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

    It is not about being high and mighty, those developers likely work for Nvidia.

    IT IS BETTER TO BE MIGHTY HIGH THAN TO BE HIGH AND MIGHTY.

    https://youtu.be/2PLC_cBJwk4

    [–]Myocarditis-Man[S] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

    I think you misunderstand the situation. The change implemented in the production kernel version, breaks drivers for all Nvidia cards. Why in the world would Nvidia want to do that? I could maybe understand Nvidia breaking compatibility for older Nvidia cards, to sell the latest ones, but there is simply no way Nvidia would want what is going on here; because even their latest cards won't work.

    Also I think the kernel developers who push these changes that are designed to sabotage Nvidia and their customers need to consider that Linux may be used in e.g. critical medical equipment. If they want to humiliate Nvidia, they can make a CUDA competitor that is mature and widely supported, but instead, vandalizing other peoples' stuff seems to be easier for them to do.

    Again, the breakage on display here is not a bug or mistake, it's a "feature", coded by someone to disrupt functionality on others' systems.

    [–]Myocarditis-Man[S] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

    It would be so nice if Debian KFreeBSD had finished development, and we could just do "apt-get install kernel-freebsd" on our existing installations, while giving the people who are doing this the middle finger.

    Maybe that's why they want to diverge Linux and BSD so much with stuff like Systemd and Wayland. Making it harder to escape.

    [–]binaryblob 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

    Just install Guix and abandon Debian like any sane person.