Commit 20ce8822 authored by Eric Vidal's avatar Eric Vidal 💬
Browse files

prepare for migration to boot@, boot-user@ services

parent 68770c8f
#!/usr/bin/bash
source /usr/lib/obarun/lib/msg.sh
HTML_PAGE="http://web.obarun.org/manager/?a=resource/update&id=121"
MAXDATE=02/15/20
DATE=$(date +%D)
if [[ $DATE > $MAXDATE ]]; then
exit 0 ;
fi
info_bold "From $DATE"
info_void
info_bold "###############################################################"
info_void
info_bold " 66 packages v0.2.4.0 and his childrens"
info_void
info_bold "###############################################################"
info_void
info "${bgreen}This document can be found at :${reset}
- ${HTML_PAGE}
- using the command: ${bgreen}
$ obnews.sh${reset}
This bulletin do not concern fresh installation."
info_void
info "This new version comes with a few more features and tool. It needs
an ${Bold}update of all trees${Reset} on your system as root and regular user.
This tedious task was previously made manually. This new version bring
the ${Bold}66-update${Reset} tool which make a smooth transition between 66 inner format
changes."
info_void
info_bold "###############################################################"
info_void
info_bold " HOW TO: Migration procedure"
info_void
info_bold "###############################################################"
info_void
info "Simply run the following command on your system as root ${Bold}and${Reset}
regular user:
${Blue} -> as root:
${BGreen}
# 66-update -d
${Reset}
${Blue} -> as user:
${BGreen}
% 66-update -d
${Reset}
The commands ${Bold}do not change anything${Reset} on your system. The
'-d' option ask at 66-update to make a dry-run and allow us to check if
the process go right.
If these commands terminate successfully, run again the 66-update removing
the '-d' options to process a real update.
Your system should be now operational and use the corresponding format of
the 66 version currently installed on your system. For further information,
please see the 66-update documentation page.
If the dry-run return you an error and you are not able to fix it,
please ask for help at the Obarun forum, by email at eric@obarun.org or
at the #Obarun chat on freenode and downgrade 66 to the previous version."
info_void
info_bold "###############################################################"
info_void
info_bold " What's news"
info_void
info_bold "###############################################################"
info_void
info_void
info_bold "Frontend files"
info_bold "---------------------------------------------------------"
info_void
info "Two new @key fields called ${bold}@optsdepends${reset} and ${bold}@extdepends${reset}
on the [main] section were added.
This two fields brings flexibility at declaration and enable phase of a service.
${Bold}@optsdepends${Reset} allow us to declare an optional dependencies and can be considere
as \"enable one on this service or none\".
${Bold}@extdepends${Reset} allow us to declare an external dependencies and can be considere
as \"enable the service if it is not already declared on a tree\".
Please see the frontend documentation page for further information."
info_void
info_bold '66-intree'
info_bold "---------------------------------------------------------"
info_void
info "Three new fields were added at information display.
The field ${Bold}\"Starts after\"${Reset} will give you the start order of the tree.
The field ${Bold}\"Allowed\"${Reset} will give you a list of allowed user to use the tree.
The field ${Bold}\"Symlinks\"${Reset} will give you the actually database used by the tree.
Also, a option ${Bold}-n${Reset} were added which permit to not display
the name of the field. This brings facility to retrieve and use informations
on a script. For example this following command return the name and the log file
of all services enabled on all trees available on your system for the owner of the process:
${BGreen}
% for i in \$(66-intree -n -o contents); do 66-inservice -o name,logfile \$i;done
${Reset}
Please refers to 66-inservice documentation page for further information."
info_void
info_bold '66-inservice'
info_bold "---------------------------------------------------------"
info_void
info "According to the new frontend key fields, 66-inservice displays
${Bold}\"Optional dependencies\"${Reset} and ${Bold}\"External dependencies\"${Reset} as new field.
As 66-intree, 66-inservice accept now the ${Bold}-n${Reset} option.
Please refers to 66-inservice documentation page for further information."
info_void
info_bold "Note"
info_bold "---------------------------------------------------------"
info_void
info "
Hope you found this bulletin usefull for you.
If you have any questions or trouble, please do not hesitate in making a report.
Thanks for your attention.
eric.vidal@obarun.org"
info_void
info "${bold}This text can be found at ${HTML_PAGE}.
You can retrieve and read again this bulletin using the command below:${reset}${bgreen}
$ obnews.sh${reset}"
#!/usr/bin/bash
##
## only use space for indentation
##
export PROG=""
export CLOCK_ENABLED=0
export COLOR_ENABLED=1
HTML_PAGE="http://web.obarun.org/"
MAXDATE=12/20/20
DATE=$(date +%D)
if [[ $DATE > $MAXDATE ]]; then
exit 0 ;
fi
BULLETIN_NAME=${0##*/}
BULLETIN_NAME=${BULLETIN_NAME%.*}
oblog -i "
From $DATE
%y
-----------------------------------
| BOOT@-66serv, BOOT-USER@-66serv |
-------------------------------------------------------------------------%n
%gThis document can be found at :%n
- %b${HTML_PAGE}%n
- using the command:
%g$ obnews.sh ${BULLETIN_NAME}%n
A new version of the %wboot-66serv%n(2.2.1) service and %wboot-user%n
(0.4.2) module is available.
These new version comes with a few more features and changes. It needs
a manual intervention to be upgraded to your system.
%y
------------------
| HOW TO MIGRATE |
-------------------------------------------------------------------------%n
%w
--------------------------------------------
| A little word before doing the migration |
--------------------------------------------%n
The %wboot-66serv%n was %rrenamed%n to %wboot@-66serv%n and become a service as type
%wmodule%n like the boot-user@-66mod. Also, the %wboot-user@-66mod%n was
%rrenamed%n to %wboot-user@-66serv%n.
Also, the %w66-mods.sh%n was used previously to configure a module. This
program do %rnot exist%n anymore. The functionnalities of the %w66-mods.sh%n
program was directly integrated at the %w66-enable%n from the %w0.4.0.0%n 66
version.
The %w/etc/66/boot.conf%n file do %rnot exist%n anymore. As the %wboot@-66serv%n
is now service as type module, it will be configured by the %w66-env%n
program(see below).
Onemore, the boot@-66serv package install its corresponding man page to
your system. So:
%b-> as user:%g
% man boot@ %n
%w
-------------------------
| rebuild the boot tree |
-------------------------%n
First disable to old services:
%b-> as root:%g
# 66-disable -t boot tty12 All %n
After the execution of this command, you should get an empty boot tree.
Now enable the new version:
%b-> as root:%g
# 66-enable -C -F -t boot boot@system %n
%wNote:%n a service as type module is also an instantiated service. So you
can name it as you want at enable time e.g boot@my_system, boot@container
and so on...
You need now to configure the boot@system service. To edit its
configuration file use the 66-env program:
%b-> as root:%g
# 66-env -t boot boot@system %n
Your preferred editor should display the contain of the configuration
file. Changes what you need inside, saves it and exit.
Finally, to apply your changes you need to enable again the service:
%b-> as root:%g
# 66-enable -F -t boot boot@system %n
Your boot tree is ready for your next boot but a supplementary change is
needed concerning the tty@ service.
Previously, you had needed to enable the tty@ service outside the boot
tree in an another tree (generally root on Obarun). The tty@ service is
now a part of the boot@ service and the number of tty to start at boot
time is set with the %wTTY=%n variable at the boot@ service configuration
file.
So, to avoid conflict between the tty enabled with the boot tree and other
tty enabled outside this tree, you need to disable every tty@ service on
any tree. For example:
%b-> as root:%g
# 66-disable -t root tty@tty1 tty@tty2 %n
If you don't know where the tty@ service was enabled, use the %w66-intree%n
program to find the tree and how many was enabled.
%w
----------------------------------
| reframe the boot-user@ service |
----------------------------------%n
This only concern person previously using the %wboot-user@-66mod%n service.
And this following example the oblive term will be used as name of the
user and boot-user as name of the tree where the boot-user@-66mod was
enabled. Replace those term by the one used on your system.
First disable the old service:
%b-> as root:%g
# 66-disable -t boot-user All-oblive %n
Now enable the new version:
%b-> as root:%g
# 66-enable -C -F -t boot-user boot-user@oblive %n
You need now to configure the boot-user@oblive service. To edit its
configuration file use the 66-env program:
%b-> as root:%g
# 66-env -t boot-user boot-user@oblive %n
Your preferred editor should display the contain of the configuration
file. Changes what you need inside, saves it and exit.
Finally, to apply your changes you need to enable again the service:
%wNote:%n Depending of your system and your needs, you may want to use
the %wCONSOLE_TRACKER=%n variable. In this case, you also %rneed%n to
install the %wconsole-tracker@-66serv%n service and the corresponding
service to use for e.g. %wconsolekit-66serv%n.
The same thing need to be applied with the %wDISPLAY_MANAGER=%n variable.
The %wdisplay-manager@-66serv%n service %rneed%n to be installed on your
system and the corresponding service to use for e.g. %wsddm-66serv%n.
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 service again. Just live commented the corresponding variable.
%b-> as root:%g
# 66-enable -F -t boot-user boot-user@oblive %n
%w
-------------------------
| user supervision tree |
-------------------------%n
If you use the %wdbus-session@%n service you %rneed%n to enable it again
with the new version of %wdbus-66serv%n(0.2.0). So, be sure to have
installed it then enable again the service:
%b-> as user:%g
% 66-enable -C -F -t graphics dbus-session@oblive %n
%wReplace%n graphics by the name of the tree where dbus-session@ service
is already enabled and oblive by the name of your user. If you don't know
the name of the tree to use, employ the %w66-intree%n program to find it.
%y
--------
| Note |
-------------------------------------------------------------------------%n
Hope you found this bulletin usefull for you.
If you have any questions or trouble, please do not hesitate in making a
report.
Thanks for your attention.
eric@obarun.org
This text can be found at %b${HTML_PAGE}%n.
You can retrieve and read again this bulletin using the command below:
%g$ obnews.sh ${BULLETIN_NAME}%n"
......@@ -10,7 +10,7 @@ target=".current"
dir="/var/cache/obarun/news"
die() {
out_error "${1}"
oblog -f "${1}"
exit 111
}
......
#!/usr/bin/bash
##
## only use space for indentation
##
export PROG=""
export CLOCK_ENABLED=0
export COLOR_ENABLED=1
HTML_PAGE="http://web.obarun.org/"
MAXDATE=12/20/20
DATE=$(date +%D)
if [[ $DATE > $MAXDATE ]]; then
exit 0 ;
fi
BULLETIN_NAME=${0##*/}
BULLETIN_NAME=${BULLETIN_NAME%.*}
oblog -i "
From $DATE
%y
------------------------------------------------
| BOOT@-66serv, BOOT-USER@-66serv, DBUS-66serv |
-------------------------------------------------------------------------%n
%gThis document can be found at :%n
- %b${HTML_PAGE}%n
- using the command:
%g$ obnews.sh ${BULLETIN_NAME}%n
This new version comes with a few more features and tool. It needs
an %wupdate of all trees%n on your system as root and regular user.
%y
------------------
| HOW TO MIGRATE |
-------------------------------------------------------------------------%n
%w
--------------------------------------------
| subtitle |
--------------------------------------------%n
Simply run the following command on your system as root %wand%n
regular user:
%b-> as root:%g
# 66-update -d%n
%b-> as user:%g
% 66-update -d%n
The commands %wdo not change anything%n on your system. The
'-d' option ask at 66-update to make a dry-run and allow us to check if
the process go right.
If these commands terminate successfully, run again the 66-update removing
the '-d' options to process a real update.
Your system should be now operational and use the corresponding format of
the 66 version currently installed on your system. For further information,
please see the 66-update documentation page.
If the dry-run return you an error and you are not able to fix it,
please ask for help at the Obarun forum, by email at eric@obarun.org or
at the #Obarun chat on freenode and downgrade 66 to the previous version.
%y
--------
| Note |
-------------------------------------------------------------------------%n
Hope you found this bulletin usefull for you.
If you have any questions or trouble, please do not hesitate in making a report.
Thanks for your attention.
eric@obarun.org
This text can be found at %b${HTML_PAGE}%n.
You can retrieve and read again this bulletin using the command below:
%g$ obnews.sh ${BULLETIN_NAME}%n"
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment