8 days later
skalibs: local (2.6.4.0-1) is newer than 66 (v2.7.0.0+7+g1af5a42-1)

???
7 days later
Package (28)                          Old Version             New Version               Net Change  Download Size

66/66                                 0.0.0.1-15              0.0.0.1-16                  0.05 MiB       0.17 MiB
66/boot-66serv                        0.0.1.0-1               0.0.1.1-1                   0.00 MiB       0.03 MiB
obarun/device-mapper                  2.02.182-3              2.02.183-2                  0.00 MiB               
obarun/lvm2                           2.02.182-3              2.02.183-2                  0.00 MiB       1.32 MiB
66/oblibs                             0.0.0.1-2               0.0.0.2-1                   0.00 MiB       0.03 MiB
obarun/qt5-base                       5.11.2-4                5.12.0-2                    0.73 MiB               
66/root-66tree                        0.0.1-1                 0.0.2-1                     0.00 MiB       0.01 MiB
I applied the above updates and booted (no VM), everything is fine.
thanks for the feedback
The documentation is now complete, the first official release will come soon
1) you need to write a service file and save the result to /etc/66/service
2) enable it on a tree enabled at boot time , to check that use 66-info -T name_of_tree : refers to http://repo.obarun.org/66/66-info.html, by default the tree will be named root
1 
[main]
@ type = classic
@ name = sshd
@ description = "sshd daemon"
@ user = ( root )
@ options = ( log env )

[start]
@ build = auto
@ execute = ( execl-cmdline -s { /usr/bin/sshd ${CMD_ARGS} } )

[environment]
!CMD_ARGS=-f /etc/ssh/sshd_config
66-enable -t tree1 sshd
66-info -T tree1
|-dbus :classic
|-dhcpcd :classic
|-tty2 :classic
|-tty1 :classic
|-tty6 :classic
|-sshd :classic
`-ntpd :classic
you got it :), very easy to make an new service , isn't it?
If you think it is right, I have no idea :)

I tried to interpolate between the format of -66serv and sshd-s6serv
a month later
I get some garbled error on login prompt and jumps to emergency shell, I hit exit a couple of times, it returns to login:
I login and at least dhcpcd has to be started manually
This is not due to the recent update in 66, I just wasn't able to figure it out.
This is partial log, before after error, then it continues down with similar messages to the last.
/run/66/log/uncaught...
@ 400000005c49ac4b05d4c27c _d /run/nscd 0755 root root 0 
@ 400000005c49ac4b06826f6c _C /etc/crypttab  0 0 0 
@ 400000005c49ac4b0684442c _C /etc/fstab  0 0 0 
@ 400000005c49ac4b06859bec _C /etc/group  0 0 0 
@ 400000005c49ac4b0686f3ac _C /etc/gshadow  0 0 0 
@ 400000005c49ac4b068866c4 _C /etc/host.conf  0 0 0 
@ 400000005c49ac4b0689fd04 _C /etc/hosts  0 0 0 
@ 400000005c49ac4b068b6464 _C /etc/issue  0 0 0 
@ 400000005c49ac4b068c624c _C /etc/ld.so.conf  0 0 0 
@ 400000005c49ac4b068dc9ac _C /etc/motd  0 0 0 
@ 400000005c49ac4b0731f8ec _C /etc/nsswitch.conf  0 0 0 
@ 400000005c49ac4b07340074 _C /etc/passwd  0 0 0 
@ 400000005c49ac4b07355c1c _C /etc/profile  0 0 0 
@ 400000005c49ac4b0736f25c _C /etc/securetty  0 0 0 
@ 400000005c49ac4b07386574 _C /etc/shadow  0 0 0 
@ 400000005c49ac4b076acfb4 _C /etc/shells  0 0 0 
@ 400000005c49ac4b0775acf4 rwfs-tmpfiles successfully started
@ 400000005c49ac4b113e7b6c 66-all: fatal: unable to selfpipe_trap: Device or resource busy
@ 400000005c49ac4b114787d4 66-dbctl: fatal: unable to bring up services list
@ 400000005c49ac4d062b4304 cleanup idle workers
@ 400000005c49ac4d062d65e4 Unload module index
@ 400000005c49ac4d062d7d54 Unload module index
can you confirm that's occurs even with the previous version of 66 (0.0.0.1-16) ?
Sorry for the delayed response, I tried on a virt.image that hadn't been updated and there was no error, after upgrade I did get the error, I revert back from 17 to 16 and the error went away. Same thing with my franken-void-66 installation.
I must have booted twice after the upgrade and since I got things working I forgot to look at the log and in my mind it remained that there was an error before the upgrade.
I hope you know what it means because I sure don't :)

PS Is the uncaught log created only if there is a warning or error between stage 1 and 2 or is it supposed to be created at all times, even when there is no boot error? Because I can't find the log now.
please update the 66 package

note a lot of changes comes with it, it should works but a good idea is to update your system to reflect the changes
# 66-enable -v3 -f -t boot boot
make the same thing for all your daemon e.g 
# 66-enable -v3 -f -t root dbus dhcpcd
the environment part have some important change, so re-enabling the daemon apply those changes (like using the new API 66-envfile) but again even if you don't do the force enable progress the things should goes right.
Ok, I am now on 66...18 rebooted after the above enabling procedure, all well.
Is it significant that login prompt (tty1) came out twice before I hit a key?
23 days later
That instant use of dhcpcd in the video looks attractive! I really want to get rid of connman, as that depends on DBus, and that just looks too complicated!
Straightforward internet connections are a good thing.
Are you on 66 or s6opts?
The 66 is in a beta phase replacement of the system, read from the beginning of this thread.
It only comes with about 4 service scripts, anything else you have to write yourself at this stage.
With ethernet it works fine, with wifi you will need wpa_supplicant and that needs some manual configuration and a service script. There are some aur wrappers for wpa_supplicant that help you configure wifi through a gui/tui thing.

Powered by Obarun