IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 18 October 2017 (all times are UTC)
| 01:06 | mistik1_ has joined IRC (mistik1_!~mistik1@69.160.115.104) | |
| 01:08 | mistik1 has left IRC (mistik1!~mistik1@184.170.55.22, Ping timeout: 248 seconds) | |
| 02:59 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14) | |
| 03:15 | mistik1 has joined IRC (mistik1!~mistik1@184.170.34.114) | |
| 03:17 | mistik1_ has left IRC (mistik1_!~mistik1@69.160.115.104, Ping timeout: 255 seconds) | |
| 03:31 | neops has left IRC (neops!52fb1f46@gateway/web/freenode/ip.82.251.31.70, Ping timeout: 260 seconds) | |
| 03:53 | qqqqqqqq19 has joined IRC (qqqqqqqq19!~guido@p5DD6F1B2.dip0.t-ipconnect.de) | |
| 03:57 | qqqqqqqqq9 has left IRC (qqqqqqqqq9!~guido@p5DD6FA8C.dip0.t-ipconnect.de, Ping timeout: 248 seconds) | |
| 04:44 | mistik1 has left IRC (mistik1!~mistik1@184.170.34.114, Ping timeout: 240 seconds) | |
| 04:49 | vagrantc has joined IRC (vagrantc!~vagrant@75.164.166.0) | |
| 04:49 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 04:51 | <alkisg> sbalneav1, vagrantc, what's the last status on libpam-external? This repository is empty: https://github.com/sbalneav/libpam-external
| |
| 04:52 | Do I remember correctly that we're supposed to use libpam-external and libnss-external?
| |
| 05:04 | kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:311f:4500:54a4:602a:8b76:338c) | |
| 05:09 | <vagrantc> alkisg: i think the latest development didn't use it, instead using libpam-python and libnss-extrafiles
| |
| 05:09 | <alkisg> ah
| |
| 05:10 | <vagrantc> sbalneav had a bit of trouble getting one of the *-external modules working correctly, and so explored re-using more existing code :)
| |
| 05:11 | well, i think extrafiles was a concession, as it lacked some feature
| |
| 05:11 | but good enough to start moving forward ... which i really should do, now that stretch is released
| |
| 05:15 | mistik1 has joined IRC (mistik1!~mistik1@69.160.109.37) | |
| 05:16 | Statler has joined IRC (Statler!~Georg@p579FED2E.dip0.t-ipconnect.de) | |
| 05:19 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 05:23 | mistik1 has left IRC (mistik1!~mistik1@69.160.109.37, Remote host closed the connection) | |
| 05:45 | kjackal_ has left IRC (kjackal_!~quassel@2a02:587:311f:4500:54a4:602a:8b76:338c, Ping timeout: 255 seconds) | |
| 06:21 | kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:311f:4500:54a4:602a:8b76:338c) | |
| 06:47 | kjackal_ has left IRC (kjackal_!~quassel@2a02:587:311f:4500:54a4:602a:8b76:338c, Remote host closed the connection) | |
| 06:53 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 07:11 | henry_ has joined IRC (henry_!b5c6b043@gateway/web/freenode/ip.181.198.176.67) | |
| 07:12 | henry_ has left IRC (henry_!b5c6b043@gateway/web/freenode/ip.181.198.176.67) | |
| 07:19 | Statler has left IRC (Statler!~Georg@p579FED2E.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 07:46 | ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 240 seconds) | |
| 07:47 | ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de) | |
| 07:53 | Statler has joined IRC (Statler!~Georg@gwrz3.lohn24.de) | |
| 08:25 | qqqqqqqqq9 has joined IRC (qqqqqqqqq9!~guido@p5DD6F1B2.dip0.t-ipconnect.de) | |
| 08:28 | qqqqqqqq19 has left IRC (qqqqqqqq19!~guido@p5DD6F1B2.dip0.t-ipconnect.de, Ping timeout: 248 seconds) | |
| 08:36 | kjackal_ has joined IRC (kjackal_!~quassel@onopfy.static.otenet.gr) | |
| 08:40 | kjackal_ has left IRC (kjackal_!~quassel@onopfy.static.otenet.gr, Remote host closed the connection) | |
| 08:49 | kjackal_ has joined IRC (kjackal_!~quassel@onopfy.static.otenet.gr) | |
| 09:06 | kjackal_ has left IRC (kjackal_!~quassel@onopfy.static.otenet.gr, Ping timeout: 255 seconds) | |
| 09:10 | kjackal_ has joined IRC (kjackal_!~quassel@onopfy.static.otenet.gr) | |
| 09:46 | zamba has left IRC (zamba!marius@flage.org, Ping timeout: 248 seconds) | |
| 09:50 | zamba has joined IRC (zamba!marius@flage.org) | |
| 09:50 | kjackal__ has joined IRC (kjackal__!~quassel@onopfy.static.otenet.gr) | |
| 09:52 | kjackal___ has joined IRC (kjackal___!~quassel@onopfy.static.otenet.gr) | |
| 09:53 | kjackal_ has left IRC (kjackal_!~quassel@onopfy.static.otenet.gr, Read error: Connection reset by peer) | |
| 09:56 | kjackal__ has left IRC (kjackal__!~quassel@onopfy.static.otenet.gr, Ping timeout: 240 seconds) | |
| 10:17 | kjackal___ has left IRC (kjackal___!~quassel@onopfy.static.otenet.gr, Ping timeout: 248 seconds) | |
| 10:41 | GodFather has joined IRC (GodFather!~rcc@cpe-74-75-116-248.maine.res.rr.com) | |
| 10:42 | kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:311f:4500:c493:83ab:61d3:9379) | |
| 10:45 | kjackal__ has joined IRC (kjackal__!~quassel@2a02:587:311f:4500:c493:83ab:61d3:9379) | |
| 10:59 | kjackal__ has left IRC (kjackal__!~quassel@2a02:587:311f:4500:c493:83ab:61d3:9379, Remote host closed the connection) | |
| 10:59 | kjackal_ has left IRC (kjackal_!~quassel@2a02:587:311f:4500:c493:83ab:61d3:9379, Remote host closed the connection) | |
| 11:07 | GodFather has left IRC (GodFather!~rcc@cpe-74-75-116-248.maine.res.rr.com, Read error: Connection reset by peer) | |
| 11:07 | GodFather has joined IRC (GodFather!~rcc@cpe-74-75-116-248.maine.res.rr.com) | |
| 12:06 | kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:311f:4500:959d:fa7c:984c:4e12) | |
| 12:16 | kjackal_ has left IRC (kjackal_!~quassel@2a02:587:311f:4500:959d:fa7c:984c:4e12, Remote host closed the connection) | |
| 12:43 | bennabiy has left IRC (bennabiy!bennabiyma@gateway/shell/matrix.org/x-hbmfkpawbcreetrv, *.net *.split) | |
| 12:51 | kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:311f:4500:e53e:1957:bc87:4c22) | |
| 12:54 | Guest46716 has joined IRC (Guest46716!bennabiyma@gateway/shell/matrix.org/x-qknhmyjazlolqszc) | |
| 13:18 | kjackal_ has left IRC (kjackal_!~quassel@2a02:587:311f:4500:e53e:1957:bc87:4c22, Remote host closed the connection) | |
| 13:46 | kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:311f:4500:bddf:c3cf:df:46e3) | |
| 14:48 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
| 14:59 | GodFather has left IRC (GodFather!~rcc@cpe-74-75-116-248.maine.res.rr.com, Quit: Ex-Chat) | |
| 15:00 | GodFather has joined IRC (GodFather!~rcc@cpe-74-75-116-248.maine.res.rr.com) | |
| 15:31 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection) | |
| 16:02 | kjackal_ has left IRC (kjackal_!~quassel@2a02:587:311f:4500:bddf:c3cf:df:46e3, Remote host closed the connection) | |
| 18:10 | Statler has left IRC (Statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection) | |
| 18:13 | markus_e92 has left IRC (markus_e92!~markus_e9@91-115-209-0.hdsl.highway.telekom.at, Ping timeout: 246 seconds) | |
| 18:19 | markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-209-0.hdsl.highway.telekom.at) | |
| 18:20 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 18:22 | Natureshadow has left IRC (Natureshadow!~Naturesha@commu.teckids.org, Read error: Connection reset by peer) | |
| 18:46 | <Hyperbyte> Hi alkisg, you around? :-)
| |
| 18:50 | <alkisg> Hey Hyperbyte
| |
| 18:51 | <Hyperbyte> How's it going?
| |
| 18:51 | <alkisg> Life, fine! LTSP, not so much :D
| |
| 18:51 | How are you?
| |
| 18:51 | <Hyperbyte> I have an issue with ltsp-update-kernels not honoring my latest changes to /etc/ltsp/update-kernels.conf. Is there some cache somewhere?
| |
| 18:51 | I'm great. Why LTSP not so much?
| |
| 18:51 | <alkisg> No funding, so no coding, so... you know
| |
| 18:51 | Is that ltsp-pnp?
| |
| 18:52 | <Hyperbyte> Nah, regular.
| |
| 18:52 | It seems problems went away when I actually installed a new kernel on the client.
| |
| 18:52 | <alkisg> That's inside the chroot, right?
| |
| 18:52 | It goes like this
| |
| 18:52 | <Hyperbyte> I guess it's cached somehow on a per-kernel basis?
| |
| 18:52 | <alkisg> Edit update-kernels.conf in the chroot
| |
| 18:52 | Run /usr/share/ltsp/update-kernels in the chroot OR install a new kernel, which runs it
| |
| 18:53 | This then updates $CHROOT/boot/pxelinux.cfg
| |
| 18:53 | <Hyperbyte> Ah
| |
| 18:53 | That step I missed. :-) No doubt.
| |
| 18:53 | <alkisg> Then, ltsp-update-image/kernels outside the chroot, copy that pxelinux.cfg in TFTP
| |
| 19:02 | <Hyperbyte> Right
| |
| 19:02 | :-)
| |
| 19:02 | Well that helps.
| |
| 19:02 | Hey what's this about no funding?
| |
| 19:03 | No more funding for Greek schools?
| |
| 19:03 | <alkisg> Yup, since 2015
| |
| 19:03 | <Hyperbyte> Oh wow
| |
| 19:04 | But you guys are still using LTSP en-masse right?
| |
| 19:06 | <vagrantc> we've got to fix this...
| |
| 19:06 | :)
| |
| 19:06 | * vagrantc just uploaded ltsp-manager 17.08.1 to debian experimental | |
| 19:06 | <vagrantc> hopefully it will pass review this time
| |
| 19:08 | <alkisg> (10:04:02 μμ) Hyperbyte: But you guys are still using LTSP en-masse right? => well, for example most schools are still using Ubuntu 12.04 because noone supports or develops it anymore
| |
| 19:09 | In my small region where I'm maintaining around 80 ltsp installations, I've upgraded them to 16.04, but with local changes, not pushed upstream...
| |
| 19:09 | Let's hope for the best, yeah :)
| |
| 19:09 | People are still trying to convince the ministry of education to support it agian
| |
| 19:09 | *again
| |
| 19:10 | vagrantc: yey! let's hope it has a long life! :)
| |
| 19:12 | <vagrantc> alkisg: indeed!
| |
| 19:14 | <Hyperbyte> ltsp-manager?
| |
| 19:14 | <quinox1> is it foolish of me to be using LTSP on 17.10 in about 2 months ?
| |
| 19:14 | <vagrantc> !ltsp-manager | echo Hyperbyte
| |
| 19:14 | <ltsp> Hyperbyte ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
| |
| 19:15 | <vagrantc> quinox1: it's foolish if you don't test it first :)
| |
| 19:15 | <quinox1> I suppose
| |
| 19:15 | quinox1 is now known as quinox | |
| 19:15 | <vagrantc> it should be in moderately ok shape, as i think it's synced from debian, but debian's missing a few things too
| |
| 19:16 | <alkisg> quinox: I don't think anyone checks non-LTS Ubuntu releases, so most likely a few small things will be broken and will need workarounds
| |
| 19:16 | * vagrantc hopes to update ltsp in debian this coming week | |
| 19:19 | <quinox> I guess it should be entirely doable to make a VM server, and get some clients to boot from it since I already use my own DHCP setup
| |
| 19:21 | <-- happily using LTSP for 7 years now, A+++ would buy again
| |
| 19:22 | it might have been longer, I inherited this network setup
| |
| 19:23 | <Hyperbyte> I wonder how long I've been using LTSP.
| |
| 19:24 | * vagrantc switched ~2006-2007 and was using lessdisks before that | |
| 19:24 | <vagrantc> although i haven't had any real-world deployments since 2016 :/
| |
| 19:24 | er, 2015
| |
| 19:24 | <Hyperbyte> First deployment in October 2008.
| |
| 19:25 | Now I maintain 3 deployments. Two thin and one fat.
| |
| 19:25 | One radio station, one radio & tv station and one touroperator office. :-)
| |
| 19:30 | <quinox> with hardware getting cheaper and cheaper, what would be a reason to run thin clients?
| |
| 19:33 | <Hyperbyte> For one it's budget related. Existing thin client setup with Windows/Citrix that broke down and turned out to be illegal software.
| |
| 19:34 | For other one it was budget related, but now we kinda like the cool and quiet office. Plus we've had the setup for almost 10 years now and it works.
| |
| 19:36 | <quinox> cool
| |
| 19:36 | <vagrantc> quinox: there's not much reason to run thin clients anymore ... which is why we've been recommending LTSP fat clients lately
| |
| 19:36 | quinox: still has the advantage of centralized management and network booting, but also takes advantage of modern client hardware
| |
| 19:36 | <quinox> yeah
| |
| 19:37 | but indeed, no need to let existing hardware go to waste
| |
| 19:37 | <vagrantc> and by modern, i think that means anything produced in the last 8-10 years
| |
| 19:38 | certainly anything 5+ years
| |
| 19:39 | * vagrantc originally got involved with thin clients at a computer recycling organization | |
| 20:00 | <Hyperbyte> vagrantc, still, now that I have thin clients running smoothly at this specific office, if I'd have budget for new clients, I'd much rather just buy a new server with that. Would still be cheaper as well, but aside from that I like having as little as possible hardware under the desks. Less targets for accidents, failures or cleaning.
| |
| 20:01 | * alkisg doesn't think fat clients have more hardware than thin clients :) | |
| 20:02 | <alkisg> Also, it's possible that wayland won't work very well with thin clients, so fat there has its benefits
| |
| 20:02 | <vagrantc> Hyperbyte: same amount of hardware
| |
| 20:02 | <Hyperbyte> Clients I have currently won't support all our software fat.
| |
| 20:02 | <alkisg> And, many software stacks don't care about remote Xorg anymore, eg. gl, compositing, desktop environments...
| |
| 20:02 | <Hyperbyte> 1.5ghz / 1gb ram. It's not enough. So I'd have to buy new ones.
| |
| 20:03 | <alkisg> Yeah, talking about the next purchase
| |
| 20:03 | My advice to schools is, use thin clients when you have them, but never buy new thin client hardware
| |
| 20:03 | <vagrantc> Hyperbyte: basically, the technology that makes thin clients work is being deprecated, partly by accident, and partly by intention
| |
| 20:04 | <Hyperbyte> alkisg, that I agree with. These are ~8 year old clients still running fine. If I would need to replace them, I might go different route.
| |
| 20:04 | vagrantc, yeah, I know. But still... it ain't broken yet. :-)
| |
| 20:04 | <vagrantc> indeed
| |
| 21:08 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 22:28 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |
| 23:01 | zamba has left IRC (zamba!marius@flage.org, Ping timeout: 240 seconds) | |
| 23:03 | zamba has joined IRC (zamba!marius@flage.org) | |