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