I had something of a surprise today. I had to shut down my server to go boot Windows. Terrible...
When I re-booted, I checked on my terminal. Nothing there, unsurprisingly. I gave it a bit of time, and KDM re-appeared a few minutes later. Upon logging in, I found everything working perfectly, including sound. That really surprised me. I figured I'd have to re-start the terminal for sound if nothing else, to re-establish whatever nebulous connection it has with the server that makes that bit of magic possible. How is it that rebooting the server didn't break any connections between it ant the terminal? I don't have a deep understanding of a lot of this stuff because it just works. No need to learn when installation is as easy as 1-2-3. :) The folks putting these packages together have done a marvelous job! However, because it works, I haven't had to dig into it, and I've missed out on the discovery process. So, I'm curious... How is it possible that the terminal is still working? How can that be? Didn't it mount the /opt/ltsp/i386 directory as / by way of NFS? Didn't I break that share by rebooting the server? It's all just very fascinating, really. I'm continually surprised by how robust and maintenance free this whole setup has been. -- Michael McIntyre zone 6b in SW VA Silvan Pagan umount /mnt/windows;mke2fs /dev/hde1;tune2fs -j /dev/hde1 www.geocities.com/Paris/Rue/5407/index.html ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
