From da2cad4b14fb16c6c186869822efb7dde18b3b55 Mon Sep 17 00:00:00 2001 From: Simon Kelley Date: Wed, 18 May 2016 15:14:08 +0100 Subject: [PATCH] Doc about --pxe-service basename change into CHANGELOG. --- CHANGELOG | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/CHANGELOG b/CHANGELOG index c73ddc2..04ff3f0 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -99,6 +99,24 @@ version 2.76 Many thanks to Jarek Polok, Michael Kuron and Dreamcat4 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 . where 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 .0 + The new behaviour is the same as the old, except when + 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 Fix reversion on 2.74 which caused 100% CPU use when a