A new crazy idea of mine in case someone likes it and has some time to
start implementing it. If not, I'll probably do it sometime in the
It should be quite easy to write a tftp server, there are e.g. python
modules for that.
But why would we need one?!
The clients would be able to send requests for files like:
So what are the benefits of that?
* New lts.conf mechanism, which is even compatible with old clients,
and may make parts of getltscfg-cluster unneeded.
Our tftp daemon would get the client info, evaluate whatever we have
in /etc/ltsp/lts.conf.d, and send whatever we want to the client,
either a simple sourceable shell file, or an old-style lts.conf.
* Merge ldminfod code in the same daemon.
* Remove the need for complicated mechanisms to generate fancy
pxelinux.cfg/default files with support for menus etc, as those can
be generated dynamically from the server which has all the needed
info (are we using NFS? NBD?).
Also we can put client-specific kernel command line parameters
in our /etc/ltsp/lts.conf.d!
* We can also configure in our lts.conf.d whatever kernel/vmlinuz we
want to send to each client, no need to configure it in dhcpd
In short, it will allow to merge our lts.conf / lts-cfg-cluster /
ldminfod / pxelinux.cfg / <some>dhcpd / tftpd configuration.
ltsp-cluster selected http for some of those tasks, but we need tftp
for the kernel, pxelinux etc anyway, so tftp gives us much more
Sounds OK? :)