LTSP 5 is in minimal maintenance mode
The new LTSP is hosted at https://ltsp.github.io

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


Channel log from 3 February 2019   (all times are UTC)

01:25fnurl has left IRC (fnurl!url@host31-49-219-13.range31-49.btcentralplus.com, Ping timeout: 250 seconds)
01:25fnurl has joined IRC (fnurl!url@host31-49-219-13.range31-49.btcentralplus.com)
02:03vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Remote host closed the connection)
08:50ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
10:05woernie has joined IRC (woernie!~werner@p50867FED.dip0.t-ipconnect.de)
10:29GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Read error: Connection reset by peer)
10:29GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net)
10:57adrianor1 has joined IRC (adrianor1!~adrianorg@187.115.110.168)
11:00adrianorg has left IRC (adrianorg!~adrianorg@177.156.56.190, Ping timeout: 246 seconds)
11:09adrianor1 has left IRC (adrianor1!~adrianorg@187.115.110.168, Ping timeout: 244 seconds)
11:27adrianorg has joined IRC (adrianorg!~adrianorg@177.18.176.175)
11:59fnurl has left IRC (fnurl!url@host31-49-219-13.range31-49.btcentralplus.com, Ping timeout: 268 seconds)
12:00fnurl has joined IRC (fnurl!url@host31-49-219-13.range31-49.btcentralplus.com)
14:22gdi2k has left IRC (gdi2k!~gdi2k@host86-185-148-160.range86-185.btcentralplus.com, Ping timeout: 245 seconds)
18:18woernie has left IRC (woernie!~werner@p50867FED.dip0.t-ipconnect.de, Remote host closed the connection)
18:45adrianor1 has joined IRC (adrianor1!~adrianorg@177.134.59.235)
18:46adrianorg has left IRC (adrianorg!~adrianorg@177.18.176.175, Ping timeout: 250 seconds)
18:55adrianor1 has left IRC (adrianor1!~adrianorg@177.134.59.235, Ping timeout: 244 seconds)
19:15adrianorg has joined IRC (adrianorg!~adrianorg@186.215.19.173)
20:03ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
20:44sukhbir has joined IRC (sukhbir!~joe@erx208b171170.smarttadsl.com)
20:46
<sukhbir>
Bidirectional communication with jetpipe
20:47
<alkisg>
Yes it is
20:47
<sukhbir>
Is bi-directional communication now supported by jetpipe?
20:48
<alkisg>
There hasn't been any work on jetpipe for 10 years or more
20:49
<sukhbir>
So bi-directional communication is still not supported?
20:50
We are still using LTSP 4.2 to communicate with weight scales and signature pads
20:50
<alkisg>
Haha
20:51
LTSP 4.2 hasn't seen any updates since ...15? years?
20:51
<sukhbir>
We cannot upgrade to LTSP 5 because of jetpipe
20:51
<alkisg>
How so?
20:51
Can't you use ltsp fat clients?
20:51
Thin client setups are not recommended nowadays
20:52
<sukhbir>
Really?
20:52
<alkisg>
!fatclient
20:52
<ltsp>
I do not know about 'fatclient', but I do know about these similar topics: 'fatclient-printers', 'fatclients'
20:52
<alkisg>
!fatclients
20:52
<ltsp>
fatclients: Nowadays LTSP supports thin and fat clients. They are both diskless and netbooted from the same LTSP chroot, but while thin clients run the session on the server and transfer the screen, fat clients run the session locally with their own CPU/RAM, thus performing amazingly better. See also !ltsp-pnp and https://help.ubuntu.com/community/UbuntuLTSP/FatClients
20:52
<alkisg>
!install
20:52
<ltsp>
install: http://wiki.ltsp.org/wiki/Installation/Ubuntu for Ubuntu, or http://wiki.ltsp.org/wiki/Installation for other distributions
20:52
<alkisg>
Read the installation page for modern-style instructions on how to setup and maintain ltsp
20:53
There's a p10nd something package in debian, can be used to replace jetpipe, but people don't use thin clients anymore, so noone cares much about it
21:12
!p910nd
21:12
<ltsp>
Error: "p910nd" is not a valid command.
21:13
<alkisg>
http://p910nd.sourceforge.net/
21:19
<sukhbir>
thanks.
21:19
I'll check p910nd out. I prefer to stick with thin clients for POS workstations.
21:41
<alkisg>
Why?
21:41
I don't think p910nd supports bidirectional communication either
21:41
I don't think it's part of the protocol
21:42
Also note that the next version of ltsp will probably not support thin clients at all; except for the various programs like x2go, xfreerdp, which offer a remote desktop on top of a "fat client" session
21:43
Any client with > $50 nowadays (e.g. raspberries, tv boxes) works better as fat than thin
21:43
!cheap-client
21:43
<ltsp>
cheap-client: https://www.gearbest.com/tv-box-c_11262/?attr=2081-1279
21:44
<alkisg>
And they need a lot less bandwidth, so you can serve e.g. 100 pos systems with a single, low cpu, low ram server
21:45
In any case, if you are certain you prefer thin clients and need normal printing, just install cups and share the printer from there
22:18GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 246 seconds)