As we have seen in thread 666 (https://forum.obarun.org/viewtopic.php?id=666) a key element in the new 66tool-kit is the term tree. After I applied the shift to 66 from the s6 supervision system, I have been left with some confusion about the trees. Yes, we should be patient of the documentation that is in the making, but patience is not a virtue that we all share.
So, I will list some assumptions that can be corrected.
0 The whole purpose of this is to have bundles (trees) of services readily turned on and off when needed or not, without manually have to bring them up/down individually one by one. (but a small script with s6opt enable a, f, s | s6opts disable e, g, k would have been the same?)
1 The true init as pid1 is still s6. 66 takes over after init.
2 A tree is something like the s6 database, the difference is that you can have more than one - ?active? - complementing the prime db (tree).
3 The clone of a tree is a copy of the tree that you can add or subtract more/less services/daemons
4 Your 2nd and 3rd tree will remain active on the reboot until you disable it again. So if you have tree1 initially with minimal services to login to the system, you activate tree2 with some more, and tree3 with even more, all three will be active next time you boot, unless you have disabled 2 or 3 or both.
5 If you have tree1 with services a.b.c and you clone it to create tree2 but on tree2 you add d and e but then disable service b. With tree1 and tree2 active, is b active or not?
6 When 66scandir goes through the s6 sv directory and looks for ****-s6serv scripts, does it automatically enable them. Then what is the purpose of tree? If it does not enable, just recognizes they are available, at this stage of development, how does my acpid or bundle-Alsa work when I did not add them in a specific active tree?
Other notes
1 -v (verbosity) 0-3, 1-10, 1-1000? As far as I have seen it is like an on/off switch, but maybe for other services it makes sense.
2 I like the -h standard for help better than the --help, as I like the difference of the 66*tool* with nothing following it returns the format of the command, while 66*tool* -h returns details of the options.
3 pstree (and options like -a) help understand the difference between s6opts and 66 better, if you have 2 systems side by side to compare, or take a screenshot before the transition to 66 and compare it with after.
4 The difference between s6serv and s6rcserv I never completely understood, will they exist side by side with 66?
I hope I am not adding confusion because I am confused, but maybe some clarification of such matters should be included in the documentation or be clarified by it. If others who try it at this alpha-beta stage come up with more I think this may help the creator of 66 document his work better.
So, I will list some assumptions that can be corrected.
0 The whole purpose of this is to have bundles (trees) of services readily turned on and off when needed or not, without manually have to bring them up/down individually one by one. (but a small script with s6opt enable a, f, s | s6opts disable e, g, k would have been the same?)
1 The true init as pid1 is still s6. 66 takes over after init.
2 A tree is something like the s6 database, the difference is that you can have more than one - ?active? - complementing the prime db (tree).
3 The clone of a tree is a copy of the tree that you can add or subtract more/less services/daemons
4 Your 2nd and 3rd tree will remain active on the reboot until you disable it again. So if you have tree1 initially with minimal services to login to the system, you activate tree2 with some more, and tree3 with even more, all three will be active next time you boot, unless you have disabled 2 or 3 or both.
5 If you have tree1 with services a.b.c and you clone it to create tree2 but on tree2 you add d and e but then disable service b. With tree1 and tree2 active, is b active or not?
6 When 66scandir goes through the s6 sv directory and looks for ****-s6serv scripts, does it automatically enable them. Then what is the purpose of tree? If it does not enable, just recognizes they are available, at this stage of development, how does my acpid or bundle-Alsa work when I did not add them in a specific active tree?
Other notes
1 -v (verbosity) 0-3, 1-10, 1-1000? As far as I have seen it is like an on/off switch, but maybe for other services it makes sense.
2 I like the -h standard for help better than the --help, as I like the difference of the 66*tool* with nothing following it returns the format of the command, while 66*tool* -h returns details of the options.
3 pstree (and options like -a) help understand the difference between s6opts and 66 better, if you have 2 systems side by side to compare, or take a screenshot before the transition to 66 and compare it with after.
4 The difference between s6serv and s6rcserv I never completely understood, will they exist side by side with 66?
I hope I am not adding confusion because I am confused, but maybe some clarification of such matters should be included in the documentation or be clarified by it. If others who try it at this alpha-beta stage come up with more I think this may help the creator of 66 document his work better.