66-deeper.md

title: The 66 Suite: deeper understanding author: Eric Vidal eric@obarun.org

66

Software

obarun.org

Deeper understanding

This documentation explains the internal structure of 66 on the system and the roles of the different directories and file components.

Never manually changes any directories or files within the 66 ecosystem,as this is the best way to break it.

%%system_dir%%

This directory is specified at compile time by using the --with-system-dir= option to ./configure.

This directory stores trees and services configuration files. You should see this following structure

%%system_dir%%
└── system
    ├── .resolve
    │   ├── service
    │   │    ├── services -> %%system_dir%%/system/service/svc/<service>
    │   │    └── services -> %%system_dir%%/system/service/svc/<service>
    │   ├── Master
    │   ├── <tree> resolve file
    │   └── <tree> resolve file
    └── service
        └── svc
            ├── <service>
            │   ├── .resolve
            │   │   └── <service> resolve file
            │   ├── state
            │   │   └── status file
            │   ├── file
            │   └── file     
            ├── <services>
            │   ├── .resolve
            │   │   └── <service> resolve file
            │   ├── state
            │   │   └── status file
            │   ├── file
            │   └── file    
            └── <service>
                ├── .resolve
                │   └── <service> resolve file
                ├── state
                │   └── status file
                ├── file
                └── file

The exact same structure is also available for regular users at the ${HOME}/%%user_dir%% directory.

The %%system_dir%%/system/.resolve directory contains resolve files for trees. Each tree have its own resolve file, while the Master resolve file contains information about all trees available on the system.

The %%system_dir%%/system/.resolve/service directory consists of symlinks that point to resolve files for each service. These symlinks enable 66 to quickly access the resolve files for individual services, facilitating the construction of the complete graph of services interdependences.

The %%system_dir%%/system/service/svc directory includes service directories, each housing the results of the parse process, as well as internal directories and files essential for 66.

%%system_dir%%/system/.resolve/

The content of the resolve file for a tree, such as %%default_treename%%, can be viewed using the 66 resolve command in the following manner

66 tree resolve global

This displays information in a self-explanatory manner

name        : global
depends     : None
requiredby  : session
allow       : 0
groups      : admin
contents    : consolekit consolekit-log dbus dbus-log networkmanager networkmanager-log
ndepends    : 0
nrequiredby : 1
nallow      : 1
ngroups     : 1
ncontents   : 6