Additional videos are available (and more), including tutorial and BOF sessions for which no paper was required.
History of network booting (TFTP/BOOTP and NBI predated PXE, which is the network booting standard published by Intel in 1997 and supported by most BIOSes today). History of SYSLINUX (contains PXELINUX) and Etherboot (precursor to gPXE).
PXE has three parts. The first two (some low-level base code, and a network driver) are saved in the firmware. They fetch a "Network Boot Program" (NBP), from the network, which is a small loader which can call the network driver out of the firmware to load the rest of the operating system. Using gPXE with PXELINUX generally means using gPXE to provide the base code and network driver in the firmware (for use with things like OpenBios), and loading PXELINUX to act as an NBP.
Ends with issues related to two projects working together.
Automated testing for the Linux kernel. Linux Test Project, Fault Injection Framework, IBM's proprietary "Automated Build And Test" server, etc.
An open source project that uses static analysis to construct a model of application behavior (control flow graphs).
[Some significant oversimplifications in this one. As far as I can tell, "it interprets Javascript" would count as "self modifying code". Being written in something like Python would fundamentally invalidate the assumptions too. The technique is aimed at non-kernel C code that doesn't implement an interpreter for another language.]