Yes, we should be patient of the documentation that is in the making, but patience is not a virtue that we all share.
yes you should be.
@ 0
s6opts and 66 haven't the same design and implementation on the system(not the same directory, not the same manner to copy file, not the same directory to store file, and so on). s6opts is a script where 66 in a program written in C. Not the same bugs problem, not the same rapidity to execution, not the same ability to add feature and so on. S6opts was created to see how s6 and s6-rc works, how to implement it and to manage file for service, 66 take experience of this and improve a lot the things like children with his father.
@ 1
no, 66 tools are wrapper around s6 and s6-rc program, some are combination of divers skarnet program. You can do what 66 tools do using skarnet program more a lot of coreutils program(mkdir,mkfifo,mv,rename and so on).
@ 2
no, a tree is a set of divers kind of service (pure s6 service and s6-rc service, so classic, longrun,oneshot,bundle).
@ 3
yes but to be correct, the clone can serve for different thing like make a backup of service set before changing something. You don't need to make a clone to modify a tree, you can simply modify it directly, it's just a safe manner to works on your service set or to have a template to make a new tree.
@ 4
correct
@ 5
b is active yes, because is already enable on the tree1. Be aware that each tree are independent from each other (this will change in the future). So you cannot have a service on tree1 which depends of a service on tree2. Every service dependencies need to be found on the same tree.
@ 6
66 don't care about directory/files used by s6opts, 66 tools do not use the same directories that s6opts, the service file for 66 tools need to be at /etc/66/service. Furthermore, s6opts to create/enable a service use a bunch of files (files that corresponds to the original one from s6 program), 66 tools use a unique file where you can define and configure any kind of service with a easy and simple syntax then it will parse this files and make the appropriate and corresponding s6 files (the frontend file documentation is not completely corrected but the main things are there).
the purpose of 66-scandir is not to parse or enable a service but to create at a correct destination the necessary directories to be able to start a scandir with s6-svscan program and to manage the service file on this directory.
other notes
@ 1
-v is for verbosity, that mean 66 tools will display more or less information about what it do. 1 mean only display error message, 2 add warning, 3 extremely talkative
@ 4
that's the point, now only one file for every kind of service. to be simple : you want a simple service which doesn't depends on any other like dhcpcd , use @ type=classic, you want a service that need some other service running to works properly use @ type=longrun, you want a service which do some operation on the system like creation of directory , checking file and so on use @ type=oneshot ...
Now to be more clear about the utility of a tree :
First, this concept cannot be found on any other service manager/service supervision, that's an original concept with 66 tools.
Let's take a stupid example :
Tree1 contain dhcpcd,ntpd
Tree2 contain cups, nfs
Tree3 contain xorg,notification-daemon,gvfsd, dbus
when your boot your machine and want to use it on console , you don't care about xorg or cups, you only care about internet connection. So at the base you only have Tree1 enabled, at every boot this tree will be started and so all the daemon into it.
Now you need to print something but for this, you also need to start the nfs daemon because your document is on some other server. What you need to do, normally you need to start cups than start nfs. Using tree you start the tree and all service that you need is available. When you have finished to print your awesome document instead of stopping service one by one you simply stop the tree and all the daemon on it will be stopped.
Now you want to see a video, you need a X server running and maybe a lot of daemon. What you need to do, just start Tree3.
Like i said it's a stupid example but give you an idea that what is can be possible.
Again , you should be patient, the works about documentation is done with Marian to be as much as possible proper about syntax and language and understandable.