mirror of
https://github.com/pi-hole/dnsmasq.git
synced 2025-12-19 18:28:25 +00:00
Doc about --pxe-service basename change into CHANGELOG.
This commit is contained in:
18
CHANGELOG
18
CHANGELOG
@@ -99,6 +99,24 @@ version 2.76
|
|||||||
Many thanks to Jarek Polok, Michael Kuron and Dreamcat4
|
Many thanks to Jarek Polok, Michael Kuron and Dreamcat4
|
||||||
for their work on the long-standing UEFI PXE problem.
|
for their work on the long-standing UEFI PXE problem.
|
||||||
|
|
||||||
|
Subtle change in the semantics of "basename" in
|
||||||
|
--pxe-service. The historical behaviour has always been
|
||||||
|
that the actual filename downloaded from the TFTP server
|
||||||
|
is <basename>.<layer> where <layer> is an integer which
|
||||||
|
corresponds to the layer parameter supplied by the client.
|
||||||
|
It's not clear what the function of the "layer"
|
||||||
|
actually is in the PXE protocol, and in practise layer
|
||||||
|
is always zero, so the filename is <basename>.0
|
||||||
|
The new behaviour is the same as the old, except when
|
||||||
|
<basename> includes a file suffix, in which case
|
||||||
|
the layer suffix is no longer added. This allows
|
||||||
|
sensible suffices to be used, rather then the
|
||||||
|
meaningless ".0". Only in the unlikely event that you
|
||||||
|
have a config with a basename which already has a
|
||||||
|
suffix, is this an incompatible change, since the file
|
||||||
|
downloaded will change from name.suffix.0 to just
|
||||||
|
name.suffix
|
||||||
|
|
||||||
|
|
||||||
version 2.75
|
version 2.75
|
||||||
Fix reversion on 2.74 which caused 100% CPU use when a
|
Fix reversion on 2.74 which caused 100% CPU use when a
|
||||||
|
|||||||
Reference in New Issue
Block a user