I've been making progress in making my laptop work with Obarun, and I was quite pleased to see that running boot-user cleared up the odd and incomprehensible troubles that LXDE was having with Dbus and Consolekit. However, since enabling boot-user@ lijsterbes, my beautifully running LXDE jumps up before I login at the TTY. Beautiful and like clockwork - but not what I had in mind.

I love the way boot-user wrangles polkit, dbus and consolekit for me. I'm very happy not to touch that. What I would prefer, though, is that on booting the computer, I get into a TTY to log in, and the whole X circus only starts when I explicitly enter 'startx'.

Is there a way to keep the boot-user functionality, but delay starting of X until my say-so?
can please you post the output of the following command 
# 66-env -L boot-user@ <username>
replacing the <username> by your username, this is obvious.
sudo 66-env -L boot-user@ lijster
66-env: info: contents of file: /etc/66/conf/boot-user@ lijster/0.4.3/boot-user@ lijster

# # Uncomment it to use a display manager.
# # Can be any display manager as long as the
# # corresponding frontend file exist on your system
# # e.g sddm,lightdm,...
# # It also prepare the .xsession file.

# DISPLAY_MANAGER=lxdm

# # Uncomment it to use a console tracker.
# # Can be any console tracker as long as the
# # corresponding frontend file exist on your system
# # e.g consolekit,elogind,...

# CONSOLE_TRACKER=consolekit

# # Create and mount the XDG_RUNTIME directory
# # at /run/user/lijster [yes|no]

XDG_RUNTIME=!yes

# # Command to use in your .xinitrc
# # to launch your desktop e.g.: openbox-session.
# # If commented the .xinitrc file is not configured.

DESKTOP_CMDLINE=!startlxde


66-env: info: contents of file: /etc/66/conf/boot-user@ lijster/0.4.3/.boot-user@ lijster
# # [STARTWARN]
# # DO NOT MODIFY THIS FILE, IT OVERWRITTEN AT UPGRADE TIME.
# # Uses '66-env boot-user@ lijster' command instead.
# # Or make a copy of this file at /etc/66/conf/boot-user@ lijster/0.4.3/boot-user@ lijster and modify it.
# # [ENDWARN]
# # Uncomment it to use a display manager.
# # Can be any display manager as long as the
# # corresponding frontend file exist on your system
# # e.g sddm,lightdm,...
# # It also prepare the .xsession file.

# DISPLAY_MANAGER=sddm

# # Uncomment it to use a console tracker.
# # Can be any console tracker as long as the
# # corresponding frontend file exist on your system
# # e.g consolekit,elogind,...

# CONSOLE_TRACKER=consolekit

# # Create and mount the XDG_RUNTIME directory
# # at /run/user/lijster [yes|no]

XDG_RUNTIME=!yes

# # Command to use in your .xinitrc
# # to launch your desktop e.g.: openbox-session.
# # If commented the .xinitrc file is not configured.

DESKTOP_CMDLINE=!jwm
But I think I tried most permutations.
your boot-user@ configuration is correct, now be sure to not have ~/.zlogin file. This file is responsible to start the X session when you logon from the console.
Second things to look for is the ~/.xinitrc file.
it should be something like this 
# !/usr/bin/bash

exec 1>/home/obarun/xinit.log 2>&1

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

env_export(){
list=( $(ls -A1 /home/obarun/.66/conf/svscan@ obarun | sort) )
for i in ${list[@ ]};do
    var=( $(</home/obarun/.66/conf/svscan@ obarun/${i}) )
    for j in ${var[@ ]}; do
        export ${j}
    done
done
}
env_export

66-all up

# # Try consolekit
if 66-which -q ck-launch-session; then
    cmd="exec ck-launch-session $@ "
else
    cmd="exec $@ "
fi

# # Select the session to start
${cmd} jwm
with the correct value for you as $HOME directory path of your user and the final command passed to X.
Now you should be able to log on console without starting automatically your X session (you must ask for startx) and the necessary user service will be started uniquely when you start your X session.
There exists no ~/.zlogin or any .zlogin file.
$ cat ~/.xinitrc
# !/usr/bin/bash

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

