Dev:Compliance
From LTSPedia
| This article, like all articles in the Dev namespace can only be edited by LTSP developers. |
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.
- Booting thin clients via PXE and Etherboot
- Local devices using LTSPFS
- Network transparent multimedia (audio and video)
- Screen scripts, including XDMCP, ldm/sdm, rdesktop, telnet, shell
- Booting thin clients with as little as 32mb of system ram
- Use of LTSP scripts and utilities (getltscfg, et al)
- Passing of VCI string from the client to the server (in initramfs)
- Transparent pass-through printing
- Network swapping (NBD is the current implementation, but other methods may include iSCSI or NFS)
- Ability to specify location of the LTSP chroot tree (default location: /opt/ltsp)
- Ability to control options per workstation using "lts.conf".
Future requirements still under consideration:
- remote shutdown
- Network authentication
- Bidrectional communication between client and server
- LTSP-defined local application framework
- 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.
