Ein neuer Name für ein bekanntes Projekt: Mistelberger Global Headquarter (MGH)

karlmistelberger · January 18, 2026, 5:51am

Die AI-Suche nach infamous host erlangen site:forums.opensuse.org ergibt:

In den openSUSE-Foren bezieht sich die Bezeichnung

“infamous host erlangen” auf den Haupt-Desktop-Rechner des langjährigen Community-Mitglieds karlmistelberger.

Hier sind die Details zu diesem bekannten System:

Ursprung des Namens: Der Begriff „infamous host erlangen“ (berüchtigter Host Erlangen) wurde ursprünglich von der Forenadministration geprägt.
Systemphilosophie: Das System dient als Projekt, um nahezu alle Computer-Ärgernisse zu beseitigen, denen der Autor seit 1978 begegnet ist. Es basiert auf dem Prinzip von „Rolling Hardware“ und „Rolling Software“.
Hardware-Historie:
- Das ursprüngliche System wurde im Februar 2014 mit Komponenten wie einem Intel i3-4130, einem ASRock H81M-DGS Mainboard und einer 60 GB SSD gebaut.
- Im Juli 2020 erfolgte ein Upgrade auf einen AMD Ryzen 5 3400G.
- Anfang 2026 ist der Host weiterhin in Betrieb; Berichte aus dem Jahr 2025 bestätigen die Nutzung aktueller Audio-Hardware (AMD Renoir/Family 17h HD Audio).
Software-Konfiguration:
- Es läuft unter openSUSE Tumbleweed.
- Das System erhält tägliche, automatisierte Updates über den Befehl zypper dist-upgrade (zypper dup), meist ohne manuelle Eingriffe.
- Es nutzt das Btrfs-Dateisystem, wobei Berichte vom Juli 2025 eine fehlerfreie Journal-Historie von über einem Jahr belegen.
Verwendung im Forum: Der Host wird in zahlreichen Diskussionen als Referenz für ein stabiles, rollierendes System angeführt, um zu zeigen, dass auch komplexe Konfigurationen (wie automatisierte Mail-Benachrichtigungen oder umfangreiche Paket-Installationen) langfristig ohne Neuinstallation funktionieren können.

Der von der Forenadministration geprägte Begriff führte zu zahlreichen Problemen.

Sauerland · January 18, 2026, 8:27am

Was soll so etwas?

Auch wenn es in Gequatsche ist?

susejunky · January 18, 2026, 10:21am

Vielleicht ein Hinweis darauf, dass @karlmistelberger die deutsche Referenzinstallation für openSUSE Tumbleweed betreibt ???

hui · January 18, 2026, 10:33am

Das wäre dann auch eine Erklärung für den niedrigen Marktanteil

karlmistelberger · January 20, 2026, 8:41am

susejunky · January 20, 2026, 12:23pm

Leider besitze ich keine Cessna 172.

Aber selbst wenn ich eine besitzen würde:

Die maximale Schneehöhe hier in meinem Garten betrug in diesen Jahr (2026) max. 2" … also 1,25 * 2" … keine Bruchgefahr

karlmistelberger · January 21, 2026, 7:55am

Der Wechsel des Internet Providers von M-net zu 1&1 war ziemlich unproblematisch. Allerdings gibt es bei 1&1 ein Problem, das bei M-net nie aufgetreten war.

Jan 20 23:02:41 erlangen sshd-session[119406]: error: Could not get shadow information for NOUSER
erlangen:~ # journalctl -q -u sshd -g USER|wc
  13928  181064 1359829

In einer knappen Woche gab es über Dreizehntausend Einbruchsversuche.

karlmistelberger · January 25, 2026, 12:39pm

Juan Browne hat mit 16 damit angefangen. Geld hatte er auch keines. Da hat er bei seinen Eltern ein Darlehen aufgenommen.

karlmistelberger · February 2, 2026, 9:12am

Aus dem Schlafzimmer

karl@erlangen:/srv/www/htdocs> systemctl list-jobs 
JOB   UNIT                                     TYPE  STATE  
22466 polkit-agent-helper@4-40870-1001.service start running
32694 dup.service                              start running

2 jobs listed.
karl@erlangen:/srv/www/htdocs> w
 08:02:35 up 3 days, 16:21,  4 users,  load average: 2,69, 1,01, 0,42
