[K12OSN] No reaction following lts.conf changes

[Radek Bursztynowski]

Sorry for big avalanche of my questions, but K12Linux is very important
to me, and I must manage new version K12.

My few next  doubts.

Using chroot mechanism I try to manage several thin client images.
/opt/ltsp/i386 and /var/lib/tftpboot/ltsp/i386 directories belong to
epel-6-i386 ltsp-build-client (LTSP 5.9)

/opt/ltsp/i386-fed14 and /var/lib/tftpboot/ltsp/i386-fed14 belong to
Fedora 14 image which I restored from my backup LTSP 5.1. I note that
original /opt/ltsp/i386-fed14/etc/ltsp_chroot file encloses
LTSP_CHROOT=/opt/ltsp/i386 line, not LTSP_CHROOT=/opt/ltsp/i386-fed14
while I expected that ltsp-build-client --release 14 --chroot i386-fed14
create LTSP_CHROOT=/opt/ltsp/i386-fed14, not LTSP_CHROOT=/opt/ltsp/i386
line. But everything worked fine with LTSP 5.1.

The question is: which line is regular?

And the second doubt.

/opt/ltsp/i386-fed14/etc/sysconfig/mkinitrd file encloses

rootdev="192.168.0.254:/opt/ltsp/i386"

Still /opt/ltsp/i386 directory, not /opt/ltsp/i386-fed14

and rootdev is 192.168.0.254 while 192.168.0.254 is my network gateway,
not my server IP address. My server address is 192.168.0.1

The question is: which line is regular:
rootdev="192.168.0.254:/opt/ltsp/i386"
or
rootdev="192.168.0.1:/opt/ltsp/i386-fed14" ?

I checked /opt/ltsp/i386/etc/sysconfig/mkinitrd (epel-6-i386) and this
line is: 
rootdev="server:/opt/ltsp/i386"

I expect that "server" is variable which we can describe in lts.conf
like: SERVER=192.168.67.1. Isn't it?
So ltsp-build-client with LTSP 5.9 cleates regular rootdev line. Isn't
it?

Best regards,
Radek

----
> Radek,
> 
> rename your /opt/ltsp to /opt/ltspOLD
> rename /var/lib/tftpboot to /var/lib/tftpbootOLD
> Do a fresh ltsp-client-build
> You will have to copy /var/lib/tfpbootOLD/pxelinux.0  & pxelinux.cfg to
> your new  /var/lib/tftpboot/i386
> 
> Also I have experinced the login hit and miss with updateding,,
> What that is,,if you installed icedtea-web for 'java-plugin' this is not
> leaving an 'netx/lock file in the /tmp dir this resolves the prob until
> a client is rebooted and the same user logs in two times???
> 
> Barry
> 
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>