Re: [Ltsp-discuss] wrong lts.conf used with more than one chroot

[Alkis G. <al...@gm...>]

Στις 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.

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".

$CHROOT/usr/share/ltsp/init-ltsp.d/05-getltsconffile searches for 
lts.conf in the same place where pxelinux.0 (dhcp boot filename) was 
downloaded from.

So ipappend 3 makes it impossible to have multiple lts.conf files, at 
least without patching the kernel command line or the chroot, and 
05-getltscconffile a bit.
E.g. a patch could be to modify 
/usr/share/initramfs-tools/scripts/init-premount/udhcp so that it uses 
the nbd parameter in the kernel command line to initialize "boot 
filename", when it's empty.