USER     TTY      VON              LOGIN@   UNTÄT. JCPU   PCPU  WAS
root     pts/0    -                 So12   19:33 m  0.24 s  0.12 s -bash
karl     tty2     -                 Do15    3Tage  0.05 s  0.05 s /usr/bin/startplasma-wayland
charlema tty8     -                 Do21    3Tage  0.32 s  0.32 s /usr/bin/startplasma-wayland
root     tty4     -                 Do15    3Tage  0.13 s  0.13 s -bash
karl@erlangen:/srv/www/htdocs> w

Timeouts

karl@erlangen:/srv/www/htdocs> journalctl --boot cc5655a015d04a2f9babe6ab09cb55eb --identifier systemd --priority err
Jan 29 15:41:13 erlangen systemd[1165]: Failed to start Start Myrlyn.
Jan 30 07:27:27 erlangen systemd[1]: Timed out waiting for device /dev/disk/by-uuid/47e6d9ee-e910-4ea4-8c8f-7ac75f49a4d3.
Jan 30 07:27:28 erlangen systemd[1]: Timed out waiting for device /dev/disk/by-uuid/78383e24-1ed7-45ad-9a6b-65b8b98b93c2.
Jan 30 07:27:58 erlangen systemd[1]: Timed out waiting for device /dev/disk/by-uuid/2260f160-cc05-47cc-9893-cc32c050177d.
Jan 31 00:49:56 erlangen systemd[1]: Timed out waiting for device /dev/disk/by-uuid/78383e24-1ed7-45ad-9a6b-65b8b98b93c2.
Jan 31 00:50:26 erlangen systemd[1]: Timed out waiting for device ST8000VN004-2M2101 Seagate.
Feb 01 00:31:57 erlangen systemd[1]: Timed out waiting for device /dev/disk/by-uuid/78383e24-1ed7-45ad-9a6b-65b8b98b93c2.
Feb 01 00:32:27 erlangen systemd[1]: Timed out waiting for device ST8000VN004-2M2101 Seagate.
Feb 02 08:01:18 erlangen systemd[1]: Timed out waiting for device /dev/disk/by-uuid/78383e24-1ed7-45ad-9a6b-65b8b98b93c2.
Feb 02 08:01:49 erlangen systemd[1]: Timed out waiting for device ST8000VN004-2M2101 Seagate.
karl@erlangen:/srv/www/htdocs>

Timers

karl@erlangen:/srv/www/htdocs> systemctl list-timers 
NEXT                                  LEFT LAST                             PASSED UNIT                            ACTIVATES                        
Mon 2026-02-02 09:45:48 CET          41min Mon 2026-02-02 08:45:48 CET   18min ago snapper-cleanup.timer           snapper-cleanup.service
Mon 2026-02-02 19:48:38 CET            10h Sun 2026-02-01 11:37:09 CET     13h ago systemd-tmpfiles-clean.timer    systemd-tmpfiles-clean.service
Tue 2026-02-03 00:00:00 CET            14h Mon 2026-02-02 08:01:14 CET 1h 3min ago btrbk.timer                     btrbk.service
Tue 2026-02-03 00:00:00 CET            14h Mon 2026-02-02 08:01:14 CET 1h 3min ago dup.timer                       dup.service
Tue 2026-02-03 00:03:24 CET            14h Mon 2026-02-02 08:01:14 CET 1h 3min ago backup-sysconfig.timer          backup-sysconfig.service
Tue 2026-02-03 00:07:00 CET            15h Mon 2026-02-02 08:01:14 CET 1h 3min ago logrotate.timer                 logrotate.service
Tue 2026-02-03 00:21:14 CET            15h Mon 2026-02-02 08:01:14 CET 1h 3min ago check-battery.timer             check-battery.service
Tue 2026-02-03 00:40:17 CET            15h Mon 2026-02-02 08:01:14 CET 1h 3min ago plocate-updatedb.timer          plocate-updatedb.service
Tue 2026-02-03 01:26:13 CET            16h Mon 2026-02-02 08:01:14 CET 1h 3min ago backup-rpmdb.timer              backup-rpmdb.service
Tue 2026-02-03 08:55:03 CET            23h Mon 2026-02-02 08:01:14 CET 1h 3min ago man-db.timer                    man-db.service
Mon 2026-02-09 00:00:00 CET         6 days Mon 2026-02-02 08:01:14 CET 1h 3min ago btrfs-balance.timer             btrfs-balance.service
Mon 2026-02-09 00:00:00 CET         6 days Mon 2026-02-02 08:01:14 CET 1h 3min ago btrfs-scrub.timer               btrfs-scrub.service
Mon 2026-02-09 00:00:00 CET         6 days Mon 2026-02-02 08:01:14 CET 1h 3min ago btrfs-trim.timer                btrfs-trim.service
Sun 2026-03-01 00:12:31 CET 3 weeks 5 days Sun 2026-02-01 00:01:10 CET     24h ago wtmpdb-rotate.timer             wtmpdb-rotate.service
-                                        - -                                     - openSUSE-build-key-import.timer openSUSE-build-key-import.service

