User Tools

Site Tools


boot-user

boot-user@ module

A service as a module-type is highly configurable and its function can be adapted easily to your needs. It also allows you to configure a complex task with a few simple commands.

to enable it simply:

You can create a specific tree named boot-user or enable the module in an existing tree. to create and enable a new tree:

66-tree -nE boot-user

to create the module boot-user@

66-enable -t boot-user boot-user@oblive

in one command you:

- set a nested scandir for the user oblive - configure and write a good configuration file used by the scandir at start time containing for example the DBUS_SESSION_ADDRESS variable. - configure the .xinitrc and .xsession file according to the desktop of choice. - ask to run a console tracker (e.g consolekit) - ask to run a Display Manager (e.g sddm) which will be configured properly to run with dbus and the console tracker.

finally with one command you can start, stop, enable, disable all the parts of the module at once:

66-start boot-user@oblive will do what it needs to be done in order to properly start all the parts of the module in the correct way and order.

Display Manager upcoming options:

Let's say you run sddm as a display manager and sometimes you like to log in to your KDE-Plasma desktop and other times you want the lean functionality of JWM, or a bare clean space of openbox, i3, awesome, etc. Each one needs different services to work properly, but in some cases the same are unneeded. So an sddm@openbox and sddm@plasma can be set differently, or be utilized by different users of the same system. This feature is not yet effective but will soon be available

reframe the boot-user@ service (step 1)

This only concerns those previously using the “boot-user@-66mod”, now “boot-user@-66serv” service.

Remove the installed boot-user@-66mod package and install boot-user@-66serv package, then repeat the procedure below for re-enabling and re-configuring the boot-user@<username> module, see step (1).

boot-user@

The following example with the “oblive” username and “boot-user” tree (as found in Obarun live images) will be used, where the boot-user@-66serv was enabled. Replace those terms with the ones of your choice. If you have not used the old service boot-user@-66mod start at step (2).

Four steps

The following commands should be issued as root

1 First disable the old service:

# 66-disable -t boot-user All-oblive

2 Now enable the new version:

# 66-enable -F -t boot-user -e <editor> boot-user@oblive

3 You need now to configure the boot-user@oblive service.

To edit its configuration file use the 66-env program:

# 66-env -t <tree-name> -e <editor> boot-user@<username>

Your preferred <editor> (vi, nano, mcedit,.. etc) should display the contents of the configuration file. Change what you need inside, save it and exit. To specify the editor used use the -e option, always after the -t tree definition. Example:

# 66-env -t boot-user -e nano boot-user@oblive

Attention (1): If you enable a specific DM in the module, such as LXDM, SDDM, Lightdm, slim, … you must also have installed the display-manager@-66serv module-type service before you enable it. For those using a DM in the past, such as sddm, this is now essential after 66-0.6.1.xx otherwise the module boot-user@ will crash.

After configuring and enabling the module with sddm, a module-type service named display-manager@sddm will also be enabled. It is listed as an optional dependency on boot-user@-66serv but essential if you are configuring a specific display manager in the module.

Attention (2): Depending on your system and your needs, you may want to use the “CONSOLE_TRACKER=” variable. In this case, you also “need” to install the “observice/console-tracker@-66serv” service and the corresponding service to use for example: “consolekit-66serv”.

Finally, to apply your changes you need to re-enable the service:

While configuring the boot-user@ module if you enable a service that has no corresponding service file or is enabled elsewhere the module will fail. Since it will fail 66-env will no longer work. To change the options you will need to manually go to /etc/66/conf/boot-user@/ directory and edit the conf file or replace it with the default copy which has the same name and a . in front.

example:

compare contents:

/etc/66/conf/boot-user@oblive/0.4.2/.boot-user@oblive

/etc/66/conf/boot-user@oblive/0.4.2/boot-user@oblive

Attention (3): If you have already enabled a console tracker like consolekit and/or a display-manager like sddm on another tree, you don't need to enable these services again. Just leave corresponding variables commented.

4 Re-enable the module to pass the new configuration

# 66-enable -t boot-user -F boot-user@oblive

Note: Substitute oblive with the name of the user you are configuring the module for and boot-user with the name of the tree you want.

user level trees

Refer to this document in handling user trees and services user trees

  • boot-user@-66serv
  • console-tracker@-66serv
  • consolekit-66serv
  • dbus-66serv (also contains the dbus-session@ user service)
  • display-manager@-66serv
  • lightdm-66serv
  • lxdm-66serv
  • sddm-66serv
  • slim-66serv
boot-user.txt · Last modified: 2021/02/27 06:32 by wikiman