Warren,Then it should say on the site " no developer wants to do the work".Now it says K12Linux is legacy.And Warren, I am grateful for the work that you put in for K12Linux.What I'm saying here, and I think what Radek is saying, is it's not legacy, It works.Legacy doesn't mean it doesn't work. It simply means no further development will be done for that particular setup. Sometimes a program becomes legacy because no one is working on it. Sometimes because it get superseded by newer projects.K12Linux on CentOS 6 is a great tool. But porting it to be fully CentOS 7 ready will require development from people other than Warren. K12Linux will be around for many more years since CentOS 6 will be around as well.
I think it's time to look at alternate methods of achieving a similar result. The PXE boot aspect will need to stay but the server platform needs to be revisited. The IT world has embraced virtual machines. Maybe a thin client should be running a VM client that provides console to a remote VM running on a server farm. The spice client is remarkably light and can push screen bits as well if not better than NX and RDP (and way faster than X over SSH or VNC). Using a management tool like Ovirt would allow tech support to build and maintain student machines as pool devices and thus only require updates to a single machine. Some coding is required to provide a single sign on screen that would connect to the next available VM console (which then auto-mounts the students home directory). The VM client (spice) can be 32 bit as well as 64 so it will run on older client hardware and it supports USB pass through for thumb drives. Sound also works.3 years ago I was doing a demo talk of Ovirt and connected through 2 layers of VPNs back to my work lab to show both windows and Linux desktops. I started a browser and went to YouTube and the flash video played smoothly and with sound synched to the video.As KVM, the technology behind Ovirt virtual machines, supports "memory ballooning", different VMs that need to use the same block of memory can share the block (read only - best for OS and application memory) and thus can perform similar types of resource sharing that K12Linux provided. Best of all, each user is truly isolated from all the others so an application crash (ahem - flash) will only affect the single user even with shared memory.