The following is taken from my system, running live and well.
# 66-info -T
               boot           
Initialized: yes | Current: no
Contains:       | Enabled: no

               root           
Initialized: yes | Current: no
Contains:       | Enabled: yes
Initialized, Current, Contains, Enabled

from: http://web.obarun.org/software/66-info.html
The first line gives you useful information about the tree itself where Name is the name of the tree, Current tells if the tree is the current one or not—see 66-tree -c and Enabled reveals the state of the tree—see 66-tree -E. For each service the first number found between '()' bracket is the corresponding pid of the service, the type of the service is shown next to it. Finally the name of the service is displayed.
I think a little more information and explanation is needed. The data from those 4 fields are yes no and sometimes flashing. Contains never seems to contain anything.
the list of the service below contain IS the field contains :)
Initialized: yes/no blinking
Current: y/n
Contains: list of services
Enabled: y/n

Ok, what about the other three?
what do you mean by the other tree?
fungalnet wroteInitialized: yes/no blinking
Current: y/n
Contains: list of services
Enabled: y/n
I am not very clear when those other three fields should say yes, when no, and when blinking. Ok, I understand enabled but enabled, not current, not initialized ..? What makes a tree Initialized, what makes it current, what makes it enabled?
I understand that we create a tree and we enable services on the tree, we alse start services, but the tree can exist without any services. When I read the output of 66-info how do I know what is supposed to be yes, what no, what it means when it is blinking.
initialized -> first, with the new 66 version this field do not blink anymore(only current field blink)
So, if you never use 66-init or 66-all(which is call 66-init if the tree was not initialized) or 66-start(which is call 66-init if the tree was not initialized) that mean that any services of the tree is currently running. If you try an htop command you will any service running of this tree. So the tree was not initialized into the scandir, for example /run/66/tree/<uid>/<tree> do not exist,/run/66/scandir/<uid>/ do not contain any services name of the tree and and /run/66/state/<uid>/<tree> doesn't exist.
Well initialized pointing to no means : Any services of the tree is currently running.

current -> yes, that means that the tree is the current one. This is specified when you use 66-tree -c. The -c option means make it as current. When you do a command like 66-start -t root ntpd , you tell to 66-start to use the tree root but if you set the tree as the current one you can use : 66-start ntpd. The tools know which tree to use because you have already define it. If any tree was defined as current the 66 tools will complain about which tree to use.
so current -> yes you can use any 66 tools without specified the -t option and all command will be applied on this tree. This field blinks if it's the current one because it's really easy when you have a bunch of tree to forgot which one is the current one and so you see quickly the current one when you do a 66-info -T command.

enabled -> yes, meaning that tree will be used when you do 66-all command. This command (if you don't specify the tree to use) will start all service for ALL tree marked enabled.
So for example if you have a tree named X containing services and marked enabled and an another one called Y containing services and marked disabled and you .xinitrc contain the command 66-all up, the 66-all command will bring up all service of the tree X but not the services into the tree Y.

I hope i'm clear, i'm not really awaken to write this post :p
So if for some reason your root tree is causing problems but you have a backup-root-04-14 you can make that one current and disable root, reboot and backup will be current. ?? This can work?
no current only concerns 66 tools, if you want to change the tree used by the init script , edit the file /etc/66/conf/boot and point the variable TREE to the desired one
Yeah backup is really integrated :p

In the future a tools will be made to replace a tree by a backup one like 66-backup

Powered by Obarun