The only 'problem' I've had with FreeBSD's init was when an NFS mount was unavailable that the machine hung during boot. The mount didn't have anything required for boot on it, but there were services that depended on those mounts being there. In retrospect, I probably should have added "failok,-t=10" to those fstab entries. This one was definitely my fault.
An ideal init system would have known (or been taught) that services x, y, and z depend on NFS mounts /a, /b, and /c, so the system could have started mounting those in the background and let other services (like sshd!) start up as required.
As to your point about the service names, that bugs me as well.
An ideal init system would have known (or been taught) that services x, y, and z depend on NFS mounts /a, /b, and /c, so the system could have started mounting those in the background and let other services (like sshd!) start up as required.
As to your point about the service names, that bugs me as well.