IRC chat logs for #ltsp on (webchat)

Channel log from 14 February 2023   (all times are UTC)

01:58wyre is now away: Auto away at Tue Feb 14 01:58:34 2023 UTC
02:01vagrantc_ has joined IRC (vagrantc_!~vagrant@2600:3c01:e000:21:7:77:0:40)
02:05vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving)
02:05vagrantc_ is now known as vagrantc
04:31Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
04:35Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Client Quit)
04:35Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
04:40Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Client Quit)
04:40Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
04:45Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Client Quit)
04:45Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
05:23Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))
05:24Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
06:51alkisg_irc1 has joined IRC (alkisg_irc1!
06:53alkisg_irc has left IRC (alkisg_irc!~Thunderbi@2a02:587:7456:4800:9ea2:f4ff:feb9:a8b0, Ping timeout: 252 seconds)
06:54alkisg_irc1 is now known as alkisg_irc
07:02ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:35vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40, Quit: leaving)
07:36wyre is back
07:47wyre is now away: Auto away at Tue Feb 14 07:47:13 2023 UTC
08:02woernie has left IRC (woernie!, Ping timeout: 252 seconds)
08:02woernie has joined IRC (woernie!
08:44wyre is back
11:23ogra is now away: currently disconnected
11:29ogra is back
11:42Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: buh bye)
11:43Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
11:45Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Client Quit)
11:45Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
11:50Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Client Quit)
11:50Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
11:55Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Client Quit)
11:55Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
17:03wyre is now away: Auto away at Tue Feb 14 17:03:20 2023 UTC
17:15yo23 has joined IRC (yo23!~yo23@
Hello, I have ltsp with 22.04 but the thin clients are very very slow, what can I do?
what manufacturer and models they are? And which comp/display manager they boot?
alkisg, got the res eventually working :)
just in time too
thanks for looking the other day
18:02lcurl has joined IRC (lcurl!~UserNick@
18:05vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)
alkisg, i don't suppose there is anyway (not for now... but maybe another day) to run ltsp in a way where if you install a package on the server, you don't need to remake an image for the clients to get it?
presumably this imaging takes *everything* except the home dirs ?
although it cant run it all in the client machins ram surely, so an image accessed over tftp/nfs ?
Lantizia: if you use a VM as an image, you can boot the clients with it without running ltsp image at all
right but surely if I 'apt-get install openarena' in the VM... then the PC's still need rebooting to play the game :P
so same issue
Lantizia: well not the same issue exactly, because you won't need 10 minutes for ltsp image; but just a reboot
The only way to do it in a completely live manner would be to use ltsp remoteapps, i.e. like thin clients, where all the processes run on the server
Of course that will put a strain on the server :)
well see we picked this r610 originally because we were running ltsp5 (on ubuntu 18.04... in fact we still can run this... by just picking another OS on boot up)
and assumed these 2012 compaq 315eu pc's wouldn't be up to much... so planned on them all being thin
but actually ltsp5 defaulted to thick (prob because they're not that bad) and so that is fine
and obviously the new ltsp doesn't do thin at all
but yeah that dell r610 was picked to be beeefy... i think it has 32 cores, 96gb ram etc...
but I'm thankful for them being thick... as (if it wasn't for trisquel) we can have things like hw accelerated games
i just assumed *more* of the servers filesystem was shared live via nfs
it seems much less actually is
ltsp remoteapps app => is the equivalent of thin clients, and is supported out of the box in the new ltsp
And if you declare mate-session or any other session as a remoteapp, you get the whole session in thin client mode
Only the squashfs image is served over nfs, as nfs is considered insecure, so it's only good for the read only and public part
18:56woernie has left IRC (woernie!, Remote host closed the connection)
18:58wyre is back
20:00yo23 has left IRC (yo23!~yo23@, Quit: Client closed)
21:51ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)