diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-04-29 05:23:45 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-05-03 18:23:01 +0200 |
| commit | 8341a5c381a72d504768fe296f8e30a324eeff77 (patch) | |
| tree | 70dc29a424eafc5d533e2b4af2c1fcf04326ab27 /.gitignore | |
| parent | dh-dhcp{,6}-client: change the semantics of DUID setting (diff) | |
| download | systemd-8341a5c381a72d504768fe296f8e30a324eeff77.tar.xz systemd-8341a5c381a72d504768fe296f8e30a324eeff77.zip | |
networkd: rework duid_{type,duid_type,duid,duid_len} setting
Separate fields are replaced with a struct.
Second second duid type field is removed. The first field was used to carry
the result of DUIDType= configuration, and the second was either a copy of
this, or contained the type extracted from DuidRawData. The semantics are changed
so that the type specified in DUIDType is always used. DUIDRawData= no longer
overrides the type setting.
The networkd code is now more constrained than the sd-dhcp code:
DUIDRawData cannot have 0 length, length 0 is treated the same as unsetting.
Likewise, it is not possible to set a DUIDType=0. If it ever becomes necessary
to set type=0 or a zero-length duid, the code can be changed to support that.
Nevertheless, I think that's unlikely.
This addresses #3127 § 1 and 3.
v2:
- rename DUID.duid, DUID.duid_len to DUID.raw_data, DUID.raw_data_len
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions