233
submitted 6 days ago* (last edited 6 days ago) by cypherpunks@lemmy.ml to c/linux@lemmy.ml
top 50 comments
sorted by: hot top controversial new old
[-] borari@lemmy.dbzer0.com 116 points 6 days ago* (last edited 6 days ago)

Holy shit that got spicy. I was not expecting a Ukrainian and a Serb to start bickering back and forth while stacking racks over the level of support a country gave to the Nazis in WW2 on a kernel mailing list like they were in the comments here on Lemmy.

I get that tensions are high, and for many people the geopolitical reality is their homes being used as cover on an active front line, but like bro your actual fucking name is attached to these messages. At least I keep my most unhinged shit on a semi-anonymous platform. They need to lock it the fuck up.

Edit - jfc, a few messages later somebody comes in with something along the lines of “Taiwan isn’t a country, it’s part of China. When reunification comes sanctions won’t be appropriate against Chinese entities.” Is Lemmy just a front end for this mailing list and I had no idea this entire time?

[-] OsrsNeedsF2P@lemmy.ml 47 points 6 days ago

I thought you were joking, but yup they actually started quizzing eachother on WW2.

It's not the end of Linux by any means, but that's gonna be hard to work together afterwards

[-] IrritableOcelot@beehaw.org 26 points 6 days ago

Jeeeeez that was a lot. I get the sense that the kernel has worked as well as it has because people saw it as separate from geopolitics and so didnt discuss them...now that politics has wedged its way in I feel like it may have opened that door permanently.

load more comments (1 replies)
[-] granolabar@kbin.melroy.org 43 points 6 days ago

At least I keep my most unhinged shit on a semi-anonymous platform.

🔥

[-] Z_Poster365@hexbear.net 16 points 6 days ago

Taiwan isn’t a country, it’s part of China

This is not a hot take, it's the official position of the United States of America and 90% of the population of the world. Those who say Taiwan is its own country are radical fringe separatists.

https://en.wikipedia.org/wiki/One_China#United_States_policy

[-] umbrella@lemmy.ml 6 points 5 days ago* (last edited 5 days ago)

this is great 🍿🍿🍿

load more comments (14 replies)
[-] JustMarkov@lemmy.ml 63 points 6 days ago

I mean, if Linus had given a more professional commentary, this whole drama definitely wouldn't be so loud, but we have what we have.

[-] lud@lemm.ee 9 points 5 days ago

That applies to most of the drama surrounding Linux.

load more comments (1 replies)
[-] dessalines@lemmy.ml 46 points 6 days ago* (last edited 6 days ago)

Damn there are a surprising number of maintainers that are comrades and not taking this lying down from the western supremacist cohort.

Linus opened up a massive can of worms and turned this into a geopolitical conflict by acting like a baby.

This comment by Hantong Chen is great:

Hi James,

Here's what Linus has said, and it's more than just "sanction."

Moreover, we have to remove any maintainers who come from the following countries or regions, as they are listed in Countries of Particular Concern and are subject to impending sanctions:

  • Burma, People’s Republic of China, Cuba, Eritrea, Iran, the Democratic People’s Republic of Korea, Nicaragua, Pakistan, Russia, Saudi Arabia, Tajikistan, and Turkmenistan.
  • Algeria, Azerbaijan, the Central African Republic, Comoros, and Vietnam.

For People’s Republic of China, there are about 500 entities that are on the U.S. OFAC SDN / non-SDN lists, especially HUAWEI, which is one of the most active employers from versions 5.16 through 6.1, according to statistics. This is unacceptable, and we must take immediate action to address it, with the same reason.

load more comments (12 replies)
[-] scarcity_of_the_self@hexbear.net 47 points 6 days ago

Getting whiplash between "haha Russian invaders and bots get fucked!!!! Finland!!!! Wooooo Finland!!!!!!" and "ah, we take no pleasure in doing this, our hands are tied"

Maybe the professional communications and Mastodon bubble Linus has been posting in led him to believe everyone in the world hates Russians now and that would be really well received

[-] dessalines@lemmy.ml 20 points 6 days ago

Theodore T'so especially:

first comment:

The question of why a particular country has decided to sanction Russia and not Ukraine, and why a country has decided to support one country versus another, whether it's Germany, France, and Poland sending tanks and armored vehicles to Ukraine, or North Korea sending artillary shells to Russia, is not up to the Linux development commuity.

next comment:

Sanctions are imposed by Governments


for example, the US, European, Japan, Switzerland, Norway, etc. Not Linux developers, nor Russian troll farms, nor Russia's useful idiots on the internet. It's not up to anyone on this mail thread.

[-] ryannathans@aussie.zone 44 points 6 days ago* (last edited 6 days ago)

What were Linus comments that precipitated this?

The rage comes from LF actions and Linus words. All they had to do was to say: Thank you people for your contribution but we have no other choice, this is the law. But they did quite the opposite and Linus showed his true ugly white western supremacy face for all to see. That is the cause of the rage.

[-] tekato@lemmy.world 45 points 6 days ago

Ok, lots of Russian trolls out and about.

