Hi: I just subscribed to this list in order to offer assistance in order to get Yast and systemd to interact in a nicer fashion. I will assist you with patches and a lot of suggestions after the decision of converting the YCP codebase into Ruby is taken and modules are translated. Here is the first and most important suggestion I have and I strongly suggest you to consider it while creating/migrating modules from YCP to Ruby. - You MUST NOT talk (I can't find a way to emphasize this) to any systemd component using systemctl, localectl, timedatectl or whatever other command line utility, those are *human interfaces* and not *programming interfaces*(exception "systemctl show") if you continue in the current direction, it will bite you and rip and piece of your skin pretty soon. Yast MUST communicate with systemd components using the respective D-BUS API.[1][2][3][4] [1] http://www.freedesktop.org/wiki/Software/systemd/dbus [2] http://www.freedesktop.org/wiki/Software/systemd/timedated [3] http://www.freedesktop.org/wiki/Software/systemd/localed [4] http://www.freedesktop.org/wiki/Software/systemd/hostnamed A little bit of googling shows that mvidner has a repo in github containing an implementation of ruby-dbus that will come handy for this purpose. That's all for now :-) Cheers! -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org