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.
no systemd is not precise, since it does use parts of the systemd codebase.
See these repos:
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.
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.