`vinit` strategy

[jspc]

We will:

1. Write vinit logs/ events to dmesg and store the last n events in memory; this will make it harder to lose logs and events. We will return these n memory logs from vinitctl, too. Service logs come later See: View logs (system, service) via vinitctl #16
2. vinitctl will respond to vinitctl force-reboot by sending the reboot signal to the kernel directly. This won't bother stopping services. perhaps it needs a confirmation flag/ the flag -f to skip confirmation. See: Reboot/ poweroff when vinit doesn't start properly #17
3. We no longer try to restart failing services. Instead, mark as failed. Exited services always show up as failed, whereas oneoffs are checked against Oneoff.ValidCodes. Logs are only configured if s.proc is not nil. See: bootup segfaults #18