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 23 April 2019   (all times are UTC)

05:33kjackal has joined IRC (kjackal!~quassel@2a02:587:3119:ef00:bdbc:926b:5dfc:1cbc)
05:55ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
05:56kjackal has left IRC (kjackal!~quassel@2a02:587:3119:ef00:bdbc:926b:5dfc:1cbc, Ping timeout: 252 seconds)
06:18kjackal has joined IRC (kjackal!~quassel@static062038141122.dsl.hol.gr)
06:25snurl has joined IRC (snurl!snurl@host81-154-10-106.range81-154.btcentralplus.com)
06:27fnurl has left IRC (fnurl!snurl@host81-154-10-70.range81-154.btcentralplus.com, Ping timeout: 255 seconds)
06:40woernie has joined IRC (woernie!~werner@pD9E8BADB.dip0.t-ipconnect.de)
07:57kjackal has left IRC (kjackal!~quassel@static062038141122.dsl.hol.gr, Ping timeout: 245 seconds)
07:58kjackal has joined IRC (kjackal!~quassel@static062038141122.dsl.hol.gr)
08:14statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
09:01GodFather has left IRC (GodFather!~rcc@143.59.184.72, Ping timeout: 246 seconds)
09:24kjackal has left IRC (kjackal!~quassel@static062038141122.dsl.hol.gr, Quit: No Ping reply in 180 seconds.)
09:24kjackal has joined IRC (kjackal!~quassel@static062038141122.dsl.hol.gr)
09:49ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
09:50ogra has joined IRC (ogra!~ogra_@ubuntu/member/ogra)
10:01kjackal has left IRC (kjackal!~quassel@static062038141122.dsl.hol.gr, Ping timeout: 244 seconds)
10:16kjackal has joined IRC (kjackal!~quassel@2a02:587:3119:ef00:bdbc:926b:5dfc:1cbc)
10:39ogra has left IRC (ogra!~ogra_@ubuntu/member/ogra, Ping timeout: 240 seconds)
10:39ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
10:40ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
10:41ogra has joined IRC (ogra!~ogra_@ubuntu/member/ogra)
11:03GodFather has joined IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net)
12:18Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:44kjackal has left IRC (kjackal!~quassel@2a02:587:3119:ef00:bdbc:926b:5dfc:1cbc, Ping timeout: 258 seconds)
12:44kjackal has joined IRC (kjackal!~quassel@athedsl-173858.home.otenet.gr)
13:55GodFather has left IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net, Ping timeout: 250 seconds)
14:08GodFather has joined IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net)
14:25lee has joined IRC (lee!~lee@flead.loathe.ms)
14:28lee has left IRC (lee!~lee@flead.loathe.ms, Client Quit)
14:30lee has joined IRC (lee!~lee@flead.loathe.ms)
14:34lee has joined IRC (lee!~lee@flead.loathe.ms)
14:34lee has left IRC (lee!~lee@flead.loathe.ms)
15:41kjackal has left IRC (kjackal!~quassel@athedsl-173858.home.otenet.gr, Ping timeout: 276 seconds)
16:08GodFather has left IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net, Ping timeout: 258 seconds)
16:33adrianorg has joined IRC (adrianorg!~adrianorg@186.213.159.56)
16:36adrianor1 has left IRC (adrianor1!~adrianorg@177.18.177.173, Ping timeout: 255 seconds)
17:52statler has left IRC (statler!~Georg@gwrz.lohn24.de, Remote host closed the connection)
17:53
<alkisg>
Heh. getltscfg speed: 0.5 msec in C, 4 msec in shell/awk, 8 msec in python.
17:53
Fortunately we just call it once, so its speed doesn't matter, so we can deprecate the C version.
17:53
Sourcing the result needs 0.3 msec in shell, great.
18:02vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:28
<alkisg>
vagrantc: our new getltscfg: https://termbin.com/alth
18:31
<vagrantc>
alkisg: awk!
18:32
i do find various awk implementations to have incompatible feature sets
18:32
<alkisg>
Hehe, for performance, I needed "tolower", sed like, tr like... all in one call
18:32
And I preferred that it would inside the initramfs too
18:32
<vagrantc>
not sure what the lowest common feature set would be
18:32
<alkisg>
It runs in gawk and in busybox awk; good enough for me
18:33
It's not like sed is any better...
18:33
<vagrantc>
mawk would be good to test
18:35
<alkisg>
mawk works too
18:35adrianor1 has joined IRC (adrianor1!~adrianorg@177.18.50.144)
18:35
<alkisg>
So currently it supports case insensitive [sections] and LIKE=section directives, spaces around the = signs,
18:36
and if someone needs them, multiline directives or even directly embedding shell code
18:36
Like, [192.168.*.*] if [ $RAM -gt 1000 ]; then...
18:37
<vagrantc>
so i'm guessing you were just looking for something minimal to shove into the initramfs?
18:37
<alkisg>
All in 1/10 of the initial code, and interpreted, so that we don't need an ltsp-client binary package
18:37
That, and to avoid the binary packages
18:38
So that the ltsp-initrd.img is arch-agnostic
18:38adrianorg has left IRC (adrianorg!~adrianorg@186.213.159.56, Ping timeout: 250 seconds)
18:38
<alkisg>
Actually we can run the awk script on the server to translate lts.conf to lts.sh (shell sourceable), and put lts.sh to the initrd...
18:38
That's a detail though
18:41
<vagrantc>
alkisg: thought you were trying to kill off lts.conf, but now you're rewriting the parser :)
18:41
<alkisg>
vagrantc: well, the config needs to live some place, even if later on a web service is used to send it to the client
18:42
I want to start ltsp19 without the configuration daemon and without whatever-will-replace-ldm, so that it's doable in a couple of months
18:42
<vagrantc>
how's the awk implementation handle a very large lts.conf ?
18:42
<alkisg>
So I'm thinking the config may live in /etc/ltsp/ltsp.conf (is ltsp.conf better than lts.conf?)
18:43
<vagrantc>
yeah, it'd be nice to fix the name and location
18:43
<alkisg>
Oh awk is C, so very efficiently
18:44
Like, we can parse 100 big lts.conf per second... speed doesn't matter at that level
18:44
(08:53:22 PM) alkisg: Heh. getltscfg speed: 0.5 msec in C, 4 msec in shell/awk, 8 msec in python.
18:44
<vagrantc>
python is typically also in C, so i'm not sure what you mean
18:45
<alkisg>
python libraries are in python
18:45
So it's very slower
18:45
If one uses only core python libraries, the ones that are written in c, then python is faster after the initial loading
18:47
<vagrantc>
well, as usual, you've been thorough :)
18:47
<alkisg>
parsing a 7 MB lts.conf:
18:47
getltscfg=0m0,079s
18:47
awk=0m0,461s
18:48
And that can be done server side, if we want it, so that it becomes zero time
18:51
vagrantc: btw: https://github.com/ltsp/ltsp/wiki/versioning
18:51
I noted down what I think we agreed on
19:09
<vagrantc>
alkisg: i don't understand the 19.04.10 version
19:10
<alkisg>
vagrantc: currently we only do distro-specific releases. Imagine the linux kernel and its lts releases. Suppose we want 19.04 to be an "lts release"
19:10
<vagrantc>
alkisg: but overall looks good
19:11
<alkisg>
That last counter then counts those releases
19:11
"it's the 10th release of the 19.04 series"
19:11
With only bug fixes there, no new features
19:11
<vagrantc>
alkisg: how is that different from 19.04.2 example ?
19:11
<alkisg>
19.04.2 is the latest upstream release, as we're still in april
19:11
while 19.04.10 may ship 2 years later
19:12
<vagrantc>
alkisg: i'd drop the distinction, personally ... and just have 19.04.N be increments
19:12
<alkisg>
I figured that difference doesn't matter much, to use different numbering
19:12
Right, it's 2 different use cases using the same counter
19:12
I think I did what you just proposed
19:13
<vagrantc>
i would just call them maintenance updates with an increment, and drop the line "within the same month"
19:13
if they happen to be in the same month or not doesn't matter much
19:14
i guess sometimes we've had other distros make "major" changes to support their distro in the same month.
19:15
(or day!)
19:15
been a while since that's happened, but i'd like to think the newer generation will be easier to package and we'll see more distros swimming upstream again :)
19:16kjackal has joined IRC (kjackal!~quassel@2a02:587:9a0a:1100:d97d:a226:af4d:1270)
19:22
<alkisg>
i mean, you release 19.04, then you discover a problem and next day you release 19.04.2
19:22
I don't imagine it will be very frequent, sure
19:23
<vagrantc>
i'm fine with increments fixing important bugs
19:28
alkisg: i'm getting excited at your work ... wish i had somewhere to deploy it :)
19:35
<alkisg>
Hehe
19:37
Hopefully it will also double as "boot this standalone machine in live mode", to test things without saving changes to disk.
19:37
So I'll use it to prevent my raspbian local installations from wearing out the sd card...
19:42
Oh and I'm also using netbooting frequently to troubleshoot local installation issues, hardware problems, even for cloning windows installations :D
19:42kjackal has left IRC (kjackal!~quassel@2a02:587:9a0a:1100:d97d:a226:af4d:1270, Ping timeout: 258 seconds)
19:43
<vagrantc>
yeah, at freegeek i used LTSP (and earlier on, lessdisks) as a general purpose operating system network boot troubleshooting, diagnostic, os installation, etc...
19:44
it was the busybox of OSes for me :)
19:45
really early on, not everything had built-in PXE, and that was annoying, but we had etherboot floppies :)
19:45
which makes it interesting to see iPXE being used more in LTSP ... it's kind of come full-circle :)
19:46
<alkisg>
I had some compex cards where etherboot worked, and later on gpxe/ipxe failed
19:46
I had to implement ltsp's kernel_device to work around that :D
19:47
The bad thing with syslinux is that it doesn't support variables at all
19:47
While grub and ipxe even implement a scripting language
20:13woernie has left IRC (woernie!~werner@pD9E8BADB.dip0.t-ipconnect.de, Remote host closed the connection)
21:01GodFather has joined IRC (GodFather!~rcc@143.59.184.72)
21:20ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
21:54Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
22:48vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)