When I was a child, I did translate knoppix boot messages, to my mother language, for a local project. In colours. For me was great and rewarding, a nice learn

When I was a child, I did translate knoppix boot messages, to my mother language, for a local project. In colours. For me was great and rewarding, a nice learning experience, about livecd's initialization and linux in general at the time. I don't feel like I could have accomplished the same experience trying to do the same with systemd (with my age and knowledge and resources at the time). Still more difficult, being a Debian user, where systemd is not in the same shape than RHEL based distros, and documentation is out of sync, or missed in blogs... What you propose reminds me to openrc or the gentoo dependency based init system. I Love too the BSD/Slackware/busybox init style (single script init). But I'm a scripting mad. One of my reasons to live, of and for, opensource, is the ethics and freedom behind it. Other one was being more K.I.S.S. on my system interactions than with MS based products. I feel capital interests hurts some things very hard to obtain, in voluntary groups of people, using guerrilla warfare, and without any care. Eventually I've deployed some Debian stable (Jessie) systems with sysvinit this same year, and I'm grateful that people in Debian did that option possible. I'm not sure if a third, or a new option with modern syntax and sparse features as you say, could be better than the years we've been moving the world using sysvinit or upstart or others... but we, the tech people, seem to like new things! Totally agree about the docs care, specially when there are distributors involved. When there are changes in opensource, there should be a lot of more care IMHO than in closed products, and this is not always the case. Unfortunately people, by brain nature, is driven a lot by media and marketing, two weapons of venture capital techs. And if service providers insert X and media inserts X, people who did never maintain a critical and complex deployments using X and did integrate a lot of things with them, starts talking about the smell of the clouds. What implementation do you suggest, to reach what you propose? I think is not easy :) My main feature request could be: reliable and malleable (not easy too). > An improvement would be something with modern syntax, sparse features, and good docs. Loved your tower of babel mess definition, upvoted just by that comparison. Have a nice day.