Description of problem: systemd service enable/disable relies on symbolic links, which we cannot use in a stateless linux environment. So we need to find a way to work around this limitation in stateless linux support so that we can enable services persistently
I don't know if I'm supposed to respond or not (maybe this was opened just for tracking), but I was thinking that it may work with something like - boot a default target that also creates a /etc/systemd/system/custom_target on tmpfs - change to the custom runlevel
Cristi, Feel free to comment/patch any bugs, your idea is along the same lines I was thinking. If you want to take a stab at it go ahead :)
We should really address this to get a clean solution to enable or disable services at runtime. This should probably also get a feature page. To be discussed on the next node meeting.
pushing to target release 3.5, assuming its not planned for 3.4 at this point...
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug. i hope the new envisioned model will address this seamlessly