This guide will be more of a crash course then a in depth guide on basic usage of 66.

The service dir for init scripts are located:


Modified init scripts, to avoid being overwritten by pkg updates, should be placed in:


Tree or in s6 terms, bundle, creation.

If, lets say, you wanted to create a tree named audio for your audio services

  66-tree -n audio

Another example: If one wanted to create another tree that you may want to run upon next reboot, but not your current default

  66-tree -ncE slim-tree

Now let me mention what the option flags are:

 -n : new 
 -c is to set tree as current
 -E is to enable

At anytime you can enable/disable/remove a tree with

  66-tree -t TREE_NAME OPTIONS:
  -E: Enable
  -D: Disable
  -R: Remove

Enable/Disable service(s)

First decide which tree or newly created tree the service will go in, for this example we are using the newly created default tree.

Enable service in tree: default

  66-enable -t default sshd

Disable service in tree: default

  66-disable -t default sshd

Start/Stop service(s)

Same tree using in this example: default


  66-start -t default sshd


  66-stop -t default sshd
  • Note: In order to start a service, it first my be enabled in a tree and started from that tree.

66's boot config/boot-services are edited using:

  66-env -t boot -e $EDITOR [email protected]

This allows one to change timezone, console font, services, hostname and etc started during boot process,etc. If the config is changed the config must be activated using:

  66-enable -t boot -F [email protected]
  • Do be careful of editing.

User services

User services are placed in:


66's user services are useful for services that does not need root privileges and prefer to run as a user. To be able to use this feature first install the scandir-66 package

  pacman -S scandir-66

In order for user(s) to be able to run their services, the admin must enable scandir for the user's service directory. For this example, user's username is artix. The following must be run as root:

  66-enable -t TREE_NAME [email protected]
  66-start -t TREE_NAME [email protected]

Now a user can place their service files in $HOME/.66/service and run as a regular user:

  66-tree -cnE TREE_NAME
  66-enable -t TREE_NAME service
  66-start -t TREE_NAME service