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


Channel log from 17 March 2022   (all times are UTC)

01:59jgee636 has left IRC (jgee636!~jgee@186.80.49.20, Quit: The Lounge - https://thelounge.chat)
02:01jgee636 has joined IRC (jgee636!~jgee@186.80.49.20)
02:03jgee636 has left IRC (jgee636!~jgee@186.80.49.20, Client Quit)
02:06jgee636 has joined IRC (jgee636!~jgee@186.80.49.20)
02:34vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving)
02:59j_sh has joined IRC (j_sh!~j_sh@ip24-254-36-233.br.br.cox.net)
03:02
<j_sh>
Thanks, alkisg ! Bonding has worked for something similar for me in the past; I just wasn't sure how to bond before the network mounts. I will look into initramfs-tools.
04:50j_sh has left IRC (j_sh!~j_sh@ip24-254-36-233.br.br.cox.net, Ping timeout: 256 seconds)
05:14
<alkisg>
j_sh: (in case you see the logs) actually on second thought it should be possible to just create the bond on POST_INITRD_BOTTOM_x, as you'll be reusing the same IP, so you don't even need to unmount and re-mount the NFS share
05:35map7`` has joined IRC (map7``!~user@121-200-30-135.79c81e.mel.nbn.aussiebb.net)
05:36map7` has left IRC (map7`!~user@103.232.216.31, Ping timeout: 256 seconds)
06:07map7`` has left IRC (map7``!~user@121-200-30-135.79c81e.mel.nbn.aussiebb.net, Ping timeout: 250 seconds)
06:48ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
08:13pr0f3s0r has joined IRC (pr0f3s0r!~pr0f3s0r@158.99.1.170)
08:14
<pr0f3s0r>
Hello, somebody knows lan software to throw surveys in class?
08:16
<alkisg>
It's best to ask in your distribution for this as it's not ltsp-specific
08:16
<pr0f3s0r>
okay
08:16
thanks
09:00sfxworks[m] has left IRC (sfxworks[m]!~sfxworksm@2001:470:69fc:105::e5d4, Quit: You have been kicked for being idle)
10:18pr0f3s0r has left IRC (pr0f3s0r!~pr0f3s0r@158.99.1.170, Quit: Client closed)
11:11lucascastro has left IRC (lucascastro!~lucascast@192-140-51-239.static.oncabo.net.br, Ping timeout: 252 seconds)
11:46lucascastro has joined IRC (lucascastro!~lucascast@177-185-131-162.corp.isotelco.net.br)
12:14woernie has left IRC (woernie!~werner@p5ddec5e9.dip0.t-ipconnect.de, Ping timeout: 256 seconds)
14:17lucas_ has joined IRC (lucas_!~lucascast@177-185-131-162.corp.isotelco.net.br)
14:19lucascastro has left IRC (lucascastro!~lucascast@177-185-131-162.corp.isotelco.net.br, Ping timeout: 240 seconds)
14:24woernie has joined IRC (woernie!~werner@p5ddec4f5.dip0.t-ipconnect.de)
14:32lucas_ has left IRC (lucas_!~lucascast@177-185-131-162.corp.isotelco.net.br, Ping timeout: 268 seconds)
15:19libh has joined IRC (libh!~libh@c-24-30-27-91.hsd1.ga.comcast.net)
15:20
<libh>
I read somewhere that ltsp only really works with GNOME or MATE, is that true or not?
15:22
<alkisg>
Νοτ
15:22
Not, even
15:22
I've tested it with MATE, GNOME, KDE, XFCE, LXDE and LXQT, but it should work in all the other ones as well. It even works without a DE.
15:23
<libh>
Thank you.
15:24
With LTSP, does this mean I have have a fleet of low spec computers be used to connect to a powerful server even if I was doing say video editing?
15:24
<alkisg>
No. It just means that you need to maintain one installation instead of many. It doesn't change what you can do with your computers.
15:27
<libh>
I thought LTSP made it possible to share resources with many different computers.
15:27
<alkisg>
No, it's not related to clustering. With LTSP, you can netboot many computers from the same image. That image has the same abilities as if it was installed locally.
15:28
It can e.g. have x2go or xrdp installed, and with that, you can do "remote desktop" to a powerful server, this is somewhat called "thin clients"
15:28
But without x2go/xrdp, it's just normal netbooted "fat" clients, that run the apps locally with their own CPU/RAM/GPU
15:28
<libh>
And if I used xrdp, I can then use a powerful GPU/CPU even if the local computer doesn't have that installed?
15:31
<alkisg>
Yes, but note that remote desktop has a latency when updating the screen
15:31
E.g. if you play youtube, you see 5-10 fps, not 30-60 fps
15:32
<libh>
You think that just having each computer be as powerful as the LTSP server be more ideal?
15:33
<alkisg>
I think that fat clients are better suited for desktop workstations, and powerful servers for running math programs or other intensive long running tasks
15:33
So, ltsp fat clients in general should meet the Ubuntu/Debian/whatever recommended hardware requirements
15:34
Thin clients are fine for tasks that don't require a lot of video updates, e.g. not for web surfing
15:35
<libh>
So a basic i5 dell computer with be ideal for a "fat client" that would connect to the powerful server and do demanding tasks on the fat client?
15:36
<alkisg>
Yes
15:37
E.g. for schools here, I recommend an i3 with 4 GB RAM. While for my own office, I prefer i5 with 8 GB RAM.
15:37
<libh>
i5 with 8GB of RAM for the local fat client or the server itself?
15:39
<alkisg>
For the fat client. The server doesn't really need to be powerful, it just needs a fast local disk
15:39
https://ubuntu.com/download/desktop => recommended requirements: 4 GB system memory
15:40
Of course if you install e.g. lxde, and don't run a browser, you can boot clients with less than 512 MB RAM
15:40
But for web surfing etc, you should follow the recommended requirements of the distribution and DE you choose
15:40
<libh>
What specs do you recommend for the fat client if we're talking about multimedia such as video editing, video encoding, streaming video, GIMP, and so on?
15:41
<alkisg>
Well it depends; for a school I would say i3 with 8 GB RAM; for a professional multimedia environment, they might need 16 GB RAM or even more
15:42
That part isn't related to LTSP, it's the same as local installations
15:42
LTSP will just put your installation on the network instead of on a local disk
15:42
It doesn't change the requirements or the running speed
15:43
A professional that opens an image of 5000x5000 pixels needs more RAM than a hobbyist that opens an HD image
15:43
<libh>
Okay, that makes sense. I was under the false impression I could do anything on any specs because the server would handle the entire load itself, even down to GPUs.
15:44
<alkisg>
If you use x2go, then that's the case. But for desktop stuff, it's not worth it to invest to a powerful server and cheap clients.
15:45
<libh>
Thanks, I'll keep the server and clients as equals.
15:45
<alkisg>
Ten i5 clients with 4 or 8 GB RAM, will run a whole lot better than a server with ten times more powerful CPU, and 40 or 80 GB RAM. Plus, they'll be cheaper.
15:46
<libh>
What makes LTSP special compared to a regular netboot and using NFS outside of LTSP?
16:01
<alkisg>
Regular netboot is for a single client
16:02
LTSP adds some magic to simplify netbooting, global configuration, multiple clients via overlayfs from the same readonly image, pam authentication for logins etc
16:02
It's all in the ltsp.org start page
16:05libh has left IRC (libh!~libh@c-24-30-27-91.hsd1.ga.comcast.net, Quit: Leaving)
16:07
<alkisg>
You're welcome :D
16:18lucas_ has joined IRC (lucas_!~lucascast@192-140-51-239.static.oncabo.net.br)
18:28woernie has left IRC (woernie!~werner@p5ddec4f5.dip0.t-ipconnect.de, Ping timeout: 240 seconds)
18:28woernie has joined IRC (woernie!~werner@p5b296add.dip0.t-ipconnect.de)
18:57woernie has left IRC (woernie!~werner@p5b296add.dip0.t-ipconnect.de, Ping timeout: 240 seconds)
18:58woernie has joined IRC (woernie!~werner@p5b296979.dip0.t-ipconnect.de)
21:20vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)
22:32ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)