IRC chat logs for #ltsp on (webchat)

Channel log from 1 July 2013   (all times are UTC)

00:05monteslu has left IRC (monteslu!, Ping timeout: 246 seconds)
00:33jammcq has joined IRC (jammcq!
00:55PhoenixSTF has joined IRC (PhoenixSTF!~rudi@
01:01gentgeen__ has joined IRC (gentgeen__!
01:01quietone has left IRC (quietone!, Ping timeout: 260 seconds)
01:17PhoenixSTF has left IRC (PhoenixSTF!~rudi@, Quit: Leaving)
01:18quietone has joined IRC (quietone!
01:35jammcq has left IRC (jammcq!, Quit: WeeChat 0.3.7)
01:36Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
01:43quietone has left IRC (quietone!, Ping timeout: 276 seconds)
01:51monteslu has joined IRC (monteslu!
02:07quietone has joined IRC (quietone!
02:10quietone has left IRC (quietone!, Read error: Connection reset by peer)
02:23quietone has joined IRC (quietone!
02:33quietone has left IRC (quietone!, Ping timeout: 246 seconds)
02:45gbaman has joined IRC (gbaman!
02:50quietone has joined IRC (quietone!
02:50gbaman has left IRC (gbaman!, Ping timeout: 248 seconds)
03:05Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 248 seconds)
03:47MonkWitDaFunk has left IRC (MonkWitDaFunk!~yaaic@, Ping timeout: 240 seconds)
03:50MonkWitDaFunk has joined IRC (MonkWitDaFunk!~yaaic@
04:40quietone has left IRC (quietone!, Quit: Leaving)
04:49gbaman has joined IRC (gbaman!
04:53gbaman has left IRC (gbaman!, Ping timeout: 264 seconds)
05:34MonkWitDaFunk has left IRC (MonkWitDaFunk!~yaaic@, Ping timeout: 268 seconds)
05:35MonkWitDaFunk has joined IRC (MonkWitDaFunk!~yaaic@
05:37vector has left IRC (vector!, Remote host closed the connection)
05:41vector has joined IRC (vector!
06:50dobber has joined IRC (dobber!~dobber@
06:53sep has left IRC (sep!, Remote host closed the connection)
06:57sep has joined IRC (sep!
07:33vnc786 has joined IRC (vnc786!~chatzilla@
07:55dobber has left IRC (dobber!~dobber@, Remote host closed the connection)
07:59dobber has joined IRC (dobber!~dobber@
08:11mikkel has joined IRC (mikkel!
08:40MonkWitDaFunk has left IRC (MonkWitDaFunk!~yaaic@, Ping timeout: 256 seconds)
08:42MonkWitDaFunk has joined IRC (MonkWitDaFunk!~yaaic@
09:02Gremble has joined IRC (Gremble!
09:41yopla has joined IRC (yopla!
09:41adrianorg_ has left IRC (adrianorg_!~adrianorg@, Read error: Operation timed out)
hello ltsp team. I need heavy configuration for LTSP-FAT client with GUI. As it seems read only filesystem, what do you suggest ?
09:54adrianorg_ has joined IRC (adrianorg_!
10:20gbaman has joined IRC (gbaman!
10:27workingcats has joined IRC (workingcats!~workingca@
10:46PhoenixSTF has joined IRC (PhoenixSTF!~rudi@
11:03adrianorg_ has left IRC (adrianorg_!, Ping timeout: 268 seconds)
11:07PhoenixSTF has left IRC (PhoenixSTF!~rudi@, Ping timeout: 264 seconds)
11:15adrianorg_ has joined IRC (adrianorg_!
11:19PhoenixSTF has joined IRC (PhoenixSTF!~rudi@
11:20PhoenixSTF has left IRC (PhoenixSTF!~rudi@, Max SendQ exceeded)
11:21PhoenixSTF has joined IRC (PhoenixSTF!~rudi@
11:45Gremble has left IRC (Gremble!, Quit: I Leave)
12:22bobby_C has joined IRC (bobby_C!
Hello, sorry I was away when the question was posted to me regarding the Raspberry Pi. You are correct in that the Pi cannot PXE boot so we are not connecting to our LTSP server booting through PXE. We hardcode the LTSP Server IP in a file on the SD Card of the PI and it makes the connection to the LTSP server.
12:57bobby_C has left IRC (bobby_C!, Ping timeout: 260 seconds)
I can connect without issue to our LTSP server from the Pi. Problem is though this O/S I'm using called Berry Terminal ignores any instructions in the lts.conf file so I cannot use it. Is there another way to add a startup instruction to a client in LTSP?
13:04dsugar100 has joined IRC (dsugar100!
greavette, what is Berry Terminal and why are you using it?
13:23bengoa has joined IRC (bengoa!~bengoa@2001:1291:229:2:1053:922b:2307:5c9d)
Berry Terminal is an O/S created for the Raspberry Pi computer. It's used to connect to an LTSP server. Raspberry Pi's cannot PXE boot so this is the only way to connect the Pi to an LTSP server.
does berry terminal have ltsp client packages on it? could it not be made to tftp the lts.conf on startup?
Hmmm, that's a question I'd have to put to the creator of Berry Terminal on the Raspberry Pi forums. Sorry, I don't know this answer. I suppose I could use the Autostart Application in Ubuntu 12.04 (which is where I've installed LTSP) to start rdesktop. My plan is to use these very cheap Raspberry Pi computers ($35) as a sort of Thin Client. I connect the Pi to our locally installed LTSP server.
rdesktop performs a lot better if you run it on the client instead of via the ltsp host
Each LTSP client will have an instruction to connect to their Windows Virtual Machine. It's a sort of VDI solution that allows me to drop in a Pi, create one type of O/S for each Pi that are identical (in that the O/S for every Pi in the office only connects to our LTSP server). As long as the LTSP server is configured for each unique client to access the Virtual Machine they need, a Thin Client going down doesn't mean a lot of u
and running again.
is there an lts.conf on the pi somewhere?
No, unfortunately there isn't.
There is a command.txt on the Pi that allows me to point to the LTSP server. I think this command.txt file might also handle auto login and language. It doesn't do all that much.
<||cw> makes it sound like you can put lts.conf options in cmdline.txt
but maybe not just any option
Really! I missed that. I'll have to give that try and see.
I had read in a forum post on the Raspberry Pi forum that lts.conf instructions were ignored. But maybe I can add some instructions to the cmdline.txt file instead. Thanks!
if you can figure out what it's doing with those LDM vars, it might be possible to expand the support, or even replace it with a tftp of lts.conf
might have to add a tftp client to the image though
but if all you need is rdesktop, it might even make more sense to just use a minimal rasbian with an xsesison that just loads rdesktop
since berryterm isn't giving you ltsp's management feature anyway
I'll do that cw...Thank you. As you can see I'm attempting to create a very cheap VDI solution for our small office using the LTSP server. They have the need to use Windows Computers due to the third party application they own that only runs on Windows. I'm investigating to move them to running all their Windows VM's to a locally hosted server (using Proxmox).
yeah, I've done the same but with older x86 clients
I've actually already deployed a couple of workstations using Rasbian where the first instruction when Rasbian boots is to rdesktop to their Windows VM. Problem is though if a Thin Client goes down or the SD Card becomes corrupt, I'll need to manually configure a new O/S for each Pi we use.
Using Berry Terrminal means I have one generic O/S that can be dropped on any Pi in the office. The configuration for each user/workstation is all done on the LTSP server side.
Reason for this complicated setup is I support my fathers small business remotely (8 hours away) and it's the easiest seutp I can think of to assist them if a Pi or the O/S (SD card) on a Pi goes down.
Not that this is a common occurrence. Just solving for the worst situation and making it as easy as possible.
what about having the script that loads rdesktop contact a server, tftp or http or whatever, so it can ask what server to connect to?
Plus showing off the benefits of Linux and using a free open source solution is always a plus. I've already gained interest in how this is setup from the company that supports the third party application we bought that only runs on Windows.
http might even be simpler since you could use php or perl or python to identify the client
Sorry, I have to confess I don't understand what you mean. So I would have as a startup application instruction on the LTSP client?
Or a script on Berry Terminal that loads rdesktop?
well, to start, berryterm isn't a proper ltsp client, it's just a ldm client
True. It just connects me to a true ltsp client on our ltsp server.
no, it connects you to an ldm session. it's not actually ltsp at all
which is the difficulty you are having
Oh, I see. But once I login with an ltsp client I am on my ltsp server with a desktop et all. Where I can then presumably have in my Autostart an command to connect to the Windows VM that client is assigned to use?
so the options are to figure out how to make berryterm pull the lts.conf and honor it, or to skip ltsp completely and make a work-alike that only support rdesktop
no, you are not on an ltsp client. berryterm is not actually an ltsp client.
it is an ldm client with some ltsp compatibility
14:37dead_inside has joined IRC (dead_inside!~taylor@
and that compatibility is only via using cmdline.txt variables that happen to match some lts.conf variables
Oh, I see. I didn't know that. So when using an rdesktop instruction from the lts.conf file (which is what I'd like to use), this would bypass the double hop I would be introducing if I did rdesktop from an ltsp client desktop.
ltsp is a collection pf standalone packages and some wrapper/glue scripts to centralize the management of them. rdekstop, ldm, nbd, pxe, can all be use without ltsp, and can be used on an ltsp server but without using ltsp.
I see. Thank you for clearing this up for me. I think what I'll have to do is look at the code for Berry Terminal and see if I can modify it for my purposes to use rdesktop instead.
14:42Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
Would it be slow to use rdesktop from a clients ltsp session? I'll have to try this maybe using compression on rdesktop and see how slow it is.
i'm not sure, it's worth comparing
on my p3 700 systems, local rdesktop is much faster
14:45dberkholz_ is now known as dberkholz
14:56mikkel has left IRC (mikkel!, Quit: Leaving)
hello, ubuntu 12.04 I can't have sound working on my ltsp thin client. Gnome-session fallback shows me empty sound device.
pulseaudio is runing on thin client
I open session via ldm
To cw...thanks you very much for taking the time to chat with me regarding us using the Pi this morning. I very much appreciate your input. Have a great day!
greavette: good luck! it would be nice to see berryterm get lts.conf support, if it can be managed
15:12alexqwesa has left IRC (alexqwesa!~alex@, Ping timeout: 252 seconds)
15:33Enlightment has joined IRC (Enlightment!555b8880@gateway/web/freenode/ip.
15:35dobber has left IRC (dobber!~dobber@, Remote host closed the connection)
Hi! I have a question and I hope someone can give me advice... Do you think that I can start Blender on LTSP thin client HP t5335z Smart Client if the terminal server is very powerful... I mean is the terminal good enough?
i bet Blender is designed to use GPU and not CPU power, it will probably run but not very well
I see... It will be great if it can run somehow. Thanks for the answer... I will wait to see if someone else also has an idea
15:43ltsp has joined IRC (ltsp!
trying hard to get sound on my thin client. After connet via ldm I get PULSE_SERVER=tcp:
thin client doesn't have this port open
16:12alexqwesa has joined IRC (alexqwesa!
16:16staffencasa has joined IRC (staffencasa!
16:17ltsp has left IRC (ltsp!, Quit: ChatZilla 0.9.90 [Firefox 22.0/20130620122109])
16:27gbaman has left IRC (gbaman!, Remote host closed the connection)
16:36MonkWitDaFunk has left IRC (MonkWitDaFunk!~yaaic@, Ping timeout: 256 seconds)
16:36gbaman has joined IRC (gbaman!~gbaman@
16:38MonkWitDaFunk has joined IRC (MonkWitDaFunk!~yaaic@
16:46gbaman has left IRC (gbaman!~gbaman@, Remote host closed the connection)
17:01gbaman has joined IRC (gbaman!~gbaman@
17:01alexqwesa has left IRC (alexqwesa!, Remote host closed the connection)
17:02Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
17:29gbaman has left IRC (gbaman!~gbaman@, Remote host closed the connection)
17:30vnc786 has left IRC (vnc786!~chatzilla@, Ping timeout: 246 seconds)
17:42rick__ has joined IRC (rick__!4c65b525@gateway/web/freenode/ip.
17:42vagrantc has joined IRC (vagrantc!
17:42vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
17:43workingcats has left IRC (workingcats!~workingca@, Quit: Verlassend)
17:46workingcats has joined IRC (workingcats!~workingca@
17:48rick__ has left IRC (rick__!4c65b525@gateway/web/freenode/ip., Ping timeout: 250 seconds)
17:49workingcats has left IRC (workingcats!~workingca@, Client Quit)
17:59* vagrantc gets back to tinkkering with libpam-sshauth
18:03gbaman has joined IRC (gbaman!
18:07bobby_C has joined IRC (bobby_C!
18:19* vagrantc waves to sbalneav
hello, is there some var to change default output audio device in pulseaudio ?
your client has multiple sound devices or something?
yes. it has analog and hdmi output
i'd like to use hdmi (shared with display) but it uses analog at boot time
if i manually change with pavucontrol it works
doesn't seem to be, but probably not terribly hard to add a new param to lts.conf
though I've never tried
you could also use the RCFILE_## options to exec the pavucontrol command
18:39MonkWitDaFunk has left IRC (MonkWitDaFunk!~yaaic@, Ping timeout: 252 seconds)
18:43MonkWitDaFunk has joined IRC (MonkWitDaFunk!~yaaic@
18:43Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
19:00PhoenixSTF has left IRC (PhoenixSTF!~rudi@, Quit: Leaving)
19:05vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
19:12Enslaver has left IRC (Enslaver!~Enslaver@fedora/Enslaver, Ping timeout: 268 seconds)
19:14Enslaver has joined IRC (Enslaver!~Enslaver@fedora/Enslaver)
19:35Enslaver has left IRC (Enslaver!~Enslaver@fedora/Enslaver, Ping timeout: 276 seconds)
19:35Enslaver has joined IRC (Enslaver!~Enslaver@fedora/Enslaver)
19:38Enlightment has left IRC (Enlightment!555b8880@gateway/web/freenode/ip., Quit: Page closed)
19:40MonkWitDaFunk has left IRC (MonkWitDaFunk!~yaaic@, Ping timeout: 240 seconds)
19:41MonkWitDaFunk has joined IRC (MonkWitDaFunk!~yaaic@
19:48Enslaver has left IRC (Enslaver!~Enslaver@fedora/Enslaver, Ping timeout: 240 seconds)
19:48Enslaver has joined IRC (Enslaver!~Enslaver@fedora/Enslaver)
19:55Enslaver has left IRC (Enslaver!~Enslaver@fedora/Enslaver, Ping timeout: 246 seconds)
19:55Enslaver has joined IRC (Enslaver!
19:55Enslaver has joined IRC (Enslaver!~Enslaver@fedora/Enslaver)
20:09Enslaver has left IRC (Enslaver!~Enslaver@fedora/Enslaver, Ping timeout: 256 seconds)
20:09Enslaver has joined IRC (Enslaver!~Enslaver@fedora/Enslaver)
20:21MonkWitDaFunk has left IRC (MonkWitDaFunk!~yaaic@, Ping timeout: 246 seconds)
20:23Enslaver has left IRC (Enslaver!~Enslaver@fedora/Enslaver, Ping timeout: 252 seconds)
20:23Enslaver has joined IRC (Enslaver!~Enslaver@fedora/Enslaver)
20:38Enslaver has left IRC (Enslaver!~Enslaver@fedora/Enslaver, Ping timeout: 276 seconds)
20:38Enslaver has joined IRC (Enslaver!~Enslaver@fedora/Enslaver)
20:48gbaman has left IRC (gbaman!, Remote host closed the connection)
21:03gbaman has joined IRC (gbaman!
21:08gbaman has left IRC (gbaman!, Remote host closed the connection)
21:39gbaman has joined IRC (gbaman!
21:43gbaman has left IRC (gbaman!, Ping timeout: 248 seconds)
21:50vagrantc has joined IRC (vagrantc!
21:50vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
21:51bengoa has left IRC (bengoa!~bengoa@2001:1291:229:2:1053:922b:2307:5c9d, Quit: Leaving)
21:58bobby_C has left IRC (bobby_C!, Ping timeout: 246 seconds)
22:17dsugar100 has left IRC (dsugar100!, Quit: dsugar100)
23:14Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Quit: Leaving.)