Re: [Ltsp-discuss] Debian Jessie amd64 using nbd i386 client
On 2014-08-15, richard kweskin wrote: > In /etc/ltsp/update-kernels.conf the line > > LIST_KERNELS_DEFAULT="486" > > is for older clients and > > LIST_KERNELS_DEFAULT="686-pae" > > is for capable clients. > > Is the one line appropriate for all the clients so that one must put > the lowest common need? No need to set LIST_KERNELS_DEFAULT, as that sets the default for all clients, and effectively defaults to 486, as it uses LIST_KERNELS_32 in preference to other kernels. LIST_KERNELS_DEFAULT is only useful if you want to override the default, such as with a custom kernel with a different variant name. I would recommend using autodetection, if you have an environment with mixed clients: ltsp-chroot --arch=i386 apt-get install linux-image-amd64 linux-image-686-pae linux-image-486 Add to update-kernels.conf: # Use ifcpu64.c32 to detect 64-bit, PAE or 32-bit machines. PXELINUX_DEFAULT=ltsp-ifcpu64-NBD IFCPU64=true Then it will pick the appropriate kernel at boot. Adjust PXELINUX_DEFAULT to use NFS, NBD, or AOE as appropriate for your configuration. This may give you some small performance improvements on clients with hyperthreading or multiple cores, at the cost of a little more disk space used having multiple kernels. live well, vagrant pgpAFPGxDdcOZ.pgp Description: PGP signature -- _ 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
Re: [Ltsp-discuss] Debian Jessie amd64 using nbd i386 client
On 2014-08-14 19:01, Vagrant Cascadian wrote: snip > The -486 kernel only supports a single CPU. You'll want either a > -686-pae > or -amd64 kernel running on your server. > > If you're using ltsp-pnp, you'll want to install both the > linux-image-486 and linux-image-686-pae and/or linux-image-amd64 > packages. You may want to explore the IFCPU64 detection features in > update-kernels.conf, so that thin clients run the appropriate kernel > at > boot time. > > live well, > vagrant In /etc/ltsp/update-kernels.conf the line LIST_KERNELS_DEFAULT="486" is for older clients and LIST_KERNELS_DEFAULT="686-pae" is for capable clients. Is the one line appropriate for all the clients so that one must put the lowest common need? Richard -- _ 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
Re: [Ltsp-discuss] Debian Jessie amd64 using nbd i386 client
On 2014-08-14 18:55, Vagrant Cascadian wrote: > On 2014-08-14, richard kweskin wrote: > >> 9 patched /usr/share/ltsp/update-kernels (using >> >> >> http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2569 >> >> >> http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2570 >> ) >> >> 10 aptitude install pxelinux > > These two steps are completely unnecessary for a thin client install > with ltsp-build-client. > > If you were doing the ltsp-pnp method, you would only need them with > an > older version of ltsp, as 5.5.2-1 is now in Debian Jessie and has the > dependency on pxelinux and patch for update-kernels to use the newer > pxelinux package. > > >> 14 patched /opt/ltsp/i386/usr/share/ltsp/update-kernels (using >> >> >> http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2569 >> >> >> http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2570 >> ) > > This step should no longer be needed with ltsp 5.5.2-1, which is now > in > Debian Jessie. > >> 16 apt-get install pxelinux && apt-get clean && exit (aptitude is >> not >> installed in the chroot) > > This step should no longer be needed with ltsp 5.5.2-1, which is now > in > Debian Jessie. > > > live well, > vagrant Once again,thank you for this clarification. For the purpose of writing up documentation for others I now put the steps: These are needed for installing ltsp with a separate chroot for clients as the server is configured for amd64 architecture and some or all clients need i386. Valid for ltsp 5.5.1-1 and 5.5.2-1 1 install dnsmasq ltsp-server-standalone lxde only with ltsp-pnp put ltsp-client on the server 2 add loop to /etc/modules and reboot the server (reported at https://bugs.debian.org/756990) 3 ltsp-config dnsmasq 4 edit /etc/dnsmasq.d/ltsp-server-dnsmasq.conf to comment out dhcp range line leaving dhcp proxy if the server has just one nic or edit (if needed) the dhcp range line to suit the subnet with clients 5 edit /etc/dnsmasq.d/ltsp-server-dnsmasq.conf to replace all instances of amd64 with i386 6 service dnsmasq restart 7 edit etc/ltsp/ltsp-server.conf to have ARCH="i386" and DIST="jessie" 8 edit /etc/ltsp/ltsp-build-client.conf to have ARCH="i386" and DIST="jessie" 9 aptitude update && aptitude -y full-upgrade && aptitude clean 10 ltsp-build-client (without parameters) 11 edit /opt/ltsp/i386/etc/ltsp/update-kernels.conf to have BOOT_METHODS=NBD, ARCH="i386" and IPAPPEND=3 uncommented If using ltsp 5.5.1-1 or older then steps 12, 13 and 14 are needed. If ltsp 5.5.2-1 or newer then skip them. 12 patched /opt/ltsp/i386/usr/share/ltsp/update-kernels (using http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2569 http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2570 ) 13 ltsp-chroot -rm 14 apt-get install pxelinux && apt-get clean && exit (aptitude is not installed in the chroot) 15 ltsp-chroot --arch i386 /usr/share/ltsp/update-kernels 16 ltsp-update-kernels (this puts pxelinux.0 and pxelinux.cfg and the latest i386 kernel into /var/lib/tftpboot/ltsp/i386/) 17 ltsp-update-image (without parameters) 18 ltsp-config nbd-server 19 service nbd-server restart May you all live well Richard -- _ 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
Re: [Ltsp-discuss] Debian Jessie amd64 using nbd i386 client
On 2014-08-14, richard kweskin wrote: > was creating the squashfs image in amd64 but for clients in i386 it was > using 2 processors and of course took less time, but in the earlier > configuration in i386 it used only one processor. ... > Is it possible that some hardware only has access to both processors in > 64 bit mode where other hardware can also do it in i386? Is it the > choice of kernel? 3.14-2-amd64 now and 3.14-2-486 before? The -486 kernel only supports a single CPU. You'll want either a -686-pae or -amd64 kernel running on your server. If you're using ltsp-pnp, you'll want to install both the linux-image-486 and linux-image-686-pae and/or linux-image-amd64 packages. You may want to explore the IFCPU64 detection features in update-kernels.conf, so that thin clients run the appropriate kernel at boot time. live well, vagrant pgpcpTf0fVtkq.pgp Description: PGP signature -- _ 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
Re: [Ltsp-discuss] Debian Jessie amd64 using nbd i386 client
On 2014-08-14, richard kweskin wrote: > 9 patched /usr/share/ltsp/update-kernels (using > > http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2569 > > http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2570 > ) > > 10 aptitude install pxelinux These two steps are completely unnecessary for a thin client install with ltsp-build-client. If you were doing the ltsp-pnp method, you would only need them with an older version of ltsp, as 5.5.2-1 is now in Debian Jessie and has the dependency on pxelinux and patch for update-kernels to use the newer pxelinux package. > 14 patched /opt/ltsp/i386/usr/share/ltsp/update-kernels (using > > http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2569 > > http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2570 > ) This step should no longer be needed with ltsp 5.5.2-1, which is now in Debian Jessie. > 16 apt-get install pxelinux && apt-get clean && exit (aptitude is not > installed in the chroot) This step should no longer be needed with ltsp 5.5.2-1, which is now in Debian Jessie. live well, vagrant pgp7PnN7dZJi_.pgp Description: PGP signature -- _ 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
Re: [Ltsp-discuss] Debian Jessie amd64 using nbd i386 client
On 2014-08-14 13:35, richard kweskin wrote: > On 2014-08-13 18:58, Vagrant Cascadian wrote: >> On 2014-08-13, richard kweskin wrote: >>> On 2014-08-13 02:04, Vagrant Cascadian wrote: On 2014-08-12, richard kweskin wrote: snip > I agree. However, there are cases in which the above method is used. > I > am only testing different cases and because you have been so > forthcoming > I can now write up some documentation both in Greek and in English. snip Using the steps below the client boots successfully: 1 install dnsmasq ltsp-server-standalone lxde 2 add loop to /etc/modules and reboot the server (reported at https://bugs.debian.org/756990) 3 ltsp-config dnsmasq 4 edit /etc/dnsmasq.d/ltsp-server-dnsmasq.conf to comment out dhcp range line leaving dhcp proxy if the server has just one nic or edit (if needed) the dhcp range line to suit the subnet with clients 5 edit /etc/dnsmasq.d/ltsp-server-dnsmasq.conf to replace all instances of amd64 with i386 6 service dnsmasq restart 7 edit etc/ltsp/ltsp-server.conf to have ARCH="i386" and DIST="jessie" 8 edit /etc/ltsp/ltsp-build-client.conf to have ARCH="i386" and DIST="jessie" 9 patched /usr/share/ltsp/update-kernels (using http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2569 http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2570 ) 10 aptitude install pxelinux 11 aptitude update aptitude full-upgrade aptitude clean 12 ltsp-build-client (without parameters) 13 edit /opt/ltsp/i386/etc/ltsp/update-kernels.conf to have BOOT_METHODS=NBD, ARCH="i386" and IPAPPEND=3 uncommented 14 patched /opt/ltsp/i386/usr/share/ltsp/update-kernels (using http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2569 http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2570 ) 15 ltsp-chroot -rm 16 apt-get install pxelinux && apt-get clean && exit (aptitude is not installed in the chroot) 17 ltsp-chroot --arch i386 /usr/share/ltsp/update-kernels 18 ltsp-update-kernels (this puts pxelinux.0 and pxelinux.cfg and the latest i386 kernel into /var/lib/tftpboot/ltsp/i386/) 19 ltsp-config nbd-server 20 service nbd-server restart 21 ltsp-update-image (also without parameters) Please help in marking this thread solved. Richard -- _ 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
Re: [Ltsp-discuss] Debian Jessie amd64 using nbd i386 client
On 2014-08-13 18:58, Vagrant Cascadian wrote: > On 2014-08-13, richard kweskin wrote: >> On 2014-08-13 02:04, Vagrant Cascadian wrote: >>> On 2014-08-12, richard kweskin wrote: > 5 edit /etc/ltsp/update-kernels.conf to have BOOT_METHODS=NBD, ARCH="i386" and IPAPPEND=3 uncommented 8 patched /usr/share/ltsp/update-kernels 9 aptitude install pxelinux >>> steps 5, 8 and 9, except in the chroot, followed by: >>> >> >> Thank you once again for all your help. In your above remark >> concerning >> steps 5, 8 and 9 do you mean that these steps are to be done both on >> the >> server's setup and on the client's chroot or to be done only on the >> client's chroot. > > Only in the client's chroot, for a setup using ltsp-build-client and > a > separate chroot, and all the client's files come from that chroot. Ah, ok. I will eliminate some steps then. > I think your earlier install was an amd64 using the ltsp-pnp method, > which needs a largely different set of instructions, since all the > client's files come from the server install. It was with i386 and ltsp-pnp. > In general, I would recommend using ltsp-pnp at this point for fat > clients or localapps; it's a much simpler configuration, with only > one > place to edit all files. > > In my opinion, ltsp-pnp is probably the best innovation in LTSP since > the switch to LTSP5. I agree. However, there are cases in which the above method is used. I am only testing different cases and because you have been so forthcoming I can now write up some documentation both in Greek and in English. > > live well, > vagrant fyi : when this same box Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:15 Model: 4 Stepping: 3 CPU MHz: 2800.000 BogoMIPS: 6400.16 L1d cache: 16K L2 cache: 2048K NUMA node0 CPU(s): 0,1 was creating the squashfs image in amd64 but for clients in i386 it was using 2 processors and of course took less time, but in the earlier configuration in i386 it used only one processor. In contrast at several schools where I have gone to help them setup they have had i3 or i5 cpu's and although we setup the server in i386 so that ltsp-pnp was used the server utilized all 4 processors to create the image as expected. Is it possible that some hardware only has access to both processors in 64 bit mode where other hardware can also do it in i386? Is it the choice of kernel? 3.14-2-amd64 now and 3.14-2-486 before? Richard -- _ 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
Re: [Ltsp-discuss] Debian Jessie amd64 using nbd i386 client
On 2014-08-13, richard kweskin wrote: > On 2014-08-13 02:04, Vagrant Cascadian wrote: >> On 2014-08-12, richard kweskin wrote: >>> 5 edit /etc/ltsp/update-kernels.conf to have BOOT_METHODS=NBD, >>> ARCH="i386" and IPAPPEND=3 uncommented >>> 8 patched /usr/share/ltsp/update-kernels >>> 9 aptitude install pxelinux >> steps 5, 8 and 9, except in the chroot, followed by: >> > > Thank you once again for all your help. In your above remark concerning > steps 5, 8 and 9 do you mean that these steps are to be done both on the > server's setup and on the client's chroot or to be done only on the > client's chroot. Only in the client's chroot, for a setup using ltsp-build-client and a separate chroot, and all the client's files come from that chroot. I think your earlier install was an amd64 using the ltsp-pnp method, which needs a largely different set of instructions, since all the client's files come from the server install. In general, I would recommend using ltsp-pnp at this point for fat clients or localapps; it's a much simpler configuration, with only one place to edit all files. In my opinion, ltsp-pnp is probably the best innovation in LTSP since the switch to LTSP5. live well, vagrant pgppHVsOdwElD.pgp Description: PGP signature -- _ 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
Re: [Ltsp-discuss] Debian Jessie amd64 using nbd i386 client
On 2014-08-13 02:04, Vagrant Cascadian wrote: > On 2014-08-12, richard kweskin wrote: snip >> 5 edit /etc/ltsp/update-kernels.conf to have BOOT_METHODS=NBD, >> ARCH="i386" and IPAPPEND=3 uncommented snip >> 8 patched /usr/share/ltsp/update-kernels >> 9 aptitude install pxelinux snip > ltsp-build-client > > steps 5, 8 and 9, except in the chroot, followed by: > Thank you once again for all your help. In your above remark concerning steps 5, 8 and 9 do you mean that these steps are to be done both on the server's setup and on the client's chroot or to be done only on the client's chroot. > ltsp-chroot --arch i386 /usr/share/ltsp/update-kernels > ltsp-update-kernels Thank you again, I will add these steps also. snip >> /etc/dnsmasq.d/ltsp-server-dnsmasq.conf contains: >> >> dhcp-boot=net:pxe,/ltsp/amd64/pxelinux.0 >> dhcp-boot=net:etherboot,/ltsp/amd64/nbi.img >> dhcp-boot=net:ltsp,/ltsp/amd64/lts.conf > > You'll need to edit this to use i386, as well as the pxelinux entry > further down in ltsp-server-dnsmasq.conf. And again, this step will be added.. snip > That's because of the above mentioned issues- you edited the server's > files, not the chroot's files. > > If your server was also an i386 install, you could do this using the > ltsp-pnp method, and it would be a little simpler. > > > live well, > vagrant May you also live well. Richard -- _ 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
Re: [Ltsp-discuss] Debian Jessie amd64 using nbd i386 client
On 2014-08-12, richard kweskin wrote: > Following the sucess with Jessie i386 I tried many of the same steps > with an installation already in use without ltsp. > > The steps: > > 1 install dnsmasq ltsp-server-standalone ltsp-client lxde No need to install ltsp-client on the server unless you're going to use ltsp-pnp (i.e. no ltsp-build-client, but building out of the server install with "ltsp-update-image --cleanup /"). > 2 add loop to /etc/modules and reboot the server > 3 ltsp-config dnsmasq and edit to comment out dhcp range line leaving > dhcp proxy since server has just one nic > 4 service dnsmasq restart > 5 edit /etc/ltsp/update-kernels.conf to have BOOT_METHODS=NBD, > ARCH="i386" and IPAPPEND=3 uncommented You'd need to edit update-kernels.conf in the chroot, after ltsp-build-client... > 6 edit etc/ltsp/ltsp-server.conf to have ARCH="i386" and DIST="jessie" > 7 edit /etc/ltsp/ltsp-build-client.conf to have ARCH="i386" and > DIST="jessie" > 8 patched /usr/share/ltsp/update-kernels You would need to patch update-kernels in the chroot, which would need to happen after ltsp-build-client... > 9 aptitude install pxelinux You would need to install pxelinux in the chroot, which would need to happen after ltsp-build-client... > 10 aptitude update aptitude full-upgrade aptitude clean > 11 ltsp-build-client-image (without parameters) ltsp-build-client steps 5, 8 and 9, except in the chroot, followed by: ltsp-chroot --arch i386 /usr/share/ltsp/update-kernels ltsp-update-kernels > 12 ltsp-update-image (also without parameters) > 13 ltsp-config nbd-server > 14 service nbd-server restart ... > As the server has the architecture amd64, > > /etc/dnsmasq.d/ltsp-server-dnsmasq.conf contains: > > dhcp-boot=net:pxe,/ltsp/amd64/pxelinux.0 > dhcp-boot=net:etherboot,/ltsp/amd64/nbi.img > dhcp-boot=net:ltsp,/ltsp/amd64/lts.conf You'll need to edit this to use i386, as well as the pxelinux entry further down in ltsp-server-dnsmasq.conf. > I didn't touch it but it expects pxelinux.0 to be in > /var/lib/tftpboot/ltsp/amd64/ but it isn't there. > Neither is it in /var/lib/tftpboot/ltsp/i386/ That's because of the above mentioned issues- you edited the server's files, not the chroot's files. If your server was also an i386 install, you could do this using the ltsp-pnp method, and it would be a little simpler. live well, vagrant pgpo_aNIkGH1h.pgp Description: PGP signature -- _ 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
[Ltsp-discuss] Debian Jessie amd64 using nbd i386 client
Hello All Following the sucess with Jessie i386 I tried many of the same steps with an installation already in use without ltsp. The steps: 1 install dnsmasq ltsp-server-standalone ltsp-client lxde 2 add loop to /etc/modules and reboot the server 3 ltsp-config dnsmasq and edit to comment out dhcp range line leaving dhcp proxy since server has just one nic 4 service dnsmasq restart 5 edit /etc/ltsp/update-kernels.conf to have BOOT_METHODS=NBD, ARCH="i386" and IPAPPEND=3 uncommented 6 edit etc/ltsp/ltsp-server.conf to have ARCH="i386" and DIST="jessie" 7 edit /etc/ltsp/ltsp-build-client.conf to have ARCH="i386" and DIST="jessie" 8 patched /usr/share/ltsp/update-kernels 9 aptitude install pxelinux 10 aptitude update aptitude full-upgrade aptitude clean 11 ltsp-build-client-image (without parameters) 12 ltsp-update-image (also without parameters) 13 ltsp-config nbd-server 14 service nbd-server restart ltsp-info server information: No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux testing (jessie) Release:testing Codename: jessie server packages: ii ldm 2:2.2.14-1 ii ldm-server 2:2.2.14-1 un ldm-themes ii ltsp-client 5.5.1-1 ii ltsp-client-core 5.5.1-1 ii ltsp-docs 1.1-1 ii ltsp-server 5.5.1-1 un ltsp-utils ii ltspfs 1.3-1 ii ltspfsd 1.3-1 ii ltspfsd-core 1.3-1 packages in chroot: /opt/ltsp/i386 ii ldm 2:2.2.13-1 ii ldm-themes 12.07.1 ii ltsp-client 5.5.1-1 ii ltsp-client-core 5.5.1-1 ii ltspfsd 1.3-1 ii ltspfsd-core 1.3-1 found: /opt/ltsp/i386/etc/lts.conf found: /var/lib/tftpboot/ltsp/i386/lts.conf found image: /opt/ltsp/images/i386.img As the server has the architecture amd64, /etc/dnsmasq.d/ltsp-server-dnsmasq.conf contains: dhcp-boot=net:pxe,/ltsp/amd64/pxelinux.0 dhcp-boot=net:etherboot,/ltsp/amd64/nbi.img dhcp-boot=net:ltsp,/ltsp/amd64/lts.conf I didn't touch it but it expects pxelinux.0 to be in /var/lib/tftpboot/ltsp/amd64/ but it isn't there. Neither is it in /var/lib/tftpboot/ltsp/i386/ Also above we saw that /var/lib/tftpboot/ltsp/i386/lts.conf, not where dnsmasq was set to find it. Richard -- _ 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
