Hey @eric if I want to start the trees boot, net and finally global, is this command right?
sudo 66 tree admin -o depends=boot,net
New release coming
@wastelander
You missed the name of the tree at the command line, right?
In theory yes, but you don't need to depends on boot. The tree boot is always launched at boot time. So any other trees are sure to already have the boot tree started.
Can you describe a little more what your try to accomplish? For example, what you want to do with the net tree?
@eric i wanted to start a net tree after boot but before global. I didn't write the name of the global tree at the end of the command because I thought that being global a default tree the name was unneeded:) however I would need the net tree with wpa_supplicant and dhcpd/dhclient enabled, while connmand would stay in global and so start later.
- Edited
You have different way to accomplish this
If your tree is already create you can administrate it to make requiredby dependency changes
$ sudo 66 tree admin -o requiredby=global net
or you can do
$ sudo 66 tree admin -o depends=net global
You have the exact same result, global
will start after net
. Passing through the first command allow to make correct interdependence without the need to touch an existing tree, and so, you can configure it at creation time too
$ sudo 66 tree create -o requiredby=global net
This is the shortest way.
For the sake of the example
enable
wpa_supplicant
,dhcpcd
, anddhclient
at net tree :$ sudo 66 -t net enable wpa_supplicant@wlan0 dhclient@enp0s6 dhcpcd
and enable to global
connmand
$ sudo 66 enable connmand
I don't known what you do exactly but this configuration will make conflicts between dhcpcd
and connmand
, you should only use one network manager at a time.
you can for example disable connmand
and start it manually when you need it by a 66 start
command.
Thank you so much @eric , you really cleared out all my doubts:). Yes, sure, I would just want to enable either connmand or dhcpcd, the reason why I would not enable connmand is that sometimes it doesn't connect when using a VPN, so I should manually create a wpa_supplicant-wlan0.conf file and just leave the wpa_supplicant@wlan0 enabled in the net tree.
- Edited
Just tested it and it's working great, though dbus seems to create duplicate in both global and session tree when I uncomment sddm in the display-manager line in boot-user@ module file. Also it cannot find consolekit service file after uncommenting the console-tracker line in same module.
edit: the duplicate entry is fine with me since it just relists the same pid.
parse: info: launch configure script of module: boot-user@orb
boot-user@orb: info: add dependency:
boot-user@orb: info: set environment at .xsession file to: /home/orb/.66/conf/svscan@orb
boot-user@orb: warning: move existing /home/orb/.xsession file to /home/orb/.xsession-53857301382.backup
boot-user@orb: info: create /home/orb/.xsession
boot-user@orb: fatal: the consolekit frontend service file do not exist on your system -- please install it and try again
Name : global
Current : no
Enabled : yes
Allowed : root
Groups : admin
Depends : \
└─None
Required by : \
└─session (Enabled)
Contents : \
├─wpa_supplicant-log (pid=1157, state=Enabled, type=classic, tree=global)
├─connmand-log (pid=1051, state=Enabled, type=classic, tree=global)
├─dbus-log (pid=1046, state=Enabled, type=classic, tree=session)
├─ntpclient-log (pid=1156, state=Enabled, type=classic, tree=global)
├─seatd-log (pid=1050, state=Enabled, type=classic, tree=global)
├─wpa_supplicant (pid=1198, state=Enabled, type=classic, tree=global)
├─dbus (pid=1060, state=Enabled, type=classic, tree=session)
├─ntpclient (pid=4009, state=Enabled, type=classic, tree=global)
├─seatd (pid=1073, state=Enabled, type=classic, tree=global)
└─connmand (pid=1079, state=Enabled, type=classic, tree=global)
Name : session
Current : no
Enabled : yes
Allowed : root
Groups : admin
Depends : \
└─global (Enabled)
Required by : \
└─None
Contents : \
├─consolekit-log (pid=1110, state=Enabled, type=classic, tree=session)
├─dbus-log (pid=1046, state=Enabled, type=classic, tree=session)
├─sddm-log (pid=1270, state=Enabled, type=classic, tree=session)
├─scandir@orb (pid=up, state=Enabled, type=module, tree=session)
├─scandir@orb:setenv@orb (pid=up, state=Enabled, type=oneshot, tree=session)
├─scandir@orb:svscan@orb-log (pid=1167, state=Enabled, type=classic, tree=session)
├─boot-user@orb:mount-run@orb (pid=up, state=Enabled, type=oneshot, tree=session)
├─dbus (pid=1060, state=Enabled, type=classic, tree=session)
├─scandir@orb:svscan@orb (pid=1197, state=Enabled, type=classic, tree=session)
├─consolekit (pid=1119, state=Enabled, type=classic, tree=session)
├─sddm (pid=0, state=Enabled, type=classic, tree=session)
└─boot-user@orb (pid=up, state=Enabled, type=module, tree=session)
Smooth transition otherwise, thanks for the clarity😎
- Edited
Wat-now dbus seems to create duplicate in both global and session tree
Nope, even on global
tree your get dbus (pid=1060, state=Enabled, type=classic, tree=session)
. So the last parameter is tree=session
and show you the associated tree of the dbus service. You also should transfert it to global
. In practice this doesn't change anything, i mean you will get a good start order of the services, but it's little weird as your tree session depends on global
. That means that consolekit will ask for dbus (66 will start it for sure) where dbus can be already up if you transfert it to global
.
Simply you can do:
66 -t global enable dbus
Wat-now Also it cannot find consolekit service file after uncommenting the console-tracker line in same module
That's odd as your consolekit daemon seems running. Do you have the frontend at file at /etc/66/service
, /usr/share/66/service
?
- Edited
eric
You also should transfert it toglobal
It was in global until i enabled sddm, so it seems when I do that, it transfers it from the global tree into the session tree. Unless.... I should start sddm in global tree as well?
eric Do you have the frontend at file at /etc/66/service, /usr/share/66/service?
yes
Hum, maybe a little glitch exist with the boot-user@ service. Need to check that
Anyway, you don't need to switch sddm. Sddm is not "mandatory" for a system (even dbus, but dbus can be largely used by other service) and as long as global is started first sddm will find up dbus when it will be its turn to be up.
But again, it's just a question of esthetic, your services will be started in a good order anyway
It's working very nicely as I have been testing but there is one quirk I've run into that may be addressed:
1st when I use sudo 66 reconfigure boot-user@orb
it takes that module from session tree and populates global tree instead
- Edited
Can you give us the complete process you did to get this behavior? for instance, what the key=value
changed before launching the reconfigure
command. I would like to reproduce it, this is not expected.
A workaround can be:
sudo 66 -t <treename> enable boot-user@orb
and you should get boot-user@orb associated to <treename>.
My user tree doesn't seem to start automatically, after logging in through SDDM the tree services remain pid=0 or uninitialized:
$ 66 -z tree status -g
Name : global
Current : no
Enabled : yes
Allowed : myuser
Groups : user
Depends : \
└─None
Required by : \
└─None
Contents : \
├─dbus@myuser-log (pid=0, state=Enabled, type=classic, tree=global)
├─xdg-user-dirs (pid=unitialized, state=Enabled, type=oneshot, tree=global)
└─dbus@myuser (pid=0, state=Enabled, type=classic, tree=global)
- Edited
what is the contents of your ~/.xsession?
eric what the key=value changed before launching the reconfigure command
CONSOLE_TRACKER=consolekit
and consolekit is already started in the global tree. That is what seems to cause the behavior. Yes, the workaround works and even without using the session treename it works just like:
sudo 66 enable boot-user@orb
and still populates the session tree.
eric
Thank you, that helped me solve it. My ~/.xsessions was
list=( $(ls -A1 /home/myuser/.66/conf/svscan@myuser) )
for i in ${list[@]};do
var=( $(</home/myuser/.66/conf/svscan@myuser/${i}) )
for j in ${var[@]}; do
export ${j}
done
done
66-all up
I replaced 66-all up
with 66 tree start
.
my system also locked up after running 66 reconfigure boot@system (just change env to enable handling of swap). also, the installed obarun-install/obarun-install-themes are still from the last version before these 66 changes. also the ones from repo. would have been a "convinient" source for steps to rebuild boot/global/session things!
ive just reinstalled system manually, not using obarun-install and setup a sway environment. had to recompiled sway since some compoments depends on libsystemd. sadly, i cant get waybar to compile so im running without a good bar for now
Ok, so
Enable the boot@ service:
$ sudo 66 enable boot@system
Configure the boot@ service using your preferred editor (replace nano with your editor of choice):
$ sudo 66 configure -e nano boot@system
Apply the changes:
$ sudo 66 reconfigure boot@system
Enable all other services that you require. For example:
$ sudo 66 enable boot-user@oblive wpa_supplicant consolekit connmand openntpd
Configure the boot-user@oblive service using your preferred editor (replace nano with your editor of choice):
$ sudo 66 configure -e nano boot-user@oblive
Apply the changes:
$ sudo 66 reconfigure boot-user@oblive
Enable user-specific services. For instance:
$ 66 enable dbus@oblive
This is the base for an X machine. It's up to you to improve it with your needs. Don't hesitate to ask