Thing is that the init side of systemd is the least of the problems.
Right now the Freedesktop approved way of handling suspend and hibernate on a Linux laptop is via systemd-logind, the systemd session and seat manager!
What used to handle it, powerkit/powerd, is not pretty much just a wrapper around the power management parts of logind.
Never mind that logind itself upped and replaced consolekit, that could be used independently.
Or that these days udev, a project for managing the content of /dev on Linux installs, and that existed for almost a decade on its own, is these days part of the systemd source ball. On paper it can be used independently, but in practice the procedure for extracting udev from systemd change at random intervals.
And where did you get the idea that FreeBSD wants to clone systemd?! Best i recall is that the developer of launchd (the OSX/MacOS inspiration for parts of systemd) was lobbying for FreeBSD to adopt Launchd. But he was largely rebuffed and has since opted to develop his own FreeBSD fork instead.
There is some effort underway to clone the external systemd APIs, but last time i read anything about it they had gotten hung up on the ever morphing nature of logind.
And more recently there has been effort spent towards developing a BSD DE that do not depend on anything Freedesktop derived, systemd included. Because The major reason for having anything Systemd related on the BSDs was to support the major DEs, Gnome in particular.
So no, the BSDs are in no way "envious" of the systemd shoggoth. And why should they be? Their own init scripts are a haven of sanity compared to the sysv derivative that RH and Debian/Ubuntu clung to for so long. Heck even venerable Slackware adopted a variant of it, and they seem uninterested in replacing it any time soon.
Right now the Freedesktop approved way of handling suspend and hibernate on a Linux laptop is via systemd-logind, the systemd session and seat manager!
What used to handle it, powerkit/powerd, is not pretty much just a wrapper around the power management parts of logind.
Never mind that logind itself upped and replaced consolekit, that could be used independently.
Or that these days udev, a project for managing the content of /dev on Linux installs, and that existed for almost a decade on its own, is these days part of the systemd source ball. On paper it can be used independently, but in practice the procedure for extracting udev from systemd change at random intervals.
And where did you get the idea that FreeBSD wants to clone systemd?! Best i recall is that the developer of launchd (the OSX/MacOS inspiration for parts of systemd) was lobbying for FreeBSD to adopt Launchd. But he was largely rebuffed and has since opted to develop his own FreeBSD fork instead.
There is some effort underway to clone the external systemd APIs, but last time i read anything about it they had gotten hung up on the ever morphing nature of logind.
And more recently there has been effort spent towards developing a BSD DE that do not depend on anything Freedesktop derived, systemd included. Because The major reason for having anything Systemd related on the BSDs was to support the major DEs, Gnome in particular.
So no, the BSDs are in no way "envious" of the systemd shoggoth. And why should they be? Their own init scripts are a haven of sanity compared to the sysv derivative that RH and Debian/Ubuntu clung to for so long. Heck even venerable Slackware adopted a variant of it, and they seem uninterested in replacing it any time soon.