4.4 KiB
Back to the top joborun wiki page
How to setup 66 trees and services in joborun
Do not be afraid of s6/66, they are your best friend. Experiment all you like, and if something goes wrong, know that it is really simple to get back to a bootable functional system.
this is how
We can only use our own default setup as a suggestion, but if and when you make different choices (than our boring simplicity) it is simple to record your setup and store it so you remember what you have done.
66 author is nearly finishing the work to make it easy, quick, and simple, to store your setup database and be able to restore it at any moment you feel you have made a mess. But till this is announced, we can suggest an easier fix.
Are you happy with how everything works now, or the initial Joborun setup?
If yes, save it!
How? (as root is indicated always with a # sign as user will be % )
# 66-intree -zg
Shows you your system trees, the services enabled in each one, and their current status and logs.
# 66-intree -g >/etc/66/mytrees.txt
Will save your tree structure in this text file. You can use it later if you run into problems to revert to it. Let's assume this is the same as stored in the tarball image of joborun.
# 66-intree -d0 | grep Name
This will give you a list of the names of all your trees (root level but same command as user will give the names of user trees).
# 66-tree -R boot # 66-tree -R net # 66-tree -R root
This will remove the existing trees.
# 66-tree -n boot # 66-tree -nE net # 66-tree -ncE -S net boot
This will recreate those three trees which are now blank. Tree boot is the default boot tree as defined in /etc/66/init.conf, doesn't need to be enabled, as it is by default. Tree net is enabled and it is where network services should be so you have network access as soon as boot finished (similar to stage 2 in runit). Tree root is both enabled, and current/default for any other service you want to enable. Tree root starts right after net.
# 66-intree -zg
This will verify those trees exist and are empty (no services enabled). But it is an optional check.
# 66-enable -t boot boot@sys
This enables the boot module boot@sys in tree boot, it is a name we choose for module boot@. You can substitute sys for any name but you must use one, even if it is a single character, like boot@z
# 66-enable -t net dhclient@eth0 dhclient@wlan0 wpa_supplicant@wlan0
This enables those three services in tree net.
# 66-enable -t root ntpd
This enables the time service ntpd on tree root.
Now, you most likely need to reconfigure the default boot@sys module, replace your hostname, choose the number of ttys you want active at boot, your bios clock and timezone, among other parameters. To do so:
# 66-env -t boot -e nano boot@sys
If you don't like using nano but another console text editor replace nano with the one of choice. It is a self explanatory configuration file. Make sure when you turn options on that you do have the necessary software for those options to take effect. For further details see the documentation at www.obarun.org.
# 66-enable -t boot -F boot@sys
To pass the changes of the boot module to the system for the next reboot you must enter the above command. It Forces the replacement of the configuration.
Now see what you have created, it should look just like the setup when you first installed and booted joborun.
# 66-intree -zg
Compare the output with had you had initially saved, it should be identical. So no need to panic, when in doubt erase all trees and start with a clean setup. After a while the 66 logic will settle in and you will not have to look this up. Feel free to experiment, you can repair this from a chroot if necessary, but even when boot parameters become impossible to boot, there is tty12 as emergency shell. Ctrl Shift F12, log in as user (root is not allowed) look up /run/66/log/0/current. The first reported error is what is throwing your boot process off. If it is not enough to determine the cause increase verbosity to 4 in /etc/66/init.conf and reboot. A more analytical error/warning will be listed. Always read the log top-bottom, the last errors shown may be effects of the real problem, not the cause. It is the first error that matters and should be fixed first.