The Linux Thread - The Autist's OS of Choice

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
I know I'm late on this but RIP to the Russian coders that can no longer legally work with the Linux Project anymore due to a stupid war that is currently going on in Eastern Europe.

It kinda sucks that the Western world that likes to put liberal democracy on a pedestal and also at times acts like autocrats and justify that with "National Security" reasons or some other bullshit excuse.
 
Last edited:
Like what, the crack pipe or 40 of Colt 45 on the table?
You meant the full auto glock switch and the 45 round glock mags before he blows his own head off trying to be real shit?
Apparently, the author of bcachefs finally got CoC'd. Looks like he tried to pull a pre-brainrot Linus, but got Shouah'd instead. So, there's a lot of RIP's lately, and with the new and improved CoC that requires devs to either bow down or get sent to CoChwitz, the future's not looking to bright.
Of course, a kike. I guess NetBSD or OpenBSD now... I guess he could work with NetBSD's HAMMER2 to make that better than staying somewhere unwanted. Maybe he ought to add a +ENDLÖSUNG and +NIGGER to his license as well for the Linux version
 
Of course, a kike.
Ironically, the handler of CoC's is not a kike, but a 'jeet. Not sure which is worse, but apparently she's the one responsible for this war crime:
In 2020, Khan provided a "Signed-off-by" tag for a patch recommending inclusive terminology in the Linux kernel.[12] This change was approved and merged by Linus Torvalds.[13][14] The patch advised developers to avoid terms such as "master," "slave," "blacklist," and "whitelist."[12][15] Alternatives such as primary/secondary, denylist/allowlist, and blocklist/passlist are suggested.[13]
 


1732233447766.png
the branch to remove reiserFS from the linux kernel has been merged into mainline. its over
 
WDYM It's a good thing.
It has been discussed for removal from the Linux kernel since early 2022 due to a lack of maintenance upstream, and technical issues inherent to the filesystem, such as suffering from the year 2038 problem
Maybe you want to butt in and fix the problem yourself. Fork it and then name it ReiserFS 2.0.
 
Apparently, the author of bcachefs finally got CoC'd. Looks like he tried to pull a pre-brainrot Linus, but got Shouah'd instead. So, there's a lot of RIP's lately, and with the new and improved CoC that requires devs to either bow down or get sent to CoChwitz, the future's not looking to bright.

I just saw and was going to post about it.

To me. The exact reason was stupid.

But as a whole with him, and his whole file system in respect to the main line kernel. It was pretty surprising they didn't tell the dude to fuck off already. If you go, and look at his interactions with linus outside of this. It was him trying to not follow the same guidelines every other person submitting patches to the kernel has to, for them to accept their patches. Then him spurging out when linus tells him repeatedly he needs to follow the same rules everyone else does.

Acting like his project is some gift from God, and being a dick.

I wouldn't be surprised if the real reason this happened was because of people outside of Linus. Seeing how he acts and not being as patient as Linus so they just decided to do what they could to get him away from. The project.
 
Ironically, the handler of CoC's is not a kike, but a 'jeet. Not sure which is worse, but apparently she's the one responsible for this war crime:
In her own photo she looks like she's in the middle of scolding:
1732236628528.png


The opening line of her article:
shuah.png

That should be "recognized". I'll guess that someone with poor command of English wrote this fluff piece.
 
I just saw and was going to post about it.

To me. The exact reason was stupid.

But as a whole with him, and his whole file system in respect to the main line kernel. It was pretty surprising they didn't tell the dude to fuck off already. If you go, and look at his interactions with linus outside of this. It was him trying to not follow the same guidelines every other person submitting patches to the kernel has to, for them to accept their patches. Then him spurging out when linus tells him repeatedly he needs to follow the same rules everyone else does.

Acting like his project is some gift from God, and being a dick.

I wouldn't be surprised if the real reason this happened was because of people outside of Linus. Seeing how he acts and not being as patient as Linus so they just decided to do what they could to get him away from. The project.
Oh, the guy is definitely an asshole. Not exactly rare among (kernel) developers, but still. What's fucked is that there wasn't even a reason for the whole "suck CoC or die", other than to put this guy through a humiliation ritual, when they could've just as easily booted him for "disrupting the workflow" or something. Much like Linus himself did to Ke(a?)y Sievers a while back (I don't remember exactly what the beef was, but I'm pretty sure the guy was being a typical systemd developer and WONTFIX'ing a bunch of stuff). So I'm kinda inclned to take the side of the narcissistic prick on this one, even if he actually deserves to be "fired".
 
I know I'm late on this but RIP to the Russian coders that can no longer legally work with the Linux Project anymore due to a stupid war that is currently going on in Eastern Europe.

It kinda sucks that the Western world that likes to put liberal democracy on a pedestal and also at times acts like autocrats and justify that with "National Security" reasons or some other bullshit excuse.
Apparently, the author of bcachefs finally got CoC'd. Looks like he tried to pull a pre-brainrot Linus, but got Shouah'd instead. So, there's a lot of RIP's lately, and with the new and improved CoC that requires devs to either bow down or get sent to CoChwitz, the future's not looking to bright.

I can understand if it's just using the CoC as an excuse, but if all he had to do was make a public apology it's not the best excuse to use. Just fucking kick him out if he's that annoying.

This and the post I quoted before it show the most retarded decision making in the history of the world. You basically have free slaves, you don't have to feed them, house them, give a shit about their pains, medicate them. Just wait and retards will give you free labor. FREE LABOR. Did I mention you don't have to give them a fucking cent?

If the code is correct, why the FUCK would you not accept it? There is 0 detriment in taking code from someone you hate, in fact that's a win isn't it? You hate the guy, yet he works for you FOR FREE. It is so illogical I get a headache trying to steelman this and justify it. I'd take code from literally Satan as long as there's no weird shit in it.

Now, if the weirdo's code is shit and even the reviews just become a waste of your time just kick him out for that reason. "Sorry bro, your code is shit. Watching paint dry is more fruitful than reviewing this crap"
 
Anybody having issues with the 560 Nvidia beta driver? I installed it and hardware acceleration just flat-out broke for most applications. And no, a driver rollback didn't fix things (???).
 
Anybody having issues with the 560 Nvidia beta driver? I installed it and hardware acceleration just flat-out broke for most applications. And no, a driver rollback didn't fix things (???).
So far it's working for me on Gentoo kernel 6.11, I can finally turn on IBS with the kernel-open build again. However, I don't really play 3D games on Linux, exllamav2 seems to working for me.
What version are you rolling back to?
 
If the code is correct, why the FUCK would you not accept it? There is 0 detriment in taking code from someone you hate, in fact that's a win isn't it?
Two reasons. First is reputation damage: if Linux with bcachefs is a bit shit, some people will conclude that Linux itself is a bit shit.
Second is that no code is completely isolated. Someday he's going to have to patch other bits of the kernel for one reason or another, he won't just stay in his tree. Or if there's a crash and it's not obvious whose fault it is, somebody's going to have to waste time diagnosing it before handing it to him. There's an overhead to all this.

That said, anybody who's done make menuconfig will know that there's some ridiculously obscure things in the kernel tree, so you must really have pissed people off for them to conclude your code's not worth the bother.
 
Back