Re: [Ltsp-discuss] this workstation isn't authorized to connect to server]
On Thu, Oct 30, 2008 at 05:17:40PM -0400, bjc wrote: Each time I reboot my ltsp-server, ldm refuses to log users into the clients. I get the message this workstation isn't authorized to connect to server. is the server getting it's primary ip address via dhcp and getting a different address each time? could you possibly configure your server to get a static ip address? Others have mentioned this problem on this list and suggest running two commands to fix the situation; ltsp-update-sshkeys followed by ltsp-update-image -a i386. This works for me, but only until I reboot my server. The situation then starts happening again. ...snip... I'm running ltsp5 in debian lenny on a amd64 server with i386 cliants. you should only need to run ltsp-update-sshkeys on Debian (if you're using NFS, which is the default, NBD doesn't have a mechanism yet to update individual files without rebuilding the image). ltsp-update-image updates NBD images. though, that should happen automatically whenever you bring up your network interface, if you're configuring your network interfaces in /etc/network/interfaces. live well, vagrant - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ _ 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] why does Debian LTSP 5 use NFS?
On Thu, Nov 06, 2008 at 07:19:10AM -0500, Rob Owens wrote: This is not a complaint by any means, but I'm wondering what the reason is that Debian uses NFS for the chroot system when other distros have changed to NBD. And while I'm asking Debian questions, could someone let me know if I am correct here: since Debian does not use NBD, there is no need to update-ltsp-image after making changes to the chroot (like adding software). indeed! no need to run ltsp-update-image whenever you make changes to the chroot. it's simpler for chroot maintenance, which is largely why i've chosen to stick with NFS on Debian, at least for now. NFS has definitely stood the test of time; NBD is considerably newer in the world of LTSP. i'm glad folks working on other distros have lead the way in experimenting with something new. :) that said, NBD definitely has noticeably faster boot times. it's possible to use NBD with Debian lenny with --squashfs-image, --create-fs-image or --create-ext2-image options to ltsp-build-client, but not as well tested. Thanks. I'm using Lenny, by the way. glad to hear it! :) live well, vagrant - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ _ 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] different root filesystems for individual clients
On Fri, Nov 14, 2008 at 06:35:37PM +0100, Csillag Kristóf wrote: I am looking for an easy way to provide slightly different root file-systems for my LTSP clients under Debian. I would like to avoid creating separate installations, since only a few files need to be different. I assume there is already a mechanism in place in LTSP to replace (or cover) some files with dynamic content on boot. not really. there is the rw_dirs, copy_dirs, and bindfiles functionality in the thin-client's /etc/init.d/ltsp-client-setup, but that's not a per-machine thing. What would be the easiest way to extend this mechanism, so that several libraries and binaries can be diverted selectively, based on the client hostname? selectively diverying libraries and binaries sounds like a bad idea, in general, unless done using the package management tools... you could write a script using RCFILE_NN in lts.conf that does whatever crazy things you want, and it will be executed when /etc/init.d/ltsp-client-setup is run at boot. you might want to use the NBD+squashfs+aufs option (ltsp-build-client --squashfs-image), as aufs will make any file effectively writeable. this would allow you to install packages at boot time, for example. it isn't as well tested as the default behavior on Debian (NFS+bind mounts of selected files and directories). live well, vagrant - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ _ 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] [ltsp-discuss] Network clients stop responding for a while after 4 or 5 units boot up.
On Mon, Nov 17, 2008 at 05:19:36PM +0800, Mark David Dumlao wrote: Thanks Steve, I didn't know gPXE was universal because I only downloaded images from rom-o-matic. you can download a universal gPXE iso from rom-o-matic.net, just select the gpxe:all-drivers driver. why it isn't the default is beyond me. i haven't had luck with the gpxe:all-drivers floppy disk images from rom-o-matic.net, though. when building from source, i had luck with padded disk images (.pdsk) floppy images which aren't built by default. i've also got .deb packages of gPXE available at: http://llama.freegeek.org/~vagrant/debian/UNRELEASED/ that has various images in /usr/share/gpxe/ live well, vagrant - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ _ 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] Power Management for individual clients
On Mon, Dec 01, 2008 at 01:12:21PM +0200, Anton Vaaranmaa wrote: Thank you very much for your advice. My scripting skills are very modest to say at least, so I used the RCFILE_01 = script approach and in my script I put the hdparm -Y /dev/sda command. I can target the client(s)that need this by placing the RCFILE_01 variable under the section for the individual client(s) in lts.conf. However when I tested it I had no luck since the command did not get executed at all :-( When I execute my script manually in a shell it works. I did remember to do an ltsp-update-image after putting the script init /etc/init.d/. what exactly is in RCFILE_01? you need to use the full path: RCFILE_01 = /FULL/PATH/TO/script i.e. if you placed it in /etc/init.d, then RCFILE_01 = /etc/init.d/script are other lts.conf values being respected? where is your lts.conf file? live well, vagrant - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ _ 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] Ltsp-5 over Grub
On Fri, Dec 19, 2008 at 04:13:42PM +0530, Nataraj S Narayan wrote: This is some where in the middle of my Ltsp server on XP experiment. that doesn't sound very fun... :) I finally managed to get vmlinuz -2.6.26-1-486, initrd.img-2.6.26-1-486 and a i386.img (file system). For this I used Debian Lenny and installed ltsp-server package, and then ltsp-build-client --create-ext2-image. i haven't really tested this much since i wrote that feature... note that the --create-ext2-image option is a little different than the NBD image that ltsp-update-image creates (or --sqaushfs-image). it uses nbd-client's initramfs-tools hooks, and a plain ext2 filesystem, which can be tweaked by mounting the image. it was noticeably faster than NFS, too... I wish to boot the ltsp-kernel using grub and load the file system (i386.img) over the network from a server (which ever). I have copied the said files except i386.img to another debian lenny's /boot, and modified the menu.lst in /boot/grub and created a new title. But how do i specify the root fs? why not just network boot them? Normally it is 'root (hd0,0)' . How do i change it so that the i386.img gets loaded from 192.168.0.196:/opt/ltsp/image/ ? you'll need nbdrootd configured in /etc/inetd.conf: update-inetd --group LTSP --add 2000 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd the commandline arguments you'll need to pass, which should already be configured in /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default if you're using the typical network booting: root=/dev/nbd0 ip=dhcp boot=local nbdroot=192.168.0.196,2000 live well, vagrant -- _ 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] Compiling custom LTSP 5 kernel
On Fri, Dec 19, 2008 at 03:24:43PM -0800, Slawek Drabot wrote: Are there any instructions available for compiling a custom kernel for LTSP 5? I have asked this question a number of times, and I've seen it asked on various forums as well with no answer. It seems really odd that there are such detailed instructions available for LTSP4.x, with kernel kits etc., while there's nothing on LTSP5. well, the instructions should be the same as for building a kernel on your host distro. there's nothing LTSP-specific about it with LTSP5. find instructions for your distro (i.e. Fedora, Debian, Ubuntu or whatever), build a kernel package, and install it into the LTSP chroot, maybe run ltsp-update-image and ltsp-update-kernels afterwards. live well, vagrant -- _ 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] Ltsp-5 problem on Etch : showing initramfs prompt
On Sat, Dec 20, 2008 at 06:42:43AM -0800, Nataraj S Narayan wrote: Please help me with this. I am trying out a normal debian Ltsp-5. ..snip... rootserver: 192.168.0.254 rootpath: /opt/ltsp/i386 filename : /ltsp/i386/nbi.img Error: Connect: Connection refused mount: Mounting /dev/nbd0 on /root/ failed: No such interface mount: Mounting /dev on /root/dev/ failed: No such file o or directory mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init No init found. try passing init = bootarg Showing busy box and initramfs prompt. Is it a problem with nbd-server configuration? Can substitute nbd with nfs server? nbd is broken in debian etch, at least for use with ltsp. if you really need to use nbd, you'll have to use lenny. defaults for etch or lenny is to use NFS. live well, vagrant -- _ 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] Compiling custom LTSP 5 kernel
On Sat, Dec 20, 2008 at 02:36:43AM -0800, Slawek Drabot wrote: If that were true, the contents of /boot would be the same as /opt/ltsp/i386/boot and /var/lib/tftpboot/ltsp/i386 no. the content is different therefore the process for generating the relevant files must be different if you install a custom kernel package in the chroot, there should be hooks in the chroot that ensure that the generated initramfs is configured to handle network booting; that's what handles the differences. at least that's how it's implemented in debian and ubuntu, and i'm pretty sure the other distros mostly follow suit. but the package containing the kernel doesn't need anything LTSP specific. btw. using mknbi, the man page states: If you are looking to boot using PXE, look no further, mknbi is not what you want. You probably want something like PXELINUX which is part of the SYSLINUX package. should I look no further or mknbi is not what I want? in other words, is that look further, mknbi is not what you want or look no further, mknbi IS what you want? if you wanted to use Etherboot instead of PXE, then you might need mknbi, mkelfimage, or another wrapper utility. if you just want to use the PXE implementation that comes with most networking cards, then pxelinux is all you should need. live well, vagrant -- _ 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] Ltsp-5 problem on Etch : showing initramfs prompt
On Mon, Dec 22, 2008 at 01:59:11PM +0530, Nataraj S Narayan wrote: It seems I need a different 'pxelinux.cfg/default' for nfs mounting, currently it is for using nbd-server. Please help me to change to nfs. you should just ensure that boot=nfs is in /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default i don't think any other changes should be needed, though it depends on what all you did to create the chroot or customize it, etc... if that doesn't work, i'd recommend re-installing and using the defaults, which will create a chroot the uses NFS. this page gives instructions for installing on Debian Lenny, with links for installing on Etch or Etch-With-Backports: http://wiki.debian.org/LTSP/Howto/ live well, vagrant -- _ 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] screen resolution through KVM switch
On Fri, Jan 09, 2009 at 09:34:07PM -0500, Rob Owens wrote: I just spent a lot of time troubleshooting some video resolution issues. No matter what I did, I couldn't get my 17 CRT monitor to display better than 800x600 resolution. I tried manually setting the resolution and forcing the vesa driver. It turned out that my KVM switch was to blame, because when I hooked the monitor directly to the thin client it worked fine! i recently encountered this issue, and basically found that i needed to specify X_VERTREFRESH and X_HORZSYNC to appropriate values for the monitor in lts.conf, and then it worked fine. I'm using LTSP 5 on Debian Lenny. The thin client is a P3 with i810 video. lately i've mostly been using the ltsp related packages from Debian experimental, though i *think* it should work with the packages in lenny. live well, vagrant -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _ 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] feature request: specify apt proxy in ltsp-build-client
On Fri, Jan 09, 2009 at 09:53:06PM -0500, Rob Owens wrote: when the installer asks for my proxy information. This gets put into /etc/apt/apt.conf like this: Acquire::http::Proxy http://myproxy:3142;; Then when any of my systems need to download new packages, they check the proxy first and go to the internet only if a current package is not available from the proxy. Anyway, I'd like to be able to do use the proxy when I'm building the chroot environment. Something like this: ltsp-build-client --proxy http://myproxy:3142 committed to the Debian plugins: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/annotate/head%3A/server/plugins/ltsp-build-client/Debian/010-http-proxy should work on older versions too, just drop the file into /usr/share/ltsp/plugins/ltsp-build-client/Debian (or /etc/ltsp/plugins/ltsp-build-client). you can use --http-proxy to specify it from the commandline, or it will autodetect it from your /etc/apt/apt.conf* settings. --no-guess-proxy will disable autodetection. live well, vagrant -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _ 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] feature request: specify apt proxy in ltsp-build-client
On Fri, Jan 23, 2009 at 02:49:12PM -0500, Rob Owens wrote: On Mon, Jan 19, 2009 at 10:18:45AM -0800, Vagrant Cascadian wrote: committed to the Debian plugins: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/annotate/head%3A/server/plugins/ltsp-build-client/Debian/010-http-proxy should work on older versions too, just drop the file into /usr/share/ltsp/plugins/ltsp-build-client/Debian (or /etc/ltsp/plugins/ltsp-build-client). you can use --http-proxy to specify it from the commandline, or it will autodetect it from your /etc/apt/apt.conf* settings. --no-guess-proxy will disable autodetection. That worked great! I like the autodetect feature. glad to hear it! A few notes: 1) My lenny installation doesn't have /etc/ltsp/plugins (I imagine it would be a symlink to /usr/share/ltsp/plugins, but it's not there) yes, the /etc/ltsp/plugins directory is entirely optional, so it is not created by default. plugins in /etc/ltsp/plugins/ will override corresponding plugins in /usr/share/ltsp/plugins, so there's no point in symlinking it to /usr/share/ltsp/plugins. /etc/ltsp/plugins is intended to be used by admins to override behavior of a specific plugin in in /usr/share/ltsp/plugins. 2) I put my proxy information in /etc/apt/apt.conf, because that's where the installer puts it. Some people create /etc/apt/apt.conf.d/01proxy, and put their proxy information in there. I tested both methods with the autodetect feature, and both worked. yes, it uses apt-config, instead of parsing configuration files manually. 3) I removed my proxy information from apt.conf* and used the --http-proxy option. That worked as well. glad it helps. i've been meaning to write that plugin for ages. thanks for giving me the impetus to actually sit down and write it. live well, vagrant -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _ 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] updating the chroot -- LTSP documentation question
On Fri, Jan 23, 2009 at 03:12:31PM -0500, Rob Owens wrote: Per http://www.ltsp.org/~sbalneav/LTSPManual.html#updating-chroot, the instructions for updating the chroot on a Debian system are: sudo chroot /opt/ltsp/i386 sudo apt-get update (I don't think sudo is needed, though, since you are chrooting as the root user) sudo mount -t proc /proc /proc (again, sudo is not needed) sudo apt-get upgrade (same here) exit indeed. as mentioned by ogra, ditch the extra calls to sudo, or call 'sudo chroot /opt/ltsp/i386' with every command. Is it necessary to umount /proc before exiting, or is that not required? i'd definitely recommend unmounting it, yes. also, be sure when you run apt-get upgrade, that the environment variable LTSP_HANDLE_DAEMONS=false is set, otherwise, any upgraded daemons will start inside the chroot. so, just for completeness, i'll add a few more important steps: sudo chroot /opt/ltsp/i386 # alternately: # su -c 'chroot /opt/ltsp/i386' # from here on out, you're in the chroot as root mount -t proc /proc /proc # make sure daemons don't start export LTSP_HANDLE_DAEMONS=false # update package lists apt-get update # install available package updates apt-get upgrade # alternately: # apt-get dist-upgrade # update the ltsp network boot configuration files if needed /usr/share/ltsp/update-kernels # unmount proc, as it really shouldn't be there. umount /proc # exit the chroot exit # update the server's /var/lib/tftpboot/ltsp/ ltsp-update-kernels i'll write up some wrapper scripts to handle this stuff, as there some issues with the above steps. proc should probably only be mounted and umounted if not already mounted, for example. live well, vagrant -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _ 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] Incomplete session list on ldm screen, Debian Lenny
On Sat, Jan 24, 2009 at 08:49:31AM -0500, Rob Owens wrote: On my Debian Lenny machine with LTSP 5 and a fresh chroot environment, I get an incomplete list of options when I attempt to choose my session at the ldm screen. These are my only options: Default Failsafe xterm I have Gnome and FVWM-Crystal installed, and see those options in my GDM screen. When I log into a thin client, I get Gnome because that is my default. sounds like ldminfod isn't set up on the server, which parses the /usr/share/xsessions/*.desktop files for session types. does /usr/sbin/ldminfod exist on your server? should be part of the ltsp-server package. grep ldminfod /etc/inetd.conf should return something like this: 9571 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/ldminfod if it doesn't, try to add it with the command: update-inetd --group LTSP --add 9571 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/ldminfod and restart inetd: invoke-rc.d openbsd-inetd restart telnet 127.0.0.1 9571 should return something like this: Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. language:en_US.UTF-8 language:es_US.UTF-8 session:/usr/bin/icewm-session session:/usr/lib/gdm/gdm-ssh-session session:startxfce4 session:/usr/bin/gnome-session session:awesome xsession:/etc/X11/Xsession rating:97 Is there any way for me to manually add to the list of session choices? you could tell inetd to run a different program on port 9571, but it sounds like ldminfod just isn't set up correctly. live well, vagrant -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _ 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] specify numlock per thin client
On Mon, Jan 26, 2009 at 05:33:37PM -0500, Rob Owens wrote: Is there a way to specify whether or not numlock will be on, based on the thin client's mac address or IP address? I need it to be client-specific, not user-specific. The reason is that I have some laptops as thin clients, and turning numlock on means that part of the alphabet turns into a numeric keypad. in newer versions you can set the lts.conf value for X_NUMLOCK (or LDM_NUMLOCK for some older versions). [Default] X_NUMLOCK=false [00:11:22:aa:bb:cc] X_NUMLOCK=true -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _ 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] Gui login problem
On Fri, Feb 27, 2009 at 10:00:05AM -0800, Skywalker wrote: I've a problem after LTSP installation on lenny: login from gui interface failed without error, it seid me :password incorrect but this is a lie. If I log in in from text shell it succeded. Can anybody help me about or explain me why it happen? sounds like you may have added your user in the chroot, which is not typically how it is done. typically, everything is done on the server- adding software, users, etc. can you ssh to the server with the same username and password? live well, vagrant -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _ 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] ldm: respawn doesn't work anymore for latest ubuntu ldm 2.0.38
On Mon, Mar 09, 2009 at 04:08:25PM +0100, Peter Stein wrote: Now I have (of course) a new problem: ldm does not respawn automatically if you hit strg+alt+backspace or type in the wrong pw. the screen scripts have changed- each screen script used to handle respawning independently (if at all). try creating a script and placing it in /opt/ltsp/i386/etc/ltsp/screen.d/ldm-respawn: while : ; do . /usr/share/ltsp/screen.d/ldm done and set in lts.conf: SCREEN_07=ldm-respawn you might very well encounter other problems, but that's at least a starting point... live well, vagrant -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _ 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] ltsp backports
On Mon, Mar 09, 2009 at 10:01:32PM -0400, Rob Owens wrote: I also am interested in not upgrading my distro for as long as possible, while keeping up-to-date on LTSP. Is there any reason that it might be easier on Debian than Ubuntu? (or vice-versa) well, as one of the active LTSP maintainers for Debian, i do attempt to keep fairly current ltsp related backports for stable Debian releases. for Debian etch, i maintained a repository on pkg-ltsp.alioth.debian.org, for lenny, i hope to use backports.org. it's mostly not been very difficult to keep up for Debian; occasionally requires a few extra patches, some testing, etc. it's really just a question of who will take the time to maintain it. live well, vagrant -- _ 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] Incomplete session list on ldm screen, Debian Lenny
On Sun, Jan 25, 2009 at 08:38:59PM -0500, Rob Owens wrote:
On Sun, Jan 25, 2009 at 03:19:10PM -0800, Vagrant Cascadian wrote:
On Sat, Jan 24, 2009 at 08:49:31AM -0500, Rob Owens wrote:
On my Debian Lenny machine with LTSP 5 and a fresh chroot environment, I
get
an incomplete list of options when I attempt to choose my session at the
ldm
screen. These are my only options:
...snip...
telnet 127.0.0.1 9571 should return something like this:
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
language:en_US.UTF-8
language:es_US.UTF-8
session:/usr/bin/icewm-session
session:/usr/lib/gdm/gdm-ssh-session
session:startxfce4
session:/usr/bin/gnome-session
session:awesome
xsession:/etc/X11/Xsession
rating:97
telnet 127.0.0.1 9571 gives me:
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
language:
language:en_US.UTF-8
Traceback (most recent call last):
File /usr/sbin/ldminfod, line 128, in module
lines = get_sessions('/usr/share/xsessions/')
File /usr/sbin/ldminfod, line 87, in get_sessions
variable, value = line.split('=')
ValueError: too many values to unpack
Connection closed by foreign host.
i think this is be fixed in bzr. you can download new version:
http://bazaar.launchpad.net/%7Eltsp-upstream/ltsp/ldm-trunk/download/head%3A/ldminfod-20081031022502-ehq85efyvrlwsedi-3/ldminfod
copy it to /usr/local/sbin/ldminfod. and make it executable:
chmod +x ldminfod
cp ldminfod /usr/local/sbin/
comment out the existing ldminfod line in /etc/inetd.conf, and add the new
entry:
update-inetd --group LTSP --add 9571 stream tcp nowait
nobody /usr/sbin/tcpd /usr/local/sbin/ldminfod
restart inetd:
invoke-rc.d openbsd-inetd restart
hopefully that fixes your problem.
live well,
vagrant
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_
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] Incomplete session list on ldm screen, Debian Lenny
On Fri, Mar 13, 2009 at 06:52:38PM -0400, Rob Owens wrote: On Fri, Mar 13, 2009 at 07:43:35AM -0700, Vagrant Cascadian wrote: i think this is be fixed in bzr. you can download new version: http://bazaar.launchpad.net/%7Eltsp-upstream/ltsp/ldm-trunk/download/head%3A/ldminfod-20081031022502-ehq85efyvrlwsedi-3/ldminfod copy it to /usr/local/sbin/ldminfod. and make it executable: chmod +x ldminfod cp ldminfod /usr/local/sbin/ comment out the existing ldminfod line in /etc/inetd.conf, and add the new entry: update-inetd --group LTSP --add 9571 stream tcp nowait nobody /usr/sbin/tcpd /usr/local/sbin/ldminfod restart inetd: invoke-rc.d openbsd-inetd restart hopefully that fixes your problem. This works. A couple of notes: glad to hear it. 1) When I installed LXDE, it set my system-wide default session to be LXDE. I didn't expect that. seems like LXDE shouldn't push out gnome as a default- i'd think it would be appropriate to file a bug on LXDE... 2) Vagrant's fix, above, gives me a complete session list. However it seems to pull the session names from the Exec= line, rather than the Name= line in the *.desktop files. This results in an ugly session list like this: /usr/bin/gnome-session /usr/bin/startlxde startkde /usr/lib/gdm/gdm-ssh-session Definitely functional, but not as pretty as it could be. Thanks for the fix, Vagrant. newer versions of LDM display the nicer looking names; that feature was added after lenny was frozen. session persistance was also very recently added upstream. i'll work on getting some backports of the newer LTSP related packages for debian lenny available- hopefully through backports.org once they hit debian/testing. live well, vagrant -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _ 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] LDM for Fat clients
On Fri, Mar 27, 2009 at 01:53:14PM +0530, Jigish Gohil wrote: Hello Community Gadi suggested that LDM can be used to launch full DE as a localapps, effectively making client a fat client. As a bonus we get all the goodness that LDM provides such as single point of authentication from the server without changing anything in the client image, local sound, printing etc. Here is what we had to do to make IceWM available as a localapp via LDM. cat /usr/bin/localapps-icewm #!/bin/bash #ltsp-localapps icewm-session ltsp-localapps icewm-session zenity --info --text Only Click OK if you want \n to log out from the session Needed the zenity hack to keep the session alive otherwise it ended after ltsp-localapps command was run thinking localapps-icewm had exited. why not: ltsp-localapps --wait icewm-session ?? i had implemented the code to handle --wait for exactly this purpose. oh, i did need to implement some other hack to keep it running server-side as well... still, using --wait is probably a good idea. it prevents additional localapps from getting started up, which should just be handled by the locally running session. i suppose --wait could do xatom queries until some flag was set to handle xsession exit... live well, vagrant -- _ 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] how to do ltsp5 on debian5.0 lenny without internet connection?
On Sat, Apr 04, 2009 at 07:00:40AM +0530, ib services kochi wrote: when i try to run ltsp-build-client --mirror file:///cdrom it gives the folloeing error: NOTE: adding default dist and components to security mirror: http://security.debian.org/ lenny/updates main I: Retrieving Release I: Retrieving Release.gpg E: Failed getting release signature file file:///cdrom/dists/lenny/Release.gpg error: LTSP client installation ended abnormally try: ltsp-build-client --mirror file:///cdrom --security-mirror none --accept-unsigned-packages this assumes, of course, that your CD contains all the packages necessary for ltsp. good luck. live well, vagrant -- _ 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] ltsp5 on debian lenny using local mirror
On Sat, Apr 04, 2009 at 10:11:54AM +0530, ib services kochi wrote: i copied the iso images of debian5.0 lenny DVDs to hard disk and mounted the images to /mnt/iso1 ...snip... /mnt/iso5 and gave the command ltsp-build-client --mirror file:///mnt/iso1/ --security-mirror none --accept-unsigned-packages output: I: Base system installed successfully. ...snip... E: Couldn't find package ltsp-client error: LTSP client installation ended abnormally how to give more than one mirror in the ltsp-build-client command? ltsp-build-client --mirror file:///mnt/iso1 \ --extra-mirror file:///mnt/iso2,file:///mnt/iso3,file:///mnt/iso4,file:///mnt/iso5 \ --security-mirror none \ --accept-unsigned-packages the file:// URL support is a little weird, as those mounts won't be there after the install, and apt-get update will stop working inside the chroot- but you can manually fix that by editing the /opt/ltsp/i386/etc/apt/sources.list later. at one point i explored adding actual support for apt-cdrom, but it proved too much hassle. live well, vagrant -- _ 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] how to mount external hard drives? + log problem? - LTSP 5 on Ubuntu 8.04
On Wed, Apr 22, 2009 at 04:44:41PM +0200, Peter Stein wrote:
my LTSP 5 gets better, but still needs some kind of attention. This
time: External hard drives. Currently I use LTSP 5 on a Ubuntu 8.04
(hardy for the thin client's OS, but Debian Etch for the
workstations). We have auto mount for USB flash drives. That works
impeccably. But I could not figure out a way to mount real external
hard drives via ltspfsmounter or any other way (manually).
external USB hard disks may not be considered removeable by udev, even though
USB is clearly removeable (i think the same is true for firewire). many of the
recent changes to ltspfs were done to address this issue.
i'm not sure if this applies to your Ubuntu 8.04 LTSP chroot, but NEWS.Debian
in Debian contains:
ltspfs (0.5.0~) unstable; urgency=low
* automatic mounting of non-removable devices is now disabled by default
to enable, in /etc/udev/rules.d/*ltspfsd.rules, remove ATTRS{removable}==1
from the appropriate lines. see http://bugs.debian.org/432024 for more
information.
-- Vagrant Cascadian vagr...@freegeek.org Thu, 10 Jan 2008 13:19:04 -0800
although in recent versions, we actually switched to LOCALDEV_DENY in lts.conf
(hmm... i'd better update the NEWS.Debian file...)
live well,
vagrant
--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_
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] Single user account and pam mount
On Tue, Apr 28, 2009 at 09:26:40PM +0200, Marius Flage wrote: Jordan Erickson wrote: I would propose a temporary user of sorts that pulls from the skel/template you created, does a pam makehomedir or whatever it is, and removes it upon logout. This way, you have separate user accounts for each login, and changes can be wiped upon user logout. The immediate problem with this is how to keep control over the different usernames/passwords currently in use. Now it's easy just telling all students to use student/student to log in. If we have to inform them to use random usernames/passwords, then it'll quickly become a user administration nightmare. But maybe you meant some other way of creating the accounts..? It needs to be simple and predictable. if you set LDM_GUESTLOGIN=True in lts.conf, there will be a button to click on that will automatically login with the hostname of the thin client, which should default user/password based on the ip address to ltsp20, ltsp21, ... ltsp255 for most setups without DNS on the thin-client network. a few related configuration options should be described here: http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspDocumentationUpstream that doesn't handle account and homedir creation, but at least gives you a simple and predictable user/passwd login. then you could experimental with some sort of skeleton home dir for users. the problem of course, is if there is user-specific data in the skeleton directory. good luck! live well, vagrant -- Register Now Save for Velocity, the Web Performance Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _ 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] ltsp backports
On Wed, Apr 29, 2009 at 02:05:50PM -0500, Scott Balneaves wrote: On Wed, Apr 29, 2009 at 12:21:55PM -0400, Dan Maranville wrote: I'm really unsure as to why Ubuntu gets all this hate directed against them because they don't backport new features from more current releases into older ones. As far as I know, LTSP current isn't being backported into either Fedora 3 or Debian Sarge. well, there haven't been any official Debian backports of LTSP, but i've generally managed to maintain backports for the current Debian stable release for most of, if not the whole cycle of of stable releases. Since Debian Lenny (released in February), there's backported current upstream versions for ldm and ltspfs, and ltsp itself is only missing a few minor updates mostly not relevent to Debian. i only stopped making backports for Debian Etch when the next release (Lenny) went into freeze last summer. similar story for Debian Sarge, although most of the initial Debian LTSP5 implementation was actually mostly tested on sarge, though a version was never included as part of sarge. that said, Debian's support cycles (approximately 3-4 years) are usually a bit shorter than Ubuntu's LTS support cycles (3 for desktop, 5 for server), usually much longer than the regular Ubuntu support cycles (1.5 years). Debian's release cycle has been about 2-3 years, while Ubuntu's LTS release cycle seems to be about 1.5-2 years, and Ubuntu's regular release cycle is usually 6 months. i don't know other distro release/support cycles well enough to comment on those. so the desires or needs for a backport may be a little different, as different distros progress in different ways. live well, vagrant -- Register Now Save for Velocity, the Web Performance Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _ 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] Passing environment variables to the window manager
On Tue, May 12, 2009 at 12:54:07PM +0200, Andre Majorel wrote: Upgrading LTSP 4.2 to LTSP 5 broke something. An Xsession script of mine (/etc/X11/Xsession.d/95xxx on Debian) starts programs that rely on environment variables from the user's ~/.bashrc. Is there a way to make LTSP 5 pass those variables to whatever process executes /etc/X11/Xsession.d/95xxx like LTSP 4.2, short of modifying /etc/X11/Xsession.d/95xxx to explicitly source ~/.bashrc ? could you post your script? that would make it much easier to help. live well, vagrant -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _ 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] ltsp-xorg.conf - which script generates it?
On Tue, May 12, 2009 at 10:14:16PM -0400, David Hopkins wrote: I have tried using both the old way as well using the lts.conf variables and neither consistently always work. e.g. I can specify 1024x768 for the resolution but it still comes back at 1280x1024 even though 1024x768 is the preferred resolution of the monitors. Similarly, specifying the Xserver doesn't always seem to work. In fact, specifying the Xserver to be what is required (which is the same as what is autodetected) causes the client to hang. My LTSP4.2 server always sets the res at 1024x768 for this hardware and honors the Xserver setting. I'll look at the screen session scripts but if there is a simple way to just generate the xorg.conf file within the way LTSP works, it would be quite nice, even if only available for debugging X issues. if you if you specify CONFIGURE_X_COMMAND in lts.conf, then it will use that command instead of the built-in configuration scripts. note that it's a full path to the command, and doesn't take any arguments. then you can either generate /etc/X11/xorg.conf or /var/run/ltsp-xorg.conf, and it'll use that as the configuration file. though if you're really using the XSERVER and X_MODE_0 or XRANDR_MODE_0 settings and they're not working properly, i'd suggest filing bug reports in addition to working around the problem. X.org (and ltsp) developers are working hard at getting rid of xorg.conf, and they can only fix issues they know about and have sufficient information about. live well, vagrant -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _ 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] X font server - xfs: or how to install mathematica fonts for thin client
On Fri, Jun 05, 2009 at 04:18:43PM +0200, Peter Stein wrote: I have a solution now. I commented something out in /usr/share/ltsp/screen-x-common the prevented ldm from starting up. ...snip... This means it is not verified that xfs is online, but nc -w 5 $SRV 7100 gave no result than waiting. That means xfs was reachable but didn't gave no return. Anybody an idea for that behavior? the verification code was added because otherwise X failed to come up at all if xfs was down for some reason. apparently, it didn't work. I used a better command instead: if nmap $SRV -p 7100 | grep font-service /dev/null ; then instead of if nc -w 5 $SRV 7100 /dev/null ; then Now it works like a charm. Might be helpful for users of xfs. i don't think nmap is installed by default, so it would be nice to not have to pull in another dependency. could you try with: if nc -z -w 5 $SRV 7100 /dev/null ; then X_ARGS=$X_ARGS -fp $xfs_line fi if that works, i'll commit it upstream. live well, vagrant -- OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _ 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] local devices / pulse audio
On Sun, Jul 05, 2009 at 01:55:27PM +0200, Holger wrote: I have problems with local devices like usb sticks and cd-roms. I use ltsp-5 on debian squezzy. After installing ltsp-5 i inserted a cdrom into a client. Gnome didn't recognize anything, the same with usb sticks. When i am logged in directly (keyboard, mouse) on the server everything works fine. Back on the client i logged in as root and everything worked. Logging in as normal user nothing works it works for me, so first off, is the user in the fuse group? getent group fuse to add them: adduser USER fuse they need to be in the fuse group for ltspfs (a.k.a. LOCALDEV) to work. what's the output on: ls -l /dev/fuse /usr/bin/fusermount /dev/fuse needs to be writeable by the fuse group, and fusermount should be executable by the fuse group. if they are in the fuse group, and it still doesn't work, does anything show up with: mount | egrep /media/USER then it may be an issue with GNOME not recognizing the /media/USER/* mounts for some reason. Then I tried to get sound with pulesaudio, but no sound :-( I tried to start the pulsaudio daemon on client side. The daemon aborted cause it could not write to /var/lib/pulse. After adding this directory to the rw_dirs in /etc/default/ltsp-client-setup sound seems to work fine. i'm having this same problem, although simply adding /var/lib/pulse to rw_dirs didn't solve it for me. i had to manually create /opt/ltsp/i386/var/lib/pulse, and even after doing that, it still didn't work. the same code (ltsp* and ldm* versions) works fine with a lenny LTSP chroot, even with a squeeze server. so there's something in pulseaudio that changed since lenny. please file a bug report in the debian bug tracking system (http://bugs.debian.org), preferrably using reportbug tool: apt-get install reportbug reportbug ltsp-server A friend of me is running a ltsp-5 server too. He had no trouble with pulesaudio and local devices. also on debian squeeze, or debian lenny? or debian lenny with backported ltsp packages from squeeze? I don't konw whats going wrong. Is there a logfile to get more information about the problem? no universal log file... look around in /var/log/* for anything meaningful. i haven't found much for this myself. live well, vagrant -- _ 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, sound and lxde
On Mon, Jul 20, 2009 at 05:43:19PM +0200, Sawar wrote: With my associates we decided that we won't need sound so I think that I'll install ltsp on Debian with lxde and few necessary applications. Hopefully I'll be able to configure lxde desktop to be as simple as possible for users. if you do end up wanting sound on debian, check out: /usr/share/doc/ltsp-server/README.Debian.sound i've been meeting with the Debian LXDE maintainer the last two days, talking about how to improve it for thin-client environments. live well, vagrant -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _ 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] How to configure LTSP to use local hardware resources?
On Mon, Jul 20, 2009 at 07:01:34PM +0300, asmo.koski...@arkki.info wrote: Here same for Ubuntu. To run the ltspfs implementation, the LOCALDEV variable must be set to True in the ltsp configuration file (/opt/ltsp/i386/etc/lts.conf). https://wiki.ubuntu.com/EnableLTSP5LocalDevices that's not exactly true. typically, LOCALDEV=True is enabled by default, without any option in lts.conf. also, some distros (ubuntu) put lts.conf in /var/lib/tftpboot/ltsp/i386/lts.conf, if using NBD root. live well, vagrant -- _ 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] XFCe and Thunar: Usb local devices
On Wed, Jul 22, 2009 at 11:19:29AM -0300, Osvaldo Filho wrote: Is it possible with XFCe and Thunar -Debian Lenny - we have local devices in the same way i have with ubuntu (icons on desktop)? you'll need to install the ltspfs hook to create files in the user's Desktop dir. see /usr/share/doc/ltspfs/examples/kde-desktop-icons for instructions. xfce may require some modifications to get it to work- the simplest option is to just use symlinks. live well, vagrant -- _ 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] ldm restart after login
On Wed, Aug 05, 2009 at 04:58:43PM +0200, Antoine Migeon wrote: I have LTSP 5, Debian Lenny (netinst without X). I don't want my thin client connect to the LTSP server. I have multiple SSH server (CentOS 5.2), and their ssh keys are in the know_host file in the thin client. XDMCP work fine. DNS work fine. SSH work fine in shell/command line. BUT when I logon with LDM, no desktop environnement is launched ! It display a black screen during 2 secondes and restart LDM ! which file is executed in the server ? Xclient ? Xsession ? where can I specified the desktop environnement ? i'm guessing you need to install and configure ldminfod on the servers, so the thin-clients know where to look for Xsession. alternately, you could specify LDM_XSESSION in lts.conf, but then all your servers would have to have the same Xsession file location. the default is to use whatever Xsession is present on the client, if not told otherwise by ldminfod. for debian, you'd just install the ldm-server package on each of your servers, not sure if something similar is available for CentOS. you could manually install ldminfod and then configure your inetd to point to it. fedora probably has an example that should work for you. live well, vagrant -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _ 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] Too few X's in template
On Fri, Aug 07, 2009 at 07:27:47PM +0200, Andre Majorel wrote: Has anybody got that one before ? In VT 7, this message is printed every 15 seconds or so : mktemp: too few X's in template `/var/run/ldm-xauth-?/Xauthority' this is fixed in bzr: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/revision/1170/screen.d/ldm It's cute, but I'd trade it for a working X server. :-) it's also likely not the cause of your problems, as that same issue exists for both squeeze and lenny with backports, but X still works (at least for me)... if you're using Debian sid/unstable, please try to reproduce the problem with Debian squeeze/testing, and if it's not present in both, please take the time to dig a little deeper to try and track down the real issue. there are frequently breakages in sid, as it's an unstable moving target; especially with LTSP as it's a bit of an unusual environment, so people make assumptions and don't test every (non-ltsp) upload in an LTSP environment. There's also this init phase message in VT 1 : Starting LTSP client Can't start Hardware abstraction layer - please ensure dbus is running ... failed! yes, i've been looking into this as well... live well, vagrant -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _ 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] localdev w/ xfce4 desktop
On Thu, Aug 13, 2009 at 06:15:48PM +0200, SZABO Zsolt wrote: Does anybody use here LOCALDEV and xfce4? ...snip... What I mean: when plugging the USB stick a corresponding icon appears on the Desktop and clicking on this icon the content of the USB stick will be browseable... you might be able to use or modify the kde-desktop-icons script to work with XFCE. on Debian systems, it should be available in /usr/share/doc/ltspfs/examples/ (is it still true that the user cannot influence its unmount? yes. does ltspfsd umount it automatically after 2 sec? yes. though typically the icon or mountpoint will still be present to the logged in session until the user physically removes the USB stick (or other media). this allows it to automatically mount it again if accessed, to give the illusion that it is mounted the whole time. what is with local hdd-s? OK they are not to be removed...) they are disabled by default, as people were booting suspend-to-disk'ed laptops and it could cause filesystem corruption in this case, as well as giving root access to the files on the hard drive to whoever logged into the laptop when used as a thin client. see http://bugs.debian.org/432024 for more information, or on debian systems, check /usr/share/doc/ltspfs*/NEWS.Debian. live well, vagrant -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _ 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] Simultaneous running of programs on server and client
On Tue, Aug 18, 2009 at 09:46:32AM -0600, Andreas J Guelzow wrote: On Tue, 2009-08-18 at 18:06 +0300, Shahar Or wrote: On Tue, Aug 18, 2009 at 5:33 PM, Alok Mahendrooalon...@fastmail.in wrote: Does the Server for LTSP have to be standalone or is it possible for one to work on both the client and server using the same program simultaneously. Dear Alok, I think that logging into the same user account from two different machines simultaneously doesn't work well. I would never do it. For any reasonable well behaved program there shouldn't be a problem working from several clients (and/or the server) simultaneously. I tend to do that frequently. Note though that one misbehaving program is Firefox since it tries to enforce a single process completely ignoring the requested display. and then there's firefox and a handful of other widely used applications (i think gnome doesn't work so well) where that just plain doesn't work. yes, that's not how it should be but that's the sad reality of many applications. i don't like it either. live well, vagrant -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _ 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] ltsp for RDP?
On Fri, Aug 28, 2009 at 11:39:23AM -0600, David Burgess wrote: We could install a linux distro on the 512MB flash drive, which is what we're doing now with HP's distro, or go straight to PXE booting. Being somewhat familiar with ltsp in a pure linux environment, and having spent hours imaging dozens of these thin clients (whose write speed averages something like 200 KB/s), I'm partial to the PXE boot option. Is this something that ltsp is suited for? ...snip... I'm not looking for a step-by-step, but something like 'yes, we do this', 'here's a link to a how-to', 'here's a quick overview', or 'no, not recommended' would be helpful. sure, should work. briefly, in lts.conf set SCREEN_07=rdesktop and RDP_SERVER=hostname (or ip of server) and if needed, RDP_OPTIONS. good luck! live well, vagrant -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _ 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] remote shutdown of a TC through ssh
On Thu, Sep 03, 2009 at 09:01:56AM +0200, Wojtek wrote: isn't nc a little bit unsecure? The $RBFILE is in plain-text. We use SSH for such situations, ...snip... So if You want to shutdown a group of TCs and you want to keep your security level high maybe the dsh is the solution. well, thing is, running sshd from the thin clients is insecure: you either have: 1) a shared publicly accessible sshd key on the thin-clients root filesystem (NFS or NBD). 2) you randomly generate host keys on boot of the thin client, at which point you have no way of knowing from the server that you're actually connecting to the thin client. granted, setting up a genuine man-in-the-middle attack is harder that simply sniffing the wire, but it's dangerous to call it a secure connection. have no such illusions. live well, vagrant -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _ 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] rdesktop and usbmount
On Wed, Sep 09, 2009 at 02:16:07PM -0600, David Burgess wrote: Another challenge I encountered while setting this up is getting local usb devices to appear in the rdp session. The problem in Ubuntu ltsp is that because the usb volume mounts only when opened by the user (i.e., in gnome/nautilus), and since the user will never see gnome, there is no mount point to pass to the rdesktop command. with ltspfs 0.5.13 on ubuntu or debian, install both the ltspfsd and ltspfs package into the chroot, and then it should at least partially work, by making a mount on the thin client in /media/root/* that you can then export via rdesktop somehow as a drive. at least that's what gadi tells me. :) live well, vagrant -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _ 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] nbdport after ltsp-update-image
On Wed, Sep 16, 2009 at 12:47:59PM +0300, Tuomo Kallio-Kokko wrote: I have ubuntu 8.04 ltsp-server with two different environment images (kiosk and normal desktop). Both are using nbd for filesystem. Normal desktop image is at port 2000 and kiosk image is at port 2001. Correct nbd port is given for pxe at /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default with nbdport-variable. If I update kiosk filesystem with ltsp-update-image -b /opt/ltsp-kiosk it'll changes the nbdport-variable of normal desktop to 2001. This will cause normal desktop environment clients to boot to kiosk environment. /var/lib/tftpboot/ltsp/* gets overwritten every time ltsp-update-kernels is run, and only works with a single base directory. rather than putting one image in one base directory, you'll need to use a different chroot name, with the same base dir, otherwise there is no way to distinguish which gets the /var/lib/tftpboot/ltsp/i386 directory. for example, when creating the chroot: ltsp-build-client --base /opt/ltsp --chroot i386 and for your kiosk: ltsp-build-client --base /opt/ltsp --chroot i386-kiosk this will generate /var/lib/tftpboot/ltsp/i386 and /var/lib/tftpboot/ltsp/i386-kiosk. you'll need to configure DHCP to decide which are regular thin-clients and which are kiosks. live well, vagrant -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf _ 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] logging into tc using ssh keys
On Fri, Oct 02, 2009 at 11:25:52AM -0600, David Burgess wrote: placing the generated id_rsa.pub into /opt/ltsp/i386/root/.ssh/authorized_keys/ on the server. I uncommented the line AuthorizedKeysFile %h/.ssh/authorized_keys then rebuilt the image (also tried replacing %h above with /root). After rebooting a test tc, I can see the file in /root/.ssh/authorized_keys, but I still get a password challenge when trying to ssh in. If I enter a blank password I am unable to connect. make sure the permissions are correct on authorized_keys: chmod og-rwx /opt/ltsp/i386/root/.ssh/ chmod og-rwx /opt/ltsp/i386/root/.ssh/authorized_keys ltsp-update-image ssh is really fussy about permissions. Is there a better way of doing this? in general, ssh-ing to thin-clients isn't very secure, as they all share the same host key, which is typically available to anyone who can mount the NFS share or NBD image. (alternately, if you generate a key on boot, you have no trust-path to the generated key) don't really know of another option for executing commands on all the thin-clients... live well, vagrant -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf _ 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] logging into tc using ssh keys
On Fri, Oct 02, 2009 at 03:45:27PM -0600, David Burgess wrote: On Fri, Oct 2, 2009 at 3:24 PM, Vagrant Cascadian vagr...@freegeek.org wrote: in general, ssh-ing to thin-clients isn't very secure, as they all share the same host key, which is typically available to anyone who can mount the NFS share or NBD image. I don't think I understand the implications of all the thin clients sharing a host key, essentially, it completely compromises the security of ssh. ssh and other public-key encryption relies on the fact that the secret key is actually secret. exporting those secret keys over insecure protocols such as NBD and NFS compromise that. someone could pretend to be the thin client and stop your commands from running on the thin client (and make it look like they had been run), monitor all communications between your server and the thin clients (including sniffing for passwords), etc. it might even open the door for them to log the entire X session (ldm, rdesktop, whatever). however the thin clients on this network are used for rdesktop exclusively. they can't boot from floppy, CD, or USB? plug a laptop into the network? root is the only valid login account and the password is secure, so if I'm not mistaken the keys are effectively off limits to non-admins, and in my case this is a non-issue. Somebody correct me if I'm wrong. maybe with the level of risk you're concerned about it is a non-issue, maybe the above scenarios are not trivial or likely, but i would have no illusions that this is a secure configuration. the important thing is to understand the risks you're taking, and develop a security model appropriate to that. live well, vagrant -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf _ 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] logging into tc using ssh keys
On Mon, Oct 05, 2009 at 11:24:38AM -0600, David Burgess wrote: On Fri, Oct 2, 2009 at 4:40 PM, Vagrant Cascadian vagr...@freegeek.org wrote: essentially, it completely compromises the security of ssh. ssh and other public-key encryption relies on the fact that the secret key is actually secret. exporting those secret keys over insecure protocols such as NBD and NFS compromise that. Are you saying that anybody with network access could get those keys over NBD or NFS? yes. Would they need shell access on a PXE-booted machine, or would it suffice to use any network-connected machine with NFS or NBD ability? they need access to a network-connected machine that has access to the server ports running NBD or NFS, such as a laptop they brought with them, or boot one of the thin clients from a livecd or usb stick or some other boot media. basically, getting a machine plugged into your network that they have control over. Personally I don't see this a a significant risk in my environment, nor do I see much at stake if somebody did gain ssh access to my thin clients. well, if someone gains root access over ssh to your thin clients, and knew what they were doing, they would be able to spy on the users of those thin clients, possibily gaining access to passwords and other private data. they can read all keystrokes, read what's displayed on the X server, display windows to the user asking for their password or other sensitive information, etc. Nevertheless, I would like to better understand the risk for future reference, and I think it bears elucidating for ltsp users in general. sure. as a general good practice, don't ever give direct root access to arbitrary commands, such as a shell. better to restrict to specific commands, using an authorized_keys file something like this: command=/path/to/some/command --arg1 --arg2 ssh-rsa KEY_GOES_HERE command=/path/to/some/other/command --arg1 --arg2 --arg3 ssh-rsa ALTERNATE_KEY_GOES_HERE another option would be to give full shell access to a non-root admin user on the thin clients with sudo access for specific commands. the key is limiting it to specific commands; giving root access to arbitrary commands over insecure ssh connections leaves the door wide open to spy on the users of the thin clients. in the end, it's a risk assesment, and in general it's better to be overly cautious. that's my take, anyway. the more you know, the more terrifying it gets. :) live well, vagrant -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf _ 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] logging into tc using ssh keys
On Tue, Oct 06, 2009 at 09:03:24AM +0200, Frédéric Grelot wrote: - Vagrant Cascadian vagr...@freegeek.org a écrit : On Mon, Oct 05, 2009 at 11:24:38AM -0600, David Burgess wrote: On Fri, Oct 2, 2009 at 4:40 PM, Vagrant Cascadian vagr...@freegeek.org wrote: essentially, it completely compromises the security of ssh. ssh and other public-key encryption relies on the fact that the secret key is actually secret. exporting those secret keys over insecure protocols such as NBD and NFS compromise that. Are you saying that anybody with network access could get those keys over NBD or NFS? yes. Well, are you sure that it gives the access? yes. Listenning to traffic, you can get the content of /root/.ssh/authorized_keys, which is used to validate the key when you try to connect as root. But, As I remember, when you want to export your key pair to a computer, you use ssh-copy-id -i ~/.ssh/id_dsa.pub (for example), and not id_dsa (which is private). This is the basis of private/public key pair : you actually give your public key, allowing people to ensure that it is *you* that try to connect with your private key. The private key, however, stays on the server (and is not even in the client NBD or NFS image), and when the admin try to connect, it is used by ssh in an encrypted form. the keys i am talking about are usually located in /opt/ltsp/i386/etc/ssh/*host*key*, which is exported via NFS or NBD. those are the host's private/public keypairs, which are used to establish that you're connecting to the machine you think you are, and prompts you with messages such as this: $ ssh somerandomhost The authenticity of host 'somerandomhost (127.0.0.1)' can't be established. RSA key fingerprint is 05:e4:5e:f6:2a:6e:9c:47:50:45:67:bc:f8:eb:8a:58. Are you sure you want to continue connecting (yes/no)? since all thin clients use the same host key, someone could play a man-in-the-middle attack when you ssh to the thin client, as you have no means of determining which thin client you're connecting to, and relay the session to the real thin client, and listen in on the whole ssh session. and if you ssh to the thin client as root, they gain root access to the thin client. However, NFS is known to be unsecure (v3), and one could actually listen to every file that is transmitted by the user (including its ~/.mozilla directory, which may contain passwords). It could even wait for the .Xautority file to be transmitted... in LTSP, you don't usually mount /home over NFS, you log into the application server and file access happens on the server. the programs are merely displayed on the thin-client. Actually, remote X is not more secure, so anyone with access to the network may listen to X commands : windows showing, mouse moving, keystrokes which is why LTSP5 uses ssh's X11 forwarding... though you have similar security concerns to the above man-in-the-middle attack, as the thin-client's /etc/ssh/known_hosts is going over a shared NFS/NBD connection. so it can't *securely* determine that the server is actually the server you think you're connecting to. As a conclusion : NFS and X are unsecure protocols, that can be used in a controlled environment, where you know that one can't plug a laptop as he wishes... Ssh, however, is secure, and relies on private/public keys, so knowing the public environment (the client) won't give access to the admin private informations (private key). as long as you don't export private *host* keys over insecure methods, yes. :) live well, vagrant -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _ 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 Lenny backport ltsp-server* package regressions?
On Wed, Oct 07, 2009 at 06:07:51PM +0100, Andy S wrote: Installing on Debian Lenny based system (Mepis 8.x) using Lenny-backports for newer ltsp packages (as per: http://wiki.debian.org/LTSP/Howto/Lenny-With-Backports ) which install ltsp-server*_5.1.1.85-1_all and ldm-server_2.0.45-1_all (needed to edit apt-pinning to get ltsp-server* packages to install..??) it uses the output of: lsb_release --codename --short to look for ltsp-build-client plugins in: /usr/share/ltsp/plugins/ltsp-build-client/ so if lsb_release returns some value other than Debian, you might be able to make a symlink in the plugins dir that points to Debian, and configure the mirrors to use mepis with the --mirror and --*-mirror options. good luck. live well, vagrant -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _ 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] saned setup ltsp5
On Mon, Oct 26, 2009 at 01:19:47PM -0500, John McMonagle wrote: I recently set up a scanner in ltsp5 using debian lenny and ltsp backports for lenny. glad to hear it! I installed sane-utils that sets up saned as a daemon. This works fine but it starts up saned on all workstations. On ltsp 4.2 there was a method to only start up inetd with saned support on only the workstation with the scanner. Is there any way to get saned enabled only on the workstations with a scanner? configure the global default in /opt/ltsp/i386/etc/lts.conf to disable scanner support, and enable it on the thin-clients that have a scanner. for a machine with mac address 00:f4:56:b3:f8:99, like so: [default] SCANNER=false [00:f4:56:b3:f8:99] SCANNER=true that *should* work. live well, vagrant -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _ 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] Using ldm standalone ?
On Sat, Nov 28, 2009 at 07:32:38PM +, Tim Day wrote: I see there's an ldm package in Lenny, completely separate from the ltsp-client packages. If I install it on my client machine, can someone give me some hints how I would go about replacing gdm with it and configuring it to point to my LTSP server ? (Is it selectable via Debian's alternatives system as I believe xdm is ?) ldm doesn't by default have an init script like gdm/kdm/xdm/wdm, since it was intended to be started from ltsp's init scripts. so you'll need an init script, or to start it directly from /etc/inittab. there's an example init script in /usr/share/doc/ldm/ that i did years ago as a proof of concept, though i suspect the syntax for ldm has changed somewhat. the init script will need to export a handful of variables that you'd typically get from lts.conf. take a look at /usr/share/ltsp/screen.d/ldm to get an idea for some of those variables. maybe even writing a wrapper script around the screen script would be the way to go. good luck, it's an adventure! live well, vagrant -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _ 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] pointer black with 2008 R2
On Mon, Jan 04, 2010 at 06:26:51PM +, Chris Roberts wrote: On Monday 04 Jan 2010, David Burgess wrote: This sounds like a problem that I have seen with via and openchrome drivers, and that the workaround was to set the following in xorg.conf [Device] section: Option SWcursor true To do this via lts.conf would be something like: X_OPTION_01 = \SWcursor\ \true\ X_OPTION_01 should be supported. gets a little tricky with exactly how to quote the characters, but that looks right to me. My only concern would be that xorg.conf doesn't seem to be used these days, and I can't remember how to resurrect it for specific clients CONFIGURE_X = True/False? Anyone? recent versions of ltsp (approximately 5.1.41+) will automatically set CONFIGURE_X = true if you specify other options that need an xorg.conf to be generated. live well, vagrant -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _ 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] backports for Lenny amd64?
On Thu, Jan 14, 2010 at 07:30:23PM -0500, Rob Owens wrote: Are there any backports of the latest LTSP stuff available for Debian Lenny on an amd64 architecture? not yet, although the server-side stuff shouldn't need any changes; you should be able to use the ltsp-server*, ldm-server and ltspfs packages from squeeze or sid. if you're building an i386 chroot, then you can just use the i386 packages for the chroot as you would for usual ltsp backports http://wiki.debian.org/LTSP/Howto/Lenny-With-Backports by additionally specifying the arch: ltsp-build-client --arch i386 --foo --bar if you're doing something that actually needs an amd64 chroot(fancy fat clients with tons of ram?), i'm hoping to get ltsp versions uploaded to backports.org someday, which may likely include amd64. you could always grab the backported sources yourself and re-build the packages from source, too. i'm fairly certain that the current ltsp packages are trivially backportable, as in they only need to be rebuilt. hmmm... i should make a server that does that automatically... good luck! live well, vagrant -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _ 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] localapps on debian lenny
On Sat, Feb 27, 2010 at 09:50:02PM +0100, SZABO Zsolt wrote: Is there a howto for setting up localapps with debian lenny's ltsp-server? The one at http://wiki.ubuntu.com/ is applicable? There is no localapps wrapper script in /usr/share/doc/ltsp-server/example dir... Could the script of ubuntu be applicable? you'll need backported ltsp packages from backports.org. ltsp-build-client --pin-dist lenny-backports --pin-packages ltsp-client ltsp-client-core ldm ltspfsd ltspfsd-core --extra-mirror 'http://backports.org/debian lenny-backports main' ltsp 5.2 has much simpler commandline options for backports, and i'll upload it to backports.org as soon as it hits testing... with updated ltsp versions, the ubuntu documentation should mostly work, although you probably don't need to run ltsp-update-image, as debian doesn't use NBD by default. additionally, i need to update the instructions at some point: http://wiki.debian.org/LTSP/Howto/Lenny-With-Backports live well, vagrant -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _ 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] Bypass Autologin
On Fri, Mar 19, 2010 at 07:54:55PM -0400, Mark Ehle wrote: I just upgraded the public catalog LTSP system we have at the library I work at and am really liking the LDM stuff. But there is one thing that I used to be able to do on the old system that I don't know how to do now. Is there a way to bypass the autologin so that you can log in with another user on a thin client? If not, no big deal, but I used it on the old system to administer from time to time. in lts.conf: LDM_GUESTLOGIN=True LDM_LOGIN_TIMEOUT=10 will display a login as guest button, but allow an alternate username to be specified, and after 10 seconds will autologin. live well, vagrant -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _ 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] possible errors in manual concerning xrandr parameters
On Mon, Mar 29, 2010 at 05:28:38PM -0500, P. Scott DeVos wrote: In the pdf version of the LTSP Manual on sourceforge, the xrandr parameters are listed as XRANDR_OUTPUT_01 ... XRANDR_OUTPUT_09 etc. Nothing was working for me so I examined the xinitrc.d/I10-xrandr script to see what was going on. It took me quite a while before I noticed that the script expects the parameters to be XRANDR_OUTPUT_0 ... XRANDR_OUTPUT_8 etc. good catch! thanks! How would a user go about requesting a modification to the manual so it matches the expectations of the script? posting here works. :) i noticed all of the XRANDR_* variables needed this fixed. committed to bzr: http://bazaar.launchpad.net/~ltsp-docwriters/ltsp/ltsp-docs-trunk/revision/106/lts.conf.xml live well, vagrant -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _ 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] Xfce, Thunar: Localdev
On Sun, Apr 25, 2010 at 03:04:49PM -0300, Osvaldo Filho wrote: ubuntu 10.04 x64 with clients i386 xfce4 and thunar I copied kde-desktop-icons to the /etc/ltspfs/mounter.d: nothing! ... kde-desktop-icons is executable. yes, it should go in /etc/ltspfs/mounter.d on the server and be marked executable. The pendrive (usb stick) is mounted on: /tmp/.lab4-ltspfs/usbdisk-sda1 this sounds like it didn't mount properly- it should be mounted in /media/lab4/usbdisk-sda1. the mount in /tmp should be temporary, so something is broken there. can you try with another user? another usb stick? even before I make the copies. are you saying before you tried to configure kde-desktop-icons it had the mount in /tmp already? before trying to get the kde-desktop-icons hook to work properly, it would need to sucessfully mount /media/USERNAME/DEVICENAME. good luck. live well, vagrant -- _ 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] HP t5325, ARM, gPXE
On Wed, Apr 28, 2010 at 09:58:01AM -0600, David Burgess wrote: If anybody has any more ideas I would love to hear them. This machine is pretty much for experimental purposes, so I'm curious to see what I might try to get ltsp going on it. Thanks for the pointers, Oli. i'm curious too! on debian squeeze you can do cross-architecture armel builds using qemu. i'm pretty sure ubuntu has something similar, though the details may be a little different. install relevent ltsp and qemu packages: apt-get install ltsp-server qemu-user-static figure out what kernel you need: http://packages.debian.org/search?arch=armelkeywords=linux-image build your armel ltsp chroot with specified kernel package: ltsp-build-client --arch armel --kernel-packages linux-image-$KERNEL_FLAVOR then all you need to do is figure out how to network boot... i've tested it last summer using a sheevaplug(network boot), and more recently using qemu-system-arm(manually specifying kernel and initramfs). i haven't had access to any real hardware, so haven't really been able to test much recently. live well, vagrant -- _ 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] don't run ltsp-update-image on debian (usually)
On Thu, Apr 29, 2010 at 11:15:33AM +0100, Chris Roberts wrote: On Thursday 29 Apr 2010, Wim De Geeter wrote: No we use nfs, But it is still really not clear to me when to use ltsp-update-image So I thought that every time you add some packages in the chroot you need to update your ltsp-update-image No, with Debian and NFS you never use this command, delete it from your mind. Indeed I think you probably need to remove the image it has created, which I think is something like /opt/ltsp/images or something like that. no *need* to remove it, other that the relatively small amount of wasted disk space and confusion of having it around. There must be a lot of Debian LTSP users diligently running this command, could it not be modified to check for whether nfs/nbd is in use and politely educate the user? i don't really see any clean way to do this, as with debian (and presumably ubuntu) you can run NFS and NBD LTSP environments on the same server. there are also options to use NBD without using ltsp-update-image, and running ltsp-update-image will clobber it, and recent versions will rewrite a bunch of configuration files for good measure. there's no simple way to detect which of these scenarios is in use. i suppose i could add a configuration file that causes ltsp-update-image to exit, and explains how to change the behavior... in short, if you don't want to switch to NBD, don't use ltsp-update-image. just don't. ugh. live well, vagrant -- _ 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] Client unable to login to server
On Thu, Jul 08, 2010 at 02:59:07PM +0200, Krzysztof Paliga wrote: SSH seems to ignore clients /etc/ssh/ssh_known_hosts, where the ltsp-update-sshkeys actually puts the keys... I had to copy it to clients /root/.ssh/known_hosts... Is this to ment be that way? that sounds most unusual. did you run ltsp-update-image after running ltsp-update-sshkeys the first time you tried? live well, vagrant -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _ 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] Localdev working only to some extend in Debian 5.2 backports
On Tue, Jul 20, 2010 at 03:46:08AM +0200, JF Straeten wrote: This evening, I tried to upgrade my LTSP server to 5.2 with Debian backports. hrm... we've got it working to some degree at freegeek, though not extensively used. so i don't know if there are corner cases where it doesn't work. After upgrading the server, I've created a new chroot, with the backports too, as stated in http://wiki.debian.org/LTSP/Howto/Lenny-With-Backports giving this output to ltsp-info[1]. But the localdevs only work to some extend : - CD/DVD doesn't work at all (nothing happens on pluging drive/inserting media/removing/etc) ; i've had some weird issues with CD/DVD drives, but only on squeeze. seems like it will spuriously create CD insertion and removal events for no apparent reason... - USB devices are mounted in /tmp/.user-ltspfs/device ; corresponding mountpoints are created in /media/USER/DEVICE ; but the bind to there is never done. (Note : devices are working normaly in /tmp though : I'm able to write/read files on them). that is odd... i haven't seen that behavior since debian etch... so i don't have a lot to say... my tests seem to work ok. *sigh* live well, vagrant -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ _ 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] Login with wrong password gives no response from server
On Mon, Jul 19, 2010 at 09:28:17AM +0100, Chris Roberts wrote: I realised that I have been putting up with a small irritation in LTSP, assuming that it is a general issue, rather than being specific to me. When my users get their password wrong, they get a No response from server, restarting error. This then leads the user to bother me, thinking that the server is down. They do generally get used to this over time, but it does make them feel that the system lacks polish. indeed. this is largely due to the fact that LDM has a somewhat hackish way of logging in. there has been some work on moving toward libssh2 (or something similar?) which has promise for an improved ssh interaction, but haven't heard much recently. This problem is compounded when the users are prompted to change their password, as it always seems to give this error, leading them to think that they haven't succeeded in changing their password. They then try fruitlessly to use their old password as they know that they haven't succeeded in changing it. I then get them to try their new password and of course that works. I have some users who have yet to successfully change their password on their own, which does add to my workload. i hear ya. I have tried googling, but, whilst there are loads of hits for ltsp \no response from server\ of course these are not related to this more general issue of the message itself being rather misleading. So is this just a general problem, or just Debian, or just us? If it is a general problem, is there a solution or workaround? Should I be logging a bug? i think it's a problem in LDM's design. originally, we tried to parse the output of the ssh session, but that proved impractical as each distro, and even different versions of the same distro, provided different output. in theory, the current design passes whatever text ssh spits out through to the user, but in practice, failed password attempts are pretty sparse on the feedback. i think that part worked better when we didn't limit the number of password tries to 1. live well, vagrant -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ _ 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] LTSp Server on LXC container.
On Mon, Aug 02, 2010 at 11:02:09PM -0300, Osvaldo Filho wrote: I want to jail users to a LTSP server. I thought it would be easy to LXC. But I'm having problems. - the ltsp-build-client - arch i386 does not end. well, ends badly. :) r...@localhost:/opt# ltsp-build-client --arch i386 ... I: Extracting upstart... I: Extracting util-linux... I: Extracting zlib1g... error: LTSP client installation ended abnormally off the top of my head, my guess is that LXC doesn't allow you to create device nodes in the chroot's /dev, or some similar restriction to prevent the container from doing evil... try to see if it fails when you debootstrap manually from within the container: debootstrap DIST $(mktemp -d) MIRROR DIST: lenny, squeeze, lucid, hardy, etc. MIRROR: http://ftp.us.debian.org/debian, http://us.archive.ubuntu.com/ubuntu ... live well, vagrant -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _ 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] default session
On Wed, Aug 04, 2010 at 08:42:59AM +0800, james wrote: I want my thin clients to run an icewm session by default. Everything works except that I cannot specify the default session for a new user - I have to select the session at the login menu. on debian/ubuntu systems: update-alternatives --config x-session-manager and/or: update-alternatives --config x-window-manager live well, vagrant -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _ 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] LTSp Server on LXC container.
On Tue, Aug 03, 2010 at 05:06:42PM -0300, Osvaldo Filho wrote: Thank you. I did remove the restrictions. Now it is installing. that might be a big security flaw with your LXC install, then, as containers will be able to access the server's devices directly referencing those device nodes. What devices are needed for ltsp? at run-time, udev usually handles the devices, so you need a very minimal set in the chroot itself. debootstrap (the tool used to create the initial LTSP chroot for debian/ubuntu) creates some minimal set of devices, and apparently more than are allowed by LXC by default. i don't know how to change that, off the top of my head. live well, vagrant -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _ 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] firefox localapp chinese characters
On Thu, Sep 02, 2010 at 11:16:51AM +1000, Michael Pope wrote: I've just installed firefox in my chroot section for my clients. I'm using Ubuntu 10.04 as my server. The problem is I have a requirement to view Chinese characters on the clients and firefox on the client will not show these characters. The server copy of firefox will. what fonts are installed on the server: dpkg -l 'ttf-*' ... After each command I rebuilt the image and tested it on a thin client. I'm running out of ideas, could anyone give me a hint as to what font or configuration I require to display all the Chinese characters in firefox running as a localapp? on debian (and probably ubuntu), i'd try ttf-arphic-uming. i don't know if this is a good set of characters, it seems to at least generally render most chinese characters. live well, vagrant -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _ 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] LTSP and Audio CD's
On Tue, Aug 31, 2010 at 04:27:22PM -0700, Joshua Riffle wrote: I'm working with Ubuntu 10.04 as a test only at this point in hopes of creating an office environment. My understanding is that an audio CD inserted in a thin client will not mount because audio CD's are not handled the same way data CD's are. Does anyone know a fix or workaround for this issue or if there is any fix indicated for future releases? Thanks for your input, for debian (and probably ubuntu) there's the cdfs-src package, which you can use to build a kernel module that renders audio CDs as .wav files. unfortunately, last i tried it (a couple years ago) it was a little unstable. live well, vagrant -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _ 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] LDM Login Language
On Fri, Sep 24, 2010 at 09:37:00AM +0200, Martin Gabel wrote: I have a problem with the LDM Language. The Login Options are all in english but the Keyboard Layout is german. The parameter LDM_LANGUAGE seems not working. it's a little confusing, but LDM_LANGUAGE sets the locale for the logged in session, not for LDM itself. if you want it to use a different language for LDM's user interface, add to lts.conf: LANG=en_US XKBLAYOUT is also not working for me. this i don't know... Is there any other way to change the keyboard layout at the ldm login screen? I have installed the Server with the english language package. you installed the english language package before you built the LTSP chroot? is the language package present in the chroot: dpkg --root=/opt/ltsp/i386 -l FOO-langpack (i don't know ubuntu language configuration so well) System: Ubuntu 9.10 LTSP : 5.1.90 lts.conf: #acerlts4 [192.168.0.104] LDM_SERVER= xxx1,xxx2 LDM_DIRECTX=True LDM_LANGUAGE=en_US XkbLayout=us LOCALDEV=True XSERVER=nvidia SOUND=True minor note: LOCALDEV and SOUND are true by default if the appropriate software is installed. good luck! live well, vagrant -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _ 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] ltstp session dispatching problem: solved.
On Fri, Oct 01, 2010 at 03:24:41PM +0200, Thierry Dumont wrote: Yesterday I asked on this list about a problem of load balancing with get_hosts. We solved it. Actually, the script ldm in /opt/ltsp/i386/usr/lib/ltsp/screen.d says: # Server scalability. If there exists a /usr/share/ltsp/get_hosts file, then if [ -x /usr/share/ltsp/get_hosts ]; then LDM_SERVER=$(/usr/share/ltsp/get_hosts) # Loop though each of the hosts, and get their ldminfo and there where no get_hosts in /usr/share/ltsp/ (as seen from the client). So, we put get_hosts there, and put a link in /opt/ltsp/i386/usr/lib/ltsp: cd /opt/ltsp/i386/usr/lib/ltsp ls -l lrwxrwxrwx 1 root root 26 2010-10-01 10:48 get_hosts - ../../share/ltsp/get_hosts Then everything is ok. the link shouldn't be necessary. it really should just go in /opt/ltsp/i386/usr/share/ltsp. But the documentation is false. indeed. fixed in bzr: http://bazaar.launchpad.net/~ltsp-docwriters/ltsp/ltsp-docs-trunk/revision/116 thanks! live well, vagrant -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _ 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] howto get client hostnames into servers /etc/hosts?
On Fri, Oct 01, 2010 at 11:48:21PM +0200, Lorenz Wenner wrote: i am running LTSP 5.2 on Debian squeeze. glad to hear it :) It seems to me, that nbd instead of nfs is in use. can anybody confirm that? I am just wondering, because i heard, that usually debian uses nfs. unless you manually configured NBD, Debian LTSP defaults to using NFS. i wonder if running ltsp-update-image somehow sets the default to switch to NBD? reading it quickly, i don't see where it would. running ltsp-update-image is completely unnecessary with NFS based setups such as Debian, but a lot of documentation suggests running it. ...and now for something completly different: is there an easy way to get the clients hostnames into the servers /etc/hosts? I know that the clients do get an individual hostname e.g. ltsp22, for client with ip address 192.168.0.22. uncommenting the get-lease-hostnames true; line in /etc/ltsp/dhcpd.conf resulted in clients that would not boot, which is logically, because there is no dns-server providing any hostnames for the ltsp clients. it surprises me that they wouldn't boot at all in that case... So my question is: where (and at what time in the boot process -- maybee even after user login?) do the hostnames -- e.g. ltsp22 -- come from and how can i get them from there into the servers /etc/hosts? it happens in the initramfs: /opt/ltsp/i386/usr/share/initramfs-tools/scripts/nfs-bottom/ltsp it is controlled by the HOSTNAME* parameters in lts.conf: apt-get install ltsp-docs ; man lts.conf for a network with ip addresses ranging from 192.168.0.1-192.168.0.254 (i.e. netmask of 255.255.255.0), you'd get ltsp1-ltsp254 for auto-generated hostnames... so a simple for loop could add them to your server's /etc/hosts: for x in $(seq 1 254) ; do echo 192.168.0.$x ltsp$x /etc/hosts done or just set up DNS. as time has moved on, and we've configured more and more workarounds, i'm wondering why we've avoided configuring DNS for LTSP environments. i guess it's just one more service to have to configure... live well, vagrant -- Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d _ 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] Chroot doesn't have Internet Access
On Mon, Oct 18, 2010 at 12:33:25PM -0400, Joseph Bishay wrote: On Mon, Oct 18, 2010 at 11:53 AM, Alkis Georgopoulos alk...@gmail.com wrote: Try this: sudo cp /etc/resolv.conf /opt/ltsp/i386/etc/ Wow that worked perfectly! Is this something that everyone has had to do in the past or a new issue? I didn't see it referenced in the documents/wiki anywhere and it's sorta crucial no? it comes up periodically and should be documented somewhere (here's to list archives, at the very least). it happens when people build the LTSP chroot and later change networking on the server. live well, vagrant -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _ 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] Distro and general setup questions
On Fri, Oct 29, 2010 at 10:23:07AM -0500, Donny Brooks wrote: The test will consist of only a handful of PC's. Eventually I would like to, pending successful testing, roll this out to all 150+ users across the state. Here is a breakdown of what we have if it helps also: Main campus (all 1GB fiber between buildings and 100MB ports per pc): 60 this part should be easy with an LTSP server... Satellite campus (connected to main campus via 802.11G wireless bridge) 8 Remote location 1 (1.5M x 256k aDSL): 6 Remote location 2 (T1): 6 Remote location 3 (T1): 4 Remote location 4 (3M x 512k cable): 7 Remote location 5 (3M x 512k cable): 5 Users on various other networks (home dsl, and other varying networks): 4 the rest of these won't work so great with a central LTSP server; LTSP will download the OS over the network, and the running session (i.e. every mouse movement, click, etc.) also goes over the network, so it would probably feel painfully slow, if it worked at all. you could set up an LTSP server for each location, though then you'd need to figure out how to keep the homedirs in sync across servers (if people would access via multiple locations). this wouldn't be LTSP at this point, but you could log into the LTSP server using something like NX or VNC from the remote locations. you'd still need an OS, though. all of the above could be mixed and matched a bit... good luck! :) live well, vagrant -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _ 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] changed server ip, no login
On Fri, Nov 12, 2010 at 07:01:23PM +0100, vla wrote: Am 04.11.2010 23:52, schrieb ltsp-discuss-requ...@lists.sourceforge.net: what i did: i clone a working ltsp-server, change its ip-address, execute ltsp-update-sshkeys and ltsp-update-image, get a logon screen on its clients but cannot login. workaround: on client, i change to the console, login as root, delete /root/.ssh/known_hosts, switch back to graphical login and can log in. so i deleted /opt/ltsp/i386/root/.ssh/known_hosts, executed ltsp-update-image and can now log in on clients. my next question, should i generate a new known_hosts file for root and how? no, you shouldn't. best not to have a /root/.ssh/known_hosts. ltsp-update-sshkeys updates /etc/ssh/ssh_known_hosts, and your /root/.ssh/known_hosts was interfering and giving conflicting information. maybe ltsp-update-sshkeys should warn if there is a /root/.ssh/known_hosts file, though maybe there are valid use-cases for that... live well, vagrant -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _ 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] localdev support on debian squeeze
On Tue, Nov 16, 2010 at 04:10:05PM -0200, Eduardo Moreira - IMA wrote: When was connected a pendrive in my ltsp server, appear in all stations an error message. i'm not sure how to restrict that from happening. what desktop environment are you running? When connected a pendrive in some station, nothing appear on desktop, and wasn't mounted in filesystem, staying unavailable to user. are your users in the fuse group? log in as a user, open an xterm, and run: groups In lts.conf exists the parameter setting LOCALDEV=true where is your lts.conf? if you're using the defaults, it should be in /opt/ltsp/i386/etc/lts.conf. I use LTSP 5.2 version with Debian 6 Squeeze. What's happened? will need a more information to know. on your server, please run: ltsp-info --verbose that will give some more useful information to help troubleshoot... live well, vagrant -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _ 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] OT!! Re: will Wayland affect LTSP?
On Wed, Nov 17, 2010 at 11:50:35AM +0100, Xavier Brochard wrote: This thread is a bit strange: currently there is nothing as a wayland only application. Nothing can prevent you tu run an X server. I don't understand why everyone is scared. i think people are understandably worried about seeing problems like firefox and openoffice's pixmap caching bugs, which were (are?) crippling for LTSP environments. because many applications are being developed to be more desktop focused, serious bugs impacting network functionality sometimes linger or even proliferate. obviously X didn't prevent those sorts of bugs from becoming a problem and for all i know, the limitations of X actually lead people to implement such bugs. but fear that (most) development efforts will move towards something that completely drops support for network transparency is not unreasonable for a project that absolutely relies on that feature. even though X is still there, if developers are no longer working on it X may get stale and dysfunctional... the capacity to re-use older hardware has long been a strength of LTSP, and like any new project, wayland doesn't yet support much in the way of hardware, so that's another concern that will hopefully improve over time. since the LTSP community depends on network transparency, i think it's only smart to raise those concerns and work together to address them. good thing we've been working on fat clients. :) live well, vagrant -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _ 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] screen resolution after boot
On Thu, Nov 18, 2010 at 07:54:50AM +0100, Helmut Lichtenberg wrote: Gideon Romm schrieb am 17. Nov 2010 um 15:38:20 CET: The lts.conf params should be: XRANDR_MODE_0 NOT XRANDR_MODE_01 (note the single digit. It is in the same style as the old X_MODE_0) Arrgh! This took me at least 2 days of testing. :^( I simply followed the man page of lts.conf (either with the installed manpage of the package or according to http://manpages.ubuntu.com/manpages/lucid/man5/lts.conf.5.html). ... Anyway, thanks a lot for your help, Gideon. Now it works. Who can make sure to get the man pages corrected? you'll have to read the manpage from newer versions of ubuntu- it didn't get fixed upstream till late march of this year, which was too late for lucid. not sure what the process for getting updated documentation into lucid is... live well, vagrant -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _ 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] LTSP for exam setting at school - r ésumé
On Wed, Nov 17, 2010 at 10:37:28AM -0800, sm8ps-ltsp...@yahoo.com wrote: H: (Alkis/Frédéric) Fatclient+iptables+D: should handle the raised issues. if you wanted to go even further, you could set up the networking to use netmask 255.255.255.255, which means all the clients would refuse to talk to each other directly- they would only go through the gateway... then you could just have the firewalling rules on the server (or both; on the server and the clients). still might allow packet sniffing, but if they've gotten that far, you're in trouble. live well, vagrant -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _ 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] LDM_LOGIN_TIMEOUT on Ubuntu 10.04
On Fri, Nov 05, 2010 at 04:13:59PM -0400, Arthur Wiebe wrote: [00:80:64:86:FA:50] CONFIGURE_X=True X_CONF=/etc/X11/xorg-c90lew-single.conf LDM_AUTOLOGIN=False LDM_LOGIN_TIMEOUT=5 LDM_USERNAME=kiosk1 LDM_PASSWORD=password What happens with this config is that once the thin client is finished booting it starts counting down the 5 seconds as expected, but then nothing happens. It doesn't even look as if it tries to login. you also need to specify LDM_GUESTLOGIN=true i'll add that to the docs for future versions... live well, vagrant -- Increase Visibility of Your 3D Game App Earn a Chance To Win $500! Tap into the largest installed PC base get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _ 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] lbmount problem and other fun
On Fri, Dec 10, 2010 at 02:09:00PM +, Ben Green wrote: I've got ltsp-5.2.4 on Debian Squeeze up and running, it's running great... except... USB local devices are not working. Some stuff is firing, but it seems that lbmount doesn't seem to be doing it's job. The setup is as follows, Linux-Vserver guest as the host LTSP server. AMD64 install with a i386 chroot. ltspfs uses fuse, and it seems like there may be some additional vserver configuration needed to use fuse: http://www.mail-archive.com/vser...@list.linux-vserver.org/maillist.xml that's a post about using sshfs in a vserver, which also uses fuse. perhaps it is relevent for ltspfs also. there are also more recent posts: http://lists.planet-lab.org/pipermail/devel/2008-August/002920.html http://www.paul.sladen.org/vserver/archives/201003/.html http://www.paul.sladen.org/vserver/archives/201003/0003.html alternately, there *might* be ltspfs-specific 32-bit/64-bit incompatibilities, but my memory is a bit hazy on that. live well, vagrant -- Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _ 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] lbmount problem and other fun
On Sat, Dec 11, 2010 at 08:31:54AM +, Ben Green wrote: Quoting JF Straeten jfstrae...@scarlet.be: On Fri, Dec 10, 2010 at 10:24:02PM +, Ben Green wrote: Vagrant's message gives me the idea to test with a full 32bit VServer, and see if it makes a difference. Perhaps I will have time to do so this week-end and report results to the list. wouldn't hurt... even if it's not likely, if it does work that would certainly give direction into what to look for. Thinking about it, I don't think it will be a 32/64 issue, as '/tmp/.jfs-ltspfs /tmp' does get mounted. i'm not so sure https://wiki.ubuntu.com/DebugLocalDev step 4 is current. ubuntu-isms aside, it would also need to get the ltspfs token, which is a security feature added later, which it needs to pull from the running X session. maybe running: ltsp-localapps xterm su - export DISPLAY=:7 and then running the ltspfsmounter command: ssh -X -S /var/run/ldm_socket_vt7_192.168.0.254 192.168.0.254 /usr/sbin/ltspfsmounter /tmp add The bit that's failing is the bind mount, which is lbmount's job, and that shouldn't be a problem i.e. there is no cross arch library interaction there. I'm going to read the lbmount source and say hello in the #vserver channel see is there's any useful leads there. another thing is to see if vserver has issues with: mkdir -p /foo/ /bar/ mount -t tmpfs tmpfs /foo/ mount --move /foo/ /bar/ which sounds like the point where it's failing. that's basically what lbmount is doing: mount --move /tmp/.ltspfs-user/mountpoint /media/user/mountpoint another wild guess, lbmount should also be setuid, so there may be issues with that as well. live well, vagrant -- Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _ 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] lbmount problem and other fun
On Fri, Dec 10, 2010 at 10:24:02PM +, Ben Green wrote: Quoting Vagrant Cascadian vagr...@freegeek.org: alternately, there *might* be ltspfs-specific 32-bit/64-bit incompatibilities, but my memory is a bit hazy on that. Thanks for all that. I have fuse working fine in the guest, and all the relevant ccapabilities are set too. All users are in the fuse and plugdev groups. have you actually gotten another fuse filesystem, such as sshfs, to work? just want to make sure. plugdev group is meaningless, also. just the fuse group is needed. Remote usb disks do actually get mounted, it's just that they don't get bind mounted to /media/user/ as they should and hence don't get shown on the desktop. There are also remove cleanup issues, but I'd be happy to get to a desktop item to start with. you can actually read the files in /tmp/.ltspfs-user/* ? if so, then i guess fuse wouldn't be the issue anymore. live well, vagrant -- Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _ 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] pastebin?
On Sun, Dec 12, 2010 at 11:41:18AM -0500, Joseph Bishay wrote: I can't remotely help with your technical issue :) , but I can propose a solution to pasting/attaching things to the email. I've found it useful to use the pastebin located at: http://ltsp.pastebin.com/ Paste what you want everyone to see, select the relevant Syntax, expiration date, etc. and then submit! It will then give you a unique URL which you can include in the email so everyone else can see. on the other hand, this means the mailing list archive doesn't contain all of the content of the conversation, and if the post expires or ltsp.pastbin.com disappears for some reason, we loose that information, and future people with the same issues might have a harder time finding the post or reconstructing the solution. we're creating a repository of hopefully useful information for the future LTSP users :) i think a pastebin is more appropriate for quick troubleshooting sessions in irc than in a mailing list discussion. live well, vagrant -- Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _ 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] LTSP fat clients vs. Debian Live netboot
On Sun, Dec 12, 2010 at 07:05:29PM -0500, Rob Owens wrote: I haven't tried using LTSP fat client mode yet -- ltsp-server 5.2.4-2 in Debian backports doesn't seem to support that yet. it definitely has support for it, just not an explicit ltsp-build-client commandline option: ltsp-build-client --late-packages $desktop_environment_or_window_manager $other_apps alternately, after you've already built an LTSP chroot: sudo ltsp-chroot apt-get install $desktop_environment_or_window_manager $other_apps in either case, then set LTSP_FATCLIENT=true in lts.conf. that's pretty much it. But today I tried using a netboot image from Debian Live, and it was pretty nice. I'm wondering how it compares to an LTSP fat client. The Debian Live solution works like this: Download or build your own live image (the same kind of live image that can be used on a USB or CD). Share the image, read-only, over NFS. Set up tftpboot and dhcp. Then your clients will download the live image over the network and use local resources to run it. i *think* debian-live loads the whole OS into ram, whereas LTSP's fatclient approach only loads parts over the network it actually uses when it uses it. both approaches have advantages and disadvantages, namely in how much server vs. local resources it takes. By default you are automatically logged in as the live user, this is more like an LTSP kiosk setup. but you can set it up to boot to a login manager. I'm going to try mounting /home over NFS and do user authentication via LDAP (I'll report back when I have something to report). with LTSP fat clients it essentially uses ssh to authenticate. scotty's been working on beautiful mastermind schemes to make that elegantly. there's a lot of similarity between debian-live and Debian LTSP, and hopefully we'll use more and more common tools. live well, vagrant -- Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _ 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] LTSP fat clients vs. Debian Live netboot
On Tue, Dec 14, 2010 at 09:10:55PM -0500, Rob Owens wrote: On Sun, Dec 12, 2010 at 08:10:13PM -0800, Vagrant Cascadian wrote: On Sun, Dec 12, 2010 at 07:05:29PM -0500, Rob Owens wrote: I haven't tried using LTSP fat client mode yet -- ltsp-server 5.2.4-2 in Debian backports doesn't seem to support that yet. it definitely has support for it, just not an explicit ltsp-build-client commandline option: ltsp-build-client --late-packages $desktop_environment_or_window_manager $other_apps alternately, after you've already built an LTSP chroot: sudo ltsp-chroot apt-get install $desktop_environment_or_window_manager $other_apps in either case, then set LTSP_FATCLIENT=true in lts.conf. that's pretty much it. This is not working for me. I keep getting logged in as a thin client -- I can run software that is installed on the server but not in the chroot. just tested and it works for me with a lenny chroot with backports (on a squeeze server, as well as squeeze for both chroot and server). i also have a few in production that are lenny+backports servers with lenny+backports chroots, and those work fine also. Is there maybe another step to make this work? more likely your LTSP chroot doesn't have the backported versions of ltsp-client*, ldm, and ltspfsd*: ltsp-info if the versions of ltsp-client*/ltspfsd*/ldm don't include ~bpo50, you probably didn't specify to use the backports when creating the ltsp chroot. somewhat more detailed instructions here: http://wiki.debian.org/LTSP/Howto/Lenny-With-Backports live well, vagrant -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _ 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] LTSP fat clients vs. Debian Live netboot
On Tue, Dec 21, 2010 at 09:06:22PM -0500, Jonathan Carter (highvoltage) wrote: On 21/12/10 08:20 PM, Rob Owens wrote: I had some success today. I got a fat client working after addressing two issues: 1) Booting would hang on network-manager and/or network-manager-dispatcher. I removed those packages and then: 2) I'd get an error about the ownership of /var/lib/gdm, which would result in me getting dropped to a text login. In the chroot, /var/lib/gdm had the correct ownership. I think the issue may be that on my server, gdm has a different uid and gid than the chroot. I fixed that problem by removing gdm. ...snip... Vagrant, did Debian strip away the fat client plugin switches? In Ubuntu the above is taken care of for the user. Any reason we can't have that in Debian too? each distro has it's own plugins, and the fatclient plugin is ubuntu-specific, and i've never taken the time to generalize it, or at least make it work for debian. the fatclient chroots i've built at freegeek so far didn't include network-manager or gdm, so i guess i wasn't aware there was much need for such a plugin. :) live well, vagrant -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _ 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] Sound setup in LTSP5.2
On Sat, Jan 29, 2011 at 01:38:24PM -0500, Mark wrote: I just installed LTSP in a multi-use server to provide services to about 4-5 clients. It's a box stock install on a debian squeeze distro. I'm using NFS and LDM managers. I can boot and login just fine with all my users, but no sound on any clients. I have searched around for sound howto's, but those I've followed have just enabled me to play sound on the server, not on the clients. can anyone explain exactly how the sound system works, and/or provide a howto or troubleshooting to get it working? have you read /usr/share/doc/ltsp-server/README.Debian.sound ? it describes how to configure alsa to use pulseaudio over the network. live well, vagrant -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _ 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] errors while updating chroot
On Fri, Feb 04, 2011 at 02:16:11PM -0700, David Burgess wrote: Using Ubuntu 10.04 and following the guide here: https://help.ubuntu.com/community/UbuntuLTSP/UpdatingChroot i'd also recommend using the ltsp-chroot utility rather than chroot /opt/ltsp/i386. it handles setting LTSP_HANDLE_DAEMONS=false and possibly other things needed in the future, and has some other useful options like mounting the package cache. live well, vagrant -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _ 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] Reading UDF cdroms on clients
On Wed, Jan 19, 2011 at 11:07:11AM +1100, Michael Pope wrote:
We keep getting UDF formatted cdroms at work and people cannot read them
on their LTSP clients. I can read them on the server though.
I've read somewhere that you just have to change the fstab to auto or
add UDF to it, but when I go to the chroot section there is nothing in
the fstab file.
Is it possible to get UDF cdroms working on clients?
this patch *might* work:
=== modified file 'src/cdpinger.c'
--- src/cdpinger.c 2010-02-11 01:32:53 +
+++ src/cdpinger.c 2011-02-05 00:01:10 +
@@ -116,7 +116,7 @@
if (last == CDP_CDROM_UMOUNT) {
syslog (LOG_INFO, Disk detected. Mounting);
snprintf(cmd, sizeof cmd,
-/lib/udev/ltspfs_entry add_disc %s iso9660, device);
+/lib/udev/ltspfs_entry add_disc %s iso9660,udf,
device);
last = CDP_CDROM_MOUNT;
return g_spawn_command_line_sync(cmd, NULL, NULL, NULL, NULL);
}
it does require rebuilding the ltspfs packages (or at least cdpinger).
i'm not sure if ltspfs_entry or ltspfsd will handle multiple filesystem types
specified, but it works fine with mount.
live well,
vagrant
--
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_
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] Can't choose language in LDM
On Tue, Feb 08, 2011 at 03:39:34PM +0100, Davy HUBERT wrote: i'm using ltsp on an ubuntu-server 10.04 box and i try to figure out how to provide many languages to the users. When the user arrive on the ldm screen, if we want to choose the language the only choice is default. I tried to install some language packs on the server and in the chroot but it doesn't work. Does anyone know how solve this problem ? is ldm-server installed on the server? what does running /usr/sbin/ldminfod display? live well, vagrant -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _ 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] is LDM_LIMIT_ONE_SESSION still supported under ubuntu lucid?
On Mon, Feb 07, 2011 at 01:03:04PM -0800, john wrote: I read that the proper way to kill stale user sessions is no longer gnome-watchdog but an lts.conf switch called LDM_LIMIT_ONE_SESSION However, it doesn't appear in the lts.conf man page for Ubuntu Lucid. Is it currently supported or is there another way...? it was added to ltsp-docs after lucid was released, so even though it's supported in the code, it's not in the ltsp-docs package in ubuntu lucid: http://bazaar.launchpad.net/~ltsp-docwriters/ltsp/ltsp-docs-trunk/revision/115 the version of ltsp-docs in natty seems to have this update, so you could check the manpage for lts.conf in natty, i think. i don't believe any options documented there aren't supported in lucid also; there haven't been that many changes. live well, vagrant -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _ 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] Can't choose language in LDM
On Thu, Feb 10, 2011 at 01:09:35PM +0100, Davy HUBERT wrote: Here is the output of /usr/sbin/ldminfod : root@ltsp-server:~# ldminfod language:fr_FR.UTF-8 language:aa_DJ.UTF-8 language:ar_AE.UTF-8 that looks good. But on the loggin screen the only language choice is default hmmm. do you get the same output with: nc 127.0.0.1 9571 maybe it's not configured in inetd? grep ldminfod /etc/inetd.conf if not, try: update-inetd --group LTSP --add 9571 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/ldminfod good luck. live well, vagrant -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _ 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] tftp server via inetd? debian squeeze
On Sat, Apr 02, 2011 at 05:42:32PM -0400, Rob Owens wrote: Is it still recommended to run tftpd via inetd, or to run it standalone? I ask because my upgrade from Debian Lenny to Squeeze changed my settings and tftpd is running standalone now. the tftpd-hpa maintainer changed it explicitly in version 5.0-1, closing a number of bugs: http://packages.debian.org/changelogs/pool/main/t/tftp-hpa/current/changelog#versionversion5.0-1 so i guess it was with reason. on a number of servers, i also use atftpd instead, which i think can run in either mode still. if you really prefer to run from inetd. live well, vagrant -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _ 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] ltsp@debian: Upgrade of chroot to squeeze gives nfsmount: need a path error
On Wed, Apr 06, 2011 at 09:39:44AM +0100, Rainer Stumbaum wrote: I found the regression: udhcpc is called in init-premount to get the DHCP configuration. The udhcpd used in the busybox does not ask the DHCP server for the rootpath option. Adjusting the udhcpc call in /usr/share/initramfs-tools/scripts/init-premount/udhcp with -O rootpath fixes my problem. udhcpc isn't part of the default LTSP install on Debian. there are hooks to use it if present. so apparently you've got a customized install. But this should be reported somewhere... feel free to report bugs at http://bugs.launchpad.net for ltsp related bugs, or http://bugs.debian.org for debian-specific bugs. live well, vagrant -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _ 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] ltsp@debian: Upgrade of chroot to squeeze gives nfsmount: need a path error
On Thu, Apr 14, 2011 at 08:32:37AM +0100, Rainer Stumbaum wrote: I just did a fresh ltsp-build-client --dist squeeze --mirror http://ftp.de.debian.org/debian/ and strangely enough now this setup tries to boot from the last device it finds (eth2) which is not the one it should use (eth0). At least it uses ipconfig now to get the dhcpd information. ipconfig (as used in initramfs-tools in squeeze) should ask on all available interfaces, and takes the first that gives a DHCP response... do you have your thin client on multiple networks with DHCP on every network? How can we force it to use the first device? (still under the nfsmount: need a path error-description since it shows the same error ;-) ). you can do a couple things: 1) set ipappend 2 in /var/lib/tftpboot/i386/ltsp/pxelinux.cfg/default which passes the mac address of the network card it's booting and initramfs-tools will use the interface that matches that mac address. 2) in /opt/ltsp/i386/etc/initramfs-tools/initramfs-tools.conf hard-code DEVICE=eth0. then rebuild your initramfs: ltsp-chroot update-initramfs -u and update the tftp dir(s) ltsp-update-kernels. hard-coding eth0 was the default on lenny, but typically didn't work well with multi-NIC setups if you wanted to boot from anything other than eth0. live well, vagrant -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _ 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] ltsp@debian: Upgrade of chroot to squeeze gives nfsmount: need a path error
On Fri, Apr 15, 2011 at 09:08:12AM +0100, Rainer Stumbaum wrote: Yes, that is how we do it here... we basically use LTSP as the base of our computing cluster (by uninstalling ltsp-client and installing ltsp-client-core) oh, interesting. i love to hear about LTSP being used in clever ways. :) ... dpkg -P ltsp-client apt-get autoremove apt-get install ltsp-client-core ... So we do not have to maintain a whole setup of Diskless Server setup scripts... rather than installing and removing it later, why not run: ltsp-build-client --early-packages ltsp-client-core and not install ltsp-client at all. :) How can we force it to use the first device? (still under the nfsmount: need a path error-description since it shows the same error ;-) ). you can do a couple things: 1) set ipappend 2 in /var/lib/tftpboot/i386/ltsp/pxelinux.cfg/default which passes the mac address of the network card it's booting and initramfs-tools will use the interface that matches that mac address. This is what sounds more clever... I did not know about this yet, but was wondering why the heck parameter BOOTIF was empty... i forgot to mention you'll want to configure that so that it won't get overwritten on upgrades, in /opt/ltsp/i386/etc/ltsp/update-kernels.conf: IPAPPEND=2 live well, vagrant -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _ 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] Like Sun Ray?
On Sat, May 21, 2011 at 11:16:33AM -0700, Yudhvir Singh Sidhu wrote: Totally new to thin clients. Question - How is a LTSP client connected from outside the network? you don't really. LTSP is about booting over the network. you could connect to the same server that LTSP is using with VNC, NX, or any remote access protocol supported in your host distro (Debian, Ubuntu, ...). b. Use fat clients like the new HP t5325 to either reduce server load or not use terminal server at all (the unit comes with xfce and a mozilla based browser as a stand-alone boot. you'd have to do something like this for off-site connectivity. c. Trying to reduce server load because the facility has power outages daily and the server room is a cleaned-up closet with A/C and a regular power plug. Therefore, using Supermicro Atom servers (dual core, 4GB RAM max and will be using SSD drives). And oh, only one terminal server for all 62 clients. And oh, I am expecting EVERYONE to log in in the morning, browse to the web app and open a word processing app and stay logged in all day. that's just a matter of having a powerful enough server. fat clients would dramatically reduce your need for a powerful server, though off-site remote connections are still going to use the server's resources. c. The future seems to be Arm based and many devices like the trimslice (http://trimslice.com/web/) are low-power and relatively cheap($ 200 USD). However, inviting Android onto a network may not be good for security - this is a medical facility that I'm working with. i've worked on support for installing ARM based LTSP from an i386 server, but haven't had many ARM thin-clients to test with yet. it should work as long as the hardware is supported by your host distro (Debian, Ubuntu, ...). d. Client expresses desire to have access from home. My first solution and the one which comes to mind now, is Sun Ray. They are ssh based and negotiate through firewalls and come find the mother ship automagically. The SRSS server has to be configured to somehow register each unit and then it just works. This isn't really LTSP, but simply using remote access protocols such as VNC, NX or others to connect to your server, which may happen to also be running LTSP. Pondering which solution to go with SRSS or LTSP? SRSS might kill performance and LTSP may not be able to ssh tunnel. What's a person to do? LTSP uses ssh by default for login, but booting to LTSP is typically only over a LAN. LTSP can use any protocol your distro supports. if you want a consistant environment, you could essentially install a tweaked LTSP image on a USB stick or other media, but then any time you update the image, you'd have to update all the USB sticks. live well, vagrant -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _ 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] root xterm and spinning wheel prompt upon login from terminal
On Mon, May 30, 2011 at 12:32:58AM -0700, Yudhvir Singh Sidhu wrote: I get an xterm and a spinning wheel prompt... And it sits there. But wait! it does give me an xterm. It is logged on the server in the xterm. I'm missing something obvious. And it seems to be hidden. i'm guessing you need to install some sort of desktop environment (or at the very least, a window manager). in a typical LTSP thin client environment, you'd install the relevent desktop environment or window manager on the server itself, and try logging in again. live well, vagrant -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _ 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] Slowly Moving Away from LTSP
On Thu, Jun 02, 2011 at 05:51:45PM -0700, Yudhvir Singh Sidhu wrote: So, while I stew over this apparent failure - Allz I can see upon boot is an xterm logged into my server, a splash screen background and a spinning cursor - it sounds like you don't have a desktop installed. on the server: apt-get install ubuntu-desktop to make sure it's installed: dpkg -l ubuntu-desktop you should see something like this (your version may differ): ii ubuntu-desktop 1.197 The Ubuntu desktop system live well, vagrant -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _ 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] ltspfs questions for EL6
On Fri, Jun 10, 2011 at 02:01:38AM -1000, Warren Togami Jr. wrote: I am attempting to fix ltspfs on EL6. I am comparing the contents of my ltspfs and ltspfsd packages to the Debian packages and I am confused by things I see in the filelists below. http://packages.debian.org/wheezy/all/ltspfsd/filelist /lib/udev/rules.d/60-ltspfsd.rules Is this file the 88-ltspfsd.rules as installed by make install, except the Debian package renames it for some some ordering issue? yes, although not explicitly renumbered- 60 is the default priority for udev rules on debian, and it works fine there for debian at least. http://packages.debian.org/wheezy/amd64/ltspfsd-core/filelist /lib/udev/add_fstab_entry /lib/udev/remove_fstab_entry My ltspfsd package has everything listed here except these two files. Where do these files come from? they're compatibility symlinks from before they were merged into ltspfs_entry. they should probably be treated as deprecated. I have latest trunk of ltsp, ltspfs and ldm on the server and client. Currently it appears nothing happens when I insert a USB storage device into a logged in client that is sitting on the GNOME2 desktop. The client hardware recognizes the new device and emumerates it as /dev/sdb, but nothing else appears to happen and nothing shows up in the logs. have you gone through the steps at: https://wiki.ubuntu.com/DebugLocalDev obviously, you'll have to use the redhat counterparts to some ubuntu-specific commands, but hopefully you get the idea. live well, vagrant -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _ 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] fatclient on squeeze
On Wed, Jul 13, 2011 at 11:01:42AM +0200, Joakim Seeberg wrote: Hi Jason, fat clients works on Debian as well. The difference from ubuntu is that there are a few steps you have to do manually that ubuntu does fore you. Start by building the chroot with ltsp-build-client. Then you have to install a desktop in the chroot and add LTSP_FATCLIENT=True to lts.conf. I have not found a way to get gdm working yet so there is a choice between kdm,xdm and ldm as display manger. i would strongly recommend using LDM, as it authenticates against the server, uses the user's homedir on the server, and has support for local apps if you install ltspfs into the chroot (see below). with the other display managers, you'll essentially have to manually configure everything. Local devices does not work with ldm so kdm is my choise at the moment. I'm not able to safely remove the local device again so that is another problem. I am sure the problems I have with gdm and local devices can be solved. if you want local devices, you'll need to install ltspfs in the ltsp-chroot: ltsp-chroot apt-get install ltspfs i recommend using ltsp-chroot as it will set some important environment variables, and has options to handle mounting of /proc and /dev/pts for you. live well, vagrant -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _ 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] fatclient on squeeze
On Thu, Jul 14, 2011 at 10:35:25AM +0200, Joakim Seeberg wrote: Den 13-07-2011 23:20, Vagrant Cascadian skrev: On Wed, Jul 13, 2011 at 11:01:42AM +0200, Joakim Seeberg wrote: Local devices does not work with ldm so kdm is my choise at the moment. I'm not able to safely remove the local device again so that is another problem. I am sure the problems I have with gdm and local devices can be solved. if you want local devices, you'll need to install ltspfs in the ltsp-chroot: ltsp-chroot apt-get install ltspfs What I want is for local devices to pup op like on a real workstation. Is that possible with LDM, thought that was why debian-edu uses kdm for fat clients at least in the Lenny version, have not tried squeeze yet. ah, debian-edu implements it's own version of a fat client, and tries to configure it just like their typical disked workstation. in theory, the fatclients shouldn't work any differently than a disked system... in practice, it's an adventure in configuration options... Installed ltspfs like you suggested (why isn't it a dependency when installing ltsp-server-standalone?) ltspfs *is* a dependency of ltsp-server-standalone, at least on Debian. but that doesn't change what gets installed in the chroot. so you need to install ltspfs in the chroot if you want LTSP-style localdev support for LTSP-style fatclients. but nothing pops up and also nothing to see in nautilus after inserting usb stick and cd. is the user in the fuse group? does anything show up in /media/$USERNAME? GNOME is the only desktop that shows icons on the desktop for ltspfs mounted devices out of the box- perhaps you're using another desktop enviropnment? With kdm pop up works only problem is umounting the local device, it asks for the root passwd which I havn't set in the chroot. And yes I have set up the chroot as a ldap client and also remembered the group rights with /etc/secutity/group.conf id confirmed the user belongs to the right groups. i don't know what software you're running, or how it should be configured, so i can't help much there. your desktop environment (KDE/GNOME) will matter more than your login manager (KDM) in that case, if you're not using typical LTSP_FATCLIENT style fat clients. sorry i don't have more helpful things to offer, but there are a myriad of options available, and i'm most familiar with the ones supported in LTSP directly. live well, vagrant -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _ 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] Why PA system mode?
On Mon, Aug 15, 2011 at 05:53:11PM -0400, Jeff Siddall wrote: Anyone know why the clients run pulseaudio in system mode? Here's an excerpt from the client system log: Aug 9 09:12:06 client-192 pulseaudio[1740]: main.c: OK, so you are running PA in system mode. Please note that you most likely shouldn't be doing that. Aug 9 09:12:06 client-192 pulseaudio[1740]: main.c: If you do it nonetheless then it's your own fault if things don't work as expected. Aug 9 09:12:06 client-192 pulseaudio[1740]: main.c: Please read http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode for an explanation why system mode is usually a bad idea I did read http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode and sure enough they say it is there for stuff like thin clients. the short answer is it is what we got to work at the time... However, the reasons for it are really not that good: we _do_ have a real user, and things like home directories typically _aren't_ flushed on each session termination. I realize that not all real users exist on the client but at least in LTSP5 some magic happens behind the scenes and a custom /etc/passwd containing the real user is mounted as a tmpfs file on the client. we only have a user and home directory on the thin client if localapps or fatclients are enabled. and it's a pretty ugly hack that enables them. Further, since PA is really designed to be run as a user, could some headaches be removed by not having it run in system mode (ie: not have to fixup permissions etc.)? if someone has patches to improve the situation, they'd surely be considered- but they need to take into account genuine thin clients vs. localapps vs. fatclients. live well, vagrant -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _ 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
