@Michael: yes, this should be "stop on unmount-filesystem or single-user" (we can create a new event for single-user to make the logic clearer).
@Clint: I agree that full migration sounds like the best approach. I have had a few discussions previously with Scott on the idea of abstract jobs. There is quite a lot of scope here. Aside from network-services, we could introduce jobs such as:
- "network-manager" (not the application, could also refer to connman, wicd, etc).
- "firewall" (iptables, ufw, etc).
- "display-manager" (gdm, kdm, xdm, etc)
- "ssh" (openssh, dropbear)
@Michael: yes, this should be "stop on unmount-filesystem or single-user" (we can create a new event for single-user to make the logic clearer).
@Clint: I agree that full migration sounds like the best approach. I have had a few discussions previously with Scott on the idea of abstract jobs. There is quite a lot of scope here. Aside from network-services, we could introduce jobs such as:
- "network-manager" (not the application, could also refer to connman, wicd, etc).
- "firewall" (iptables, ufw, etc).
- "display-manager" (gdm, kdm, xdm, etc)
- "ssh" (openssh, dropbear)