I was thinking of waiting a bit for the 66-info replacement to come out at the same time, since it is a key tool for most users, to see what you have done is actually taking effect, now and after reboot.
i thought to tell you that. Actually, i'm just waiting the 20 October(end of the obnews announcement about the v0.2.1.2). The next release is ready yet and so it will come with the 66-intree and 66-inservice which are clearly better to use, more flexible and more understandable.
The user/admin differentiation on one side it seems like a good idea, on the other side it seems as anti-unix/linux, where every user needs to become admin too. Even windows had admin, many people didn't know, of what they could do with it. The way I understand it is the "user" mode is the one who doesn't know or needs to know what s6/66 do. They make an installation, boot and go to work or play. They may be stuck with sddm and plasma for an eternity and will not know how to change to lxdm, or how to enable remote access, or get accurate time on the system, but they have had they installed. So a non-admin user doesn't even need an introductory manual. Why read an introduction to dog breeding if you don't like dogs and never going to have one, or two?
it's not what i had in my mind. A future user want to know quickly if Obarun and s6/66 is a one for him. So, a general view can help at the start like a general overview or a quick start(something like this).
Working on the 66wiki, especially after the addition of 66-tools, I look at it and say that I need to print this and have it hanging next to my screen because I will never memorize all those tools.
That's the point. Some tools are unavoidable (66-{enable,disable},66-{start,stop},66-tree,66-{intree,inservice} and maybe 66-all), the rest are clearly usefull on debug or very special tasks. Do you have played with 66-svctl, 66-init or 66-scandir? I don't think so. It's generally not necessary for a day to day use.
Tools at 66-tools was especially spitted for this reason. It's not a part of 66 and should be on another wiki. Those tools are made to help on service scripts and have nothing to do with service management. Service creation is a policy decision where 66 works on mechanism, it's not the same thing (some dev/user have some difficulty to understand the difference).
1 You make a tree called boot (66-tree -n boot), then you make root -cnE root, and then a third called play (-cn play)??? When you use # 66-enable acpid, does it go to root or play? It errors out as no tree being current. If play didn't exist it would automatically go to root. Is this correct?
for example:
# 66-tree -n boot
# 66-enable -t boot boot
# 66-tree -nE root
# 66-enable acpid
At the last enable command 66 will complain: "unable to find the current tree. You must use -t option". By default you don't have any tree set as current. In this case you must provide the -t option. So , yes when you pass the -c option to a tree every followed command will be apply on this tree. That's why the (blinking) field current exist at 66-info -T command, to show which is the current one
2
# 66-enable -t play acpid
# 66-start -t play acpid
or
# 66-enable -t play -S acpid
Is there a difference?
No difference but i think it's better to explain each command separately to understand clearly which command do what. Also, i found a little trouble with the command 66-enable -F -S acpid where acpid in a classic one and already running. 66 will complain but do the stuff, i need to investigate this before making the new release. Enable a service doesn't mean starts a service. The difference should be understand by every one. For example when you works on a server , you want to change the state of your server after a reboot not the current state of your server. This difference in this case is really important and usefull.