list=( $(ls -A1 /home/lijster/.66/conf/svscan@ lijster | sort) )
for i in ${list[@ ]};do
    var=( $(</home/lijster/.66/conf/svscan@ lijster/${i}) )
    for j in ${var[@ ]}; do
        export ${j}
    done
done

66-all up

# # Try consolekit
if 66-which -q ck-launch-session; then
    cmd="exec ck-launch-session $@ "
else
    cmd="exec $@ "
fi

# # Select the session to start
${cmd} startlxde
Slightly different, but not very different.

And still LXDM logs me in as soon as I power up the laptop.

Perhaps important: I experimented with some settings in the boot-user environment file, and I tried to change them later. Maybe some settings don't roll back well?
Lijsterbes wrote And still LXDM logs me in as soon as I power up the laptop.
if you just want to use startx from a tty, then you certainly don't want LXDM to start, at all.
i'd just remove it..
can please you post the output of 
# 66-intree -zg
% 66-intree -zg

$ sudo 66-intree -zg
[sudo] password for lijster: 
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(202,Enabled,classic) tty-earlier@ tty12
               ├─(up,Enabled,oneshot) system-hostname
               ├─(up,Enabled,oneshot) mount-run
               ├─(up,Enabled,oneshot) populate-run
               ├─(up,Enabled,oneshot) mount-tmp
               ├─(up,Enabled,oneshot) populate-tmp
               ├─(up,Enabled,oneshot) mount-proc
               ├─(up,Enabled,oneshot) mount-sys
               ├─(up,Enabled,oneshot) populate-sys
               ├─(up,Enabled,oneshot) mount-dev
               ├─(up,Enabled,oneshot) mount-pts
               ├─(up,Enabled,oneshot) mount-shm
               ├─(up,Enabled,oneshot) populate-dev
               ├─(up,Enabled,oneshot) mount-cgroups
               ├─(up,Enabled,bundle) 00
               ├─(up,Enabled,bundle) all-Mount
               ├─(up,Enabled,oneshot) system-hwclock
               ├─(up,Enabled,oneshot) modules-kernel
               ├─(up,Enabled,oneshot) system-random
               ├─(up,Enabled,oneshot) modules-system
               ├─(up,Enabled,oneshot) system-sysctl
               ├─(250,Enabled,longrun) udevd-log
               ├─(433,Enabled,longrun) udevd
               ├─(up,Enabled,oneshot) udevadm
               ├─(up,Enabled,oneshot) system-fontnkey
               ├─(up,Enabled,oneshot) system-fsck
               ├─(up,Enabled,oneshot) mount-fstab
               ├─(up,Enabled,bundle) all-System
               ├─(up,Enabled,oneshot) mount-rw
               ├─(up,Enabled,oneshot) mount-netfs
               ├─(up,Enabled,oneshot) local-loop
               ├─(up,Enabled,oneshot) local-sethostname
               ├─(up,Enabled,oneshot) local-time
               ├─(up,Enabled,oneshot) local-authfiles
               ├─(up,Enabled,oneshot) local-tmpfiles
               ├─(up,Enabled,oneshot) local-dmesg
               ├─(up,Enabled,bundle) all-Local
               ├─(up,Enabled,oneshot) all-Runtime
               ├─(up,Enabled,bundle) All
               ├─(891,Enabled,longrun) tty-rc@ tty1
               ├─(890,Enabled,longrun) tty-rc@ tty2
               └─(up,Enabled,module) boot@ system

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(731,Enabled,classic) dhcpcd-log
               ├─(732,Enabled,classic) dhcpcd
               ├─(up,Enabled,oneshot) rclite
               ├─(756,Enabled,longrun) dbus-log
               └─(765,Enabled,longrun) dbus

Name         : net
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(777,Enabled,classic) openntpd-log
               ├─(779,Enabled,classic) openntpd
               ├─(781,Enabled,classic) wpa_supplicant-log
               └─(780,Enabled,classic) wpa_supplicant

