Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
no systemd is not precise, since it does use parts of the systemd codebase.
See these repos:
Interesting. There's also a project that pulls logind out.
Both projects claim that they're decoupled from systemd, so I think "no systemd" is still a valid statement. systemd - the OS layer living immediately under the kernel - is not present. Even systemd's original mandate, the init process, isn't present, and is anything is "systemd," it's that part. Chimera uses dinit for init.
Depending on
blame, it might not be accurate to say that it contains no code written by Poettering, but I think most people's objection to stuff Poettering writes isn't individual chunks of code, but his overall system design and architecture.This seems to hint that they're using systemd's udev as well:
https://pkgs.chimera-linux.org/package/current/main/aarch64/base-udev
I wonder if they plan to adopt eudev at some point.