Hi, Your step by step description is not really what the folks at Ubuntu had in mind with their attempt at "hands-off", quick start installation.
So I can now say that my process is stopping before it gets the initramfs via TFTP! Why? I am none the wiser at this point. Ciao Joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Oliver Grawert Sent: Monday, November 26, 2007 12:51 PM To: ltsp-discuss@lists.sourceforge.net Subject: Re: [Ltsp-discuss] Problem booting client (Ubuntu 7.10 AMD 64 bit) hi, On So, 2007-11-25 at 16:34 +0000, Joseph Gregory wrote: > > > > > > Don't quite know where to continue the debugging. It would be > > > really good to have a step by step list of what happens after DHCP > > > request has been accepted and IP address assigned to client. > > well, after the first DHCP request the client connects to the server (by default the dhcp server in ubuntu if next-server isnt set in dhcpd.conf (note that next-server is needed in other distros)) it retrieves the initramfs via tftp, unpacks it and runs the different hooks in there. 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. then it creates a writeable tmpfs and merges that with the readonly squashfs in a unionfs stack, this stack gets mounted as /root which at the end of the bootprocess in initramfs will become / through the run-init program's root switching mechanism. after this step it checks if there is an lts.conf is available in the tftp dir. if so, it downloads it and copies it in place. (if someone wants to come up with an optional ldap backend for that which reads the config out of initramfs that would be very appreciated btw ;) ) at this stage run-inits kicks in, switches /root to / and runs /bin/init (actually that binary upstart in ubuntu) on the actual system root. 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 ...) ciao oli ************************************************************************************************** E-mail Confidentiality Notice and Disclaimer. This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. E-mail messages are not necessarily secure. Hitachi does not accept responsibility for any changes made to this message after it was sent. Hitachi checks outgoing e-mail messages for the presence of computer viruses. ************************************************************************************************** ------------------------------------------------------------------------- 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
