Alkis Georgopoulos wrote: > Στις 25/04/2013 04:30 μμ, ο/η Thomas Boehm έγραψε: >> ipappend 3 >> ------------------------------------------------------------------- >> >> I prefer the second configuration, as it works around the bug(?) of the >> disappearing "ipappend 3" line on every ltsp-update-image... > > > First, to tell LTSP to include ipappend 3, you put > IPAPPEND=3 > in $CHROOT/etc/ltsp/ltsp-client.conf.
$CHROOT/etc/ltsp/ltsp-client.conf didn't exist, so I created one. Then I added IPAPPEND=3 and later ipappend 3 instead, after it didn't work. When running ltsp-update-image --arch ... nothing gets added to pxelinux.cfg/default > Second, ipappend 3 tells pxelinux to include the IP from PXE to the > kernel command line, > and then udhcpc in the client initramfs reuses it, without doing the > usual second DHCP request. > The downside there is that the initramfs doesn't know about the "boot > filename", which usually is "/ltsp/i386/pxelinux.0", or, in your case, > could also be "/ltsp/fatclient/pxelinux.0". > ... Thanks for the explanation. So if I really go ahead with two chroots, I just need to use one lts.conf. ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _____________________________________________________________________ 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
