Honestly, with this response although I think he didn’t deserve all of that from Linus, he did deserve quite a bit of it. So condescending and smug to application developers that actually make the user experience of Linux a good thing.
Okay, I agree that this is a really dickish way to respond to a dev, and I can see Torvald’s message being as much an olive branch to app devs as it was a thorough humbling of the maintainer. Still wouldn’t call it professional, but… I get it.
Seeing the rest of the thread really contextualizes Linus’ anger.
Only seeing the message from Linus makes him look like a dick. But when you see that he’s responding to someone deflecting blame and being a shithead to the guy trying to report a problem and provide a suggested fix, the aggressive response seems more justifiable.
Yes. I did not include patch from first person in screenshot because I thought it would make it too boring to read. But it kinda adds even more to context.
Replying to “I get this regression with KDE on this system caused by this commit and here how I fixed it” with “lol, pulseaudio sucks, opensuse sucks” of course will make Linus angry and he will reply not only “no u”, but also “and here’s why”.
Treat your volunteers well, or why should they continue volunteering?
Kernel maintainers have plenty of other opportunities.
I don’t know if they are volunteering or being paid. The other person said they are being paid.
Either way, no one deserves being talked down to like that, even if they made a mistake. It’s a matter of respect and self-respect. And as a skilled person like a kernel developer, it should be trivially easy to find other work in a more appropriate environment.
That being said, maybe I’m missing something. Torvalds has been known to be like that for a long time (although that seems to be over now). And still, Linux has been developed over decades. So apparently, skilled people flocked around Torvalds, or maybe rather his project. Not entirely sure why, but I’m taking it as a hint I might be missing something.
Generally speaking: not these days, and not for a long long time. Mauro, for instance, worked for Red Hat at the time. It’s of course possible to be unpaid and work for Linux, but I believe it’s much more likely that one is employed by a big tech corpo and they maintain the kernel as part of their work.
The fact that people here value feelings and pretty expressions more over quality, standards and passion shows exactly how human civilization will decline into mediocrity and sickness.
Your subpar ability to understand that the self fellating anger in that email is in no way something that generates quality and standards says much more about the decline to mediocrity.
Nonsense. It’s simply that that kind of conduct is deeply unprofessional and reflects poorly on Linus. He could have said the exact same things about the issues with that patch without the obscenities and personal attacks.
I’ve worked as a software team lead for nearly 30 years, you do not get the best out of people by belittling and berating them.
I find it ironic that Linus’s explanation for ENOENT being invalid for an ioctl given its meaning of “No such file or directory”, while simultaneously ioctl can return ENOTTY when using a mismatched device fd despite the error meaning “Not a typewriter.”
That’s why the non-parentheses number is zero for all seeded torrents. In parentheses number is “hey I’m here”. Out of parentheses number is “hey I’m here. Let me in.”
For actively downloading torrents they’re an indication of connection health. If there’s 150 announced seeders but you only open a connection to one or two of them, you might have a network problem.
It’s the other way around; you connect to seeders.
In the example of 2 (3), there are 3 total seeders and you’re connected to 2 of them.
Although in your screenshot, you’re at 100%, so you’re not connected to any seeders at the moment and are, yourself, a seeder. You have peers (leechers) connecting to you. Same principle applies; in an example of 2 (7), there are 7 peers in total, and 2 of them are actively leeching off you.
Interesting take. I’ve always posited that the earth and nature will survive but I never included people in that. It’d probably be a reversion to nomadic and hunter/gatherer tribes to start. The question is would it take as long to rebuild? And would it follow the same path again?
Humanity will survive; society as we know it, or in any form higher than nomadic tribes, not so much.
Glad to know Reddit moderator behavior has carried over, it’s just like old times!
people really seem to have a boner for the apocalypse, from what i’ve seen the reality is that poor people will as always get shafted and most people in developed countries will be mostly fine albeit with a lot of change and maybe having to move if you live in a flooding-prone area.
It’s soo weird when you a lot of people have weird fantasies about the apocalypse. It gets downright terrifying when you start to mix in nationalism in it.
I hate to break it everyone, most of us are not going to survive the apocalypse. The only ones who are going to survive are the ones that I can survive and were lucky enough to be in the right place at the wrong time. It won’t matter that you have a bunker full of supplies, what the fuck are you going to do when your supplies run out? Or someone with a bigger gun comes? All that gold and crypto you bought for the apocalypse won’t mean shit.
Yeah I kind of realised that the instructions assumed I had already upgraded, will try to keep track of new updates better in the future. So for sake of completion here’s how I solved it in the end:
Ran into conflicts: file /usr/lib64/libopenh264.so.2.3.1 conflicts between attempted installs of openh264-2.3.1-2.fc38.x86_64 and noopenh264-0.1.0~openh264_2.3.1-2.fc38.x86_64
Solved it with exclusion: sudo dnf -v system-upgrade download --releasever=38 --allowerasing --exclude=openh264.x86_64
Fonts and glitches are gone, got some broken deps instead. So if anyone got a suggestion for that instead let me know. Otherwise I’ll do as it suggest –best --allowerasing’ and see what else breaks:
<span style="color:#323232;">Problem: The operation would result in removing the following protected packages: plasma-desktop
</span><span style="color:#323232;">================================================================================
</span><span style="color:#323232;"> Package Arch Version Repository Size
</span><span style="color:#323232;">================================================================================
</span><span style="color:#323232;">Skipping packages with conflicts:
</span><span style="color:#323232;">(add '--best --allowerasing' to command line to force their upgrade):
</span><span style="color:#323232;"> kde-settings noarch 38.2-5.fc38 nobara-baseos-38 33 k
</span><span style="color:#323232;"> libkworkspace5 x86_64 5.27.8-1.fc38 nobara-baseos-38 115 k
</span><span style="color:#323232;"> libkworkspace5 x86_64 5.27.9.1-3.fc38 nobara-baseos-38 115 k
</span><span style="color:#323232;"> plasma-workspace-common x86_64 5.27.8-1.fc38 nobara-baseos-38 41 k
</span><span style="color:#323232;"> plasma-workspace-common x86_64 5.27.9.1-3.fc38 nobara-baseos-38 40 k
</span><span style="color:#323232;"> plasma-workspace-libs x86_64 5.27.8-1.fc38 nobara-baseos-38 2.2 M
</span><span style="color:#323232;"> plasma-workspace-libs x86_64 5.27.9.1-3.fc38 nobara-baseos-38 2.2 M
</span><span style="color:#323232;"> plasma-workspace-wayland
</span><span style="color:#323232;"> x86_64 5.27.8-1.fc38 nobara-baseos-38 70 k
</span><span style="color:#323232;"> plasma-workspace-wayland
</span><span style="color:#323232;"> x86_64 5.27.9.1-3.fc38 nobara-baseos-38 70 k
</span><span style="color:#323232;">Skipping packages with broken dependencies:
</span><span style="color:#323232;"> kde-settings-plasma noarch 38.2-5.fc38 nobara-baseos-38 13 k
</span><span style="color:#323232;"> plasma-lookandfeel-fedora
</span><span style="color:#323232;"> noarch 5.27.8-1.fc38 nobara-baseos-38 403 k
</span><span style="color:#323232;"> plasma-workspace i686 5.27.8-1.fc38 nobara-baseos-multilib-38 15 M
</span><span style="color:#323232;"> plasma-workspace x86_64 5.27.8-1.fc38 nobara-baseos-38 15 M
</span><span style="color:#323232;"> plasma-workspace i686 5.27.9.1-2.fc38 nobara-baseos-multilib-38 15 M
</span><span style="color:#323232;"> plasma-workspace i686 5.27.9.1-3.fc38 nobara-baseos-multilib-38 15 M
</span><span style="color:#323232;"> plasma-workspace x86_64 5.27.9.1-3.fc38 nobara-baseos-38 15 M
</span><span style="color:#323232;"> plasma-workspace-x11 x86_64 5.27.9.1-3.fc38 nobara-baseos-38 68 k
</span><span style="color:#323232;"> sddm-breeze noarch 5.27.9.1-3.fc38 nobara-baseos-38 440 k
</span><span style="color:#323232;">
</span><span style="color:#323232;">Transaction Summary
</span><span style="color:#323232;">================================================================================
</span><span style="color:#323232;">Skip 18 Packages
</span>
Yeah I forgot to mention that I’ll not be using dnf manually but rely on nobara-sync. But I must stress that I already did that before this issue, BUT I followed advice on nobaras own website where the solution was to use dnfand I still ended up with this problem. The real issue was still my own though, I should have upgraded to Nobara 38 before trying the workarounds, since 37 isn’t supported any more.
It un-fucked itself thankfully, I haven’t done anything to resolve that issue. But when I ran the update today it went well with several new packages. Which means Nobara or Fedora pushed some changes to packages in the repos.
Every time you’re excluding something you’re excluding updating a package, while updating all the others. Then if the new packages depend on the newer version of the package you didn’t upgrade by excluding it, things break. That’s what’s happened here. Every time you use exclude to upgrade something you’re essentially breaking your system worse. That’s what the other person means by “partial upgrading”
And now that message says it’s going to completely remove your desktop environment so you’re gonna have no desktop, just a cli shell.
At this point the easiest thing would probably be to back up your home directory and whatever else you want to keep and just reinstall the system. Any other process to try and fix it is going to require more trouble and time than it would take to just reinstall unfortunately. There may not even be a way to successfully unbreak your system.
lemmy.one
Active