Dev:Compliance

For a distribution to be LTSP Compliant, it is proposed that they must support the following. This list is pretty old (conceived in the pre 5.0 era I think). I put an active discussion on the Talk page.


 * 1) Booting thin clients via PXE and Etherboot
 * 2) Local devices using LTSPFS
 * 3) Network transparent multimedia (audio and video)
 * 4) Screen scripts, including XDMCP, ldm/sdm, rdesktop, telnet, shell
 * 5) Booting thin clients with as little as 32mb of system ram
 * 6) Use of LTSP scripts and utilities (getltscfg, et al)
 * 7) Passing of VCI string from the client to the server (in initramfs)
 * 8) Transparent pass-through printing
 * 9) Network swapping (NBD is the current implementation, but other methods may include iSCSI or NFS)
 * 10) Ability to specify location of the LTSP chroot tree (default location: /opt/ltsp)
 * 11) Ability to control options per workstation using "lts.conf".

Future requirements still under consideration:


 * 1) remote shutdown
 * 2) Network authentication
 * 3) Bidrectional communication between client and server
 * 4) LTSP-defined local application framework
 * 5) Support for "diskless PC" mode (entire session is run on the thin client)

Many of the items in the above 2 lists are either being developed now, or are planned for the future. The list isn't cast in stone and we're definitely interested in feedback.