Single terminal session

Here is a typical and simple session with a server and only one terminal :

  1. The server is up and offers DHCP, TFTP (PXE), NBD and HTTP services ;
  2. A terminal is powered ;
  3. The BIOS terminal has been configured to try a networked boot via PXE ;
  4. The DHCP daemon responds and gives the terminal an IP address and a TFTP path to retrieve stuffs needed for boot (kernel and ramdisk) ;
  5. The terminal loads via TFTP the kernel and the ramdisk ;
  6. The kernel is executed on the terminal ;
  7. The ramdisk in uncompressed in RAM and the boot process continues on the terminal ;
  8. The root (/) partition is mounted read-only via the NBD daemon ; This partition contains the whole LTLJ terminal image with all games and applications (several Gb) ;
  9. A read-write partition is created in RAM and mounted with union fs onto the root partition to give full local read-write accesses to the terminal ;
  10. The control is passed to some LTLJ scripts ;
  11. The terminal configuration file (where you set role for each terminal) is downloaded to the client via TFTP or SSH ;
  12. The terminal look for its current role in the config file (OpenArena for this example)
  13. A X window server is created on the terminal ;
  14. A welcome application (termnav) is launched ;
  15. The user strikes a key on the terminal ;
  16. termnav launches the game OpenArena ;
  17. The user frags many bots ;-) ;

Change role session

\### TODO

Several terminals with a game server

\### TODO

Terminal abnormal usage

\### TODO
\### game quit, hard reboot,

Terminal registering

\### TODO
\### how to register a new terminal for LTLJ use