IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 2 August 2022 (all times are UTC)
| 03:13 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 03:37 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 06:42 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 07:33 | fiesh has left IRC (fiesh!~fiesh@2003:fb:1018::21, Ping timeout: 240 seconds) | |
| 07:50 | fiesh has joined IRC (fiesh!~fiesh@2003:fb:1018::21) | |
| 08:12 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Ping timeout: 252 seconds) | |
| 08:19 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 13:17 | woernie has joined IRC (woernie!~werner@p5ddec8bb.dip0.t-ipconnect.de) | |
| 13:53 | woernie has left IRC (woernie!~werner@p5ddec8bb.dip0.t-ipconnect.de, Ping timeout: 245 seconds) | |
| 14:44 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 240 seconds) | |
| 15:06 | woernie has joined IRC (woernie!~werner@p5ddec8bb.dip0.t-ipconnect.de) | |
| 15:16 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 15:44 | woernie has left IRC (woernie!~werner@p5ddec8bb.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 18:33 | woernie has joined IRC (woernie!~werner@p5ddec8bb.dip0.t-ipconnect.de) | |
| 20:45 | woernie has left IRC (woernie!~werner@p5ddec8bb.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 21:08 | bluejaypop has joined IRC (bluejaypop!~7f000001@user/josefig) | |
| 21:10 | <bluejaypop> Hi, is the 2019 LTSP working with newest ubuntu ?
| |
| 21:15 | <vagrantc> there's LTSP 22.01 now
| |
| 21:15 | which should work ...
| |
| 21:16 | <bluejaypop> ok, i used it from 2016, and we're going to use it again, with raspberry clients is it possible that works?
| |
| 21:19 | <vagrantc> probably? :)
| |
| 21:19 | you need clients fast enough to run as workstations, all the software generally runs on the client themsevles
| |
| 21:19 | so older raspberry pi clients might not be so great
| |
| 21:20 | <bluejaypop> ah, so only the server is for the image?
| |
| 21:21 | I used to work with the server as the one who runs all the software itself and only the terminal to run as a thin terminal to load the image and work over the network as a local user in the linux server.
| |
| 21:25 | <vagrantc> yeah, the model has shifted as X11 network transparency is basically loosing support in newer software
| |
| 21:25 | so the old model just breaks in some cases
| |
| 21:26 | the shift from x.org to wayland for many things accelerated the issue, but it's been slowly happening even with x.org ... applications making poor assumptions, etc.
| |
| 21:31 | so the model shifted from thin clients to network-booted fat clients where all the applications run on the client hardware for the most part
| |
| 21:31 | for the last few years of LTSP5 that was also the recommended model
| |
| 21:34 | <bluejaypop> i understand, so i need a little more powerful client pc now
| |
| 21:35 | <vagrantc> my wild guess would be rpi3 are probably the smallest you'd want to use in the raspberry pi world...
| |
| 21:37 | <bluejaypop> maybe yes, in my case is for software development, so the server might probably run the process
| |
| 21:37 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 21:37 | <bluejaypop> only editors and some client software run in the client pc
| |
| 21:38 | like DB, Webserver, etc will run from server's side
| |
| 21:41 | <vagrantc> yeah, obviously depends on your use-case
| |
| 21:41 | though the number of times people say "I *just* want to run a web browser and ..."
| |
| 22:08 | <bluejaypop> i understand vagrantc , thanks for the hint
| |
| 22:08 | :)
| |