thanks eric
i read the wiki before doing a minimal install.
i looked into my .zsh history and these are all the commands i've typed as root user that relates to 66, dbus and dms:
pacman --noconfirm -S lightdm-66serv && pacman --noconfirm -S dbus-66serv consolekit2 consolekit-66serv
pacman --noconfirm -S boot-user@ -66mod
66-mods.sh boot-user@ myuser
66-tree -nE myuser-session
66-enable -t myuser-session All-myuser
66-tree -ncE desktop
66-enable -t desktop dbus consolekit lightdm
sudo -u myuser 66-tree -nE myuser
sudo -u myuser 66-enable -t myuser dbus-session@ myuser
other noteworthy stuff.
inside /home/myuser/.66/conf/boot-user/boot-user@ myuser.conf file i do see a line:
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/dbus.
/run/user/1001/dbus socket/file does exist
Running services with name dbus:
PID USER Command
834 root s6-supervise desktop-dbus-log
835 root s6-supervise desktop-dbus
862 s6log s6-log -d3 n3 T s1000000 /var/log/66/dbus
867 dbus dbus-daemon --system --print-pid=4 --nofork --nopidfile --address=unix:path=/run/dbus/system_bus_socket
1066 myuser s6-supervise myuser-dbus-session@ myuser
1069 myuser s6-supervise myuser-dbus-session@ myuser-log
1084 myuser s6-log -d3 n3 T s1000000 /home/myuser/.66/log/dbus-session@ myuser
1088 myuser dbus-daemon --session --print-pid=4 --nofork --nopidfile --address=unix:path=/run/user/1001/dbus