Au contraire, selon Lennart il a bien architecturé son code pour exploiter à fond tous les mécanismes d'un noyau Linux moderne et ainsi avoir un code plus compact, plus fiable et plus lisible.
Son explication dans la FAQ systemd est la suivante:
Will this run on [insert non-Linux OS here]?
Unlikely. As pointed out, systemd uses many Linux specific APIs (such as epoll, signalfd, libudev, cgroups, and numerous more), a port to other operating systems appears to us as not making a lot of sense. Also, we, the people involved are unlikely to be interested in merging possible ports to other platforms and work with the constraints this introduces. That said, git supports branches and rebasing quite well, in case people really want to do a port. Actually portability is even more limited than just to other OSes: we require a very recent Linux kernel, glibc, libcgroup and libudev. No support for less-than-current Linux systems, sorry. If folks want to implement something similar for other operating systems, the preferred mode of cooperation is probably that we help you identify which interfaces can be shared with your system, to make life easier for daemon writers to support both systemd and your systemd counterpart. Probably, the focus should be to share interfaces, not code.
[^] # Re: systemd
Posté par patrick_g (site web personnel) . En réponse au journal Lennart casse les logs!. Évalué à 5.
Au contraire, selon Lennart il a bien architecturé son code pour exploiter à fond tous les mécanismes d'un noyau Linux moderne et ainsi avoir un code plus compact, plus fiable et plus lisible.
Son explication dans la FAQ systemd est la suivante:
Will this run on [insert non-Linux OS here]?