Skip to content

Commit a2d9813

Browse files
thomaskoslowskiMattias Schlenker
authored andcommitted
KNW-2015, prepare edition renaming, pick-24
1 parent fbacd5e commit a2d9813

File tree

2 files changed

+24
-24
lines changed

2 files changed

+24
-24
lines changed

src/onprem/de/update.asciidoc

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ In folgendem Beispiel installieren wir ein Paket für Ubuntu 24.04 (Noble Numbat
178178

179179
[{shell}]
180180
----
181-
{c-root} apt install /tmp/check-mk-enterprise-{current}_0.noble_amd64.deb
181+
{c-root} apt install /tmp/{pkg-cee}-{current}_0.noble_amd64.deb
182182
----
183183

184184
*Hinweis:* Wenn Sie ein lokal vorliegendes Paket mit `apt install` installieren, müssen Sie den vollständigen Pfad zu der .deb-Datei angeben.
@@ -665,7 +665,7 @@ Am Monitoring-Kern und dem Benachrichtigungssystem gibt es keine Unterschiede zw
665665
Je nach Schwerpunkt des Einsatzes werden Sie den größeren Funktionsumfang oft erst beim Hinzufügen neuer Hosts nutzen.
666666
An einigen Stellen ist dennoch die Überprüfung der vorhandenen Einstellungen angeraten.
667667

668-
Eine vollständige Übersicht der zusätzlichen Funktionalität bietet der Artikel zu xref:cce#[{CE} (Self-hosted)].
668+
Eine vollständige Übersicht der zusätzlichen Funktionalität bietet der Artikel zu xref:cce#[{CE-onprem}].
669669

670670

671671
==== Check-Plugins für Cloud-Services
@@ -801,7 +801,7 @@ Als Folge werden Sie xref:wato_services#vanished[verschwundene Services] aufräu
801801

802802
Falls Sie unter {CE} das xref:grafana#[Grafana-Plugin] aus dem „Grafana Store“ genutzt haben, müssen Sie dieses durch ein aus dem Zip-Archiv installiertes ersetzen.
803803

804-
Eine Übersicht der Unterschiede zwischen {CE} und {SE} liefert der Artikel zu xref:cce#[{CE} (Self-hosted)].
804+
Eine Übersicht der Unterschiede zwischen {CE} und {SE} liefert der Artikel zu xref:cce#[{CE-onprem}].
805805

806806

807807
[#cee2cre]
@@ -862,18 +862,18 @@ So finden Sie heraus, welche Pakete installiert sind:
862862
[{shell}]
863863
----
864864
{c-root} dpkg -l | grep check-mk
865-
ii check-mk-enterprise-{current} 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
866-
ii check-mk-raw-{oldstable}p32 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
867-
ii check-mk-raw-{current} 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
865+
ii {pkg-cee}-{current} 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
866+
ii {pkg-cre}-{oldstable}p32 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
867+
ii {pkg-cre}-{current} 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
868868
----
869869

870870
Die Deinstallation geschieht mit `dpkg --purge`:
871871

872872
[{shell}]
873873
----
874-
{c-root} dpkg --purge check-mk-raw-{oldstable}p32
874+
{c-root} dpkg --purge {pkg-cre}-{oldstable}p32
875875
(Reading database ... 603038 files and directories currently installed.)
876-
Removing check-mk-raw-{oldstable}p32 (0.noble) ...
876+
Removing {pkg-cre}-{oldstable}p32 (0.noble) ...
877877
...
878878
----
879879

@@ -885,16 +885,16 @@ So finden Sie bei RPM-basierten Systemen heraus, welche {CMK}-Pakete installiert
885885
[{shell}]
886886
----
887887
{c-root} rpm -qa | grep check-mk
888-
check-mk-enterprise-{current}-el9-38.x86_64.rpm
889-
check-mk-raw-{current}-el9-38.x86_64.rpm
890-
check-mk-raw-{oldstable}p32-el9-38.x86_64.rpm
888+
{pkg-cee}-{current}-el9-38.x86_64.rpm
889+
{pkg-cre}-{current}-el9-38.x86_64.rpm
890+
{pkg-cre}-{oldstable}p32-el9-38.x86_64.rpm
891891
----
892892

893893
Das Löschen geschieht mit `rpm -e`:
894894

895895
[{shell}]
896896
----
897-
{c-root} rpm -e check-mk-raw-{oldstable}p32-el9-38.x86_64.rpm
897+
{c-root} rpm -e {pkg-cre}-{oldstable}p32-el9-38.x86_64.rpm
898898
----
899899

900900

src/onprem/en/update.asciidoc

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ In the following example we are installing a package for Ubuntu 24.04 (Noble Num
178178

179179
[{shell}]
180180
----
181-
{c-root} apt install /tmp/check-mk-enterprise-{current}_0.noble_amd64.deb
181+
{c-root} apt install /tmp/{pkg-cee}-{current}_0.noble_amd64.deb
182182
----
183183

184184
*Note:* When installing a local package via `apt install`, you have to state the pull path to the .deb file.
@@ -666,7 +666,7 @@ When it comes to the monitoring core and the notification system, there are no d
666666
Depending on the focus of the deployment, you will often use the larger feature set only when adding new hosts.
667667
In some places, however, it is still advisable to review the existing settings.
668668

669-
For a complete overview of the additional functionality, see the article on xref:cce#[{CE} (Self-hosted)].
669+
For a complete overview of the additional functionality, see the article on xref:cce#[{CE-onprem}].
670670

671671

672672
==== Check plug-ins for cloud services
@@ -803,7 +803,7 @@ As a result, you will need to clean up xref:wato_services#vanished[vanished serv
803803

804804
If under {CE} you used the xref:grafana#[Grafana plug-in] from the 'Grafana Store', you will need to replace it with one installed from the zip archive.
805805

806-
An overview of the differences between {CE} and {SE} is provided by the article on xref:cce#[{CE} (Self-hosted)].
806+
An overview of the differences between {CE} and {SE} is provided by the article on xref:cce#[{CE-onprem}].
807807

808808

809809
[#cee2cre]
@@ -864,18 +864,18 @@ Use the below to identify which packets are installed:
864864
[{shell}]
865865
----
866866
{c-root} dpkg -l | grep check-mk
867-
ii check-mk-enterprise-{current} 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
868-
ii check-mk-raw-{oldstable}p32 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
869-
ii check-mk-raw-{current} 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
867+
ii {pkg-cee}-{current} 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
868+
ii {pkg-cre}-{oldstable}p32 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
869+
ii {pkg-cre}-{current} 0.noble amd64 Checkmk - Best-in-class infrastructure & application monitoring
870870
----
871871

872872
The uninstallation is performed with `dpkg --purge`:
873873

874874
[{shell}]
875875
----
876-
{c-root} dpkg --purge check-mk-raw-{oldstable}p32
876+
{c-root} dpkg --purge {pkg-cre}-{oldstable}p32
877877
(Reading database ... 603038 files and directories currently installed.)
878-
Removing check-mk-raw-{oldstable}p32 (0.noble) ...
878+
Removing {pkg-cre}-{oldstable}p32 (0.noble) ...
879879
...
880880
----
881881

@@ -887,16 +887,16 @@ Here is how to identify which {CMK} packages are being used in RPM-based systems
887887
[{shell}]
888888
----
889889
{c-root} rpm -qa | grep check-mk
890-
check-mk-enterprise-{current}-el9-38.x86_64.rpm
891-
check-mk-raw-{current}-el9-38.x86_64.rpm
892-
check-mk-raw-{oldstable}p32-el9-38.x86_64.rpm
890+
{pkg-cee}-{current}-el9-38.x86_64.rpm
891+
{pkg-cre}-{current}-el9-38.x86_64.rpm
892+
{pkg-cre}-{oldstable}p32-el9-38.x86_64.rpm
893893
----
894894

895895
The deletion is performed with `rpm -e`:
896896

897897
[{shell}]
898898
----
899-
{c-root} rpm -e check-mk-raw-{oldstable}p32-el9-38.x86_64.rpm
899+
{c-root} rpm -e {pkg-cre}-{oldstable}p32-el9-38.x86_64.rpm
900900
----
901901

902902

0 commit comments

Comments
 (0)