IRC chat logs for #ltsp on irc.libera.chat (webchat)


Channel log from 22 November 2022   (all times are UTC)

01:19vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)
02:53vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving)
07:03ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
08:16woernie has joined IRC (woernie!~werner@p200300cf07203600bde9c7e335e39ed0.dip0.t-ipconnect.de)
08:35Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))
08:39Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas)
09:58book` has left IRC (book`!~book`@static.38.6.217.95.clients.your-server.de, Quit: Leaving)
10:02book` has joined IRC (book`!~book`@static.38.6.217.95.clients.your-server.de)
10:35vsuojanen[m] has left IRC (vsuojanen[m]!~vsuojanen@2001:470:69fc:105::d24b, Quit: Bridge terminating on SIGTERM)
10:35nnannos78[m] has left IRC (nnannos78[m]!~nnannos78@2001:470:69fc:105::2:ab24, Quit: Bridge terminating on SIGTERM)
10:35denispyr[m] has left IRC (denispyr[m]!~denispyrm@2001:470:69fc:105::1:5545, Quit: Bridge terminating on SIGTERM)
10:35alkisg has left IRC (alkisg!~alkisg@2001:470:69fc:105::2d3, Quit: Bridge terminating on SIGTERM)
10:35alkisg_irc is now known as alkisg
10:35gidarakos[m] has left IRC (gidarakos[m]!~gidarakos@2001:470:69fc:105::ce6, Quit: Bridge terminating on SIGTERM)
10:35SunilThomasThoni has left IRC (SunilThomasThoni!~vu2swmatr@2001:470:69fc:105::2:bf12, Quit: Bridge terminating on SIGTERM)
10:35RolandStiebel[m] has left IRC (RolandStiebel[m]!~stiebelma@2001:470:69fc:105::1:b67e, Quit: Bridge terminating on SIGTERM)
10:35err404[m] has left IRC (err404[m]!~err404mat@2001:470:69fc:105::444, Quit: Bridge terminating on SIGTERM)
10:35NickolayZaytsev[ has left IRC (NickolayZaytsev[!~madcmk2ma@2001:470:69fc:105::2:be6f, Quit: Bridge terminating on SIGTERM)
10:35MaximKostyuchenk has left IRC (MaximKostyuchenk!~rintfsmat@2001:470:69fc:105::2:b6d4, Quit: Bridge terminating on SIGTERM)
10:37alkisg1 has joined IRC (alkisg1!~alkisg@2001:470:69fc:105::2d3)
10:43err404[m] has joined IRC (err404[m]!~err404mat@2001:470:69fc:105::444)
10:43nnannos78[m] has joined IRC (nnannos78[m]!~nnannos78@2001:470:69fc:105::2:ab24)
10:43denispyr[m] has joined IRC (denispyr[m]!~denispyrm@2001:470:69fc:105::1:5545)
10:43MaximKostyuchenk has joined IRC (MaximKostyuchenk!~rintfsmat@2001:470:69fc:105::2:b6d4)
10:43vsuojanen[m] has joined IRC (vsuojanen[m]!~vsuojanen@2001:470:69fc:105::d24b)
10:43gidarakos[m] has joined IRC (gidarakos[m]!~gidarakos@2001:470:69fc:105::ce6)
10:43NickolayZaytsev[ has joined IRC (NickolayZaytsev[!~madcmk2ma@2001:470:69fc:105::2:be6f)
10:43RolandStiebel[m] has joined IRC (RolandStiebel[m]!~stiebelma@2001:470:69fc:105::1:b67e)
10:43SunilThomasThoni has joined IRC (SunilThomasThoni!~vu2swmatr@2001:470:69fc:105::2:bf12)
12:47alkisg has left IRC (alkisg!~Thunderbi@2a02:587:744e:8500:c24a:ff:fe02:bc1e, Ping timeout: 260 seconds)
12:48Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)
12:49Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas)
12:50alkisg has joined IRC (alkisg!~Thunderbi@2a02:587:744e:8500:c24a:ff:fe02:bc1e)
13:11Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)
13:12Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas)
13:37woernie has left IRC (woernie!~werner@p200300cf07203600bde9c7e335e39ed0.dip0.t-ipconnect.de, Remote host closed the connection)
15:10Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))
15:11Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas)
15:13Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)
15:14Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas)
16:01
<NickolayZaytsev[>
Hey guys. It's me again. Hope you all have good week start.... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/9164a555f8b0a4afdbceca3d1e9f8611afc446af>)
16:02
Sorry for md
16:02
* Hey guys. It's me again. Hope you all have good week start.... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/263a724f5cdfaf7ed2da46382bad9e70719b3b0e>)
16:08
> <@madcmk2:matrix.org> Hey guys. It's me again. Hope you all have good week start.... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/218ee37186137f7aad6f2b7323a86da2cf67642c>)
16:08
* Guess I sovled it.
16:08
It's need to use "ubuntu-flat.vmdk" instead of "ubuntu.vmdk"
16:11
<alkisg1>
Yup, like the instructions say ;)
16:12
<ogra>
who reads instructions anyway 🙂
16:12
<alkisg1>
I really think
16:13
.. just the authors themselves anymore..
16:15
<ogra>
lol, yeah
16:18
<NickolayZaytsev[>
I have a few theoretical questions about refactored LTSP version (since LTSP5 version):
16:18
1. In LTSP5 was fat and thin client modes. But the desctiption of the new version said:
16:18
*The older LTSP5 targetted thin clients with reduced hardware specifications; this is no longer the case. The LTSP clients should be able to run the distribution with their own CPU/RAM...*
16:18
Does it mean the new version of LTSP is working only in "fat" mode? Or "fat" is by deafult and I can change it behaviour by adding apps via "ltsp remoteapps/REMOTEAPPS in ltsp.conf"?
16:18
2. In LTSP5 was an ldm-server, that provides ldm for clients via tunnels (if my understanding is correct). Now it's a past, and clients use their own DMs?
16:24
<quinox>
The new LTPS is like the old fat mode: clients run their own UI, and thus their own DMs
16:27
<NickolayZaytsev[>
quinox: I see. So if I have some complicated program that I would to like execute on server side, can I manage this situation by using REMOTEAPPS property? Or it's for different purpose?
16:29
<quinox>
I just checked https://ltsp.org/man/ltsp-remoteapps/ , it indeed allows you to run programs on the server more easily than doing a `ssh -X` yourself
16:44
<NickolayZaytsev[>
I'm totally confused about LTSP at moment) Could you please help me?
16:44
I have a server with bunch of software, that I would like to execute on the server side, not on the client side. So here is question:
16:44
Could I get access to the server software from the LTSP client and execute it on the server side?
16:46
For LTSP5 it was the case, as I understand.
16:47
<alkisg1>
That's what the ltsp remote apps directive does, it runs programs on the server
16:48
<NickolayZaytsev[>
alkisg1: Ok. Sounds reassuringly
16:56oh207 has joined IRC (oh207!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net)
17:04
<alkisg1>
Nickolay Zaytsev: note that if you ONLY want remote apps, then maybe you'd want to use xfreerdp, to get a session directly on the server, without even logging in on the client
17:29
<NickolayZaytsev[>
<alkisg1> "Nickolay Zaytsev: note that if..." <- I need to load an image from the network, cause thin clients are diskless in my case.
17:29
If I understand correct the purpose of xfreerdp after quick look, it's only an app/protocol, not a whole "os distribution over network" system, as LTSP is.
17:29
Does it make sence to combine LTSP and xfreerdp?
17:40
<quinox>
it depends on your needs and usecases, but it's not a strange combination
17:42
RDP is a really cool powerful protocol, works great in a Windows landscape. I wasn't impressed by xfreerdp the last time I tried it though
17:42
there's also x2go that you might find interesting
17:42
it can all be used on top of LTSP, yup
17:44
<NickolayZaytsev[>
Talking of client side logging. I'm steel haven't luck with PAM configuration. All examples with "libpam-google-authenticator" are consists of manully changing the sshd_config file and pam.d/sshd. No "pam-auth-update" participation at all! I've have read "libpam-doc" documectation, but didn't find siutable... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/088978e067677481446959026c0637fdb07cc29c>)
17:44
quinox: Ok. I'll check x2go and xfreerdp in parrallel. Thank you guys
18:03
<alkisg1>
Nickolay Zaytsev: yes, ltsp and xfreerdp/x2go make a lot of sense, there's even a display manager that authenticates directly with xfreerdp, so you won't need any local (on thin client) authentication at all
18:03
(a lightdm plugin for xfreerdp or x2go, don't remember which of these, made by the arctica greeter project, in the debian/ubuntu repositories)
18:05
https://packages.ubuntu.com/jammy/lightdm-remote-session-x2go
18:05
That way you can do whatever you want with pam directly on the server; ltsp isn't involved at all in authentication then, it's only used for netbooting
18:13
<NickolayZaytsev[>
<alkisg1> "https://packages.ubuntu.com/..." <- Okay, I'll try it in that way
18:44vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)
21:17ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
23:22oh207 has left IRC (oh207!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net, Ping timeout: 252 seconds)
23:58Vercas62 has joined IRC (Vercas62!~Vercas@gateway/tor-sasl/vercas)
23:59Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 255 seconds)
23:59Vercas62 is now known as Vercas6
23:59vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving)