Re: [systemd-devel] systemd 256 released

2024-06-16 Thread Luna Jernberg
https://linuxunplugged.com/567

Den tis 11 juni 2024 kl 23:45 skrev systemd tag bot
:
>
>  A new, official systemd release has just  been  tagged . Please download 
> the tarball here:
>
> https://github.com/systemd/systemd/archive/v256.tar.gz
>
> Changes since the previous release:
>
> Announcements of Future Feature Removals and Incompatible Changes:
>
> * Support for automatic flushing of the nscd user/group database 
> caches
>   will be dropped in a future release.
>
> * Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now
>   considered obsolete and systemd by default will refuse to boot under
>   it. To forcibly reenable cgroup v1 support,
>   SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command
>   line. The meson option 'default-hierarchy=' is also deprecated, i.e.
>   only cgroup v2 ('unified' hierarchy) can be selected as build-time
>   default.
>
> * Support for System V service scripts is deprecated and will be
>   removed in a future release. Please make sure to update your 
> software
>   *now* to include a native systemd unit file instead of a legacy
>   System V script to retain compatibility with future systemd 
> releases.
>
> * Support for the SystemdOptions EFI variable is deprecated.
>   'bootctl systemd-efi-options' will emit a warning when used. It 
> seems
>   that this feature is little-used and it is better to use alternative
>   approaches like credentials and confexts. The plan is to drop 
> support
>   altogether at a later point, but this might be revisited based on
>   user feedback.
>
> * systemd-run's switch --expand-environment= which currently is 
> disabled
>   by default when combined with --scope, will be changed in a future
>   release to be enabled by default.
>
> * Previously, systemd-networkd did not explicitly remove any bridge
>   VLAN IDs assigned on bridge master and ports. Since version 256, if 
> a
>   .network file for an interface has at least one valid setting in the
>   [BridgeVLAN] section, then all assigned VLAN IDs on the interface
>   that are not configured in the .network file are removed.
>
> * IPForward= setting in .network file is deprecated and replaced with
>   IPv4Forwarding= and IPv6Forwarding= settings. These new settings are
>   supported both in .network file and networkd.conf. If specified in a
>   .network file, they control corresponding per-link settings. If
>   specified in networkd.conf, they control corresponding global
>   settings. Note, previously IPv6SendRA= and IPMasquerade= implied
>   IPForward=, but now they imply the new per-link settings. One of the
>   simplest ways to migrate configurations, that worked as a router 
> with
>   the previous version, is enabling both IPv4Forwarding= and
>   IPv6Forwarding= in networkd.conf. See systemd.network(5) and
>   networkd.conf(5) for more details.
>
> * systemd-gpt-auto-generator will stop generating units for ESP or
>   XBOOTLDR partitions if it finds mount entries for or below the 
> /boot/
>   or /efi/ hierarchies in /etc/fstab. This is to prevent the generator
>   from interfering with systems where the ESP is explicitly configured
>   to be mounted at some path, for example /boot/efi/ (this type of
>   setup is obsolete, but still commonly found).
>
> * The behavior of systemd-sleep and systemd-homed has been updated to
>   freeze user sessions when entering the various sleep modes or when
>   locking a homed-managed home area. This is known to cause issues 
> with
>   the proprietary NVIDIA drivers. Packagers of the NVIDIA proprietary
>   drivers may want to add drop-in configuration files that set
>   SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false for systemd-suspend.service
>   and related services, and SYSTEMD_HOME_LOCK_FREEZE_SESSION=false for
>   systemd-homed.service.
>
> * systemd-tmpfiles and systemd-sysusers, when given a relative
>   configuration file path (with at least one directory separator '/'),
>   will open the file directly, instead of searching for the given
>   partial path in the standard locations. The old mode wasn't useful
>   because tmpfiles.d/ and sysusers.d/ configuration has a flat
>   structure with no subdirectories under the standard locations and
>   this change makes it easier to work with local files with those
>   tools.
>
> * systemd-tmpfiles now properly applies nested configuration to 'R' 
> and
>   'D' stanzas. For example, with the combination of 'R /foo' and 'x
>   /foo/bar', /foo/bar will now be 

