esgwpl

This one? https://lore.kernel.org/lkml/[email protected]...

In fact, sending too many patches to the mailing list is frowned upon:

https://lkml.org/lkml/2005/7/11/336

>"run this daemon that tries to beat the kernel OOM to the punch"

Considering that the kernel OOM killer tends to be way too late in doing its thing I don't see how this is inelegant, maybe there's a reason you can't just have the kernel kill processes earlier in the face of memory pressure.

Yes, please. I added a vote on AUR as well.

"The inode64 and inode32 names are used based on existing precedent from XFS."

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

>and yet the defensiveness is so reflexively strong

It's hard not to get defensive because this reddit post is basically flamebait:

>use of words like sapping and deadend

>"there's little to no payoff for the rest of humanity"

Like you said we can probably discuss this question without getting defensive but it's impossible thanks to the way it's worded.

I found a detailed explanation here:

https://stackoverflow.com/a/49481218

>The kernel is different from userspace projects - more difficult in some respects (we use a lot of very odd header files that pushes the boundary of what can be called "C"), but easier in many other respects (mainly in the sense that the kernel is fairly self-contained, and then doesn't rely on other projects for the final binary).

I'm interested in what Torvalds meant by these odd header files, does anyone know?

I don't know about you but to me what makes D2 so charming is its loot and character progression.

Small nit, the PRO version of Ryzen APUs do support ECC[0], also ASRock has been quoted saying that all of their AM4 motherboards support ECC, even the low end offerings with the A320 chipset.

[0] https://www.asrock.com/mb/amd/a320m-hdv%20r4.0/index.asp#Spe...

Sorry if my post sounds like a jab, it wasn't meant to be, thanks for your work and Merry Christmas.

This version has got to be the worst kernel released in a while in terms of regression, from AMDGPU null pointer dereference crash[0] to f2fs data corruption bug[1] and now this. Fixes for these are on their way as far as I can tell but since the stable team are probably on Christmas vacation it might take a while.

[0] https://bbs.archlinux.org/viewtopic.php?pid=1943906#p1943906

[1] https://bugzilla.kernel.org/show_bug.cgi?id=210765

This being an LTS release made me wonder: why do distros with long support cycle like RHEL not come with LTS kernel?

As far as I know Corsair only design PSUs, the actual manufacturing are all outsourced to Chinese or Taiwanese OEMs. Edit: as for the unit you linked, it's manufactured by Flextronics[0]

[0] https://www.tomshardware.com/reviews/corsair-ax1600i-psu,540...

Probably because you have to be somewhat familiar with git to be able to upload stuff to it, there is a barrier of entry.

Not a lot, you can see it on the development statistics that LWN releases for every major kernel releases, for 5.7, it's only about 13-14%, so most people working on the kernel do indeed get paid for it.

https://lwn.net/Articles/821813/

I like how everyone's answering questions about someone's personal experience with even more personal experience, I'm not being sarcastic, keep them coming, please.

I believe AGESA 1.0.0.4 Patch B broke something for the APUs, you should try either upgrading or downgrading your BIOS but what worked for me was downgrading to AGESA 1.0.0.3 ABB, both Windows and Linux has stopped crashing now, although I still get the occasional lockup when browsing with Firefox on Linux. I found out the culprit after stumbling into this thread: https://old.reddit.com/r/AMDHelp/comments/gj9kpz/bsod_new_pc...

Not to take away from their success but their recent progress have been more like them catching up to Intel. It will be interesting to see if they can truly pull ahead though.

To be fair to Poettering, someone accused the systemd devs of being on Google's payroll, if I were him I'd be annoyed as well.