Stop alteratord in /mnt/destination Stopping alteratord service: [ tput: unknown terminfo capability '2' DONE ] [ DONE ] Stop alteratord.service Stopping 'alteratord.service', but its triggering units are still active: alteratord.socket [ DONE ] Stop alteratord.socket [ DONE ] cp: not replacing '/usr/share/install2/postinstall.d/90-firsttime.sh' cp: not replacing '/usr/share/install2/postinstall.d/10-increase-raid-limit.sh' cp: not replacing '/usr/share/install2/postinstall.d/01-wizard-log.sh' cp: not replacing '/usr/share/install2/postinstall.d/30-gen-host-keys.sh' cp: not replacing '/usr/share/install2/postinstall.d/95-dconf-update' cp: not replacing '/usr/share/install2/postinstall.d/90-clean.sh' cp: not replacing '/usr/share/install2/postinstall.d/40-lightdm-config.sh' cp: not replacing '/usr/share/install2/postinstall.d/00-remove-installer-pkgs.sh' cp: not replacing '/usr/share/install2/postinstall.d/90-runlevel5.sh' cp: not replacing '/usr/share/install2/postinstall.d/66-setup-mdmon.sh' cp: not replacing '/usr/share/install2/postinstall.d/45-setup-dhcp.sh' cp: not replacing '/usr/share/install2/postinstall.d/65-setup-services.sh' Running postinstall script [00-remove-installer-pkgs.sh] alterator-kopidel-1.1.2-alt1.noarch error: Failed dependencies: installer-common-functions = 1.16.38-alt1:p11+425359.200.4.1 is needed by (installed) installer-common-base-stage2-1.16.38-alt1.x86_64 /usr/sbin/install2-init-functions is needed by (installed) installer-alterator-fs-1.0.1-alt1.noarch /usr/sbin/install2-init-functions is needed by (installed) alterator-kopidel-1.1.2-alt1.noarch /usr/sbin/install2-sh-functions is needed by (installed) alterator-preinstall-0.9.2-alt1.noarch [FAILED] Running postinstall script [01-remove-installer-desktop-pkgs.sh] error: Failed dependencies: alterator-wizardface is needed by (installed) installer-common-base-stage2-1.16.38-alt1.x86_64 alterator-wizardface is needed by (installed) alterator-setup-base-0.5.5-alt1.noarch alterator-luks is needed by (installed) installer-distro-alt-education-stage3-11.1-alt6.noarch [FAILED] Running postinstall script [01-wizard-log.sh] [ DONE ] Running postinstall script [05-setup-iptables] [ DONE ] Running postinstall script [05-virtualbox] [ DONE ] Running postinstall script [10-increase-raid-limit.sh] [ DONE ] Running postinstall script [20-alterator-menu] [ DONE ] Running postinstall script [30-gen-host-keys.sh] [ DONE ] Running postinstall script [30-xdg-user-dirs.sh] [ DONE ] Running postinstall script [40-lightdm-config.sh] [ DONE ] Running postinstall script [40-oem-step.sh] [ DONE ] Running postinstall script [45-setup-dhcp.sh] [ DONE ] Running postinstall script [60-no-bell.sh] [ DONE ] Running postinstall script [60-setup-journald] [ DONE ] Running postinstall script [65-setup-services.sh] Synchronizing state of cups.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable cups Synchronizing state of cups-browsed.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable cups-browsed Created symlink '/etc/systemd/system/multi-user.target.wants/cups-browsed.service' → '/usr/lib/systemd/system/cups-browsed.service'. Synchronizing state of avahi-daemon.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable avahi-daemon Synchronizing state of NetworkManager.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable NetworkManager Created symlink '/etc/systemd/system/dbus-org.freedesktop.ModemManager1.service' → '/usr/lib/systemd/system/ModemManager.service'. Created symlink '/etc/systemd/system/multi-user.target.wants/ModemManager.service' → '/usr/lib/systemd/system/ModemManager.service'. Synchronizing state of nmb.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable nmb Created symlink '/etc/systemd/system/multi-user.target.wants/nmb.service' → '/usr/lib/systemd/system/nmb.service'. Synchronizing state of smb.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable smb Created symlink '/etc/systemd/system/multi-user.target.wants/smb.service' → '/usr/lib/systemd/system/smb.service'. Synchronizing state of cpufreq-simple.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable cpufreq-simple Created symlink '/etc/systemd/system/multi-user.target.wants/cpufreq-simple.service' → '/usr/lib/systemd/system/cpufreq-simple.service'. Created symlink '/etc/systemd/system/sleep.target.wants/cpufreq-simple-wake.service' → '/usr/lib/systemd/system/cpufreq-simple-wake.service'. Created symlink '/etc/systemd/system/sockets.target.wants/alteratord.socket' → '/usr/lib/systemd/system/alteratord.socket'. Synchronizing state of ahttpd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable ahttpd Created symlink '/etc/systemd/system/multi-user.target.wants/ahttpd.service' → '/usr/lib/systemd/system/ahttpd.service'. Synchronizing state of bluetoothd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable bluetoothd Synchronizing state of crond.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable crond Created symlink '/etc/systemd/system/multi-user.target.wants/crond.service' → '/usr/lib/systemd/system/crond.service'. Synchronizing state of anacron.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable anacron Created symlink '/etc/systemd/system/multi-user.target.wants/anacron.service' → '/usr/lib/systemd/system/anacron.service'. Synchronizing state of lvm2-monitor.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable lvm2-monitor Created symlink '/etc/systemd/system/sysinit.target.wants/lvm2-monitor.service' → '/usr/lib/systemd/system/lvm2-monitor.service'. Synchronizing state of network.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable network Created symlink '/etc/systemd/system/network-online.target.wants/network.service' → '/usr/lib/systemd/system/network.service'. Created symlink '/etc/systemd/system/multi-user.target.wants/network.service' → '/usr/lib/systemd/system/network.service'. Created symlink '/etc/systemd/system/multi-user.target.wants/chronyd.service' → '/usr/lib/systemd/system/chronyd.service'. Synchronizing state of x11presetdrv.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable x11presetdrv Synchronizing state of sshd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable sshd Created symlink '/etc/systemd/system/multi-user.target.wants/sshd.service' → '/usr/lib/systemd/system/sshd.service'. Failed to enable unit: Unit acpid.service does not exist Synchronizing state of chronyd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable chronyd Created symlink '/etc/systemd/system/timers.target.wants/fstrim.timer' → '/usr/lib/systemd/system/fstrim.timer'. Failed to enable unit: Unit livecd-auto-hostname.service does not exist Failed to enable unit: Unit livecd-backlight-max.service does not exist Failed to enable unit: Unit livecd-evms.service does not exist Failed to enable unit: Unit livecd-fstab.service does not exist Failed to enable unit: Unit livecd-install-wmaker.service does not exist Failed to enable unit: Unit livecd-net-eth.service does not exist Failed to enable unit: Unit livecd-save-nfs.service does not exist Failed to enable unit: Unit livecd-setauth.service does not exist Failed to enable unit: Unit livecd-setlocale.service does not exist Failed to enable unit: Unit livecd-timezone.service does not exist Failed to enable unit: Unit livecd-user.service does not exist Created symlink '/etc/systemd/system/systemd-hibernate.service.wants/nvidia-hibernate.service' → '/usr/lib/systemd/system/nvidia-hibernate.service'. Failed to enable unit: Unit nvidia-powerd.service does not exist Created symlink '/etc/systemd/system/systemd-suspend.service.wants/nvidia-resume.service' → '/usr/lib/systemd/system/nvidia-resume.service'. Created symlink '/etc/systemd/system/systemd-hibernate.service.wants/nvidia-resume.service' → '/usr/lib/systemd/system/nvidia-resume.service'. Created symlink '/etc/systemd/system/systemd-suspend-then-hibernate.service.wants/nvidia-resume.service' → '/usr/lib/systemd/system/nvidia-resume.service'. Created symlink '/etc/systemd/system/systemd-suspend.service.wants/nvidia-suspend.service' → '/usr/lib/systemd/system/nvidia-suspend.service'. Created symlink '/etc/systemd/system/systemd-suspend-then-hibernate.service.wants/nvidia-suspend-then-hibernate.service' → '/usr/lib/systemd/system/nvidia-suspend-then-hibernate.service'. Synchronizing state of plymouth.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable plymouth The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Created symlink '/etc/systemd/system/graphical.target.wants/power-profiles-daemon.service' → '/usr/lib/systemd/system/power-profiles-daemon.service'. The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of rpcbind.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable rpcbind Created symlink '/etc/systemd/system/multi-user.target.wants/rpcbind.service' → '/usr/lib/systemd/system/rpcbind.service'. Created symlink '/etc/systemd/system/graphical.target.wants/switcheroo-control.service' → '/usr/lib/systemd/system/switcheroo-control.service'. Failed to disable unit: Unit bridge.service does not exist Failed to disable unit: Unit bridge.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit ethtool.service does not exist Failed to disable unit: Unit ethtool.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of iptables.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable iptables Synchronizing state of lm_sensors.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable lm_sensors Synchronizing state of openvpn.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable openvpn Synchronizing state of consolesaver.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable consolesaver Failed to disable unit: Unit syslogd.service does not exist Failed to disable unit: Unit syslogd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit krb5kdc.service does not exist Failed to disable unit: Unit krb5kdc.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Removed '/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service'. Failed to disable unit: Unit systemd-networkd.service does not exist Failed to disable unit: Unit systemd-networkd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit systemd-resolved.service does not exist Failed to disable unit: Unit systemd-resolved.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit clamd.service does not exist Failed to disable unit: Unit clamd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit clamsmtpd.service does not exist Failed to disable unit: Unit clamsmtpd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of blk-availability.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable blk-availability Failed to disable unit: Unit dhcpd.service does not exist Failed to disable unit: Unit dhcpd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit dmeventd.service does not exist Failed to disable unit: Unit dmeventd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of dnsmasq.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable dnsmasq Failed to disable unit: Unit lvm2-lvmetad.service does not exist Failed to disable unit: Unit lvm2-lvmetad.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of lvm2-lvmpolld.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable lvm2-lvmpolld The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of mdadm.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable mdadm The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Unit /usr/lib/systemd/system/netfs.service is masked, ignoring. The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of o2cb.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable o2cb Synchronizing state of ocfs2.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable ocfs2 Synchronizing state of postfix.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable postfix Failed to disable unit: Unit rawdevices.service does not exist Failed to disable unit: Unit rawdevices.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit slapd.service does not exist Failed to disable unit: Unit slapd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of smartd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable smartd Synchronizing state of sysstat.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable sysstat Failed to disable unit: Unit update_wms.service does not exist Failed to disable unit: Unit update_wms.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit xinetd.service does not exist Failed to disable unit: Unit xinetd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Created symlink '/etc/systemd/user/sockets.target.wants/pipewire-pulse.socket' → '/usr/lib/systemd/user/pipewire-pulse.socket'. Created symlink '/etc/systemd/user/sockets.target.wants/pipewire.socket' → '/usr/lib/systemd/user/pipewire.socket'. Created symlink '/etc/systemd/user/pipewire-session-manager.service' → '/usr/lib/systemd/user/wireplumber.service'. Created symlink '/etc/systemd/user/pipewire.service.wants/wireplumber.service' → '/usr/lib/systemd/user/wireplumber.service'. Created symlink '/etc/systemd/user/graphical-session-pre.target.wants/xdg-user-dirs.service' → '/usr/lib/systemd/user/xdg-user-dirs.service'. [ DONE ] Running postinstall script [66-setup-mdmon.sh] [ DONE ] Running postinstall script [90-clean.sh] [ DONE ] Running postinstall script [90-firsttime.sh] [ DONE ] Running postinstall script [90-pkg.sh] Using Media mount point /media/ALTLinux/ Identifying.. [7330b2ff8f6026569a7b18469430f70b-2] Scanning Media for index files.. Found 1 package indexes and 0 source indexes. Found label 'ALT Education 11.2 x86_64 build 2026-09-09' This Media is called: 'ALT Education 11.2 x86_64 build 2026-09-09' Reading Indexes... 0% Reading Indexes... Done Writing new source list Source List entries for this Media are: rpm cdrom:[ALT Education 11.2 x86_64 build 2026-09-09]/ ALTLinux main Repeat this process for the rest of the Media in your set. [ DONE ] Running postinstall script [90-runlevel5.sh] [ DONE ] Running postinstall script [95-autodomain.sh] [ DONE ] Running postinstall script [95-dconf-update] [ DONE ] Running postinstall script [99-online-repo.sh] [ DONE ]