LTSP 5 is in minimal maintenance mode
The new LTSP is hosted at

IRC chat logs for #ltsp on (webchat)

Channel log from 21 May 2019   (all times are UTC)

00:57vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 252 seconds)
00:58vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
01:37GodFather has left IRC (GodFather!~rcc@, Ping timeout: 246 seconds)
01:45jeblesh has left IRC (jeblesh!2e78d540@gateway/web/freenode/ip., Ping timeout: 256 seconds)
02:12jeblesh has joined IRC (jeblesh!2e78d540@gateway/web/freenode/ip.
how do i update the image in a chrotless instolation after i updated the kernel, just rerun "ltsp-update-image --cleanup"?
"ltsp-update-image --cleanup /"
the "/" is important, it tells it where the files you want to update are, otherwise i think it defaults to /opt/ltsp/ARCH
02:33jeblesh has left IRC (jeblesh!2e78d540@gateway/web/freenode/ip., Ping timeout: 256 seconds)
02:43jgee9 has left IRC (jgee9!~jgee@, Quit: The Lounge -
03:39vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
04:46nehemiah has left IRC (nehemiah!~nehemiah@, Ping timeout: 268 seconds)
04:55ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
05:36nehemiah has joined IRC (nehemiah!~nehemiah@
07:06woernie has joined IRC (woernie!
07:50statler has joined IRC (statler!
08:13woernie has left IRC (woernie!, Remote host closed the connection)
08:55eu^athedsl-36158 has joined IRC (eu^athedsl-36158!
08:55eu^athedsl-36158 has left IRC (eu^athedsl-36158!, Remote host closed the connection)
09:34GodFather has joined IRC (GodFather!~rcc@
10:09woernie has joined IRC (woernie!
10:45zerkalo has joined IRC (zerkalo!
12:28Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:55GodFather has left IRC (GodFather!~rcc@, Ping timeout: 258 seconds)
13:20nehemiah has left IRC (nehemiah!~nehemiah@, Remote host closed the connection)
13:47os_a has joined IRC (os_a!~Thunderbi@
13:59os_a has left IRC (os_a!~Thunderbi@, Quit: os_a)
14:01vsuojane1 has joined IRC (vsuojane1!
14:05sutula_ has joined IRC (sutula_!
14:06sutula has left IRC (sutula!, *.net *.split)
14:06vsuojanen has left IRC (vsuojanen!, *.net *.split)
14:06mwalters has left IRC (mwalters!, *.net *.split)
14:13mwalters has joined IRC (mwalters!
14:49sutula_ is now known as sutula
14:56nehemiah has joined IRC (nehemiah!~nehemiah@
15:02woernie has left IRC (woernie!, Remote host closed the connection)
I've been writing an app since a while now where a network booted client makes a socket connection to the server while booting. The client then gets the SSH public key from the the server and sets it as authorized key.
On top of that I've been writing some functionality to manage the clients. Boot them, shut them down, remote control them using VNC and websockets etc.
It's written in Node. I can share it by the beginning of June as I'm still finishing it up. I'm presenting it next week but I got the 'OK' to share it if there would be any interest.
I'll very likely still do something with ipxe in the app as that's something I've been hoping to do instead of dynamically generate syslinux config files.
hello guys, gm.
15:35nehemiah has left IRC (nehemiah!~nehemiah@, Remote host closed the connection)
15:39nehemiah has joined IRC (nehemiah!~nehemiah@
nehemiah: reimplementing epoptes? :)
16:01uumas has left IRC (uumas!
16:01uumas has joined IRC (uumas!
alkisg: Yes, it it's very similar. The big difference being that it works in the browser. So you can control your clients from anywhere just using the browser.
I guess that I can share what I have but I can not maintain it in LTSP form meaning it'll be very specific to how our organization is working.
nehemiah, that's very nice, monitoring from the browser. Are you releasing the project to open source?
Yes, it will be open source.
17:34woernie has joined IRC (woernie!
17:39woernie has left IRC (woernie!, Ping timeout: 245 seconds)
17:52statler has left IRC (statler!, Remote host closed the connection)
nehemiah: I actually proposed that for last year's gsoc, with the clients connecting to the server via https (not ssh), the server written in node.js, and the gui in javascript; but it was too big a rewrite to be in feature parity within 3 months
I think it would need something like a year to be as stable
alkisg: Okay, I'm going to take some time this to make what I have a bit more modular. I experience it extremely robust as the sockets reconnect after an outage and commands are just being send using SSH.
Of course there are always bugs but this is not rocket science so it should be quite stable.
With modular I mean that I'm going to separate our own logic from what you's typically want for LTSP.
18:29vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
epoptes works without ltsp as well
ssh unfortunately is limited to linux
if you're going for web-based, might as well make it cross platform
I see, yes, that is far removed from our use case although you can send information using the sockets of course.
18:47spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Ping timeout: 268 seconds)
21:15kjackal has joined IRC (kjackal!~quassel@
21:17ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
22:17Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
22:23kjackal has left IRC (kjackal!~quassel@, Ping timeout: 245 seconds)