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


Channel log from 14 September 2022   (all times are UTC)

06:04ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:22alkisg_web has joined IRC (alkisg_web!~alkisg_we@2a02:587:752d:a900:c24a:ff:fe02:bc1e)
09:13bcg__ has left IRC (bcg__!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi, Ping timeout: 244 seconds)
09:47bcg__ has joined IRC (bcg__!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi)
11:04Guest0 has joined IRC (Guest0!~Guest0@p57b67d50.dip0.t-ipconnect.de)
11:09bcg__ has left IRC (bcg__!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi, Quit: bcg__)
11:09
<Guest0>
Hello everybody, I got a question on ltspclient for moyOS. Is it possible to connect to ltsp terminal server viy imac with macOS
11:09
typo vij=via
11:15bcg has joined IRC (bcg!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi)
11:23* alkisg has never even seen macOS
11:29
<Guest0>
Does the clienside need a booted linux image?
11:29
<alkisg>
No, it only needs netbooting ability, e.g. bios pxe or the ipxe.org software
11:30
I think they have used x86 architecture with uefi at some point, tha should be easy to netboot if it's not otherwise locked
11:30
<Guest0>
but what kind of software gets started on client side. i know what netbooting or pxe is.
11:31
<alkisg>
Check the site I mentioned, ipxe.org
11:31
It's a small program like a boot manager that loads the kernel/initrd over the network
11:31
Then its role is finished and the kernel takes over
11:32
<Guest0>
The problem is, that the imac has bad linux graphics support. I insatlled a ubuntu workstation. but it does not support modern graphics
11:32
<alkisg>
The same thing will happen if you netboot it then
11:32
LTSP is diskless Linux
11:33
A completely different approach would be to boot macos and use remote desktop to connect to some linux server
11:33
<Guest0>
diskless linux on both sides? server and client?
11:33
<alkisg>
That's remote desktop,and it's unrelated to ltsp
11:33
No, the server has a disk
11:35
<Guest0>
ok, now i understand. Has ltsp somthing todo with nomachine or is nomachine commercial.
11:35
<alkisg>
nomachine is commercial remote desktop, it's unrelated to ltsp
11:35
LTSP is if you want to maintain one installation and boot any number of diskless machines from the same template image
11:35
It saves disks and administration effort
11:36
Remote desktop requires a local disk and operating system; ltsp doesn't
11:36
<Guest0>
How does ltsp handle the different hardware on the clients. Do they make several images for the different machines or do they pack multiple drivers into one image?
11:37
<alkisg>
It's like an ubuntu live cd; linux live cds have all the drivers on it
11:37
<Guest0>
I have knowledge to windows terminal server and thin clients. At home i only use linux server and workstations.
11:38
So it is for environment with only slightly diffeing hardware clients.
11:43
The first versions seemed to use the xserver protocol. In witch way does the graphic transmission happen today. Like rdp, spice or vnc.
11:53
Oh, just so an article in german that mentions that it uses its own windows manager and went from xdcmp to ssh-x transmission.
11:53
typo so=saw
11:56
<alkisg>
Imagine putting a live cd into a file server
11:56
Then, booting 1000 clients from the same live cd
11:56
Do they need to have similar hardware? NO.
11:57
Do they need to have the same architecture? Yes.
11:57
If you want to boot different architectures (e.g. x86 32bit, 64bit, arm, powerpc) you'd need one livecd (ltsp image) for each architecture
11:57
<Guest0>
only if you provid plug and play hardware detection and the necessary amount of drivers
11:57
<alkisg>
Other than that, the client hardware doesn't matter, it can be anything as long as it can boot linux
11:57
That plug and play is default in any linux distribution nowadays
11:58
Everything works out of the box
11:58
Otherwise live cds wouldn't exist
11:58
LTSP doesn't transmit any kind of screen. Everything runs locally on the client. Only the disk is remote
11:59
So instead of "live cd" or "live usb", it's "live network disk image"
11:59
<Guest0>
Your right, but the live cd on my mac does not work, because the graphics card is shitty diferent in firmware from apple.
12:00
<alkisg>
That's a linux matter, it's not an ltsp matter
12:00
LTSP makes linux run over the network, it doesn't provide anything more
12:00
If you have one client, there's no need to use ltsp
12:00
LTSP is for multiple clients
12:01bcg has left IRC (bcg!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi, Ping timeout: 240 seconds)
12:03
<Guest0>
I have already understood, that ltsp is not the right solution for my usecase, but im interested in the technology. I ticled arroun with several remote solutions and multiple virtual machines, (aswell a different usecase)
12:04
<DouglasGiovaniOe>
alkisg: I love LTSP, its fantastic, save money, support, no disks needed, easy administration, all works fine
12:04
<alkisg>
👍️
12:05
<Guest0>
I have a  final Question How does ltsp handle wayland. I thought the graphics is running on the server and only transmitts the compressed content to a client.
12:05jinnjus has joined IRC (jinnjus!~jinnjus@2604:3d08:9b7e:51b0::a99b)
12:05
<alkisg>
Everything runs locally, so wayland also runs locally. LTSP doesn't need to handle graphics at all.
12:06
If you read OLD articles about LTSP, they may confuse you with thin clients and remote desktop and XDMCP stuff. That's no longer the case
12:06
<Guest0>
Did they change that from the first versions?
12:06
<alkisg>
LTSP now is about network booting, and anyone that wants remote desktop can just install one application on top of LTSP
12:07
Yes, LTSP5 defaulted to fat clients, while since 2019 the new LTSP doesn't handle graphics at all
12:07
<Guest0>
Oh thanks, now I understand. Thanks for your patience.
12:07
<alkisg>
The initial LTSP was developed at a time when remote xorg made sense. Now it doesn't; tools like xrdp and x2go are needed instead
12:08
So LTSP doesn't bother with these; anyone that needs them can just install them
12:09
<Guest0>
Seems, I need a big trash bin for my imac ;-)
12:09bcg has joined IRC (bcg!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi)
12:10
<alkisg>
🚮
12:11
<Guest0>
Thanks for the explanations and goodbye.
12:12
<alkisg>
Good by!
12:12
* Goodbye!
12:12Guest0 has left IRC (Guest0!~Guest0@p57b67d50.dip0.t-ipconnect.de, Quit: Guest0)
12:18
<DouglasGiovaniOe>
only pfsene and ipxe are ugly and hard to works together hehehehe
12:24* DouglasGiovaniOe uploaded an image: (8KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/cgOBmJtJQLqoBAfAeOgOsaWM/ltsp-tela9-24-13.png >
12:25
<DouglasGiovaniOe>
what the file name of boot file ltsp server?
12:25
please?
12:43jinnjus has left IRC (jinnjus!~jinnjus@2604:3d08:9b7e:51b0::a99b, Ping timeout: 264 seconds)
13:09we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-07a8-4561-420b-60ea.res6.spectrum.com)
13:18we6jbo has left IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-07a8-4561-420b-60ea.res6.spectrum.com, Remote host closed the connection)
13:58
<alkisg>
Douglas Giovani Oechsler: read the "filename" lines in this page: https://ltsp.org/guides/isc-dhcp-server/
13:59
As I said, pfsense is dumb and cannot do multiple filenames using "if" commands
14:20
<DouglasGiovaniOe>
I am in the pfsense forum and other guy tell me to follow the same link that you show me heheheheheh. Thank you! Lets go! This will need work hehehe and thank support and patience
14:26
<alkisg>
Douglas Giovani Oechsler: if the solution was like 10-minutes-easy, I would have given it to you already; I already have more work than I can handle, I'm not looking for customers.
14:26
Pfsense is dumb, it'll probably require the solution I mention to the github discussion I gave you yesterday
14:28
<DouglasGiovaniOe>
no problem. Thanks all.
14:44vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)
15:01bcg has left IRC (bcg!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi, Quit: bcg)
15:12bcg has joined IRC (bcg!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi)
15:18oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net)
15:22oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net)
15:23oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 268 seconds)
15:32oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net)
15:32oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 265 seconds)
15:37oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net)
15:38oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 250 seconds)
15:44oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net)
15:45oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 250 seconds)
15:50oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 265 seconds)
16:29jinnjus has joined IRC (jinnjus!~jinnjus@2604:3d08:9b7e:51b0::a99b)
16:31jinnjus has left IRC (jinnjus!~jinnjus@2604:3d08:9b7e:51b0::a99b)
17:45alkisg_web has left IRC (alkisg_web!~alkisg_we@2a02:587:752d:a900:c24a:ff:fe02:bc1e, Quit: Client closed)
20:38ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:28oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net)
22:41oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 265 seconds)