[systemd-devel] systemd 256 released

2024-06-11 Thread systemd tag bot
 A new, official systemd release has just  been  tagged . Please download 
the tarball here:

https://github.com/systemd/systemd/archive/v256.tar.gz

Changes since the previous release:

Announcements of Future Feature Removals and Incompatible Changes:

* Support for automatic flushing of the nscd user/group database caches
  will be dropped in a future release.

* Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now
  considered obsolete and systemd by default will refuse to boot under
  it. To forcibly reenable cgroup v1 support,
  SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command
  line. The meson option 'default-hierarchy=' is also deprecated, i.e.
  only cgroup v2 ('unified' hierarchy) can be selected as build-time
  default.

* Support for System V service scripts is deprecated and will be
  removed in a future release. Please make sure to update your software
  *now* to include a native systemd unit file instead of a legacy
  System V script to retain compatibility with future systemd releases.

* Support for the SystemdOptions EFI variable is deprecated.
  'bootctl systemd-efi-options' will emit a warning when used. It seems
  that this feature is little-used and it is better to use alternative
  approaches like credentials and confexts. The plan is to drop support
  altogether at a later point, but this might be revisited based on
  user feedback.

* systemd-run's switch --expand-environment= which currently is disabled
  by default when combined with --scope, will be changed in a future
  release to be enabled by default.

* Previously, systemd-networkd did not explicitly remove any bridge
  VLAN IDs assigned on bridge master and ports. Since version 256, if a
  .network file for an interface has at least one valid setting in the
  [BridgeVLAN] section, then all assigned VLAN IDs on the interface
  that are not configured in the .network file are removed.

* IPForward= setting in .network file is deprecated and replaced with
  IPv4Forwarding= and IPv6Forwarding= settings. These new settings are
  supported both in .network file and networkd.conf. If specified in a
  .network file, they control corresponding per-link settings. If
  specified in networkd.conf, they control corresponding global
  settings. Note, previously IPv6SendRA= and IPMasquerade= implied
  IPForward=, but now they imply the new per-link settings. One of the
  simplest ways to migrate configurations, that worked as a router with
  the previous version, is enabling both IPv4Forwarding= and
  IPv6Forwarding= in networkd.conf. See systemd.network(5) and
  networkd.conf(5) for more details.

* systemd-gpt-auto-generator will stop generating units for ESP or
  XBOOTLDR partitions if it finds mount entries for or below the /boot/
  or /efi/ hierarchies in /etc/fstab. This is to prevent the generator
  from interfering with systems where the ESP is explicitly configured
  to be mounted at some path, for example /boot/efi/ (this type of
  setup is obsolete, but still commonly found).

* The behavior of systemd-sleep and systemd-homed has been updated to
  freeze user sessions when entering the various sleep modes or when
  locking a homed-managed home area. This is known to cause issues with
  the proprietary NVIDIA drivers. Packagers of the NVIDIA proprietary
  drivers may want to add drop-in configuration files that set
  SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false for systemd-suspend.service
  and related services, and SYSTEMD_HOME_LOCK_FREEZE_SESSION=false for
  systemd-homed.service.

* systemd-tmpfiles and systemd-sysusers, when given a relative
  configuration file path (with at least one directory separator '/'),
  will open the file directly, instead of searching for the given
  partial path in the standard locations. The old mode wasn't useful
  because tmpfiles.d/ and sysusers.d/ configuration has a flat
  structure with no subdirectories under the standard locations and
  this change makes it easier to work with local files with those
  tools.

* systemd-tmpfiles now properly applies nested configuration to 'R' and
  'D' stanzas. For example, with the combination of 'R /foo' and 'x
  /foo/bar', /foo/bar will now be excluded from removal.

* systemd.crash_reboot and related settings are deprecated in favor of
  systemd.crash_action=.

General Changes and New Features:

* Various programs will now attempt to load the main configuration file