I like that Linus is so strict on not breaking user space because this obviously aids with compatibility and it’s probably a big part of why rolling releases work.
I think kernel still has compatibility with paleolithic glibc enabled by default
ENOENT is not a valid error return from an ioctl. Never has been, never will be. ENOENT means “No such file and directory”, and is for path operations. ioctl’s are done on files that have already been opened, there’s no way in hell that ENOENT would ever be valid.
Why so many people see letter as containing onlt 3 words and ignore part where Linus says that maintainer shouldn’t randomly blame userspace, how unrelated error code is(it’s like if your router crashed with message “there is no milk in the fridge”), repeats that maintainer shouldn’t randomly blame userspace, asks if patch good enough, says “WE DO NOT BREAK USERSPACE”,
I’m angry, because your whole email was so horribly wrong, and the patch that broke things was so obviously crap.
The fact that you then try to make excuses for breaking user space, and blaming some external program that used to work, is just shameful. It’s not how we work.
After twenty plus years of watching LKML and Linus’s behavior in general, I have to concur with you. Reading a lot of the ‘linus is an asshole’ threads, there’s generally a clear runup towards an outburst.
Just recently he called some developers out because it seemed evident they weren’t testing their patchsets on bare metal. So it’s not just code that gets called out, it’s also development methods that end up causing upstream pain.
[Translated] How I spent summer. Essay. (treebrary.pone.social)
How I spent summer. Essay....
Linus does not fuck around (lemmy.one)
An oldie, but a goodie
What the hell! Let's all just go crazy! (lemmy.world)
Laptop with long runtime
I’m looking to buy a new laptop. I recently switched to Linux (Fedora) and would like to stay with it (Not necessarily Fedora though)....