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


Channel log from 9 March 2016   (all times are UTC)

02:30
<sbalneav>
No, functionally they're identical. The only reason would be if you needed features in webkit2 over webkit
03:26kd0204 has left IRC (kd0204!~Jd0302@host86-160-52-45.range86-160.btcentralplus.com, Read error: Connection reset by peer)
03:58vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
06:24alkisg_away is now known as alkisg
06:36ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:21alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)
07:24alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
07:57gehidore has left IRC (gehidore!~username@unaffiliated/man, Quit: WeeChat 1.4)
08:04mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
08:05gehidore has joined IRC (gehidore!~username@unaffiliated/man)
08:26kjackal has left IRC (kjackal!~kjackal@2a02:587:3110:5800:ddcc:f4ea:9ce8:23fd, Ping timeout: 246 seconds)
08:53kjackal has joined IRC (kjackal!~kjackal@onopfy.static.otenet.gr)
08:58lliurex-server has joined IRC (lliurex-server!c3391364@gateway/web/freenode/ip.195.57.19.100)
08:58
<lliurex-server>
no puedo desbloquear internet
08:59lliurex-server has left IRC (lliurex-server!c3391364@gateway/web/freenode/ip.195.57.19.100, Client Quit)
09:27F-GT has left IRC (F-GT!~phantom@ppp121-44-70-200.lns20.syd4.internode.on.net, Ping timeout: 244 seconds)
09:29F-GT has joined IRC (F-GT!~phantom@ppp121-44-70-200.lns20.syd4.internode.on.net)
10:10lbssousa has joined IRC (lbssousa!~laercio@177.143.61.50)
10:25adrianorg has left IRC (adrianorg!~adrianorg@177.18.169.51, Ping timeout: 240 seconds)
10:27adrianorg has joined IRC (adrianorg!~adrianorg@177.156.229.136)
10:39johnson has joined IRC (johnson!3e9fffbd@gateway/web/freenode/ip.62.159.255.189)
10:42
<johnson>
Hi
10:42
<alkisg>
Hello
10:51Faith has joined IRC (Faith!~paty_@unaffiliated/faith)
11:05ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
11:12markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
11:29johnson has left IRC (johnson!3e9fffbd@gateway/web/freenode/ip.62.159.255.189)
12:22Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
12:27alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 240 seconds)
12:27Parker955_Away has left IRC (Parker955_Away!~parker@2607:5300:60:8425::2d62:a8e6, Ping timeout: 240 seconds)
12:27stgraber has left IRC (stgraber!~stgraber@ubuntu/member/stgraber, Ping timeout: 240 seconds)
12:27alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
12:28stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber)
12:32Parker955_Away has joined IRC (Parker955_Away!~parker@2607:5300:60:8425::2d62:a8e6)
12:44kjackal has left IRC (kjackal!~kjackal@onopfy.static.otenet.gr, Ping timeout: 260 seconds)
12:44alkisg is now known as alkisg_away
13:36kjackal has joined IRC (kjackal!~kjackal@2a02:587:3110:5800:58ab:539e:d3d7:ca14)
13:55lbssousa has left IRC (lbssousa!~laercio@177.143.61.50, Ping timeout: 268 seconds)
13:56markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, )
14:16ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
14:16sbalneav has left IRC (sbalneav!~sbalneav@wnpgmb0412w-ds01-45-12-121.dynamic.mtsallstream.net, Ping timeout: 276 seconds)
14:30sbalneav has joined IRC (sbalneav!~sbalneav@wnpgmb0412w-ds01-45-12-121.dynamic.mtsallstream.net)
14:56ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
15:12NeonLicht has left IRC (NeonLicht!~NeonLicht@darwin.ugr.es, Remote host closed the connection)
15:17vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
15:21gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
15:24mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
15:33dtcrshr has left IRC (dtcrshr!~datacrush@unaffiliated/datacrusher, Ping timeout: 246 seconds)
16:04alkisg_away is now known as alkisg
16:30dtcrshr has joined IRC (dtcrshr!~datacrush@unaffiliated/datacrusher)
17:08jinnjus has left IRC (jinnjus!~user1@CPE788df72324c1-CM788df72324c0.cpe.net.cable.rogers.com, Ping timeout: 240 seconds)
17:58
<alkisg>
vagrantc: Hello! Question... sch-scripts recommends: ltsp-server, ltsp-client etc. And sch-scripts.postinst does: if [ ! -d /boot/pxelinux.cfg ]; then /usr/share/ltsp/update-kernels; fi
17:58
The problem I've seen is that sometimes /boot/pxelinux.cfg/ltsp is generated with NFS first, like if /etc/ltsp/update-kernels.conf => BOOT_METHODS was missing at the time update-kernels was called!
17:58
I can't think how that's possible, can you imagine any way for sch-scripts.postinst to get to run before /etc/ltsp/update-kernels.conf gets installed?!
18:00
To work around the issue, whatever that may be, would you mind if I changed this? ./client/share/ltsp/update-kernels:BOOT_METHODS=${BOOT_METHODS:-"NFS NBD AOE"}
18:00
...to have NBD first?
18:00
That way even if update-kernels.conf isn't present, NBD will still come first
18:01
The problematic pxelinux.cfg/ltsp is: http://paste.debian.net/413696/
18:02
Hmm it doesn't even have the correct kernels there...
18:04
Yup, if I remove /etc/ltsp/update-kernels.conf and run /usr/share/ltsp/update-kernels, then I can reproduce that specific pxelinux.cfg/ltsp file
18:04
But how it's possible for /usr/share/ltsp/update-kernels to exist while /etc/ltsp/update-kernels.conf does not exist, when both files are in ltsp-client-core, is beyond me...
18:13
vagrantc: I guess my question is, when ltsp-client-core is "unpacked" but not "configured" yet, does /etc/ltsp/update-kernels.conf exist?
18:14
How would I even check that? By writing a preinst script that runs `ls /etc/ltsp`?
18:26
<vagrantc>
wow
18:27
alkisg: why not just always run update-kernels ?
18:35vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 246 seconds)
18:37vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:49
<alkisg>
vagrantc: I do always run update-kernels from sch-scripts.postinst, but some times at that poin update-kernels.conf doesn't exist, and produces the wrong pxelinux.cfg/ltsp
18:50
<vagrantc>
pre-depends on ltsp-client-core ?
18:50
<alkisg>
err I mean, the problem is not that it doesn't run some times, it is that when it runs, it some times causes issues
18:50
no, sch-scripts just recommends ltsp-client
18:50
Should I make that predepends instead?
18:50
<vagrantc>
or maybe just depends, in that case ...
18:50
i'm not *sure* pre-depends will help ... generally to be avoided
18:51
<alkisg>
I can't see how depends will be different from recommends though, as update-kernels is there... it's update-kernels that's missing
18:51
And I don't even know how that's possible, unless files under /etc get special treatment even if they're shipped and not generated on postinst
18:52
*it's update-kernels.conf that's missing, sorry
18:53
It's also strange that it *sometimes* happens, not always... like a race condition somewhere
18:53
<vagrantc>
yeah, i get that ... files in /etc are sometimes treated as special snowflakes ... but i would expect them to be unpacked when the rest of the package files are unpacked
18:54
<alkisg>
Hmm maybe I could test if /etc/ltsp/update-kernels.conf doesn't exist, then sch-scripts.postinst should not call update-kernels... at least that will mitigate the issue
18:55
<vagrantc>
hrm.
18:58gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: $HOME)
19:10
<alkisg>
stgraber: there are a few fixes after the ltsp version that we got in 16.04. What's the last date that we can sync those with xenial? March 24th? https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule
19:11
For example, some systemd update yesterday broke getltscfg with non-ascii content in lts.conf, so it'd be nice to have that fix in 16.04...
19:12
(r2715 in ltsp-trunk)
19:20ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
19:24vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
19:33vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
19:44
<alkisg>
vagrantc: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2716
19:44
...what's the purpose of "eval" there?!
19:44
Doesn't that evaluate an empty string?
19:45
getltscfg -a gets the values, grep discards the "export" lines, and >> gets them to ltsp_config_env
19:45
There's nothing in stdout to be evaluated...
19:54
<vagrantc>
alkisg: artifact of history, i guess.
19:54
<alkisg>
vagrantc: should I remove that?
19:55
Maybe a "tee" was meant there, to duplicate the >> to stdout
19:56
<vagrantc>
you wouldn't want to exclude "export" then
19:57
<alkisg>
Well actually the variables shouldn't be exported in the environment...
19:57
But sure, ok, let's not ask for trouble :)
20:00
<vagrantc>
that would be a rewrite
20:00
the current implementation relies on the variables being exported for some features
20:01
<alkisg>
Usually the ltsp scripts are sourced, not executed, so they don't need the vars to be exported, but I imagine there might be a couple of cases where they're executed
20:02
<vagrantc>
or programs they're running on need them, etc.
20:02
it's been that way since before LTSP5 was called LTSP5 ... i don't think it makes sense to change it and still call it LTSP5
20:03
<alkisg>
CLIENT_ENV is not related to exported variables
20:03
No I mean that I think that if we just omit the export, it'll still work
20:03
Without changing any code anywhere...
20:03
<vagrantc>
i think there will be subtle breakages
20:04
and hard to track down
20:04
was fairly sure the screen scripts executed, too
20:04
<alkisg>
Yup, that part would be a pain, if it broke in 1-2 places
20:04
The screen scripts source ltsp_config
20:04
So they get the vars without needing them exported
20:05
<vagrantc>
i'm not sure what we really gain by making changes like that
20:05
<alkisg>
Sure, that was just theoretical, I wasn't suggesting that I want us to work on that
20:06
<vagrantc>
on the other hand, maybe it's already accidentally broken by the code you pointed out, and it's working as well as it's working :)
20:06
<alkisg>
But also in theory, it's not nice to have child processes have all the ltsp vars
20:06
<vagrantc>
yeah, i get that
20:06
it's time to make LTSP6 happen, and apply what we've learned all these years :)
20:07* alkisg isn't sure it'll be ltsp if we apply all that we've learned :)
20:07
<alkisg>
Maybe just "configd"...
20:08
Also, I'm not sure that ltsp6 will ever happen without some sponsorship...
20:25ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 240 seconds)
20:25ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
20:30alkisg is now known as alkisg_away
20:41Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving)
20:52ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:29kjackal has left IRC (kjackal!~kjackal@2a02:587:3110:5800:58ab:539e:d3d7:ca14, Ping timeout: 246 seconds)
23:04ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 268 seconds)
23:09ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
23:52Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas, Quit: Leaving.)