How would I go about rebuilding my tree from scratch? Currently, the error I have on screen is about "unable to initiate earlier service of tree:boot"
The wiki has an introduction to 66 entry, and also has an entry about dbus and user tree services (
https://wiki.obarun.org/doku.php?id=dbus_and_dm). Those two without reading anything else should have plenty of practical information on how to delete all current trees, make new ones, and enable services in them.
Basically to boot and have a fully functional console you need:
root shell or use sudo in front:
1 # 66-intree -zg root (record what services you have enabled on root tree)
2 # 66-tree -R boot (remove boot tree)
3 # 66-tree -R root (remove root tree)
4 # 66-intree -zg (will show you if you have any other root level trees)
if you do, record their services and repeate the removal command for each of these trees.
5 # 66-intree -zg (you should have no trees now)
6 # 66-tree -n boot (create a (n)ew boot tree /etc/66/init.conf defines to the init which tree to run, you can change the name there and call it kukuruku if you don't like the word boot)
7 # 66-enable -t boot boot (enable on (t)ree boot the service bundle named boot - the contents of boot-66serv)
8 # 66-tree -ncE root (create root tree, (n)ew, (c)urrent, (E)nabled
9 # 66-enable -t root tty@ tty1 (this will give you tty1 console to log in, nothing else running ... feel free to add other things, dhcpcd, tty@ tty{2,3,4,5} connmand, cupsd, sshd, ntpd, sddm, ......
After 7 you can reboot and you will have to switch to tty12 (Ctrl-Sift-F12) the next steps are optional :)
For 66 to run user services you first need a user level scandir created and active, this is what the
https://wiki.obarun.org/doku.php?id=dbus_and_dm wiki explains. I never use it myself but I've done for many others' computers and I have yet to deal with a problem with it. Most of my victims don't know the difference between what they are using, ubuntu, or ms-W7 ... they just enter their name and pw and it works.
What you said about Debian with systemd being paralyzed is why most of us are here. Because systemd is fine for dummies when it works, when it fails it is a maze of dynamic events that hardly anyone can diagnose anymore. If you had hired red-hat to provide support and maintenance I assure you that you wouldn't have problems with upgrades :D They are the best in the business (mafia, nSA, etc).