15 timers listed.
Pass --all to see loaded but inactive timers, too.
karl@erlangen:/srv/www/htdocs>

Er schläft immer wieder einmal

karl@erlangen:/srv/www/htdocs> journalctl --boot cc5655a015d04a2f9babe6ab09cb55eb --unit systemd-suspend.service --identifier systemd
Jan 29 23:52:10 erlangen systemd[1]: Starting System Suspend...
Jan 30 07:27:21 erlangen systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 30 07:27:21 erlangen systemd[1]: Finished System Suspend.
Jan 31 08:27:50 erlangen systemd[1]: Starting System Suspend...
Jan 31 20:33:34 erlangen systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 31 20:33:34 erlangen systemd[1]: Finished System Suspend.
Feb 01 23:49:42 erlangen systemd[1]: Starting System Suspend...
Feb 02 08:01:14 erlangen systemd[1]: systemd-suspend.service: Deactivated successfully.
Feb 02 08:01:14 erlangen systemd[1]: Finished System Suspend.
karl@erlangen:/srv/www/htdocs>

Alle Services laufen wie sie sollen

erlangen:~ # systemctl list-units --type service --state running 
  UNIT                       LOAD   ACTIVE SUB     DESCRIPTION                                   
  apache2.service            loaded active running The Apache Webserver
  avahi-daemon.service       loaded active running Avahi mDNS/DNS-SD Stack
  bluetooth.service          loaded active running Bluetooth service
  chronyd.service            loaded active running NTP client/server
  cron.service               loaded active running Command Scheduler
  cups.service               loaded active running CUPS Scheduler
  dbus-broker.service        loaded active running D-Bus System Message Bus
  fetchmail.service          loaded active running A remote-mail retrieval utility
  getty@tty3.service         loaded active running Getty on tty3
  getty@tty4.service         loaded active running Getty on tty4
  getty@tty5.service         loaded active running Getty on tty5
  getty@tty6.service         loaded active running Getty on tty6
  irqbalance.service         loaded active running irqbalance daemon
  minidlna.service           loaded active running MiniDLNA is a DLNA/UPnP-AV server software
  NetworkManager.service     loaded active running Network Manager
  polkit.service             loaded active running Authorization Manager
  postfix.service            loaded active running Postfix Mail Transport Agent
  rpcbind.service            loaded active running RPC Bind
  rtkit-daemon.service       loaded active running RealtimeKit Scheduling Policy Service
  sddm.service               loaded active running Simple Desktop Display Manager
  sshd.service               loaded active running OpenSSH Daemon
  switcheroo-control.service loaded active running Switcheroo Control Proxy service
  systemd-journald.service   loaded active running Journal Service
  systemd-logind.service     loaded active running User Login Management
  systemd-udevd.service      loaded active running Rule-based Manager for Device Events and Files
  udisks2.service            loaded active running Disk Manager
  upower.service             loaded active running Daemon for power management
  user@0.service             loaded active running User Manager for UID 0
  user@1000.service          loaded active running User Manager for UID 1000
  user@1001.service          loaded active running User Manager for UID 1001
  wpa_supplicant.service     loaded active running WPA Supplicant daemon

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.

31 loaded units listed.
erlangen:~ #

Die schon gelaufen sind

