Re:Rustysd – A minimal drop-in for a subset of systemd in Rust
by dnautics on Monday December 16, 2019 @03:12AM
(#21801522)
Name one problem you personally have encountered deploying systemd in production.
Re:Rustysd – A minimal drop-in for a subset of systemd in Rust
by marcosdumay on Monday December 16, 2019 @07:40AM
(#21802587)
The launching order of the internal daemons is not explicit on the services graph. For a long while I had a computer that mounted the disks on a non-predictable time and most attempts to fsck the root partition would fail.
For a while it would ignore the system DNS settings, so it didn't only require it to be configured twice, but the systemd settings had an habit of changing in format every so often.
Udev failed a bit at the time it was being included on the package.
Oh, there was the time when the simple service launcher didn't conform to the documentation so a lot of daemons could fail to launch in unpredictable ways.
But the first I started using it was at the Debian migration. So the earlier bugs were all solved already.
No amount of testing and bug-fixing solves badly created software. Systemd is begging for a rewrite.
Now, I don't know if this one will be complete enough to replace the original. But yours is not a promising argument.