Name         : boot-user
Initialized  : yes
Enabled      : yes
Starts after : root net
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(up,Enabled,oneshot) setenv@ lijster
               ├─(838,Enabled,longrun) svscan@ lijster-log
               ├─(875,Enabled,longrun) svscan@ lijster
               ├─(up,Enabled,module) scandir@ lijster
               ├─(up,Enabled,oneshot) mount-run@ lijster
               ├─(841,Enabled,longrun) consolekit-log
               ├─(848,Enabled,longrun) consolekit
               ├─(840,Enabled,longrun) lxdm-log
               ├─(853,Enabled,longrun) lxdm
               ├─(up,Enabled,module) display-manager@ lxdm
               ├─(up,Enabled,module) console-tracker@ consolekit
               └─(up,Enabled,module) boot-user@ lijster

[lijster@ swaffel ~]$ 66-intree -zg
Name         : lijster
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : lijster
Symlinks     : svc->source db->source
Contents     : /
               ├─(1009,Enabled,longrun) dbus-session@ lijster-log
               └─(1013,Enabled,longrun) dbus-session@ lijster

[lijster@ swaffel ~]$
I considered nuking LXDM off the machine, but that would leave the supervision hanging. I figured it would be better to do things 'right' instead of just amputating the DM.
your output are really weird. I means the output of the 66-env command show me that you didn't enabled the console-tracker@ service the display-manager@ too. But your 66-intree output show them enabled and running.
Are you sure to have enabled again the boot-user@ service after a change on your configuration file? 
# 66-enable -t boot-user -F boot-user@ lijster
please confirm us the success of this command and the result in your boot-user tree.
Every time I changed anything, I used 
66-disable -t boot-user boot-user@ lijster
66-enable -t boot-user boot-user@ lijster
66-update
But apparently, the -F switch makes a big difference:
[lijster@ swaffel ~]$ sudo 66-enable -t boot-user -F boot-user@ lijster
[sudo] password for lijster: 
66-enable: info: launch script configure of module: scandir@ lijster
scandir@ lijster: info: set live directory to: /run/66/
scandir@ lijster: info: enable service: setenv@ lijster
scandir@ lijster: info: enable logger options
scandir@ lijster: info: enable notification
scandir@ lijster: info: set verbosity level to: 3
scandir@ lijster: info: successfully configured
66-enable: info: launch script configure of module: boot-user@ lijster
boot-user@ lijster: info: enable service: mount-run@ lijster
boot-user@ lijster: info: set environment at .xinitrc file to: /home/lijster/.66/conf/svscan@ lijster
boot-user@ lijster: info: set commandline at .xinitrc file to: startlxde
boot-user@ lijster: warning: move existing /home/lijster/.xinitrc file to /home/lijster/.xinitrc-40254002644.backup
boot-user@ lijster: info: create /home/lijster/.xinitrc
boot-user@ lijster: info: successfully configured
66-enable: info: Disabled successfully: boot-user@ lijster
66-enable: info: Disabled successfully: setenv@ lijster
66-enable: info: Disabled successfully: svscan@ lijster
66-enable: info: Disabled successfully: svscan@ lijster-log
66-enable: info: Disabled successfully: scandir@ lijster
66-enable: info: Disabled successfully: mount-run@ lijster
66-enable: info: Disabled successfully: display-manager@ lxdm
66-enable: info: Disabled successfully: lxdm
66-enable: info: Disabled successfully: lxdm-log
66-enable: info: Disabled successfully: console-tracker@ consolekit
66-enable: info: Disabled successfully: consolekit
66-enable: info: Disabled successfully: consolekit-log
66-enable: info: Enabled successfully: setenv@ lijster
66-enable: info: Enabled successfully: svscan@ lijster
66-enable: info: Enabled successfully: scandir@ lijster
66-enable: info: Enabled successfully: mount-run@ lijster
66-enable: info: Enabled successfully: boot-user@ lijster
And things seem to work as expected now!
To clarify something for other users who may be new to 66, one may have the same exact user module and update/enable it and still have lxdm or another display manager running still, IF the display manager service was enabled separately. In such a case if the DM is not wanted it should be disabled by (# 66-disable -t boot-user -FS lxdm)

In other words the user module can only control its own set of services but it does not prevent one from enabling same services separately. The same may hold true for boot module as well, where you can specify not to have something enabled through the boot module but be able to enable the service independently in the boot tree, or elsewhere.

Powered by Obarun