On a Guix System the PID 1 is called Shepherd and is controlled using the command herd. I often find myself wanting to tab-complete commands beginning with herd, like:

$ sudo herd restart some

But lacking that, I can't even find a way to list all services known to (the) Shepherd. The help printout reads:

└$ sudo herd --help
herd [OPTIONS...] ACTION SERVICE [ARG...]
Apply ACTION (start, stop, status, etc.) on \
SERVICE with the ARGs.
  -s, --socket=FILE           send commands to FILE
      --help                  display this help and exit
      --usage                 display short usage message and exit
      --version               display version information and exit

and only seems to mention actions that should be taken on services. The info and man pages are both terse, merely listing the available actions.

herd [OPTION...] ACTION [SERVICE [ARG...]]

   It causes the ACTION of the SERVICE to be invoked.  When SERVICE is
omitted and ACTION is ‘status’ or ‘detailed-status’, the ‘root’ service
is used(1) (*note The root and unknown services::, for more information
on the ‘root’ service.)

   For each action, you should pass the appropriate ARGs.  Actions that
are available for every service are ‘start’, ‘stop’, ‘restart’,
‘status’, ‘enable’, ‘disable’, and ‘doc’.

My knowledge about init is limited. All the things I know is that init is the first process that kernel starts after getting booted and is assigned with Process ID of 1. > Recently while going through [GNU Shepherd](https://www.gnu.org/software/shepherd/) , I noticed the following sentence. >It provides a replacement for the service-managing capabilities of SysV-init (or any other init) with a both powerful and beautiful **dependency-based system** with a convenient interface. So, I want to know what is meant by dependency-based system here? Is it the feature that distinguish it with popular SysV or Sysmted init systems?