mirror of
https://github.com/systemd/systemd-stable.git
synced 2025-01-05 09:17:44 +03:00
NEWS: adjust grammar and other small changes
This commit is contained in:
parent
4076ad9daf
commit
287079696c
211
NEWS
211
NEWS
@ -5,9 +5,9 @@ CHANGES WITH 249 in spe:
|
|||||||
* When operating on disk images via the --image= switch of various
|
* When operating on disk images via the --image= switch of various
|
||||||
tools (such as systemd-nspawn or systemd-dissect), and multiple
|
tools (such as systemd-nspawn or systemd-dissect), and multiple
|
||||||
suitable root or /usr/ partitions exist in the image, then a simple
|
suitable root or /usr/ partitions exist in the image, then a simple
|
||||||
strverscmp() inspired comparison is done on the GPT partition label,
|
comparison inspired by strverscmp() is done on the GPT partition
|
||||||
and the newest partition picked. This permits a simple and generic
|
label, and the newest partition is picked. This permits a simple and
|
||||||
whole-file-system A/B update logic where new operating system
|
generic whole-file-system A/B update logic where new operating system
|
||||||
versions are dropped into partitions whose label is then updated with
|
versions are dropped into partitions whose label is then updated with
|
||||||
a matching version identifier.
|
a matching version identifier.
|
||||||
|
|
||||||
@ -44,31 +44,31 @@ CHANGES WITH 249 in spe:
|
|||||||
* The systemd-machine-id-setup tool now supports a --image= switch for
|
* The systemd-machine-id-setup tool now supports a --image= switch for
|
||||||
provisioning a machine ID file into an OS disk image, similar to how
|
provisioning a machine ID file into an OS disk image, similar to how
|
||||||
--root= operates on an OS file tree. This matches the existing switch
|
--root= operates on an OS file tree. This matches the existing switch
|
||||||
of the same name to the systemd-tmpfiles, systemd-firstboot or
|
of the same name for systemd-tmpfiles, systemd-firstboot, and
|
||||||
systemd-sysusers tools.
|
systemd-sysusers tools.
|
||||||
|
|
||||||
* Similar, systemd-repart gained support for a --image= switch, too. In
|
* Similarly, systemd-repart gained support for the --image= switch too.
|
||||||
combination with the existing --size= makes the tool particularly
|
In combination with the existing --size= option, this makes the tool
|
||||||
useful for easily growing disk images in a single command invocation,
|
particularly useful for easily growing disk images in a single
|
||||||
following the declarative rules included in the image itself.
|
invocation, following the declarative rules included in the image
|
||||||
|
itself.
|
||||||
|
|
||||||
* systemd-repart's partition configuration files gained support for a
|
* systemd-repart's partition configuration files gained support for a
|
||||||
new switch MakeDirectories= which may be used to create arbitrary
|
new switch MakeDirectories= which may be used to create arbitrary
|
||||||
directories inside file systems that are created, before registering
|
directories inside file systems that are created, before registering
|
||||||
them in the partition table. This is useful in particular if root
|
them in the partition table. This is useful in particular for root
|
||||||
partitions are created that way to create mount point directories for
|
partitions to create mount point directories for other partitions
|
||||||
other partitions included in the image. For example, a disk image
|
included in the image. For example, a disk image that contains a
|
||||||
that is created to contain a /home/ and a /var/ partition in addition
|
root, /home/, and /var/ partitions, may set MakeDirectories=yes to
|
||||||
to a root partition may MakeDirectories= to create /home/ and /var/
|
create /home/ and /var/ as empty directories in the root file system
|
||||||
as empty directories in the root file system on creation so that the
|
on its creation, so that the resulting image can mounted immediately,
|
||||||
resulting image can mounted immediately, even in read-only mode.
|
even in read-only mode.
|
||||||
|
|
||||||
* systemd-repart's CopyBlocks= setting gained support for a special
|
* systemd-repart's CopyBlocks= setting gained support for the special
|
||||||
value "auto". If used a suitable, matching partition on the booted OS
|
value "auto". If used, a suitable matching partition on the booted OS
|
||||||
is found as source to copy blocks from. This is useful for
|
is found as source to copy blocks from. This is useful when
|
||||||
implementing replicating installers, that are booted from one medium
|
implementing replicating installers, that are booted from one medium
|
||||||
and then shall stream their own root partition onto the target
|
and then stream their own root partition onto the target medium.
|
||||||
medium.
|
|
||||||
|
|
||||||
* systemd-repart's partition configuration files gained support for a
|
* systemd-repart's partition configuration files gained support for a
|
||||||
Flags= and a ReadOnly= setting, allowing control of the GPT partition
|
Flags= and a ReadOnly= setting, allowing control of the GPT partition
|
||||||
@ -76,40 +76,40 @@ CHANGES WITH 249 in spe:
|
|||||||
created partitions as read-only from the start.
|
created partitions as read-only from the start.
|
||||||
|
|
||||||
* The /etc/os-release file has been extended with two new (optional)
|
* The /etc/os-release file has been extended with two new (optional)
|
||||||
variables IMAGE_VERSION= and IMAGE_ID=, for carrying identification
|
variables IMAGE_VERSION= and IMAGE_ID=, carrying identity and version
|
||||||
and versioning information for OS images that are updated
|
information for OS images that are updated comprehensively and
|
||||||
consistently, comprehensively and atomically as one image. The two
|
atomically as one image. Two new specifiers %M, %A now resolve to
|
||||||
new specifiers %M, %A now resolve to these two fields in the various
|
these two fields in the various configuration options that resolve
|
||||||
configuration options that resolve specifiers.
|
specifiers.
|
||||||
|
|
||||||
* portablectl gained a new switch --extension= for enabling portable
|
* portablectl gained a new switch --extension= for enabling portable
|
||||||
service images with extensions that follow the extension image
|
service images with extensions that follow the extension image
|
||||||
concept introduced with v248.
|
concept introduced with v248.
|
||||||
|
|
||||||
* systemd-coredump will now extract ELF build-id information from
|
* systemd-coredump will now extract ELF build-id information from
|
||||||
processes dumping core and include it in the coredump
|
processes dumping core and include it in the coredump report.
|
||||||
report. Moreover, if will look for ELF .note.package sections that
|
Moreover, it will look for ELF .note.package sections with
|
||||||
may carry distribution packaging meta-information about the crashing
|
distribution packaging meta-information about the crashing process.
|
||||||
process. This is useful to directly embed the RPM or Debian (or any
|
This is useful to directly embed the rpm or deb (or any other)
|
||||||
other) package name and version in the ELF files where they originate
|
package name and version in ELF files, making it easy to match
|
||||||
from, making it easy to match up coredump reports with the software
|
coredump reports with the specific package for which the software was
|
||||||
versions they were found it. This is particular useful on
|
compiled. This is particularly useful on environments with ELF files
|
||||||
environments with ELF files form multiple vendors, different
|
from multiple vendors, different distributions and versions, as is
|
||||||
distributions and versions, as it is common today, in particular in a
|
common today in our containerized and sand-boxed world. For further
|
||||||
containerized and sand-boxed world. For further information, see:
|
information, see:
|
||||||
|
|
||||||
https://systemd.io/COREDUMP_PACKAGE_METADATA
|
https://systemd.io/COREDUMP_PACKAGE_METADATA
|
||||||
|
|
||||||
* A new udev hwdb database has been added for FireWire devices (IEEE
|
* A new udev hardware database has been added for FireWire devices
|
||||||
1394).
|
(IEEE 1394).
|
||||||
|
|
||||||
* sd-bus' sd_bus_is_ready() and sd_bus_is_open() calls now accept a
|
* sd-bus' sd_bus_is_ready() and sd_bus_is_open() calls now accept a
|
||||||
NULL bus object, for which they will return false. Or in other words,
|
NULL bus object, for which they will return false. Or in other words,
|
||||||
an unallocated bus connection is neither ready nor open.
|
an unallocated bus connection is neither ready nor open.
|
||||||
|
|
||||||
* The sd-device API acquired a new API function
|
* The sd-device API acquired a new API function
|
||||||
sd_device_get_usec_initialized() that returns the monotonic timestamp
|
sd_device_get_usec_initialized() that returns the monotonic time when
|
||||||
when a udev device appeared in the database first.
|
the udev device first appeared in the database.
|
||||||
|
|
||||||
* sd-device gained a new APIs sd_device_trigger_with_uuid() and
|
* sd-device gained a new APIs sd_device_trigger_with_uuid() and
|
||||||
sd_device_get_trigger_uuid(). The former is similar to
|
sd_device_get_trigger_uuid(). The former is similar to
|
||||||
@ -168,13 +168,14 @@ CHANGES WITH 249 in spe:
|
|||||||
[NextHop] entries, via the new Group= setting.
|
[NextHop] entries, via the new Group= setting.
|
||||||
|
|
||||||
* The DHCP server logic configured in .network files gained a new
|
* The DHCP server logic configured in .network files gained a new
|
||||||
setting RelayTarget= that turns the server into a DHCP server
|
setting RelayTarget= that turns the server into a DHCP server relay.
|
||||||
relay. The RelayAgentCircuitId= and RelayAgentRemoteId= settings may
|
The RelayAgentCircuitId= and RelayAgentRemoteId= settings may be used
|
||||||
be used to further tweak the DHCP relay behaviour.
|
to further tweak the DHCP relay behaviour.
|
||||||
|
|
||||||
* The DHCP server logic also gained a new setting ServerAddress= in
|
* The DHCP server logic also gained a new ServerAddress= setting in
|
||||||
.network files for explicitly specifying the server IP address to
|
.network files that explicitly specifies the server IP address to
|
||||||
use. If not used, the address is determined automatically, as before.
|
use. If not specified, the address is determined automatically, as
|
||||||
|
before.
|
||||||
|
|
||||||
* The DHCP server logic in systemd-networkd gained support for static
|
* The DHCP server logic in systemd-networkd gained support for static
|
||||||
DHCP leases, configurable via the [DHCPServerStaticLease]
|
DHCP leases, configurable via the [DHCPServerStaticLease]
|
||||||
@ -187,53 +188,51 @@ CHANGES WITH 249 in spe:
|
|||||||
|
|
||||||
* systemd-fstab-generator and systemd-repart have been updated to
|
* systemd-fstab-generator and systemd-repart have been updated to
|
||||||
support booting from disks that carry only a /usr/ partition but no
|
support booting from disks that carry only a /usr/ partition but no
|
||||||
root partition yet, but where systemd-repart can add them in on first
|
root partition yet, and where systemd-repart can add it in on the
|
||||||
boot. This is useful for implementing systems that ship with a single
|
first boot. This is useful for implementing systems that ship with a
|
||||||
/usr/ file system and whose root file system shall be set up on a
|
single /usr/ file system, and whose root file system shall be set up
|
||||||
LUKS encrypted volume whose key is generated locally (and possibly
|
and formatted on a LUKS-encrypted volume whose key is generated
|
||||||
enrolled in TPM), and which is set up and formatted during first
|
locally (and possibly enrolled in the TPM) during the first boot.
|
||||||
boot.
|
|
||||||
|
|
||||||
* The [Address] section of .network files now accepts a new
|
* The [Address] section of .network files now accepts a new
|
||||||
RouteMetric= setting that configures the routing metric to use for
|
RouteMetric= setting that configures the routing metric to use for
|
||||||
the prefix route created as effect of the address
|
the prefix route created as effect of the address configuration.
|
||||||
configuration. Similar, the [DHCPv6PrefixDelegation] and [IPv6Prefix]
|
Similarly, the [DHCPv6PrefixDelegation] and [IPv6Prefix] sections
|
||||||
sections gained matching settings for their prefix routes. (The
|
gained matching settings for their prefix routes. (The option of the
|
||||||
option of the same name of the [DHCPv6] section is moved to
|
same name in the [DHCPv6] section is moved to [IPv6AcceptRA], since
|
||||||
[IPv6AcceptRA], since it conceptually belongs there; the old option
|
it conceptually belongs there; the old option is still understood for
|
||||||
is still understood for compatibility.)
|
compatibility.)
|
||||||
|
|
||||||
* The DHCPv6 IAID and DUID are now explicitly configurable in .network
|
* The DHCPv6 IAID and DUID are now explicitly configurable in .network
|
||||||
files.
|
files.
|
||||||
|
|
||||||
* A new udev property ID_NET_DHCP_BROADCAST on network interface
|
* A new udev property ID_NET_DHCP_BROADCAST on network interface
|
||||||
devices is not honoured by systemd-networkd, that controls whether to
|
devices is now honoured by systemd-networkd, controlling whether to
|
||||||
issue DHCP offers via broadcasting. This is used to ensure that s390
|
issue DHCP offers via broadcasting. This is used to ensure that s390
|
||||||
layer 3 network interfaces work out-of-the-box with systemd-networkd.
|
layer 3 network interfaces work out-of-the-box with systemd-networkd.
|
||||||
|
|
||||||
* nss-myhostname and systemd-resolved will now synthesize address
|
* nss-myhostname and systemd-resolved will now synthesize address
|
||||||
records for a new special hostname "_outbound". The name will always
|
records for a new special hostname "_outbound". The name will always
|
||||||
resolve to the local IP addresses most likely used for outbound
|
resolve to the local IP addresses most likely used for outbound
|
||||||
connections towards the default route. On multi-homed hosts this is
|
connections towards the default routes. On multi-homed hosts this is
|
||||||
useful to have a stable handle referring to "the" local IP address
|
useful to have a stable handle referring to "the" local IP address
|
||||||
that matters most, to the point where this is defined.
|
that matters most, to the point where this is defined.
|
||||||
|
|
||||||
* The Discoverable Partition Specification has been updated with a new
|
* The Discoverable Partition Specification has been updated with a new
|
||||||
GPT partition flag defined its partition types: a "growfs"
|
GPT partition flag "growsfs" defined for its partition types.
|
||||||
flag. Whenever partitions with this flag set are automatically
|
Whenever partitions with this flag set are automatically mounted
|
||||||
mounted (i.e. via systemd-gpt-auto-generator or the --image= switch
|
(i.e. via systemd-gpt-auto-generator or the --image= switch of
|
||||||
of systemd-nspawn or other tools; and as opposed to explicit mounting
|
systemd-nspawn or other tools; and as opposed to explicit mounting
|
||||||
via /etc/fstab), the file system within the partition is
|
via /etc/fstab), the file system within the partition is
|
||||||
automatically grown to the full size of the partition should it be
|
automatically grown to the full size of the partition. If the file
|
||||||
smaller. If the file system size already matches the partition size
|
system size already matches the partition size this flag has no
|
||||||
this flag has no effect. Previously, this functionality has been
|
effect. Previously, this functionality has been available via the
|
||||||
available via the explicit x-systemd.growfs mount option, and this
|
explicit x-systemd.growfs mount option, and this new flag extends
|
||||||
new flag extends this to automatically discovered mounts. A new
|
this to automatically discovered mounts. A new GrowFileSystem=
|
||||||
GrowFileSystem= setting has been added to systemd-repart drop-in
|
setting has been added to systemd-repart drop-in files that allows
|
||||||
files that allows configuring this partition flag. This new flag
|
configuring this partition flag. This new flag defaults to on for
|
||||||
defaults to on for partitions automatically created by
|
partitions automatically created by systemd-repart, except if they
|
||||||
systemd-repart, except if they are marked read-only. See the
|
are marked read-only. See the specification for further details:
|
||||||
specification for further details:
|
|
||||||
|
|
||||||
https://systemd.io/DISCOVERABLE_PARTITIONS
|
https://systemd.io/DISCOVERABLE_PARTITIONS
|
||||||
|
|
||||||
@ -250,27 +249,27 @@ CHANGES WITH 249 in spe:
|
|||||||
sockets created by the service may be bound to. This is implemented
|
sockets created by the service may be bound to. This is implemented
|
||||||
via BPF.
|
via BPF.
|
||||||
|
|
||||||
* A new ConditionFirmware= condition type has been added to unit
|
* A new ConditionFirmware= condition type has been added to unit files.
|
||||||
files. It may be used to detect certain firmware features. At the
|
It may be used to detect certain firmware features. At the moment it
|
||||||
moment it may check whether running on an UEFI system, a device.tree
|
may check whether running on an UEFI system, a device.tree system, or
|
||||||
system or if the system is compatible with some specified device-tree
|
if the system is compatible with some specified device-tree feature.
|
||||||
feature.
|
|
||||||
|
|
||||||
* hostnamed gained a new Describe() D-Bus method that returns a JSON
|
* hostnamed gained a new Describe() D-Bus method that returns a JSON
|
||||||
serialization of the host data it exposes. This is exposed via
|
serialization of the host data it exposes. This is exposed via
|
||||||
"hostnamectl --json=" to acquire a host identity description in
|
"hostnamectl --json=" to acquire a host identity description in JSON.
|
||||||
JSON. It's our intention to add a similar concept to most services
|
It's our intention to add a similar features to most services and
|
||||||
and objects systemd manages, in order to simplify integration with
|
objects systemd manages, in order to simplify integration with
|
||||||
program code the consumes JSON.
|
program code that can consume JSON.
|
||||||
|
|
||||||
* Similar, networkd gained a Describe() method on its Manager and Link
|
* Similarly, networkd gained a Describe() method on its Manager and
|
||||||
bus objects. This is exposed via "networkctl --json=".
|
Link bus objects. This is exposed via "networkctl --json=".
|
||||||
|
|
||||||
* hostnamectl's various set-xyz verbs (e.g. "hostnamectl set-hostname")
|
* hostnamectl's various "get-xyz"/"set-xyz" verb pairs
|
||||||
have been renamed to just xyz (e.g. "hostnamectl hostname") and may
|
(e.g. "hostnamectl get-hostname", "hostnamectl "set-hostname") have
|
||||||
now be used to print the indicated data in terse form, instead of
|
been replaced by a single "xyz" verb (e.g. "hostnamectl hostname")
|
||||||
only setting it. The old names continue to be supported for
|
that is used both to get the value (when no argument is given), and
|
||||||
compatibility.
|
to set the value (when an argument is specified). The old names
|
||||||
|
continue to be supported for compatibility.
|
||||||
|
|
||||||
* systemd-detect-virt and ConditionVirtualization= are now able to
|
* systemd-detect-virt and ConditionVirtualization= are now able to
|
||||||
correctly identify Amazon EC2 environments.
|
correctly identify Amazon EC2 environments.
|
||||||
@ -283,8 +282,8 @@ CHANGES WITH 249 in spe:
|
|||||||
|
|
||||||
* bootctl gained support for a new --make-machine-id-directory= switch
|
* bootctl gained support for a new --make-machine-id-directory= switch
|
||||||
that allows precise control on whether to create the top-level
|
that allows precise control on whether to create the top-level
|
||||||
per-machine directory in the boot partition that typically contain
|
per-machine directory in the boot partition that typically contains
|
||||||
Type #1 boot loader entries.
|
Type 1 boot loader entries.
|
||||||
|
|
||||||
* During build SBAT data to include in the systemd-boot EFI PE binaries
|
* During build SBAT data to include in the systemd-boot EFI PE binaries
|
||||||
may be specified now.
|
may be specified now.
|
||||||
@ -385,21 +384,20 @@ CHANGES WITH 249 in spe:
|
|||||||
|
|
||||||
* A new dependency type OnSuccess= has been added (plus the reverse
|
* A new dependency type OnSuccess= has been added (plus the reverse
|
||||||
dependency OnSuccessOf=, which cannot be configured directly, but
|
dependency OnSuccessOf=, which cannot be configured directly, but
|
||||||
exists only as effect of the reverse OnSuccess=). It's similar to
|
exists only as effect of the reverse OnSuccess=). It is similar to
|
||||||
OnFailure= but triggers in the opposite case: when a service exits
|
OnFailure=, but triggers in the opposite case: when a service exits
|
||||||
cleanly. This allows "chaining up" of services where one or more
|
cleanly. This allows "chaining up" of services where one or more
|
||||||
services are started once another service successfully completed its
|
services are started once another service has successfully completed.
|
||||||
runtime.
|
|
||||||
|
|
||||||
* A new dependency type Upholds= has been added (plus the reverse
|
* A new dependency type Upholds= has been added (plus the reverse
|
||||||
dependency UpheldBy=, which cannot be configured directly, but
|
dependency UpheldBy=, which cannot be configured directly, but exists
|
||||||
exists only as effect of the reverse Upholds=). This dependency type
|
only as effect of Upholds=). This dependency type is a stronger form
|
||||||
is a stronger form of Wants=: if a unit has an UpHolds= dependency on
|
of Wants=: if a unit has an UpHolds= dependency on some other unit
|
||||||
some other unit and the former is active then the latter is started
|
and the former is active then the latter is started whenever it is
|
||||||
whenever it is found inactive (and no job queued for it). This is an
|
found inactive (and no job is queued for it). This is an alternative
|
||||||
alternative to Restart= inside service units, but less configurable,
|
to Restart= inside service units, but less configurable, and the
|
||||||
and the request to uphold a unit is not encoded in the unit itself
|
request to uphold a unit is not encoded in the unit itself but in
|
||||||
but in another unit that intends to uphold it.
|
another unit that intends to uphold it.
|
||||||
|
|
||||||
* The systemd-ask-password tool now also supports reading passwords
|
* The systemd-ask-password tool now also supports reading passwords
|
||||||
from the credentials subsystem, via the new --credential= switch.
|
from the credentials subsystem, via the new --credential= switch.
|
||||||
@ -409,10 +407,9 @@ CHANGES WITH 249 in spe:
|
|||||||
shown in the password prompt on suitable TTYs.
|
shown in the password prompt on suitable TTYs.
|
||||||
|
|
||||||
* The --echo switch of systemd-ask-password now optionally takes a
|
* The --echo switch of systemd-ask-password now optionally takes a
|
||||||
parameter that controls whether to echo the typed in password back
|
parameter that controls character echo. It may either show asterisks
|
||||||
while typing in. It may either show asterisks as echo (default, as
|
(default, as before), turn echo off entirely, or echo the typed
|
||||||
before), turn the echo off entirely, or echo the types characters
|
characters literally.
|
||||||
literally.
|
|
||||||
|
|
||||||
* New documentation has been added that describes the organization of
|
* New documentation has been added that describes the organization of
|
||||||
the systemd source code tree:
|
the systemd source code tree:
|
||||||
|
Loading…
Reference in New Issue
Block a user