Linux

49964 readers

947 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

315

Resigning as Asahi Linux project lead (marcan.st)

submitted 2 days ago by [email protected] to c/[email protected]

136 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 30 points 1 day ago (2 children)

Again: what cooperation is possible when the maintainer says "I'll do everything in my power to keep Rust out of the kernel"? When they NACK a patch outside of their Subsystem?

[–] [email protected] 1 points 1 day ago* (last edited 1 day ago) (2 children)

Can a maintainer really NACK any patch they dislike? I mean I get that Hellwig said he won't merge it. Fine. What if for example Kroah-Hartman says "whatever, I like it" and merges it nonetheless in his tree?

[–] [email protected] 3 points 1 day ago (1 children)

I doubt Greg is pulling in Rust until it has been through the mainline. That said, Linus can merge anything he wants.

[–] [email protected] 2 points 1 day ago

It was an example. I don't have a fucking clue how all the maintainers are named.

The main question was: why can a maintainer NACK something not in their responsibility? Isn't it simply necessary to find one maintainer who is fine with it and pulls it in?

Or even asked differently: shouldn't you need to find someone who ACKs it rather than caring about who NACKs it?

[–] [email protected] 1 points 23 hours ago

Yes, but asking him in this case was basically a courtesy, the code isn't going into anything he manages. He can reject it, but that's an opinion, not a decision. It can still be merged if the regular maintainer (or someone senior like Linus himself) approves.

[–] [email protected] -4 points 1 day ago (1 children)

Can you quote where that was said?

I've been following this debate for a bit and as far as I can tell it's not so much that they'll do what they can to keep rust out but more to make sure that the people who want to develop in rust are the ones who end up maintaining that part of the code and not the current maintainers.

[–] [email protected] 23 points 1 day ago* (last edited 1 day ago)

Sure: https://lore.kernel.org/rust-for-linux/[email protected]/

I accept that you don't want to be involved with Rust in the kernel, which is why we offered to maintain the Rust abstraction layer for the DMA coherent allocator as a separate component (which it would be anyways) ourselves.

Which doesn't help me a bit. Every additional bit that the another language creeps in drastically reduces the maintainability of the kernel as an integrated project. The only reason Linux managed to survive so long is by not having internal boundaries, and adding another language complely breaks this. You might not like my answer, but I will do everything I can do to stop this.

Can't get more explicit than this.