-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to SystemD #94
Comments
Switching to systemd is imaginable, but we haven't planned for that yet, specifically not for the next version. It would require rewriting some startup scripts and adjusting the iot2000setup tool. And then testing everything. You could support that effort by sending PRs, though. |
Just to ref:
The following local_conf should enable systemd: DISTRO_FEATURES_append = " systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" Looks like there are some errors in compilation due init scripts. |
NVM, @jan-kiszka would you like to open a branch for systemd so I can send PR there? Also, I think that I could create a |
@deinok Just fork the project into your own namespace and issue PRs from there. That's a typical workflow pattern. |
Yes, i know the typical workflow, I'd just want to be sure that this kind of heavy changes are going to be accepted (If they work well :) ). |
If they work, I would be optimistic. The effort is likely as much in testing as it is in finding the places that need changes and applying them. |
@jan-kiszka Most of the required changes are SysV init vs SystemD init mechanisms. |
Unlikely to happen for this layer anymore. |
Due the fact that the SO of IOT seems to lack some common commands from Linux, I would like to suggest move to SystemD init system.
I know that SystemD have a bit of bad reputation for Linux purists, but this will really help IOT be more near to an expected Linux Board
The text was updated successfully, but these errors were encountered: