3 ms·
The good old "design by commitee", catering for a still-unexisting alternative init system implementing the same interfaces? No, thanks. systemd's interfaces a
by EmanueleAina 12y ago
The good old "design by commitee", catering for a still-unexisting alternative init system implementing the same interfaces?
No, thanks. systemd's interfaces are publicly available and with good enough documentation. Most of them are even declared stable, only the internal ones are obviously free to change.
In fact many project are now attempting to reimplement systemd's interfaces as this is how FLOSS work.
- lmm 12y agoYou don't have to design by committee, but you do have to publish your interface and commit to keeping it stable. Yes, this slows down development, but it's essential for interoperability. Of course the alternative doesn't exist yet when the interfaces change every week. And systemd's definition of "internal" is rather dubious; to most of us, udev or journald should be separate components that can be swapped out.
- EmanueleAina 12y agoPublish the interface and committing to keep them stable is exactly what the systemd team did. Of course internal interface are not stable and sparsely documented, but they are just that, internal. Reimplementors should only bother about the public interfaces. Note that udev does not use systemd internal interfaces and happily runs on non-systemd systems. Journald can be disabled if you don't want it, or you want to run it on non-systemd?