On Mon, Nov 26, 2007 at 12:51:25PM +0100, Oliver Grawert wrote: > the first hook after bringing up all devices grabs either 'nbdroot' or > 'nbdport' from the kernel commandline or falls back to port 2000 and the > rootserver variable from dhcp to establish the nbd connection and get > the squashfs image from the server.
Is the entire image fetched over the wire? Or is it more like mounting the file system? > after this step it checks if there is an lts.conf is available in the > tftp dir. And on my Gutsy setup powerpc and i386 on not consistent on where that file is loaded (one in tfpt root and the other in ltsp/<arch>/. I still want to track that down. > hope thats enough step by step :) if you need info about later stuff > look at /etc/init.d/ltsp-client-setup (excecuted in rcS.d) and > /etc/init.d/ltsp-client-core (excecuted in rc2.d) they run various > configuration scripts and start various ltsp related services (pulse for > the virtual alsa device in the users session, the ltspfs bits, x > configuration, ldm, etc ...) It would be nice if starting the related services were in separate scripts. For example, I'm having problems with starting Pulse on a specific type of client so it would be handy to be able to run a separate init.d script for just that service. -- Bill Moseley [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _____________________________________________________________________ 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.freenode.net
