Compare commits
No commits in common. "c05b8edde024b69a0e1eac0cc326c3a8a320b167" and "0cfb490fe9e3af39f7d7f9431b9fee9b5c98b992" have entirely different histories.
c05b8edde0
...
0cfb490fe9
17
NEWS
17
NEWS
|
@ -185,15 +185,9 @@ CHANGES WITH 246:
|
|||
new boolean setting Assign=. If enabled an address from the prefix is
|
||||
automatically assigned to the interface.
|
||||
|
||||
* systemd-networkd gained a new section [DHCPv6PrefixDelegation] which
|
||||
controls delegated prefixes assigned by DHCPv6 client. The section
|
||||
has three settings: SubnetID=, Assign=, and Token=. The setting
|
||||
SubnetID= allows explicit configuration of the preferred subnet that
|
||||
systemd-networkd's Prefix Delegation logic assigns to interfaces. If
|
||||
Assign= is enabled (which is the default) an address from any acquired
|
||||
delegated prefix is automatically chosen and assigned to the
|
||||
interface. The setting Token= specifies an optional address generation
|
||||
mode for Assign=.
|
||||
* systemd-networkd's [Network] section gained a new setting
|
||||
IPv6PDSubnetId= that allows explicit configuration of the preferred
|
||||
subnet that networkd's Prefix Delegation logic assigns to interfaces.
|
||||
|
||||
* systemd-networkd's [Network] section gained a new setting
|
||||
IPv4AcceptLocal=. If enabled the interface accepts packets with local
|
||||
|
@ -266,6 +260,11 @@ CHANGES WITH 246:
|
|||
interface which is fully set up for host communication, simply by
|
||||
carefully picking an interface name to use.
|
||||
|
||||
* A new boolean option AssignAcquiredDelegatedPrefixAddress= has been
|
||||
added to the [DHCPv6] section of .network files. If enabled (which is
|
||||
the default) an address from any acquired delegated prefix is
|
||||
automatically chosen and assigned to the interface.
|
||||
|
||||
* systemd-networkd's [DHCPv6] section gained a new setting RouteMetric=
|
||||
which sets the route priority for routes specified by the DHCP server.
|
||||
|
||||
|
|
|
@ -639,7 +639,6 @@ manpages = [
|
|||
['sd_journal_get_data',
|
||||
'3',
|
||||
['SD_JOURNAL_FOREACH_DATA',
|
||||
'sd_journal_enumerate_available_data',
|
||||
'sd_journal_enumerate_data',
|
||||
'sd_journal_get_data_threshold',
|
||||
'sd_journal_restart_data',
|
||||
|
@ -700,7 +699,6 @@ manpages = [
|
|||
['sd_journal_query_unique',
|
||||
'3',
|
||||
['SD_JOURNAL_FOREACH_UNIQUE',
|
||||
'sd_journal_enumerate_available_unique',
|
||||
'sd_journal_enumerate_unique',
|
||||
'sd_journal_restart_unique'],
|
||||
''],
|
||||
|
@ -852,7 +850,7 @@ manpages = [
|
|||
['systemd-initctl.service',
|
||||
'8',
|
||||
['systemd-initctl', 'systemd-initctl.socket'],
|
||||
'HAVE_SYSV_COMPAT'],
|
||||
''],
|
||||
['systemd-journal-gatewayd.service',
|
||||
'8',
|
||||
['systemd-journal-gatewayd', 'systemd-journal-gatewayd.socket'],
|
||||
|
|
|
@ -188,10 +188,10 @@
|
|||
the same name (except if the image has the <filename>.raw</filename> suffix, in which case the verity data file must
|
||||
not have it in its name), the verity data is read from it and automatically used.</para>
|
||||
|
||||
<para>This option is supported only for disk images that contain a single file system, without an
|
||||
enveloping partition table. Images that contain a GPT partition table should instead include both
|
||||
root file system and matching Verity data in the same image, implementing the <ulink
|
||||
url="https://systemd.io/DISCOVERABLE_PARTITIONS">Discoverable Partition Specification</ulink>.</para>
|
||||
<para>This option is supported only for disk images that contain a single file system, without an enveloping partition
|
||||
table. Images that contain a GPT partition table should instead include both root file system and matching Verity
|
||||
data in the same image, implementing the
|
||||
[Discoverable Partition Specification](https://systemd.io/DISCOVERABLE_PARTITIONS)</para>
|
||||
|
||||
<xi:include href="system-only.xml" xpointer="singular"/></listitem>
|
||||
</varlistentry>
|
||||
|
|
Loading…
Reference in New Issue