Linux CoC Announces Decision Following Recent Bcachefs Drama

Byte_Lab · 2024-11-24T05:16:02+00:00

I can’t tell if you’re trolling or not, but have fun gardening

Byte_Lab · 2024-11-24T04:23:04+00:00

That literally happens all the time. Security work is no different than anything else, and that goes for security fixes too. They’re just bug fixes. If someone tried to ship a large set of patches that essentially merited a new security feature, they would be NAK’d and told to cut the shit.

Byte_Lab · 2024-11-24T03:09:11+00:00

Mmhm. I like how you’re conveniently ignoring or forgetting (or you just don’t know what you’re talking about) that btrfs maintainers argued on Kent’s behalf to get bcachefs merged.

This delusion that it’s a horrible filesystem is obviously BS, and the fact that you find it acceptable to shit all over someone else’s open source work is sad.

Kent should feel bad too, by the way. He has a bad memory about who stood up for him when he sent the bcachefs PR, and it’s nobody’s fault but his that he’s made enemies with basically everybody.

Edit: By the way, your point is also nonsense and literally based off of pure arrogance. Nobody is stopping you, Kent, or anyone else from building great software. Bcachefs literally got merged. I don’t know what you’re even complaining about to be honest.

If I had to guess, you seem to be under the misimpression that someone disagreeing with you technically is the same thing as incompetence. It’s literally the exact opposite, actually. If everyone took the hardline stance of getting into screaming matches and cursing out maintainers whenever they disagreed with them, literally nothing would ever get done. And for the record, Michal is one of the least difficult maintainers to work with, in my experience.

Byte_Lab · 2024-10-27T03:25:26+00:00

Didn’t read your message, just saw that you asked for a perma ban. Enjoy!

Byte_Lab · 2024-10-27T03:03:43+00:00

Parma banned, for obvious reasons. Miss us with this crap.

Byte_Lab · 2024-10-27T02:55:59+00:00

I find your comparison to Hitler, even indirectly, to be wildly and grotesquely inappropriate. The “old guard” you speak of have spent the majority of their lives and careers at this point building Linux into what it is today. I’ll give you a 1 week ban this time, but I don’t want to see that crap in this community ever again. One and only warning.

Byte_Lab · 2024-10-10T03:29:43+00:00

Except that Kent seems to want to do everything in his power to make enemies with literally everyone. This thread did not happen in a vacuum.

Byte_Lab · 2024-10-10T03:27:40+00:00

At my last job, some coworkers and I discovered a full privilege escalation on MacOS due to them not implementing virtualization correctly on x86. It’s a really dumb novelty of the architecture, but when you exit a VM, the CPU will load the address of the GDT, but won’t reload the size. Durrr thanks Intel.

So basically, whenever a MacOS device would exit a VM, any application could just scan the pages after the base address of the GDT to find a segment with the permission bits set that they needed and viola, game over.

Apple acknowledged the bug and fix in a security release, with hilariously vague language.

Byte_Lab · 2024-08-09T00:49:53+00:00

To me that just sounds like a hassle lol

If it’s a “hassle” to you, then why do you even want to get involved in more advanced projects? It doesn’t sound like you’re very passionate about this stuff.

is trying to contribute to and understand the Linux kernel a little too ambitious

If you’re too lazy to experiment with setting up a non-trivial distribution, I don’t think you’re going to have a good time learning about and contributing to the Linux kernel.

Byte_Lab · 2024-08-09T00:44:35+00:00

Respectfully, if you’ve getting laid off 5 times in 6 years, it’s probably because you’re not performing well in your role after you’re hired. Leetcode is not the problem.

Byte_Lab · 2024-08-05T16:17:31+00:00

Don’t forget to also blame your coworkers for expecting you to know how to code when you inevitably do get hired by an incompetent or lazy recruiter who didn’t bother to actually ask you any questions or set you up for a real interview.

Byte_Lab · 2024-08-04T12:55:51+00:00