erlangen:~ # systemctl list-units --type service --state exited
  UNIT                                     LOAD   ACTIVE SUB    DESCRIPTION                                  
  alsa-restore.service                     loaded active exited Save/Restore Sound Card State
  blk-availability.service                 loaded active exited Availability of block devices
  dracut-shutdown.service                  loaded active exited Restore /run/initramfs on shutdown
  iscsi.service                            loaded active exited Login and scanning of iSCSI devices
  kbdsettings.service                      loaded active exited Apply settings from /etc/sysconfig/keyboard
  kernel-sysctl.service                    loaded active exited Apply Kernel Variables for 6.18.7-1-default
  kmod-static-nodes.service                loaded active exited Create List of Static Device Nodes
  lm_sensors.service                       loaded active exited Initialize hardware monitoring sensors
  soft-reboot-cleanup.service              loaded active exited Cleanup system data after soft-reboot
  systemd-journal-flush.service            loaded active exited Flush Journal to Persistent Storage
  systemd-modules-load.service             loaded active exited Load Kernel Modules
  systemd-random-seed.service              loaded active exited Load/Save OS Random Seed
  systemd-remount-fs.service               loaded active exited Remount Root and Kernel File Systems
  systemd-sysctl.service                   loaded active exited Apply Kernel Variables
  systemd-tmpfiles-setup-dev-early.service loaded active exited Create Static Device Nodes in /dev gracefully
  systemd-tmpfiles-setup-dev.service       loaded active exited Create Static Device Nodes in /dev
  systemd-tmpfiles-setup.service           loaded active exited Create System Files and Directories
  systemd-udev-load-credentials.service    loaded active exited Load udev Rules from Credentials
  systemd-udev-trigger.service             loaded active exited Coldplug All udev Devices
  systemd-user-sessions.service            loaded active exited Permit User Sessions
  systemd-vconsole-setup.service           loaded active exited Virtual Console Setup
  user-runtime-dir@0.service               loaded active exited User Runtime Directory /run/user/0
  user-runtime-dir@1000.service            loaded active exited User Runtime Directory /run/user/1000
  user-runtime-dir@1001.service            loaded active exited User Runtime Directory /run/user/1001
  wtmpdb-update-boot.service               loaded active exited Write boot and shutdown times into wtmpdb

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.

25 loaded units listed.
erlangen:~ #

Offenbar haben es alle geschafft

erlangen:~ # systemctl list-units --type service --state failed
  UNIT LOAD ACTIVE SUB DESCRIPTION

0 loaded units listed.
erlangen:~ #

Probleme gab es dennoch

karl@erlangen:/srv/www/htdocs> journalctl --boot cc5655a015d04a2f9babe6ab09cb55eb --grep '\*ERROR\*'
Jan 29 15:54:27 erlangen kernel: amdgpu 0000:30:00.0: [drm] *ERROR* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Jan 29 15:54:27 erlangen kernel: amdgpu 0000:30:00.0: [drm] *ERROR* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Jan 29 15:54:27 erlangen kernel: amdgpu 0000:30:00.0: [drm] *ERROR* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed
Jan 29 15:54:27 erlangen kernel: amdgpu 0000:30:00.0: [drm] *ERROR* dpcd_set_link_settings:1122: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Jan 29 15:54:27 erlangen kernel: amdgpu 0000:30:00.0: [drm] *ERROR* dpcd_set_link_settings:1127: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Jan 29 15:54:27 erlangen kernel: amdgpu 0000:30:00.0: [drm] *ERROR* dpcd_set_link_settings:1155: core_link_write_dpcd (DP_LINK_BW_SET) failed
karl@erlangen:/srv/www/htdocs>

Da muss ich nachschauen.

karlmistelberger · February 4, 2026, 6:12pm

Wer sind denn diese Nasenbohrer? Die kenne ich gar nicht:

