joborun/web
2
1
Fork 0
Code Issues 2 Pull requests Projects Releases Wiki Activity

add 66-v2.md

Browse source 
About 66 > 0.7.0.0
This commit is contained in:
joborun linux 2024-11-22 08:59:35 +01:00
parent 1147ce2b4a
commit 0fd58ba43f
1 changed files with 38 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

38
66-v2.md Normal file
View file

@ -0,0 +1,38 @@
### [[Back to the top joborun wiki page|index.md]] ###
#### If you do want to try it on your own see section below this discussion
The new version of 66 appearing May 2024 as v 0.7.0.0 is so different than the previous version that is a wonder why it is still called 66 and not have a different name.
We have built and experimented with its evolved edition 0.8.0.0 using our existing and current build stack of s6/skalibs/execline ..etc. (branded skarnet group in our jobcomm repository), same as Obarun is currently using.
As we have gotten 0 feedback for questions and configuration problems we have given up trying to harness the beast. Our skarnet stack is complete with s6-rc available for anyone to build their system and at this point it appears easier to learn and use s6-rc than manage its equivalent of 66. 66 presented a more user friendly way in managing s6/s6-rc and we can not say this for this new version.
Basically the shell 66 command base is too unforgiving to any syntax mixmatch without being consistent. Command, flag, option, object when switched around in order just fail, 0 feedback, and just the 66 --help output as response. No documentation to clarify why and how the order of commands flags options must go. So if you do experiment with it, keep a notebook, and when in the n-th time you get a command right make a note of it so you don't repeat the entire sequence of 9 out of 10 fails you get for EVERY SINGLE attempt to modify anything.
We can not maintain and support something we can not explain well or be able to answer on why should something work the way it does or why it wouldn't.
** Too much guess work and too little feedback **
### Try 66 0.8.0.0
First of all you must enable obcore and observice repositories in your pacman.conf
If you have 66-EOL installed it must be removed.
66-EOL packages removed (use the rm.66 script) then disable the 66-EOL repository
Our runit setup will not interfere with the existence of obarun's s6/66 except for init,poweroff,reboot,shutdown,halt files would need to be redefined in our corresponding /usr/local/bin/poweroff,reboot,shutdown,halt and on the boot loader you remove init=/usr/bin/runit-init for s6/66 booting.
modules opentmpfiles obsysusers can be replaced by obarun's
From then on you are on your own ..
## In the future
When we are able and adequately proficient to support 66 and when communication with 66 developers is open we may consider re-adopting the maintenance of the 66 system.
### UNTIL THEN we will only support runit which takes minutes to learn instead of years