3 ms·
I had some issues with console initiation, and display in general. But I can't recall if that was before or after release (rough edges are to be expected in "te
by e12e 11y ago
I had some issues with console initiation, and display in general. But I can't recall if that was before or after release (rough edges are to be expected in "testing", especially when large infrastructure changes are happening).
I'm not happy Debian moved to systemd, but I understand why -- and I think they (I wish I could say we, but I didn't really encounter any unreported bugs) did a great job with the transition.
I do agree that for many use cases having a simple text-DSL for startup scripts make sense (even for someone reasonably proficient in shell scripts, the code-duplication and complexity of init-scripts are a problem. The duplication might be the worst part -- it requires a lot of job moving the system as a whole forward, and keeping even less-used packages consistent with current "best practices" as they evolve).
But that's not an argument for a monolithic init-system -- it just happened that systemd came with a DSL. One could even generate shell scripts based on unit-files[1].
I'm keeping a close eye on the kFreeBSD-port -- I wouldn't mind getting off Linux and systemd, while remaining on Debian.
[1] https://github.com/akhilvij/systemd-to-sysvinit-converter https://github.com/akhilvij/systemd-to-sysvinit-converter
- digi_owl 11y agoThe whole code duplication had long since been solved by other shell based init schemes. Its only sysv thats hanging on to the notion that each script has to be self contained.