Update systemd from 242 to 243

[pmenzel]

Tested on rabammel with systemctl daemon-reexec.

[wwwutz]

systemd changes a kernel default AGAIN.

         This release enables unprivileged programs (i.e. requiring neither
          setuid nor file capabilities) to send ICMP Echo (i.e. ping) requests
          by turning on the "net.ipv4.ping_group_range" sysctl of the Linux
          kernel for the whole UNIX group range, i.e. all processes. This
          change should be reasonably safe, as the kernel support for it was
          specifically implemented to allow safe access to ICMP Echo for
          processes lacking any privileges. If this is not desirable, it can be
          disabled again by setting the parameter to "1 0".

[wwwutz]

an next:

           On 64 bit systems, the "kernel.pid_max" sysctl is now bumped to
          4194304 by default, i.e. the full 22bit range the kernel allows, up
          from the old 16bit range. 

[wwwutz]

Na klasse, jetzt gibts auch noch nen systemd OOM - Killer... viel spass bei Ursache suchen....

* PID 1 will now listen to Out-Of-Memory (OOM) events the kernel
          generates when processes it manages are reaching their memory limits,
          and will place their units in a special state, and optionally kill or
          stop the whole unit.

[wwwutz]

danke fuer diene farbwahl ...

 journalctl (and the other tools that display logs) will now highlight
          warnings in yellow (previously, both LOG_NOTICE and LOG_WARNING where
          shown in bright bold, now only LOG_NOTICE is). Moreover, audit logs
          are now shown in blue color, to separate them visually from regular
          logs. References to configuration files are now turned into clickable
          links on terminals that support that.

[wwwutz]

und WIEDER ein default... noch besser wieder im network-naming rumpfuschen

The predictable naming scheme for network devices now supports
          generating predictable names for "netdevsim" devices.

          Moreover, the "en" prefix was dropped from the ID_NET_NAME_ONBOARD
          udev property.

          Those two changes form a new net.naming-policy-scheme= entry.
          Distributions which want to preserve naming stability may want to set
          the -Ddefault-net-naming-scheme= configuration option.

[wwwutz]

Don't tell mne where to put my binaries and how to name them you fi.

* The order of entries is $PATH used by the user manager instance was
          changed to put bin/ entries before the corresponding sbin/ entries.
          It is recommended to not rely on this order, and only ever have one
          binary with a given name in the system paths under /usr.

[pmenzel]

Please note, what changes you find unreasonable (and why it wouldn’t fit in MarIuX). Then I can change it back.

[wwwutz]

Wenn man wieder jemand nix sieht... jetzt gibts die naechste fehlerquelle:

* The order of entries is $PATH used by the user manager instance was
          changed to put bin/ entries before the corresponding sbin/ entries.
          It is recommended to not rely on this order, and only ever have one
          binary with a given name in the system paths under /usr.

[wwwutz]

ich fass es nicht. DAS war/ist schon bei Windows ne Frechheit. "ich such mir mal was, oh das nehm ich"

* When the system is hibernated the swap device to write the
          hibernation image to is now automatically picked from all available
          swap devices, preferring the swap device with the highest configured
          priority over all others, and picking the device with the most free
          space if there are multiple devices with the highest priority.

[wwwutz]

the bee-queen (a.k.a. build:build) disapproves:

# CHECK # less work/systemd.stdout
#FIXME-NEEDROOT# FAIL bee_install(): chown: changing ownership of '/scratch/local2/beehive/systemd/buildroot/systemd/systemd-243-0/image/var/log/journal': Operation not permitted

Installing /scratch/local2/beehive/systemd/buildroot/systemd/systemd-243-0/build/po/zh_CN.gmo to /scratch/local2/beehive/systemd/buildroot/systemd/systemd-243-0/image/usr/share/locale/zh_CN/LC_MESSAGES/systemd.mo
Installing /scratch/local2/beehive/systemd/buildroot/systemd/systemd-243-0/build/po/zh_TW.gmo to /scratch/local2/beehive/systemd/buildroot/systemd/systemd-243-0/image/usr/share/locale/zh_TW/LC_MESSAGES/systemd.mo
chown: changing ownership of '/scratch/local2/beehive/systemd/buildroot/systemd/systemd-243-0/image/var/log/journal': Operation not permitted
setfacl: Option -m: Invalid argument near character 3
mkdir: created directory '/scratch/local2/beehive/systemd/buildroot/systemd/systemd-243-0/image/sbin'
'/scratch/local2/beehive/systemd/buildroot/systemd/systemd-243-0/image/sbin/init' -> '../lib/systemd/systemd'
mkdir: created directory '/scratch/local2/beehive/systemd/buildroot/systemd/systemd-243-0/image/usr/lib/environment.d'
'/scratch/local2/beehive/systemd/buildroot/systemd/systemd-243-0/image/usr/lib/environment.d/99-environment.conf' -> '../../../etc/environment'

[wwwutz]

Issue #1216 ? Ignored or nothing learned ?

Connecting to codeload.github.com|140.82.114.9|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: ‘/scratch/local2/beehive/systemd/buildroot/systemd/files/v243.tar.gz’

[pmenzel]

Issue #1216 ? Ignored or nothing learned?

[…]

Forgotten and overlooked.