Anton Aylward wrote:
O
Your problem here is not that you CAN'T but that, as you say
I want to be able to use my current recovery methods
Systemd does have beet debug capabilities, but they are different because systemd is not SysVInit.
1) Recovery means I can run xfsrestore from repair mode. 2) I can try starting 1 more services manually. 3) I can look at all of the startup operations in one place for a given service. If I need to make a change in a utility's startup while in emergency -- I can. 4) When I have worked around a problem, I can continue to boot. I've had network problems due to naming issues that were very difficult to work with and I wanted the system "up" so I could work on them. I should be able to manually bring up the network and start needed services, so I can login from a normal GUI. There are multiple reasons why that doesn't work on sysd, not the least is it doesn't allow you to continue from after a problem-point. Those are not sysvinit features: they are *basic* features.
They exists. They work differently.
--- Oh? How do you continue after a boot problem and not have to restart? If it isn't possible, then please don't claim such methods exist. They don't work. You can't modify or look at the source and rebuild and continue execution. It's not a matter of different, it's a matter of not having basic features. BTW, what is a 'beet' debug capability? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org