erlangen:~ # journalctl -b -u sshd --grep sol|tail
Feb 04 16:12:56 erlangen sshd-session[126409]: Invalid user sol from 92.118.39.92 port 37540
Feb 04 16:12:56 erlangen sshd-session[126409]: Connection closed by invalid user sol 92.118.39.92 port 37540 [preauth]
Feb 04 16:15:12 erlangen sshd-session[126486]: Invalid user solana from 92.118.39.92 port 52038
Feb 04 16:15:12 erlangen sshd-session[126486]: Connection closed by invalid user solana 92.118.39.92 port 52038 [preauth]
Feb 04 16:23:57 erlangen sshd-session[126798]: Invalid user solana from 92.118.39.92 port 53494
Feb 04 16:23:58 erlangen sshd-session[126798]: Connection closed by invalid user solana 92.118.39.92 port 53494 [preauth]
Feb 04 16:52:52 erlangen sshd-session[130490]: Invalid user sol from 92.118.39.92 port 44204
Feb 04 16:52:52 erlangen sshd-session[130490]: Connection closed by invalid user sol 92.118.39.92 port 44204 [preauth]
Feb 04 18:38:03 erlangen sshd-session[140329]: Invalid user solana from 80.94.92.168 port 52260
Feb 04 18:38:03 erlangen sshd-session[140329]: Connection closed by invalid user solana 80.94.92.168 port 52260 [preauth]
erlangen:~ #

karlmistelberger · February 5, 2026, 7:51am

erlangen:~ # systemctl status|head -22
● erlangen
    State: running
    Units: 688 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 0 units
    Since: Mon 2026-02-02 13:34:50 CET; 2 days ago
  systemd: 257.9+suse.23.gc139debf2c
  Tainted: unmerged-bin
   CGroup: /
           ├─init.scope
           │ └─1 /usr/lib/systemd/systemd --switched-root --system --deserialize=51
           ├─system.slice
           │ ├─NetworkManager.service
           │ │ └─1113 /usr/sbin/NetworkManager --no-daemon
           │ ├─apache2.service
           │ │ ├─174668 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -C "PidFile /run/httpd.pid" -C "Include /etc/apache2/sysconfig.d//loadmodule.conf" -C "Include /etc/apache2/sysconfig.d//global.conf" -f /etc/apache2/httpd.conf -c "Include /etc/apache2/sysconfig.d//include.conf" -DSYSTEMD -DFOREGROUND -k start
           │ │ ├─174672 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -C "PidFile /run/httpd.pid" -C "Include /etc/apache2/sysconfig.d//loadmodule.conf" -C "Include /etc/apache2/sysconfig.d//global.conf" -f /etc/apache2/httpd.conf -c "Include /etc/apache2/sysconfig.d//include.conf" -DSYSTEMD -DFOREGROUND -k start
           │ │ ├─174673 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -C "PidFile /run/httpd.pid" -C "Include /etc/apache2/sysconfig.d//loadmodule.conf" -C "Include /etc/apache2/sysconfig.d//global.conf" -f /etc/apache2/httpd.conf -c "Include /etc/apache2/sysconfig.d//include.conf" -DSYSTEMD -DFOREGROUND -k start
           │ │ ├─174675 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -C "PidFile /run/httpd.pid" -C "Include /etc/apache2/sysconfig.d//loadmodule.conf" -C "Include /etc/apache2/sysconfig.d//global.conf" -f /etc/apache2/httpd.conf -c "Include /etc/apache2/sysconfig.d//include.conf" -DSYSTEMD -DFOREGROUND -k start
           │ │ ├─174676 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -C "PidFile /run/httpd.pid" -C "Include /etc/apache2/sysconfig.d//loadmodule.conf" -C "Include /etc/apache2/sysconfig.d//global.conf" -f /etc/apache2/httpd.conf -c "Include /etc/apache2/sysconfig.d//include.conf" -DSYSTEMD -DFOREGROUND -k start
           │ │ ├─174677 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -C "PidFile /run/httpd.pid" -C "Include /etc/apache2/sysconfig.d//loadmodule.conf" -C "Include /etc/apache2/sysconfig.d//global.conf" -f /etc/apache2/httpd.conf -c "Include /etc/apache2/sysconfig.d//include.conf" -DSYSTEMD -DFOREGROUND -k start
           │ │ └─218661 /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -C "PidFile /run/httpd.pid" -C "Include /etc/apache2/sysconfig.d//loadmodule.conf" -C "Include /etc/apache2/sysconfig.d//global.conf" -f /etc/apache2/httpd.conf -c "Include /etc/apache2/sysconfig.d//include.conf" -DSYSTEMD -DFOREGROUND -k start
erlangen:~ #