CLIENT SIDE
update-kernels:

 * Distro specific, generates symlinks for the latest version of each kernel variant.
 * symlinks: vmlinuz-64, vmlinuz-pae, vmlinuz-32, vmlinuz-default (vmlinuz fallback)?
 ** other arches? sub-arches(486)? featuresets (rt)? (implement later)
 ** we could just copy all the symlinks that start with vmlinuz-*
 ** and match the respective initrd-*.

ltsp-client-core: /etc/ltsp/update-kernels.conf
 * Contains variables with just the kernel parameters for NBD, NFS etc.
 * Maybe it contains variables with the kernel suffixes too? pae, 32, 64?

SERVER SIDE
ltsp-update-kernels:
 * Generates a <tftpdir>/ltsp/<arch>/pxelinux.cfg/default, if it doesn't exist. That basically has an INCLUDE line and a comment that tells the user to copy the contents of the INCLUDEd file if he wants to change them, because they're always regenerated.
 * copies <chroot>/boot and <img>/boot to <tftpdir>/ltsp/<chroot|img>
 * regenerates <tftpdir>/ltsp/<chroot>/pxelinux.cfg/ltsp and puts all the vmlinu[xz]* files in <tftpdir>/ltsp/<chroot>, defaulting to known symlinked versions, with the kernel parameters from <chroot>/etc/ltsp/update-kernels.conf. It tries to match the supported BOOT_METHODS of the chroot with the ones provided by the server.
 * one pxelinux boot entry per chroot/img and kernel combination