as @bonnietwin already wrote, IPFire 2.x comes with SysV as an initsystem, and there are no plans to change this.
IPFire 3.x will indeed shift towards
systemd - to my knowledge, however, we will be using it as an initsystem only (where is indeed much more powerful and flexible than SysV), and will not use it for anything else.
systemd suite became quite confusing, as it appears to be capable of nearly any given task except for brewing coffee by now. I once had to dig deeper into
systemd-resolved, which are lightweight daemons for NTP syncing and DNS resolving.
Both were working pieces of technology for most users, but did not provide all of the features we’d need in IPFire, and were not written primarily with security in mind. Therefore, I guess we will stick to Unbound as a DNS resolver in IPFire 3.x as well, trimming
systemd down to a bare minimum.
Hope to have your concerns solved.
Thanks, and best regards,