On 2015-01-31, Nicolas LEBRUN wrote: > I'm trying to build a ltsp-server as versatile as possible (old kernel > or not, fat or not...) because clients can be very different... We > have actually about 20 servers on Wheezy with NFS chroots with no fat. ... > And i have many questions > > - NBD seems to be really stable. The only advantage of NFS seems to > be able to modify chroot in real time... What do you think ?
I find NFS to be more resilient in case of brief network outages, where NBD seems more prone to hang. With LTSP on Debian wheezy or jessie, you should be able to switch between NBD and NFS at boot time by configuring the menu options in update-kernels.conf: PXELINUX_DEFAULT=menu #PXELINUX_DEFAULT=vesamenu # 10 second timeout: TIMEOUT=100 ONTIMEOUT=ltsp-ifcpu64-NFS #ONTIMEOUT=ltsp-ifcpu64-NBD IFCPU64=true BOOT_METHODS="NFS NBD" If you need to switch between Jessie ltsp-pnp and wheezy chroots, you'll need to manually generate your own PXE configuration to select between the various options. > - I can't login in gnome flashback when the client is not fat... > Apparently because there is no 3D acceleration... What can I do ? If it works fine on fat clients, I suspect it's an issue with running at 16-bit color depth (the default for thin clients). Experiment with setting X_SMART_COLOR_DEPTH=false in lts.conf: https://bugs.debian.org/705143 > - In my virtualbox, i can't try ltsp-pnp ... ltsp-update-image > --cleanup / remain stuck. Is it possible to have an ltsp-pnp in a > virtual machine (will surely be a kvm) ? No idea with virtualbox. I've mostly been testing using libvirt with KVM, and haven't experienced problems like that. > - Can ltsp-pnp have many kernels ? 586, 686-pae and amd64 ? Yes, though you'll need to install the server as i386 instead of amd64, but you can run the amd64 kernel to gain (most of) the benefits of 4GB+ ram. You'll want to make sure the initramfs for all kernel versions get updated, edit /etc/initramfs-tools/update-initramfs.conf: update_initramfs=all > At the moment, i install everything in a Jessie virtualbox... with the > script attached (thks Richard K and Vagrant C) That script is probably more invasive than it needs to be; there are several options (dnsmasq, /etc/exports) to write to .d dirs instead of overwriting the whole configuration file, which will result in easier upgrades, and also preserve the original comments in the configuration files. Running both "ltsp-config dnsmasq --overwrite" and then manually overwriting /etc/dnsmasq.d/ltsp-server-dnsmasq.conf is a bit redundant. :) live well, vagrant
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_____________________________________________________________________
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