It's entirely clear why the change was done, it's not getting reverted, and using multiple random anonymous accounts to try to "grass root" it by Russian troll factories isn't going to change anything.

And FYI for the actual innocent bystanders who aren't troll farm accounts - the "various compliance requirements" are not just a US thing.

If you haven't heard of Russian sanctions yet, you should try to read the news some day. And by "news", I don't mean Russian state-sponsored spam.

As to sending me a revert patch - please use whatever mush you call brains. I'm Finnish. Did you think I'd be *supporting* Russian aggression? Apparently it's not just lack of real news, it's lack of history knowledge too.

load more comments (9 replies)
[-] Cysioland@lemmygrad.ml 31 points 6 days ago* (last edited 6 days ago)

https://www.phoronix.com/news/Linus-Torvalds-Russian-Devs

tl;dr: anyone who disagrees is a russian troll or a useful idiot, according to the linux man

load more comments (1 replies)
[-] NeoNachtwaechter@lemmy.world 53 points 6 days ago

It is not good for the kernel and it's team to suddenly have to kowtow to Usamerican politics.

[-] mkwt@lemmy.world 86 points 6 days ago

The reality is that the Linux Foundation is in the United States, and Linus is a naturalized US citizen who lives in Oregon (at least on Wikipedia). So they both will have to pay attention to avoid transacting business with individuals and companies on the SDN list. That is the law in the United States.

[-] dessalines@lemmy.ml 37 points 6 days ago

What an extremely dangerous place to domicile such an important project.

[-] lambalicious@lemmy.sdf.org 3 points 4 days ago

Maybe it's time to fork the Linux Foundation and fix those two problems.

[-] treadful@lemmy.zip 34 points 6 days ago

And it can cost you up to 30 years for breaking it. I'd listen to my lawyers too.

[-] j4k3@lemmy.world 18 points 6 days ago

Kreg moved to Europe, last I heard. So at least the heir apparent is in a region with better potential international diplomacy and neutrality.

[-] 5714@lemmy.dbzer0.com 31 points 6 days ago

Inheritance wars wasn't something on my FOSS list...

load more comments (1 replies)
load more comments (1 replies)
load more comments (18 replies)
[-] RightEdofer@lemmy.ca 17 points 6 days ago

Suddenly? Linux entities have always had to follow the rules of the country they exist in. A kernel isn’t a sovereign nation no matter how loud the what-about army becomes.

[-] isVeryLoud@lemmy.ca 29 points 6 days ago

This will be a nothing burger in 6 months

[-] j4k3@lemmy.world 17 points 6 days ago

Wow:

Oleksiy Protas

P.S. "Don't feed the trolls"

Don't you worry. Our friend here tried to reply to this message, he did so twice in fact with slightly different wording, but it was full of political rage and tu quoque so I assume he fell victim to the spam filter thanks to you special counter-baiting operation so to speak.

That aside, I did a very superficial search and it seems that the original author had already had a pull being rejected on the grounds it was coming straight from his Baikal credentials. It's a real pity that an apparently very able engineer is just playing pretend despite knowing full well why is it so that LF migh not want to be associated with Baikal in any way.

::: spoiler Serge Semin

Hello Linux-kernel community,

I am sure you have already heard the news caused by the recent Greg' commit 6e90b675cf942e ("MAINTAINERS: Remove some entries due to various compliance requirements."). As you may have noticed the change concerned some of the Ru-related developers removal from the list of the official kernel maintainers, including me.

The community members rightly noted that the quite short commit log contained very vague terms with no explicit change justification. No matter how hard I tried to get more details about the reason, alas the senior maintainer I was discussing the matter with haven't given an explanation to what compliance requirements that was. I won't cite the exact emails text since it was a private messaging, but the key words are "sanctions", "sorry", "nothing I can do", "talk to your (company) lawyer"... I can't say for all the guys affected by the change, but my work for the community has been purely volunteer for more than a year now (and less than half of it had been payable before that). For that reason I have no any (company) lawyer to talk to, and honestly after the way the patch has been merged in I don't really want to now. Silently, behind everyone's back, bypassing the standard patch-review process, with no affected developers/subsystem notified - it's indeed the worse way to do what has been done. No gratitude, no credits to the developers for all these years of the devoted work for the community. No matter the reason of the situation but haven't we deserved more than that? Adding to the GREDITS file at least, no?..

I can't believe the kernel senior maintainers didn't consider that the patch wouldn't go unnoticed, and the situation might get out of control with unpredictable results for the community, if not straight away then in the middle or long term perspective. I am sure there have been plenty ways to solve the problem less harmfully, but they decided to take the easiest path. Alas what's done is done. A bifurcation point slightly initiated a year ago has just been fully implemented. The reason of the situation is obviously in the political ground which in this case surely shatters a basement the community has been built on in the first place. If so then God knows what might be next (who else might be sanctioned...), but the implemented move clearly sends a bad signal to the Linux community new comers, to the already working volunteers and hobbyists like me.

