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

Update '66-setup.md'

Browse source 
Note the add.66 and 66.setup scripts at /home/make
This commit is contained in:
joborun linux 2022-06-13 21:25:17 +00:00
parent a6e840aa93
commit d4c09f4815
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
66-setup.md
View file

@ -1,6 +1,12 @@
### [[Back to the top joborun wiki page|index.md]] ###
edit: Note that on the joborun image available (see the download page on the main web page at http://pozol.eu) the home directory of user make (/home/make) contains a script for adding 66 to the runit installation and contains an intial setup.
If after playing with it you think you messed up, run this other script called 66.setup, which pretty much does what is explained here. This will return you to the default 66 bootable state.
#### How to setup 66 trees and services in joborun ####
@ -12,6 +18,7 @@ We can only use our own default setup as a suggestion, but if and when you make
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!
@ -89,5 +96,6 @@ Now see what you have created, it should look just like the setup when you first
<pre># 66-intree -zg </pre>
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.