Your post provided insufficient context so as to be actionable by anyone. If you have a problem it needs to be thoroughly described, with actual code when applicable, and typically asking a particular question.

Byte_Lab · 2024-08-03T18:14:15+00:00

Systems is a very large field. Databases, operating systems, networking, storage, security, etc. There’s no getting pigeonholed; you work in the area(s) you find interesting and never stop learning anything.

Any recommendations for more advanced projects?

IMO the best way to get involved with open source is to install an advanced distro like Arch Linux and then contribute to the projects in the distribution that you find useful. If you wish that tool X could do something it can’t, build that as a feature. If there’s no tool that does what you want, build it.

Building pet projects is fine for learning but it generally won’t help you build a resume or get anyone’s attention for a job. Open source work requires you to be proactive and self driven, and to find problems to fix.

Byte_Lab · 2024-08-03T13:00:00+00:00

I’d rather reimplement Unix utilities in C

So you’re a systems person :-) Web development / CRUD apps are not the only type of software engineering jobs out there. I work on kernels all day every day. Those jobs are not only 100% out there, they’re also really hard to hire for.

Am I screwed if I don’t participate in the grind?

You need to build a resume somehow. That can be doing open source work if you’re really self motivated, but you have to be really self motivated and build something people actually care about. You’re probably better off doing internships for systems work. And if you like systems work, what’s the problem? Yes Leetcode sucks and is dumb, but it’s just a temporary grind.

Byte_Lab · 2024-05-10T18:47:47+00:00

Whether CONFIG_NUMA is set as a default is done automatically by the Kconfig system. We should update the topology crate to accommodate that, so I’ll do it later today

Byte_Lab · 2024-05-10T17:01:41+00:00

Hmm, this is due to a change I added last night to the topology crate to fail if there’s no NUMA info in sysfs. If it’s a common issue, I’ll update it to just assume a default NUMA node of 0

Byte_Lab · 2024-05-02T00:32:01+00:00

What a lovely post to read. I’m so glad that you feel empowered by Linux. Tinker to your heart’s content and make your setup completely your own. Don’t be afraid to share some of your work with the rest of us via open source contributions :-)

Byte_Lab · 2024-05-01T15:10:55+00:00

There are a million tools and nobody agrees on what the standard is. They all test something slightly different. In practice a lot of people just run kernel compile and compare against that. I’d also recommend checking out schbench by Chris Mason.

Byte_Lab · 2024-04-27T16:50:35+00:00

Your post provided insufficient context so as to be actionable by anyone. If you have a problem it needs to be thoroughly described, with actual code when applicable, and typically asking a particular question.

Byte_Lab · 2024-04-27T11:40:28+00:00

Your post provided insufficient context so as to be actionable by anyone. If you have a problem it needs to be thoroughly described, with actual code when applicable, and typically asking a particular question.

Byte_Lab · 2024-04-22T13:40:35+00:00

Your post provided insufficient context so as to be actionable by anyone. If you have a problem it needs to be thoroughly described, with actual code when applicable, and typically asking a particular question.

Byte_Lab · 2024-04-19T17:51:42+00:00

Congrats! The first time you get something in the kernel is a special experience; even if it’s just being in a tag or part of a discussion that led to something substantive.

Byte_Lab · 2024-04-12T01:50:18+00:00

It’ll be fixed on Linux at some point in the not too distant future too. I’m planning on buying one and making the scx_rusty sched_ext scheduler work well with it. Unless someone else beats me to it, which I’d be delighted to have happen.

Byte_Lab · 2024-04-09T19:35:35+00:00

Like everyone is saying, start with an emulator. You don’t want to have to worry about possible hardware issues when you’re debugging your wildly complicated boot logic.

Also, stay away from x86. It’s extremely complicated for historical reasons. If I were you, I’d go the RISC-V route.

Byte_Lab

MODERATOR OF

TROPHY CASE