Thus even if it was still possible for me to send patches or perform some reviews, after what has been done my motivation to do that as a volunteer has simply vanished. (I might be doing a commercial upstreaming in future though). But before saying goodbye I'd like to express my gratitude to all the community members I have been lucky to work with during all these years. Specifically:

NTB-folks, Jon, Dave, Allen. NTB was my starting point in the kernel upstream work. Thanks for the initial advices and despite of very-very-very tough reviews with several complete patchset refactorings, I learned a lot back then. That experience helped me afterwards. Thanks a lot for that. BTW since then I've got several thank-you letters for the IDT NTB and IDT EEPROM drivers. If not for you it wouldn't have been possible.

Andy, it's hard to remember who else would have given me more on my Linux kernel journey as you have. We first met in the I2C subsystem review of my DW I2C driver patches. Afterwards we've got to be frequently meeting here and there - GPIO, SPI, TTY, DMA, NET, etc, clean/fixes/features patch(set)s. Quite heat discussions in your first reviews drove me crazy really. But all the time we managed to come up with some consensus somehow. And you never quit the discussions calmly explaining your point over and over. You never refused to provide more detailed justification to your requests/comments even though you didn't have to. Thanks to that I learned how to be patient to reviewers and reviewees. And of course thank you for the Linux-kernel knowledges and all the tips and tricks you shared.

Linus (Walleij), after you merged one of my pretty much heavy patchset in you suggested to me to continue the DW APB GPIO driver maintaining. It was a first time I was asked to maintain a not-my driver. Thank you for the trust. I'll never forget that.

Mark, thank you very much for entrusting the DW APB SSI driver maintenance to me. I've put a lot of efforts into making it more generic and less errors-prune, especially when it comes working under a DMA-engine control or working in the mem-ops mode. I am sure the results have been beneficial to a lot of DW SPI-controller users since then.

Damien, our first and last meeting was at my generic AHCI-platform and DW AHCI SATA driver patches review. You didn't make it a quick and easy path. But still all the reviews comments were purely on the technical basis, and the patches were eventually merged in. Thank you for your time and experience I've got from the reviews.

Paul, Thomas, Arnd, Jiaxun, we met several times in the mailing list during my MIPS P5600 patches and just generic MIPS patches review. It was always a pleasure to discuss the matters with such brilliant experts in the field. Alas I've spent too much time working on the patches for another subsystems and failed to submit all the MIPS-related bits. Sorry I didn't keep my promise, but as you can see the circumstances have suddenly drawn its own deadline.

Bjorn, Mani, we were working quite a lot with you in the framework of the DW PCIe RC drivers. You reviewed my patches. I helped you to review another patches for some time. Despite of some arguing it was always a pleasure to work with you. Mani, special thanks for the cooperative DW eDMA driver maintenance. I think we were doing a great work together.

Paolo, Jakub, David, Andrew, Vladimir, Russell. The network subsystem and particularly the STMMAC driver (no doubt the driver sucks) have turned to be a kind of obstacle on which my current Linux-kernel activity has stopped. I really hope that at least in some way my help with the incoming STMMAC and DW XPCS patches reviews lightened up your maintainance duty. I know Russell might disagree, but I honestly think that all our discussions were useful after all, at least for me. I also think we did a great work working together with Russell on the DW GMAC/QoS ETH PCS patches. Hopefully you'll find a time to finish it up after all.

Rob, Krzysztof, from your reviews I've learned a lot about the most hardwary part of the kernel - DT sources and DT-bindings. All your comments have been laconic and straight to the point. That made reviews quick and easy. Thank you very much for that.

Guenter, special thanks for reviewing and accepting my patches to the hwmon and watchdog subsystems. It was pleasure to be working with you.

Borislav, we disagreed and argued a lot. So my DW uMCTL2 DDRC EDAC patches even got stuck in limbo for quite a long time. Anyway thank you for the time you spent reviewing my patches and trying to explain your point.

  • Borislav, it looks like I won't be able to work on my Synopsys EDAC patchsets anymore. If you or somebody else could pick them up and finish up the work it would be great (you can find it in the lore archive). The patches convert the mainly Zynq(MP)-specific Synopsys EDAC driver to supporting the generic DW uMCTL2 DDRC. It would be very beneficial for each platform based on that controller.

Greg, we met several times in the mailing lists. You reviewed my patches sent for the USB and TTY subsystems, and all the time the process was straight, highly professional, and simpler than in the most of my other case. Thank you very much for that.

Yoshihiro, Keguang, Yanteng, Kory, Cai and everybody I was lucky to meet in the kernel mailing lists, but forgot to mention here. Thank you for the time spent for our cooperative work on making the Linux kernel better. It was a pleasure to meet you here.

I also wish to say huge thanks to the community members trying to defend the kicked off maintainers and for support you expressed in these days. It means a lot.

A little bit statics of my kernel-work at the end:

Signed-off patches: 518 Reviewed and Acked patches: 253 Tested patches: 80

...

Best Regards, -Serge(y)

load more comments
view more: next ›
this post was submitted on 25 Oct 2024
233 points (94.6% liked)

Linux

47946 readers
1731 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS