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


Channel log from 9 November 2023   (all times are UTC)

00:38wyre is now away: Auto away at Thu Nov 9 00:38:42 2023 UTC
03:37Vercas2 has left IRC (Vercas2!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 264 seconds)
06:36wyre is back
07:09woernie has joined IRC (woernie!~werner@p5ddec891.dip0.t-ipconnect.de)
07:23parlos has joined IRC (parlos!~pal@2001:6b0:2a:c240:aa5e:45ff:fed1:c4a1)
07:29wyre is now away: Auto away at Thu Nov 9 07:29:30 2023 UTC
08:05wyre is back
09:32ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
09:47wyre is now away: Auto away at Thu Nov 9 09:47:43 2023 UTC
09:56alkisg has left IRC (alkisg!~Thunderbi@2a02:587:7450:a000:56e0:4cff:fe68:d, Quit: alkisg)
10:00alkisg has joined IRC (alkisg!~Thunderbi@2a02:587:7450:a000:56e0:4cff:fe68:d)
10:00wyre is back
10:11parlos has left IRC (parlos!~pal@2001:6b0:2a:c240:aa5e:45ff:fed1:c4a1, Quit: Konversation terminated!)
10:16alkisg has left IRC (alkisg!~Thunderbi@2a02:587:7450:a000:56e0:4cff:fe68:d, Quit: alkisg)
10:31alkisg has joined IRC (alkisg!~Thunderbi@2a02:587:7450:a000:56e0:4cff:fe68:d)
10:36sugarbeet has left IRC (sugarbeet!~barbas@81.4.123.134, Server closed connection)
10:37sugarbeet has joined IRC (sugarbeet!~barbas@81.4.123.134)
10:38wyre is now away: Auto away at Thu Nov 9 10:38:47 2023 UTC
10:48wyre is back
10:53wyre is now away: Auto away at Thu Nov 9 10:53:30 2023 UTC
11:00wyre is back
11:14wyre is now away: Auto away at Thu Nov 9 11:14:18 2023 UTC
11:20wyre is back
11:26wyre is now away: Auto away at Thu Nov 9 11:26:32 2023 UTC
11:33wyre is back
11:42wyre is now away: Auto away at Thu Nov 9 11:42:00 2023 UTC
12:56wyre is back
13:37ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
15:32wyre is now away: Auto away at Thu Nov 9 15:32:17 2023 UTC
16:09wyre is back
16:16wyre is now away: Auto away at Thu Nov 9 16:15:56 2023 UTC
17:05Phio has joined IRC (Phio!~Phio@2a02:810d:cc0:e40:5868:8e24:2a61:e0af)
17:19Phio has left IRC (Phio!~Phio@2a02:810d:cc0:e40:5868:8e24:2a61:e0af, Quit: Client closed)
17:43wyre is back
17:49woernie has left IRC (woernie!~werner@p5ddec891.dip0.t-ipconnect.de, Ping timeout: 252 seconds)
18:11woernie has joined IRC (woernie!~werner@p5ddec891.dip0.t-ipconnect.de)
19:11mcgwrath has joined IRC (mcgwrath!~mcgwrath@2607:fa49:d53c:eb00:d81:8171:9420:3bbe)
19:12
<mcgwrath>
Does LTSP tie into Ubuntu's livepatch system, or since a chrootless image is created from root, one would have to recreate the image when the system is patched?
19:36
<alkisg>
mcgwrath: livepatch is for live kernel patching; you don't reboot your clients?!
19:36
mcgwrath: a good policy is to run `apt full-upgrade; ltsp image /` periodically on the server, AND reboot the server and the clients
19:37
People that boast "567 days uptime!" should be ashamed of it, not proud :D
19:38
<mcgwrath>
Normally the clients are always on, until I get notified that there's an update.  Then I do the updates, run ltsp initrd, if needed reboot clients and then the server.
19:39
lol, no 500 day + uptime. ;)
19:39
The system is seasonal, and I have the server with me now as the site is shutdown for the winter.
19:43
It looks like there was an image made in April 2023 and another at the beginning of October 2023.  So no, no years of uptime. :P
19:44
But if I do livepatch, and create an image of / every few months, that's okay?
19:46
<alkisg>
When you get important updates on the server, run ltsp image /, and then the clients will get the updates when they're rebooted
19:46
<mcgwrath>
I get that the clients won't have the latest and greatest *immediately*, but at least the main server will, and images (created with chrootless) will be built upon that.  That's not a problem?
19:47
<alkisg>
Livepatch is not related to security issues. It's just for the kernel; you don't want to have all the rest of the system unprotected
19:47
Livepatch along with selected service restarting may make sense for hypervisors on the cloud
19:47
It doesn't make any sense for desktop installations
19:48
You may even apply the updates on the server, and run ltsp image /, and the clients will get all of them on their next reboot, even if the server itself hasn't rebooted and hasn't applied the updates to itself
19:49
<mcgwrath>
"Live-patch" - pardon, specifically an Ubuntu Pro subscription.
19:49
<alkisg>
Don't bother with it. You care about security updates, not about livepatch
19:50
<mcgwrath>
Right, I used the wrong term at the beginning of the chat.
19:50
It's security updates and patches that I'm looking for on the server, and then rolling that into the client image..
19:51
<alkisg>
Right, do what I wrote above
19:51
<mcgwrath>
Or am I going about this all wrong? :P
19:51
<alkisg>
09:46:44 PM - alkisg: When you get important updates on the server, run ltsp image /, and then the clients will get the updates when they're rebooted
19:51
<mcgwrath>
yeah, full-upgrade and reimage /
19:51
Yes.
19:51
:)
19:51
<alkisg>
Yes. While ltsp initrd doesn't help there, you need ltsp image
19:52
<mcgwrath>
Nono- sometimes there's new users, client stations that are assigned a user based on the MAC address... yadda
19:52
(hence why sometimes initrd gets called.)
19:52
But yes, overall, very cool system!  Much thanks. :)
19:53
<alkisg>
ltsp initrd is needed when you update ltsp.conf, add new users or get a newer ltsp version
19:53
<mcgwrath>
(y)
20:02vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50)
20:04
<mcgwrath>
Cools, I was reading your ubuntu wiki page alkisg, that's quite the list of degrees!  Next on the list is server-failover. 8)
20:09
<alkisg>
mcgwrath: yeah unfortunately I have more than 25 years of studies; I hope I won't need anything else in the future :D
20:09
<mcgwrath>
X) :')
20:10
Yeah, my partner earned a PhD in forensic psych, she always jokes that she was in school for her first 3.5 decades.
20:22woernie has left IRC (woernie!~werner@p5ddec891.dip0.t-ipconnect.de, Quit: http://quassel-irc.org - Chat comfortably. Anywhere.)
21:28mcgwrath has left IRC (mcgwrath!~mcgwrath@2607:fa49:d53c:eb00:d81:8171:9420:3bbe, Quit: Client closed)
23:47vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50, Quit: leaving)