I'm not sure I agree with the comment about it being Bash-driven, though. I chose bash because it's readily available and had been proven to work fine from what systems I studied (namely OpenBSD and Arch Linux's initscripts). Being a modern replacement is not what I'm looking for, I just want to make something different that doesn't needlessly complicate.
#!/bin/bash
#!/bin/bash
#!/bin/bash
One of the major improvements to System 5 rc on Linux in the past couple of decades came not from adjusting configuration mechanisms (e.g. r2d2, file-rc) or helper script function libraries. It came from the simple realization that the Bourne Again shell was a quite heavyweight choice for running a lot of non-interactive scripts.* https://wiki.ubuntu.com/DashAsBinSh
* https://wiki.debian.org/BootProcessSpeedup#Using_a_faster_sy...
* http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/b...
HWCLOCK_TZ=$(readlink /etc/localtime | cut -d/ -f5-)
One of the improvements to BSD /etc/rc.conf{,.local} pioneered by OpenBSD 5.6 is that they are no longer shell scripts, but are simple lists of name=value pairs, that can thus be parsed, used, and maintained by things other than just shell script interpreters.OpenBSD also gained an rcctl command, where one could run (say) "rcctl enable salt_master" and it would adjust the rc.conf files to enable the salt_master service. nosh has a shim for it.