|01:25||fnurl has left IRC (firstname.lastname@example.org, Ping timeout: 250 seconds)|
|01:25||fnurl has joined IRC (email@example.com)|
|02:03||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Remote host closed the connection)|
|08:50||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|10:05||woernie has joined IRC (woernie!~werner@p50867FED.dip0.t-ipconnect.de)|
|10:29||GodFather has left IRC (GodFatherfirstname.lastname@example.org, Read error: Connection reset by peer)|
|10:29||GodFather has joined IRC (GodFatheremail@example.com)|
|10:57||adrianor1 has joined IRC (firstname.lastname@example.org)|
|11:00||adrianorg has left IRC (email@example.com, Ping timeout: 246 seconds)|
|11:09||adrianor1 has left IRC (firstname.lastname@example.org, Ping timeout: 244 seconds)|
|11:27||adrianorg has joined IRC (email@example.com)|
|11:59||fnurl has left IRC (firstname.lastname@example.org, Ping timeout: 268 seconds)|
|12:00||fnurl has joined IRC (email@example.com)|
|14:22||gdi2k has left IRC (firstname.lastname@example.org, Ping timeout: 245 seconds)|
|18:18||woernie has left IRC (woernie!~werner@p50867FED.dip0.t-ipconnect.de, Remote host closed the connection)|
|18:45||adrianor1 has joined IRC (email@example.com)|
|18:46||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 250 seconds)|
|18:55||adrianor1 has left IRC (email@example.com, Ping timeout: 244 seconds)|
|19:15||adrianorg has joined IRC (firstname.lastname@example.org)|
|20:03||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)|
|20:44||sukhbir has joined IRC (email@example.com)|
Bidirectional communication with jetpipe
Yes it is
Is bi-directional communication now supported by jetpipe?
There hasn't been any work on jetpipe for 10 years or more
So bi-directional communication is still not supported?
We are still using LTSP 4.2 to communicate with weight scales and signature pads
LTSP 4.2 hasn't seen any updates since ...15? years?
We cannot upgrade to LTSP 5 because of jetpipe
Can't you use ltsp fat clients?
Thin client setups are not recommended nowadays
I do not know about 'fatclient', but I do know about these similar topics: 'fatclient-printers', 'fatclients'
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
install: http://wiki.ltsp.org/wiki/Installation/Ubuntu for Ubuntu, or http://wiki.ltsp.org/wiki/Installation for other distributions
Read the installation page for modern-style instructions on how to setup and maintain ltsp
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
Error: "p910nd" is not a valid command.
I'll check p910nd out. I prefer to stick with thin clients for POS workstations.
I don't think p910nd supports bidirectional communication either
I don't think it's part of the protocol
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
Any client with > $50 nowadays (e.g. raspberries, tv boxes) works better as fat than thin
And they need a lot less bandwidth, so you can serve e.g. 100 pos systems with a single, low cpu, low ram server
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:18||GodFather has left IRC (GodFatherfirstname.lastname@example.org, Ping timeout: 246 seconds)|