681
edits
Changes
Jump to navigation
Jump to search
Line 1,281:
Line 1,281: − + + + + + + + Line 1,302:
Line 1,308: + + + + + + + + + + + + + + Line 1,311:
Line 1,331: − + − + Line 1,323:
Line 1,343: − + + + + + + Line 1,339:
Line 1,364: − +
→Bare install test
et voilà, you have a non functional SME 11 over Rocky 8 minimal.
et voilà, you have a non functional SME 11 over Rocky 8 minimal.
<nowiki>##</nowiki> this needs safer to be done directly on tty, not via ssh:
Also remember that the legacy server manager (SM1) is not installed by the above, so, perhaps:
dnf install e-smith-manager
If you then find you get an SM1 login but the login just celars the fields and does not login, then you can fix this with:<syntaxhighlight lang="shell">
expand-template /etc/e-smith/web/common//cgi-bin/AuthTKT.cfg
</syntaxhighlight>'''<nowiki>##</nowiki> This is safer to be done directly on tty, not via ssh:'''
lget ride of Messup-Network-Manager NOW!
lget ride of Messup-Network-Manager NOW!
then try to configure using console
then try to configure using console
/sbin/e-smith/console
/sbin/e-smith/console
To get better information from Server Manager 2 (this replaces the barfing dinosaur):<syntaxhighlight lang="shell">
mkdir -p /etc/e-smith/templates-custom/usr/share/smanager/conf/srvmngr.conf/
cat <<EOF > /etc/e-smith/templates-custom/usr/share/smanager/conf/srvmngr.conf/30Other
modules_dir => 'lib/SrvMngr/Controller',
webapp => 'smanager',
mode => 'development',
debug => 1,
\}
EOF
expand-template /usr/share/smanager/conf/srvmngr.conf
signal-event smanager-refresh
</syntaxhighlight>
then to be sure to get sshd back
then to be sure to get sshd back
/sbin/e-smith/db configuration setprop sshd status enabled PermitRootLogin yes access public
/sbin/e-smith/db configuration setprop sshd status enabled PermitRootLogin yes access public
then you can
then you can
signal-event post-upgrade;
signal-event post-upgrade;
signal-event-reboot;
signal-event reboot;
or maybe
or maybe
signal-event bootstrap-console-save;
signal-event bootstrap-console-save;
signal-event-reboot
signal-event-reboot
<nowiki>##</nowiki> end of the part better on tty than on sshd
'''<nowiki>##</nowiki> end of the part better on tty than on sshd'''
you can also tidy a little
you can also tidy a little
you might need to disable sme* repos from there as they are still yet to be created on mirrors. so to help you follow updates you should do
you might need avoid using sme* repo except for koji builsdsystem one as long as they are not populated to do so:
<syntaxhighlight lang="shell">
mkdir -p /etc/e-smith/templates-custom/etc/dnf/dnf.conf/
echo "#rem custom"> /etc/e-smith/templates-custom/etc/dnf/dnf.conf/20main_reposdir
expand-template /etc/dnf/dnf.conf
</syntaxhighlight>also you might want to plan ahead and put the koji repo for when you will have deleted the custom template.
vim /etc/yum.smerepos.d/koji.repo
vim /etc/yum.smerepos.d/koji.repo
and paste:
and paste:
from there if you are lucky something went up and you can try to test , report as bug or event create a patch
from there if you are lucky it worked and you can try to test , report as bug or even create a patch
== Notes ==
== Notes ==