"For the future, it is planned that LTSP chroots will be bootable read-write..."
This would be useful. The issue for us isn't so much the graphics, but, for certain circumstances, in being able to have the programs see the client hardware at installation (e.g., virtualbox or nvidia drivers from sources). I realize this conversation is about fat clients, and I'm interested in thin clients. If that makes a difference to what I'm about to say, let me know. I didn't know about the speed issue in the mounted chroot. Our situation is all about speed, so that matters a lot. But, we don't want everyone to have to stop working and reboot their clients every time someone installs a new program. I think you explained it, but I don't understand how you can make changes to the client's chroot visible to the running client. For example: [client] ltsp-localapps xterm [client, xterm] ls /opt ...(shows empty) [server] echo "hello" > /opt/ltsp/i386/opt/hello.txt [client, xterm] ls /opt ...(still shows empty) How can I make changes visible on the fly like that? This is why I went to using the extra mounts for the other installed programs. :-) L On Mon, Jan 2, 2012 at 11:41 AM, Alkis Georgopoulos <[email protected]> wrote: > Στις 02-01-2012, ημέρα Δευ, και ώρα 11:29 -0500, ο/η Todd O'Bryan > έγραψε: >> You'd also be able to install a new program or make a tweak without >> having to rebuild the image and restart the clients, wouldn't you? > > Not to my knowledge. Run `dpkg -L firefox` and see where the "firefox" > package puts its files. All over the file system. I don't think there's > any easy way to expose all those directories to the clients, AND to > rebuild any icon/menu/whatever caches dynamically, etc etc. > Maybe the /usr/local/* dirs can be utilized for this, but I doubt it > would be painless. > >> I also still haven't figured out a good way to install/update programs >> that use a GUI installer/update. Especially annoying are Eclipse >> plugins > > If they're per-user plugins, they get installed > in /home/username/.something, so you just install them normally from a > user account. > If they're per-system plugins, and no .deb packages exist for them, just > mount --bind whatever dirs you need from the server to your chroot, and > run that program while chrooted. You do have X access there, I don't > suppose eclipse requires anything more fancy like system dbus to install > plugins, does it? > > For the future, it is planned that LTSP chroots will be bootable > read-write from a client or from a virtual machines, so that one can > administer the chroot graphically (e.g. with virtualbox). > > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > _____________________________________________________________________ > 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 -- :-) Lachele Lachele Foley CCRC/UGA Athens, GA USA ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _____________________________________________________________________ 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
